From 13ef12bae0666a1483fa5868d82be19738e53a4b Mon Sep 17 00:00:00 2001
From: "donatohorn@gmail.com" <donatohorn@gmail.com>
Date: Mon, 18 Jul 2022 21:56:01 -0300
Subject: [PATCH 001/272] [pt-br] add
 content/pt-br/docs/tasks/configure-pod-container/share-process-namespace.md

---
 .../share-process-namespace.md                | 131 ++++++++++++++++++
 .../pods/share-process-namespace.yaml         |  17 +++
 2 files changed, 148 insertions(+)
 create mode 100644 content/pt-br/docs/tasks/configure-pod-container/share-process-namespace.md
 create mode 100644 content/pt-br/examples/pods/share-process-namespace.yaml

diff --git a/content/pt-br/docs/tasks/configure-pod-container/share-process-namespace.md b/content/pt-br/docs/tasks/configure-pod-container/share-process-namespace.md
new file mode 100644
index 00000000000..d3161a8ad14
--- /dev/null
+++ b/content/pt-br/docs/tasks/configure-pod-container/share-process-namespace.md
@@ -0,0 +1,131 @@
+---
+title: Compartilhando o Namespace de Processo Entre Contêineres em um Pod
+update_date: 2022-07-16
+origin_version: 1.24
+contributors: DonatoHorn
+reviewers:
+- verb
+- yujuhong
+- dchen1107
+content_type: task
+weight: 160
+---
+
+<!-- overview -->
+
+Esta página mostra como configurar o compartilhamento de namespace de processos para um Pod. Quando
+O compartilhamento de namespace de processos está ativado, os processos em um Contêiner são visíveis
+para todos os outros Contêineres no mesmo Pod.
+
+Você pode usar este recurso para configurar Contêineres de cooperação, como um manipulador de log 
+`sidecar` de contêiner, ou para solucionar problemas em imagens de contêiner que não
+incluem utilitários de depuração como um shell.
+
+## {{% heading "prerequisites" %}}
+
+{{< include "task-tutorial-prereqs.md" >}}
+
+<!-- steps -->
+
+## Configure um pod
+
+O compartilhamento de namespace de processos é ativado usando o campo `shareProcessNamespace` da
+`.spec` para um Pod. Por exemplo:
+
+{{< codenew file="pods/share-process-namespace.yaml" >}}
+
+1. Crie o pod `nginx` no seu cluster:
+
+   ```shell
+   kubectl apply -f https://k8s.io/examples/pods/share-process-namespace.yaml
+   ```
+
+1. Conecte ao `shell` do contêiner e execute o comando `ps`:
+
+   ```shell
+   kubectl attach -it nginx -c shell
+   ```
+
+   Se você não vir um prompt de comando, tente pressionar Enter. No shell do Contêiner execute:
+
+   ```shell
+   # execute este comando dentro do "shell" do contêiner
+   ps ax
+   ```
+
+   A saída é semelhante a esta:
+
+   ```none
+   PID   USER     TIME  COMMAND
+       1 root      0:00 /pause
+       8 root      0:00 nginx: master process nginx -g daemon off;
+      14 101       0:00 nginx: worker process
+      15 root      0:00 sh
+      21 root      0:00 ps ax
+   ```
+
+Você pode sinalizar processos em outros Contêineres. Por exemplo, mandando `SIGHUP` ao
+`nginx` para restartar o processo `worker`. Isso requer a capacidade `SYS_PTRACE`.
+
+```shell
+# execute este comando dentro do "shell" do contêiner
+kill -HUP 8   # substitua o "8" pelo PID do processo principal do nginx, se necessário
+ps ax
+```
+
+A saída é semelhante a esta:
+
+```none
+PID   USER     TIME  COMMAND
+    1 root      0:00 /pause
+    8 root      0:00 nginx: master process nginx -g daemon off;
+   15 root      0:00 sh
+   22 101       0:00 nginx: worker process
+   23 root      0:00 ps ax
+```
+
+É até possível acessar o sistema de arquivos de outro contêiner usando o link
+`/proc/$pid/root`.
+
+```shell
+# execute este comando dentro do "shell" do contêiner
+# substitua o "8" pelo PID do processo Nginx, se necessario
+head /proc/8/root/etc/nginx/nginx.conf
+```
+
+A saída é semelhante a esta:
+
+```none
+user  nginx;
+worker_processes  1;
+
+error_log  /var/log/nginx/error.log warn;
+pid        /var/run/nginx.pid;
+
+
+events {
+    worker_connections  1024;
+```
+
+<!-- discussion -->
+
+## Compreendendo o compartilhamento de namespace de processos
+
+Os Pods compartilham muitos recursos, por isso faz sentido que eles também compartilhem um namespace de processo. 
+Alguns Contêineres podem esperar serem isolados de outros, no entanto,
+por isso, é importante entender as diferenças:
+
+1. **O processo de contêiner não tem mais o PID 1.** Alguns Contêineres recusam
+   começar sem o PID 1 (por exemplo, contêineres usando `systemd`) ou executando comandos 
+   como `kill -HUP 1` para sinalizar o processo de Contêiner. Em pods com um
+   namespace de processos compartilhado, `kill -HUP 1` irá sinalizar a `sandbox`
+   (`/pause` no exemplo acima).
+
+1. **Os processos são visíveis para outros contêineres no Pod.** Isso inclui todas
+   informações visíveis em `/proc`, como senhas que foram passadas como argumentos
+   ou variáveis de ambiente. Estes são protegidos apenas por permissões regulares do Unix.
+
+1. **Sistema de arquivos do Contêiner são visíveis para outros Contêineres do pod através do link
+   `/proc/$pid/root`.** Isso facilita a depuração, mas também significa
+   que os segredos do sistema de arquivos, são protegidos apenas por permissões de sistema de arquivos.
+
diff --git a/content/pt-br/examples/pods/share-process-namespace.yaml b/content/pt-br/examples/pods/share-process-namespace.yaml
new file mode 100644
index 00000000000..bd48bf0ff6e
--- /dev/null
+++ b/content/pt-br/examples/pods/share-process-namespace.yaml
@@ -0,0 +1,17 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: nginx
+spec:
+  shareProcessNamespace: true
+  containers:
+  - name: nginx
+    image: nginx
+  - name: shell
+    image: busybox:1.28
+    securityContext:
+      capabilities:
+        add:
+        - SYS_PTRACE
+    stdin: true
+    tty: true

From 14a6477abb696f535efad4fb718a69c1d7b1d4b3 Mon Sep 17 00:00:00 2001
From: "donatohorn@gmail.com" <donatohorn@gmail.com>
Date: Mon, 18 Jul 2022 22:26:15 -0300
Subject: [PATCH 002/272] [pt-br] add
 content/pt-br/docs/tasks/configure-pod-container/static-pod.md

---
 .../configure-pod-container/static-pod.md     | 248 ++++++++++++++++++
 1 file changed, 248 insertions(+)
 create mode 100644 content/pt-br/docs/tasks/configure-pod-container/static-pod.md

diff --git a/content/pt-br/docs/tasks/configure-pod-container/static-pod.md b/content/pt-br/docs/tasks/configure-pod-container/static-pod.md
new file mode 100644
index 00000000000..c7609582745
--- /dev/null
+++ b/content/pt-br/docs/tasks/configure-pod-container/static-pod.md
@@ -0,0 +1,248 @@
+---
+title: Criando Pods Estáticos
+weight: 170
+content_type: task
+update_date: 2022-07-16
+origin_version: 1.24
+contributors: DonatoHorn
+reviewers:
+- jsafrane
+---
+
+<!-- overview -->
+
+
+*Pods Estáticos* são gerenciados diretamente pelo `daemon` kubelet em um nó específico,
+sem o {{< glossary_tooltip text="servidor de API" term_id="kube-apiserver" >}}
+observando-os.
+Ao contrário dos pods que são gerenciados pelo `Control Plane` (por exemplo, uma
+{{< glossary_tooltip text="Implantação" term_id="deployment" >}});
+em vez disso, o kubelet observa cada Pod estático 
+(e reinicia-os se falharem).
+
+Pods estáticos estão sempre ligados a um {{< glossary_tooltip term_id="kubelet" >}} em um nó específico.
+
+O Kubelet tenta automaticamente criar um {{< glossary_tooltip text="mirror Pod" term_id="mirror-pod" >}}
+no servidor de API do Kubernetes para cada Pod estático.
+Isso significa que os pods em execução em um nó são visíveis no servidor de API,
+mas não podem ser controlados a partir daí.
+Aos nomes de Pods será acrescido um sufixo com o nome de host do nó, com um hífem. 
+
+
+{{< note >}}
+Se você está executando um cluster Kubernetes, usando Pods estáticos para executar um Pod em cada Nó,
+provávelmente você deveria estar usando um {{< glossary_tooltip text="DaemonSet" term_id="daemonset" >}} em substituição.
+{{< /note >}}
+
+{{< note >}}
+A `especificação` de um Pod estático não pode referir-se à outros objetos da API
+(ex., {{< glossary_tooltip text="Conta de Serviço" term_id="service-account" >}},
+{{< glossary_tooltip text="Mapa de Configuração" term_id="configmap" >}},
+{{< glossary_tooltip text="Segredo" term_id="secret" >}}, etc).
+{{< /note >}}
+
+## {{% heading "prerequisites" %}}
+
+{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
+
+Esta página assume que você está usando um {{< glossary_tooltip term_id="cri-o" >}} para executar os Pods,
+e que seus nós estão executando o sistema operacional Fedora.
+Instruções para outras distribuições, ou instalações de Kubernetes, podem variar.
+
+<!-- steps -->
+
+## Crie um pod estático {#static-pod-creation}
+
+Você pode configurar um Pod estático com um [arquivo de configuração hospedado no sistema de arquivos](/docs/tasks/configure-pod-container/static-pod/#configuration-files) ou um [arquivo de configuração hospedado na Web](/docs/tasks/configure-pod-container/static-pod/#pods-created-via-http).
+
+### Manifesto do Pod estático hospedado no sistema de arquivos {#configuration-files}
+
+Os manifestos, são definições de Pod padrão em formato JSON ou YAML em um diretório específico. Use o campo `staticPodPath: <diretório>` no
+[arquivo de configuração do kubelet](/docs/reference/config-api/kubelet-config.v1beta1/),
+que periodicamente varre o diretório e cria/exclui Pods estáticos conforme os arquivos YAML/JSON aparecem/desaparecem.
+Observe que o Kubelet ignorará os arquivos começando com pontos ao varrer o diretório especificado.
+
+Por exemplo, como iniciar um servidor Web simples como um Pod estático
+
+1. Escolha um nó onde você deseja executar um Pod estático. Neste exemplo, é `my-node1`.
+
+    ```shell
+    ssh my-node1
+    ```
+
+2. Escolha um diretório, digamos `/etc/kubernetes/manifests` e coloque uma definição de pod para um servidor web lá, por exemplo `/etc/kubernetes/manifests/static-web.yaml`:
+
+    ```shell
+    # Execute este comando no nó onde o Kubelet está funcionando
+    mkdir -p /etc/kubernetes/manifests/
+    cat <<EOF >/etc/kubernetes/manifests/static-web.yaml
+    apiVersion: v1
+    kind: Pod
+    metadata:
+      name: static-web
+      labels:
+        role: myrole
+    spec:
+      containers:
+        - name: web
+          image: nginx
+          ports:
+            - name: web
+              containerPort: 80
+              protocol: TCP
+    EOF
+    ```
+
+3. Configure seu kubelet no nó para usar este diretório executando-o com o argumento `--pod-manifest-path=/etc/kubernetes/manifests/`. No Fedora, edite o arquivo `/etc/kubernetes/kubelet` para incluir esta linha:
+
+   ```
+   KUBELET_ARGS="--cluster-dns=10.254.0.10 --cluster-domain=kube.local --pod-manifest-path=/etc/kubernetes/manifests/"
+   ```
+   ou adicione o campo `staticPodPath: <o diretótio>` no 
+   [arquivo de configuração do kubelet](/docs/reference/config-api/kubelet-config.v1beta1/).
+
+4. Reinicie o kubelet. No Fedora, você poderia executar:
+
+   ```shell
+   # Execute este comando no nó onde o kubelet está funcionando
+   systemctl restart kubelet
+   ```
+
+### Manifesto do Pod estático hospedado na Web {#pods-created-via-http}
+
+O Kubelet baixa periodicamente um arquivo especificado pelo argumento `--manifest-url=<URL>` 
+e interpreta-o como um arquivo JSON/YAML que contém as definições do Pod.
+Similar ao que [manifestos hospedados no sistema de arquivos](#configuration-files) fazem, o kubelet
+reexamina o manifesto em um agendamento. Se houver alterações na lista de Pods estáticos, o kubelet aplica-os.
+
+Para usar esta abordagem: 
+
+1. Crie um arquivo YAML e armazene-o em um servidor da Web, para que você possa passar o URL desse arquivo para o Kubelet.
+
+    ```yaml
+    apiVersion: v1
+    kind: Pod
+    metadata:
+      name: static-web
+      labels:
+        role: myrole
+    spec:
+      containers:
+        - name: web
+          image: nginx
+          ports:
+            - name: web
+              containerPort: 80
+              protocol: TCP
+    ```
+
+2. Configure o kubelet no seu nó selecionado para usar este manifesto da Web, executando-o com `--manifest-url=<manifest-url>`. No Fedora, edite `/etc/kubernetes/kubelet` para incluir esta linha:
+
+    ```
+    KUBELET_ARGS="--cluster-dns=10.254.0.10 --cluster-domain=kube.local --manifest-url=<manifest-url>"
+    ```
+
+3. Reinicie o Kubelet. No Fedora, você usaria:
+
+    ```shell
+    # Execute este comando no nó onde o kubelet está funcionando
+    systemctl restart kubelet
+    ```
+
+## Observe o comportamento do Pod estático {#behavior-of-static-pods}
+
+Quando o kubelet começa, inicia automaticamente todos os pods estáticos definidos. 
+Como você definiu um Pod estático e reiniciou o kubelet, o novo pod estático deveria
+já estar em execução.
+
+Você pode ver os Contêineres em execução (incluindo os Pods estáticos) ao executar (no Nó):
+
+```shell
+# Execute este comando no nó onde o kubelet está funcionando
+crictl ps
+```
+
+A saída pode ser algo como:
+
+```console
+CONTAINER       IMAGE                                 CREATED           STATE      NAME    ATTEMPT    POD ID
+129fd7d382018   docker.io/library/nginx@sha256:...    11 minutes ago    Running    web     0          34533c6729106
+```
+
+{{< note >}}
+`crictl` mostra a URI da imagem e o checksum SHA-256. O `NAME` vai parecer mais como:
+`docker.io/library/nginx@sha256:0d17b565c37bcbd895e9d92315a05c1c3c9a29f762b011a10c54a66cd53c9b31`.
+{{< /note >}}
+
+Você pode ver o Pod espelho no servidor de API:
+
+```shell
+kubectl get pods
+```
+```
+NAME         READY   STATUS    RESTARTS        AGE
+static-web   1/1     Running   0               2m
+```
+
+{{< note >}}
+Verifique se o Kubelet tem permissão para criar o Pod espelho no servidor de API. Caso contrário, a solicitação de criação é rejeitada pelo servidor de API. Veja [Admissão de segurança do pod](/docs/concepts/security/pod-security-admission) e [Políticas de Segurança de Pod](/docs/concepts/security/pod-security-policy/).
+{{< /note >}}
+
+Os {{< glossary_tooltip term_id="label" text="Rótulos" >}} dos pods estáticos são
+propagados no Pod espelho. Você pode usar esses rótulos como 
+{{< glossary_tooltip term_id="selector" text="seletores" >}} via normal, etc.
+
+Se você tentar usar o `kubectl` para excluir o Pod espelho do servidor de API,
+o kubelet _não_ remove o Pod estático:
+
+```shell
+kubectl delete pod static-web
+```
+```
+pod "static-web" deleted
+```
+Você pode ver que o Pod ainda está funcionando:
+```shell
+kubectl get pods
+```
+```
+NAME         READY   STATUS    RESTARTS   AGE
+static-web   1/1     Running   0          4s
+```
+
+De volta ao seu nó, onde o kubelet está funcionando, você pode tentar parar o Contêiner manualmente.
+Você verá que, depois de algum tempo, o Kubelet notará e reiniciará o Pod
+automaticamente:
+
+```shell
+# Execute esses comandos no nó onde o Kubelet está funcionando
+crictl stop 129fd7d382018 # substitua pelo ID do seu contêiner
+sleep 20
+crictl ps
+```
+```console
+CONTAINER       IMAGE                                 CREATED           STATE      NAME    ATTEMPT    POD ID
+89db4553e1eeb   docker.io/library/nginx@sha256:...    19 seconds ago    Running    web     1          34533c6729106
+```
+
+## Adição e remoção dinâmica de Pods estáticos
+
+O Kubelet em execução varre periodicamente o diretório configurado (`/etc/kubernetes/manifests` em nosso exemplo) por alterações, e adiciona/remove os pods à medida que os arquivos aparecem/desaparecem neste diretório.
+
+```shell
+# Pressupondo que você esteja usando a configuração de Pod estático hospedada no sistema de arquivos
+# Execute esses comandos no nó onde o Kubelet está funcionando
+#
+mv /etc/kubelet.d/static-web.yaml /tmp
+sleep 20
+crictl ps
+# Você vê que nenhum contêiner nginx está funcionando
+#
+mv /tmp/static-web.yaml  /etc/kubelet.d/
+sleep 20
+crictl ps
+```
+```console
+CONTAINER       IMAGE                                 CREATED           STATE      NAME    ATTEMPT    POD ID
+f427638871c35   docker.io/library/nginx@sha256:...    19 seconds ago    Running    web     1          34533c6729106
+```

From 4129eeb430fd747042fea310f481d3c0451a77b9 Mon Sep 17 00:00:00 2001
From: "donatohorn@gmail.com" <donatohorn@gmail.com>
Date: Fri, 22 Jul 2022 16:09:28 -0300
Subject: [PATCH 003/272] [pt-br] add
 content/pt-br/docs/tasks/configure-pod-container/static-pod.md

---
 content/pt-br/docs/tasks/configure-pod-container/static-pod.md | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/content/pt-br/docs/tasks/configure-pod-container/static-pod.md b/content/pt-br/docs/tasks/configure-pod-container/static-pod.md
index c7609582745..3447d39ab91 100644
--- a/content/pt-br/docs/tasks/configure-pod-container/static-pod.md
+++ b/content/pt-br/docs/tasks/configure-pod-container/static-pod.md
@@ -2,9 +2,6 @@
 title: Criando Pods Estáticos
 weight: 170
 content_type: task
-update_date: 2022-07-16
-origin_version: 1.24
-contributors: DonatoHorn
 reviewers:
 - jsafrane
 ---

From 00a58ac4662bca01aa2154a188ceb2ed49e5003c Mon Sep 17 00:00:00 2001
From: "donatohorn@gmail.com" <donatohorn@gmail.com>
Date: Fri, 22 Jul 2022 16:14:44 -0300
Subject: [PATCH 004/272] [pt-br] add
 content/pt-br/docs/tasks/configure-pod-container/share-process-namespace.md

---
 .../tasks/configure-pod-container/share-process-namespace.md   | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/content/pt-br/docs/tasks/configure-pod-container/share-process-namespace.md b/content/pt-br/docs/tasks/configure-pod-container/share-process-namespace.md
index d3161a8ad14..e26f1f4895f 100644
--- a/content/pt-br/docs/tasks/configure-pod-container/share-process-namespace.md
+++ b/content/pt-br/docs/tasks/configure-pod-container/share-process-namespace.md
@@ -1,8 +1,5 @@
 ---
 title: Compartilhando o Namespace de Processo Entre Contêineres em um Pod
-update_date: 2022-07-16
-origin_version: 1.24
-contributors: DonatoHorn
 reviewers:
 - verb
 - yujuhong

From 93af2becccfbcc31c2bc134e8ad5647964c64837 Mon Sep 17 00:00:00 2001
From: lakshmi <thummala.prasuna@india.nec.com>
Date: Fri, 2 Dec 2022 15:13:10 +0530
Subject: [PATCH 005/272] Updated Owners and Dependents page

---
 .../working-with-objects/owners-dependents.md | 22 ++++++++++---------
 1 file changed, 12 insertions(+), 10 deletions(-)

diff --git a/content/en/docs/concepts/overview/working-with-objects/owners-dependents.md b/content/en/docs/concepts/overview/working-with-objects/owners-dependents.md
index fd11031ab3c..9e09dc31b13 100644
--- a/content/en/docs/concepts/overview/working-with-objects/owners-dependents.md
+++ b/content/en/docs/concepts/overview/working-with-objects/owners-dependents.md
@@ -6,13 +6,13 @@ weight: 90
 
 <!-- overview -->
 
-In Kubernetes, some objects are *owners* of other objects. For example, a
-{{<glossary_tooltip text="ReplicaSet" term_id="replica-set">}} is the owner of a set of Pods. These owned objects are *dependents*
+In Kubernetes, some {{< glossary_tooltip text="objects" term_id="Object" >}} are *owners* of other objects. For example, a
+{{<glossary_tooltip text="ReplicaSet" term_id="replica-set">}} is the owner of a set of {{<glossary_tooltip text="Pods" term_id="pod">}}. These owned objects are *dependents*
 of their owner. 
 
 Ownership is different from the [labels and selectors](/docs/concepts/overview/working-with-objects/labels/)
 mechanism that some resources also use. For example, consider a Service that 
-creates `EndpointSlice` objects. The Service uses labels to allow the control plane to
+creates `EndpointSlice` objects. The Service uses {{<glossary_tooltip text="labels" term_id="label">}} to allow the control plane to
 determine which `EndpointSlice` objects are used for that Service. In addition
 to the labels, each `EndpointSlice` that is managed on behalf of a Service has
 an owner reference. Owner references help different parts of Kubernetes avoid
@@ -21,8 +21,8 @@ interfering with objects they don’t control.
 ## Owner references in object specifications
 
 Dependent objects have a `metadata.ownerReferences` field that references their
-owner object. A valid owner reference consists of the object name and a UID
-within the same namespace as the dependent object. Kubernetes sets the value of
+owner object. A valid owner reference consists of the object name and a {{<glossary_tooltip text="UID" term_id="uid">}} 
+within the same {{<glossary_tooltip text="namespace" term_id="namespace">}} as the dependent object. Kubernetes sets the value of
 this field automatically for objects that are dependents of other objects like
 ReplicaSets, DaemonSets, Deployments, Jobs and CronJobs, and ReplicationControllers.
 You can also configure these relationships manually by changing the value of
@@ -66,10 +66,10 @@ When you tell Kubernetes to delete a resource, the API server allows the
 managing controller to process any [finalizer rules](/docs/concepts/overview/working-with-objects/finalizers/)
 for the resource. {{<glossary_tooltip text="Finalizers" term_id="finalizer">}}
 prevent accidental deletion of resources your cluster may still need to function
-correctly. For example, if you try to delete a `PersistentVolume` that is still
+correctly. For example, if you try to delete a [PersistentVolume](/docs/concepts/storage/persistent-volumes/) that is still
 in use by a Pod, the deletion does not happen immediately because the
 `PersistentVolume` has the `kubernetes.io/pv-protection` finalizer on it.
-Instead, the volume remains in the `Terminating` status until Kubernetes clears
+Instead, the [volume](/docs/concepts/storage/volumes/) remains in the `Terminating` status until Kubernetes clears
 the finalizer, which only happens after the `PersistentVolume` is no longer
 bound to a Pod. 
 
@@ -84,6 +84,8 @@ object.
 
 ## {{% heading "whatsnext" %}}
 
-* Learn more about [Kubernetes finalizers](/docs/concepts/overview/working-with-objects/finalizers/).
-* Learn about [garbage collection](/docs/concepts/architecture/garbage-collection).
-* Read the API reference for [object metadata](/docs/reference/kubernetes-api/common-definitions/object-meta/#System).
\ No newline at end of file
+Learn more about the following:
+* [Kubernetes finalizers](/docs/concepts/overview/working-with-objects/finalizers/).
+* [garbage collection](/docs/concepts/architecture/garbage-collection).
+* API reference for [object metadata](/docs/reference/kubernetes-api/common-definitions/object-meta/#System).
+* Objets such as [ReplicaSets](/docs/concepts/workloads/controllers/replicaset/), [DaemonSets](/docs/concepts/workloads/controllers/daemonset/), [Deployments](/docs/concepts/workloads/controllers/deployment/), [Jobs](/docs/concepts/workloads/controllers/job/), [CronJobs](/docs/concepts/workloads/controllers/cron-jobs/) and [ReplicationControllers](/docs/concepts/workloads/controllers/replicationcontroller/). 

From ca16a714c78d51da4296acd2fffde94a0bd84373 Mon Sep 17 00:00:00 2001
From: Mengjiao Liu <mengjiao.liu@daocloud.io>
Date: Mon, 19 Dec 2022 11:28:47 +0800
Subject: [PATCH 007/272] Move volume expansion feature gates to removed
 feature gates list

---
 .../feature-gates-removed.md                    | 17 +++++++++++++++++
 .../feature-gates.md                            | 14 --------------
 2 files changed, 17 insertions(+), 14 deletions(-)

diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates-removed.md b/content/en/docs/reference/command-line-tools-reference/feature-gates-removed.md
index 26f6663e902..cc095f28330 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates-removed.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates-removed.md
@@ -127,6 +127,15 @@ In the following table:
 | `EvenPodsSpread` | `false` | Alpha | 1.16 | 1.17 |
 | `EvenPodsSpread` | `true` | Beta | 1.18 | 1.18 |
 | `EvenPodsSpread` | `true` | GA | 1.19 | 1.21 |
+| `ExpandCSIVolumes` | `false` | Alpha | 1.14 | 1.15 |
+| `ExpandCSIVolumes` | `true` | Beta | 1.16 | 1.23 |
+| `ExpandCSIVolumes` | `true` | GA | 1.24 | 1.27 |
+| `ExpandInUsePersistentVolumes` | `false` | Alpha | 1.11 | 1.14 |
+| `ExpandInUsePersistentVolumes` | `true` | Beta | 1.15 | 1.23 |
+| `ExpandInUsePersistentVolumes` | `true` | GA | 1.24 | 1.27 |
+| `ExpandPersistentVolumes` | `false` | Alpha | 1.8 | 1.10 |
+| `ExpandPersistentVolumes` | `true` | Beta | 1.11 | 1.23 |
+| `ExpandPersistentVolumes` | `true` | GA | 1.24 | 1.27 |
 | `ExperimentalCriticalPodAnnotation` | `false` | Alpha | 1.5 | 1.12 |
 | `ExperimentalCriticalPodAnnotation` | `false` | Deprecated | 1.13 | 1.16 |
 | `ExternalPolicyForExternalIP` | `true` | GA | 1.18 | 1.22 |
@@ -470,6 +479,14 @@ In the following table:
 - `EvenPodsSpread`: Enable pods to be scheduled evenly across topology domains. See
   [Pod Topology Spread Constraints](/docs/concepts/scheduling-eviction/topology-spread-constraints/).
 
+- `ExpandCSIVolumes`: Enable the expanding of CSI volumes.
+
+- `ExpandInUsePersistentVolumes`: Enable expanding in-use PVCs. See
+  [Resizing an in-use PersistentVolumeClaim](/docs/concepts/storage/persistent-volumes/#resizing-an-in-use-persistentvolumeclaim).
+
+- `ExpandPersistentVolumes`: Enable the expanding of persistent volumes. See
+  [Expanding Persistent Volumes Claims](/docs/concepts/storage/persistent-volumes/#expanding-persistent-volumes-claims).
+
 - `ExperimentalCriticalPodAnnotation`: Enable annotating specific pods as *critical*
   so that their [scheduling is guaranteed](/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/).
   This feature is deprecated by Pod Priority and Preemption as of v1.13.
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 48de9a13dd2..eb293652925 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
@@ -282,15 +282,6 @@ For a reference to old feature gates that are removed, please refer to
 | `EphemeralContainers` | `true` | GA | 1.25 | - |
 | `EventedPLEG` | `false` | Alpha | 1.26 | - |
 | `ExecProbeTimeout` | `true` | GA | 1.20 | - |
-| `ExpandCSIVolumes` | `false` | Alpha | 1.14 | 1.15 |
-| `ExpandCSIVolumes` | `true` | Beta | 1.16 | 1.23 |
-| `ExpandCSIVolumes` | `true` | GA | 1.24 | - |
-| `ExpandInUsePersistentVolumes` | `false` | Alpha | 1.11 | 1.14 |
-| `ExpandInUsePersistentVolumes` | `true` | Beta | 1.15 | 1.23 |
-| `ExpandInUsePersistentVolumes` | `true` | GA | 1.24 | - |
-| `ExpandPersistentVolumes` | `false` | Alpha | 1.8 | 1.10 |
-| `ExpandPersistentVolumes` | `true` | Beta | 1.11 | 1.23 |
-| `ExpandPersistentVolumes` | `true` | GA | 1.24 |- |
 | `IdentifyPodOS` | `false` | Alpha | 1.23 | 1.23 |
 | `IdentifyPodOS` | `true` | Beta | 1.24 | 1.24 |
 | `IdentifyPodOS` | `true` | GA | 1.25 | - |
@@ -553,15 +544,10 @@ Each feature gate is designed for enabling/disabling a specific feature:
   This feature gate exists in case any of your existing workloads depend on a
   now-corrected fault where Kubernetes ignored exec probe timeouts. See
   [readiness probes](/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#configure-probes).
-- `ExpandCSIVolumes`: Enable the expanding of CSI volumes.
 - `ExpandedDNSConfig`: Enable kubelet and kube-apiserver to allow more DNS
   search paths and longer list of DNS search paths. This feature requires container
   runtime support(Containerd: v1.5.6 or higher, CRI-O: v1.22 or higher). See
   [Expanded DNS Configuration](/docs/concepts/services-networking/dns-pod-service/#expanded-dns-configuration).
-- `ExpandInUsePersistentVolumes`: Enable expanding in-use PVCs. See
-  [Resizing an in-use PersistentVolumeClaim](/docs/concepts/storage/persistent-volumes/#resizing-an-in-use-persistentvolumeclaim).
-- `ExpandPersistentVolumes`: Enable the expanding of persistent volumes. See
-  [Expanding Persistent Volumes Claims](/docs/concepts/storage/persistent-volumes/#expanding-persistent-volumes-claims).
 - `ExperimentalHostUserNamespaceDefaulting`: Enabling the defaulting user
   namespace to host. This is for containers that are using other host namespaces,
   host mounts, or containers that are privileged or using specific non-namespaced

From 0201ddd70f13adf7f21e1ebc08c0cc3eadb525d8 Mon Sep 17 00:00:00 2001
From: Mengjiao Liu <mengjiao.liu@daocloud.io>
Date: Mon, 19 Dec 2022 11:08:02 +0800
Subject: [PATCH 008/272] Update MinDomainsInPodTopologySpread feature gate
 default value.

---
 .../reference/command-line-tools-reference/feature-gates.md    | 3 ++-
 1 file 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 48de9a13dd2..ae69a369316 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
@@ -139,7 +139,8 @@ For a reference to old feature gates that are removed, please refer to
 | `MemoryManager` | `true` | Beta | 1.22 | |
 | `MemoryQoS` | `false` | Alpha | 1.22 | |
 | `MinDomainsInPodTopologySpread` | `false` | Alpha | 1.24 | 1.24 |
-| `MinDomainsInPodTopologySpread` | `false` | Beta | 1.25 | |
+| `MinDomainsInPodTopologySpread` | `false` | Beta | 1.25 | 1.26 |
+| `MinDomainsInPodTopologySpread` | `true` | Beta | 1.27 | |
 | `MixedProtocolLBService` | `false` | Alpha | 1.20 | 1.23 |
 | `MixedProtocolLBService` | `true` | Beta | 1.24 | |
 | `MultiCIDRRangeAllocator` | `false` | Alpha | 1.25 | |

From fed60f3728f84bd163e5315a7a18caee44eb7382 Mon Sep 17 00:00:00 2001
From: Wei Huang <weihuang@apple.com>
Date: Mon, 9 Jan 2023 12:29:33 -0800
Subject: [PATCH 009/272] Rename 'PreemptionByKubeScheduler' to
 'PreemptionByScheduler'

---
 content/en/docs/concepts/workloads/pods/disruptions.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/concepts/workloads/pods/disruptions.md b/content/en/docs/concepts/workloads/pods/disruptions.md
index 66d05ef92a3..1ddbfa4c2aa 100644
--- a/content/en/docs/concepts/workloads/pods/disruptions.md
+++ b/content/en/docs/concepts/workloads/pods/disruptions.md
@@ -247,7 +247,7 @@ that the Pod is about to be deleted due to a {{<glossary_tooltip term_id="disrup
 The `reason` field of the condition additionally
 indicates one of the following reasons for the Pod termination:
 
-`PreemptionByKubeScheduler`
+`PreemptionByScheduler`
 : Pod is due to be {{<glossary_tooltip term_id="preemption" text="preempted">}} by a scheduler in order to accommodate a new Pod with a higher priority. For more information, see [Pod priority preemption](/docs/concepts/scheduling-eviction/pod-priority-preemption/).
 
 `DeletionByTaintManager`

From 1f612943ad02f18bbceff2d27bd8283b26fb5083 Mon Sep 17 00:00:00 2001
From: lakshmi <thummala.prasuna@india.nec.com>
Date: Wed, 18 Jan 2023 12:53:53 +0530
Subject: [PATCH 010/272] revert the previous changes for what's next session.

---
 .../overview/working-with-objects/owners-dependents.md    | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/content/en/docs/concepts/overview/working-with-objects/owners-dependents.md b/content/en/docs/concepts/overview/working-with-objects/owners-dependents.md
index 9e09dc31b13..035298930ba 100644
--- a/content/en/docs/concepts/overview/working-with-objects/owners-dependents.md
+++ b/content/en/docs/concepts/overview/working-with-objects/owners-dependents.md
@@ -84,8 +84,6 @@ object.
 
 ## {{% heading "whatsnext" %}}
 
-Learn more about the following:
-* [Kubernetes finalizers](/docs/concepts/overview/working-with-objects/finalizers/).
-* [garbage collection](/docs/concepts/architecture/garbage-collection).
-* API reference for [object metadata](/docs/reference/kubernetes-api/common-definitions/object-meta/#System).
-* Objets such as [ReplicaSets](/docs/concepts/workloads/controllers/replicaset/), [DaemonSets](/docs/concepts/workloads/controllers/daemonset/), [Deployments](/docs/concepts/workloads/controllers/deployment/), [Jobs](/docs/concepts/workloads/controllers/job/), [CronJobs](/docs/concepts/workloads/controllers/cron-jobs/) and [ReplicationControllers](/docs/concepts/workloads/controllers/replicationcontroller/). 
+* Learn more about [Kubernetes finalizers](/docs/concepts/overview/working-with-objects/finalizers/).
+* Learn about [garbage collection](/docs/concepts/architecture/garbage-collection).
+* Read the API reference for [object metadata](/docs/reference/kubernetes-api/common-definitions/object-meta/#System).

From c1bf88e71e530cb534cf01433021e042a33af1bd Mon Sep 17 00:00:00 2001
From: Sascha Grunert <sgrunert@redhat.com>
Date: Wed, 18 Jan 2023 13:55:45 +0100
Subject: [PATCH 011/272] Update seccomp docs for v1.27

seccomp annotation will become non-functional in v1.27, which will be
now reflected in the documentation as well.

Ref: https://github.com/kubernetes/kubernetes/pull/114947

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
---
 .../labels-annotations-taints/_index.md       | 24 ++++++++-----------
 content/en/docs/tutorials/security/seccomp.md | 16 ++++---------
 2 files changed, 15 insertions(+), 25 deletions(-)

diff --git a/content/en/docs/reference/labels-annotations-taints/_index.md b/content/en/docs/reference/labels-annotations-taints/_index.md
index 75974454588..514e4c921a8 100644
--- a/content/en/docs/reference/labels-annotations-taints/_index.md
+++ b/content/en/docs/reference/labels-annotations-taints/_index.md
@@ -737,23 +737,19 @@ When the PodSecurityPolicy admission controller admitted a Pod, the admission co
 modified the Pod to have this annotation.
 The value of the annotation was the name of the PodSecurityPolicy that was used for validation.
 
-### seccomp.security.alpha.kubernetes.io/pod (deprecated) {#seccomp-security-alpha-kubernetes-io-pod}
+### seccomp.security.alpha.kubernetes.io/pod (non-functional) {#seccomp-security-alpha-kubernetes-io-pod}
 
-This annotation has been deprecated since Kubernetes v1.19 and will become non-functional in a future release.
-please use the corresponding pod or container `securityContext.seccompProfile` field instead.
-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.
+Older versions of Kubernetes allowed you to configure seccomp
+behavior using this {{< glossary_tooltip text="annotation" term_id="annotation" >}}.
+See [Restrict a Container's Syscalls with seccomp](/docs/tutorials/security/seccomp/) to
+learn the supported way to specify seccomp restrictions for a Pod.
 
-### container.seccomp.security.alpha.kubernetes.io/[NAME] (deprecated) {#container-seccomp-security-alpha-kubernetes-io}
+### container.seccomp.security.alpha.kubernetes.io/[NAME] (non-functional) {#container-seccomp-security-alpha-kubernetes-io}
 
-This annotation has been deprecated since Kubernetes v1.19 and will become non-functional in a future release.
-please use the corresponding pod or container `securityContext.seccompProfile` field instead.
-The tutorial [Restrict a Container's Syscalls with seccomp](/docs/tutorials/security/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`.
+Older versions of Kubernetes allowed you to configure seccomp
+behavior using this {{< glossary_tooltip text="annotation" term_id="annotation" >}}.
+See [Restrict a Container's Syscalls with seccomp](/docs/tutorials/security/seccomp/) to
+learn the supported way to specify seccomp restrictions for a Pod.
 
 ### snapshot.storage.kubernetes.io/allowVolumeModeChange
 
diff --git a/content/en/docs/tutorials/security/seccomp.md b/content/en/docs/tutorials/security/seccomp.md
index 6187d198f19..05b2fde77f1 100644
--- a/content/en/docs/tutorials/security/seccomp.md
+++ b/content/en/docs/tutorials/security/seccomp.md
@@ -275,17 +275,11 @@ Here's a manifest for that Pod:
 {{< codenew file="pods/security/seccomp/ga/audit-pod.yaml" >}}
 
 {{< 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 a future release of Kubernetes. Please always use
-the native API fields in favor of the annotations.
-
-Since Kubernetes v1.25, kubelets no longer support the annotations, use of the
-annotations in static pods is no longer supported, and the seccomp annotations
-are no longer auto-populated when pods with seccomp fields are created.
-Auto-population of the seccomp fields from the annotations is planned to be
-removed in a future release.
+Older versions of Kubernetes allowed you to configure seccomp
+behavior using {{< glossary_tooltip text="annotations" term_id="annotation" >}}.
+Kubernetes {{< skew currentVersion >}} only supports using fields within
+`.spec.securityContext` to configure seccomp, and this tutorial explains that
+approach.
 {{< /note >}}
 
 Create the Pod in the cluster:

From 7093775c888405bf72e1202a746fa04812e54155 Mon Sep 17 00:00:00 2001
From: "jack.casey" <jack.casey@visier.com>
Date: Mon, 6 Feb 2023 16:38:58 -0800
Subject: [PATCH 012/272] Improve grammar in etcd glossary

---
 content/en/docs/reference/glossary/etcd.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/reference/glossary/etcd.md b/content/en/docs/reference/glossary/etcd.md
index 474b923caf1..3689df2b1d7 100644
--- a/content/en/docs/reference/glossary/etcd.md
+++ b/content/en/docs/reference/glossary/etcd.md
@@ -17,6 +17,6 @@ tags:
 
 If your Kubernetes cluster uses etcd as its backing store, make sure you have a
 [back up](/docs/tasks/administer-cluster/configure-upgrade-etcd/#backing-up-an-etcd-cluster) plan
-for those data.
+for the data.
 
 You can find in-depth information about etcd in the official [documentation](https://etcd.io/docs/).

From 4480cd3634a1e511f7e926d7a69fb9f581a5d126 Mon Sep 17 00:00:00 2001
From: Paco Xu <paco.xu@daocloud.io>
Date: Wed, 1 Mar 2023 13:37:38 +0800
Subject: [PATCH 013/272] removed ControllerManagerLeaderMigration in v1.27

Signed-off-by: Paco Xu <paco.xu@daocloud.io>
---
 .../feature-gates-removed.md                          | 10 ++++++++++
 .../command-line-tools-reference/feature-gates.md     | 11 -----------
 .../controller-manager-leader-migration.md            |  2 --
 3 files changed, 10 insertions(+), 13 deletions(-)

diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates-removed.md b/content/en/docs/reference/command-line-tools-reference/feature-gates-removed.md
index fea125c3763..5536e254b48 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates-removed.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates-removed.md
@@ -93,6 +93,9 @@ In the following table:
 | `CronJobControllerV2` | `true` | GA | 1.22 | 1.23 |
 | `CSRDuration` | `true` | Beta | 1.22 | 1.23 |
 | `CSRDuration` | `true` | GA | 1.24 | 1.25 |
+| `ControllerManagerLeaderMigration` | `false` | Alpha | 1.21 | 1.21 |
+| `ControllerManagerLeaderMigration` | `true` | Beta | 1.22 | 1.23 |
+| `ControllerManagerLeaderMigration` | `true` | GA | 1.24 | 1.26 |
 | `CustomPodDNS` | `false` | Alpha | 1.9 | 1.9 |
 | `CustomPodDNS` | `true` | Beta| 1.10 | 1.13 |
 | `CustomPodDNS` | `true` | GA | 1.14 | 1.16 |
@@ -477,6 +480,13 @@ In the following table:
   {{< glossary_tooltip text="CronJob" term_id="cronjob" >}} controller. Otherwise,
   version 1 of the same controller is selected.
 
+- `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.
+
 - `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.
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 d9b2505960a..3680548e7af 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
@@ -251,9 +251,6 @@ For a reference to old feature gates that are removed, please refer to
 | `CSIStorageCapacity` | `true` | Beta | 1.21 | 1.23 |
 | `CSIStorageCapacity` | `true` | GA | 1.24 | - |
 | `ConsistentHTTPGetHandlers` | `true` | GA | 1.25 | - |
-| `ControllerManagerLeaderMigration` | `false` | Alpha | 1.21 | 1.21 |
-| `ControllerManagerLeaderMigration` | `true` | Beta | 1.22 | 1.23 |
-| `ControllerManagerLeaderMigration` | `true` | GA | 1.24 | - |
 | `DaemonSetUpdateSurge` | `false` | Alpha | 1.21 | 1.21 |
 | `DaemonSetUpdateSurge` | `true` | Beta | 1.22 | 1.24 |
 | `DaemonSetUpdateSurge` | `true` | GA | 1.25 | - |
@@ -390,12 +387,6 @@ Each feature gate is designed for enabling/disabling a specific feature:
   See [AppArmor Tutorial](/docs/tutorials/security/apparmor/) for more details.
 - `ContainerCheckpoint`: Enables the kubelet `checkpoint` API.
   See [Kubelet Checkpoint API](/docs/reference/node/kubelet-checkpoint-api/) 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
-  (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/).
 - `CPUManagerPolicyAlphaOptions`: This allows fine-tuning of CPUManager policies,
@@ -467,8 +458,6 @@ Each feature gate is designed for enabling/disabling a specific feature:
   handlers with probers.
 - `ContextualLogging`: When you enable this feature gate, Kubernetes components that support
    contextual logging add extra detail to log output.
-- `ControllerManagerLeaderMigration`: Enables leader migration for
-  `kube-controller-manager` and `cloud-controller-manager`.
 - `CronJobTimeZone`: Allow the use of the `timeZone` optional field in [CronJobs](/docs/concepts/workloads/controllers/cron-jobs/)
 - `CrossNamespaceVolumeDataSource`: Enable the usage of cross namespace volume data source
    to allow you to specify a source namespace in the `dataSourceRef` field of a
diff --git a/content/en/docs/tasks/administer-cluster/controller-manager-leader-migration.md b/content/en/docs/tasks/administer-cluster/controller-manager-leader-migration.md
index 743e23d0bd1..c31f309b190 100644
--- a/content/en/docs/tasks/administer-cluster/controller-manager-leader-migration.md
+++ b/content/en/docs/tasks/administer-cluster/controller-manager-leader-migration.md
@@ -10,8 +10,6 @@ weight: 250
 
 <!-- overview -->
 
-{{< feature-state for_k8s_version="v1.24" state="stable"  >}}
-
 {{< glossary_definition term_id="cloud-controller-manager" length="all" prepend="The cloud-controller-manager is">}}
 
 ## Background

From 51ed819df191783bc07584eeba561cea017c6962 Mon Sep 17 00:00:00 2001
From: "donatohorn@gmail.com" <donatohorn@gmail.com>
Date: Sun, 5 Mar 2023 13:33:43 +1300
Subject: [PATCH 014/272] [pt-br] Add
 content/pt-br/docs/tasks/configure-pod-container/static-pod.md

---
 .../docs/tasks/configure-pod-container/static-pod.md      | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/content/pt-br/docs/tasks/configure-pod-container/static-pod.md b/content/pt-br/docs/tasks/configure-pod-container/static-pod.md
index 3447d39ab91..805e6d04949 100644
--- a/content/pt-br/docs/tasks/configure-pod-container/static-pod.md
+++ b/content/pt-br/docs/tasks/configure-pod-container/static-pod.md
@@ -23,7 +23,7 @@ O Kubelet tenta automaticamente criar um {{< glossary_tooltip text="mirror Pod"
 no servidor de API do Kubernetes para cada Pod estático.
 Isso significa que os pods em execução em um nó são visíveis no servidor de API,
 mas não podem ser controlados a partir daí.
-Aos nomes de Pods será acrescido um sufixo com o nome de host do nó, com um hífem. 
+Aos nomes de Pods será sufixados com o nome de host do nó, com um hífem a esquerda. 
 
 
 {{< note >}}
@@ -33,9 +33,9 @@ provávelmente você deveria estar usando um {{< glossary_tooltip text="DaemonSe
 
 {{< note >}}
 A `especificação` de um Pod estático não pode referir-se à outros objetos da API
-(ex., {{< glossary_tooltip text="Conta de Serviço" term_id="service-account" >}},
-{{< glossary_tooltip text="Mapa de Configuração" term_id="configmap" >}},
-{{< glossary_tooltip text="Segredo" term_id="secret" >}}, etc).
+(ex., {{< glossary_tooltip text="ServiceAccount" term_id="service-account" >}},
+{{< glossary_tooltip text="ConfigMap" term_id="configmap" >}},
+{{< glossary_tooltip text="Secret" term_id="secret" >}}, etc).
 {{< /note >}}
 
 ## {{% heading "prerequisites" %}}

From fc019615abd2ab1dc0008d28875720349ff9b2be Mon Sep 17 00:00:00 2001
From: Wei Huang <weihuang@apple.com>
Date: Mon, 6 Mar 2023 09:02:48 -0800
Subject: [PATCH 015/272] Doc for Beta feature PodSchedulingReadiness

---
 .../concepts/scheduling-eviction/pod-scheduling-readiness.md  | 2 +-
 .../reference/command-line-tools-reference/feature-gates.md   | 3 ++-
 content/en/examples/pods/pod-with-scheduling-gates.yaml       | 4 ++--
 3 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/content/en/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md b/content/en/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md
index be999463155..07064386701 100644
--- a/content/en/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md
+++ b/content/en/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md
@@ -55,7 +55,7 @@ kubectl get pod test-pod -o jsonpath='{.spec.schedulingGates}'
 The output is:
 
 ```none
-[{"name":"foo"},{"name":"bar"}]
+[{"name":"example.com/foo"},{"name":"example.com/bar"}]
 ```
 
 To inform scheduler this Pod is ready for scheduling, you can remove its `schedulingGates` entirely
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 3680548e7af..2d1cf00ffa6 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
@@ -164,7 +164,8 @@ For a reference to old feature gates that are removed, please refer to
 | `PodDisruptionConditions` | `false` | Alpha | 1.25 | 1.25 |
 | `PodDisruptionConditions` | `true` | Beta | 1.26 | |
 | `PodHasNetworkCondition` | `false` | Alpha | 1.25 | |
-| `PodSchedulingReadiness` | `false` | Alpha | 1.26 | |
+| `PodSchedulingReadiness` | `false` | Alpha | 1.26 | 1.26 |
+| `PodSchedulingReadiness` | `true` | Beta | 1.27 | |
 | `ProbeTerminationGracePeriod` | `false` | Alpha | 1.21 | 1.21 |
 | `ProbeTerminationGracePeriod` | `false` | Beta | 1.22 | 1.24 |
 | `ProbeTerminationGracePeriod` | `true` | Beta | 1.25 | |
diff --git a/content/en/examples/pods/pod-with-scheduling-gates.yaml b/content/en/examples/pods/pod-with-scheduling-gates.yaml
index b0b012fb72c..de761d96946 100644
--- a/content/en/examples/pods/pod-with-scheduling-gates.yaml
+++ b/content/en/examples/pods/pod-with-scheduling-gates.yaml
@@ -4,8 +4,8 @@ metadata:
   name: test-pod
 spec:
   schedulingGates:
-  - name: foo
-  - name: bar
+  - name: example.com/foo
+  - name: example.com/bar
   containers:
   - name: pause
     image: registry.k8s.io/pause:3.6

From d84256921bc738f87508792e7a9a8997daa7d373 Mon Sep 17 00:00:00 2001
From: Alex Wang <wangqingcan1990@gmail.com>
Date: Tue, 7 Mar 2023 11:07:09 +0800
Subject: [PATCH 016/272] doc: graduate matchLabelKeys in podTopologySpread to
 beta

Signed-off-by: Alex Wang <wangqingcan1990@gmail.com>
---
 .../scheduling-eviction/topology-spread-constraints.md     | 7 +++----
 .../command-line-tools-reference/feature-gates.md          | 3 ++-
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/content/en/docs/concepts/scheduling-eviction/topology-spread-constraints.md b/content/en/docs/concepts/scheduling-eviction/topology-spread-constraints.md
index 76855f5a5e5..6e47447100c 100644
--- a/content/en/docs/concepts/scheduling-eviction/topology-spread-constraints.md
+++ b/content/en/docs/concepts/scheduling-eviction/topology-spread-constraints.md
@@ -64,7 +64,7 @@ spec:
       topologyKey: <string>
       whenUnsatisfiable: <string>
       labelSelector: <object>
-      matchLabelKeys: <list> # optional; alpha since v1.25
+      matchLabelKeys: <list> # optional; beta since v1.27
       nodeAffinityPolicy: [Honor|Ignore] # optional; beta since v1.26
       nodeTaintsPolicy: [Honor|Ignore] # optional; beta since v1.26
   ### other Pod fields go here
@@ -144,9 +144,8 @@ your cluster. Those fields are:
   ```
 
   {{< note >}}
-  The `matchLabelKeys` field is an alpha field added in 1.25. You have to enable the
-  `MatchLabelKeysInPodTopologySpread` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
-  in order to use it.
+  The `matchLabelKeys` field is a beta-level field and enabled by default in 1.27. You can disable it by disabling the
+  `MatchLabelKeysInPodTopologySpread` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/).
   {{< /note >}}
 
 - **nodeAffinityPolicy** indicates how we will treat Pod's nodeAffinity/nodeSelector
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 3680548e7af..afac9234a7e 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 @@ For a reference to old feature gates that are removed, please refer to
 | `LogarithmicScaleDown` | `true` | Beta | 1.22 | |
 | `LoggingAlphaOptions` | `false` | Alpha | 1.24 | - |
 | `LoggingBetaOptions` | `true` | Beta | 1.24 | - |
-| `MatchLabelKeysInPodTopologySpread` | `false` | Alpha | 1.25 | |
+| `MatchLabelKeysInPodTopologySpread` | `false` | Alpha | 1.25 | 1.26 |
+| `MatchLabelKeysInPodTopologySpread` | `true` | Beta | 1.27 | - |
 | `MaxUnavailableStatefulSet` | `false` | Alpha | 1.24 | |
 | `MemoryManager` | `false` | Alpha | 1.21 | 1.21 |
 | `MemoryManager` | `true` | Beta | 1.22 | |

From 1cbca5cf369aa9db7376dbb5d97259e13d702af8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Arda=20G=C3=BC=C3=A7l=C3=BC?= <aguclu@redhat.com>
Date: Mon, 6 Mar 2023 08:21:57 +0300
Subject: [PATCH 017/272] document plugin resolution as subcommand for builtin
 commands

---
 content/en/docs/reference/kubectl/kubectl.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/content/en/docs/reference/kubectl/kubectl.md b/content/en/docs/reference/kubectl/kubectl.md
index 00314826750..aa92d9f9685 100644
--- a/content/en/docs/reference/kubectl/kubectl.md
+++ b/content/en/docs/reference/kubectl/kubectl.md
@@ -361,6 +361,14 @@ kubectl [flags]
 </td>
 </tr>
 
+<tr>
+<td colspan="2">KUBECTL_ENABLE_CMD_SHADOW</td>
+</tr>
+<tr>
+<td></td><td style="line-height: 130%; word-wrap: break-word;">When set to true, external plugins can be used as subcommands for builtin commands if subcommand does not exist. In alpha stage, this feature can only be used for create command(e.g. kubectl create networkpolicy). 
+</td>
+</tr>
+
 </tbody>
 </table>
 

From bb14c6db8d9cbfe8917ef9b98bbfbec47fa50d7b Mon Sep 17 00:00:00 2001
From: "m.nabokikh" <maksim.nabokikh@flant.com>
Date: Sun, 5 Mar 2023 22:28:04 +0100
Subject: [PATCH 018/272] Promote SelfSubjectReview to Beta

Signed-off-by: m.nabokikh <maksim.nabokikh@flant.com>
---
 .../reference/access-authn-authz/authentication.md | 14 +++++++-------
 .../command-line-tools-reference/feature-gates.md  |  3 ++-
 .../configure-access-multiple-clusters.md          |  2 +-
 3 files changed, 10 insertions(+), 9 deletions(-)

diff --git a/content/en/docs/reference/access-authn-authz/authentication.md b/content/en/docs/reference/access-authn-authz/authentication.md
index 6ab9ba3c75d..ed0c8ef5cfa 100644
--- a/content/en/docs/reference/access-authn-authz/authentication.md
+++ b/content/en/docs/reference/access-authn-authz/authentication.md
@@ -1221,7 +1221,7 @@ The following `ExecCredential` manifest describes a cluster information sample.
 
 ## API access to authentication information for a client {#self-subject-review}
 
-{{< feature-state for_k8s_version="v1.26" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
 
 If your cluster has the API enabled, you can use the `SelfSubjectReview` API to find out how your Kubernetes cluster maps your authentication
 information to identify you as a client. This works whether you are authenticating as a user (typically representing
@@ -1231,11 +1231,11 @@ a real person) or as a ServiceAccount.
 
 Request example (the body would be a `SelfSubjectReview`):
 ```
-POST /apis/authentication.k8s.io/v1alpha1/selfsubjectreviews
+POST /apis/authentication.k8s.io/v1beta1/selfsubjectreviews
 ```
 ```json
 {
-  "apiVersion": "authentication.k8s.io/v1alpha1",
+  "apiVersion": "authentication.k8s.io/v1beta1",
   "kind": "SelfSubjectReview"
 }
 ```
@@ -1243,7 +1243,7 @@ Response example:
 
 ```json
 {
-  "apiVersion": "authentication.k8s.io/v1alpha1",
+  "apiVersion": "authentication.k8s.io/v1beta1",
   "kind": "SelfSubjectReview",
   "status": {
     "userInfo": {
@@ -1262,7 +1262,7 @@ Response example:
 }
 ```
 
-For convenience, the `kubectl alpha auth whoami` command is present. Executing this command will produce the following output (yet different user attributes will be shown):
+For convenience, the `kubectl auth whoami` command is present. Executing this command will produce the following output (yet different user attributes will be shown):
 
 * Simple output example
     ```
@@ -1352,8 +1352,8 @@ By default, all authenticated users can create `SelfSubjectReview` objects when
 You can only make `SelfSubjectReview` requests if:
 * the `APISelfSubjectReview`
   [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
-  is enabled for your cluster
-* the API server for your cluster has the `authentication.k8s.io/v1alpha1`
+  is enabled for your cluster (enabled by default after reaching Beta)
+* the API server for your cluster has the `authentication.k8s.io/v1alpha1` or `authentication.k8s.io/v1beta1`
   {{< glossary_tooltip term_id="api-group" text="API group" >}}
   enabled.
 {{< /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 626cc6931f6..de505faa007 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
@@ -62,7 +62,8 @@ For a reference to old feature gates that are removed, please refer to
 | `APIPriorityAndFairness` | `true` | Beta | 1.20 | |
 | `APIResponseCompression` | `false` | Alpha | 1.7 | 1.15 |
 | `APIResponseCompression` | `true` | Beta | 1.16 | |
-| `APISelfSubjectReview` | `false` | Alpha | 1.26 | |
+| `APISelfSubjectReview` | `false` | Alpha | 1.26 | 1.26 |
+| `APISelfSubjectReview` | `true` | Beta | 1.27 | |
 | `APIServerIdentity` | `false` | Alpha | 1.20 | 1.25 |
 | `APIServerIdentity` | `true` | Beta | 1.26 | |
 | `APIServerTracing` | `false` | Alpha | 1.22 | |
diff --git a/content/en/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md b/content/en/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md
index 03dc6b4dc03..01f44c7fee8 100644
--- a/content/en/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md
+++ b/content/en/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md
@@ -404,7 +404,7 @@ It is not always obvious what attributes (username, groups) you will get after a
 It can be even more challenging if you are managing more than one cluster at the same time.
 
 There is a `kubectl` alpha subcommand command to check subject attributes, such as username,
-for your selected Kubernetes client context: `kubectl alpha auth whoami`.
+for your selected Kubernetes client context: `kubectl auth whoami`.
 
 Read [API access to authentication information for a client](/docs/reference/access-authn-authz/authentication/#self-subject-review)
 to learn about this in more detail.

From 112f01d2fca316db4b283e16b2577139b9337ed3 Mon Sep 17 00:00:00 2001
From: Peter Schuurman <psch@google.com>
Date: Mon, 6 Mar 2023 16:56:51 -0800
Subject: [PATCH 019/272] Update KEP-3335 documentation for beta in 1.27

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

diff --git a/content/en/docs/concepts/workloads/controllers/statefulset.md b/content/en/docs/concepts/workloads/controllers/statefulset.md
index cfa65e285ad..8023c1020f0 100644
--- a/content/en/docs/concepts/workloads/controllers/statefulset.md
+++ b/content/en/docs/concepts/workloads/controllers/statefulset.md
@@ -160,7 +160,7 @@ pods will be assigned ordinals from 0 up through N-1.
 
 ### Start ordinal
 
-{{< feature-state for_k8s_version="v1.26" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
 
 `.spec.ordinals` is an optional field that allows you to configure the integer
 ordinals assigned to each Pod. It defaults to nil. You must enable the
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 626cc6931f6..1844be19a62 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,7 +190,7 @@ For a reference to old feature gates that are removed, please refer to
 | `SizeMemoryBackedVolumes` | `false` | Alpha | 1.20 | 1.21 |
 | `SizeMemoryBackedVolumes` | `true` | Beta | 1.22 | |
 | `StatefulSetAutoDeletePVC` | `false` | Alpha | 1.22 | |
-| `StatefulSetStartOrdinal` | `false` | Alpha | 1.26 | |
+| `StatefulSetStartOrdinal` | `true` | Beta | 1.27 | |
 | `StorageVersionAPI` | `false` | Alpha | 1.20 | |
 | `StorageVersionHash` | `false` | Alpha | 1.14 | 1.14 |
 | `StorageVersionHash` | `true` | Beta | 1.15 | |

From 6f689fe306c62006a4e470330fc02433c5aa6eaa Mon Sep 17 00:00:00 2001
From: Peter Schuurman <psch@google.com>
Date: Fri, 10 Mar 2023 08:02:51 -0800
Subject: [PATCH 020/272] Add back 1.26 Alpha documentation for
 StatefulSetStartOrdinal feature gate

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

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 1844be19a62..5bda7723a89 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,6 +190,7 @@ For a reference to old feature gates that are removed, please refer to
 | `SizeMemoryBackedVolumes` | `false` | Alpha | 1.20 | 1.21 |
 | `SizeMemoryBackedVolumes` | `true` | Beta | 1.22 | |
 | `StatefulSetAutoDeletePVC` | `false` | Alpha | 1.22 | |
+| `StatefulSetStartOrdinal` | `false` | Alpha | 1.26 | 1.26 |
 | `StatefulSetStartOrdinal` | `true` | Beta | 1.27 | |
 | `StorageVersionAPI` | `false` | Alpha | 1.20 | |
 | `StorageVersionHash` | `false` | Alpha | 1.14 | 1.14 |

From 1054d0bcc78ac2fbcff15f6913a6685abd28c6c4 Mon Sep 17 00:00:00 2001
From: Nilekh Chaudhari <1626598+nilekhc@users.noreply.github.com>
Date: Thu, 9 Mar 2023 22:52:38 +0000
Subject: [PATCH 021/272] docs: updates EncryptionConfiguration doc to add
 wildcard support to encrypt all resources.

Signed-off-by: Nilekh Chaudhari <1626598+nilekhc@users.noreply.github.com>
---
 .../tasks/administer-cluster/encrypt-data.md  | 43 +++++++++++++++++++
 1 file changed, 43 insertions(+)

diff --git a/content/en/docs/tasks/administer-cluster/encrypt-data.md b/content/en/docs/tasks/administer-cluster/encrypt-data.md
index c683c5aa9b2..d34281b2283 100644
--- a/content/en/docs/tasks/administer-cluster/encrypt-data.md
+++ b/content/en/docs/tasks/administer-cluster/encrypt-data.md
@@ -19,6 +19,8 @@ This page shows how to enable and configure encryption of secret data at rest.
 
 * To encrypt a custom resource, your cluster must be running Kubernetes v1.26 or newer.
 
+* Use of wildcard for resource encryption is available from Kubernetes v1.27 or newer.
+
 
 <!-- steps -->
 
@@ -63,6 +65,24 @@ resources:
           keys:
             - name: key1
               secret: YWJjZGVmZ2hpamtsbW5vcHFyc3R1dnd4eXoxMjM0NTY=
+  - resources:
+      - events
+    providers:
+      - identity: {} # do not encrypt events even though  *.* is specified below
+  - resources:
+      - '*.apps'
+    providers:
+      - aescbc:
+          keys:
+          - name: key2
+            secret: c2VjcmV0IGlzIHNlY3VyZSwgb3IgaXMgaXQ/Cg==
+  - resources:
+      - '*.*'
+    providers:
+      - aescbc:
+          keys:
+          - name: key3
+            secret: c2VjcmV0IGlzIHNlY3VyZSwgSSB0aGluaw==
 ```
 
 Each `resources` array item is a separate config and contains a complete configuration. The
@@ -84,6 +104,29 @@ resources from storage, each provider that matches the stored data attempts in o
 data. If no provider can read the stored data due to a mismatch in format or secret key, an error
 is returned which prevents clients from accessing that resource.
 
+`EncryptionConfiguration` supports the use of wildcards to specify the resources that should be encrypted.
+Use '`*.<group>`' to encrypt all resources within a group (for eg '`*.apps`' in above example) or '`*.*`'
+to encrypt all resources. '`*.`' can be used to encrypt all resource in the core group. '`*.*`' will
+encrypt all resources, even custom resources that are added after API server start. 
+
+{{< note >}} Use of wildcards that overlap within the same resource list or across multiple entries are not allowed
+since part of the configuration would be ineffective. The `resources` list's processing order and precedence
+are determined by the order it's listed in the configuration. {{< /note >}}
+
+Opting out of encryption for specific resources while wildcard is enabled can be achieved by adding a new
+`resources` array item with the resource name, followed by the `providers` array item with the `identity` provider.
+For example, if '`*.*`' is enabled and you want to opt-out encryption for the `events` resource, add a new item
+to the `resources` array with `events` as the resource name, followed by the providers array item with `identity`.
+The new item should look like this:
+
+```yaml
+- resources:
+    - events
+  providers:
+    - identity: {}
+```
+Ensure that the new item is listed before the wildcard '`*.*`' item in the resources array to give it precedence.
+
 For more detailed information about the `EncryptionConfiguration` struct, please refer to the
 [encryption configuration API](/docs/reference/config-api/apiserver-encryption.v1/).
 

From e600a75b414e3932e3e0dda6aa12817590839100 Mon Sep 17 00:00:00 2001
From: Chris Henzie <chrishenzie@google.com>
Date: Tue, 7 Mar 2023 09:43:35 -0800
Subject: [PATCH 022/272] Update ReadWriteOncePod feature to beta

---
 content/en/docs/concepts/storage/persistent-volumes.md         | 3 ++-
 .../reference/command-line-tools-reference/feature-gates.md    | 3 ++-
 .../en/docs/tasks/configure-pod-container/security-context.md  | 3 +--
 3 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/content/en/docs/concepts/storage/persistent-volumes.md b/content/en/docs/concepts/storage/persistent-volumes.md
index 6df299674b4..ca68c365eef 100644
--- a/content/en/docs/concepts/storage/persistent-volumes.md
+++ b/content/en/docs/concepts/storage/persistent-volumes.md
@@ -637,7 +637,8 @@ The access modes are:
 : the volume can be mounted as read-write by many nodes.
 
  `ReadWriteOncePod`
-: the volume can be mounted as read-write by a single Pod. Use ReadWriteOncePod
+: {{< feature-state for_k8s_version="v1.27" state="beta" >}}
+  the volume can be mounted as read-write by a single Pod. Use ReadWriteOncePod
   access mode if you want to ensure that only one pod across whole cluster can
   read that PVC or write to it. This is only supported for CSI volumes and
   Kubernetes version 1.22+.
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 626cc6931f6..4ed52963f64 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
@@ -174,7 +174,8 @@ For a reference to old feature gates that are removed, please refer to
 | `ProxyTerminatingEndpoints` | `false` | Alpha | 1.22 | 1.25 |
 | `ProxyTerminatingEndpoints` | `true` | Beta | 1.26 | |
 | `QOSReserved` | `false` | Alpha | 1.11 | |
-| `ReadWriteOncePod` | `false` | Alpha | 1.22 | |
+| `ReadWriteOncePod` | `false` | Alpha | 1.22 | 1.26 |
+| `ReadWriteOncePod` | `true` | Beta | 1.27 | |
 | `RecoverVolumeExpansionFailure` | `false` | Alpha | 1.23 | |
 | `RemainingItemCount` | `false` | Alpha | 1.15 | 1.15 |
 | `RemainingItemCount` | `true` | Beta | 1.16 | |
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 756222eb426..0f5549c220b 100644
--- a/content/en/docs/tasks/configure-pod-container/security-context.md
+++ b/content/en/docs/tasks/configure-pod-container/security-context.md
@@ -449,8 +449,7 @@ SELinux label of a volume instantly by using a mount option
 
 To benefit from this speedup, all these conditions must be met:
 
-* Alpha feature gates `ReadWriteOncePod` and `SELinuxMountReadWriteOncePod` must
-  be enabled.
+* Alpha feature gate `SELinuxMountReadWriteOncePod` must be enabled.
 * Pod must use PersistentVolumeClaim with `accessModes: ["ReadWriteOncePod"]`.
 * Pod (or all its Containers that use the PersistentVolumeClaim) must
   have `seLinuxOptions` set.

From 993bae24c3dd634bf9f419e6751c81f4b5ce1629 Mon Sep 17 00:00:00 2001
From: ystkfujii <ystk.fujii0731@gmail.com>
Date: Thu, 16 Mar 2023 02:03:36 +0900
Subject: [PATCH 023/272] Drop turnkey cloud solutions for ja

---
 .../production-environment/turnkey/_index.md  |   4 -
 .../turnkey/alibaba-cloud.md                  |  17 --
 .../production-environment/turnkey/aws.md     |  82 -------
 .../production-environment/turnkey/azure.md   |  33 ---
 .../production-environment/turnkey/gce.md     | 217 ------------------
 .../production-environment/turnkey/icp.md     |  63 -----
 6 files changed, 416 deletions(-)
 delete mode 100644 content/ja/docs/setup/production-environment/turnkey/_index.md
 delete mode 100644 content/ja/docs/setup/production-environment/turnkey/alibaba-cloud.md
 delete mode 100644 content/ja/docs/setup/production-environment/turnkey/aws.md
 delete mode 100644 content/ja/docs/setup/production-environment/turnkey/azure.md
 delete mode 100644 content/ja/docs/setup/production-environment/turnkey/gce.md
 delete mode 100644 content/ja/docs/setup/production-environment/turnkey/icp.md

diff --git a/content/ja/docs/setup/production-environment/turnkey/_index.md b/content/ja/docs/setup/production-environment/turnkey/_index.md
deleted file mode 100644
index 6b9dabb7ab6..00000000000
--- a/content/ja/docs/setup/production-environment/turnkey/_index.md
+++ /dev/null
@@ -1,4 +0,0 @@
----
-title: ターンキークラウドソリューション
-weight: 30
----
diff --git a/content/ja/docs/setup/production-environment/turnkey/alibaba-cloud.md b/content/ja/docs/setup/production-environment/turnkey/alibaba-cloud.md
deleted file mode 100644
index 4506e9cba0b..00000000000
--- a/content/ja/docs/setup/production-environment/turnkey/alibaba-cloud.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: Alibaba CloudでKubernetesを動かす
----
-
-## Alibaba Cloud Container Service
-
-[Alibaba Cloud Container Service](https://www.alibabacloud.com/product/container-service)はAlibaba Cloud ECSインスタンスのクラスター上もしくはサーバーレスの形態でDockerアプリケーションを起動して管理します。著名なオープンソースのコンテナオーケストレーターであるDocker SwarmおよびKubernetesをサポートしています。
-
-クラスターの構築と管理を簡素化するために、[Alibaba Cloud Container ServiceのためのKubernetesサポート](https://www.alibabacloud.com/product/kubernetes)を使用します。[Kubernetes walk-through](https://www.alibabacloud.com/help/doc-detail/86737.htm)に従ってすぐに始めることができ、中国語の[Alibaba CloudにおけるKubernetesサポートのためのチュートリアル](https://yq.aliyun.com/teams/11/type_blog-cid_200-page_1)もあります。
-
-カスタムバイナリもしくはオープンソースKubernetesを使用する場合は、以下の手順に従って下さい。
-
-## 構築のカスタム
-
-[Alibaba Cloudプロバイダーが実装されたKubernetesのソースコード](https://github.com/AliyunContainerService/kubernetes)はオープンソースであり、GitHubから入手可能です。
-
-さらなる情報は英語の[Kubernetesのクイックデプロイメント - Alibaba CloudのVPC環境](https://www.alibabacloud.com/forum/read-830)をご覧下さい。
diff --git a/content/ja/docs/setup/production-environment/turnkey/aws.md b/content/ja/docs/setup/production-environment/turnkey/aws.md
deleted file mode 100644
index f7ec4bd0123..00000000000
--- a/content/ja/docs/setup/production-environment/turnkey/aws.md
+++ /dev/null
@@ -1,82 +0,0 @@
----
-title: AWS EC2上でKubernetesを動かす
-content_type: task
----
-
-<!-- overview -->
-
-このページでは、AWS上でKubernetesクラスターをインストールする方法について説明します。
-
-
-
-## {{% heading "prerequisites" %}}
-
-
-AWS上でKubernetesクラスターを作成するには、AWSからアクセスキーIDおよびシークレットアクセスキーを入手する必要があります。
-
-### サポートされているプロダクショングレードのツール
-
-* [conjure-up](https://docs.conjure-up.io/stable/en/cni/k8s-and-aws)はUbuntu上でネイティブなAWSインテグレーションを用いてKubernetesクラスターを作成するオープンソースのインストーラーです。
-
-* [Kubernetes Operations](https://github.com/kubernetes/kops) - プロダクショングレードなKubernetesのインストール、アップグレード、管理が可能です。AWS上のDebian、Ubuntu、CentOS、RHELをサポートしています。
-
-* [kube-aws](https://github.com/kubernetes-incubator/kube-aws) EC2、CloudFormation、Auto Scalingを使用して、[Flatcar Linux](https://www.flatcar-linux.org/)ノードでKubernetesクラスターを作成および管理します。
-
-* [KubeOne](https://github.com/kubermatic/kubeone)は可用性の高いKubernetesクラスターを作成、アップグレード、管理するための、オープンソースのライフサイクル管理ツールです。
-
-
-
-<!-- steps -->
-
-## クラスターの始まり
-
-### コマンドライン管理ツール: kubectl
-
-クラスターの起動スクリプトによってワークステーション上に`kubernetes`ディレクトリが作成されます。もしくは、Kubernetesの最新リリースを[こちら](https://github.com/kubernetes/kubernetes/releases)からダウンロードすることも可能です。
-
-次に、kubectlにアクセスするために適切なバイナリフォルダーを`PATH`へ追加します:
-
-```shell
-# macOS
-export PATH=<path/to/kubernetes-directory>/platforms/darwin/amd64:$PATH
-
-# Linux
-export PATH=<path/to/kubernetes-directory>/platforms/linux/amd64:$PATH
-```
-
-ツールに関する最新のドキュメントページはこちらです: [kubectl manual](/docs/reference/kubectl/kubectl/)
-
-デフォルトでは、`kubectl`はクラスターの起動中に生成された`kubeconfig`ファイルをAPIに対する認証に使用します。
-詳細な情報は、[kubeconfig files](/ja/docs/tasks/access-application-cluster/configure-access-multiple-clusters/)を参照してください。
-
-### 例
-
-新しいクラスターを試すには、[簡単なnginxの例](/ja/docs/tasks/run-application/run-stateless-application-deployment/)を参照してください。
-
-"Guestbook"アプリケーションは、Kubernetesを始めるもう一つのポピュラーな例です: [guestbookの例](https://github.com/kubernetes/examples/tree/master/guestbook/)
-
-より完全なアプリケーションについては、[examplesディレクトリ](https://github.com/kubernetes/examples/tree/master/)を参照してください。
-
-## クラスターのスケーリング
-
-`kubectl`を使用したノードの追加および削除はサポートしていません。インストール中に作成された[Auto Scaling Group](https://docs.aws.amazon.com/autoscaling/latest/userguide/as-manual-scaling.html)内の'Desired'および'Max'プロパティを手動で調整することで、ノード数をスケールさせることができます。
-
-## クラスターの解体
-
-クラスターのプロビジョニングに使用した環境変数がexportされていることを確認してから、`kubernetes`ディレクトリ内で以下のスクリプトを実行してください:
-
-```shell
-cluster/kube-down.sh
-```
-
-## サポートレベル
-
-
-IaaS プロバイダー    | 構成管理     | OS            | ネットワーク  | ドキュメント                                  | 適合     | サポートレベル
--------------------- | ------------ | ------------- | ------------  | --------------------------------------------- | ---------| ----------------------------
-AWS                  | kops         | Debian        | k8s (VPC)     | [docs](https://github.com/kubernetes/kops)    |          | Community ([@justinsb](https://github.com/justinsb))
-AWS                  | CoreOS       | CoreOS        | flannel     | -  |          | Community
-AWS                  | Juju         | Ubuntu        | flannel, calico, canal     | - | 100%     | Commercial, Community
-AWS                  | KubeOne         | Ubuntu, CoreOS, CentOS   | canal, weavenet     | [docs](https://github.com/kubermatic/kubeone)      | 100%    | Commercial, Community
-
-
diff --git a/content/ja/docs/setup/production-environment/turnkey/azure.md b/content/ja/docs/setup/production-environment/turnkey/azure.md
deleted file mode 100644
index dcf4a4ffb00..00000000000
--- a/content/ja/docs/setup/production-environment/turnkey/azure.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: Azure 上で Kubernetes を動かす
----
-
-## Azure Kubernetes Service (AKS)
-
-[Azure Kubernetes Service](https://azure.microsoft.com/ja-jp/services/kubernetes-service/)は、Kubernetesクラスターのためのシンプルなデプロイ機能を提供します。
-
-Azure Kubernetes Serviceを利用してAzure上にKubernetesクラスターをデプロイする例:
-
-**[Microsoft Azure Kubernetes Service](https://docs.microsoft.com/ja-jp/azure/aks/intro-kubernetes)**
-
-## デプロイのカスタマイズ: AKS-Engine
-
-Azure Kubernetes Serviceのコア部分は**オープンソース**であり、コミュニティのためにGitHub上で公開され、利用およびコントリビュートすることができます: **[AKS-Engine](https://github.com/Azure/aks-engine)**。レガシーな [ACS-Engine](https://github.com/Azure/acs-engine) のコードベースはAKS-engineのために廃止となりました。
-
-AKS-Engineは、Azure Kubernetes Serviceが公式にサポートしている機能を超えてデプロイをカスタマイズしたい場合に適した選択肢です。
-既存の仮想ネットワークへのデプロイや、複数のagent poolを利用するなどのカスタマイズをすることができます。
-コミュニティによるAKS-Engineへのコントリビュートが、Azure Kubernetes Serviceに組み込まれる場合もあります。
-
-AKS-Engineへの入力は、Kubernetesクラスターを記述するapimodelのJSONファイルです。これはAzure Kubernetes Serviceを使用してクラスターを直接デプロイするために使用されるAzure Resource Manager (ARM) のテンプレート構文と似ています。
-処理結果はARMテンプレートとして出力され、ソース管理に組み込んだり、AzureにKubernetesクラスターをデプロイするために使うことができます。
-
-**[AKS-Engine Kubernetes Tutorial](https://github.com/Azure/aks-engine/blob/master/docs/tutorials/README.md)** を参照して始めることができます。
-
-## Azure上でCoreOS Tectonicを動かす
-
-Azureで利用できるCoreOS Tectonic Installerは**オープンソース**であり、コミュニティのためにGitHub上で公開され、利用およびコントリビュートすることができます: **[Tectonic Installer](https://github.com/coreos/tectonic-installer)**.
-
-Tectonic Installerは、 [Hashicorp が提供する Terraform](https://www.terraform.io/docs/providers/azurerm/)のAzure Resource Manager(ARM)プロバイダーを用いてクラスターをカスタマイズしたい場合に適した選択肢です。
-これを利用することにより、Terraformと親和性の高いツールを使用してカスタマイズしたり連携したりすることができます。
-
-[Tectonic Installer for Azure Guide](https://coreos.com/tectonic/docs/latest/install/azure/azure-terraform.html)を参照して、すぐに始めることができます。
diff --git a/content/ja/docs/setup/production-environment/turnkey/gce.md b/content/ja/docs/setup/production-environment/turnkey/gce.md
deleted file mode 100644
index 39e03efc941..00000000000
--- a/content/ja/docs/setup/production-environment/turnkey/gce.md
+++ /dev/null
@@ -1,217 +0,0 @@
----
-title: Google Compute Engine上でKubernetesを動かす
-content_type: task
----
-
-<!-- overview -->
-
-The example below creates a Kubernetes cluster with 3 worker node Virtual Machines and a master Virtual Machine (i.e. 4 VMs in your cluster). This cluster is set up and controlled from your workstation (or wherever you find convenient).
-
-
-
-## {{% heading "prerequisites" %}}
-
-
-If you want a simplified getting started experience and GUI for managing clusters, please consider trying [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine/) for hosted cluster installation and management.
-
-For an easy way to experiment with the Kubernetes development environment, click the button below
-to open a Google Cloud Shell with an auto-cloned copy of the Kubernetes source repo.
-
-[![Open in Cloud Shell](https://gstatic.com/cloudssh/images/open-btn.png)](https://console.cloud.google.com/cloudshell/open?git_repo=https://github.com/kubernetes/kubernetes&page=editor&open_in_editor=README.md)
-
-If you want to use custom binaries or pure open source Kubernetes, please continue with the instructions below.
-
-### 前提条件
-
-1. You need a Google Cloud Platform account with billing enabled. Visit the [Google Developers Console](https://console.cloud.google.com) for more details.
-1. Install `gcloud` as necessary. `gcloud` can be installed as a part of the [Google Cloud SDK](https://cloud.google.com/sdk/).
-1. Enable the [Compute Engine Instance Group Manager API](https://console.developers.google.com/apis/api/replicapool.googleapis.com/overview) in the [Google Cloud developers console](https://console.developers.google.com/apis/library).
-1. Make sure that gcloud is set to use the Google Cloud Platform project you want. You can check the current project using `gcloud config list project` and change it via `gcloud config set project <project-id>`.
-1. Make sure you have credentials for GCloud by running `gcloud auth login`.
-1. (Optional)  In order to make API calls against GCE, you must also run `gcloud auth application-default login`.
-1. Make sure you can start up a GCE VM from the command line.  At least make sure you can do the [Create an instance](https://cloud.google.com/compute/docs/instances/#startinstancegcloud) part of the GCE Quickstart.
-1. Make sure you can SSH into the VM without interactive prompts.  See the [Log in to the instance](https://cloud.google.com/compute/docs/instances/#sshing) part of the GCE Quickstart.
-
-
-
-<!-- steps -->
-
-## クラスターの起動
-
-You can install a client and start a cluster with either one of these commands (we list both in case only one is installed on your machine):
-
-
-```shell
-curl -sS https://get.k8s.io | bash
-```
-
-or
-
-```shell
-wget -q -O - https://get.k8s.io | bash
-```
-
-Once this command completes, you will have a master VM and four worker VMs, running as a Kubernetes cluster.
-
-By default, some containers will already be running on your cluster. Containers like `fluentd` provide [logging](/docs/concepts/cluster-administration/logging/), while `heapster` provides [monitoring](https://releases.k8s.io/master/cluster/addons/cluster-monitoring/README.md) services.
-
-The script run by the commands above creates a cluster with the name/prefix "kubernetes". It defines one specific cluster config, so you can't run it more than once.
-
-Alternately, you can download and install the latest Kubernetes release from [this page](https://github.com/kubernetes/kubernetes/releases), then run the `<kubernetes>/cluster/kube-up.sh` script to start the cluster:
-
-```shell
-cd kubernetes
-cluster/kube-up.sh
-```
-
-If you want more than one cluster running in your project, want to use a different name, or want a different number of worker nodes, see the `<kubernetes>/cluster/gce/config-default.sh` file for more fine-grained configuration before you start up your cluster.
-
-If you run into trouble, please see the section on [troubleshooting](/ja/docs/setup/production-environment/turnkey/gce/#troubleshooting), post to the
-[Kubernetes Forum](https://discuss.kubernetes.io), or come ask questions on `#gke` Slack channel.
-
-The next few steps will show you:
-
-1. How to set up the command line client on your workstation to manage the cluster
-1. Examples of how to use the cluster
-1. How to delete the cluster
-1. How to start clusters with non-default options (like larger clusters)
-
-## ワークステーション上でのKubernetesコマンドラインツールのインストール
-
-The cluster startup script will leave you with a running cluster and a `kubernetes` directory on your workstation.
-
-The [kubectl](/docs/reference/kubectl/kubectl/) tool controls the Kubernetes cluster
-manager.  It lets you inspect your cluster resources, create, delete, and update
-components, and much more. You will use it to look at your new cluster and bring
-up example apps.
-
-You can use `gcloud` to install the `kubectl` command-line tool on your workstation:
-
-```shell
-gcloud components install kubectl
-```
-
-{{< note >}}
-The kubectl version bundled with `gcloud` may be older than the one
-The [kubectl](/ja/docs/reference/kubectl/kubectl/) tool controls the Kubernetes cluster
-document to see how you can set up the latest `kubectl` on your workstation.
-{{< /note >}}
-
-## クラスターの始まり
-
-### クラスターの様子を見る
-
-Once `kubectl` is in your path, you can use it to look at your cluster. E.g., running:
-
-```shell
-kubectl get --all-namespaces services
-```
-
-should show a set of [services](/docs/concepts/services-networking/service/) that look something like this:
-
-```shell
-NAMESPACE     NAME          TYPE             CLUSTER_IP       EXTERNAL_IP       PORT(S)        AGE
-default       kubernetes    ClusterIP        10.0.0.1         <none>            443/TCP        1d
-kube-system   kube-dns      ClusterIP        10.0.0.2         <none>            53/TCP,53/UDP  1d
-kube-system   kube-ui       ClusterIP        10.0.0.3         <none>            80/TCP         1d
-...
-```
-
-Similarly, you can take a look at the set of [pods](/ja/docs/concepts/workloads/pods/) that were created during cluster startup.
-You can do this via the
-
-```shell
-kubectl get --all-namespaces pods
-```
-
-command.
-
-You'll see a list of pods that looks something like this (the name specifics will be different):
-
-```shell
-NAMESPACE     NAME                                           READY     STATUS    RESTARTS   AGE
-kube-system   coredns-5f4fbb68df-mc8z8                       1/1       Running   0          15m
-kube-system   fluentd-cloud-logging-kubernetes-minion-63uo   1/1       Running   0          14m
-kube-system   fluentd-cloud-logging-kubernetes-minion-c1n9   1/1       Running   0          14m
-kube-system   fluentd-cloud-logging-kubernetes-minion-c4og   1/1       Running   0          14m
-kube-system   fluentd-cloud-logging-kubernetes-minion-ngua   1/1       Running   0          14m
-kube-system   kube-ui-v1-curt1                               1/1       Running   0          15m
-kube-system   monitoring-heapster-v5-ex4u3                   1/1       Running   1          15m
-kube-system   monitoring-influx-grafana-v1-piled             2/2       Running   0          15m
-```
-
-Some of the pods may take a few seconds to start up (during this time they'll show `Pending`), but check that they all show as `Running` after a short period.
-
-### いくつかの例の実行
-
-Then, see [a simple nginx example](/ja/docs/tasks/run-application/run-stateless-application-deployment/) to try out your new cluster.
-
-For more complete applications, please look in the [examples directory](https://github.com/kubernetes/examples/tree/master/).  The [guestbook example](https://github.com/kubernetes/examples/tree/master/guestbook/) is a good "getting started" walkthrough.
-
-## クラスターの解体
-
-To remove/delete/teardown the cluster, use the `kube-down.sh` script.
-
-```shell
-cd kubernetes
-cluster/kube-down.sh
-```
-
-Likewise, the `kube-up.sh` in the same directory will bring it back up. You do not need to rerun the `curl` or `wget` command: everything needed to setup the Kubernetes cluster is now on your workstation.
-
-## カスタマイズ
-
-The script above relies on Google Storage to stage the Kubernetes release. It
-then will start (by default) a single master VM along with 3 worker VMs.  You
-can tweak some of these parameters by editing `kubernetes/cluster/gce/config-default.sh`
-You can view a transcript of a successful cluster creation
-[here](https://gist.github.com/satnam6502/fc689d1b46db9772adea).
-
-## トラブルシューティング
-
-### プロジェクトの設定
-
-You need to have the Google Cloud Storage API, and the Google Cloud Storage
-JSON API enabled. It is activated by default for new projects. Otherwise, it
-can be done in the Google Cloud Console.  See the [Google Cloud Storage JSON
-API Overview](https://cloud.google.com/storage/docs/json_api/) for more
-details.
-
-Also ensure that-- as listed in the [Prerequisites section](#前提条件)-- you've enabled the `Compute Engine Instance Group Manager API`, and can start up a GCE VM from the command line as in the [GCE Quickstart](https://cloud.google.com/compute/docs/quickstart) instructions.
-
-### クラスター初期化のハング
-
-If the Kubernetes startup script hangs waiting for the API to be reachable, you can troubleshoot by SSHing into the master and node VMs and looking at logs such as `/var/log/startupscript.log`.
-
-**Once you fix the issue, you should run `kube-down.sh` to cleanup** after the partial cluster creation, before running `kube-up.sh` to try again.
-
-### SSH
-
-If you're having trouble SSHing into your instances, ensure the GCE firewall
-isn't blocking port 22 to your VMs.  By default, this should work but if you
-have edited firewall rules or created a new non-default network, you'll need to
-expose it: `gcloud compute firewall-rules create default-ssh --network=<network-name>
---description "SSH allowed from anywhere" --allow tcp:22`
-
-Additionally, your GCE SSH key must either have no passcode or you need to be
-using `ssh-agent`.
-
-### ネットワーク
-
-The instances must be able to connect to each other using their private IP. The
-script uses the "default" network which should have a firewall rule called
-"default-allow-internal" which allows traffic on any port on the private IPs.
-If this rule is missing from the default network or if you change the network
-being used in `cluster/config-default.sh` create a new rule with the following
-field values:
-
-* Source Ranges: `10.0.0.0/8`
-* Allowed Protocols and Port: `tcp:1-65535;udp:1-65535;icmp`
-
-## サポートレベル
-
-
-IaaS Provider        | Config. Mgmt | OS     | Networking  | Docs                                              | Conforms | Support Level
--------------------- | ------------ | ------ | ----------  | ---------------------------------------------     | ---------| ----------------------------
-GCE                  | Saltstack    | Debian | GCE         | [docs](/ja/docs/setup/production-environment/turnkey/gce/)                                    |   | Project
-
diff --git a/content/ja/docs/setup/production-environment/turnkey/icp.md b/content/ja/docs/setup/production-environment/turnkey/icp.md
deleted file mode 100644
index 1313f37ff0c..00000000000
--- a/content/ja/docs/setup/production-environment/turnkey/icp.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: IBM Cloud Privateを使ってマルチクラウドでKubernetesを動かす
----
-
-IBM® Cloud Private is a turnkey cloud solution and an on-premises turnkey cloud solution. IBM Cloud Private delivers pure upstream Kubernetes with the typical management components that are required to run real enterprise workloads. These workloads include health management, log management, audit trails, and metering for tracking usage of workloads on the platform.
-
-IBM Cloud Private is available in a community edition and a fully supported enterprise edition. The community edition is available at no charge from [Docker Hub](https://hub.docker.com/r/ibmcom/icp-inception/). The enterprise edition supports high availability topologies and includes commercial support from IBM for Kubernetes and the IBM Cloud Private management platform. If you want to try IBM Cloud Private, you can use either the hosted trial, the tutorial, or the self-guided demo. You can also try the free community edition. For details, see [Get started with IBM Cloud Private](https://www.ibm.com/cloud/private/get-started).
-
-For more information, explore the following resources:
-
-* [IBM Cloud Private](https://www.ibm.com/cloud/private)
-* [Reference architecture for IBM Cloud Private](https://github.com/ibm-cloud-architecture/refarch-privatecloud)
-* [IBM Cloud Private documentation](https://www.ibm.com/support/knowledgecenter/SSBS6K/product_welcome_cloud_private.html)
-
-## IBM Cloud PrivateとTerraform
-
-The following modules are available where you can deploy IBM Cloud Private by using Terraform:
-
-* AWS: [Deploy IBM Cloud Private to AWS](https://github.com/ibm-cloud-architecture/terraform-icp-aws)
-* Azure: [Deploy IBM Cloud Private to Azure](https://github.com/ibm-cloud-architecture/terraform-icp-azure)
-* IBM Cloud: [Deploy IBM Cloud Private cluster to IBM Cloud](https://github.com/ibm-cloud-architecture/terraform-icp-ibmcloud)
-* OpenStack: [Deploy IBM Cloud Private to OpenStack](https://github.com/ibm-cloud-architecture/terraform-icp-openstack)
-* Terraform module: [Deploy IBM Cloud Private on any supported infrastructure vendor](https://github.com/ibm-cloud-architecture/terraform-module-icp-deploy)
-* VMware: [Deploy IBM Cloud Private to VMware](https://github.com/ibm-cloud-architecture/terraform-icp-vmware)
-
-## AWS上でのIBM Cloud Private
-
-You can deploy an IBM Cloud Private cluster on Amazon Web Services (AWS) using Terraform.
-
-IBM Cloud Private can also run on the AWS cloud platform by using Terraform. To deploy IBM Cloud Private in an AWS EC2 environment, see [Installing IBM Cloud Private on AWS](https://github.com/ibm-cloud-architecture/terraform-icp-aws).
-
-## Azure上でのIBM Cloud Private
-
-You can enable Microsoft Azure as a cloud provider for IBM Cloud Private deployment and take advantage of all the IBM Cloud Private features on the Azure public cloud. For more information, see [IBM Cloud Private on Azure](https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/supported_environments/azure_overview.html).
-
-## Red Hat OpenShiftを用いたIBM Cloud Private
-
-You can deploy IBM certified software containers that are running on IBM Cloud Private onto Red Hat OpenShift.
-
-Integration capabilities:
-
-* Supports Linux® 64-bit platform in offline-only installation mode
-* Single-master configuration
-* Integrated IBM Cloud Private cluster management console and catalog
-* Integrated core platform services, such as monitoring, metering, and logging
-* IBM Cloud Private uses the OpenShift image registry
-
-For more information see, [IBM Cloud Private on OpenShift](https://www.ibm.com/support/knowledgecenter/SSBS6K_3.2.0/supported_environments/openshift/overview.html).
-
-## VirtualBox上でのIBM Cloud Private
-
-To install IBM Cloud Private to a VirtualBox environment, see [Installing IBM Cloud Private on VirtualBox](https://github.com/ibm-cloud-architecture/refarch-privatecloud-virtualbox).
-
-## VMware上でのIBM Cloud Private
-
-You can install IBM Cloud Private on VMware with either Ubuntu or RHEL images. For details, see the following projects:
-
-* [Installing IBM Cloud Private with Ubuntu](https://github.com/ibm-cloud-architecture/refarch-privatecloud/blob/master/Installing_ICp_on_prem_ubuntu.md)
-* [Installing IBM Cloud Private with Red Hat Enterprise](https://github.com/ibm-cloud-architecture/refarch-privatecloud/tree/master/icp-on-rhel)
-
-The IBM Cloud Private Hosted service automatically deploys IBM Cloud Private Hosted on your VMware vCenter Server instances. This service brings the power of microservices and containers to your VMware environment on IBM Cloud. With this service, you can extend the same familiar VMware and IBM Cloud Private operational model and tools from on-premises into the IBM Cloud.
-
-For more information, see [IBM Cloud Private Hosted service](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-icp_overview).

From efa8181fde21353fa0ac6e1c04d49b55def2244c Mon Sep 17 00:00:00 2001
From: Harshal Patil <harpatil@redhat.com>
Date: Tue, 14 Mar 2023 11:15:45 -0400
Subject: [PATCH 024/272] Graduate Evented PLEG to Beta

Signed-off-by: Harshal Patil <harpatil@redhat.com>
Co-authored-by:  Tim Bannister <sftim@users.noreply.github.com>
---
 .../feature-gates.md                          |  3 +-
 .../switch-to-evented-pleg.md                 | 91 +++++++++++++++++++
 2 files changed, 93 insertions(+), 1 deletion(-)
 create mode 100644 content/en/docs/tasks/administer-cluster/switch-to-evented-pleg.md

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 626cc6931f6..bd28ebde4df 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
@@ -94,7 +94,8 @@ For a reference to old feature gates that are removed, please refer to
 | `DownwardAPIHugePages` | `false` | Beta | 1.21 | 1.21 |
 | `DownwardAPIHugePages` | `true` | Beta | 1.22 | |
 | `DynamicResourceAllocation` | `false` | Alpha | 1.26 | |
-| `EventedPLEG` | `false` | Alpha | 1.26 | - |
+| `EventedPLEG` | `false` | Alpha | 1.26 | 1.26 |
+| `EventedPLEG` | `false` | Beta | 1.27 | - |
 | `ExpandedDNSConfig` | `false` | Alpha | 1.22 | 1.25 |
 | `ExpandedDNSConfig` | `true` | Beta | 1.26 | |
 | `ExperimentalHostUserNamespaceDefaulting` | `false` | Beta | 1.5 | |
diff --git a/content/en/docs/tasks/administer-cluster/switch-to-evented-pleg.md b/content/en/docs/tasks/administer-cluster/switch-to-evented-pleg.md
new file mode 100644
index 00000000000..8fdb491c28a
--- /dev/null
+++ b/content/en/docs/tasks/administer-cluster/switch-to-evented-pleg.md
@@ -0,0 +1,91 @@
+---
+title: Switching From Polling to CRI Event-based Updates to Container Status
+min-kubernetes-server-version: 1.26
+content_type: task
+weight: 90
+---
+
+{{< feature-state for_k8s_version="v1.26" state="beta" >}}
+
+<!-- overview -->
+This page shows how to migrate notes to use event based updates for container status. The event-based
+implementation reduces node resource consumption by the kubelet, compared to the legacy approach
+that relies on polling.
+You may know this feature as _evented Pod lifecycle event generator (PLEG)_. That's the name used
+internally within the Kubernetes project for a key implementation detail.
+
+
+## {{% heading "prerequisites" %}}
+
+* You need to run a version of Kubernetes that provides this feature.
+Kubernetes {{< skew currentVersion >}} includes beta support for event-based container
+status updates. The feature is beta and is disabled by default. 
+{{< version-check >}}
+If you are running a different version of Kubernetes, check the documentation for that release.
+
+
+<!-- steps -->
+
+## Why switch to Evented PLEG?
+
+* The current `Generic PLEG` incurs non-negligible overhead due to frequent polling of container statuses.
+* This overhead is exacerbated by Kubelet's parallelism, limiting its scalability and causing poor performance and reliability problems.
+* The goal of `Evented PLEG` is to reduce unnecessary work during inactivity by replacing periodic polling.
+
+## Switching to Evented PLEG
+
+
+1. Start the Kubelet with the [feature gate](https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/) `EventedPLEG` enabled. In Kubelet feature gates can be enabled by editing [config file](https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/) and restarting the Kubelet service.
+
+2. Please make sure the node is [drained](https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/) before proceeding. 
+
+3. Start the `CRI Runtime` with the `Evented PLEG` support. 
+      {{< tabs name="tab_with_code" >}}
+      {{< tab name="Containerd" codelang="bash" >}}
+      Version 1.7+
+      {{< /tab >}}
+      {{< tab name="CRI-O" codelang="bash" >}}
+      Version 1.26+
+      
+      Check if the CRI-O is already configured to emit `CRI Events` by verifying the configuration, 
+      ```
+      $ crio config | grep enable_pod_events
+      ```
+      If its enabled it should show, 
+      ```
+      # enable_pod_events = true
+      ```
+
+      To enable it, start the cri-o daemon with the flag `--enable-pod-events=true` or using a drop in config like,
+            
+      [crio.runtime]
+      enable_pod_events: true
+      
+
+      {{< /tab >}}
+      {{< /tabs >}}
+
+
+{{< version-check >}}
+
+4. Verify that `Evented PLEG` is in use by looking for the term `EventedPLEG` in the kubelet logs
+
+      The output is similar to this:
+      ```
+      I0314 11:10:13.909915 1105457 feature_gate.go:249] feature gates: &{map[EventedPLEG:true]}
+      ```
+
+      If you have set LOG_LEVEL to 4 and above, you might see more entries that indicate `Evented PLEG` is in use by the kubelet.
+      
+      ```
+      I0314 11:12:42.009542 1110177 evented.go:238] "Evented PLEG: Generated pod status from the received event" podUID=3b2c6172-b112-447a-ba96-94e7022912dc
+      I0314 11:12:44.623326 1110177 evented.go:238] "Evented PLEG: Generated pod status from the received event" podUID=b3fba5ea-a8c5-4b76-8f43-481e17e8ec40
+      I0314 11:12:44.714564 1110177 evented.go:238] "Evented PLEG: Generated pod status from the received event" podUID=b3fba5ea-a8c5-4b76-8f43-481e17e8ec40
+      ```
+
+## {{% heading "whatsnext" %}}
+
+* Learn more about [KEP 3386](https://github.com/kubernetes/enhancements/blob/5b258a990adabc2ffdc9d84581ea6ed696f7ce6c/keps/sig-node/3386-kubelet-evented-pleg/README.md).
+
+
+

From 5beb348e62422da89c3270aa21de7c5059d33411 Mon Sep 17 00:00:00 2001
From: Patrick Ohly <patrick.ohly@intel.com>
Date: Fri, 17 Mar 2023 11:56:25 +0100
Subject: [PATCH 025/272] dynamic resource allocation: update for 1.27

The API group was bumped to make some incompatible internal changes and the
user-visible renaming of PodScheduling to PodSchedulingContext.
---
 .../dynamic-resource-allocation.md              | 17 +++++++++--------
 1 file changed, 9 insertions(+), 8 deletions(-)

diff --git a/content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md b/content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md
index e1c468f58f0..5a6779a8747 100644
--- a/content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md
+++ b/content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md
@@ -9,7 +9,7 @@ weight: 65
 
 <!-- overview -->
 
-{{< feature-state for_k8s_version="v1.26" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.27" state="alpha" >}}
 
 Dynamic resource allocation is a new API for requesting and sharing resources
 between pods and containers inside a pod. It is a generalization of the
@@ -31,7 +31,7 @@ check the documentation for that version of Kubernetes.
 
 ## API
 
-The new `resource.k8s.io/v1alpha1` {{< glossary_tooltip text="API group"
+The `resource.k8s.io/v1alpha2` {{< glossary_tooltip text="API group"
 term_id="api-group" >}} provides four new types:
 
 ResourceClass
@@ -51,7 +51,7 @@ ResourceClaimTemplate
 : Defines the spec and some meta data for creating
   ResourceClaims. Created by a user when deploying a workload.
 
-PodScheduling
+PodSchedulingContext
 : Used internally by the control plane and resource drivers
   to coordinate pod scheduling when ResourceClaims need to be allocated
   for a Pod.
@@ -76,7 +76,7 @@ Here is an example for a fictional resource driver. Two ResourceClaim objects
 will get created for this Pod and each container gets access to one of them.
 
 ```yaml
-apiVersion: resource.k8s.io/v1alpha1
+apiVersion: resource.k8s.io/v1alpha2
 kind: ResourceClass
 name: resource.example.com
 driverName: resource-driver.example.com
@@ -88,7 +88,7 @@ spec:
   color: black
   size: large
 ---
-apiVersion: resource.k8s.io/v1alpha1
+apiVersion: resource.k8s.io/v1alpha2
 kind: ResourceClaimTemplate
 metadata:
   name: large-black-cat-claim-template
@@ -176,7 +176,7 @@ future.
 Dynamic resource allocation is an *alpha feature* and only enabled when the
 `DynamicResourceAllocation` [feature
 gate](/docs/reference/command-line-tools-reference/feature-gates/) and the
-`resource.k8s.io/v1alpha1` {{< glossary_tooltip text="API group"
+`resource.k8s.io/v1alpha2` {{< glossary_tooltip text="API group"
 term_id="api-group" >}} are enabled. For details on that, see the
 `--feature-gates` and `--runtime-config` [kube-apiserver
 parameters](/docs/reference/command-line-tools-reference/kube-apiserver/).
@@ -203,8 +203,9 @@ error: the server doesn't have a resource type "resourceclasses"
 ```
 
 The default configuration of kube-scheduler enables the "DynamicResources"
-plugin if and only if the feature gate is enabled. Custom configurations may
-have to be modified to include it.
+plugin if and only if the feature gate is enabled and when using
+the v1 configuration API. Custom configurations may have to be modified to
+include it.
 
 In addition to enabling the feature in the cluster, a resource driver also has to
 be installed. Please refer to the driver's documentation for details.

From b6b1fc392d1255c12b9d9f741ff49fd9645c1e59 Mon Sep 17 00:00:00 2001
From: Maciej Szulik <maszulik@redhat.com>
Date: Tue, 7 Mar 2023 13:08:01 +0100
Subject: [PATCH 026/272] Promote CronJobTimeZone to stable

---
 .../workloads/controllers/cron-jobs.md        | 35 +++++++++----------
 .../feature-gates.md                          |  5 +--
 2 files changed, 20 insertions(+), 20 deletions(-)

diff --git a/content/en/docs/concepts/workloads/controllers/cron-jobs.md b/content/en/docs/concepts/workloads/controllers/cron-jobs.md
index dd327758e33..29ec67caab7 100644
--- a/content/en/docs/concepts/workloads/controllers/cron-jobs.md
+++ b/content/en/docs/concepts/workloads/controllers/cron-jobs.md
@@ -14,9 +14,9 @@ weight: 80
 
 A _CronJob_ creates {{< glossary_tooltip term_id="job" text="Jobs" >}} on a repeating schedule.
 
-CronJob is meant for performing regular scheduled actions such as backups, report generation, 
-and so on. One CronJob object is like one line of a _crontab_ (cron table) file on a 
-Unix system. It runs a job periodically on a given schedule, written in 
+CronJob is meant for performing regular scheduled actions such as backups, report generation,
+and so on. One CronJob object is like one line of a _crontab_ (cron table) file on a
+Unix system. It runs a job periodically on a given schedule, written in
 [Cron](https://en.wikipedia.org/wiki/Cron) format.
 
 CronJobs have limitations and idiosyncrasies.
@@ -162,19 +162,22 @@ For another way to clean up jobs automatically, see [Clean up finished jobs auto
 
 ### Time zones
 
-For CronJobs with no time zone specified, the {{< glossary_tooltip term_id="kube-controller-manager" text="kube-controller-manager" >}} interprets schedules relative to its local time zone.
+{{< feature-state for_k8s_version="v1.27" state="stable" >}}
 
-{{< feature-state for_k8s_version="v1.25" state="beta" >}}
+For CronJobs with no time zone specified, the {{< glossary_tooltip term_id="kube-controller-manager" text="kube-controller-manager" >}}
+interprets schedules relative to its local time zone.
 
-If you enable the  `CronJobTimeZone` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/),
-you can specify a time zone for a CronJob (if you don't enable that feature gate, or if you are using a version of
-Kubernetes that does not have experimental time zone support, all CronJobs in your cluster have an unspecified
-timezone).
+You can specify a time zone for a CronJob by setting `.spec.timeZone` to the name
+of a valid [time zone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
+For example, setting `.spec.timeZone: "Etc/UTC"` instructs Kubernetes to interpret
+the schedule relative to Coordinated Universal Time.
 
-When you have the feature enabled, you can set `.spec.timeZone` to the name of a valid [time zone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). For example, setting
-`.spec.timeZone: "Etc/UTC"` instructs Kubernetes to interpret the schedule relative to Coordinated Universal Time.
+A time zone database from the Go standard library is included in the binaries and used as a fallback in case an external database is not available on the system.
+
+## CronJob limitations {#cron-job-limitations}
+
+### Unsupported TimeZone specification
 
-{{< caution >}}
 The implementation of the CronJob API in Kubernetes {{< skew currentVersion >}} lets you set
 the `.spec.schedule` field to include a timezone; for example: `CRON_TZ=UTC * * * * *`
 or `TZ=UTC * * * * *`.
@@ -183,14 +186,10 @@ Specifying a timezone that way is **not officially supported** (and never has be
 
 If you try to set a schedule that includes `TZ` or `CRON_TZ` timezone specification,
 Kubernetes reports a [warning](/blog/2020/09/03/warnings/) to the client.
-Future versions of Kubernetes might not implement that unofficial timezone mechanism at all.
-{{< /caution >}}
-
-A time zone database from the Go standard library is included in the binaries and used as a fallback in case an external database is not available on the system.
-
-## CronJob limitations {#cron-job-limitations}
+Future versions of Kubernetes will prevent setting the unofficial timezone mechanism entirely.
 
 ### Modifying a CronJob
+
 By design, a CronJob contains a template for _new_ Jobs.
 If you modify an existing CronJob, the changes you make will apply to new Jobs that
 start to run after your modification is complete. Jobs (and their Pods) that have already
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 3680548e7af..f6288cb26d0 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
@@ -82,8 +82,6 @@ For a reference to old feature gates that are removed, please refer to
 | `ComponentSLIs` | `false` | Alpha | 1.26 | |
 | `ContainerCheckpoint` | `false` | Alpha | 1.25 | |
 | `ContextualLogging` | `false` | Alpha | 1.24 | |
-| `CronJobTimeZone` | `false` | Alpha | 1.24 | 1.24 |
-| `CronJobTimeZone` | `true` | Beta | 1.25 | |
 | `CrossNamespaceVolumeDataSource` | `false` | Alpha| 1.26 | |
 | `CustomCPUCFSQuotaPeriod` | `false` | Alpha | 1.12 | |
 | `CustomResourceValidationExpressions` | `false` | Alpha | 1.23 | 1.24 |
@@ -251,6 +249,9 @@ For a reference to old feature gates that are removed, please refer to
 | `CSIStorageCapacity` | `true` | Beta | 1.21 | 1.23 |
 | `CSIStorageCapacity` | `true` | GA | 1.24 | - |
 | `ConsistentHTTPGetHandlers` | `true` | GA | 1.25 | - |
+| `CronJobTimeZone` | `false` | Alpha | 1.24 | 1.24 |
+| `CronJobTimeZone` | `true` | Beta | 1.25 | 1.26 |
+| `CronJobTimeZone` | `true` | GA | 1.27 | - |
 | `DaemonSetUpdateSurge` | `false` | Alpha | 1.21 | 1.21 |
 | `DaemonSetUpdateSurge` | `true` | Beta | 1.22 | 1.24 |
 | `DaemonSetUpdateSurge` | `true` | GA | 1.25 | - |

From 7eefbb8de09c52e4072085567928d498ef10c6d5 Mon Sep 17 00:00:00 2001
From: Jan Safranek <jsafrane@redhat.com>
Date: Thu, 16 Mar 2023 09:53:26 +0100
Subject: [PATCH 027/272] Add NewVolumeManagerReconstruction feature gate

---
 .../command-line-tools-reference/feature-gates.md  | 14 ++++++++++++++
 1 file changed, 14 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 626cc6931f6..8c6b666b020 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
@@ -149,6 +149,7 @@ For a reference to old feature gates that are removed, please refer to
 | `MinimizeIPTablesRestore` | `false` | Alpha | 1.26 | - |
 | `MultiCIDRRangeAllocator` | `false` | Alpha | 1.25 | |
 | `NetworkPolicyStatus` | `false` | Alpha | 1.24 |  |
+| `NewVolumeManagerReconstruction` | `true` | Beta | 1.27 |  |
 | `NodeInclusionPolicyInPodTopologySpread` | `false` | Alpha | 1.25 | 1.25 |
 | `NodeInclusionPolicyInPodTopologySpread` | `true` | Beta | 1.26 | |
 | `NodeOutOfServiceVolumeDetach` | `false` | Alpha | 1.24 | 1.25 |
@@ -626,6 +627,19 @@ Each feature gate is designed for enabling/disabling a specific feature:
 - `NetworkPolicyEndPort`: Enable use of the field `endPort` in NetworkPolicy objects,
   allowing the selection of a port range instead of a single port.
 - `NetworkPolicyStatus`: Enable the `status` subresource for NetworkPolicy objects.
+- `NewVolumeManagerReconstruction`: Enable improved discovery of mounted volumes during kubelet
+  startup.
+  <!-- remove next 2 paragraphs when feature graduates to GA -->
+  Before Kubernetes v1.25, the kubelet used different default behavior for discovering mounted
+  volumes during the kubelet startup. If you disable this feature gate (it's enabled by default), you select
+  the legacy discovery behavior.
+
+  In Kubernetes v1.25 and v1.26, this behavior toggle was part of the `SELinuxMountReadWriteOncePod`
+  feature gate.
+- `NewVolumeManagerReconstruction`: Enables improved discovery of mounted volumes during kubelet
+  startup. Since this code has been significantly refactored, we allow to opt-out in case kubelet
+  gets stuck at the startup or is not unmounting volumes from terminated Pods. Note that this
+  refactoring was behind `SELinuxMountReadWriteOncePod` alpha feature gate in Kubernetes 1.25.
 - `NodeInclusionPolicyInPodTopologySpread`: Enable using `nodeAffinityPolicy` and `nodeTaintsPolicy` in
   [Pod topology spread constraints](/docs/concepts/scheduling-eviction/topology-spread-constraints/)
   when calculating pod topology spread skew.

From 3a4f7ab1e75d9426d44ed8c517a6d70f96862d87 Mon Sep 17 00:00:00 2001
From: Kensei Nakada <handbomusic@gmail.com>
Date: Sun, 12 Mar 2023 13:39:35 +0900
Subject: [PATCH 028/272] fix: HPA container resource metrics beta graduation

---
 .../reference/command-line-tools-reference/feature-gates.md    | 3 ++-
 .../en/docs/tasks/run-application/horizontal-pod-autoscale.md  | 2 +-
 2 files 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 1ea5df83424..94dcf45504f 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
@@ -104,7 +104,8 @@ For a reference to old feature gates that are removed, please refer to
 | `GracefulNodeShutdown` | `true` | Beta | 1.21 | |
 | `GracefulNodeShutdownBasedOnPodPriority` | `false` | Alpha | 1.23 | 1.23 |
 | `GracefulNodeShutdownBasedOnPodPriority` | `true` | Beta | 1.24 | |
-| `HPAContainerMetrics` | `false` | Alpha | 1.20 | |
+| `HPAContainerMetrics` | `false` | Alpha | 1.20 | 1.26 |
+| `HPAContainerMetrics` | `true` | Beta | 1.27 | |
 | `HPAScaleToZero` | `false` | Alpha | 1.16 | |
 | `HonorPVReclaimPolicy` | `false` | Alpha | 1.23 |  |
 | `IPTablesOwnershipCleanup` | `false` | Alpha | 1.25 | |
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 09c91f87803..b9c2b56a0c6 100644
--- a/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md
+++ b/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md
@@ -274,7 +274,7 @@ pod usage is still within acceptable limits.
 
 ### Container resource metrics
 
-{{< feature-state for_k8s_version="v1.20" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
 
 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.

From 3a81c94ba8b6ada277bc5e5e44a4e7ce62c2cfa9 Mon Sep 17 00:00:00 2001
From: Todd Neal <tnealt@amazon.com>
Date: Wed, 15 Mar 2023 14:06:10 -0500
Subject: [PATCH 029/272] remove pod-eviction-timeout documentation

pod-eviction-timeout has been removed from v1.27, update the docs to
reference the taint based eviction that is now the default and only
mechanism.
---
 .../en/docs/concepts/architecture/nodes.md    | 36 ++++++-------------
 .../taint-and-toleration.md                   |  5 +++
 2 files changed, 16 insertions(+), 25 deletions(-)

diff --git a/content/en/docs/concepts/architecture/nodes.md b/content/en/docs/concepts/architecture/nodes.md
index d36d82174b7..301f2b2fab6 100644
--- a/content/en/docs/concepts/architecture/nodes.md
+++ b/content/en/docs/concepts/architecture/nodes.md
@@ -215,34 +215,20 @@ of the Node resource. For example, the following JSON structure describes a heal
 ]
 ```
 
-If the `status` of the Ready condition remains `Unknown` or `False` for longer
-than the `pod-eviction-timeout` (an argument passed to the
-{{< glossary_tooltip text="kube-controller-manager" term_id="kube-controller-manager"
->}}), then the [node controller](#node-controller) triggers
-{{< glossary_tooltip text="API-initiated eviction" term_id="api-eviction" >}}
-for all Pods assigned to that node. The default eviction timeout duration is
-**five minutes**.
-In some cases when the node is unreachable, the API server is unable to communicate
-with the kubelet on the node. The decision to delete the pods cannot be communicated to
-the kubelet until communication with the API server is re-established. In the meantime,
-the pods that are scheduled for deletion may continue to run on the partitioned node.
-
-The node controller does not force delete pods until it is confirmed that they have stopped
-running in the cluster. You can see the pods that might be running on an unreachable node as
-being in the `Terminating` or `Unknown` state. In cases where Kubernetes cannot deduce from the
-underlying infrastructure if a node has permanently left a cluster, the cluster administrator
-may need to delete the node object by hand. Deleting the node object from Kubernetes causes
-all the Pod objects running on the node to be deleted from the API server and frees up their
-names.
-
 When problems occur on nodes, the Kubernetes control plane automatically creates
 [taints](/docs/concepts/scheduling-eviction/taint-and-toleration/) that match the conditions
-affecting the node.
-The scheduler takes the Node's taints into consideration when assigning a Pod to a Node.
-Pods can also have {{< glossary_tooltip text="tolerations" term_id="toleration" >}} that let
-them run on a Node even though it has a specific taint.
+affecting the node.  An example of this is when the `status` of the Ready condition
+remains `Unknown` or `False` for longer than the kube-controller-manager's `NodeMonitorGracePeriod`,
+which defaults to 40 seconds.  This will cause either an `node.kubernetes.io/unreachable` taint, for an `Unknown` status,
+or a `node.kubernetes.io/not-ready` taint, for a `False` status, to be added to the Node.
 
-See [Taint Nodes by Condition](/docs/concepts/scheduling-eviction/taint-and-toleration/#taint-nodes-by-condition)
+These taints affect pending pods as the scheduler takes the Node's taints into consideration when
+assigning a pod to a Node. Existing pods scheduled to the node may be evicted due to the application
+of `NoExecute` taints. Pods may also have {{< glossary_tooltip text="tolerations" term_id="toleration" >}} that let
+them schedule to and continue running on a Node even though it has a specific taint.
+
+See [Taint Based Evictions](/docs/concepts/scheduling-eviction/taint-and-toleration/#taint-based-evictions) and
+[Taint Nodes by Condition](/docs/concepts/scheduling-eviction/taint-and-toleration/#taint-nodes-by-condition)
 for more details.
 
 ### Capacity and Allocatable {#capacity}
diff --git a/content/en/docs/concepts/scheduling-eviction/taint-and-toleration.md b/content/en/docs/concepts/scheduling-eviction/taint-and-toleration.md
index 7fde68c09f8..3ffb845ec87 100644
--- a/content/en/docs/concepts/scheduling-eviction/taint-and-toleration.md
+++ b/content/en/docs/concepts/scheduling-eviction/taint-and-toleration.md
@@ -224,6 +224,11 @@ In case a node is to be evicted, the node controller or the kubelet adds relevan
 with `NoExecute` effect. If the fault condition returns to normal the kubelet or node
 controller can remove the relevant taint(s).
 
+In some cases when the node is unreachable, the API server is unable to communicate
+with the kubelet on the node. The decision to delete the pods cannot be communicated to
+the kubelet until communication with the API server is re-established. In the meantime,
+the pods that are scheduled for deletion may continue to run on the partitioned node.
+
 {{< note >}}
 The control plane limits the rate of adding node new taints to nodes. This rate limiting
 manages the number of evictions that are triggered when many nodes become unreachable at

From b17509592b4113e5c6fbc5c7d9d0cd3484488851 Mon Sep 17 00:00:00 2001
From: Ritikaa96 <ritika@india.nec.com>
Date: Fri, 17 Mar 2023 15:39:27 +0530
Subject: [PATCH 030/272] Deprecation Note addedi for loadbalancerIP

---
 .../concepts/services-networking/service.md   | 26 +++++++------------
 1 file changed, 10 insertions(+), 16 deletions(-)

diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md
index d096096ec2a..8aa0edf068d 100644
--- a/content/en/docs/concepts/services-networking/service.md
+++ b/content/en/docs/concepts/services-networking/service.md
@@ -645,12 +645,6 @@ status:
 Traffic from the external load balancer is directed at the backend Pods.
 The cloud provider decides how it is load balanced.
 
-Some cloud providers allow you to specify the `loadBalancerIP`. In those cases, the load-balancer is created
-with the user-specified `loadBalancerIP`. If the `loadBalancerIP` field is not specified,
-the loadBalancer is set up with an ephemeral IP address. If you specify a `loadBalancerIP`
-but your cloud provider does not support the feature, the `loadbalancerIP` field that you
-set is ignored.
-
 To implement a Service of `type: LoadBalancer`, Kubernetes typically starts off
 by making the changes that are equivalent to you requesting a Service of
 `type: NodePort`. The cloud-controller-manager component then configures the external load balancer to
@@ -663,16 +657,16 @@ cloud provider implementation supports this.
 
 {{< note >}}
 
-On **Azure**, if you want to use a user-specified public type `loadBalancerIP`, you first need
-to create a static type public IP address resource. This public IP address resource should
-be in the same resource group of the other automatically created resources of the cluster.
-For example, `MC_myResourceGroup_myAKSCluster_eastus`.
-
-Specify the assigned IP address as loadBalancerIP. Ensure that you have updated the
-`securityGroupName` in the cloud provider configuration file.
-For information about troubleshooting `CreatingLoadBalancerFailed` permission issues see,
-[Use a static IP address with the Azure Kubernetes Service (AKS) load balancer](https://docs.microsoft.com/en-us/azure/aks/static-ip)
-or [CreatingLoadBalancerFailed on AKS cluster with advanced networking](https://github.com/Azure/AKS/issues/357).
+The`.spec.loadBalancerIP` field for a Service was deprecated in Kubernetes v1.24.
+	
+This field was under-specified and its meaning varies across implementations. It also cannot support dual-stack networking. This field may be removed in a future API version.
+	
+If you're integrating with a provider that supports specifying the load balancer IP address(es)
+for a Service via a (provider specific) annotation, you should switch to doing that.
+	
+If you are writing code for a load balancer integration with Kubernetes, avoid using this field.
+You can integrate with [Gateway](https://gateway-api.sigs.k8s.io/) rather than Service, or you
+can define your own (provider specific) annotations on the Service that specify the equivalent detail.
 
 {{< /note >}}
 

From c79c8f2a12c59fd91418ba1e77a30451b88d2610 Mon Sep 17 00:00:00 2001
From: Ritikaa96 <ritika@india.nec.com>
Date: Tue, 21 Mar 2023 19:04:20 +0530
Subject: [PATCH 031/272] Adding loadbalancerdeprecation info and removing
 Azure Info in NOTE

Signed-off-by: Ritikaa96 <ritika@india.nec.com>
---
 content/en/docs/concepts/services-networking/service.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md
index 8aa0edf068d..2f97b28f25f 100644
--- a/content/en/docs/concepts/services-networking/service.md
+++ b/content/en/docs/concepts/services-networking/service.md
@@ -654,6 +654,11 @@ You can configure a load balanced Service to
 [omit](#load-balancer-nodeport-allocation) assigning a node port, provided that the
 cloud provider implementation supports this.
 
+Some cloud providers allow you to specify the `loadBalancerIP`. In those cases, the load-balancer is created
+with the user-specified `loadBalancerIP`. If the `loadBalancerIP` field is not specified,
+the loadBalancer is set up with an ephemeral IP address. If you specify a `loadBalancerIP`
+but your cloud provider does not support the feature, the `loadbalancerIP` field that you
+set is ignored.
 
 {{< note >}}
 

From 6f914b6f60b3937af868d436dd1f84971a4f8a19 Mon Sep 17 00:00:00 2001
From: Antonio Ojea <aojea@google.com>
Date: Tue, 21 Mar 2023 13:57:44 +0000
Subject: [PATCH 033/272] KEP-1880 MultiCIDRServiceAllocator

Signed-off-by: Antonio Ojea <aojea@google.com>
---
 .../reference/command-line-tools-reference/feature-gates.md | 3 +++
 content/en/docs/reference/networking/virtual-ips.md         | 6 ++++++
 2 files changed, 9 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 6021f29a734..95151f0e27c 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
@@ -146,6 +146,7 @@ For a reference to old feature gates that are removed, please refer to
 | `MinDomainsInPodTopologySpread` | `false` | Beta | 1.25 | |
 | `MinimizeIPTablesRestore` | `false` | Alpha | 1.26 | - |
 | `MultiCIDRRangeAllocator` | `false` | Alpha | 1.25 | |
+| `MultiCIDRServiceAllocator` | `false` | Alpha | 1.27 | |
 | `NetworkPolicyStatus` | `false` | Alpha | 1.24 |  |
 | `NodeInclusionPolicyInPodTopologySpread` | `false` | Alpha | 1.25 | 1.25 |
 | `NodeInclusionPolicyInPodTopologySpread` | `true` | Beta | 1.26 | |
@@ -625,6 +626,8 @@ Each feature gate is designed for enabling/disabling a specific feature:
 - `MixedProtocolLBService`: Enable using different protocols in the same `LoadBalancer` type
   Service instance.
 - `MultiCIDRRangeAllocator`: Enables the MultiCIDR range allocator.
+- `MultiCIDRServiceAllocator`: Enables a new IPAddress object kind, and a new Service ClusterIP allocator.
+  The new allocator removes previous Service CIDR block size limitations for IPv4, and limits IPv6 size to a /64.
 - `NetworkPolicyEndPort`: Enable use of the field `endPort` in NetworkPolicy objects,
   allowing the selection of a port range instead of a single port.
 - `NetworkPolicyStatus`: Enable the `status` subresource for NetworkPolicy objects.
diff --git a/content/en/docs/reference/networking/virtual-ips.md b/content/en/docs/reference/networking/virtual-ips.md
index 670960f1710..32ff8626f0e 100644
--- a/content/en/docs/reference/networking/virtual-ips.md
+++ b/content/en/docs/reference/networking/virtual-ips.md
@@ -271,6 +271,12 @@ When clients connect to the VIP, their traffic is automatically transported to a
 appropriate endpoint. The environment variables and DNS for Services are actually
 populated in terms of the Service's virtual IP address (and port).
 
+{{< feature-state for_k8s_version="v1.27" state="alpha" >}}
+If you enable the `MultiCIDRServiceAllocator`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/),
+the `ClusterIP` address associated to each `Service` will have a referenced
+`IPAddress` object.
+
 ### Avoiding collisions
 
 One of the primary philosophies of Kubernetes is that you should not be

From 801b556183b2e8a29c601325f69c66b86af3a7d3 Mon Sep 17 00:00:00 2001
From: Michal Wozniak <mw219725@gmail.com>
Date: Mon, 6 Mar 2023 12:43:19 +0100
Subject: [PATCH 034/272] Update for KEP3329: "Retriable and non-retriable Pod
 failures for Jobs"

Co-authored-by: Aldo Culquicondor <1299064+alculquicondor@users.noreply.github.com>
---
 .../concepts/workloads/controllers/job.md     |  11 ++
 .../concepts/workloads/pods/disruptions.md    |   5 -
 .../concepts/workloads/pods/pod-lifecycle.md  |   8 ++
 .../en/docs/tasks/job/pod-failure-policy.md   | 111 ++++++++++++++++++
 .../job-pod-failure-policy-config-issue.yaml  |  19 +++
 5 files changed, 149 insertions(+), 5 deletions(-)
 create mode 100644 content/en/examples/controllers/job-pod-failure-policy-config-issue.yaml

diff --git a/content/en/docs/concepts/workloads/controllers/job.md b/content/en/docs/concepts/workloads/controllers/job.md
index ecdcb62027b..7d83ca69992 100644
--- a/content/en/docs/concepts/workloads/controllers/job.md
+++ b/content/en/docs/concepts/workloads/controllers/job.md
@@ -807,6 +807,17 @@ These are some requirements and semantics of the API:
   - `Count`: use to indicate that the Pod should be handled in the default way.
      The counter towards the `.spec.backoffLimit` should be incremented.
 
+{{< note >}}
+When you use a `podFailurePolicy`, the job controller only matches Pods in the
+`Failed` phase. Pods with a deletion timestamp that are not in a terminal phase
+(`Failed` or `Succeeded`) are considered still terminating. This implies that
+terminating pods retain a [tracking finalizer](#job-tracking-with-finalizers)
+until they reach a terminal phase.
+Since Kubernetes 1.27, Kubelet transitions deleted pods to a terminal phase
+(see: [Pod Phase](/docs/concepts/workloads/pods/pod-lifecycle/#pod-phase)). This
+ensures that deleted pods have their finalizers removed by the Job controller.
+{{< /note >}}
+
 ### Job tracking with finalizers
 
 {{< feature-state for_k8s_version="v1.26" state="stable" >}}
diff --git a/content/en/docs/concepts/workloads/pods/disruptions.md b/content/en/docs/concepts/workloads/pods/disruptions.md
index 1ddbfa4c2aa..25982067532 100644
--- a/content/en/docs/concepts/workloads/pods/disruptions.md
+++ b/content/en/docs/concepts/workloads/pods/disruptions.md
@@ -231,11 +231,6 @@ can happen, according to:
 
 {{< feature-state for_k8s_version="v1.26" state="beta" >}}
 
-{{< note >}}
-If you are using an older version of Kubernetes than {{< skew currentVersion >}}
-please refer to the corresponding version of the documentation.
-{{< /note >}}
-
 {{< note >}}
 In order to use this behavior, you must have the `PodDisruptionConditions`
 [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
diff --git a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md
index 43f9c70ccf3..d37dbb18eb3 100644
--- a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md
+++ b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md
@@ -91,6 +91,12 @@ A Pod is granted a term to terminate gracefully, which defaults to 30 seconds.
 You can use the flag `--force` to [terminate a Pod by force](/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination-forced).
 {{< /note >}}
 
+Since Kubernetes 1.27, the kubelet transitions deleted pods, except for
+[static pods](/docs/tasks/configure-pod-container/static-pod/) and
+[force-deleted pods](/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination-forced)
+without a finalizer, to a terminal phase (`Failed` or `Succeeded` depending on
+the exit statuses of the pod containers) before their deletion from the API server.
+
 If a node dies or is disconnected from the rest of the cluster, Kubernetes
 applies a policy for setting the `phase` of all Pods on the lost node to Failed.
 
@@ -476,6 +482,8 @@ An example flow:
 1. When the grace period expires, the kubelet triggers forcible shutdown. The container runtime sends
    `SIGKILL` to any processes still running in any container in the Pod.
    The kubelet also cleans up a hidden `pause` container if that container runtime uses one.
+1. The kubelet transitions the pod into a terminal phase (`Failed` or `Succeeded` depending on
+   the end state of its containers). This step is guaranteed since version 1.27.
 1. The kubelet triggers forcible removal of Pod object from the API server, by setting grace period
    to 0 (immediate deletion).
 1. The API server deletes the Pod's API object, which is then no longer visible from any client.
diff --git a/content/en/docs/tasks/job/pod-failure-policy.md b/content/en/docs/tasks/job/pod-failure-policy.md
index 3cafd35ae98..124331847cc 100644
--- a/content/en/docs/tasks/job/pod-failure-policy.md
+++ b/content/en/docs/tasks/job/pod-failure-policy.md
@@ -28,6 +28,9 @@ You should already be familiar with the basic use of [Job](/docs/concepts/worklo
 
 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
 
+Ensure that the [feature gates](/docs/reference/command-line-tools-reference/feature-gates/)
+`PodDisruptionConditions` and `JobPodFailurePolicy` are both enabled in your cluster.
+
 ## Using Pod failure policy to avoid unnecessary Pod retries
 
 With the following example, you can learn how to use Pod failure policy to
@@ -129,6 +132,114 @@ kubectl delete jobs/job-pod-failure-policy-ignore
 
 The cluster automatically cleans up the Pods.
 
+## Using Pod failure policy to avoid unnecessary Pod retries based on custom Pod Conditions
+
+With the following example, you can learn how to use Pod failure policy to
+avoid unnecessary Pod restarts based on custom Pod Conditions.
+
+{{< note >}}
+The example below works since version 1.27 as it relies on transitioning of
+deleted pods, in the `Pending` phase, to a terminal phase
+(see: [Pod Phase](/docs/concepts/workloads/pods/pod-lifecycle/#pod-phase)).
+{{< /note >}}
+
+1. First, create a Job based on the config:
+
+   {{< codenew file="/controllers/job-pod-failure-policy-config-issue.yaml" >}}
+
+   by running:
+
+   ```sh
+   kubectl create -f job-pod-failure-policy-config-issue.yaml
+   ```
+
+   Note that, the image is misconfigured, as it does not exist.
+
+2. Inspect the status of the job's Pods by running:
+
+   ```sh
+   kubectl get pods -l job-name=job-pod-failure-policy-config-issue -o yaml
+   ```
+
+   You will see output similar to this:
+   ```yaml
+   containerStatuses:
+   - image: non-existing-repo/non-existing-image:example
+      ...
+      state:
+      waiting:
+         message: Back-off pulling image "non-existing-repo/non-existing-image:example"
+         reason: ImagePullBackOff
+         ...
+   phase: Pending
+   ```
+
+   Note that the pod remains in the `Pending` phase as it fails to pull the
+   misconfigured image. This, in principle, could be a transient issue and the
+   image could get pulled. However, in this case, the image does not exist so
+   we indicate this fact by a custom condition.
+
+3. Add the custom condition. First prepare the patch by running:
+
+   ```sh
+   cat <<EOF > patch.yaml
+   status:
+     conditions:
+     - type: ConfigIssue
+       status: "True"
+       reason: "NonExistingImage"
+       lastTransitionTime: "$(date -u +"%Y-%m-%dT%H:%M:%SZ")"
+   EOF
+   ```
+   Second, select one of the pods created by the job by running:
+   ```
+   podName=$(kubectl get pods -l job-name=job-pod-failure-policy-config-issue -o jsonpath='{.items[0].metadata.name}')
+   ```
+
+   Then, apply the patch on one of the pods by running the following command:
+
+   ```sh
+   kubectl patch pod $podName --subresource=status --patch-file=patch.yaml
+   ```
+
+   If applied successfully, you will get a notification like this:
+
+   ```sh
+   pod/job-pod-failure-policy-config-issue-k6pvp patched
+   ```
+
+4. Delete the pod to transition it to `Failed` phase, by running the command:
+
+   ```sh
+   kubectl delete pods/$podName
+   ```
+
+5. Inspect the status of the Job by running:
+
+   ```sh
+   kubectl get jobs -l job-name=job-pod-failure-policy-config-issue -o yaml
+   ```
+
+   In the Job status, see a job `Failed` condition with the field `reason`
+   equal `PodFailurePolicy`. Additionally, the `message` field contains a
+   more detailed information about the Job termination, such as:
+   `Pod default/job-pod-failure-policy-config-issue-k6pvp has condition ConfigIssue matching FailJob rule at index 0`.
+
+{{< note >}}
+In a production environment, the steps 3 and 4 should be automated by a
+user-provided controller.
+{{< /note >}}
+
+### Cleaning up
+
+Delete the Job you created:
+
+```sh
+kubectl delete jobs/job-pod-failure-policy-config-issue
+```
+
+The cluster automatically cleans up the Pods.
+
 ## Alternatives
 
 You could rely solely on the
diff --git a/content/en/examples/controllers/job-pod-failure-policy-config-issue.yaml b/content/en/examples/controllers/job-pod-failure-policy-config-issue.yaml
new file mode 100644
index 00000000000..fc82ca188c0
--- /dev/null
+++ b/content/en/examples/controllers/job-pod-failure-policy-config-issue.yaml
@@ -0,0 +1,19 @@
+apiVersion: batch/v1
+kind: Job
+metadata:
+  name: job-pod-failure-policy-config-issue
+spec:
+  completions: 8
+  parallelism: 2
+  template:
+    spec:
+      restartPolicy: Never
+      containers:
+      - name: main
+        image: "non-existing-repo/non-existing-image:example"
+  backoffLimit: 6
+  podFailurePolicy:
+    rules:
+    - action: FailJob
+      onPodConditions:
+      - type: ConfigIssue

From 15b2e78646ee694f028adebef141b116a74b0732 Mon Sep 17 00:00:00 2001
From: Han Kang <hankang@google.com>
Date: Tue, 21 Mar 2023 09:04:28 -0700
Subject: [PATCH 035/272] add documentation for beta stability levels

---
 content/en/docs/reference/using-api/deprecation-policy.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/content/en/docs/reference/using-api/deprecation-policy.md b/content/en/docs/reference/using-api/deprecation-policy.md
index 9bf80456e46..ad8b0291b27 100644
--- a/content/en/docs/reference/using-api/deprecation-policy.md
+++ b/content/en/docs/reference/using-api/deprecation-policy.md
@@ -425,7 +425,7 @@ to determine SLOs, these tend to have greater import. Other metrics are more
 experimental in nature or are used primarily in the Kubernetes development
 process.
 
-Accordingly, metrics fall under two stability classes (`ALPHA` and `STABLE`);
+Accordingly, metrics fall under three stability classes (`ALPHA`, `BETA` `STABLE`);
 this impacts removal of a metric during a Kubernetes release. These classes
 are determined by the perceived importance of the metric. The rules for
 deprecating and removing a metric are as follows:
@@ -433,11 +433,13 @@ deprecating and removing a metric are as follows:
 **Rule #9a: Metrics, for the corresponding stability class, must function for no less than:**
 
    * **STABLE: 4 releases or 12 months (whichever is longer)**
+   * **BETA: 2 releases or 8 months (whichever is longer)**
    * **ALPHA: 0 releases**
 
 **Rule #9b: Metrics, after their _announced deprecation_, must function for no less than:**
 
    * **STABLE: 3 releases or 9 months (whichever is longer)**
+   * **BETA: 1 releases or 4 months (whichever is longer)**
    * **ALPHA: 0 releases**
 
 Deprecated metrics will have their description text prefixed with a deprecation notice

From 8212bf1edd6aacd7b261575fafd79b5d778720a5 Mon Sep 17 00:00:00 2001
From: Shihang Zhang <zshihang@google.com>
Date: Tue, 21 Mar 2023 09:10:08 -0700
Subject: [PATCH 036/272] update LegacyServiceAccountTokenTracking to beta

---
 .../reference/command-line-tools-reference/feature-gates.md    | 3 ++-
 1 file 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 6021f29a734..6145065a73e 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
@@ -126,7 +126,8 @@ For a reference to old feature gates that are removed, please refer to
 | `KubeletPodResourcesGetAllocatable` | `false` | Alpha | 1.21 | 1.22 |
 | `KubeletPodResourcesGetAllocatable` | `true` | Beta | 1.23 | |
 | `KubeletTracing` | `false` | Alpha | 1.25 | |
-| `LegacyServiceAccountTokenTracking` | `false` | Alpha | 1.25 | |
+| `LegacyServiceAccountTokenTracking` | `false` | Alpha | 1.26 | 1.26 |
+| `LegacyServiceAccountTokenTracking` | `true` | Beta | 1.27 | |
 | `LocalStorageCapacityIsolationFSQuotaMonitoring` | `false` | Alpha | 1.15 | - |
 | `LogarithmicScaleDown` | `false` | Alpha | 1.21 | 1.21 |
 | `LogarithmicScaleDown` | `true` | Beta | 1.22 | |

From 6887d395f3db9913904cdcd9a9bab7dd2b3b9abe Mon Sep 17 00:00:00 2001
From: xuzhenglun <xuzhenglun@gmail.com>
Date: Wed, 22 Mar 2023 03:38:02 +0800
Subject: [PATCH 037/272] add docs in service concepts

---
 .../docs/concepts/services-networking/service.md   | 14 ++++++++++++++
 .../command-line-tools-reference/feature-gates.md  |  1 +
 2 files changed, 15 insertions(+)

diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md
index df4895e52fb..1eaa5539754 100644
--- a/content/en/docs/concepts/services-networking/service.md
+++ b/content/en/docs/concepts/services-networking/service.md
@@ -586,6 +586,20 @@ spec:
       nodePort: 30007
 ```
 
+#### Reserve Nodeport Ranges to avoid collisions when port assigning 
+
+{{< feature-state for_k8s_version="v1.27" state="alpha" >}}
+
+The policy for assigning ports to NodePort services applies to both the auto-assignment and
+the manual assignment scenarios. When a user wants to create a NodePort service that
+uses a specific port, the target port may conflict with another port that has already been assigned.
+In this case, you can enable the feature gate `ServiceNodePortStaticSubrange`, which allows you
+to use a different port allocation strategy for NodePort Services. The port range for NodePort services
+is divided into two bands. Dynamic port assignment uses the upper band by default, and it may use
+the lower band once the upper band has been exhausted. Users can then allocate from the lower band
+with a lower risk of port collision.
+
+
 #### Custom IP address configuration for `type: NodePort` Services {#service-nodeport-custom-listen-address}
 
 You can set up nodes in your cluster to use a particular IP address for serving node port
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 afac9234a7e..234a31af40d 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,6 +186,7 @@ For a reference to old feature gates that are removed, please refer to
 | `SeccompDefault` | `true` | Beta | 1.25 | |
 | `ServerSideFieldValidation` | `false` | Alpha | 1.23 | 1.24 |
 | `ServerSideFieldValidation` | `true` | Beta | 1.25 | |
+| `ServiceNodePortStaticSubrange` | `false` | Alpha | 1.27 | |
 | `SizeMemoryBackedVolumes` | `false` | Alpha | 1.20 | 1.21 |
 | `SizeMemoryBackedVolumes` | `true` | Beta | 1.22 | |
 | `StatefulSetAutoDeletePVC` | `false` | Alpha | 1.22 | |

From bcff6ab600cc3ba873cbac0f515036fba0af1822 Mon Sep 17 00:00:00 2001
From: Sascha Grunert <sgrunert@redhat.com>
Date: Fri, 10 Mar 2023 08:25:27 +0100
Subject: [PATCH 038/272] [KEP-2053] Add docs for DownwardAPIHugepages
 graduation

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
---
 content/en/docs/concepts/workloads/pods/downward-api.md    | 4 ++--
 .../command-line-tools-reference/feature-gates.md          | 7 ++++---
 2 files changed, 6 insertions(+), 5 deletions(-)

diff --git a/content/en/docs/concepts/workloads/pods/downward-api.md b/content/en/docs/concepts/workloads/pods/downward-api.md
index a3cb201d473..971475199c5 100644
--- a/content/en/docs/concepts/workloads/pods/downward-api.md
+++ b/content/en/docs/concepts/workloads/pods/downward-api.md
@@ -107,10 +107,10 @@ for resources such as CPU and memory.
 : A container's memory request
 
 `resource: limits.hugepages-*`
-: A container's hugepages limit (provided that the `DownwardAPIHugePages` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled)
+: A container's hugepages limit
 
 `resource: requests.hugepages-*`
-: A container's hugepages request (provided that the `DownwardAPIHugePages` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled)
+: A container's hugepages request
 
 `resource: limits.ephemeral-storage`
 : A container's ephemeral-storage limit
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 626cc6931f6..a2ec9b47f87 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
@@ -90,9 +90,6 @@ For a reference to old feature gates that are removed, please refer to
 | `CustomResourceValidationExpressions` | `true` | Beta | 1.25 | |
 | `DisableCloudProviders` | `false` | Alpha | 1.22 | |
 | `DisableKubeletCloudCredentialProviders` | `false` | Alpha | 1.23 | |
-| `DownwardAPIHugePages` | `false` | Alpha | 1.20 | 1.20 |
-| `DownwardAPIHugePages` | `false` | Beta | 1.21 | 1.21 |
-| `DownwardAPIHugePages` | `true` | Beta | 1.22 | |
 | `DynamicResourceAllocation` | `false` | Alpha | 1.26 | |
 | `EventedPLEG` | `false` | Alpha | 1.26 | - |
 | `ExpandedDNSConfig` | `false` | Alpha | 1.22 | 1.25 |
@@ -265,6 +262,10 @@ For a reference to old feature gates that are removed, please refer to
 | `DisableAcceleratorUsageMetrics` | `false` | Alpha | 1.19 | 1.19 |
 | `DisableAcceleratorUsageMetrics` | `true` | Beta | 1.20 | 1.24 |
 | `DisableAcceleratorUsageMetrics` | `true` | GA | 1.25 |- |
+| `DownwardAPIHugePages` | `false` | Alpha | 1.20 | 1.20 |
+| `DownwardAPIHugePages` | `false` | Beta | 1.21 | 1.21 |
+| `DownwardAPIHugePages` | `true` | Beta | 1.22 | 1.26 |
+| `DownwardAPIHugePages` | `true` | GA | 1.27 | - |
 | `DryRun` | `false` | Alpha | 1.12 | 1.12 |
 | `DryRun` | `true` | Beta | 1.13 | 1.18 |
 | `DryRun` | `true` | GA | 1.19 | - |

From 5170f4a669576e01c7a2a79a822851163d7c9a5a Mon Sep 17 00:00:00 2001
From: Dan Winship <danwinship@redhat.com>
Date: Tue, 31 Jan 2023 09:11:06 -0500
Subject: [PATCH 039/272] Update iptables perf discussion for 1.27

Co-authored-by: Tim Bannister <tim@scalefactory.com>
---
 .../docs/reference/networking/virtual-ips.md  | 60 +++++++++----------
 1 file changed, 28 insertions(+), 32 deletions(-)

diff --git a/content/en/docs/reference/networking/virtual-ips.md b/content/en/docs/reference/networking/virtual-ips.md
index 670960f1710..d022448ea09 100644
--- a/content/en/docs/reference/networking/virtual-ips.md
+++ b/content/en/docs/reference/networking/virtual-ips.md
@@ -131,6 +131,26 @@ iptables:
 ...
 ```
 
+##### Performance optimization for `iptables` mode {#minimize-iptables-restore}
+
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
+
+In Kubernetes {{< skew currentVersion >}} the kube-proxy defaults to a minimal approach
+to `iptables-restore` operations, only making updates where Services or EndpointSlices have
+actually changed. This is a performance optimization.
+The original implementation updated all the rules for all Services on every sync; this
+sometimes led to performance issues (update lag) in large clusters.
+
+If you are not running kube-proxy from Kubernetes {{< skew currentVersion >}}, check
+the behavior and associated advice for the version that you are actually running.
+
+If you were previously overriding `minSyncPeriod`, you should try
+removing that override and letting kube-proxy use the default value
+(`1s`) or at least a smaller value than you were using before upgrading.
+You can select the legacy behavior by disabling the `MinimizeIPTablesRestore`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+(you should not need to).
+
 ##### `minSyncPeriod`
 
 The `minSyncPeriod` parameter sets the minimum duration between
@@ -142,7 +162,7 @@ things change in a small time period. For example, if you have a
 Service backed by a {{< glossary_tooltip term_id="deployment" text="Deployment" >}}
 with 100 pods, and you delete the
 Deployment, then with `minSyncPeriod: 0s`, kube-proxy would end up
-removing the Service's Endpoints from the iptables rules one by one,
+removing the Service's endpoints from the iptables rules one by one,
 for a total of 100 updates. With a larger `minSyncPeriod`, multiple
 Pod deletion events would get aggregated
 together, so kube-proxy might
@@ -154,20 +174,19 @@ The larger the value of `minSyncPeriod`, the more work that can be
 aggregated, but the downside is that each individual change may end up
 waiting up to the full `minSyncPeriod` before being processed, meaning
 that the iptables rules spend more time being out-of-sync with the
-current apiserver state.
+current API server state.
 
-The default value of `1s` is a good compromise for small and medium
-clusters. In large clusters, it may be necessary to set it to a larger
-value. (Especially, if kube-proxy's
-`sync_proxy_rules_duration_seconds` metric indicates an average
-time much larger than 1 second, then bumping up `minSyncPeriod` may
-make updates more efficient.)
+The default value of `1s` should work well in most clusters, but in very
+large clusters it may be necessary to set it to a larger value.
+Especially, if kube-proxy's `sync_proxy_rules_duration_seconds` metric
+indicates an average time much larger than 1 second, then bumping up
+`minSyncPeriod` may make updates more efficient.
 
 ##### `syncPeriod`
 
 The `syncPeriod` parameter controls a handful of synchronization
 operations that are not directly related to changes in individual
-Services and Endpoints. In particular, it controls how quickly
+Services and EndpointSlices. In particular, it controls how quickly
 kube-proxy notices if an external component has interfered with
 kube-proxy's iptables rules. In large clusters, kube-proxy also only
 performs certain cleanup operations once every `syncPeriod` to avoid
@@ -178,29 +197,6 @@ impact on performance, but in the past, it was sometimes useful to set
 it to a very large value (eg, `1h`). This is no longer recommended,
 and is likely to hurt functionality more than it improves performance.
 
-##### Experimental performance improvements {#minimize-iptables-restore}
-
-{{< feature-state for_k8s_version="v1.26" state="alpha" >}}
-
-In Kubernetes 1.26, some new performance improvements were made to the
-iptables proxy mode, but they are not enabled by default (and should
-probably not be enabled in production clusters yet). To try them out,
-enable the `MinimizeIPTablesRestore` [feature
-gate](/docs/reference/command-line-tools-reference/feature-gates/) for
-kube-proxy with `--feature-gates=MinimizeIPTablesRestore=true,…`.
-
-If you enable that feature gate and
-you were previously overriding
-`minSyncPeriod`, you should try removing that override and letting
-kube-proxy use the default value (`1s`) or at least a smaller value
-than you were using before.
-
-If you notice kube-proxy's
-`sync_proxy_rules_iptables_restore_failures_total` or
-`sync_proxy_rules_iptables_partial_restore_failures_total` metrics
-increasing after enabling this feature, that likely indicates you are
-encountering bugs in the feature and you should file a bug report.
-
 ### IPVS proxy mode {#proxy-mode-ipvs}
 
 In `ipvs` mode, kube-proxy watches Kubernetes Services and EndpointSlices,

From b17085427749eb68ee43c00b1f1712cc27510204 Mon Sep 17 00:00:00 2001
From: Kevin Delgado <kevindelgado@google.com>
Date: Tue, 31 Jan 2023 16:58:29 +0000
Subject: [PATCH 040/272] docs for field validation GA

---
 .../reference/command-line-tools-reference/feature-gates.md  | 5 +++--
 content/en/docs/reference/using-api/api-concepts.md          | 2 +-
 2 files changed, 4 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 544dc68d612..96fd5d7937c 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
@@ -181,8 +181,6 @@ For a reference to old feature gates that are removed, please refer to
 | `SELinuxMountReadWriteOncePod` | `false` | Alpha | 1.25 | |
 | `SeccompDefault` | `false` | Alpha | 1.22 | 1.24 |
 | `SeccompDefault` | `true` | Beta | 1.25 | |
-| `ServerSideFieldValidation` | `false` | Alpha | 1.23 | 1.24 |
-| `ServerSideFieldValidation` | `true` | Beta | 1.25 | |
 | `ServiceNodePortStaticSubrange` | `false` | Alpha | 1.27 | |
 | `SizeMemoryBackedVolumes` | `false` | Alpha | 1.20 | 1.21 |
 | `SizeMemoryBackedVolumes` | `true` | Beta | 1.22 | |
@@ -313,6 +311,9 @@ For a reference to old feature gates that are removed, please refer to
 | `ServerSideApply` | `false` | Alpha | 1.14 | 1.15 |
 | `ServerSideApply` | `true` | Beta | 1.16 | 1.21 |
 | `ServerSideApply` | `true` | GA | 1.22 | - |
+| `ServerSideFieldValidation` | `false` | Alpha | 1.23 | 1.24 |
+| `ServerSideFieldValidation` | `true` | Beta | 1.25 | 1.26 |
+| `ServerSideFieldValidation` | `true` | GA | 1.27 | - |
 | `ServiceIPStaticSubrange` | `false` | Alpha | 1.24 | 1.24 |
 | `ServiceIPStaticSubrange` | `true` | Beta | 1.25 | 1.25 |
 | `ServiceIPStaticSubrange` | `true` | GA | 1.26 | - |
diff --git a/content/en/docs/reference/using-api/api-concepts.md b/content/en/docs/reference/using-api/api-concepts.md
index 3c7c0fa8ccb..2396fbd1eb4 100644
--- a/content/en/docs/reference/using-api/api-concepts.md
+++ b/content/en/docs/reference/using-api/api-concepts.md
@@ -700,7 +700,7 @@ These situations are:
 
 ### Setting the field validation level
 
-  {{< feature-state for_k8s_version="v1.25" state="beta" >}}
+  {{< feature-state for_k8s_version="v1.27" state="stable" >}}
 
 Provided that the `ServerSideFieldValidation` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled (disabled
 by default in 1.23 and 1.24, enabled by default starting in 1.25), you can take

From c0df96e6aab96d246b747c572043fbd5d23494e7 Mon Sep 17 00:00:00 2001
From: Kevin Delgado <kevindelgado@google.com>
Date: Wed, 1 Feb 2023 17:29:54 +0000
Subject: [PATCH 041/272] make more timeless

---
 .../docs/reference/using-api/api-concepts.md  | 62 ++++++++++---------
 1 file changed, 32 insertions(+), 30 deletions(-)

diff --git a/content/en/docs/reference/using-api/api-concepts.md b/content/en/docs/reference/using-api/api-concepts.md
index 2396fbd1eb4..803736957ea 100644
--- a/content/en/docs/reference/using-api/api-concepts.md
+++ b/content/en/docs/reference/using-api/api-concepts.md
@@ -698,29 +698,13 @@ These situations are:
    fields via `x-kubernetes-preserve-unknown-fields`).
 2. The field is duplicated in the object.
 
-### Setting the field validation level
+### Validation for unrecognized or duplicate fields (#setting-the-field-validation-level)
 
   {{< feature-state for_k8s_version="v1.27" state="stable" >}}
 
-Provided that the `ServerSideFieldValidation` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled (disabled
-by default in 1.23 and 1.24, enabled by default starting in 1.25), you can take
-advantage of server side field validation to catch these unrecognized fields.
-
-When you use HTTP verbs that can submit data (`POST`, `PUT`, and `PATCH`), field
-validation gives you the option to choose how you would like to be notified of
-these fields that are being dropped by the API server. Possible levels of
-validation are `Ignore`, `Warn`, and `Strict`.
-
-{{< note >}}
-If you submit a request that specifies an unrecognized field, and that is also invalid for
-a different reason (for example, the request provides a string value where the API expects
-an integer), then the API server responds with a 400 Bad Request error response.
-
-You always receive an error response in this case, no matter what field validation level you requested.
-{{< /note >}}
-
-Field validation is set by the `fieldValidation` query parameter. The three
-values that you can provide for this parameter are:
+From 1.25 onward, unrecognized or duplicate fields in an object are detected via
+validation on the server when you use HTTP verbs that can submit data (`POST`, `PUT`, and `PATCH`). Possible levels of
+validation are `Ignore`, `Warn` (default), and `Strict`.
 
 `Ignore`
 : The API server succeeds in handling the request as it would without the erroneous fields
@@ -740,20 +724,38 @@ detects any unknown or duplicate fields. The response message from the API
 server specifies all the unknown or duplicate fields that the API server has
 detected.
 
+The field validation level is set by the `fieldValidation` query parameter.
+
+{{< note >}}
+If you submit a request that specifies an unrecognized field, and that is also invalid for
+a different reason (for example, the request provides a string value where the API expects
+an integer for a known field), then the API server responds with a 400 Bad Request error, but will
+not provide any information on unknown or duplicate fields (only which fatal
+error it encountered first).
+
+You always receive an error response in this case, no matter what field validation level you requested.
+{{< /note >}}
+
 Tools that submit requests to the server (such as `kubectl`), might set their own
 defaults that are different from the `Warn` validation level that the API server uses
 by default.
 
-The `kubectl` tool uses the `--validate` flag to set the level of field validation.
-Historically `--validate` was used to toggle client-side validation on or off as
-a boolean flag. Since Kubernetes 1.25, kubectl uses
-server-side field validation when sending requests to a server with this feature
-enabled. Validation will fall back to client-side only when it cannot connect
-to an API server with field validation enabled.
-It accepts the values `ignore`, `warn`,
-and `strict` while also accepting the values `true` (equivalent to `strict`) and `false`
-(equivalent to `ignore`). The default validation setting for kubectl is `--validate=true`,
-which means strict server-side field validation.
+The `kubectl` tool uses the `--validate` flag to set the level of field
+validation. It accepts the values `ignore`, `warn`, and `strict` while
+also accepting the values `true` (equivalent to `strict`) and `false`
+(equivalent to `ignore`). The default validation setting for kubectl is
+`--validate=true`, which means strict server-side field validation.
+
+When kubectl cannot connect to an API server with field validation (API servers
+prior to Kubernetes 1.27), it will fall back to using client-side validation.
+Client-side validation will be removed entirely in a future version of kubectl.
+
+{{< note >}}
+
+Prior to Kubernetes 1.25  `kubectl --validate` was used to toggle client-side validation on or off as
+a boolean flag.
+
+{{< /note >}}
 
 ## Dry-run
 

From 457c26b997ed2d3564a6b3fa46f2f271e7c9b32e Mon Sep 17 00:00:00 2001
From: Cici Huang <cicih@google.com>
Date: Tue, 21 Mar 2023 23:46:15 +0000
Subject: [PATCH 042/272] Adding MatchConditions into ValidatingAdmissionPolicy

---
 .../validating-admission-policy.md            | 21 ++++++++++++++++++
 ...ing-admission-policy-match-conditions.yaml | 22 +++++++++++++++++++
 2 files changed, 43 insertions(+)
 create mode 100644 content/en/examples/access/validating-admission-policy-match-conditions.yaml

diff --git a/content/en/docs/reference/access-authn-authz/validating-admission-policy.md b/content/en/docs/reference/access-authn-authz/validating-admission-policy.md
index 2bf6610eebd..d30c5206b5b 100644
--- a/content/en/docs/reference/access-authn-authz/validating-admission-policy.md
+++ b/content/en/docs/reference/access-authn-authz/validating-admission-policy.md
@@ -365,3 +365,24 @@ HTTP response code, are used in the HTTP response to the client.
 The currently supported reasons are: `Unauthorized`, `Forbidden`, `Invalid`, `RequestEntityTooLarge`.
 If not set, `StatusReasonInvalid` is used in the response to the client.
 
+### Matching requests: `matchConditions`
+
+You can define _match conditions_ for a `ValidatingAdmissionPolicy` if you need fine-grained request filtering. These
+conditions are useful if you find that match rules, `objectSelectors` and `namespaceSelectors` still
+doesn't provide the filtering you want. Match conditions are
+[CEL expressions](/docs/reference/using-api/cel/). All match conditions must evaluate to true for the
+resource to be evaluated.
+
+Here is an example illustrating a few different uses for match conditions:
+
+{{< codenew file="access/validating-admission-policy-match-conditions.yaml" >}}
+
+Match conditions have access to the same CEL variables as validation expressions.
+
+In the event of an error evaluating a match condition the policy is not evaluated. Whether to reject
+the request is determined as follows:
+
+1. If **any** match condition evaluated to `false` (regardless of other errors), the API server skips the policy.
+2. Otherwise:
+  - for [`failurePolicy: Fail`](#failure-policy), reject the request (without evaluating the policy).
+  - for [`failurePolicy: Ignore`](#failure-policy), proceed with the request but skip the policy.
diff --git a/content/en/examples/access/validating-admission-policy-match-conditions.yaml b/content/en/examples/access/validating-admission-policy-match-conditions.yaml
new file mode 100644
index 00000000000..77d0dd61867
--- /dev/null
+++ b/content/en/examples/access/validating-admission-policy-match-conditions.yaml
@@ -0,0 +1,22 @@
+apiVersion: admissionregistration.k8s.io/v1alpha1
+kind: ValidatingAdmissionPolicy
+metadata:
+  name: "demo-policy.example.com"
+spec:
+  failurePolicy: Fail
+  matchConstraints:
+    resourceRules:
+      - apiGroups:   ["*"]
+        apiVersions: ["*"]
+        operations:  ["CREATE", "UPDATE"]
+        resources:   ["*"]
+  matchConditions:
+    - name: 'exclude-leases' # Each match condition must have a unique name
+      expression: '!(request.resource.group == "coordination.k8s.io" && request.resource.resource == "leases")' # Match non-lease resources.
+    - name: 'exclude-kubelet-requests'
+      expression: '!("system:nodes" in request.userInfo.groups)' # Match requests made by non-node users.
+    - name: 'rbac' # Skip RBAC requests.
+      expression: 'request.resource.group != "rbac.authorization.k8s.io"'
+  validations:
+    - expression: "object.metadata.name.startWith('demo')"
+

From 350ce035a53ee85a99b84264dd76c92d3a511b20 Mon Sep 17 00:00:00 2001
From: Cici Huang <cicih@google.com>
Date: Wed, 22 Mar 2023 20:14:36 +0000
Subject: [PATCH 043/272] Fix previous virables in exampes

---
 .../validating-admission-policy.md                   | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/content/en/docs/reference/access-authn-authz/validating-admission-policy.md b/content/en/docs/reference/access-authn-authz/validating-admission-policy.md
index d30c5206b5b..6342fd3994e 100644
--- a/content/en/docs/reference/access-authn-authz/validating-admission-policy.md
+++ b/content/en/docs/reference/access-authn-authz/validating-admission-policy.md
@@ -323,12 +323,12 @@ For example, `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')`           |
+|property name    | rule with escaped property name   |
+| ----------------|-----------------------------------|
+| namespace       | `object.__namespace__ > 0`        |
+| x-prop          | `object.x__dash__prop > 0`          |
+| redact__d       | `object.redact__underscores__d > 0` |
+| string          | `object.startsWith('kube')`         |
 	
 Equality on arrays with 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:

From 1ee260fea500d7d2d51af94e7ea06874a89f847b Mon Sep 17 00:00:00 2001
From: Mickey Boxell <mickey.boxell@oracle.com>
Date: Wed, 22 Mar 2023 15:24:08 -0500
Subject: [PATCH 044/272] Updated config.toml for 1.27 release

---
 hugo.toml | 38 +++++++++++++++++++-------------------
 1 file changed, 19 insertions(+), 19 deletions(-)

diff --git a/hugo.toml b/hugo.toml
index c34cfa20d27..796630004c9 100644
--- a/hugo.toml
+++ b/hugo.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.26"
+latest = "v1.27"
 
-fullversion = "v1.26.0"
-version = "v1.26"
+fullversion = "v1.27.0"
+version = "v1.27"
 githubbranch = "main"
 docsbranch = "main"
 deprecated = false
@@ -181,40 +181,40 @@ js = [
 ]
 
 [[params.versions]]
-fullversion = "v1.26.0"
-version = "v1.26"
-githubbranch = "v1.26.0"
+fullversion = "v1.27.0"
+version = "v1.27"
+githubbranch = "v1.27.0"
 docsbranch = "main"
 url = "https://kubernetes.io"
 
 [[params.versions]]
-fullversion = "v1.25.5"
+fullversion = "v1.26.3"
+version = "v1.26"
+githubbranch = "v1.26.3"
+docsbranch = "release-1.26"
+url = "https://v1-26.docs.kubernetes.io"
+
+[[params.versions]]
+fullversion = "v1.25.8"
 version = "v1.25"
-githubbranch = "v1.25.5"
+githubbranch = "v1.25.8"
 docsbranch = "release-1.25"
 url = "https://v1-25.docs.kubernetes.io"
 
 [[params.versions]]
-fullversion = "v1.24.9"
+fullversion = "v1.24.12"
 version = "v1.24"
-githubbranch = "v1.24.9"
+githubbranch = "v1.24.12"
 docsbranch = "release-1.24"
 url = "https://v1-24.docs.kubernetes.io"
 
 [[params.versions]]
-fullversion = "v1.23.15"
+fullversion = "v1.23.17"
 version = "v1.23"
-githubbranch = "v1.23.15"
+githubbranch = "v1.23.17"
 docsbranch = "release-1.23"
 url = "https://v1-23.docs.kubernetes.io"
 
-[[params.versions]]
-fullversion = "v1.22.17"
-version = "v1.22"
-githubbranch = "v1.22.17"
-docsbranch = "release-1.22"
-url = "https://v1-22.docs.kubernetes.io"
-
 # User interface configuration
 [params.ui]
 # Enable to show the side bar menu in its compact state.

From d9a2c85ba53f4cc5aece5605b7d8cff8297674de Mon Sep 17 00:00:00 2001
From: Cici Huang <cicih@google.com>
Date: Wed, 22 Mar 2023 20:29:16 +0000
Subject: [PATCH 045/272] Update example expression

---
 .../access/validating-admission-policy-match-conditions.yaml    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/examples/access/validating-admission-policy-match-conditions.yaml b/content/en/examples/access/validating-admission-policy-match-conditions.yaml
index 77d0dd61867..9a49adf1521 100644
--- a/content/en/examples/access/validating-admission-policy-match-conditions.yaml
+++ b/content/en/examples/access/validating-admission-policy-match-conditions.yaml
@@ -18,5 +18,5 @@ spec:
     - name: 'rbac' # Skip RBAC requests.
       expression: 'request.resource.group != "rbac.authorization.k8s.io"'
   validations:
-    - expression: "object.metadata.name.startWith('demo')"
+    - expression: "!object.metadata.name.contains('demo') || object.metadata.namespace == 'demo'"
 

From ee72c5485320b316faa31fce62b01d9fd0b04297 Mon Sep 17 00:00:00 2001
From: ruiwen-zhao <ruiwen@google.com>
Date: Tue, 14 Mar 2023 18:36:03 +0000
Subject: [PATCH 046/272] Document update for MaxParallelImagePulls

Signed-off-by: ruiwen-zhao <ruiwen@google.com>
---
 content/en/docs/concepts/containers/images.md | 42 +++++++++++++++++++
 1 file changed, 42 insertions(+)

diff --git a/content/en/docs/concepts/containers/images.md b/content/en/docs/concepts/containers/images.md
index 6e00eb46b67..247c8309d9e 100644
--- a/content/en/docs/concepts/containers/images.md
+++ b/content/en/docs/concepts/containers/images.md
@@ -157,6 +157,48 @@ that Kubernetes will keep trying to pull the image, with an increasing back-off
 Kubernetes raises the delay between each attempt until it reaches a compiled-in limit,
 which is 300 seconds (5 minutes).
 
+## Serial and parallel image pulls
+
+By default, kubelet pulls images serially. In other words, kubelet sends only
+one image pull request to the image service at a time. Other image pull requests
+have to wait until the one being processed is complete.
+
+Nodes make image pull decisions in isolation. Even when you use serialized image
+pulls, two different nodes can pull the same image in parallel.
+
+If you would like to enable parallel image pulls, you can set the field
+`serializeImagePulls` to false in the [kubelet configuration](/docs/reference/config-api/kubelet-config.v1beta1/).
+With `serializeImagePulls` set to false, image pull requests will be sent to the image service immediately,
+and multiple images will be pulled at the same time.
+
+When enabling parallel image pulls, please make sure the image service of your
+container runtime can handle parallel image pulls.
+
+The kubelet never pulls multiple images in parallel on behalf of one Pod. For example,
+if you have a Pod that has an init container and an application container, the image
+pulls for the two containers will not be parallelized. However, if you have two
+Pods that use different images, the kubelet pulls the images in parallel on
+behalf of the two different Pods, when parallel image pulls is enabled.
+
+### Maximum parallel image pulls
+
+{{< feature-state for_k8s_version="v1.27" state="alpha" >}}
+
+When `serializeImagePulls` is set to false, the kubelet defaults to no limit on the
+maximum number of images being pulled at the same time. If you would like to
+limit the number of parallel image pulls, you can set the field `maxParallelImagePulls`
+in kubelet configuration. With `maxParallelImagePulls` set to _n_, only _n_ images
+can be pulled at the same time, and any image pull beyond _n_ will have to wait
+until at least one ongoing image pull is complete.
+
+Limiting the number parallel image pulls would prevent image pulling from consuming
+too much network bandwidth or disk I/O, when parallel image pulling is enabled.
+
+You can set `maxParallelImagePulls` to a positive number that is greater than or
+equal to 1. If you set `maxParallelImagePulls` to be greater than or equal to 2, you
+must set the `serializeImagePulls` to false. The kubelet will fail to start with invalid
+`maxParallelImagePulls` settings.
+
 ## Multi-architecture images with image indexes
 
 As well as providing binary images, a container registry can also serve a

From ea3b7b44e7d010f1c59c3416e78d4533b5b8ba88 Mon Sep 17 00:00:00 2001
From: Humble Chirammal <humble.devassy@gmail.com>
Date: Wed, 15 Mar 2023 20:30:15 +0530
Subject: [PATCH 047/272] KEP-3107 update docs for csiNodeExpand secret support

This feature has moved to Beta in this release. The documentation
has been updated to reflect the same.

Signed-off-by: Humble Chirammal <humble.devassy@gmail.com>
---
 content/en/docs/concepts/storage/volumes.md                | 7 +++++--
 .../command-line-tools-reference/feature-gates.md          | 3 ++-
 .../docs/reference/command-line-tools-reference/kubelet.md | 2 +-
 3 files changed, 8 insertions(+), 4 deletions(-)

diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md
index 80f259aab31..e28532d90b2 100644
--- a/content/en/docs/concepts/storage/volumes.md
+++ b/content/en/docs/concepts/storage/volumes.md
@@ -1168,10 +1168,13 @@ persistent volume:
   secrets are passed.  When you have configured secret data for node-initiated
   volume expansion, the kubelet passes that data via the `NodeExpandVolume()`
   call to the CSI driver. In order to use the `nodeExpandSecretRef` field, your
-  cluster should be running Kubernetes version 1.25 or later and you must enable
+  cluster should be running Kubernetes version 1.25 or later.
+* If you are running Kubernetes Version 1.25 or 1.26, you must enable
   the [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
   named `CSINodeExpandSecret` for each kube-apiserver and for the kubelet on every
-  node. You must also be using a CSI driver that supports or requires secret data during
+  node. In Kubernetes version 1.27 this feature has been enabled by default
+  and no explicit enablement of the feature gate is required.
+  You must also be using a CSI driver that supports or requires secret data during
   node-initiated storage resize operations.
 * `nodePublishSecretRef`: A reference to the secret object containing
   sensitive information to pass to the CSI driver to complete the CSI
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 626cc6931f6..70a2ca815a4 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
@@ -77,7 +77,8 @@ For a reference to old feature gates that are removed, please refer to
 | `CSIMigrationPortworx` | `false` | Alpha | 1.23 | 1.24 |
 | `CSIMigrationPortworx` | `false` | Beta | 1.25 | |
 | `CSIMigrationRBD` | `false` | Alpha | 1.23 | |
-| `CSINodeExpandSecret` | `false` | Alpha | 1.25 | |
+| `CSINodeExpandSecret` | `false` | Alpha | 1.25 | 1.26 |
+| `CSINodeExpandSecret` | `true` | Beta | 1.27 | |
 | `CSIVolumeHealth` | `false` | Alpha | 1.21 | |
 | `ComponentSLIs` | `false` | Alpha | 1.26 | |
 | `ContainerCheckpoint` | `false` | Alpha | 1.25 | |
diff --git a/content/en/docs/reference/command-line-tools-reference/kubelet.md b/content/en/docs/reference/command-line-tools-reference/kubelet.md
index f0ecdb0b7ff..deb186ec5f6 100644
--- a/content/en/docs/reference/command-line-tools-reference/kubelet.md
+++ b/content/en/docs/reference/command-line-tools-reference/kubelet.md
@@ -381,7 +381,7 @@ CPUManagerPolicyBetaOptions=true|false (BETA - default=true)<br/>
 CPUManagerPolicyOptions=true|false (BETA - default=true)<br/>
 CSIMigrationPortworx=true|false (BETA - default=false)<br/>
 CSIMigrationRBD=true|false (ALPHA - default=false)<br/>
-CSINodeExpandSecret=true|false (ALPHA - default=false)<br/>
+CSINodeExpandSecret=true|false (BETA - default=true)<br/>
 CSIVolumeHealth=true|false (ALPHA - default=false)<br/>
 ComponentSLIs=true|false (ALPHA - default=false)<br/>
 ContainerCheckpoint=true|false (ALPHA - default=false)<br/>

From 35c0ef2431bafd9cbf2b650b02d048c4e645f2cc Mon Sep 17 00:00:00 2001
From: Antonio Ojea <aojea@google.com>
Date: Thu, 23 Mar 2023 11:08:09 +0000
Subject: [PATCH 048/272] address comments and fix one bug

---
 .../feature-gates.md                          |  3 +--
 .../docs/reference/networking/virtual-ips.md  | 22 ++++++++++++-------
 2 files changed, 15 insertions(+), 10 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 95151f0e27c..8a60fb989ff 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
@@ -626,8 +626,7 @@ Each feature gate is designed for enabling/disabling a specific feature:
 - `MixedProtocolLBService`: Enable using different protocols in the same `LoadBalancer` type
   Service instance.
 - `MultiCIDRRangeAllocator`: Enables the MultiCIDR range allocator.
-- `MultiCIDRServiceAllocator`: Enables a new IPAddress object kind, and a new Service ClusterIP allocator.
-  The new allocator removes previous Service CIDR block size limitations for IPv4, and limits IPv6 size to a /64.
+- `MultiCIDRServiceAllocator`: Track IP address allocations for Service cluster IPs using IPAddress objects.
 - `NetworkPolicyEndPort`: Enable use of the field `endPort` in NetworkPolicy objects,
   allowing the selection of a port range instead of a single port.
 - `NetworkPolicyStatus`: Enable the `status` subresource for NetworkPolicy objects.
diff --git a/content/en/docs/reference/networking/virtual-ips.md b/content/en/docs/reference/networking/virtual-ips.md
index 32ff8626f0e..555d3c8ea59 100644
--- a/content/en/docs/reference/networking/virtual-ips.md
+++ b/content/en/docs/reference/networking/virtual-ips.md
@@ -271,25 +271,21 @@ When clients connect to the VIP, their traffic is automatically transported to a
 appropriate endpoint. The environment variables and DNS for Services are actually
 populated in terms of the Service's virtual IP address (and port).
 
-{{< feature-state for_k8s_version="v1.27" state="alpha" >}}
-If you enable the `MultiCIDRServiceAllocator`
-[feature gate](/docs/reference/command-line-tools-reference/feature-gates/),
-the `ClusterIP` address associated to each `Service` will have a referenced
-`IPAddress` object.
-
 ### Avoiding collisions
 
 One of the primary philosophies of Kubernetes is that you should not be
 exposed to situations that could cause your actions to fail through no fault
 of your own. For the design of the Service resource, this means not making
-you choose your own port number if that choice might collide with
+you choose your own IP address if that choice might collide with
 someone else's choice.  That is an isolation failure.
 
-In order to allow you to choose a port number for your Services, we must
+In order to allow you to choose an IP address for your Services, we must
 ensure that no two Services can collide. Kubernetes does that by allocating each
 Service its own IP address from within the `service-cluster-ip-range`
 CIDR range that is configured for the {{< glossary_tooltip term_id="kube-apiserver" text="API Server" >}}.
 
+#### IP address allocation tracking
+
 To ensure each Service receives a unique IP, an internal allocator atomically
 updates a global allocation map in {{< glossary_tooltip term_id="etcd" >}}
 prior to creating each Service. The map object must exist in the registry for
@@ -302,6 +298,16 @@ in-memory locking). Kubernetes also uses controllers to check for invalid
 assignments (e.g. due to administrator intervention) and for cleaning up allocated
 IP addresses that are no longer used by any Services.
 
+{{< feature-state for_k8s_version="v1.27" state="alpha" >}}
+If you enable the `MultiCIDRServiceAllocator`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/),
+the control plane replaces the existing etcd allocator with a new one, using IPAddress
+objects instead of an internal global allocation map.  The ClusterIP address
+associated to each `Service` will have a referenced IPAddress object.
+
+The background allocator is also replaced by a new one to handle the new IPAddress
+objects and the migration from the old allocator model.
+
 #### IP address ranges for Service virtual IP addresses {#service-ip-static-sub-range}
 
 {{< feature-state for_k8s_version="v1.25" state="beta" >}}

From 278215cfbac4f42507ba71bfd8911a0e80878fa9 Mon Sep 17 00:00:00 2001
From: Antonio Ojea <aojea@google.com>
Date: Thu, 23 Mar 2023 11:24:06 +0000
Subject: [PATCH 049/272] expand on the use of IPAddress

---
 .../docs/reference/networking/virtual-ips.md  | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/content/en/docs/reference/networking/virtual-ips.md b/content/en/docs/reference/networking/virtual-ips.md
index 555d3c8ea59..c4d13d37ecd 100644
--- a/content/en/docs/reference/networking/virtual-ips.md
+++ b/content/en/docs/reference/networking/virtual-ips.md
@@ -308,6 +308,25 @@ associated to each `Service` will have a referenced IPAddress object.
 The background allocator is also replaced by a new one to handle the new IPAddress
 objects and the migration from the old allocator model.
 
+One of the main benefits of the new allocator is that it removes the size limitations
+for the `service-cluster-ip-range`, there is no limitations for IPv4 and for IPv6
+users can use masks equal or larger than /64 (previously it was /108).
+
+Users now will be able to inspect the IP addresses assigned to their Services, and
+new network APIs, like Gateway API, can use this new object to extend the Kubernetes
+networking capabilities overcoming the limitations of current Services API.
+
+```bash
+$ kubectl get services
+NAME         TYPE        CLUSTER-IP        EXTERNAL-IP   PORT(S)   AGE
+kubernetes   ClusterIP   2001:db8:1:2::1   <none>        443/TCP   3d1h
+
+$ kubectl get ipaddresses
+NAME              PARENTREF
+2001:db8:1:2::1   services/default/kubernetes
+2001:db8:1:2::a   services/kube-system/kube-dns
+```
+
 #### IP address ranges for Service virtual IP addresses {#service-ip-static-sub-range}
 
 {{< feature-state for_k8s_version="v1.25" state="beta" >}}

From a4a4d453ec34beb0d32d7fe5236bd064b8c714e1 Mon Sep 17 00:00:00 2001
From: Antonio Ojea <antonio.ojea.garcia@gmail.com>
Date: Thu, 23 Mar 2023 15:58:17 +0000
Subject: [PATCH 050/272] Update
 content/en/docs/reference/networking/virtual-ips.md

---
 content/en/docs/reference/networking/virtual-ips.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/reference/networking/virtual-ips.md b/content/en/docs/reference/networking/virtual-ips.md
index c4d13d37ecd..a33b08da067 100644
--- a/content/en/docs/reference/networking/virtual-ips.md
+++ b/content/en/docs/reference/networking/virtual-ips.md
@@ -305,7 +305,7 @@ the control plane replaces the existing etcd allocator with a new one, using IPA
 objects instead of an internal global allocation map.  The ClusterIP address
 associated to each `Service` will have a referenced IPAddress object.
 
-The background allocator is also replaced by a new one to handle the new IPAddress
+The background controller is also replaced by a new one to handle the new IPAddress
 objects and the migration from the old allocator model.
 
 One of the main benefits of the new allocator is that it removes the size limitations

From bd64321a1857a2905ef79eda30bebb990bcf59d1 Mon Sep 17 00:00:00 2001
From: Kensei Nakada <handbomusic@gmail.com>
Date: Sat, 4 Mar 2023 14:11:52 +0900
Subject: [PATCH 051/272] add general section

---
 .../2023-04-11-topology-spread-features.md    | 43 +++++++++++++++++++
 1 file changed, 43 insertions(+)
 create mode 100644 content/en/blog/_posts/2023-04-11-topology-spread-features.md

diff --git a/content/en/blog/_posts/2023-04-11-topology-spread-features.md b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
new file mode 100644
index 00000000000..8d38440562c
--- /dev/null
+++ b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
@@ -0,0 +1,43 @@
+---
+layout: blog
+title: "TBD" // TODO: have a cool title.
+date: 2023-04-11
+slug: topology-spread-new-features
+evergreen: true
+---
+
+**Authors:** [Alex Wang](https://github.com/denkensk)(), [Kante Yin](https://github.com/kerthcet)(), [Kensei Nakada](https://github.com/sanposhiho)(Mercari)
+
+In Kubernetes v1.19, [Pod Topology Spread Constraints](https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/) went to GA. 
+It is the feature to control how Pods are spread to each failure-domain (regions, zones, nodes etc).
+
+As time passes, we've got further feedbacks from users,
+and we're actively working on improving the Topology Spread via three KEPs from v1.25.
+All of these features have reached beta in Kubernetes v1.27 and been enabled by default.
+
+This blog post is going to introduce each feature and the usecase/issue behind them.
+
+## KEP-3022: min domains in Pod Topology Spread
+
+TODO(sanposhiho): write it
+
+## KEP-3094: Take taints/tolerations into consideration when calculating PodTopologySpread skew
+
+TODO(kerthcet): write it
+
+## KEP-3243: Respect PodTopologySpread after rolling upgrades
+
+TODO(denkensk): write it
+
+## Getting involved 
+
+These features are managed by the [SIG/Scheduling](https://github.com/kubernetes/community/tree/master/sig-scheduling). 
+
+Please join us and share your feedback. We look forward to hearing from you!
+
+## How can I learn more?
+
+- [Pod Topology Spread Constraints | Kubernetes](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#container-resource-metrics)
+- [KEP-3022: min domains in Pod Topology Spread](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/3022-min-domains-in-pod-topology-spread)
+- [KEP-3094: Take taints/tolerations into consideration when calculating PodTopologySpread skew](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/3094-pod-topology-spread-considering-taints)
+- [KEP-3243: Respect PodTopologySpread after rolling upgrades](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/3243-respect-pod-topology-spread-after-rolling-upgrades)
\ No newline at end of file

From bd847326ad3febdf496104779b5c315c9c778000 Mon Sep 17 00:00:00 2001
From: "Mr. Erlison" <sisal.cordame_0a@icloud.com>
Date: Sat, 25 Mar 2023 09:47:44 -0300
Subject: [PATCH 052/272] Add pt-br/docs/reference/glossary/daemonset.md

---
 .../pt-br/docs/reference/glossary/daemonset.md | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
 create mode 100644 content/pt-br/docs/reference/glossary/daemonset.md

diff --git a/content/pt-br/docs/reference/glossary/daemonset.md b/content/pt-br/docs/reference/glossary/daemonset.md
new file mode 100644
index 00000000000..ab93250efde
--- /dev/null
+++ b/content/pt-br/docs/reference/glossary/daemonset.md
@@ -0,0 +1,18 @@
+---
+title: DaemonSet
+id: daemonset
+date: 2018-04-12
+full_link: /docs/concepts/workloads/controllers/daemonset
+short_description: >
+  Garante que uma cópia de um Pod esteja sendo executada em um conjunto de nós em um cluster.
+
+aka: 
+tags:
+- fundamental
+- core-object
+- workload
+---
+ Garante que uma cópia de um {{< glossary_tooltip text="Pod" term_id="pod" >}} esteja sendo executada em um conjunto de nós em um {{< glossary_tooltip text="cluster" term_id="cluster" >}}.
+<!--more--> 
+
+Usado para instalar daemons do sistema como coletores de log e agentes de monitoramento que normalmente devem ser executados em todos os {{< glossary_tooltip text="nós" term_id="node" >}}.
\ No newline at end of file

From c3d698a44370012c5f691c4dc9e82446fd94fe80 Mon Sep 17 00:00:00 2001
From: Han Kang <hankang@google.com>
Date: Sun, 26 Mar 2023 09:41:54 -0700
Subject: [PATCH 053/272] update APIServerTracing docs

---
 .../concepts/cluster-administration/system-traces.md   | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/content/en/docs/concepts/cluster-administration/system-traces.md b/content/en/docs/concepts/cluster-administration/system-traces.md
index 04bd58ce38b..e43def4436a 100644
--- a/content/en/docs/concepts/cluster-administration/system-traces.md
+++ b/content/en/docs/concepts/cluster-administration/system-traces.md
@@ -9,7 +9,7 @@ weight: 90
 
 <!-- overview -->
 
-{{< feature-state for_k8s_version="v1.22" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
 
 System component traces record the latency of and relationships between operations in the cluster.
 
@@ -59,14 +59,12 @@ as the kube-apiserver is often a public endpoint.
 
 #### Enabling tracing in the kube-apiserver
 
-To enable tracing, enable the `APIServerTracing`
-[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
-on the kube-apiserver. Also, provide the kube-apiserver with a tracing configuration file
+To enable tracing, provide the kube-apiserver with a tracing configuration file
 with `--tracing-config-file=<path-to-config>`. This is an example config that records
 spans for 1 in 10000 requests, and uses the default OpenTelemetry endpoint:
 
 ```yaml
-apiVersion: apiserver.config.k8s.io/v1alpha1
+apiVersion: apiserver.config.k8s.io/v1beta1
 kind: TracingConfiguration
 # default value
 #endpoint: localhost:4317
@@ -74,7 +72,7 @@ samplingRatePerMillion: 100
 ```
 
 For more information about the `TracingConfiguration` struct, see
-[API server config API (v1alpha1)](/docs/reference/config-api/apiserver-config.v1alpha1/#apiserver-k8s-io-v1alpha1-TracingConfiguration).
+[API server config API (v1beta1)](/docs/reference/config-api/apiserver-config.v1beta1/#apiserver-k8s-io-v1beta1-TracingConfiguration).
 
 ### kubelet traces
 

From e07c3d66b8552f6b61081c2806cf2de748af5780 Mon Sep 17 00:00:00 2001
From: Rodrigo Campos <rodrigoca@microsoft.com>
Date: Mon, 27 Mar 2023 12:48:00 +0200
Subject: [PATCH 054/272] content: Remove "new" keyword in user namespaces docs

While we are there, we also change pod.spec to pod spec.

Signed-off-by: Rodrigo Campos <rodrigoca@microsoft.com>
---
 .../en/docs/tasks/configure-pod-container/user-namespaces.md  | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/en/docs/tasks/configure-pod-container/user-namespaces.md b/content/en/docs/tasks/configure-pod-container/user-namespaces.md
index 96e1ff2d01a..6c4c01234cb 100644
--- a/content/en/docs/tasks/configure-pod-container/user-namespaces.md
+++ b/content/en/docs/tasks/configure-pod-container/user-namespaces.md
@@ -50,8 +50,8 @@ to use this feature with Kubernetes stateless pods:
 * CRI-O: v1.25 has support for user namespaces.
 
 Please note that **if your container runtime doesn't support user namespaces, the
-new `pod.spec` field will be silently ignored and the pod will be created without
-user namespaces.**
+`hostUsers` field in the pod spec will be silently ignored and the pod will be
+created without user namespaces.**
 
 <!-- steps -->
 

From 3648d983c6a227f7496fff4d0c8ff01d851ee6f8 Mon Sep 17 00:00:00 2001
From: Sascha Grunert <sgrunert@redhat.com>
Date: Fri, 10 Mar 2023 08:24:51 +0100
Subject: [PATCH 055/272] [KEP-2413] Add docs for SeccompDefault graduation

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
---
 .../feature-gates.md                          |  5 ++--
 content/en/docs/tutorials/security/seccomp.md | 23 +++++++------------
 2 files changed, 11 insertions(+), 17 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 96fd5d7937c..b405731b796 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
@@ -179,8 +179,6 @@ For a reference to old feature gates that are removed, please refer to
 | `RotateKubeletServerCertificate` | `false` | Alpha | 1.7 | 1.11 |
 | `RotateKubeletServerCertificate` | `true` | Beta | 1.12 | |
 | `SELinuxMountReadWriteOncePod` | `false` | Alpha | 1.25 | |
-| `SeccompDefault` | `false` | Alpha | 1.22 | 1.24 |
-| `SeccompDefault` | `true` | Beta | 1.25 | |
 | `ServiceNodePortStaticSubrange` | `false` | Alpha | 1.27 | |
 | `SizeMemoryBackedVolumes` | `false` | Alpha | 1.20 | 1.21 |
 | `SizeMemoryBackedVolumes` | `true` | Beta | 1.22 | |
@@ -308,6 +306,9 @@ For a reference to old feature gates that are removed, please refer to
 | `RemoveSelfLink` | `false` | Alpha | 1.16 | 1.19 |
 | `RemoveSelfLink` | `true` | Beta | 1.20 | 1.23 |
 | `RemoveSelfLink` | `true` | GA | 1.24 | - |
+| `SeccompDefault` | `false` | Alpha | 1.22 | 1.24 |
+| `SeccompDefault` | `true` | Beta | 1.25 | 1.26 |
+| `SeccompDefault` | `true` | GA | 1.27 | - |
 | `ServerSideApply` | `false` | Alpha | 1.14 | 1.15 |
 | `ServerSideApply` | `true` | Beta | 1.16 | 1.21 |
 | `ServerSideApply` | `true` | GA | 1.22 | - |
diff --git a/content/en/docs/tutorials/security/seccomp.md b/content/en/docs/tutorials/security/seccomp.md
index bc94348f25f..7db5ffe6d3f 100644
--- a/content/en/docs/tutorials/security/seccomp.md
+++ b/content/en/docs/tutorials/security/seccomp.md
@@ -156,14 +156,12 @@ running within kind.
 
 ## Enable the use of `RuntimeDefault` as the default seccomp profile for all workloads
 
-{{< feature-state state="beta" for_k8s_version="v1.25" >}}
+{{< feature-state state="stable" for_k8s_version="v1.27" >}}
 
-To use seccomp profile defaulting, you must run the kubelet with the `SeccompDefault`
-[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) enabled
-(this is the default). You must also explicitly enable the defaulting behavior for each
-node where you want to use this with the corresponding `--seccomp-default`
-[command line flag](/docs/reference/command-line-tools-reference/kubelet).
-Both have to be enabled simultaneously to use the feature.
+To use seccomp profile defaulting, you must run the kubelet with the
+`--seccomp-default`
+[command line flag](/docs/reference/command-line-tools-reference/kubelet)
+enabled for each node where you want to use it. 
 
 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.
@@ -200,10 +198,8 @@ in the related Kubernetes Enhancement Proposal (KEP):
 
 Kubernetes {{< skew currentVersion >}} lets you configure the seccomp profile
 that applies when the spec for a Pod doesn't define a specific seccomp profile.
-This is a beta feature and the corresponding `SeccompDefault` [feature
-gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled by
-default. However, you still need to enable this defaulting for each node where
-you would like to use it.
+However, you still need to enable this defaulting for each node where you would
+like to use it.
 
 If you are running a Kubernetes {{< skew currentVersion >}} cluster and want to
 enable the feature, either run the kubelet with the `--seccomp-default` command
@@ -216,8 +212,6 @@ the minimum required Kubernetes version and enables the `SeccompDefault` feature
 ```yaml
 kind: Cluster
 apiVersion: kind.x-k8s.io/v1alpha4
-featureGates:
-  SeccompDefault: true
 nodes:
   - role: control-plane
     image: kindest/node:v1.23.0@sha256:49824ab1727c04e56a21a5d8372a402fcd32ea51ac96a2706a12af38934f81ac
@@ -234,7 +228,6 @@ nodes:
         kind: JoinConfiguration
         nodeRegistration:
           kubeletExtraArgs:
-            feature-gates: SeccompDefault=true
             seccomp-default: "true"
 ```
 
@@ -272,7 +265,7 @@ 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/)
+If you have the `seccompDefault` [configuration](/docs/reference/config-api/kubelet-config.v1beta1/)
 enabled, then Pods use the `RuntimeDefault` seccomp profile whenever
 no other seccomp profile is specified. Otherwise, the default is `Unconfined`.
 {{< /note >}}

From 2bf6e39053df99dad850afbe20f599a9feac4ff2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Wojciech=20Tyczy=C5=84ski?= <wojtekt@google.com>
Date: Tue, 14 Mar 2023 09:48:14 +0100
Subject: [PATCH 056/272] Streaming lists documentation

---
 .../feature-gates.md                          |  2 +
 .../docs/reference/using-api/api-concepts.md  | 60 ++++++++++++++++++-
 2 files changed, 61 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 626cc6931f6..23059645567 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
@@ -205,6 +205,7 @@ For a reference to old feature gates that are removed, please refer to
 | `UserNamespacesStatelessPodsSupport` | `false` | Alpha | 1.25 | |
 | `ValidatingAdmissionPolicy` | `false` | Alpha | 1.26 | |
 | `VolumeCapacityPriority` | `false` | Alpha | 1.21 | - |
+| `WatchList` | false | Alpha | 1.27 | |
 | `WinDSR` | `false` | Alpha | 1.14 | |
 | `WinOverlay` | `false` | Alpha | 1.14 | 1.19 |
 | `WinOverlay` | `true` | Beta | 1.20 | |
@@ -729,6 +730,7 @@ Each feature gate is designed for enabling/disabling a specific feature:
 - `VolumeCapacityPriority`: Enable support for prioritizing nodes in different
   topologies based on available PV capacity.
 - `WatchBookmark`: Enable support for watch bookmark events.
+- `WatchList` : Enable support for [streaming initial state of objects in watch requests](/docs/reference/using-api/api-concepts/#streaming-lists).
 - `WinDSR`: Allows kube-proxy to create DSR loadbalancers for Windows.
 - `WinOverlay`: Allows kube-proxy to run in overlay mode for Windows.
 - `WindowsHostNetwork`: Enables support for joining Windows containers to a hosts' network namespace.
diff --git a/content/en/docs/reference/using-api/api-concepts.md b/content/en/docs/reference/using-api/api-concepts.md
index 3c7c0fa8ccb..7c2cc093714 100644
--- a/content/en/docs/reference/using-api/api-concepts.md
+++ b/content/en/docs/reference/using-api/api-concepts.md
@@ -195,7 +195,7 @@ For subscribing to collections, Kubernetes client libraries typically offer some
 of standard tool for this **list**-then-**watch** logic. (In the Go client library,
 this is called a `Reflector` and is located in the `k8s.io/client-go/tools/cache` package.)
 
-### Watch bookmarks
+### Watch bookmarks {#watch-bookmarks}
 
 To mitigate the impact of short history window, the Kubernetes API provides a watch
 event named `BOOKMARK`. It is a special kind of event to mark that all changes up
@@ -226,6 +226,64 @@ As a client, you can request `BOOKMARK` events by setting the
 assume bookmarks are returned at any specific interval, nor can clients assume that
 the API server will send any `BOOKMARK` event even when requested.
 
+## Streaming lists
+
+{{< feature-state for_k8s_version="v1.27" state="alpha" >}}
+
+On large clusters, retrieving the collection of some resource types may result in
+a significant increase of resource usage (primarily RAM) on the control plane.
+In order to alleviate its impact and simplify the user experience of the **list** + **watch**
+pattern, Kubernetes v1.27 introduces as an alpha feature the support
+for requesting the initial state (previously requested via the **list** request) as part of
+the **watch** request.
+
+Provided that the `WatchList` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+is enabled, this can be achieved by specifying `sendInitialEvents=true` as query string parameter
+in a **watch** request. If set, the API server starts the watch stream with synthetic init
+events (of type `ADDED`) to build the whole state of all existing objects followed by a
+[`BOOKMARK` event](/docs/reference/using-api/api-concepts/#watch-bookmarks)
+(if requested via `allowWatchBookmarks=true` option). The bookmark event includes the resource version
+to which is synced. After sending the bookmark event, the API server continues as for any other **watch**
+request.
+
+When you set `sendInitialEvents=true` in the query string, Kubernetes also requires that you set
+`resourceVersionMatch` to `NotOlderThan` value.
+If you provided `resourceVersion` in the query string without providing a value or don't provide
+it at all, this is interpreted as a request for _consistent read_;
+the bookmark event is sent when the state is synced at least to the moment of a consistent read
+from when the request started to be processed. If you specify `resourceVersion` (in the query string),
+the bookmark event is sent when the state is synced at least to the provided resource version.
+
+### Example {#example-streaming-lists}
+
+An example: you want to watch a collection of Pods. For that collection, the current resource version
+is 10245 and there are two pods: `foo` and `bar`. Then sending the following request (explicitly requesting
+_consistent read_ by setting empty resource version using `resourceVersion=`) could result
+in the following sequence of events:
+
+```console
+GET /api/v1/namespaces/test/pods?watch=1&sendInitialEvents=true&allowWatchBookmarks=true&resourceVersion=&resourceVersionMatch=NotOlderThan
+---
+200 OK
+Transfer-Encoding: chunked
+Content-Type: application/json
+
+{
+  "type": "ADDED",
+  "object": {"kind": "Pod", "apiVersion": "v1", "metadata": {"resourceVersion": "8467", "name": "foo"}, ...}
+}
+{
+  "type": "ADDED",
+  "object": {"kind": "Pod", "apiVersion": "v1", "metadata": {"resourceVersion": "5726", "name": "bar"}, ...}
+}
+{
+  "type": "BOOKMARK",
+  "object": {"kind": "Pod", "apiVersion": "v1", "metadata": {"resourceVersion": "10245"} }
+}
+...
+<followed by regular watch stream starting from resourceVersion="10245">
+```
+
 ## Retrieving large results sets in chunks
 
 {{< feature-state for_k8s_version="v1.9" state="beta" >}}

From 66906fd6e68a6e5f1875691fe1e2dd1c2ae840b5 Mon Sep 17 00:00:00 2001
From: Han Kang <hankang@google.com>
Date: Mon, 27 Mar 2023 06:43:08 -0700
Subject: [PATCH 057/272] add tracing feature flag update

---
 .../reference/command-line-tools-reference/feature-gates.md    | 3 ++-
 1 file 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 96fd5d7937c..56c8782b450 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
@@ -65,7 +65,8 @@ For a reference to old feature gates that are removed, please refer to
 | `APISelfSubjectReview` | `false` | Alpha | 1.26 | |
 | `APIServerIdentity` | `false` | Alpha | 1.20 | 1.25 |
 | `APIServerIdentity` | `true` | Beta | 1.26 | |
-| `APIServerTracing` | `false` | Alpha | 1.22 | |
+| `APIServerTracing` | `false` | Alpha | 1.22 | 1.26 |
+| `APIServerTracing` | `true` | Beta | 1.27 | |
 | `AggregatedDiscoveryEndpoint` | `false` | Alpha | 1.26 | |
 | `AnyVolumeDataSource` | `false` | Alpha | 1.18 | 1.23 |
 | `AnyVolumeDataSource` | `true` | Beta | 1.24 | |

From a36e0381fe7417e7655fca71d07882ff82433dd5 Mon Sep 17 00:00:00 2001
From: Jefftree <jeffrey.ying86@live.com>
Date: Tue, 21 Mar 2023 21:52:01 +0000
Subject: [PATCH 058/272] Update OpenAPI V3 for GA

---
 .../en/docs/concepts/overview/kubernetes-api.md    | 14 ++++++--------
 .../command-line-tools-reference/feature-gates.md  |  5 +++--
 2 files changed, 9 insertions(+), 10 deletions(-)

diff --git a/content/en/docs/concepts/overview/kubernetes-api.md b/content/en/docs/concepts/overview/kubernetes-api.md
index 27e4829ba55..725d47778bd 100644
--- a/content/en/docs/concepts/overview/kubernetes-api.md
+++ b/content/en/docs/concepts/overview/kubernetes-api.md
@@ -82,17 +82,13 @@ packages that define the API objects.
 
 ### OpenAPI V3
 
-{{< feature-state state="beta"  for_k8s_version="v1.24" >}}
+{{< feature-state state="stable"  for_k8s_version="v1.27" >}}
 
-Kubernetes {{< param "version" >}} offers beta support for publishing its APIs as OpenAPI v3; this is a
-beta feature that is enabled by default.
-You can disable the beta feature by turning off the
-[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) named `OpenAPIV3`
-for the kube-apiserver component.
+Kubernetes {{< param "version" >}} offers stable support for publishing its APIs as OpenAPI v3.
 
 A discovery endpoint `/openapi/v3` is provided to see a list of all
-group/versions available. This endpoint only returns JSON. These group/versions
-are provided in the following format:
+group/versions available. This endpoint only returns JSON. These
+group/versions are provided in the following format:
 
 ```yaml
 {
@@ -153,6 +149,8 @@ Refer to the table below for accepted request headers.
   </tbody>
 </table>
 
+A golang implementation to fetch the OpenAPI V3 is provided in the package `k8s.io/client-go/openapi3`.
+
 ## Persistence
 
 Kubernetes stores the serialized state of objects by writing them into
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 08666007a13..719fce6f1bc 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
@@ -151,8 +151,6 @@ For a reference to old feature gates that are removed, please refer to
 | `NodeSwap` | `false` | Alpha | 1.22 | |
 | `OpenAPIEnums` | `false` | Alpha | 1.23 | 1.23 |
 | `OpenAPIEnums` | `true` | Beta | 1.24 | |
-| `OpenAPIV3` | `false` | Alpha | 1.23 | 1.23 |
-| `OpenAPIV3` | `true` | Beta | 1.24 | |
 | `PDBUnhealthyPodEvictionPolicy` | `false` | Alpha | 1.26 | |
 | `PodAndContainerStatsFromCRI` | `false` | Alpha | 1.23 | |
 | `PodDeletionCost` | `false` | Alpha | 1.21 | 1.21 |
@@ -315,6 +313,9 @@ For a reference to old feature gates that are removed, please refer to
 | `ServerSideFieldValidation` | `false` | Alpha | 1.23 | 1.24 |
 | `ServerSideFieldValidation` | `true` | Beta | 1.25 | 1.26 |
 | `ServerSideFieldValidation` | `true` | GA | 1.27 | - |
+| `OpenAPIV3` | `false` | Alpha | 1.23 | 1.23 |
+| `OpenAPIV3` | `true` | Beta | 1.24 | 1.26 |
+| `OpenAPIV3` | `true` | GA | 1.27 | - |
 | `ServiceIPStaticSubrange` | `false` | Alpha | 1.24 | 1.24 |
 | `ServiceIPStaticSubrange` | `true` | Beta | 1.25 | 1.25 |
 | `ServiceIPStaticSubrange` | `true` | GA | 1.26 | - |

From af3e11936b59660e2005c1b8600008e212638bee Mon Sep 17 00:00:00 2001
From: Jefftree <jeffrey.ying86@live.com>
Date: Tue, 21 Mar 2023 22:16:30 +0000
Subject: [PATCH 059/272] Update OpenAPI V3 section for CRDs

---
 .../custom-resources/custom-resource-definitions.md | 13 ++++++-------
 1 file changed, 6 insertions(+), 7 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 c439aa35dfd..4e08b9f1149 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
@@ -1346,19 +1346,19 @@ with `foo` pruned and defaulted because the field is non-nullable, `bar` maintai
 value due to `nullable: true`, and `baz` pruned because the field is non-nullable and has no
 default.
 
-### Publish Validation Schema in OpenAPI v2
+### Publish Validation Schema in OpenAPI
 
 CustomResourceDefinition [OpenAPI v3 validation schemas](#validation) which are
 [structural](#specifying-a-structural-schema) and [enable pruning](#field-pruning) are published
-as part of the [OpenAPI v2 spec](/docs/concepts/overview/kubernetes-api/#openapi-and-swagger-definitions)
-from Kubernetes API server.
+as [OpenAPI v3](/docs/concepts/overview/kubernetes-api/#openapi-and-swagger-definitions) and OpenAPI v2 from Kubernetes API server. It is recommended to use the OpenAPI v3 document as it is a lossless representation of the CustomResourceDefinition OpenAPI v3 validation schema while OpenAPI v2 represents a lossy conversion.
 
 The [kubectl](/docs/reference/kubectl/) command-line tool consumes the published schema to perform
 client-side validation (`kubectl create` and `kubectl apply`), schema explanation (`kubectl explain`)
 on custom resources. The published schema can be consumed for other purposes as well, like client generation or documentation.
 
-The OpenAPI v3 validation schema is converted to OpenAPI v2 schema, and
-show up in `definitions` and `paths` fields in the
+#### Compatibility with OpenAPI V2
+
+For compatibility with OpenAPI V2, the OpenAPI v3 validation schema performs a lossy conversion to the OpenAPI v2 schema. The schema show up in `definitions` and `paths` fields in the
 [OpenAPI v2 spec](/docs/concepts/overview/kubernetes-api/#openapi-and-swagger-definitions).
 
 The following modifications are applied during the conversion to keep backwards compatibility with
@@ -1366,8 +1366,7 @@ kubectl in previous 1.13 version. These modifications prevent kubectl from being
 valid OpenAPI schemas that it doesn't understand. The conversion won't modify the validation schema defined in CRD,
 and therefore won't affect [validation](#validation) in the API server.
 
-1. The following fields are removed as they aren't supported by OpenAPI v2
-   (in future versions OpenAPI v3 will be used without these restrictions)
+1. The following fields are removed as they aren't supported by OpenAPI v2.
 
    - The fields `allOf`, `anyOf`, `oneOf` and `not` are removed
 

From eb417b7128830a6035b59d09fccda62d115677a2 Mon Sep 17 00:00:00 2001
From: Jefftree <jeffrey.ying86@live.com>
Date: Tue, 21 Mar 2023 22:16:48 +0000
Subject: [PATCH 060/272] Whitespace fix

---
 .../custom-resource-definitions.md            | 33 +++++++++----------
 1 file changed, 16 insertions(+), 17 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 4e08b9f1149..de6106e50a4 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
@@ -765,7 +765,7 @@ For example:
         required:
           - minReplicas
           - replicas
-          - maxReplicas 
+          - maxReplicas
 ```
 
 will reject a request to create this custom resource:
@@ -788,7 +788,7 @@ The CronTab "my-new-cron-object" is invalid:
 * 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. 
+`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:
@@ -798,22 +798,22 @@ 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. 
+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.
- 
+
   For example, a rule like `self == true` against a field of integer type will get error:
 
   ```none
   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.
-  
+
   For example, a rule like `self.nonExistingField > 0` against a non-existing field will return
   the following error:
 
@@ -822,7 +822,7 @@ The compilation failure:
   ```
 
 - `invalid argument`: invalid argument to macros.
- 
+
   For example, a rule like `has(self)` will return error:
 
   ```none
@@ -961,7 +961,7 @@ Examples:
 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:
 
@@ -1007,7 +1007,7 @@ the list type:
 - `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:
 
@@ -1100,8 +1100,8 @@ estimated to be prohibitively expensive to execute, the API server rejects the c
 or update operation, and returns an error message.
 A similar system is used at runtime that observes the actions the interpreter takes. If the interpreter executes
 too many instructions, execution of the rule will be halted, and an error will result.
-Each CustomResourceDefinition is also allowed a certain amount of resources to finish executing all of 
-its validation rules. If the sum total of its rules are estimated at creation time to go over that limit, 
+Each CustomResourceDefinition is also allowed a certain amount of resources to finish executing all of
+its validation rules. If the sum total of its rules are estimated at creation time to go over that limit,
 then a validation error will also occur.
 
 You are unlikely to encounter issues with the resource budget for validation if you only
@@ -1114,7 +1114,7 @@ Another example would be if `foo` were an array, and you specified a validation
 The cost system always assumes the worst-case scenario if a limit on the length of `foo` is not
 given, and this will happen for anything that can be iterated over (lists, maps, etc.).
 
-Because of this, it is considered best practice to put a limit via `maxItems`, `maxProperties`, and 
+Because of this, it is considered best practice to put a limit via `maxItems`, `maxProperties`, and
 `maxLength` for anything that will be processed in a validation rule in order to prevent validation
 errors during cost estimation. For example, given this schema with one rule:
 
@@ -1133,8 +1133,8 @@ openAPIV3Schema:
 then the API server rejects this rule on validation budget grounds with error:
 
 ```
-spec.validation.openAPIV3Schema.properties[spec].properties[foo].x-kubernetes-validations[0].rule: Forbidden: 
-CEL rule exceeded budget by more than 100x (try simplifying the rule, or adding maxItems, maxProperties, and 
+spec.validation.openAPIV3Schema.properties[spec].properties[foo].x-kubernetes-validations[0].rule: Forbidden:
+CEL rule exceeded budget by more than 100x (try simplifying the rule, or adding maxItems, maxProperties, and
 maxLength where arrays, maps, and strings are used)
 ```
 
@@ -1177,7 +1177,7 @@ openAPIV3Schema:
         maxLength: 10
 ```
 
-If a list inside of a list has a validation rule that uses `self.all`, that is significantly more expensive 
+If a list inside of a list has a validation rule that uses `self.all`, that is significantly more expensive
 than a non-nested list with the same rule. A rule that would have been allowed on a non-nested list might need
 lower limits set on both nested lists in order to be allowed. For example, even without having limits set,
 the following rule is allowed:
@@ -1768,4 +1768,3 @@ crontabs/my-new-cron-object   3s
 
 * Serve [multiple versions](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/) of a
   CustomResourceDefinition.
-

From a67328526b958a365bf39f29484e3b49e715f227 Mon Sep 17 00:00:00 2001
From: Paco Xu <paco.xu@daocloud.io>
Date: Tue, 28 Mar 2023 10:42:07 +0800
Subject: [PATCH 061/272] update IdentifyPodOS as it is removed

---
 content/en/docs/concepts/windows/intro.md                 | 4 ----
 content/en/docs/concepts/windows/user-guide.md            | 4 ----
 .../command-line-tools-reference/feature-gates-removed.md | 8 ++++++++
 .../command-line-tools-reference/feature-gates.md         | 7 -------
 4 files changed, 8 insertions(+), 15 deletions(-)

diff --git a/content/en/docs/concepts/windows/intro.md b/content/en/docs/concepts/windows/intro.md
index 16a7ea3d8a1..19a9c2c7888 100644
--- a/content/en/docs/concepts/windows/intro.md
+++ b/content/en/docs/concepts/windows/intro.md
@@ -89,10 +89,6 @@ section refers to several key workload abstractions and how they map to Windows.
 
     The `.spec.os.name` field should be set to `windows` to indicate that the current Pod uses Windows containers.
 
-    {{< note >}}
-    Starting from 1.25, the `IdentifyPodOS` feature gate is in GA stage and defaults to be enabled.
-    {{< /note >}}
-
     If you set the `.spec.os.name` field to `windows`,
     you must not set the following fields in the `.spec` of that Pod:
 
diff --git a/content/en/docs/concepts/windows/user-guide.md b/content/en/docs/concepts/windows/user-guide.md
index df3306f01ab..53f78951efc 100644
--- a/content/en/docs/concepts/windows/user-guide.md
+++ b/content/en/docs/concepts/windows/user-guide.md
@@ -162,10 +162,6 @@ that the containers in that Pod are designed for. For Pods that run Linux contai
 `.spec.os.name` to `linux`. For Pods that run Windows containers, set `.spec.os.name`
 to `windows`.
 
-{{< note >}}
-Starting from 1.25, the `IdentifyPodOS` feature is in GA stage and defaults to be enabled.
-{{< /note >}}
-
 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/)
diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates-removed.md b/content/en/docs/reference/command-line-tools-reference/feature-gates-removed.md
index 67939e8e45b..50d1dd29bfc 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates-removed.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates-removed.md
@@ -169,6 +169,9 @@ In the following table:
 | `IPv6DualStack` | `false` | Alpha | 1.15 | 1.20 |
 | `IPv6DualStack` | `true` | Beta | 1.21 | 1.22 |
 | `IPv6DualStack` | `true` | GA | 1.23 | 1.24 |
+| `IdentifyPodOS` | `false` | Alpha | 1.23 | 1.23 |
+| `IdentifyPodOS` | `true` | Beta | 1.24 | 1.24 |
+| `IdentifyPodOS` | `true` | GA | 1.25 | 1.27 |
 | `ImmutableEphemeralVolumes` | `false` | Alpha | 1.18 | 1.18 |
 | `ImmutableEphemeralVolumes` | `true` | Beta | 1.19 | 1.20 |
 | `ImmutableEphemeralVolumes` | `true` | GA | 1.21 | 1.24 |
@@ -575,6 +578,11 @@ In the following table:
 - `IPv6DualStack`: Enable [dual stack](/docs/concepts/services-networking/dual-stack/)
   support for IPv6.
 
+- `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.
 
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 08666007a13..e90baeebcf6 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
@@ -282,9 +282,6 @@ For a reference to old feature gates that are removed, please refer to
 | `EphemeralContainers` | `true` | Beta | 1.23 | 1.24 |
 | `EphemeralContainers` | `true` | GA | 1.25 | - |
 | `ExecProbeTimeout` | `true` | GA | 1.20 | - |
-| `IdentifyPodOS` | `false` | Alpha | 1.23 | 1.23 |
-| `IdentifyPodOS` | `true` | Beta | 1.24 | 1.24 |
-| `IdentifyPodOS` | `true` | GA | 1.25 | - |
 | `JobTrackingWithFinalizers` | `false` | Alpha | 1.22 | 1.22 |
 | `JobTrackingWithFinalizers` | `false` | Beta | 1.23 | 1.24 |
 | `JobTrackingWithFinalizers` | `true` | Beta | 1.25 | 1.25 |
@@ -543,10 +540,6 @@ Each feature gate is designed for enabling/disabling a specific feature:
 - `HPAScaleToZero`: Enables setting `minReplicas` to 0 for `HorizontalPodAutoscaler`
   resources when using custom or external metrics.
 - `IPTablesOwnershipCleanup`: This causes kubelet to no longer create legacy iptables rules.
-- `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`.
 - `InTreePluginAWSUnregister`: Stops registering the aws-ebs in-tree plugin in kubelet
   and volume controllers.
 - `InTreePluginAzureDiskUnregister`: Stops registering the azuredisk in-tree plugin in kubelet

From 448e70ff20a0196c7bd57db45761f2b90a51112d Mon Sep 17 00:00:00 2001
From: Han Kang <hankang@google.com>
Date: Tue, 21 Mar 2023 09:05:25 -0700
Subject: [PATCH 062/272] add autogenerated documentation for metrics

---
 .../docs/reference/instrumentation/metrics.md | 1809 ++++++++++++-----
 1 file changed, 1310 insertions(+), 499 deletions(-)

diff --git a/content/en/docs/reference/instrumentation/metrics.md b/content/en/docs/reference/instrumentation/metrics.md
index 196c9b97d3e..0cc90d8d78e 100644
--- a/content/en/docs/reference/instrumentation/metrics.md
+++ b/content/en/docs/reference/instrumentation/metrics.md
@@ -1,18 +1,22 @@
 ---
 title: Kubernetes Metrics Reference
 content_type: reference
+auto_generated: true
 description: >-
   Details of the metric data that Kubernetes components export.
 ---
 
+## Metrics (v1.27)
 
-## Metrics (auto-generated 2022 Nov 01)
-
+<!-- (auto-generated 2023 Mar 16) -->
+<!-- (auto-generated v1.27) -->
 This page details the metrics that different Kubernetes components export. You can query the metrics endpoint for these 
 components using an HTTP scrape, and fetch the current metrics data in Prometheus format.
 
 ### List of Stable Kubernetes Metrics
 
+Stable metrics observe strict API contracts and no labels can be added or removed from stable metrics during their lifetime. 
+
 <table class="table metrics" caption="This is the list of STABLE metrics emitted from core Kubernetes components">
 <thead>
 	<tr>
@@ -22,6 +26,7 @@ components using an HTTP scrape, and fetch the current metrics data in Prometheu
 		<th class="metric_help">Help</th>
 		<th class="metric_labels">Labels</th>
 		<th class="metric_const_labels">Const Labels</th>
+		<th class="metric_deprecated_version">Deprecated Version</th>
 	</tr>
 </thead>
 <tbody>
@@ -31,126 +36,219 @@ components using an HTTP scrape, and fetch the current metrics data in Prometheu
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Admission controller latency histogram in seconds, identified by name and broken out for each operation and API resource and type (validate or admit).</td>
 <td class="metric_labels_varying"><div class="metric_label">name</div><div class="metric_label">operation</div><div class="metric_label">rejected</div><div class="metric_label">type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_admission_step_admission_duration_seconds</td>
 <td class="metric_stability_level" data-stability="stable">STABLE</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Admission sub-step latency histogram in seconds, broken out for each operation and API resource and step type (validate or admit).</td>
 <td class="metric_labels_varying"><div class="metric_label">operation</div><div class="metric_label">rejected</div><div class="metric_label">type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_admission_webhook_admission_duration_seconds</td>
 <td class="metric_stability_level" data-stability="stable">STABLE</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Admission webhook latency histogram in seconds, identified by name and broken out for each operation and API resource and type (validate or admit).</td>
 <td class="metric_labels_varying"><div class="metric_label">name</div><div class="metric_label">operation</div><div class="metric_label">rejected</div><div class="metric_label">type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_current_inflight_requests</td>
 <td class="metric_stability_level" data-stability="stable">STABLE</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Maximal number of currently used inflight request limit of this apiserver per request kind in last second.</td>
 <td class="metric_labels_varying"><div class="metric_label">request_kind</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_longrunning_requests</td>
 <td class="metric_stability_level" data-stability="stable">STABLE</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Gauge of all active long-running apiserver requests broken out by verb, group, version, resource, scope and component. Not all requests are tracked this way.</td>
 <td class="metric_labels_varying"><div class="metric_label">component</div><div class="metric_label">group</div><div class="metric_label">resource</div><div class="metric_label">scope</div><div class="metric_label">subresource</div><div class="metric_label">verb</div><div class="metric_label">version</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_request_duration_seconds</td>
 <td class="metric_stability_level" data-stability="stable">STABLE</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Response latency distribution in seconds for each verb, dry run value, group, version, resource, subresource, scope and component.</td>
 <td class="metric_labels_varying"><div class="metric_label">component</div><div class="metric_label">dry_run</div><div class="metric_label">group</div><div class="metric_label">resource</div><div class="metric_label">scope</div><div class="metric_label">subresource</div><div class="metric_label">verb</div><div class="metric_label">version</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_request_total</td>
 <td class="metric_stability_level" data-stability="stable">STABLE</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter of apiserver requests broken out for each verb, dry run value, group, version, resource, scope, component, and HTTP response code.</td>
 <td class="metric_labels_varying"><div class="metric_label">code</div><div class="metric_label">component</div><div class="metric_label">dry_run</div><div class="metric_label">group</div><div class="metric_label">resource</div><div class="metric_label">scope</div><div class="metric_label">subresource</div><div class="metric_label">verb</div><div class="metric_label">version</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_requested_deprecated_apis</td>
 <td class="metric_stability_level" data-stability="stable">STABLE</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Gauge of deprecated APIs that have been requested, broken out by API group, version, resource, subresource, and removed_release.</td>
 <td class="metric_labels_varying"><div class="metric_label">group</div><div class="metric_label">removed_release</div><div class="metric_label">resource</div><div class="metric_label">subresource</div><div class="metric_label">version</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_response_sizes</td>
 <td class="metric_stability_level" data-stability="stable">STABLE</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Response size distribution in bytes for each group, version, verb, resource, subresource, scope and component.</td>
 <td class="metric_labels_varying"><div class="metric_label">component</div><div class="metric_label">group</div><div class="metric_label">resource</div><div class="metric_label">scope</div><div class="metric_label">subresource</div><div class="metric_label">verb</div><div class="metric_label">version</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_storage_objects</td>
 <td class="metric_stability_level" data-stability="stable">STABLE</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of stored objects at the time of last check split by kind.</td>
 <td class="metric_labels_varying"><div class="metric_label">resource</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">cronjob_controller_job_creation_skew_duration_seconds</td>
+<td class="metric_stability_level" data-stability="stable">STABLE</td>
+<td class="metric_type" data-type="histogram">Histogram</td>
+<td class="metric_description">Time between when a cronjob is scheduled to be run, and when the corresponding job is created</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">job_controller_job_pods_finished_total</td>
+<td class="metric_stability_level" data-stability="stable">STABLE</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">The number of finished Pods that are fully tracked</td>
+<td class="metric_labels_varying"><div class="metric_label">completion_mode</div><div class="metric_label">result</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">job_controller_job_sync_duration_seconds</td>
+<td class="metric_stability_level" data-stability="stable">STABLE</td>
+<td class="metric_type" data-type="histogram">Histogram</td>
+<td class="metric_description">The time it took to sync a job</td>
+<td class="metric_labels_varying"><div class="metric_label">action</div><div class="metric_label">completion_mode</div><div class="metric_label">result</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">job_controller_job_syncs_total</td>
+<td class="metric_stability_level" data-stability="stable">STABLE</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">The number of job syncs</td>
+<td class="metric_labels_varying"><div class="metric_label">action</div><div class="metric_label">completion_mode</div><div class="metric_label">result</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">job_controller_jobs_finished_total</td>
+<td class="metric_stability_level" data-stability="stable">STABLE</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">The number of finished jobs</td>
+<td class="metric_labels_varying"><div class="metric_label">completion_mode</div><div class="metric_label">reason</div><div class="metric_label">result</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kube_pod_resource_limit</td>
+<td class="metric_stability_level" data-stability="stable">STABLE</td>
+<td class="metric_type" data-type="custom">Custom</td>
+<td class="metric_description">Resources limit for workloads on the cluster, broken down by pod. This shows the resource usage the scheduler and kubelet expect per pod for resources along with the unit for the resource if any.</td>
+<td class="metric_labels_varying"><div class="metric_label">namespace</div><div class="metric_label">pod</div><div class="metric_label">node</div><div class="metric_label">scheduler</div><div class="metric_label">priority</div><div class="metric_label">resource</div><div class="metric_label">unit</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kube_pod_resource_request</td>
+<td class="metric_stability_level" data-stability="stable">STABLE</td>
+<td class="metric_type" data-type="custom">Custom</td>
+<td class="metric_description">Resources requested by workloads on the cluster, broken down by pod. This shows the resource usage the scheduler and kubelet expect per pod for resources along with the unit for the resource if any.</td>
+<td class="metric_labels_varying"><div class="metric_label">namespace</div><div class="metric_label">pod</div><div class="metric_label">node</div><div class="metric_label">scheduler</div><div class="metric_label">priority</div><div class="metric_label">resource</div><div class="metric_label">unit</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">node_collector_evictions_total</td>
 <td class="metric_stability_level" data-stability="stable">STABLE</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of Node evictions that happened since current instance of NodeController started.</td>
 <td class="metric_labels_varying"><div class="metric_label">zone</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">scheduler_framework_extension_point_duration_seconds</td>
 <td class="metric_stability_level" data-stability="stable">STABLE</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Latency for running all plugins of a specific extension point.</td>
 <td class="metric_labels_varying"><div class="metric_label">extension_point</div><div class="metric_label">profile</div><div class="metric_label">status</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">scheduler_pending_pods</td>
 <td class="metric_stability_level" data-stability="stable">STABLE</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
-<td class="metric_description">Number of pending pods, by the queue type. 'active' means number of pods in activeQ; 'backoff' means number of pods in backoffQ; 'unschedulable' means number of pods in unschedulablePods.</td>
+<td class="metric_description">Number of pending pods, by the queue type. 'active' means number of pods in activeQ; 'backoff' means number of pods in backoffQ; 'unschedulable' means number of pods in unschedulablePods that the scheduler attempted to schedule and failed; 'gated' is the number of unschedulable pods that the scheduler never attempted to schedule because they are gated.</td>
 <td class="metric_labels_varying"><div class="metric_label">queue</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">scheduler_pod_scheduling_attempts</td>
 <td class="metric_stability_level" data-stability="stable">STABLE</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Number of attempts to successfully schedule a pod.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">scheduler_pod_scheduling_duration_seconds</td>
 <td class="metric_stability_level" data-stability="stable">STABLE</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">E2e latency for a pod being scheduled which may include multiple scheduling attempts.</td>
 <td class="metric_labels_varying"><div class="metric_label">attempts</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">scheduler_preemption_attempts_total</td>
 <td class="metric_stability_level" data-stability="stable">STABLE</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Total preemption attempts in the cluster till now</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">scheduler_preemption_victims</td>
 <td class="metric_stability_level" data-stability="stable">STABLE</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Number of selected preemption victims</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">scheduler_queue_incoming_pods_total</td>
 <td class="metric_stability_level" data-stability="stable">STABLE</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of pods added to scheduling queues by event and queue type.</td>
 <td class="metric_labels_varying"><div class="metric_label">event</div><div class="metric_label">queue</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">scheduler_schedule_attempts_total</td>
 <td class="metric_stability_level" data-stability="stable">STABLE</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of attempts to schedule pods, by the result. 'unschedulable' means a pod could not be scheduled, while 'error' means an internal scheduler problem.</td>
 <td class="metric_labels_varying"><div class="metric_label">profile</div><div class="metric_label">result</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">scheduler_scheduling_attempt_duration_seconds</td>
 <td class="metric_stability_level" data-stability="stable">STABLE</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Scheduling attempt latency in seconds (scheduling algorithm + binding)</td>
 <td class="metric_labels_varying"><div class="metric_label">profile</div><div class="metric_label">result</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+</tbody>
+</table>
+
+### List of Beta Kubernetes Metrics
+
+Beta metrics observe a looser API contract than its stable counterparts. No labels can be removed from beta metrics during their lifetime, however, labels can be added while the metric is in the beta stage. This offers the assurance that beta metrics will honor existing dashboards and alerts, while allowing for amendments in the future. 
+
+
+<table class="table metrics" caption="This is the list of BETA metrics emitted from core Kubernetes components">
+<thead>
+	<tr>
+		<th class="metric_name">Name</th>
+		<th class="metric_stability_level">Stability Level</th>
+		<th class="metric_type">Type</th>
+		<th class="metric_help">Help</th>
+		<th class="metric_labels">Labels</th>
+		<th class="metric_const_labels">Const Labels</th>
+		<th class="metric_deprecated_version">Deprecated Version</th>
+	</tr>
+</thead>
+<tbody>
+
 </tbody>
 </table>
 
 ### List of Alpha Kubernetes Metrics
 
+Alpha metrics do not have any API guarantees. These metrics must be used at your own risk, subsequent versions of Kubernetes may remove these metrics altogether, or mutate the API in such a way that breaks existing dashboards and alerts. 
+
 <table class="table metrics" caption="This is the list of ALPHA metrics emitted from core Kubernetes components">
 <thead>
 	<tr>
@@ -160,1887 +258,2600 @@ components using an HTTP scrape, and fetch the current metrics data in Prometheu
 		<th class="metric_help">Help</th>
 		<th class="metric_labels">Labels</th>
 		<th class="metric_const_labels">Const Labels</th>
+		<th class="metric_deprecated_version">Deprecated Version</th>
 	</tr>
 </thead>
 <tbody>
 
+<tr class="metric"><td class="metric_name">aggregator_discovery_aggregation_count_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Counter of number of times discovery was aggregated</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">aggregator_openapi_v2_regeneration_count</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter of OpenAPI v2 spec regeneration count broken down by causing APIService name and reason.</td>
 <td class="metric_labels_varying"><div class="metric_label">apiservice</div><div class="metric_label">reason</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">aggregator_openapi_v2_regeneration_duration</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Gauge of OpenAPI v2 spec regeneration duration in seconds.</td>
 <td class="metric_labels_varying"><div class="metric_label">reason</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">aggregator_unavailable_apiservice</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Gauge of APIServices which are marked as unavailable broken down by APIService name.</td>
 <td class="metric_labels_varying"><div class="metric_label">name</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">aggregator_unavailable_apiservice_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter of APIServices which are marked as unavailable broken down by APIService name and reason.</td>
 <td class="metric_labels_varying"><div class="metric_label">name</div><div class="metric_label">reason</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiextensions_openapi_v2_regeneration_count</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter of OpenAPI v2 spec regeneration count broken down by causing CRD name and reason.</td>
 <td class="metric_labels_varying"><div class="metric_label">crd</div><div class="metric_label">reason</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiextensions_openapi_v3_regeneration_count</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter of OpenAPI v3 spec regeneration count broken down by group, version, causing CRD and reason.</td>
 <td class="metric_labels_varying"><div class="metric_label">crd</div><div class="metric_label">group</div><div class="metric_label">reason</div><div class="metric_label">version</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_admission_admission_match_condition_evaluation_errors_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Admission match condition evaluation errors count, identified by name of resource containing the match condition and broken out for each admission type (validating or mutating).</td>
+<td class="metric_labels_varying"><div class="metric_label">name</div><div class="metric_label">type</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_admission_step_admission_duration_seconds_summary</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="summary">Summary</td>
 <td class="metric_description">Admission sub-step latency summary in seconds, broken out for each operation and API resource and step type (validate or admit).</td>
 <td class="metric_labels_varying"><div class="metric_label">operation</div><div class="metric_label">rejected</div><div class="metric_label">type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_admission_webhook_fail_open_count</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Admission webhook fail open count, identified by name and broken out for each admission type (validating or mutating).</td>
 <td class="metric_labels_varying"><div class="metric_label">name</div><div class="metric_label">type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_admission_webhook_rejection_count</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Admission webhook rejection count, identified by name and broken out for each admission type (validating or admit) and operation. Additional labels specify an error type (calling_webhook_error or apiserver_internal_error if an error occurred; no_error otherwise) and optionally a non-zero rejection code if the webhook rejects the request with an HTTP status code (honored by the apiserver when the code is greater or equal to 400). Codes greater than 600 are truncated to 600, to keep the metrics cardinality bounded.</td>
 <td class="metric_labels_varying"><div class="metric_label">error_type</div><div class="metric_label">name</div><div class="metric_label">operation</div><div class="metric_label">rejection_code</div><div class="metric_label">type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_admission_webhook_request_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Admission webhook request total, identified by name and broken out for each admission type (validating or mutating) and operation. Additional labels specify whether the request was rejected or not and an HTTP status code. Codes greater than 600 are truncated to 600, to keep the metrics cardinality bounded.</td>
 <td class="metric_labels_varying"><div class="metric_label">code</div><div class="metric_label">name</div><div class="metric_label">operation</div><div class="metric_label">rejected</div><div class="metric_label">type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_audit_error_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter of audit events that failed to be audited properly. Plugin identifies the plugin affected by the error.</td>
 <td class="metric_labels_varying"><div class="metric_label">plugin</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_audit_event_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter of audit events generated and sent to the audit backend.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_audit_level_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter of policy levels for audit events (1 per request).</td>
 <td class="metric_labels_varying"><div class="metric_label">level</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_audit_requests_rejected_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter of apiserver requests rejected due to an error in audit logging backend.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_cache_list_fetched_objects_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of objects read from watch cache in the course of serving a LIST request</td>
 <td class="metric_labels_varying"><div class="metric_label">index</div><div class="metric_label">resource_prefix</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_cache_list_returned_objects_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of objects returned for a LIST request from watch cache</td>
 <td class="metric_labels_varying"><div class="metric_label">resource_prefix</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_cache_list_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of LIST requests served from watch cache</td>
 <td class="metric_labels_varying"><div class="metric_label">index</div><div class="metric_label">resource_prefix</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_cel_compilation_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
-<td class="metric_description"></td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_description">CEL compilation time in seconds.</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_cel_evaluation_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
-<td class="metric_description"></td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_description">CEL evaluation time in seconds.</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_certificates_registry_csr_honored_duration_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Total number of issued CSRs with a requested duration that was honored, sliced by signer (only kubernetes.io signer names are specifically identified)</td>
 <td class="metric_labels_varying"><div class="metric_label">signerName</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_certificates_registry_csr_requested_duration_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Total number of issued CSRs with a requested duration, sliced by signer (only kubernetes.io signer names are specifically identified)</td>
 <td class="metric_labels_varying"><div class="metric_label">signerName</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_client_certificate_expiration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Distribution of the remaining lifetime on the certificate used to authenticate a request.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_crd_webhook_conversion_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">CRD webhook conversion duration in seconds</td>
 <td class="metric_labels_varying"><div class="metric_label">crd_name</div><div class="metric_label">from_version</div><div class="metric_label">succeeded</div><div class="metric_label">to_version</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_current_inqueue_requests</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Maximal number of queued requests in this apiserver per request kind in last second.</td>
 <td class="metric_labels_varying"><div class="metric_label">request_kind</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_delegated_authn_request_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Request latency in seconds. Broken down by status code.</td>
 <td class="metric_labels_varying"><div class="metric_label">code</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_delegated_authn_request_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of HTTP requests partitioned by status code.</td>
 <td class="metric_labels_varying"><div class="metric_label">code</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_delegated_authz_request_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Request latency in seconds. Broken down by status code.</td>
 <td class="metric_labels_varying"><div class="metric_label">code</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_delegated_authz_request_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of HTTP requests partitioned by status code.</td>
 <td class="metric_labels_varying"><div class="metric_label">code</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_egress_dialer_dial_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Dial latency histogram in seconds, labeled by the protocol (http-connect or grpc), transport (tcp or uds)</td>
 <td class="metric_labels_varying"><div class="metric_label">protocol</div><div class="metric_label">transport</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_egress_dialer_dial_failure_count</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Dial failure count, labeled by the protocol (http-connect or grpc), transport (tcp or uds), and stage (connect or proxy). The stage indicates at which stage the dial failed</td>
 <td class="metric_labels_varying"><div class="metric_label">protocol</div><div class="metric_label">stage</div><div class="metric_label">transport</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_egress_dialer_dial_start_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Dial starts, labeled by the protocol (http-connect or grpc) and transport (tcp or uds).</td>
+<td class="metric_labels_varying"><div class="metric_label">protocol</div><div class="metric_label">transport</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_envelope_encryption_dek_cache_fill_percent</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Percent of the cache slots currently occupied by cached DEKs.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_envelope_encryption_dek_cache_inter_arrival_time_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Time (in seconds) of inter arrival of transformation requests.</td>
 <td class="metric_labels_varying"><div class="metric_label">transformation_type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_envelope_encryption_invalid_key_id_from_status_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Number of times an invalid keyID is returned by the Status RPC call split by error.</td>
+<td class="metric_labels_varying"><div class="metric_label">error</div><div class="metric_label">provider_name</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_envelope_encryption_key_id_hash_last_timestamp_seconds</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">The last time in seconds when a keyID was used.</td>
+<td class="metric_labels_varying"><div class="metric_label">key_id_hash</div><div class="metric_label">provider_name</div><div class="metric_label">transformation_type</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_envelope_encryption_key_id_hash_status_last_timestamp_seconds</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">The last time in seconds when a keyID was returned by the Status RPC call.</td>
+<td class="metric_labels_varying"><div class="metric_label">key_id_hash</div><div class="metric_label">provider_name</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_envelope_encryption_key_id_hash_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Number of times a keyID is used split by transformation type and provider.</td>
+<td class="metric_labels_varying"><div class="metric_label">key_id_hash</div><div class="metric_label">provider_name</div><div class="metric_label">transformation_type</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_envelope_encryption_kms_operations_latency_seconds</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="histogram">Histogram</td>
+<td class="metric_description">KMS operation duration with gRPC error code status total.</td>
+<td class="metric_labels_varying"><div class="metric_label">grpc_status_code</div><div class="metric_label">method_name</div><div class="metric_label">provider_name</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_flowcontrol_current_executing_requests</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of requests in initial (for a WATCH) or any (for a non-WATCH) execution stage in the API Priority and Fairness subsystem</td>
 <td class="metric_labels_varying"><div class="metric_label">flow_schema</div><div class="metric_label">priority_level</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_flowcontrol_current_inqueue_requests</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of requests currently pending in queues of the API Priority and Fairness subsystem</td>
 <td class="metric_labels_varying"><div class="metric_label">flow_schema</div><div class="metric_label">priority_level</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_flowcontrol_current_limit_seats</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">current derived number of execution seats available to each priority level</td>
+<td class="metric_labels_varying"><div class="metric_label">priority_level</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_flowcontrol_current_r</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">R(time of last change)</td>
 <td class="metric_labels_varying"><div class="metric_label">priority_level</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_flowcontrol_demand_seats</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="timingratiohistogram">TimingRatioHistogram</td>
+<td class="metric_description">Observations, at the end of every nanosecond, of (the number of seats each priority level could use) / (nominal number of seats for that level)</td>
+<td class="metric_labels_varying"><div class="metric_label">priority_level</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_flowcontrol_demand_seats_average</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">Time-weighted average, over last adjustment period, of demand_seats</td>
+<td class="metric_labels_varying"><div class="metric_label">priority_level</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_flowcontrol_demand_seats_high_watermark</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">High watermark, over last adjustment period, of demand_seats</td>
+<td class="metric_labels_varying"><div class="metric_label">priority_level</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_flowcontrol_demand_seats_smoothed</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">Smoothed seat demands</td>
+<td class="metric_labels_varying"><div class="metric_label">priority_level</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_flowcontrol_demand_seats_stdev</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">Time-weighted standard deviation, over last adjustment period, of demand_seats</td>
+<td class="metric_labels_varying"><div class="metric_label">priority_level</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_flowcontrol_dispatch_r</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">R(time of last dispatch)</td>
 <td class="metric_labels_varying"><div class="metric_label">priority_level</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_flowcontrol_dispatched_requests_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of requests executed by API Priority and Fairness subsystem</td>
 <td class="metric_labels_varying"><div class="metric_label">flow_schema</div><div class="metric_label">priority_level</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_flowcontrol_epoch_advance_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of times the queueset's progress meter jumped backward</td>
 <td class="metric_labels_varying"><div class="metric_label">priority_level</div><div class="metric_label">success</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_flowcontrol_latest_s</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">S(most recently dispatched request)</td>
 <td class="metric_labels_varying"><div class="metric_label">priority_level</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_flowcontrol_lower_limit_seats</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">Configured lower bound on number of execution seats available to each priority level</td>
+<td class="metric_labels_varying"><div class="metric_label">priority_level</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_flowcontrol_next_discounted_s_bounds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">min and max, over queues, of S(oldest waiting request in queue) - estimated work in progress</td>
 <td class="metric_labels_varying"><div class="metric_label">bound</div><div class="metric_label">priority_level</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_flowcontrol_next_s_bounds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">min and max, over queues, of S(oldest waiting request in queue)</td>
 <td class="metric_labels_varying"><div class="metric_label">bound</div><div class="metric_label">priority_level</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_flowcontrol_nominal_limit_seats</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">Nominal number of execution seats configured for each priority level</td>
+<td class="metric_labels_varying"><div class="metric_label">priority_level</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_flowcontrol_priority_level_request_utilization</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="timingratiohistogram">TimingRatioHistogram</td>
 <td class="metric_description">Observations, at the end of every nanosecond, of number of requests (as a fraction of the relevant limit) waiting or in any stage of execution (but only initial stage for WATCHes)</td>
 <td class="metric_labels_varying"><div class="metric_label">phase</div><div class="metric_label">priority_level</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_flowcontrol_priority_level_seat_utilization</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="timingratiohistogram">TimingRatioHistogram</td>
 <td class="metric_description">Observations, at the end of every nanosecond, of utilization of seats for any stage of execution (but only initial stage for WATCHes)</td>
 <td class="metric_labels_varying"><div class="metric_label">priority_level</div></td>
-<td class="metric_labels_constant">map[phase:executing]</td></tr>
+<td class="metric_labels_constant"><div class="metric_label">phase:executing</div></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_flowcontrol_read_vs_write_current_requests</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="timingratiohistogram">TimingRatioHistogram</td>
 <td class="metric_description">Observations, at the end of every nanosecond, of the number of requests (as a fraction of the relevant limit) waiting or in regular stage of execution</td>
 <td class="metric_labels_varying"><div class="metric_label">phase</div><div class="metric_label">request_kind</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_flowcontrol_rejected_requests_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of requests rejected by API Priority and Fairness subsystem</td>
 <td class="metric_labels_varying"><div class="metric_label">flow_schema</div><div class="metric_label">priority_level</div><div class="metric_label">reason</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_flowcontrol_request_concurrency_in_use</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Concurrency (number of seats) occupied by the currently executing (initial stage for a WATCH, any stage otherwise) requests in the API Priority and Fairness subsystem</td>
 <td class="metric_labels_varying"><div class="metric_label">flow_schema</div><div class="metric_label">priority_level</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_flowcontrol_request_concurrency_limit</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Shared concurrency limit in the API Priority and Fairness subsystem</td>
 <td class="metric_labels_varying"><div class="metric_label">priority_level</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_flowcontrol_request_dispatch_no_accommodation_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of times a dispatch attempt resulted in a non accommodation due to lack of available seats</td>
 <td class="metric_labels_varying"><div class="metric_label">flow_schema</div><div class="metric_label">priority_level</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_flowcontrol_request_execution_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Duration of initial stage (for a WATCH) or any (for a non-WATCH) stage of request execution in the API Priority and Fairness subsystem</td>
 <td class="metric_labels_varying"><div class="metric_label">flow_schema</div><div class="metric_label">priority_level</div><div class="metric_label">type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_flowcontrol_request_queue_length_after_enqueue</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Length of queue in the API Priority and Fairness subsystem, as seen by each request after it is enqueued</td>
 <td class="metric_labels_varying"><div class="metric_label">flow_schema</div><div class="metric_label">priority_level</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_flowcontrol_request_wait_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Length of time a request spent waiting in its queue</td>
 <td class="metric_labels_varying"><div class="metric_label">execute</div><div class="metric_label">flow_schema</div><div class="metric_label">priority_level</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_flowcontrol_seat_fair_frac</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">Fair fraction of server's concurrency to allocate to each priority level that can use it</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_flowcontrol_target_seats</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">Seat allocation targets</td>
+<td class="metric_labels_varying"><div class="metric_label">priority_level</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_flowcontrol_upper_limit_seats</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">Configured upper bound on number of execution seats available to each priority level</td>
+<td class="metric_labels_varying"><div class="metric_label">priority_level</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_flowcontrol_watch_count_samples</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">count of watchers for mutating requests in API Priority and Fairness</td>
 <td class="metric_labels_varying"><div class="metric_label">flow_schema</div><div class="metric_label">priority_level</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_flowcontrol_work_estimated_seats</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Number of estimated seats (maximum of initial and final seats) associated with requests in API Priority and Fairness</td>
 <td class="metric_labels_varying"><div class="metric_label">flow_schema</div><div class="metric_label">priority_level</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_init_events_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter of init events processed in watch cache broken by resource type.</td>
 <td class="metric_labels_varying"><div class="metric_label">resource</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_kube_aggregator_x509_insecure_sha1_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counts the number of requests to servers with insecure SHA1 signatures in their serving certificate OR the number of connection failures due to the insecure SHA1 signatures (either/or, based on the runtime environment)</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_kube_aggregator_x509_missing_san_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counts the number of requests to servers missing SAN extension in their serving certificate OR the number of connection failures due to the lack of x509 certificate SAN extension missing (either/or, based on the runtime environment)</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_request_aborts_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of requests which apiserver aborted possibly due to a timeout, for each group, version, verb, resource, subresource and scope</td>
 <td class="metric_labels_varying"><div class="metric_label">group</div><div class="metric_label">resource</div><div class="metric_label">scope</div><div class="metric_label">subresource</div><div class="metric_label">verb</div><div class="metric_label">version</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_request_body_sizes</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Apiserver request body sizes broken out by size.</td>
 <td class="metric_labels_varying"><div class="metric_label">resource</div><div class="metric_label">verb</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_request_filter_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Request filter latency distribution in seconds, for each filter type</td>
 <td class="metric_labels_varying"><div class="metric_label">filter</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_request_post_timeout_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Tracks the activity of the request handlers after the associated requests have been timed out by the apiserver</td>
 <td class="metric_labels_varying"><div class="metric_label">source</div><div class="metric_label">status</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_request_sli_duration_seconds</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="histogram">Histogram</td>
+<td class="metric_description">Response latency distribution (not counting webhook duration and priority & fairness queue wait times) in seconds for each verb, group, version, resource, subresource, scope and component.</td>
+<td class="metric_labels_varying"><div class="metric_label">component</div><div class="metric_label">group</div><div class="metric_label">resource</div><div class="metric_label">scope</div><div class="metric_label">subresource</div><div class="metric_label">verb</div><div class="metric_label">version</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_request_slo_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
-<td class="metric_description">Response latency distribution (not counting webhook duration) in seconds for each verb, group, version, resource, subresource, scope and component.</td>
+<td class="metric_description">Response latency distribution (not counting webhook duration and priority & fairness queue wait times) in seconds for each verb, group, version, resource, subresource, scope and component.</td>
 <td class="metric_labels_varying"><div class="metric_label">component</div><div class="metric_label">group</div><div class="metric_label">resource</div><div class="metric_label">scope</div><div class="metric_label">subresource</div><div class="metric_label">verb</div><div class="metric_label">version</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version">1.27.0</td></tr>
 <tr class="metric"><td class="metric_name">apiserver_request_terminations_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of requests which apiserver terminated in self-defense.</td>
 <td class="metric_labels_varying"><div class="metric_label">code</div><div class="metric_label">component</div><div class="metric_label">group</div><div class="metric_label">resource</div><div class="metric_label">scope</div><div class="metric_label">subresource</div><div class="metric_label">verb</div><div class="metric_label">version</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_request_timestamp_comparison_time</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Time taken for comparison of old vs new objects in UPDATE or PATCH requests</td>
 <td class="metric_labels_varying"><div class="metric_label">code_path</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_selfrequest_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter of apiserver self-requests broken out for each verb, API resource and subresource.</td>
 <td class="metric_labels_varying"><div class="metric_label">resource</div><div class="metric_label">subresource</div><div class="metric_label">verb</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_storage_data_key_generation_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Latencies in seconds of data encryption key(DEK) generation operations.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_storage_data_key_generation_failures_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Total number of failed data encryption key(DEK) generation operations.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_storage_db_total_size_in_bytes</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Total size of the storage database file physically allocated in bytes.</td>
 <td class="metric_labels_varying"><div class="metric_label">endpoint</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_storage_decode_errors_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Number of stored object decode errors split by object type</td>
+<td class="metric_labels_varying"><div class="metric_label">resource</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_storage_envelope_transformation_cache_misses_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Total number of cache misses while accessing key decryption key(KEK).</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_storage_events_received_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Number of etcd events received split by kind.</td>
+<td class="metric_labels_varying"><div class="metric_label">resource</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_storage_list_evaluated_objects_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of objects tested in the course of serving a LIST request from storage</td>
 <td class="metric_labels_varying"><div class="metric_label">resource</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_storage_list_fetched_objects_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of objects read from storage in the course of serving a LIST request</td>
 <td class="metric_labels_varying"><div class="metric_label">resource</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_storage_list_returned_objects_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of objects returned for a LIST request from storage</td>
 <td class="metric_labels_varying"><div class="metric_label">resource</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_storage_list_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of LIST requests served from storage</td>
 <td class="metric_labels_varying"><div class="metric_label">resource</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_storage_transformation_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Latencies in seconds of value transformation operations.</td>
-<td class="metric_labels_varying"><div class="metric_label">transformation_type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"><div class="metric_label">transformation_type</div><div class="metric_label">transformer_prefix</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_storage_transformation_operations_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Total number of transformations.</td>
 <td class="metric_labels_varying"><div class="metric_label">status</div><div class="metric_label">transformation_type</div><div class="metric_label">transformer_prefix</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_terminated_watchers_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter of watchers closed due to unresponsiveness broken by resource type.</td>
 <td class="metric_labels_varying"><div class="metric_label">resource</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_tls_handshake_errors_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of requests dropped with 'TLS handshake error from' error</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_validating_admission_policy_check_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
-<td class="metric_description">Validation admission latency for individual validation expressions in seconds, labeled by policy and param resource, further including binding, state and enforcement action taken.</td>
-<td class="metric_labels_varying"><div class="metric_label">enforcement_action</div><div class="metric_label">params</div><div class="metric_label">policy</div><div class="metric_label">policy_binding</div><div class="metric_label">state</div><div class="metric_label">validation_expression</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_description">Validation admission latency for individual validation expressions in seconds, labeled by policy and further including binding, state and enforcement action taken.</td>
+<td class="metric_labels_varying"><div class="metric_label">enforcement_action</div><div class="metric_label">policy</div><div class="metric_label">policy_binding</div><div class="metric_label">state</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_validating_admission_policy_check_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
-<td class="metric_description">Validation admission policy check total, labeled by policy and param resource, and further identified by binding, validation expression, enforcement action taken, and state.</td>
-<td class="metric_labels_varying"><div class="metric_label">enforcement_action</div><div class="metric_label">params</div><div class="metric_label">policy</div><div class="metric_label">policy_binding</div><div class="metric_label">state</div><div class="metric_label">validation_expression</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_description">Validation admission policy check total, labeled by policy and further identified by binding, enforcement action taken, and state.</td>
+<td class="metric_labels_varying"><div class="metric_label">enforcement_action</div><div class="metric_label">policy</div><div class="metric_label">policy_binding</div><div class="metric_label">state</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_validating_admission_policy_definition_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Validation admission policy count total, labeled by state and enforcement action.</td>
 <td class="metric_labels_varying"><div class="metric_label">enforcement_action</div><div class="metric_label">state</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_watch_cache_events_dispatched_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter of events dispatched in watch cache broken by resource type.</td>
 <td class="metric_labels_varying"><div class="metric_label">resource</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">apiserver_watch_cache_events_received_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Counter of events received in watch cache broken by resource type.</td>
+<td class="metric_labels_varying"><div class="metric_label">resource</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_watch_cache_initializations_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter of watch cache initializations broken by resource type.</td>
 <td class="metric_labels_varying"><div class="metric_label">resource</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_watch_events_sizes</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Watch event size distribution in bytes</td>
 <td class="metric_labels_varying"><div class="metric_label">group</div><div class="metric_label">kind</div><div class="metric_label">version</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_watch_events_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of events sent in watch clients</td>
 <td class="metric_labels_varying"><div class="metric_label">group</div><div class="metric_label">kind</div><div class="metric_label">version</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_webhooks_x509_insecure_sha1_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counts the number of requests to servers with insecure SHA1 signatures in their serving certificate OR the number of connection failures due to the insecure SHA1 signatures (either/or, based on the runtime environment)</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">apiserver_webhooks_x509_missing_san_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counts the number of requests to servers missing SAN extension in their serving certificate OR the number of connection failures due to the lack of x509 certificate SAN extension missing (either/or, based on the runtime environment)</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">attachdetach_controller_forced_detaches</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of times the A/D Controller performed a forced detach</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">attachdetach_controller_total_volumes</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Number of volumes in A/D Controller</td>
 <td class="metric_labels_varying"><div class="metric_label">plugin_name</div><div class="metric_label">state</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">authenticated_user_requests</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter of authenticated requests broken out by username.</td>
 <td class="metric_labels_varying"><div class="metric_label">username</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">authentication_attempts</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter of authenticated attempts.</td>
 <td class="metric_labels_varying"><div class="metric_label">result</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">authentication_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Authentication duration in seconds broken out by result.</td>
 <td class="metric_labels_varying"><div class="metric_label">result</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">authentication_token_cache_active_fetch_count</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description"></td>
 <td class="metric_labels_varying"><div class="metric_label">status</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">authentication_token_cache_fetch_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description"></td>
 <td class="metric_labels_varying"><div class="metric_label">status</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">authentication_token_cache_request_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description"></td>
 <td class="metric_labels_varying"><div class="metric_label">status</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">authentication_token_cache_request_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description"></td>
 <td class="metric_labels_varying"><div class="metric_label">status</div></td>
-<td class="metric_labels_constant">None</td></tr>
-<tr class="metric"><td class="metric_name">cloudprovider_aws_api_request_duration_seconds</td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">cloud_provider_webhook_request_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
-<td class="metric_description">Latency of AWS API calls</td>
-<td class="metric_labels_varying"><div class="metric_label">request</div></td>
-<td class="metric_labels_constant">None</td></tr>
-<tr class="metric"><td class="metric_name">cloudprovider_aws_api_request_errors</td>
+<td class="metric_description">Request latency in seconds. Broken down by status code.</td>
+<td class="metric_labels_varying"><div class="metric_label">code</div><div class="metric_label">webhook</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">cloud_provider_webhook_request_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
-<td class="metric_description">AWS API errors</td>
-<td class="metric_labels_varying"><div class="metric_label">request</div></td>
-<td class="metric_labels_constant">None</td></tr>
-<tr class="metric"><td class="metric_name">cloudprovider_aws_api_throttled_requests_total</td>
-<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
-<td class="metric_type" data-type="counter">Counter</td>
-<td class="metric_description">AWS API throttled requests</td>
-<td class="metric_labels_varying"><div class="metric_label">operation_name</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_description">Number of HTTP requests partitioned by status code.</td>
+<td class="metric_labels_varying"><div class="metric_label">code</div><div class="metric_label">webhook</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">cloudprovider_azure_api_request_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Latency of an Azure API call</td>
 <td class="metric_labels_varying"><div class="metric_label">request</div><div class="metric_label">resource_group</div><div class="metric_label">source</div><div class="metric_label">subscription_id</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">cloudprovider_azure_api_request_errors</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of errors for an Azure API call</td>
 <td class="metric_labels_varying"><div class="metric_label">request</div><div class="metric_label">resource_group</div><div class="metric_label">source</div><div class="metric_label">subscription_id</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">cloudprovider_azure_api_request_ratelimited_count</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of rate limited Azure API calls</td>
 <td class="metric_labels_varying"><div class="metric_label">request</div><div class="metric_label">resource_group</div><div class="metric_label">source</div><div class="metric_label">subscription_id</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">cloudprovider_azure_api_request_throttled_count</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of throttled Azure API calls</td>
 <td class="metric_labels_varying"><div class="metric_label">request</div><div class="metric_label">resource_group</div><div class="metric_label">source</div><div class="metric_label">subscription_id</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">cloudprovider_azure_op_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Latency of an Azure service operation</td>
 <td class="metric_labels_varying"><div class="metric_label">request</div><div class="metric_label">resource_group</div><div class="metric_label">source</div><div class="metric_label">subscription_id</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">cloudprovider_azure_op_failure_count</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of failed Azure service operations</td>
 <td class="metric_labels_varying"><div class="metric_label">request</div><div class="metric_label">resource_group</div><div class="metric_label">source</div><div class="metric_label">subscription_id</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">cloudprovider_gce_api_request_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Latency of a GCE API call</td>
 <td class="metric_labels_varying"><div class="metric_label">region</div><div class="metric_label">request</div><div class="metric_label">version</div><div class="metric_label">zone</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">cloudprovider_gce_api_request_errors</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of errors for an API call</td>
 <td class="metric_labels_varying"><div class="metric_label">region</div><div class="metric_label">request</div><div class="metric_label">version</div><div class="metric_label">zone</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">cloudprovider_vsphere_api_request_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Latency of vsphere api call</td>
 <td class="metric_labels_varying"><div class="metric_label">request</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">cloudprovider_vsphere_api_request_errors</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">vsphere Api errors</td>
 <td class="metric_labels_varying"><div class="metric_label">request</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">cloudprovider_vsphere_operation_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Latency of vsphere operation call</td>
 <td class="metric_labels_varying"><div class="metric_label">operation</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">cloudprovider_vsphere_operation_errors</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">vsphere operation errors</td>
 <td class="metric_labels_varying"><div class="metric_label">operation</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">cloudprovider_vsphere_vcenter_versions</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Versions for connected vSphere vCenters</td>
 <td class="metric_labels_varying"><div class="metric_label">hostname</div><div class="metric_label">version</div><div class="metric_label">build</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">container_cpu_usage_seconds_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Cumulative cpu time consumed by the container in core-seconds</td>
 <td class="metric_labels_varying"><div class="metric_label">container</div><div class="metric_label">pod</div><div class="metric_label">namespace</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">container_memory_working_set_bytes</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Current working set of the container in bytes</td>
 <td class="metric_labels_varying"><div class="metric_label">container</div><div class="metric_label">pod</div><div class="metric_label">namespace</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">container_start_time_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Start time of the container since unix epoch in seconds</td>
 <td class="metric_labels_varying"><div class="metric_label">container</div><div class="metric_label">pod</div><div class="metric_label">namespace</div></td>
-<td class="metric_labels_constant">None</td></tr>
-<tr class="metric"><td class="metric_name">cronjob_controller_cronjob_job_creation_skew_duration_seconds</td>
-<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
-<td class="metric_type" data-type="histogram">Histogram</td>
-<td class="metric_description">Time between when a cronjob is scheduled to be run, and when the corresponding job is created</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">csi_operations_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Container Storage Interface operation duration with gRPC error code status total</td>
 <td class="metric_labels_varying"><div class="metric_label">driver_name</div><div class="metric_label">grpc_status_code</div><div class="metric_label">method_name</div><div class="metric_label">migrated</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">endpoint_slice_controller_changes</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of EndpointSlice changes</td>
 <td class="metric_labels_varying"><div class="metric_label">operation</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">endpoint_slice_controller_desired_endpoint_slices</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of EndpointSlices that would exist with perfect endpoint allocation</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">endpoint_slice_controller_endpoints_added_per_sync</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Number of endpoints added on each Service sync</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">endpoint_slice_controller_endpoints_desired</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of endpoints desired</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">endpoint_slice_controller_endpoints_removed_per_sync</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Number of endpoints removed on each Service sync</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">endpoint_slice_controller_endpointslices_changed_per_sync</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Number of EndpointSlices changed on each Service sync</td>
 <td class="metric_labels_varying"><div class="metric_label">topology</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">endpoint_slice_controller_num_endpoint_slices</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of EndpointSlices</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">endpoint_slice_controller_syncs</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of EndpointSlice syncs</td>
 <td class="metric_labels_varying"><div class="metric_label">result</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">endpoint_slice_mirroring_controller_addresses_skipped_per_sync</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Number of addresses skipped on each Endpoints sync due to being invalid or exceeding MaxEndpointsPerSubset</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">endpoint_slice_mirroring_controller_changes</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of EndpointSlice changes</td>
 <td class="metric_labels_varying"><div class="metric_label">operation</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">endpoint_slice_mirroring_controller_desired_endpoint_slices</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of EndpointSlices that would exist with perfect endpoint allocation</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">endpoint_slice_mirroring_controller_endpoints_added_per_sync</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Number of endpoints added on each Endpoints sync</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">endpoint_slice_mirroring_controller_endpoints_desired</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of endpoints desired</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">endpoint_slice_mirroring_controller_endpoints_removed_per_sync</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Number of endpoints removed on each Endpoints sync</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">endpoint_slice_mirroring_controller_endpoints_sync_duration</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Duration of syncEndpoints() in seconds</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">endpoint_slice_mirroring_controller_endpoints_updated_per_sync</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Number of endpoints updated on each Endpoints sync</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">endpoint_slice_mirroring_controller_num_endpoint_slices</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of EndpointSlices</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">ephemeral_volume_controller_create_failures_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of PersistenVolumeClaims creation requests</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">ephemeral_volume_controller_create_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of PersistenVolumeClaims creation requests</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">etcd_bookmark_counts</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of etcd bookmarks (progress notify events) split by kind.</td>
 <td class="metric_labels_varying"><div class="metric_label">resource</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">etcd_lease_object_counts</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Number of objects attached to a single etcd lease.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">etcd_request_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Etcd request latency in seconds for each operation and object type.</td>
 <td class="metric_labels_varying"><div class="metric_label">operation</div><div class="metric_label">type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">etcd_version_info</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Etcd server's binary version</td>
 <td class="metric_labels_varying"><div class="metric_label">binary_version</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">field_validation_request_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
-<td class="metric_description">Response latency distribution in seconds for each field validation value and whether field validation is enabled or not</td>
-<td class="metric_labels_varying"><div class="metric_label">enabled</div><div class="metric_label">field_validation</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_description">Response latency distribution in seconds for each field validation value</td>
+<td class="metric_labels_varying"><div class="metric_label">field_validation</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">force_cleaned_failed_volume_operation_errors_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">The number of volumes that failed force cleanup after their reconstruction failed during kubelet startup.</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">force_cleaned_failed_volume_operations_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">The number of volumes that were force cleaned after their reconstruction failed during kubelet startup. This includes both successful and failed cleanups.</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">garbagecollector_controller_resources_sync_error_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of garbage collector resources sync errors</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">get_token_count</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter of total Token() requests to the alternate token source</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">get_token_fail_count</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter of failed Token() requests to the alternate token source</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
-<tr class="metric"><td class="metric_name">job_controller_job_finished_total</td>
-<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
-<td class="metric_type" data-type="counter">Counter</td>
-<td class="metric_description">The number of finished job</td>
-<td class="metric_labels_varying"><div class="metric_label">completion_mode</div><div class="metric_label">reason</div><div class="metric_label">result</div></td>
-<td class="metric_labels_constant">None</td></tr>
-<tr class="metric"><td class="metric_name">job_controller_job_pods_finished_total</td>
-<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
-<td class="metric_type" data-type="counter">Counter</td>
-<td class="metric_description">The number of finished Pods that are fully tracked</td>
-<td class="metric_labels_varying"><div class="metric_label">completion_mode</div><div class="metric_label">result</div></td>
-<td class="metric_labels_constant">None</td></tr>
-<tr class="metric"><td class="metric_name">job_controller_job_sync_duration_seconds</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">horizontal_pod_autoscaler_controller_metric_computation_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
-<td class="metric_description">The time it took to sync a job</td>
-<td class="metric_labels_varying"><div class="metric_label">action</div><div class="metric_label">completion_mode</div><div class="metric_label">result</div></td>
-<td class="metric_labels_constant">None</td></tr>
-<tr class="metric"><td class="metric_name">job_controller_job_sync_total</td>
+<td class="metric_description">The time(seconds) that the HPA controller takes to calculate one metric. The label 'action' should be either 'scale_down', 'scale_up', or 'none'. The label 'error' should be either 'spec', 'internal', or 'none'. The label 'metric_type' corresponds to HPA.spec.metrics[*].type</td>
+<td class="metric_labels_varying"><div class="metric_label">action</div><div class="metric_label">error</div><div class="metric_label">metric_type</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">horizontal_pod_autoscaler_controller_metric_computation_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
-<td class="metric_description">The number of job syncs</td>
-<td class="metric_labels_varying"><div class="metric_label">action</div><div class="metric_label">completion_mode</div><div class="metric_label">result</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_description">Number of metric computations. The label 'action' should be either 'scale_down', 'scale_up', or 'none'. Also, the label 'error' should be either 'spec', 'internal', or 'none'. The label 'metric_type' corresponds to HPA.spec.metrics[*].type</td>
+<td class="metric_labels_varying"><div class="metric_label">action</div><div class="metric_label">error</div><div class="metric_label">metric_type</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">horizontal_pod_autoscaler_controller_reconciliation_duration_seconds</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="histogram">Histogram</td>
+<td class="metric_description">The time(seconds) that the HPA controller takes to reconcile once. The label 'action' should be either 'scale_down', 'scale_up', or 'none'. Also, the label 'error' should be either 'spec', 'internal', or 'none'. Note that if both spec and internal errors happen during a reconciliation, the first one to occur is reported in `error` label.</td>
+<td class="metric_labels_varying"><div class="metric_label">action</div><div class="metric_label">error</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">horizontal_pod_autoscaler_controller_reconciliations_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Number of reconciliations of HPA controller. The label 'action' should be either 'scale_down', 'scale_up', or 'none'. Also, the label 'error' should be either 'spec', 'internal', or 'none'. Note that if both spec and internal errors happen during a reconciliation, the first one to occur is reported in `error` label.</td>
+<td class="metric_labels_varying"><div class="metric_label">action</div><div class="metric_label">error</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">job_controller_pod_failures_handled_by_failure_policy_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">`The number of failed Pods handled by failure policy with, 			respect to the failure policy action applied based on the matched, 			rule. Possible values of the action label correspond to the, 			possible values for the failure policy rule action, which are:, 			"FailJob", "Ignore" and "Count".`</td>
 <td class="metric_labels_varying"><div class="metric_label">action</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">job_controller_terminated_pods_tracking_finalizer_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">`The number of terminated pods (phase=Failed|Succeeded), that have the finalizer batch.kubernetes.io/job-tracking, The event label can be "add" or "delete".`</td>
 <td class="metric_labels_varying"><div class="metric_label">event</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kube_apiserver_clusterip_allocator_allocated_ips</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Gauge measuring the number of allocated IPs for Services</td>
 <td class="metric_labels_varying"><div class="metric_label">cidr</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kube_apiserver_clusterip_allocator_allocation_errors_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of errors trying to allocate Cluster IPs</td>
 <td class="metric_labels_varying"><div class="metric_label">cidr</div><div class="metric_label">scope</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kube_apiserver_clusterip_allocator_allocation_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of Cluster IPs allocations</td>
 <td class="metric_labels_varying"><div class="metric_label">cidr</div><div class="metric_label">scope</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kube_apiserver_clusterip_allocator_available_ips</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Gauge measuring the number of available IPs for Services</td>
 <td class="metric_labels_varying"><div class="metric_label">cidr</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kube_apiserver_nodeport_allocator_allocated_ports</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">Gauge measuring the number of allocated NodePorts for Services</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kube_apiserver_nodeport_allocator_allocation_errors_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Number of errors trying to allocate NodePort</td>
+<td class="metric_labels_varying"><div class="metric_label">scope</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kube_apiserver_nodeport_allocator_allocation_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Number of NodePort allocations</td>
+<td class="metric_labels_varying"><div class="metric_label">scope</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kube_apiserver_nodeport_allocator_available_ports</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">Gauge measuring the number of available NodePorts for Services</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kube_apiserver_pod_logs_backend_tls_failure_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Total number of requests for pods/logs that failed due to kubelet server TLS verification</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kube_apiserver_pod_logs_insecure_backend_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Total number of requests for pods/logs sliced by usage type: enforce_tls, skip_tls_allowed, skip_tls_denied</td>
+<td class="metric_labels_varying"><div class="metric_label">usage</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kube_apiserver_pod_logs_pods_logs_backend_tls_failure_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Total number of requests for pods/logs that failed due to kubelet server TLS verification</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version">1.27.0</td></tr>
 <tr class="metric"><td class="metric_name">kube_apiserver_pod_logs_pods_logs_insecure_backend_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Total number of requests for pods/logs sliced by usage type: enforce_tls, skip_tls_allowed, skip_tls_denied</td>
 <td class="metric_labels_varying"><div class="metric_label">usage</div></td>
-<td class="metric_labels_constant">None</td></tr>
-<tr class="metric"><td class="metric_name">kube_pod_resource_limit</td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version">1.27.0</td></tr>
+<tr class="metric"><td class="metric_name">kubelet_active_pods</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
-<td class="metric_type" data-type="custom">Custom</td>
-<td class="metric_description">Resources limit for workloads on the cluster, broken down by pod. This shows the resource usage the scheduler and kubelet expect per pod for resources along with the unit for the resource if any.</td>
-<td class="metric_labels_varying"><div class="metric_label">namespace</div><div class="metric_label">pod</div><div class="metric_label">node</div><div class="metric_label">scheduler</div><div class="metric_label">priority</div><div class="metric_label">resource</div><div class="metric_label">unit</div></td>
-<td class="metric_labels_constant">None</td></tr>
-<tr class="metric"><td class="metric_name">kube_pod_resource_request</td>
-<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
-<td class="metric_type" data-type="custom">Custom</td>
-<td class="metric_description">Resources requested by workloads on the cluster, broken down by pod. This shows the resource usage the scheduler and kubelet expect per pod for resources along with the unit for the resource if any.</td>
-<td class="metric_labels_varying"><div class="metric_label">namespace</div><div class="metric_label">pod</div><div class="metric_label">node</div><div class="metric_label">scheduler</div><div class="metric_label">priority</div><div class="metric_label">resource</div><div class="metric_label">unit</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">The number of pods the kubelet considers active and which are being considered when admitting new pods. static is true if the pod is not from the apiserver.</td>
+<td class="metric_labels_varying"><div class="metric_label">static</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_certificate_manager_client_expiration_renew_errors</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter of certificate renewal errors.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_certificate_manager_client_ttl_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Gauge of the TTL (time-to-live) of the Kubelet's client certificate. The value is in seconds until certificate expiry (negative if already expired). If client certificate is invalid or unused, the value will be +INF.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_certificate_manager_server_rotation_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Histogram of the number of seconds the previous certificate lived before being rotated.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_certificate_manager_server_ttl_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Gauge of the shortest TTL (time-to-live) of the Kubelet's serving certificate. The value is in seconds until certificate expiry (negative if already expired). If serving certificate is invalid or unused, the value will be +INF.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_cgroup_manager_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Duration in seconds for cgroup manager operations. Broken down by method.</td>
 <td class="metric_labels_varying"><div class="metric_label">operation_type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_container_log_filesystem_used_bytes</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Bytes used by the container's logs on the filesystem.</td>
 <td class="metric_labels_varying"><div class="metric_label">uid</div><div class="metric_label">namespace</div><div class="metric_label">pod</div><div class="metric_label">container</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_containers_per_pod_count</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">The number of containers per pod.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_cpu_manager_pinning_errors_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">The number of cpu core allocations which required pinning failed.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_cpu_manager_pinning_requests_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">The number of cpu core allocations which required pinning.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kubelet_credential_provider_plugin_duration</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="histogram">Histogram</td>
+<td class="metric_description">Duration of execution in seconds for credential provider plugin</td>
+<td class="metric_labels_varying"><div class="metric_label">plugin_name</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kubelet_credential_provider_plugin_errors</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Number of errors from credential provider plugin</td>
+<td class="metric_labels_varying"><div class="metric_label">plugin_name</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kubelet_desired_pods</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">The number of pods the kubelet is being instructed to run. static is true if the pod is not from the apiserver.</td>
+<td class="metric_labels_varying"><div class="metric_label">static</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_device_plugin_alloc_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Duration in seconds to serve a device plugin Allocation request. Broken down by resource name.</td>
 <td class="metric_labels_varying"><div class="metric_label">resource_name</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_device_plugin_registration_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Cumulative number of device plugin registrations. Broken down by resource name.</td>
 <td class="metric_labels_varying"><div class="metric_label">resource_name</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kubelet_evented_pleg_connection_error_count</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">The number of errors encountered during the establishment of streaming connection with the CRI runtime.</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kubelet_evented_pleg_connection_latency_seconds</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="histogram">Histogram</td>
+<td class="metric_description">The latency of streaming connection with the CRI runtime, measured in seconds.</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kubelet_evented_pleg_connection_success_count</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">The number of times a streaming client was obtained to receive CRI Events.</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_eviction_stats_age_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Time between when stats are collected, and when pod is evicted based on those stats by eviction signal</td>
 <td class="metric_labels_varying"><div class="metric_label">eviction_signal</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_evictions</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Cumulative number of pod evictions by eviction signal</td>
 <td class="metric_labels_varying"><div class="metric_label">eviction_signal</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_graceful_shutdown_end_time_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Last graceful shutdown start time since unix epoch in seconds</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_graceful_shutdown_start_time_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Last graceful shutdown start time since unix epoch in seconds</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_http_inflight_requests</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of the inflight http requests</td>
 <td class="metric_labels_varying"><div class="metric_label">long_running</div><div class="metric_label">method</div><div class="metric_label">path</div><div class="metric_label">server_type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_http_requests_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Duration in seconds to serve http requests</td>
 <td class="metric_labels_varying"><div class="metric_label">long_running</div><div class="metric_label">method</div><div class="metric_label">path</div><div class="metric_label">server_type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_http_requests_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of the http requests received since the server started</td>
 <td class="metric_labels_varying"><div class="metric_label">long_running</div><div class="metric_label">method</div><div class="metric_label">path</div><div class="metric_label">server_type</div></td>
-<td class="metric_labels_constant">None</td></tr>
-<tr class="metric"><td class="metric_name">kubelet_kubelet_credential_provider_plugin_duration</td>
-<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
-<td class="metric_type" data-type="histogram">Histogram</td>
-<td class="metric_description">Duration of execution in seconds for credential provider plugin</td>
-<td class="metric_labels_varying"><div class="metric_label">plugin_name</div></td>
-<td class="metric_labels_constant">None</td></tr>
-<tr class="metric"><td class="metric_name">kubelet_kubelet_credential_provider_plugin_errors</td>
-<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
-<td class="metric_type" data-type="counter">Counter</td>
-<td class="metric_description">Number of errors from credential provider plugin</td>
-<td class="metric_labels_varying"><div class="metric_label">plugin_name</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_lifecycle_handler_http_fallbacks_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">The number of times lifecycle handlers successfully fell back to http from https.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_managed_ephemeral_containers</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
-<td class="metric_description">Current number of ephemeral containers in pods managed by this kubelet. Ephemeral containers will be ignored if disabled by the EphemeralContainers feature gate, and this number will be 0.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_description">Current number of ephemeral containers in pods managed by this kubelet.</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kubelet_mirror_pods</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">The number of mirror pods the kubelet will try to create (one per admitted static pod)</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_node_name</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">The node's name. The count is always 1.</td>
 <td class="metric_labels_varying"><div class="metric_label">node</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kubelet_orphan_pod_cleaned_volumes</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">The total number of orphaned Pods whose volumes were cleaned in the last periodic sweep.</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kubelet_orphan_pod_cleaned_volumes_errors</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">The number of orphaned Pods whose volumes failed to be cleaned in the last periodic sweep.</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kubelet_orphaned_runtime_pods_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Number of pods that have been detected in the container runtime without being already known to the pod worker. This typically indicates the kubelet was restarted while a pod was force deleted in the API or in the local configuration, which is unusual.</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_pleg_discard_events</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">The number of discard events in PLEG.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_pleg_last_seen_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Timestamp in seconds when PLEG was last seen active.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_pleg_relist_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Duration in seconds for relisting pods in PLEG.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_pleg_relist_interval_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Interval in seconds between relisting in PLEG.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kubelet_pod_resources_endpoint_errors_get</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Number of requests to the PodResource Get endpoint which returned error. Broken down by server api version.</td>
+<td class="metric_labels_varying"><div class="metric_label">server_api_version</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_pod_resources_endpoint_errors_get_allocatable</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of requests to the PodResource GetAllocatableResources endpoint which returned error. Broken down by server api version.</td>
 <td class="metric_labels_varying"><div class="metric_label">server_api_version</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_pod_resources_endpoint_errors_list</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of requests to the PodResource List endpoint which returned error. Broken down by server api version.</td>
 <td class="metric_labels_varying"><div class="metric_label">server_api_version</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kubelet_pod_resources_endpoint_requests_get</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Number of requests to the PodResource Get endpoint. Broken down by server api version.</td>
+<td class="metric_labels_varying"><div class="metric_label">server_api_version</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_pod_resources_endpoint_requests_get_allocatable</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of requests to the PodResource GetAllocatableResources endpoint. Broken down by server api version.</td>
 <td class="metric_labels_varying"><div class="metric_label">server_api_version</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_pod_resources_endpoint_requests_list</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of requests to the PodResource List endpoint. Broken down by server api version.</td>
 <td class="metric_labels_varying"><div class="metric_label">server_api_version</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_pod_resources_endpoint_requests_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Cumulative number of requests to the PodResource endpoint. Broken down by server api version.</td>
 <td class="metric_labels_varying"><div class="metric_label">server_api_version</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_pod_start_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Duration in seconds from kubelet seeing a pod for the first time to the pod starting to run</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kubelet_pod_start_sli_duration_seconds</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="histogram">Histogram</td>
+<td class="metric_description">Duration in seconds to start a pod, excluding time to pull images and run init containers, measured from pod creation timestamp to when all its containers are reported as started and observed via watch</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_pod_status_sync_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Duration in seconds to sync a pod status update. Measures time from detection of a change to pod status until the API is successfully updated for that pod, even if multiple intevening changes to pod status occur.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_pod_worker_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Duration in seconds to sync a single pod. Broken down by operation type: create, update, or sync</td>
 <td class="metric_labels_varying"><div class="metric_label">operation_type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_pod_worker_start_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Duration in seconds from kubelet seeing a pod to starting a worker.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_preemptions</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Cumulative number of pod preemptions by preemption resource</td>
 <td class="metric_labels_varying"><div class="metric_label">preemption_signal</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kubelet_restarted_pods_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Number of pods that have been restarted because they were deleted and recreated with the same UID while the kubelet was watching them (common for static pods, extremely uncommon for API pods)</td>
+<td class="metric_labels_varying"><div class="metric_label">static</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_run_podsandbox_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Duration in seconds of the run_podsandbox operations. Broken down by RuntimeClass.Handler.</td>
 <td class="metric_labels_varying"><div class="metric_label">runtime_handler</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_run_podsandbox_errors_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Cumulative number of the run_podsandbox operation errors by RuntimeClass.Handler.</td>
 <td class="metric_labels_varying"><div class="metric_label">runtime_handler</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_running_containers</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of containers currently running</td>
 <td class="metric_labels_varying"><div class="metric_label">container_state</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_running_pods</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of pods that have a running pod sandbox</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_runtime_operations_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Duration in seconds of runtime operations. Broken down by operation type.</td>
 <td class="metric_labels_varying"><div class="metric_label">operation_type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_runtime_operations_errors_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Cumulative number of runtime operation errors by operation type.</td>
 <td class="metric_labels_varying"><div class="metric_label">operation_type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_runtime_operations_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Cumulative number of runtime operations by operation type.</td>
 <td class="metric_labels_varying"><div class="metric_label">operation_type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_server_expiration_renew_errors</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter of certificate renewal errors.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_started_containers_errors_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Cumulative number of errors when starting containers</td>
 <td class="metric_labels_varying"><div class="metric_label">code</div><div class="metric_label">container_type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_started_containers_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Cumulative number of containers started</td>
 <td class="metric_labels_varying"><div class="metric_label">container_type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_started_host_process_containers_errors_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Cumulative number of errors when starting hostprocess containers. This metric will only be collected on Windows and requires WindowsHostProcessContainers feature gate to be enabled.</td>
 <td class="metric_labels_varying"><div class="metric_label">code</div><div class="metric_label">container_type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_started_host_process_containers_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Cumulative number of hostprocess containers started. This metric will only be collected on Windows and requires WindowsHostProcessContainers feature gate to be enabled.</td>
 <td class="metric_labels_varying"><div class="metric_label">container_type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_started_pods_errors_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Cumulative number of errors when starting pods</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_started_pods_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Cumulative number of pods started</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kubelet_topology_manager_admission_duration_ms</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="histogram">Histogram</td>
+<td class="metric_description">Duration in milliseconds to serve a pod admission request.</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kubelet_topology_manager_admission_errors_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">The number of admission request failures where resources could not be aligned.</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kubelet_topology_manager_admission_requests_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">The number of admission requests where resources have to be aligned.</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_volume_metric_collection_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Duration in seconds to calculate volume stats</td>
 <td class="metric_labels_varying"><div class="metric_label">metric_source</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_volume_stats_available_bytes</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Number of available bytes in the volume</td>
 <td class="metric_labels_varying"><div class="metric_label">namespace</div><div class="metric_label">persistentvolumeclaim</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_volume_stats_capacity_bytes</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Capacity in bytes of the volume</td>
 <td class="metric_labels_varying"><div class="metric_label">namespace</div><div class="metric_label">persistentvolumeclaim</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_volume_stats_health_status_abnormal</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Abnormal volume health status. The count is either 1 or 0. 1 indicates the volume is unhealthy, 0 indicates volume is healthy</td>
 <td class="metric_labels_varying"><div class="metric_label">namespace</div><div class="metric_label">persistentvolumeclaim</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_volume_stats_inodes</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Maximum number of inodes in the volume</td>
 <td class="metric_labels_varying"><div class="metric_label">namespace</div><div class="metric_label">persistentvolumeclaim</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_volume_stats_inodes_free</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Number of free inodes in the volume</td>
 <td class="metric_labels_varying"><div class="metric_label">namespace</div><div class="metric_label">persistentvolumeclaim</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_volume_stats_inodes_used</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Number of used inodes in the volume</td>
 <td class="metric_labels_varying"><div class="metric_label">namespace</div><div class="metric_label">persistentvolumeclaim</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubelet_volume_stats_used_bytes</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Number of used bytes in the volume</td>
 <td class="metric_labels_varying"><div class="metric_label">namespace</div><div class="metric_label">persistentvolumeclaim</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kubelet_working_pods</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">Number of pods the kubelet is actually running, broken down by lifecycle phase, whether the pod is desired, orphaned, or runtime only (also orphaned), and whether the pod is static. An orphaned pod has been removed from local configuration or force deleted in the API and consumes resources that are not otherwise visible.</td>
+<td class="metric_labels_varying"><div class="metric_label">config</div><div class="metric_label">lifecycle</div><div class="metric_label">static</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubeproxy_network_programming_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">In Cluster Network Programming Latency in seconds</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubeproxy_sync_proxy_rules_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">SyncProxyRules latency in seconds</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubeproxy_sync_proxy_rules_endpoint_changes_pending</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Pending proxy rules Endpoint changes</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubeproxy_sync_proxy_rules_endpoint_changes_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Cumulative proxy rules Endpoint changes</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">kubeproxy_sync_proxy_rules_iptables_partial_restore_failures_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Cumulative proxy iptables partial restore failures</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubeproxy_sync_proxy_rules_iptables_restore_failures_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Cumulative proxy iptables restore failures</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubeproxy_sync_proxy_rules_iptables_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of proxy iptables rules programmed</td>
 <td class="metric_labels_varying"><div class="metric_label">table</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubeproxy_sync_proxy_rules_last_queued_timestamp_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">The last time a sync of proxy rules was queued</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubeproxy_sync_proxy_rules_last_timestamp_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">The last time proxy rules were successfully synced</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubeproxy_sync_proxy_rules_no_local_endpoints_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of services with a Local traffic policy and no endpoints</td>
 <td class="metric_labels_varying"><div class="metric_label">traffic_policy</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubeproxy_sync_proxy_rules_service_changes_pending</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Pending proxy rules Service changes</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubeproxy_sync_proxy_rules_service_changes_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Cumulative proxy rules Service changes</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubernetes_build_info</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">A metric with a constant '1' value labeled by major, minor, git version, git commit, git tree state, build date, Go version, and compiler from which Kubernetes was built, and platform on which it is running.</td>
 <td class="metric_labels_varying"><div class="metric_label">build_date</div><div class="metric_label">compiler</div><div class="metric_label">git_commit</div><div class="metric_label">git_tree_state</div><div class="metric_label">git_version</div><div class="metric_label">go_version</div><div class="metric_label">major</div><div class="metric_label">minor</div><div class="metric_label">platform</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubernetes_feature_enabled</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">This metric records the data about the stage and enablement of a k8s feature.</td>
 <td class="metric_labels_varying"><div class="metric_label">name</div><div class="metric_label">stage</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubernetes_healthcheck</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">This metric records the result of a single healthcheck.</td>
 <td class="metric_labels_varying"><div class="metric_label">name</div><div class="metric_label">type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">kubernetes_healthchecks_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">This metric records the results of all healthcheck.</td>
 <td class="metric_labels_varying"><div class="metric_label">name</div><div class="metric_label">status</div><div class="metric_label">type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">leader_election_master_status</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Gauge of if the reporting system is master of the relevant lease, 0 indicates backup, 1 indicates master. 'name' is the string used to identify the lease. Please make sure to group by name.</td>
 <td class="metric_labels_varying"><div class="metric_label">name</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">node_authorizer_graph_actions_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Histogram of duration of graph actions in node authorizer.</td>
 <td class="metric_labels_varying"><div class="metric_label">operation</div></td>
-<td class="metric_labels_constant">None</td></tr>
-<tr class="metric"><td class="metric_name">node_collector_evictions_number</td>
-<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
-<td class="metric_type" data-type="counter">Counter</td>
-<td class="metric_description">Number of Node evictions that happened since current instance of NodeController started, This metric is replaced by node_collector_evictions_total.</td>
-<td class="metric_labels_varying"><div class="metric_label">zone</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">node_collector_unhealthy_nodes_in_zone</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Gauge measuring number of not Ready Nodes per zones.</td>
 <td class="metric_labels_varying"><div class="metric_label">zone</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">node_collector_update_all_nodes_health_duration_seconds</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="histogram">Histogram</td>
+<td class="metric_description">Duration in seconds for NodeController to update the health of all nodes.</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">node_collector_update_node_health_duration_seconds</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="histogram">Histogram</td>
+<td class="metric_description">Duration in seconds for NodeController to update the health of a single node.</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">node_collector_zone_health</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Gauge measuring percentage of healthy nodes per zone.</td>
 <td class="metric_labels_varying"><div class="metric_label">zone</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">node_collector_zone_size</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Gauge measuring number of registered Nodes per zones.</td>
 <td class="metric_labels_varying"><div class="metric_label">zone</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">node_cpu_usage_seconds_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Cumulative cpu time consumed by the node in core-seconds</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">node_ipam_controller_cidrset_allocation_tries_per_request</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Number of endpoints added on each Service sync</td>
 <td class="metric_labels_varying"><div class="metric_label">clusterCIDR</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">node_ipam_controller_cidrset_cidrs_allocations_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter measuring total number of CIDR allocations.</td>
 <td class="metric_labels_varying"><div class="metric_label">clusterCIDR</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">node_ipam_controller_cidrset_cidrs_releases_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter measuring total number of CIDR releases.</td>
 <td class="metric_labels_varying"><div class="metric_label">clusterCIDR</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">node_ipam_controller_cidrset_usage_cidrs</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Gauge measuring percentage of allocated CIDRs.</td>
 <td class="metric_labels_varying"><div class="metric_label">clusterCIDR</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">node_ipam_controller_cirdset_max_cidrs</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">Maximum number of CIDRs that can be allocated.</td>
+<td class="metric_labels_varying"><div class="metric_label">clusterCIDR</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">node_ipam_controller_multicidrset_allocation_tries_per_request</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Histogram measuring CIDR allocation tries per request.</td>
 <td class="metric_labels_varying"><div class="metric_label">clusterCIDR</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">node_ipam_controller_multicidrset_cidrs_allocations_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter measuring total number of CIDR allocations.</td>
 <td class="metric_labels_varying"><div class="metric_label">clusterCIDR</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">node_ipam_controller_multicidrset_cidrs_releases_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Counter measuring total number of CIDR releases.</td>
 <td class="metric_labels_varying"><div class="metric_label">clusterCIDR</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">node_ipam_controller_multicidrset_usage_cidrs</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Gauge measuring percentage of allocated CIDRs.</td>
 <td class="metric_labels_varying"><div class="metric_label">clusterCIDR</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">node_ipam_controller_multicirdset_max_cidrs</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="gauge">Gauge</td>
+<td class="metric_description">Maximum number of CIDRs that can be allocated.</td>
+<td class="metric_labels_varying"><div class="metric_label">clusterCIDR</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">node_memory_working_set_bytes</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Current working set of the node in bytes</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">number_of_l4_ilbs</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of L4 ILBs</td>
 <td class="metric_labels_varying"><div class="metric_label">feature</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">plugin_manager_total_plugins</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Number of plugins in Plugin Manager</td>
 <td class="metric_labels_varying"><div class="metric_label">socket_path</div><div class="metric_label">state</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">pod_cpu_usage_seconds_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Cumulative cpu time consumed by the pod in core-seconds</td>
 <td class="metric_labels_varying"><div class="metric_label">pod</div><div class="metric_label">namespace</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">pod_gc_collector_force_delete_pod_errors_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Number of errors encountered when forcefully deleting the pods since the Pod GC Controller started.</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">pod_gc_collector_force_delete_pods_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Number of pods that are being forcefully deleted since the Pod GC Controller started.</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">pod_memory_working_set_bytes</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Current working set of the pod in bytes</td>
 <td class="metric_labels_varying"><div class="metric_label">pod</div><div class="metric_label">namespace</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">pod_security_errors_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of errors preventing normal evaluation. Non-fatal errors may result in the latest restricted profile being used for evaluation.</td>
 <td class="metric_labels_varying"><div class="metric_label">fatal</div><div class="metric_label">request_operation</div><div class="metric_label">resource</div><div class="metric_label">subresource</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">pod_security_evaluations_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of policy evaluations that occurred, not counting ignored or exempt requests.</td>
 <td class="metric_labels_varying"><div class="metric_label">decision</div><div class="metric_label">mode</div><div class="metric_label">policy_level</div><div class="metric_label">policy_version</div><div class="metric_label">request_operation</div><div class="metric_label">resource</div><div class="metric_label">subresource</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">pod_security_exemptions_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of exempt requests, not counting ignored or out of scope requests.</td>
 <td class="metric_labels_varying"><div class="metric_label">request_operation</div><div class="metric_label">resource</div><div class="metric_label">subresource</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">prober_probe_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Duration in seconds for a probe response.</td>
 <td class="metric_labels_varying"><div class="metric_label">container</div><div class="metric_label">namespace</div><div class="metric_label">pod</div><div class="metric_label">probe_type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">prober_probe_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Cumulative number of a liveness, readiness or startup probe for a container by result.</td>
 <td class="metric_labels_varying"><div class="metric_label">container</div><div class="metric_label">namespace</div><div class="metric_label">pod</div><div class="metric_label">pod_uid</div><div class="metric_label">probe_type</div><div class="metric_label">result</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">pv_collector_bound_pv_count</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Gauge measuring number of persistent volume currently bound</td>
 <td class="metric_labels_varying"><div class="metric_label">storage_class</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">pv_collector_bound_pvc_count</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Gauge measuring number of persistent volume claim currently bound</td>
 <td class="metric_labels_varying"><div class="metric_label">namespace</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">pv_collector_total_pv_count</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Gauge measuring total number of persistent volumes</td>
 <td class="metric_labels_varying"><div class="metric_label">plugin_name</div><div class="metric_label">volume_mode</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">pv_collector_unbound_pv_count</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Gauge measuring number of persistent volume currently unbound</td>
 <td class="metric_labels_varying"><div class="metric_label">storage_class</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">pv_collector_unbound_pvc_count</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Gauge measuring number of persistent volume claim currently unbound</td>
 <td class="metric_labels_varying"><div class="metric_label">namespace</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">reconstruct_volume_operations_errors_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">The number of volumes that failed reconstruction from the operating system during kubelet startup.</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">reconstruct_volume_operations_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">The number of volumes that were attempted to be reconstructed from the operating system during kubelet startup. This includes both successful and failed reconstruction.</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">replicaset_controller_sorting_deletion_age_ratio</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">The ratio of chosen deleted pod's ages to the current youngest pod's age (at the time). Should be <2.The intent of this metric is to measure the rough efficacy of the LogarithmicScaleDown feature gate's effect onthe sorting (and deletion) of pods when a replicaset scales down. This only considers Ready pods when calculating and reporting.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">resourceclaim_controller_create_attempts_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Number of ResourceClaims creation requests</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">resourceclaim_controller_create_failures_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Number of ResourceClaims creation request failures</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">rest_client_exec_plugin_call_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of calls to an exec plugin, partitioned by the type of event encountered (no_error, plugin_execution_error, plugin_not_found_error, client_internal_error) and an optional exit code. The exit code will be set to 0 if and only if the plugin call was successful.</td>
 <td class="metric_labels_varying"><div class="metric_label">call_status</div><div class="metric_label">code</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">rest_client_exec_plugin_certificate_rotation_age</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Histogram of the number of seconds the last auth exec plugin client certificate lived before being rotated. If auth exec plugin client certificates are unused, histogram will contain no data.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">rest_client_exec_plugin_ttl_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Gauge of the shortest TTL (time-to-live) of the client certificate(s) managed by the auth exec plugin. The value is in seconds until certificate expiry (negative if already expired). If auth exec plugins are unused or manage no TLS certificates, the value will be +INF.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">rest_client_rate_limiter_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Client side rate limiter latency in seconds. Broken down by verb, and host.</td>
 <td class="metric_labels_varying"><div class="metric_label">host</div><div class="metric_label">verb</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">rest_client_request_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Request latency in seconds. Broken down by verb, and host.</td>
 <td class="metric_labels_varying"><div class="metric_label">host</div><div class="metric_label">verb</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">rest_client_request_retries_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Number of request retries, partitioned by status code, verb, and host.</td>
+<td class="metric_labels_varying"><div class="metric_label">code</div><div class="metric_label">host</div><div class="metric_label">verb</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">rest_client_request_size_bytes</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Request size in bytes. Broken down by verb and host.</td>
 <td class="metric_labels_varying"><div class="metric_label">host</div><div class="metric_label">verb</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">rest_client_requests_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of HTTP requests, partitioned by status code, method, and host.</td>
 <td class="metric_labels_varying"><div class="metric_label">code</div><div class="metric_label">host</div><div class="metric_label">method</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">rest_client_response_size_bytes</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Response size in bytes. Broken down by verb and host.</td>
 <td class="metric_labels_varying"><div class="metric_label">host</div><div class="metric_label">verb</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">retroactive_storageclass_errors_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Total number of failed retroactive StorageClass assignments to persistent volume claim</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">retroactive_storageclass_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Total number of retroactive StorageClass assignments to persistent volume claim</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">root_ca_cert_publisher_sync_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Number of namespace syncs happened in root ca cert publisher.</td>
 <td class="metric_labels_varying"><div class="metric_label">code</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">root_ca_cert_publisher_sync_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Number of namespace syncs happened in root ca cert publisher.</td>
 <td class="metric_labels_varying"><div class="metric_label">code</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">running_managed_controllers</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Indicates where instances of a controller are currently running</td>
 <td class="metric_labels_varying"><div class="metric_label">manager</div><div class="metric_label">name</div></td>
-<td class="metric_labels_constant">None</td></tr>
-<tr class="metric"><td class="metric_name">scheduler_e2e_scheduling_duration_seconds</td>
-<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
-<td class="metric_type" data-type="histogram">Histogram</td>
-<td class="metric_description">E2e scheduling latency in seconds (scheduling algorithm + binding). This metric is replaced by scheduling_attempt_duration_seconds.</td>
-<td class="metric_labels_varying"><div class="metric_label">profile</div><div class="metric_label">result</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">scheduler_goroutines</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of running goroutines split by the work they do such as binding.</td>
 <td class="metric_labels_varying"><div class="metric_label">operation</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">scheduler_permit_wait_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Duration of waiting on permit.</td>
 <td class="metric_labels_varying"><div class="metric_label">result</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">scheduler_plugin_evaluation_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">Number of attempts to schedule pods by each plugin and the extension point (available only in PreFilter and Filter.).</td>
+<td class="metric_labels_varying"><div class="metric_label">extension_point</div><div class="metric_label">plugin</div><div class="metric_label">profile</div></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">scheduler_plugin_execution_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Duration for running a plugin at a specific extension point.</td>
 <td class="metric_labels_varying"><div class="metric_label">extension_point</div><div class="metric_label">plugin</div><div class="metric_label">status</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">scheduler_scheduler_cache_size</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of nodes, pods, and assumed (bound) pods in the scheduler cache.</td>
 <td class="metric_labels_varying"><div class="metric_label">type</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">scheduler_scheduler_goroutines</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of running goroutines split by the work they do such as binding. This metric is replaced by the \"goroutines\" metric.</td>
 <td class="metric_labels_varying"><div class="metric_label">work</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version">1.26.0</td></tr>
 <tr class="metric"><td class="metric_name">scheduler_scheduling_algorithm_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Scheduling algorithm latency in seconds</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">scheduler_unschedulable_pods</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">The number of unschedulable pods broken down by plugin name. A pod will increment the gauge for all plugins that caused it to not schedule and so this metric have meaning only when broken down by plugin.</td>
 <td class="metric_labels_varying"><div class="metric_label">plugin</div><div class="metric_label">profile</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">scheduler_volume_binder_cache_requests_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Total number for request volume binding cache</td>
 <td class="metric_labels_varying"><div class="metric_label">operation</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">scheduler_volume_scheduling_stage_error_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Volume scheduling stage error count</td>
 <td class="metric_labels_varying"><div class="metric_label">operation</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">scrape_error</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">1 if there was an error while getting container metrics, 0 otherwise</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">service_controller_loadbalancer_sync_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">A metric counting the amount of times any load balancer has been configured, as an effect of service/node changes on the cluster</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
+<tr class="metric"><td class="metric_name">service_controller_nodesync_error_total</td>
+<td class="metric_stability_level" data-stability="alpha">ALPHA</td>
+<td class="metric_type" data-type="counter">Counter</td>
+<td class="metric_description">A metric counting the amount of times any load balancer has been configured and errored, as an effect of node changes on the cluster</td>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">service_controller_nodesync_latency_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">A metric measuring the latency for nodesync which updates loadbalancer hosts on cluster node updates.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">service_controller_update_loadbalancer_host_latency_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">A metric measuring the latency for updating each load balancer hosts.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">serviceaccount_legacy_tokens_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Cumulative legacy service account tokens used</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">serviceaccount_stale_tokens_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Cumulative stale projected service account tokens used</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">serviceaccount_valid_tokens_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Cumulative valid projected service account tokens used</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">storage_count_attachable_volumes_in_use</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Measure number of volumes in use</td>
 <td class="metric_labels_varying"><div class="metric_label">node</div><div class="metric_label">volume_plugin</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">storage_operation_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Storage operation duration</td>
 <td class="metric_labels_varying"><div class="metric_label">migrated</div><div class="metric_label">operation_name</div><div class="metric_label">status</div><div class="metric_label">volume_plugin</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">ttl_after_finished_controller_job_deletion_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">The time it took to delete the job since it became eligible for deletion</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">volume_manager_selinux_container_errors_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of errors when kubelet cannot compute SELinux context for a container. Kubelet can't start such a Pod then and it will retry, therefore value of this metric may not represent the actual nr. of containers.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">volume_manager_selinux_container_warnings_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of errors when kubelet cannot compute SELinux context for a container that are ignored. They will become real errors when SELinuxMountReadWriteOncePod feature is expanded to all volume access modes.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">volume_manager_selinux_pod_context_mismatch_errors_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of errors when a Pod defines different SELinux contexts for its containers that use the same volume. Kubelet can't start such a Pod then and it will retry, therefore value of this metric may not represent the actual nr. of Pods.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">volume_manager_selinux_pod_context_mismatch_warnings_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of errors when a Pod defines different SELinux contexts for its containers that use the same volume. They are not errors yet, but they will become real errors when SELinuxMountReadWriteOncePod feature is expanded to all volume access modes.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">volume_manager_selinux_volume_context_mismatch_errors_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of errors when a Pod uses a volume that is already mounted with a different SELinux context than the Pod needs. Kubelet can't start such a Pod then and it will retry, therefore value of this metric may not represent the actual nr. of Pods.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">volume_manager_selinux_volume_context_mismatch_warnings_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of errors when a Pod uses a volume that is already mounted with a different SELinux context than the Pod needs. They are not errors yet, but they will become real errors when SELinuxMountReadWriteOncePod feature is expanded to all volume access modes.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">volume_manager_selinux_volumes_admitted_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Number of volumes whose SELinux context was fine and will be mounted with mount -o context option.</td>
-<td class="metric_labels_varying">None</td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_varying"></td>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">volume_manager_total_volumes</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="custom">Custom</td>
 <td class="metric_description">Number of volumes in Volume Manager</td>
 <td class="metric_labels_varying"><div class="metric_label">plugin_name</div><div class="metric_label">state</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">volume_operation_total_errors</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Total volume operation errors</td>
 <td class="metric_labels_varying"><div class="metric_label">operation_name</div><div class="metric_label">plugin_name</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">volume_operation_total_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">Storage operation end to end duration in seconds</td>
 <td class="metric_labels_varying"><div class="metric_label">operation_name</div><div class="metric_label">plugin_name</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">watch_cache_capacity</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Total capacity of watch cache broken by resource type.</td>
 <td class="metric_labels_varying"><div class="metric_label">resource</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">watch_cache_capacity_decrease_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Total number of watch cache capacity decrease events broken by resource type.</td>
 <td class="metric_labels_varying"><div class="metric_label">resource</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">watch_cache_capacity_increase_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Total number of watch cache capacity increase events broken by resource type.</td>
 <td class="metric_labels_varying"><div class="metric_label">resource</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">workqueue_adds_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Total number of adds handled by workqueue</td>
 <td class="metric_labels_varying"><div class="metric_label">name</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">workqueue_depth</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">Current depth of workqueue</td>
 <td class="metric_labels_varying"><div class="metric_label">name</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">workqueue_longest_running_processor_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">How many seconds has the longest running processor for workqueue been running.</td>
 <td class="metric_labels_varying"><div class="metric_label">name</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">workqueue_queue_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">How long in seconds an item stays in workqueue before being requested.</td>
 <td class="metric_labels_varying"><div class="metric_label">name</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">workqueue_retries_total</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="counter">Counter</td>
 <td class="metric_description">Total number of retries handled by workqueue</td>
 <td class="metric_labels_varying"><div class="metric_label">name</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">workqueue_unfinished_work_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="gauge">Gauge</td>
 <td class="metric_description">How many seconds of work has done that is in progress and hasn't been observed by work_duration. Large values indicate stuck threads. One can deduce the number of stuck threads by observing the rate at which this increases.</td>
 <td class="metric_labels_varying"><div class="metric_label">name</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 <tr class="metric"><td class="metric_name">workqueue_work_duration_seconds</td>
 <td class="metric_stability_level" data-stability="alpha">ALPHA</td>
 <td class="metric_type" data-type="histogram">Histogram</td>
 <td class="metric_description">How long in seconds processing an item from workqueue takes.</td>
 <td class="metric_labels_varying"><div class="metric_label">name</div></td>
-<td class="metric_labels_constant">None</td></tr>
+<td class="metric_labels_constant"></td>
+<td class="metric_deprecated_version"></td></tr>
 </tbody>
 </table>

From 6054c6c8d282f0bd59d8f0b39e8e12b7875a58bb Mon Sep 17 00:00:00 2001
From: ystkfujii <ystk.fujii0731@gmail.com>
Date: Wed, 29 Mar 2023 01:19:27 +0900
Subject: [PATCH 063/272] [ja] remove IdentifyPodOS in feature-gates

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

diff --git a/content/ja/docs/reference/command-line-tools-reference/feature-gates.md b/content/ja/docs/reference/command-line-tools-reference/feature-gates.md
index 436a80752da..153bd8fb104 100644
--- a/content/ja/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/ja/docs/reference/command-line-tools-reference/feature-gates.md
@@ -264,9 +264,6 @@ content_type: concept
 | `ExpandPersistentVolumes` | `false` | Alpha | 1.8 | 1.10 |
 | `ExpandPersistentVolumes` | `true` | Beta | 1.11 | 1.23 |
 | `ExpandPersistentVolumes` | `true` | GA | 1.24 |- |
-| `IdentifyPodOS` | `false` | Alpha | 1.23 | 1.23 |
-| `IdentifyPodOS` | `true` | Beta | 1.24 | 1.24 |
-| `IdentifyPodOS` | `true` | GA | 1.25 | - |
 | `JobTrackingWithFinalizers` | `false` | Alpha | 1.22 | 1.22 |
 | `JobTrackingWithFinalizers` | `false` | Beta | 1.23 | 1.24 |
 | `JobTrackingWithFinalizers` | `true` | Beta | 1.25 | 1.25 |

From 7168071c756138180001d48f8c36a6908e84d247 Mon Sep 17 00:00:00 2001
From: Alexander Zielenski <351783+alexzielenski@users.noreply.github.com>
Date: Tue, 21 Mar 2023 14:55:55 -0700
Subject: [PATCH 065/272] regenerate cli docs

---
 .../generated/kubectl/kubectl-commands.html   | 1270 ++++++-----------
 .../reference/generated/kubectl/navData.js    |    2 +-
 .../jquery.scrollto/jquery.scrollTo.min.js    |   14 +-
 .../node_modules/jquery/dist/jquery.min.js    |    4 +-
 4 files changed, 411 insertions(+), 879 deletions(-)

diff --git a/static/docs/reference/generated/kubectl/kubectl-commands.html b/static/docs/reference/generated/kubectl/kubectl-commands.html
index d2a59477231..4fff80b171a 100644
--- a/static/docs/reference/generated/kubectl/kubectl-commands.html
+++ b/static/docs/reference/generated/kubectl/kubectl-commands.html
@@ -12,7 +12,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 </head>
 <body>
-<div id="sidebar-wrapper" class="side-nav side-bar-nav"><ul><li class="nav-level-1 strong-nav"><a href="#-strong-getting-started-strong-" class="nav-item"><strong>GETTING STARTED</strong></a></li></ul><ul><li class="nav-level-1"><a href="#create" class="nav-item">create</a></li><ul id="create-nav" style="display: none;"><li class="nav-level-2"><a href="#-em-clusterrole-em-" class="nav-item"><em>clusterrole</em></a></li><li class="nav-level-2"><a href="#-em-clusterrolebinding-em-" class="nav-item"><em>clusterrolebinding</em></a></li><li class="nav-level-2"><a href="#-em-configmap-em-" class="nav-item"><em>configmap</em></a></li><li class="nav-level-2"><a href="#-em-cronjob-em-" class="nav-item"><em>cronjob</em></a></li><li class="nav-level-2"><a href="#-em-deployment-em-" class="nav-item"><em>deployment</em></a></li><li class="nav-level-2"><a href="#-em-ingress-em-" class="nav-item"><em>ingress</em></a></li><li class="nav-level-2"><a href="#-em-job-em-" class="nav-item"><em>job</em></a></li><li class="nav-level-2"><a href="#-em-namespace-em-" class="nav-item"><em>namespace</em></a></li><li class="nav-level-2"><a href="#-em-poddisruptionbudget-em-" class="nav-item"><em>poddisruptionbudget</em></a></li><li class="nav-level-2"><a href="#-em-priorityclass-em-" class="nav-item"><em>priorityclass</em></a></li><li class="nav-level-2"><a href="#-em-quota-em-" class="nav-item"><em>quota</em></a></li><li class="nav-level-2"><a href="#-em-role-em-" class="nav-item"><em>role</em></a></li><li class="nav-level-2"><a href="#-em-rolebinding-em-" class="nav-item"><em>rolebinding</em></a></li><li class="nav-level-2"><a href="#-em-secret-em-" class="nav-item"><em>secret</em></a></li><li class="nav-level-2"><a href="#-em-secret-docker-registry-em-" class="nav-item"><em>secret docker-registry</em></a></li><li class="nav-level-2"><a href="#-em-secret-generic-em-" class="nav-item"><em>secret generic</em></a></li><li class="nav-level-2"><a href="#-em-secret-tls-em-" class="nav-item"><em>secret tls</em></a></li><li class="nav-level-2"><a href="#-em-service-em-" class="nav-item"><em>service</em></a></li><li class="nav-level-2"><a href="#-em-service-clusterip-em-" class="nav-item"><em>service clusterip</em></a></li><li class="nav-level-2"><a href="#-em-service-externalname-em-" class="nav-item"><em>service externalname</em></a></li><li class="nav-level-2"><a href="#-em-service-loadbalancer-em-" class="nav-item"><em>service loadbalancer</em></a></li><li class="nav-level-2"><a href="#-em-service-nodeport-em-" class="nav-item"><em>service nodeport</em></a></li><li class="nav-level-2"><a href="#-em-serviceaccount-em-" class="nav-item"><em>serviceaccount</em></a></li><li class="nav-level-2"><a href="#-em-token-em-" class="nav-item"><em>token</em></a></li></ul></ul><ul><li class="nav-level-1"><a href="#get" class="nav-item">get</a></li></ul><ul><li class="nav-level-1"><a href="#run" class="nav-item">run</a></li></ul><ul><li class="nav-level-1"><a href="#expose" class="nav-item">expose</a></li></ul><ul><li class="nav-level-1"><a href="#delete" class="nav-item">delete</a></li></ul><ul><li class="nav-level-1 strong-nav"><a href="#-strong-app-management-strong-" class="nav-item"><strong>APP MANAGEMENT</strong></a></li></ul><ul><li class="nav-level-1"><a href="#apply" class="nav-item">apply</a></li><ul id="apply-nav" style="display: none;"><li class="nav-level-2"><a href="#-em-edit-last-applied-em-" class="nav-item"><em>edit-last-applied</em></a></li><li class="nav-level-2"><a href="#-em-set-last-applied-em-" class="nav-item"><em>set-last-applied</em></a></li><li class="nav-level-2"><a href="#-em-view-last-applied-em-" class="nav-item"><em>view-last-applied</em></a></li></ul></ul><ul><li class="nav-level-1"><a href="#annotate" class="nav-item">annotate</a></li></ul><ul><li class="nav-level-1"><a href="#autoscale" class="nav-item">autoscale</a></li></ul><ul><li class="nav-level-1"><a href="#debug" class="nav-item">debug</a></li></ul><ul><li class="nav-level-1"><a href="#diff" class="nav-item">diff</a></li></ul><ul><li class="nav-level-1"><a href="#edit" class="nav-item">edit</a></li></ul><ul><li class="nav-level-1"><a href="#kustomize" class="nav-item">kustomize</a></li></ul><ul><li class="nav-level-1"><a href="#label" class="nav-item">label</a></li></ul><ul><li class="nav-level-1"><a href="#patch" class="nav-item">patch</a></li></ul><ul><li class="nav-level-1"><a href="#replace" class="nav-item">replace</a></li></ul><ul><li class="nav-level-1"><a href="#rollout" class="nav-item">rollout</a></li><ul id="rollout-nav" style="display: none;"><li class="nav-level-2"><a href="#-em-history-em-" class="nav-item"><em>history</em></a></li><li class="nav-level-2"><a href="#-em-pause-em-" class="nav-item"><em>pause</em></a></li><li class="nav-level-2"><a href="#-em-restart-em-" class="nav-item"><em>restart</em></a></li><li class="nav-level-2"><a href="#-em-resume-em-" class="nav-item"><em>resume</em></a></li><li class="nav-level-2"><a href="#-em-status-em-" class="nav-item"><em>status</em></a></li><li class="nav-level-2"><a href="#-em-undo-em-" class="nav-item"><em>undo</em></a></li></ul></ul><ul><li class="nav-level-1"><a href="#scale" class="nav-item">scale</a></li></ul><ul><li class="nav-level-1"><a href="#set" class="nav-item">set</a></li><ul id="set-nav" style="display: none;"><li class="nav-level-2"><a href="#-em-env-em-" class="nav-item"><em>env</em></a></li><li class="nav-level-2"><a href="#-em-image-em-" class="nav-item"><em>image</em></a></li><li class="nav-level-2"><a href="#-em-resources-em-" class="nav-item"><em>resources</em></a></li><li class="nav-level-2"><a href="#-em-selector-em-" class="nav-item"><em>selector</em></a></li><li class="nav-level-2"><a href="#-em-serviceaccount-em--1" class="nav-item"><em>serviceaccount</em></a></li><li class="nav-level-2"><a href="#-em-subject-em-" class="nav-item"><em>subject</em></a></li></ul></ul><ul><li class="nav-level-1"><a href="#wait" class="nav-item">wait</a></li></ul><ul><li class="nav-level-1 strong-nav"><a href="#-strong-working-with-apps-strong-" class="nav-item"><strong>WORKING WITH APPS</strong></a></li></ul><ul><li class="nav-level-1"><a href="#attach" class="nav-item">attach</a></li></ul><ul><li class="nav-level-1"><a href="#auth" class="nav-item">auth</a></li><ul id="auth-nav" style="display: none;"><li class="nav-level-2"><a href="#-em-can-i-em-" class="nav-item"><em>can-i</em></a></li><li class="nav-level-2"><a href="#-em-reconcile-em-" class="nav-item"><em>reconcile</em></a></li></ul></ul><ul><li class="nav-level-1"><a href="#cp" class="nav-item">cp</a></li></ul><ul><li class="nav-level-1"><a href="#describe" class="nav-item">describe</a></li></ul><ul><li class="nav-level-1"><a href="#events" class="nav-item">events</a></li></ul><ul><li class="nav-level-1"><a href="#exec" class="nav-item">exec</a></li></ul><ul><li class="nav-level-1"><a href="#logs" class="nav-item">logs</a></li></ul><ul><li class="nav-level-1"><a href="#port-forward" class="nav-item">port-forward</a></li></ul><ul><li class="nav-level-1"><a href="#proxy" class="nav-item">proxy</a></li></ul><ul><li class="nav-level-1"><a href="#top" class="nav-item">top</a></li><ul id="top-nav" style="display: none;"><li class="nav-level-2"><a href="#-em-node-em-" class="nav-item"><em>node</em></a></li><li class="nav-level-2"><a href="#-em-pod-em-" class="nav-item"><em>pod</em></a></li></ul></ul><ul><li class="nav-level-1 strong-nav"><a href="#-strong-cluster-management-strong-" class="nav-item"><strong>CLUSTER MANAGEMENT</strong></a></li></ul><ul><li class="nav-level-1"><a href="#api-versions" class="nav-item">api-versions</a></li></ul><ul><li class="nav-level-1"><a href="#api-resources" class="nav-item">api-resources</a></li></ul><ul><li class="nav-level-1"><a href="#certificate" class="nav-item">certificate</a></li><ul id="certificate-nav" style="display: none;"><li class="nav-level-2"><a href="#-em-approve-em-" class="nav-item"><em>approve</em></a></li><li class="nav-level-2"><a href="#-em-deny-em-" class="nav-item"><em>deny</em></a></li></ul></ul><ul><li class="nav-level-1"><a href="#cluster-info" class="nav-item">cluster-info</a></li><ul id="cluster-info-nav" style="display: none;"><li class="nav-level-2"><a href="#-em-dump-em-" class="nav-item"><em>dump</em></a></li></ul></ul><ul><li class="nav-level-1"><a href="#cordon" class="nav-item">cordon</a></li></ul><ul><li class="nav-level-1"><a href="#drain" class="nav-item">drain</a></li></ul><ul><li class="nav-level-1"><a href="#taint" class="nav-item">taint</a></li></ul><ul><li class="nav-level-1"><a href="#uncordon" class="nav-item">uncordon</a></li></ul><ul><li class="nav-level-1 strong-nav"><a href="#-strong-kubectl-settings-and-usage-strong-" class="nav-item"><strong>KUBECTL SETTINGS AND USAGE</strong></a></li></ul><ul><li class="nav-level-1"><a href="#alpha" class="nav-item">alpha</a></li><ul id="alpha-nav" style="display: none;"><li class="nav-level-2"><a href="#-em-auth-em-" class="nav-item"><em>auth</em></a></li><li class="nav-level-2"><a href="#-em-auth-whoami-em-" class="nav-item"><em>auth whoami</em></a></li></ul></ul><ul><li class="nav-level-1"><a href="#completion" class="nav-item">completion</a></li></ul><ul><li class="nav-level-1"><a href="#config" class="nav-item">config</a></li><ul id="config-nav" style="display: none;"><li class="nav-level-2"><a href="#-em-current-context-em-" class="nav-item"><em>current-context</em></a></li><li class="nav-level-2"><a href="#-em-delete-cluster-em-" class="nav-item"><em>delete-cluster</em></a></li><li class="nav-level-2"><a href="#-em-delete-context-em-" class="nav-item"><em>delete-context</em></a></li><li class="nav-level-2"><a href="#-em-delete-user-em-" class="nav-item"><em>delete-user</em></a></li><li class="nav-level-2"><a href="#-em-get-clusters-em-" class="nav-item"><em>get-clusters</em></a></li><li class="nav-level-2"><a href="#-em-get-contexts-em-" class="nav-item"><em>get-contexts</em></a></li><li class="nav-level-2"><a href="#-em-get-users-em-" class="nav-item"><em>get-users</em></a></li><li class="nav-level-2"><a href="#-em-rename-context-em-" class="nav-item"><em>rename-context</em></a></li><li class="nav-level-2"><a href="#-em-set-em-" class="nav-item"><em>set</em></a></li><li class="nav-level-2"><a href="#-em-set-cluster-em-" class="nav-item"><em>set-cluster</em></a></li><li class="nav-level-2"><a href="#-em-set-context-em-" class="nav-item"><em>set-context</em></a></li><li class="nav-level-2"><a href="#-em-set-credentials-em-" class="nav-item"><em>set-credentials</em></a></li><li class="nav-level-2"><a href="#-em-unset-em-" class="nav-item"><em>unset</em></a></li><li class="nav-level-2"><a href="#-em-use-context-em-" class="nav-item"><em>use-context</em></a></li><li class="nav-level-2"><a href="#-em-view-em-" class="nav-item"><em>view</em></a></li></ul></ul><ul><li class="nav-level-1"><a href="#explain" class="nav-item">explain</a></li></ul><ul><li class="nav-level-1"><a href="#options" class="nav-item">options</a></li></ul><ul><li class="nav-level-1"><a href="#plugin" class="nav-item">plugin</a></li><ul id="plugin-nav" style="display: none;"><li class="nav-level-2"><a href="#-em-list-em-" class="nav-item"><em>list</em></a></li></ul></ul><ul><li class="nav-level-1"><a href="#version" class="nav-item">version</a></li></ul><br/><div class="copyright"><a href="https://github.com/kubernetes/kubernetes">Copyright 2020 The Kubernetes Authors.</a></div></div>
+<div id="sidebar-wrapper" class="side-nav side-bar-nav"><ul><li class="nav-level-1 strong-nav"><a href="#-strong-getting-started-strong-" class="nav-item"><strong>GETTING STARTED</strong></a></li></ul><ul><li class="nav-level-1"><a href="#create" class="nav-item">create</a></li><ul id="create-nav" style="display: none;"><li class="nav-level-2"><a href="#-em-clusterrole-em-" class="nav-item"><em>clusterrole</em></a></li><li class="nav-level-2"><a href="#-em-clusterrolebinding-em-" class="nav-item"><em>clusterrolebinding</em></a></li><li class="nav-level-2"><a href="#-em-configmap-em-" class="nav-item"><em>configmap</em></a></li><li class="nav-level-2"><a href="#-em-cronjob-em-" class="nav-item"><em>cronjob</em></a></li><li class="nav-level-2"><a href="#-em-deployment-em-" class="nav-item"><em>deployment</em></a></li><li class="nav-level-2"><a href="#-em-ingress-em-" class="nav-item"><em>ingress</em></a></li><li class="nav-level-2"><a href="#-em-job-em-" class="nav-item"><em>job</em></a></li><li class="nav-level-2"><a href="#-em-namespace-em-" class="nav-item"><em>namespace</em></a></li><li class="nav-level-2"><a href="#-em-poddisruptionbudget-em-" class="nav-item"><em>poddisruptionbudget</em></a></li><li class="nav-level-2"><a href="#-em-priorityclass-em-" class="nav-item"><em>priorityclass</em></a></li><li class="nav-level-2"><a href="#-em-quota-em-" class="nav-item"><em>quota</em></a></li><li class="nav-level-2"><a href="#-em-role-em-" class="nav-item"><em>role</em></a></li><li class="nav-level-2"><a href="#-em-rolebinding-em-" class="nav-item"><em>rolebinding</em></a></li><li class="nav-level-2"><a href="#-em-secret-em-" class="nav-item"><em>secret</em></a></li><li class="nav-level-2"><a href="#-em-secret-docker-registry-em-" class="nav-item"><em>secret docker-registry</em></a></li><li class="nav-level-2"><a href="#-em-secret-generic-em-" class="nav-item"><em>secret generic</em></a></li><li class="nav-level-2"><a href="#-em-secret-tls-em-" class="nav-item"><em>secret tls</em></a></li><li class="nav-level-2"><a href="#-em-service-em-" class="nav-item"><em>service</em></a></li><li class="nav-level-2"><a href="#-em-service-clusterip-em-" class="nav-item"><em>service clusterip</em></a></li><li class="nav-level-2"><a href="#-em-service-externalname-em-" class="nav-item"><em>service externalname</em></a></li><li class="nav-level-2"><a href="#-em-service-loadbalancer-em-" class="nav-item"><em>service loadbalancer</em></a></li><li class="nav-level-2"><a href="#-em-service-nodeport-em-" class="nav-item"><em>service nodeport</em></a></li><li class="nav-level-2"><a href="#-em-serviceaccount-em-" class="nav-item"><em>serviceaccount</em></a></li></ul></ul><ul><li class="nav-level-1"><a href="#get" class="nav-item">get</a></li></ul><ul><li class="nav-level-1"><a href="#run" class="nav-item">run</a></li></ul><ul><li class="nav-level-1"><a href="#expose" class="nav-item">expose</a></li></ul><ul><li class="nav-level-1"><a href="#delete" class="nav-item">delete</a></li></ul><ul><li class="nav-level-1 strong-nav"><a href="#-strong-app-management-strong-" class="nav-item"><strong>APP MANAGEMENT</strong></a></li></ul><ul><li class="nav-level-1"><a href="#apply" class="nav-item">apply</a></li><ul id="apply-nav" style="display: none;"><li class="nav-level-2"><a href="#-em-edit-last-applied-em-" class="nav-item"><em>edit-last-applied</em></a></li><li class="nav-level-2"><a href="#-em-set-last-applied-em-" class="nav-item"><em>set-last-applied</em></a></li><li class="nav-level-2"><a href="#-em-view-last-applied-em-" class="nav-item"><em>view-last-applied</em></a></li></ul></ul><ul><li class="nav-level-1"><a href="#annotate" class="nav-item">annotate</a></li></ul><ul><li class="nav-level-1"><a href="#autoscale" class="nav-item">autoscale</a></li></ul><ul><li class="nav-level-1"><a href="#debug" class="nav-item">debug</a></li></ul><ul><li class="nav-level-1"><a href="#diff" class="nav-item">diff</a></li></ul><ul><li class="nav-level-1"><a href="#edit" class="nav-item">edit</a></li></ul><ul><li class="nav-level-1"><a href="#kustomize" class="nav-item">kustomize</a></li></ul><ul><li class="nav-level-1"><a href="#label" class="nav-item">label</a></li></ul><ul><li class="nav-level-1"><a href="#patch" class="nav-item">patch</a></li></ul><ul><li class="nav-level-1"><a href="#replace" class="nav-item">replace</a></li></ul><ul><li class="nav-level-1"><a href="#rollout" class="nav-item">rollout</a></li><ul id="rollout-nav" style="display: none;"><li class="nav-level-2"><a href="#-em-history-em-" class="nav-item"><em>history</em></a></li><li class="nav-level-2"><a href="#-em-pause-em-" class="nav-item"><em>pause</em></a></li><li class="nav-level-2"><a href="#-em-restart-em-" class="nav-item"><em>restart</em></a></li><li class="nav-level-2"><a href="#-em-resume-em-" class="nav-item"><em>resume</em></a></li><li class="nav-level-2"><a href="#-em-status-em-" class="nav-item"><em>status</em></a></li><li class="nav-level-2"><a href="#-em-undo-em-" class="nav-item"><em>undo</em></a></li></ul></ul><ul><li class="nav-level-1"><a href="#scale" class="nav-item">scale</a></li></ul><ul><li class="nav-level-1"><a href="#set" class="nav-item">set</a></li><ul id="set-nav" style="display: none;"><li class="nav-level-2"><a href="#-em-env-em-" class="nav-item"><em>env</em></a></li><li class="nav-level-2"><a href="#-em-image-em-" class="nav-item"><em>image</em></a></li><li class="nav-level-2"><a href="#-em-resources-em-" class="nav-item"><em>resources</em></a></li><li class="nav-level-2"><a href="#-em-selector-em-" class="nav-item"><em>selector</em></a></li><li class="nav-level-2"><a href="#-em-serviceaccount-em--1" class="nav-item"><em>serviceaccount</em></a></li><li class="nav-level-2"><a href="#-em-subject-em-" class="nav-item"><em>subject</em></a></li></ul></ul><ul><li class="nav-level-1"><a href="#wait" class="nav-item">wait</a></li></ul><ul><li class="nav-level-1 strong-nav"><a href="#-strong-working-with-apps-strong-" class="nav-item"><strong>WORKING WITH APPS</strong></a></li></ul><ul><li class="nav-level-1"><a href="#attach" class="nav-item">attach</a></li></ul><ul><li class="nav-level-1"><a href="#auth" class="nav-item">auth</a></li><ul id="auth-nav" style="display: none;"><li class="nav-level-2"><a href="#-em-can-i-em-" class="nav-item"><em>can-i</em></a></li><li class="nav-level-2"><a href="#-em-reconcile-em-" class="nav-item"><em>reconcile</em></a></li></ul></ul><ul><li class="nav-level-1"><a href="#cp" class="nav-item">cp</a></li></ul><ul><li class="nav-level-1"><a href="#describe" class="nav-item">describe</a></li></ul><ul><li class="nav-level-1"><a href="#exec" class="nav-item">exec</a></li></ul><ul><li class="nav-level-1"><a href="#logs" class="nav-item">logs</a></li></ul><ul><li class="nav-level-1"><a href="#port-forward" class="nav-item">port-forward</a></li></ul><ul><li class="nav-level-1"><a href="#proxy" class="nav-item">proxy</a></li></ul><ul><li class="nav-level-1"><a href="#top" class="nav-item">top</a></li><ul id="top-nav" style="display: none;"><li class="nav-level-2"><a href="#-em-node-em-" class="nav-item"><em>node</em></a></li><li class="nav-level-2"><a href="#-em-pod-em-" class="nav-item"><em>pod</em></a></li></ul></ul><ul><li class="nav-level-1 strong-nav"><a href="#-strong-cluster-management-strong-" class="nav-item"><strong>CLUSTER MANAGEMENT</strong></a></li></ul><ul><li class="nav-level-1"><a href="#api-versions" class="nav-item">api-versions</a></li></ul><ul><li class="nav-level-1"><a href="#certificate" class="nav-item">certificate</a></li><ul id="certificate-nav" style="display: none;"><li class="nav-level-2"><a href="#-em-approve-em-" class="nav-item"><em>approve</em></a></li><li class="nav-level-2"><a href="#-em-deny-em-" class="nav-item"><em>deny</em></a></li></ul></ul><ul><li class="nav-level-1"><a href="#cluster-info" class="nav-item">cluster-info</a></li><ul id="cluster-info-nav" style="display: none;"><li class="nav-level-2"><a href="#-em-dump-em-" class="nav-item"><em>dump</em></a></li></ul></ul><ul><li class="nav-level-1"><a href="#cordon" class="nav-item">cordon</a></li></ul><ul><li class="nav-level-1"><a href="#drain" class="nav-item">drain</a></li></ul><ul><li class="nav-level-1"><a href="#taint" class="nav-item">taint</a></li></ul><ul><li class="nav-level-1"><a href="#uncordon" class="nav-item">uncordon</a></li></ul><ul><li class="nav-level-1 strong-nav"><a href="#-strong-kubectl-settings-and-usage-strong-" class="nav-item"><strong>KUBECTL SETTINGS AND USAGE</strong></a></li></ul><ul><li class="nav-level-1"><a href="#alpha" class="nav-item">alpha</a></li></ul><ul><li class="nav-level-1"><a href="#api-resources" class="nav-item">api-resources</a></li></ul><ul><li class="nav-level-1"><a href="#completion" class="nav-item">completion</a></li></ul><ul><li class="nav-level-1"><a href="#config" class="nav-item">config</a></li><ul id="config-nav" style="display: none;"><li class="nav-level-2"><a href="#-em-current-context-em-" class="nav-item"><em>current-context</em></a></li><li class="nav-level-2"><a href="#-em-delete-cluster-em-" class="nav-item"><em>delete-cluster</em></a></li><li class="nav-level-2"><a href="#-em-delete-context-em-" class="nav-item"><em>delete-context</em></a></li><li class="nav-level-2"><a href="#-em-delete-user-em-" class="nav-item"><em>delete-user</em></a></li><li class="nav-level-2"><a href="#-em-get-clusters-em-" class="nav-item"><em>get-clusters</em></a></li><li class="nav-level-2"><a href="#-em-get-contexts-em-" class="nav-item"><em>get-contexts</em></a></li><li class="nav-level-2"><a href="#-em-get-users-em-" class="nav-item"><em>get-users</em></a></li><li class="nav-level-2"><a href="#-em-rename-context-em-" class="nav-item"><em>rename-context</em></a></li><li class="nav-level-2"><a href="#-em-set-em-" class="nav-item"><em>set</em></a></li><li class="nav-level-2"><a href="#-em-set-cluster-em-" class="nav-item"><em>set-cluster</em></a></li><li class="nav-level-2"><a href="#-em-set-context-em-" class="nav-item"><em>set-context</em></a></li><li class="nav-level-2"><a href="#-em-set-credentials-em-" class="nav-item"><em>set-credentials</em></a></li><li class="nav-level-2"><a href="#-em-unset-em-" class="nav-item"><em>unset</em></a></li><li class="nav-level-2"><a href="#-em-use-context-em-" class="nav-item"><em>use-context</em></a></li><li class="nav-level-2"><a href="#-em-view-em-" class="nav-item"><em>view</em></a></li></ul></ul><ul><li class="nav-level-1"><a href="#explain" class="nav-item">explain</a></li></ul><ul><li class="nav-level-1"><a href="#options" class="nav-item">options</a></li></ul><ul><li class="nav-level-1"><a href="#plugin" class="nav-item">plugin</a></li><ul id="plugin-nav" style="display: none;"><li class="nav-level-2"><a href="#-em-list-em-" class="nav-item"><em>list</em></a></li></ul></ul><ul><li class="nav-level-1"><a href="#version" class="nav-item">version</a></li></ul><br/><div class="copyright"><a href="https://github.com/kubernetes/kubernetes">Copyright 2020 The Kubernetes Authors.</a></div></div>
 <div id="wrapper">
 <div id="code-tabs-wrapper" class="code-tabs"><ul class="code-tab-list"><li class="code-tab" id="example">example</li></ul></div>
 <div id="page-content-wrapper" class="body-content container-fluid"><h1 id="-strong-getting-started-strong-"><strong>GETTING STARTED</strong></h1>
@@ -38,11 +38,12 @@ inspect them.</p>
 <pre class="code-block example"><code class="lang-shell">cat pod.json | kubectl <span class="hljs-keyword">create</span> -f -
 </code></pre>
 <blockquote class="code-block example">
-<p> Edit the data in registry.yaml in JSON then create the resource using the edited data</p>
+<p> Edit the data in docker-registry.yaml in JSON then create the resource using the edited data</p>
 </blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-keyword">create</span> -f registry.yaml --<span class="hljs-keyword">edit</span> -o json
+<pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-keyword">create</span> -f docker-registry.yaml --<span class="hljs-keyword">edit</span> -o json
 </code></pre>
-<p>Create a resource from a file or from stdin.<br><br> JSON and YAML formats are accepted.</p>
+<p>Create a resource from a file or from stdin.</p>
+<p> JSON and YAML formats are accepted.</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl create -f FILENAME</code></p>
 <h3 id="flags">Flags</h3>
@@ -96,7 +97,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>raw</td>
@@ -126,7 +127,7 @@ inspect them.</p>
 <td>selector</td>
 <td>l</td>
 <td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
+<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2) </td>
 </tr>
 <tr>
 <td>show-managed-fields</td>
@@ -143,8 +144,8 @@ inspect them.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 <tr>
 <td>windows-line-endings</td>
@@ -169,7 +170,7 @@ inspect them.</p>
 <blockquote class="code-block example">
 <p> Create a cluster role named &quot;foo&quot; with API Group specified</p>
 </blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl create clusterrole foo <span class="hljs-attribute">--verb</span>=get,list,watch <span class="hljs-attribute">--resource</span>=rs.apps
+<pre class="code-block example"><code class="lang-shell">kubectl create clusterrole foo <span class="hljs-attribute">--verb</span>=get,list,watch <span class="hljs-attribute">--resource</span>=rs.extensions
 </code></pre>
 <blockquote class="code-block example">
 <p> Create a cluster role named &quot;foo&quot; with SubResource specified</p>
@@ -234,7 +235,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>resource</td>
@@ -269,8 +270,8 @@ inspect them.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 <tr>
 <td>verb</td>
@@ -329,13 +330,13 @@ inspect them.</p>
 <td>group</td>
 <td></td>
 <td>[]</td>
-<td>Groups to bind to the clusterrole. The flag can be repeated to add multiple groups. </td>
+<td>Groups to bind to the clusterrole </td>
 </tr>
 <tr>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>save-config</td>
@@ -347,7 +348,7 @@ inspect them.</p>
 <td>serviceaccount</td>
 <td></td>
 <td>[]</td>
-<td>Service accounts to bind to the clusterrole, in the format &lt;namespace&gt;:&lt;name&gt;. The flag can be repeated to add multiple service accounts. </td>
+<td>Service accounts to bind to the clusterrole, in the format &lt;namespace&gt;:&lt;name&gt; </td>
 </tr>
 <tr>
 <td>show-managed-fields</td>
@@ -362,16 +363,10 @@ inspect them.</p>
 <td>Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates <span>[</span><a href="http://golang.org/pkg/text/template/#pkg-overview">http://golang.org/pkg/text/template/#pkg-overview</a><span>]</span>. </td>
 </tr>
 <tr>
-<td>user</td>
-<td></td>
-<td>[]</td>
-<td>Usernames to bind to the clusterrole. The flag can be repeated to add multiple users. </td>
-</tr>
-<tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 </tbody>
 </table>
@@ -400,7 +395,7 @@ inspect them.</p>
 <blockquote class="code-block example">
 <p> Create a new config map named my-config from an env file</p>
 </blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-keyword">create</span> configmap my-config --<span class="hljs-keyword">from</span>-env-file=<span class="hljs-keyword">path</span>/<span class="hljs-keyword">to</span>/foo.env --<span class="hljs-keyword">from</span>-env-file=<span class="hljs-keyword">path</span>/<span class="hljs-keyword">to</span>/bar.env
+<pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-keyword">create</span> configmap my-config --<span class="hljs-keyword">from</span>-env-file=<span class="hljs-keyword">path</span>/<span class="hljs-keyword">to</span>/bar.env
 </code></pre>
 <p>Create a config map based on a file, directory, or specified literal value.</p>
 <p> A single config map may package one or more key/value pairs.</p>
@@ -446,8 +441,8 @@ inspect them.</p>
 <tr>
 <td>from-env-file</td>
 <td></td>
-<td>[]</td>
-<td>Specify the path to a file to read lines of key=val pairs to create a configmap. </td>
+<td></td>
+<td>Specify the path to a file to read lines of key=val pairs to create a configmap (i.e. a Docker .env file). </td>
 </tr>
 <tr>
 <td>from-file</td>
@@ -465,7 +460,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>save-config</td>
@@ -488,8 +483,8 @@ inspect them.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 </tbody>
 </table>
@@ -547,7 +542,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>restart</td>
@@ -582,8 +577,8 @@ inspect them.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 </tbody>
 </table>
@@ -651,7 +646,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>port</td>
@@ -686,8 +681,8 @@ inspect them.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 </tbody>
 </table>
@@ -798,7 +793,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>rule</td>
@@ -827,8 +822,8 @@ inspect them.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 </tbody>
 </table>
@@ -897,7 +892,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>save-config</td>
@@ -920,8 +915,8 @@ inspect them.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 </tbody>
 </table>
@@ -968,7 +963,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>save-config</td>
@@ -991,8 +986,8 @@ inspect them.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 </tbody>
 </table>
@@ -1056,7 +1051,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>save-config</td>
@@ -1085,8 +1080,8 @@ inspect them.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 </tbody>
 </table>
@@ -1155,7 +1150,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>preemption-policy</td>
@@ -1184,8 +1179,8 @@ inspect them.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 <tr>
 <td>value</td>
@@ -1249,7 +1244,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>save-config</td>
@@ -1278,8 +1273,8 @@ inspect them.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 </tbody>
 </table>
@@ -1298,7 +1293,7 @@ inspect them.</p>
 <blockquote class="code-block example">
 <p> Create a role named &quot;foo&quot; with API Group specified</p>
 </blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl create role foo <span class="hljs-attribute">--verb</span>=get,list,watch <span class="hljs-attribute">--resource</span>=rs.apps
+<pre class="code-block example"><code class="lang-shell">kubectl create role foo <span class="hljs-attribute">--verb</span>=get,list,watch <span class="hljs-attribute">--resource</span>=rs.extensions
 </code></pre>
 <blockquote class="code-block example">
 <p> Create a role named &quot;foo&quot; with SubResource specified</p>
@@ -1341,7 +1336,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>resource</td>
@@ -1376,8 +1371,8 @@ inspect them.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 <tr>
 <td>verb</td>
@@ -1436,13 +1431,13 @@ inspect them.</p>
 <td>group</td>
 <td></td>
 <td>[]</td>
-<td>Groups to bind to the role. The flag can be repeated to add multiple groups. </td>
+<td>Groups to bind to the role </td>
 </tr>
 <tr>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>role</td>
@@ -1460,7 +1455,7 @@ inspect them.</p>
 <td>serviceaccount</td>
 <td></td>
 <td>[]</td>
-<td>Service accounts to bind to the role, in the format &lt;namespace&gt;:&lt;name&gt;. The flag can be repeated to add multiple service accounts. </td>
+<td>Service accounts to bind to the role, in the format &lt;namespace&gt;:&lt;name&gt; </td>
 </tr>
 <tr>
 <td>show-managed-fields</td>
@@ -1475,16 +1470,10 @@ inspect them.</p>
 <td>Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates <span>[</span><a href="http://golang.org/pkg/text/template/#pkg-overview">http://golang.org/pkg/text/template/#pkg-overview</a><span>]</span>. </td>
 </tr>
 <tr>
-<td>user</td>
-<td></td>
-<td>[]</td>
-<td>Usernames to bind to the role. The flag can be repeated to add multiple users. </td>
-</tr>
-<tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 </tbody>
 </table>
@@ -1508,13 +1497,13 @@ inspect them.</p>
 <p>Create a new secret for use with Docker registries.</p>
 <p>  Dockercfg secrets are used to authenticate against Docker registries.</p>
 <p>  When using the Docker command line to push images, you can authenticate to a given registry by running:
-  &#39;$ docker login DOCKER_REGISTRY_SERVER --username=DOCKER_USER --password=DOCKER_PASSWORD --email=DOCKER_EMAIL&#39;.</p>
+    &#39;$ docker login DOCKER_REGISTRY_SERVER --username=DOCKER_USER --password=DOCKER_PASSWORD --email=DOCKER_EMAIL&#39;.</p>
 <p> That produces a ~/.dockercfg file that is used by subsequent &#39;docker push&#39; and &#39;docker pull&#39; commands to authenticate to the registry. The email address is optional.</p>
 <p>  When creating applications, you may have a Docker registry that requires authentication.  In order for the
   nodes to pull images on your behalf, they must have the credentials.  You can provide this information
   by creating a dockercfg secret and attaching it to your service account.</p>
 <h3 id="usage">Usage</h3>
-<p><code>$ kubectl create secret docker-registry NAME --docker-username=user --docker-password=password --docker-email=email [--docker-server=string] [--from-file=[key=]source] [--dry-run=server|client|none]</code></p>
+<p><code>$ kubectl create docker-registry NAME --docker-username=user --docker-password=password --docker-email=email [--docker-server=string] [--from-file=[key=]source] [--dry-run=server|client|none]</code></p>
 <h3 id="flags">Flags</h3>
 <table>
 <thead>
@@ -1584,7 +1573,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>save-config</td>
@@ -1607,8 +1596,8 @@ inspect them.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 </tbody>
 </table>
@@ -1635,16 +1624,16 @@ inspect them.</p>
 <pre class="code-block example"><code class="lang-shell">kubectl create<span class="hljs-built_in"> secret </span>generic my-secret <span class="hljs-attribute">--from-file</span>=ssh-privatekey=path/to/id_rsa <span class="hljs-attribute">--from-literal</span>=passphrase=topsecret
 </code></pre>
 <blockquote class="code-block example">
-<p> Create a new secret named my-secret from env files</p>
+<p> Create a new secret named my-secret from an env file</p>
 </blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl create<span class="hljs-built_in"> secret </span>generic my-secret <span class="hljs-attribute">--from-env-file</span>=path/to/foo.env <span class="hljs-attribute">--from-env-file</span>=path/to/bar.env
+<pre class="code-block example"><code class="lang-shell">kubectl create<span class="hljs-built_in"> secret </span>generic my-secret <span class="hljs-attribute">--from-env-file</span>=path/to/bar.env
 </code></pre>
 <p>Create a secret based on a file, directory, or specified literal value.</p>
 <p> A single secret may package one or more key/value pairs.</p>
 <p> When creating a secret based on a file, the key will default to the basename of the file, and the value will default to the file content. If the basename is an invalid key or you wish to chose your own, you may specify an alternate key.</p>
 <p> When creating a secret based on a directory, each file whose basename is a valid key in the directory will be packaged into the secret. Any directory entries except regular files are ignored (e.g. subdirectories, symlinks, devices, pipes, etc).</p>
 <h3 id="usage">Usage</h3>
-<p><code>$ kubectl create secret generic NAME [--type=string] [--from-file=[key=]source] [--from-literal=key1=value1] [--dry-run=server|client|none]</code></p>
+<p><code>$ kubectl create generic NAME [--type=string] [--from-file=[key=]source] [--from-literal=key1=value1] [--dry-run=server|client|none]</code></p>
 <h3 id="flags">Flags</h3>
 <table>
 <thead>
@@ -1683,8 +1672,8 @@ inspect them.</p>
 <tr>
 <td>from-env-file</td>
 <td></td>
-<td>[]</td>
-<td>Specify the path to a file to read lines of key=val pairs to create a secret. </td>
+<td></td>
+<td>Specify the path to a file to read lines of key=val pairs to create a secret (i.e. a Docker .env file). </td>
 </tr>
 <tr>
 <td>from-file</td>
@@ -1702,7 +1691,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>save-config</td>
@@ -1731,8 +1720,8 @@ inspect them.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 </tbody>
 </table>
@@ -1746,7 +1735,7 @@ inspect them.</p>
 <p>Create a TLS secret from the given public/private key pair.</p>
 <p> The public/private key pair must exist beforehand. The public key certificate must be .PEM encoded and match the given private key.</p>
 <h3 id="usage">Usage</h3>
-<p><code>$ kubectl create secret tls NAME --cert=path/to/cert/file --key=path/to/key/file [--dry-run=server|client|none]</code></p>
+<p><code>$ kubectl create tls NAME --cert=path/to/cert/file --key=path/to/key/file [--dry-run=server|client|none]</code></p>
 <h3 id="flags">Flags</h3>
 <table>
 <thead>
@@ -1798,7 +1787,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>save-config</td>
@@ -1821,8 +1810,8 @@ inspect them.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 </tbody>
 </table>
@@ -1845,7 +1834,7 @@ inspect them.</p>
 </code></pre>
 <p>Create a ClusterIP service with the specified name.</p>
 <h3 id="usage">Usage</h3>
-<p><code>$ kubectl create service clusterip NAME [--tcp=&lt;port&gt;:&lt;targetPort&gt;] [--dry-run=server|client|none]</code></p>
+<p><code>$ kubectl create clusterip NAME [--tcp=&lt;port&gt;:&lt;targetPort&gt;] [--dry-run=server|client|none]</code></p>
 <h3 id="flags">Flags</h3>
 <table>
 <thead>
@@ -1885,7 +1874,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>save-config</td>
@@ -1914,8 +1903,8 @@ inspect them.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 </tbody>
 </table>
@@ -1929,7 +1918,7 @@ inspect them.</p>
 <p>Create an ExternalName service with the specified name.</p>
 <p> ExternalName service references to an external DNS address instead of only pods, which will allow application authors to reference services that exist off platform, on other clusters, or locally.</p>
 <h3 id="usage">Usage</h3>
-<p><code>$ kubectl create service externalname NAME --external-name external.name [--dry-run=server|client|none]</code></p>
+<p><code>$ kubectl create externalname NAME --external-name external.name [--dry-run=server|client|none]</code></p>
 <h3 id="flags">Flags</h3>
 <table>
 <thead>
@@ -1969,7 +1958,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>save-config</td>
@@ -1998,8 +1987,8 @@ inspect them.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 </tbody>
 </table>
@@ -2012,7 +2001,7 @@ inspect them.</p>
 </code></pre>
 <p>Create a LoadBalancer service with the specified name.</p>
 <h3 id="usage">Usage</h3>
-<p><code>$ kubectl create service loadbalancer NAME [--tcp=port:targetPort] [--dry-run=server|client|none]</code></p>
+<p><code>$ kubectl create loadbalancer NAME [--tcp=port:targetPort] [--dry-run=server|client|none]</code></p>
 <h3 id="flags">Flags</h3>
 <table>
 <thead>
@@ -2046,7 +2035,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>save-config</td>
@@ -2075,8 +2064,8 @@ inspect them.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 </tbody>
 </table>
@@ -2089,7 +2078,7 @@ inspect them.</p>
 </code></pre>
 <p>Create a NodePort service with the specified name.</p>
 <h3 id="usage">Usage</h3>
-<p><code>$ kubectl create service nodeport NAME [--tcp=port:targetPort] [--dry-run=server|client|none]</code></p>
+<p><code>$ kubectl create nodeport NAME [--tcp=port:targetPort] [--dry-run=server|client|none]</code></p>
 <h3 id="flags">Flags</h3>
 <table>
 <thead>
@@ -2129,7 +2118,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>save-config</td>
@@ -2158,8 +2147,8 @@ inspect them.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 </tbody>
 </table>
@@ -2206,7 +2195,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>save-config</td>
@@ -2229,110 +2218,8 @@ inspect them.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
-</tr>
-</tbody>
-</table>
-<hr>
-<h2 id="-em-token-em-"><em>token</em></h2>
-<blockquote class="code-block example">
-<p> Request a token to authenticate to the kube-apiserver as the service account &quot;myapp&quot; in the current namespace</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-keyword">create</span> <span class="hljs-built_in">token</span> myapp
-</code></pre>
-<blockquote class="code-block example">
-<p> Request a token for a service account in a custom namespace</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-built_in">create</span> <span class="hljs-keyword">token</span> myapp <span class="hljs-comment">--namespace myns</span>
-</code></pre>
-<blockquote class="code-block example">
-<p> Request a token with a custom expiration</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-built_in">create</span> <span class="hljs-keyword">token</span> myapp <span class="hljs-comment">--duration 10m</span>
-</code></pre>
-<blockquote class="code-block example">
-<p> Request a token with a custom audience</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-keyword">create</span> <span class="hljs-built_in">token</span> myapp --audience https:<span class="hljs-comment">//example.com</span>
-</code></pre>
-<blockquote class="code-block example">
-<p> Request a token bound to an instance of a Secret object</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl create token myapp --bound-object-kind<span class="hljs-built_in"> Secret </span>--bound-object-name mysecret
-</code></pre>
-<blockquote class="code-block example">
-<p> Request a token bound to an instance of a Secret object with a specific uid</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl create token myapp --bound-object-kind Secret --bound-object-name mysecret --bound-object-uid <span class="hljs-number">0d4691ed</span>-<span class="hljs-number">659b-4935</span>-a832-355f77ee47cc
-</code></pre>
-<p>Request a service account token.</p>
-<h3 id="usage">Usage</h3>
-<p><code>$ kubectl create token SERVICE_ACCOUNT_NAME</code></p>
-<h3 id="flags">Flags</h3>
-<table>
-<thead>
-<tr>
-<th>Name</th>
-<th>Shorthand</th>
-<th>Default</th>
-<th>Usage</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>allow-missing-template-keys</td>
-<td></td>
 <td>true</td>
-<td>If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. </td>
-</tr>
-<tr>
-<td>audience</td>
-<td></td>
-<td>[]</td>
-<td>Audience of the requested token. If unset, defaults to requesting a token for use with the Kubernetes API server. May be repeated to request a token valid for multiple audiences. </td>
-</tr>
-<tr>
-<td>bound-object-kind</td>
-<td></td>
-<td></td>
-<td>Kind of an object to bind the token to. Supported kinds are Pod, Secret. If set, --bound-object-name must be provided. </td>
-</tr>
-<tr>
-<td>bound-object-name</td>
-<td></td>
-<td></td>
-<td>Name of an object to bind the token to. The token will expire when the object is deleted. Requires --bound-object-kind. </td>
-</tr>
-<tr>
-<td>bound-object-uid</td>
-<td></td>
-<td></td>
-<td>UID of an object to bind the token to. Requires --bound-object-kind and --bound-object-name. If unset, the UID of the existing object is used. </td>
-</tr>
-<tr>
-<td>duration</td>
-<td></td>
-<td>0s</td>
-<td>Requested lifetime of the issued token. The server may return a token with a longer or shorter lifetime. </td>
-</tr>
-<tr>
-<td>output</td>
-<td>o</td>
-<td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
-</tr>
-<tr>
-<td>show-managed-fields</td>
-<td></td>
-<td>false</td>
-<td>If true, keep the managedFields when printing objects in JSON or YAML format. </td>
-</tr>
-<tr>
-<td>template</td>
-<td></td>
-<td></td>
-<td>Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates <span>[</span><a href="http://golang.org/pkg/text/template/#pkg-overview">http://golang.org/pkg/text/template/#pkg-overview</a><span>]</span>. </td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 </tbody>
 </table>
@@ -2393,12 +2280,11 @@ inspect them.</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-builtin-name">get</span> rc/web service/frontend pods/web-pod-13je7
 </code></pre>
-<blockquote class="code-block example">
-<p> List status subresource for a single pod.</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-keyword">get</span> pod web-pod<span class="hljs-number">-13</span>je7 <span class="hljs-comment">--subresource status</span>
-</code></pre>
-<p>Display one or many resources.<br><br> Prints a table of the most important information about the specified resources. You can filter the list using a label selector and the --selector flag. If the desired resource type is namespaced you will only see results in your current namespace unless you pass --all-namespaces.<br><br> By specifying the output as &#39;template&#39; and providing a Go template as the value of the --template flag, you can filter the attributes of the fetched resources.<br><br>Use &quot;kubectl api-resources&quot; for a complete list of supported resources.</p>
+<p>Display one or many resources.</p>
+<p> Prints a table of the most important information about the specified resources. You can filter the list using a label selector and the --selector flag. If the desired resource type is namespaced you will only see results in your current namespace unless you pass --all-namespaces.</p>
+<p> Uninitialized objects are not shown unless --include-uninitialized is passed.</p>
+<p> By specifying the output as &#39;template&#39; and providing a Go template as the value of the --template flag, you can filter the attributes of the fetched resources.</p>
+<p>Use &quot;kubectl api-resources&quot; for a complete list of supported resources.</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl get [(-o|--output=)json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file|custom-columns|custom-columns-file|wide] (TYPE[.VERSION][.GROUP] [NAME | -l label] | TYPE[.VERSION][.GROUP]/NAME ...) [flags]</code></p>
 <h3 id="flags">Flags</h3>
@@ -2470,7 +2356,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file, custom-columns, custom-columns-file, wide). See custom columns <span>[</span><a href="https://kubernetes.io/docs/reference/kubectl/#custom-columns">https://kubernetes.io/docs/reference/kubectl/#custom-columns</a><span>]</span>, golang template <span>[</span><a href="http://golang.org/pkg/text/template/#pkg-overview">http://golang.org/pkg/text/template/#pkg-overview</a><span>]</span> and jsonpath template <span>[</span><a href="https://kubernetes.io/docs/reference/kubectl/jsonpath/">https://kubernetes.io/docs/reference/kubectl/jsonpath/</a><span>]</span>. </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file&#124;custom-columns-file&#124;custom-columns&#124;wide See custom columns <span>[</span><a href="https://kubernetes.io/docs/reference/kubectl/overview/#custom-columns">https://kubernetes.io/docs/reference/kubectl/overview/#custom-columns</a><span>]</span>, golang template <span>[</span><a href="http://golang.org/pkg/text/template/#pkg-overview">http://golang.org/pkg/text/template/#pkg-overview</a><span>]</span> and jsonpath template <span>[</span><a href="https://kubernetes.io/docs/reference/kubectl/jsonpath/">https://kubernetes.io/docs/reference/kubectl/jsonpath/</a><span>]</span>. </td>
 </tr>
 <tr>
 <td>output-watch-events</td>
@@ -2494,7 +2380,7 @@ inspect them.</p>
 <td>selector</td>
 <td>l</td>
 <td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
+<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2) </td>
 </tr>
 <tr>
 <td>server-print</td>
@@ -2527,12 +2413,6 @@ inspect them.</p>
 <td>If non-empty, sort list types using this field specification.  The field specification is expressed as a JSONPath expression (e.g. &#39;{.metadata.name}&#39;). The field in the API resource specified by this JSONPath expression must be an integer or a string. </td>
 </tr>
 <tr>
-<td>subresource</td>
-<td></td>
-<td></td>
-<td>If specified, gets the subresource of the requested object. Must be one of <span>[</span>status scale<span>]</span>. This flag is alpha and may change in the future. </td>
-</tr>
-<tr>
 <td>template</td>
 <td></td>
 <td></td>
@@ -2548,7 +2428,7 @@ inspect them.</p>
 <td>watch</td>
 <td>w</td>
 <td>false</td>
-<td>After listing/getting the requested object, watch for changes. </td>
+<td>After listing/getting the requested object, watch for changes. Uninitialized objects are excluded if no object name is provided. </td>
 </tr>
 <tr>
 <td>watch-only</td>
@@ -2665,7 +2545,7 @@ inspect them.</p>
 <td>expose</td>
 <td></td>
 <td>false</td>
-<td>If true, create a ClusterIP service associated with the pod.  Requires <code>--port</code>. </td>
+<td>If true, service is created for the container(s) which are run </td>
 </tr>
 <tr>
 <td>field-manager</td>
@@ -2692,6 +2572,12 @@ inspect them.</p>
 <td>Period of time in seconds given to the resource to terminate gracefully. Ignored if negative. Set to 1 for immediate shutdown. Can only be set to 0 when --force is true (force deletion). </td>
 </tr>
 <tr>
+<td>hostport</td>
+<td></td>
+<td>-1</td>
+<td>The host port mapping for the container port. To demonstrate a single-machine container. </td>
+</tr>
+<tr>
 <td>image</td>
 <td></td>
 <td></td>
@@ -2701,7 +2587,7 @@ inspect them.</p>
 <td>image-pull-policy</td>
 <td></td>
 <td></td>
-<td>The image pull policy for the container.  If left empty, this value will not be specified by the client and defaulted by the server. </td>
+<td>The image pull policy for the container. If left empty, this value will not be specified by the client and defaulted by the server </td>
 </tr>
 <tr>
 <td>kustomize</td>
@@ -2713,7 +2599,7 @@ inspect them.</p>
 <td>labels</td>
 <td>l</td>
 <td></td>
-<td>Comma separated labels to apply to the pod. Will override previous values. </td>
+<td>Comma separated labels to apply to the pod(s). Will override previous values. </td>
 </tr>
 <tr>
 <td>leave-stdin-open</td>
@@ -2722,16 +2608,16 @@ inspect them.</p>
 <td>If the pod is started in interactive mode or with stdin, leave stdin open after the first attach completes. By default, stdin will be closed after the first attach completes. </td>
 </tr>
 <tr>
+<td>limits</td>
+<td></td>
+<td></td>
+<td>The resource requirement limits for this container.  For example, &#39;cpu=200m,memory=512Mi&#39;.  Note that server side components may assign limits depending on the server configuration, such as limit ranges. </td>
+</tr>
+<tr>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
-</tr>
-<tr>
-<td>override-type</td>
-<td></td>
-<td>merge</td>
-<td>The method used to override the generated object: json, merge, or strategic. </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>overrides</td>
@@ -2776,6 +2662,12 @@ inspect them.</p>
 <td>Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory. </td>
 </tr>
 <tr>
+<td>requests</td>
+<td></td>
+<td></td>
+<td>The resource requirement requests for this container.  For example, &#39;cpu=100m,memory=256Mi&#39;.  Note that server side components may assign requests depending on the server configuration, such as limit ranges. </td>
+</tr>
+<tr>
 <td>restart</td>
 <td></td>
 <td>Always</td>
@@ -2785,7 +2677,7 @@ inspect them.</p>
 <td>rm</td>
 <td></td>
 <td>false</td>
-<td>If true, delete the pod after it exits.  Only valid when attaching to the container, e.g. with &#39;--attach&#39; or with &#39;-i/--stdin&#39;. </td>
+<td>If true, delete resources created in this command for attached containers. </td>
 </tr>
 <tr>
 <td>save-config</td>
@@ -2794,6 +2686,12 @@ inspect them.</p>
 <td>If true, the configuration of current object will be saved in its annotation. Otherwise, the annotation will be unchanged. This flag is useful when you want to perform kubectl apply on this object in the future. </td>
 </tr>
 <tr>
+<td>serviceaccount</td>
+<td></td>
+<td></td>
+<td>Service account to set in the pod spec. </td>
+</tr>
+<tr>
 <td>show-managed-fields</td>
 <td></td>
 <td>false</td>
@@ -2803,7 +2701,7 @@ inspect them.</p>
 <td>stdin</td>
 <td>i</td>
 <td>false</td>
-<td>Keep stdin open on the container in the pod, even if nothing is attached. </td>
+<td>Keep stdin open on the container(s) in the pod, even if nothing is attached. </td>
 </tr>
 <tr>
 <td>template</td>
@@ -2821,7 +2719,7 @@ inspect them.</p>
 <td>tty</td>
 <td>t</td>
 <td>false</td>
-<td>Allocate a TTY for the container in the pod. </td>
+<td>Allocated a TTY for each container in the pod. </td>
 </tr>
 <tr>
 <td>wait</td>
@@ -2868,7 +2766,10 @@ inspect them.</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">kubectl expose deployment nginx <span class="hljs-attribute">--port</span>=80 <span class="hljs-attribute">--target-port</span>=8000
 </code></pre>
-<p>Expose a resource as a new Kubernetes service.<br><br> Looks up a deployment, service, replica set, replication controller or pod by name and uses the selector for that resource as the selector for a new service on the specified port. A deployment or replica set will be exposed as a service only if its selector is convertible to a selector that service supports, i.e. when the selector contains only the matchLabels component. Note that if no port is specified via --port and the exposed resource has multiple ports, all will be re-used by the new service. Also if no labels are specified, the new service will re-use the labels from the resource it exposes.<br><br> Possible resources include (case insensitive):<br><br> pod (po), service (svc), replicationcontroller (rc), deployment (deploy), replicaset (rs)</p>
+<p>Expose a resource as a new Kubernetes service.</p>
+<p> Looks up a deployment, service, replica set, replication controller or pod by name and uses the selector for that resource as the selector for a new service on the specified port. A deployment or replica set will be exposed as a service only if its selector is convertible to a selector that service supports, i.e. when the selector contains only the matchLabels component. Note that if no port is specified via --port and the exposed resource has multiple ports, all will be re-used by the new service. Also if no labels are specified, the new service will re-use the labels from the resource it exposes.</p>
+<p> Possible resources include (case insensitive):</p>
+<p> pod (po), service (svc), replicationcontroller (rc), deployment (deploy), replicaset (rs)</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl expose (-f FILENAME | TYPE NAME) [--port=port] [--protocol=TCP|UDP|SCTP] [--target-port=number-or-name] [--name=name] [--external-ip=external-ip-of-service] [--type=type]</code></p>
 <h3 id="flags">Flags</h3>
@@ -2895,6 +2796,12 @@ inspect them.</p>
 <td>ClusterIP to be assigned to the service. Leave empty to auto-allocate, or set to &#39;None&#39; to create a headless service. </td>
 </tr>
 <tr>
+<td>container-port</td>
+<td></td>
+<td></td>
+<td>Synonym for --target-port </td>
+</tr>
+<tr>
 <td>dry-run</td>
 <td></td>
 <td>none</td>
@@ -2919,6 +2826,12 @@ inspect them.</p>
 <td>Filename, directory, or URL to files identifying the resource to expose a service </td>
 </tr>
 <tr>
+<td>generator</td>
+<td></td>
+<td>service/v2</td>
+<td>The name of the API generator to use. There are 2 generators: &#39;service/v1&#39; and &#39;service/v2&#39;. The only difference between them is that service port in v1 is named &#39;default&#39;, while it is left unnamed in v2. Default is &#39;service/v2&#39;. </td>
+</tr>
+<tr>
 <td>kustomize</td>
 <td>k</td>
 <td></td>
@@ -2946,13 +2859,7 @@ inspect them.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
-</tr>
-<tr>
-<td>override-type</td>
-<td></td>
-<td>merge</td>
-<td>The method used to override the generated object: json, merge, or strategic. </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>overrides</td>
@@ -3041,11 +2948,6 @@ inspect them.</p>
 <pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-keyword">delete</span> -k dir
 </code></pre>
 <blockquote class="code-block example">
-<p> Delete resources from all files that end with &#39;.json&#39; - i.e. expand wildcard characters in file names</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-keyword">delete</span> -f <span class="hljs-string">'*.json'</span>
-</code></pre>
-<blockquote class="code-block example">
 <p> Delete a pod based on the type and name in the JSON passed into stdin</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">cat pod.json | kubectl <span class="hljs-keyword">delete</span> -f -
@@ -3075,7 +2977,11 @@ inspect them.</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-built_in">delete</span> pods <span class="hljs-comment">--all</span>
 </code></pre>
-<p>Delete resources by file names, stdin, resources and names, or by resources and label selector.<br><br> JSON and YAML formats are accepted. Only one type of argument may be specified: file names, resources and names, or resources and label selector.<br><br> Some resources, such as pods, support graceful deletion. These resources define a default period before they are forcibly terminated (the grace period) but you may override that value with the --grace-period flag, or pass --now to set a grace-period of 1. Because these resources often represent entities in the cluster, deletion may not be acknowledged immediately. If the node hosting a pod is down or cannot reach the API server, termination may take significantly longer than the grace period. To force delete a resource, you must specify the --force flag. Note: only a subset of resources support graceful deletion. In absence of the support, the --grace-period flag is ignored.<br><br> IMPORTANT: Force deleting pods does not wait for confirmation that the pod&#39;s processes have been terminated, which can leave those processes running until the node detects the deletion and completes graceful deletion. If your processes use shared storage or talk to a remote API and depend on the name of the pod to identify themselves, force deleting those pods may result in multiple processes running on different machines using the same identification which may lead to data corruption or inconsistency. Only force delete pods when you are sure the pod is terminated, or if your application can tolerate multiple copies of the same pod running at once. Also, if you force delete pods, the scheduler may place new pods on those nodes before the node has released those resources and causing those pods to be evicted immediately.<br><br> Note that the delete command does NOT do resource version checks, so if someone submits an update to a resource right when you submit a delete, their update will be lost along with the rest of the resource.<br><br> After a CustomResourceDefinition is deleted, invalidation of discovery cache may take up to 6 hours. If you don&#39;t want to wait, you might want to run &quot;kubectl api-resources&quot; to refresh the discovery cache.</p>
+<p>Delete resources by file names, stdin, resources and names, or by resources and label selector.</p>
+<p> JSON and YAML formats are accepted. Only one type of argument may be specified: file names, resources and names, or resources and label selector.</p>
+<p> Some resources, such as pods, support graceful deletion. These resources define a default period before they are forcibly terminated (the grace period) but you may override that value with the --grace-period flag, or pass --now to set a grace-period of 1. Because these resources often represent entities in the cluster, deletion may not be acknowledged immediately. If the node hosting a pod is down or cannot reach the API server, termination may take significantly longer than the grace period. To force delete a resource, you must specify the --force flag. Note: only a subset of resources support graceful deletion. In absence of the support, the --grace-period flag is ignored.</p>
+<p> IMPORTANT: Force deleting pods does not wait for confirmation that the pod&#39;s processes have been terminated, which can leave those processes running until the node detects the deletion and completes graceful deletion. If your processes use shared storage or talk to a remote API and depend on the name of the pod to identify themselves, force deleting those pods may result in multiple processes running on different machines using the same identification which may lead to data corruption or inconsistency. Only force delete pods when you are sure the pod is terminated, or if your application can tolerate multiple copies of the same pod running at once. Also, if you force delete pods, the scheduler may place new pods on those nodes before the node has released those resources and causing those pods to be evicted immediately.</p>
+<p> Note that the delete command does NOT do resource version checks, so if someone submits an update to a resource right when you submit a delete, their update will be lost along with the rest of the resource.</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl delete ([-f FILENAME] | [-k DIRECTORY] | TYPE [(NAME | -l label | --all)])</code></p>
 <h3 id="flags">Flags</h3>
@@ -3093,7 +2999,7 @@ inspect them.</p>
 <td>all</td>
 <td></td>
 <td>false</td>
-<td>Delete all resources, in the namespace of the specified resource types. </td>
+<td>Delete all resources, including uninitialized ones, in the namespace of the specified resource types. </td>
 </tr>
 <tr>
 <td>all-namespaces</td>
@@ -3177,7 +3083,7 @@ inspect them.</p>
 <td>selector</td>
 <td>l</td>
 <td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
+<td>Selector (label query) to filter on, not including uninitialized ones. </td>
 </tr>
 <tr>
 <td>timeout</td>
@@ -3214,11 +3120,6 @@ viewing your workloads in a Kubernetes cluster.</p>
 <pre class="code-block example"><code class="lang-shell">cat pod.json | <span class="hljs-type">kubectl</span> <span class="hljs-built_in">apply</span> -f -
 </code></pre>
 <blockquote class="code-block example">
-<p> Apply the configuration from all files that end with &#39;.json&#39; - i.e. expand wildcard characters in file names</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell"><span class="hljs-attribute">kubectl</span> apply -f <span class="hljs-string">'*.json'</span>
-</code></pre>
-<blockquote class="code-block example">
 <p> Note: --prune is still in Alpha # Apply the configuration in manifest.yaml that matches label app=nginx and delete all other resources that are not in the file and match label app=nginx</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">kubectl apply --prune -f manifest.yaml -l <span class="hljs-attribute">app</span>=nginx
@@ -3226,9 +3127,11 @@ viewing your workloads in a Kubernetes cluster.</p>
 <blockquote class="code-block example">
 <p> Apply the configuration in manifest.yaml and delete all the other config maps that are not in the file</p>
 </blockquote>
-<pre class="code-block example"><code class="lang-shell"><span class="hljs-comment">kubectl</span> <span class="hljs-comment">apply</span> --<span class="hljs-comment">prune</span> <span class="hljs-literal">-</span><span class="hljs-comment">f</span> <span class="hljs-comment">manifest</span><span class="hljs-string">.</span><span class="hljs-comment">yaml</span> --<span class="hljs-comment">all</span> --<span class="hljs-comment">prune</span><span class="hljs-literal">-</span><span class="hljs-comment">allowlist=core/v1/ConfigMap</span>
+<pre class="code-block example"><code class="lang-shell"><span class="hljs-comment">kubectl</span> <span class="hljs-comment">apply</span> --<span class="hljs-comment">prune</span> <span class="hljs-literal">-</span><span class="hljs-comment">f</span> <span class="hljs-comment">manifest</span><span class="hljs-string">.</span><span class="hljs-comment">yaml</span> --<span class="hljs-comment">all</span> --<span class="hljs-comment">prune</span><span class="hljs-literal">-</span><span class="hljs-comment">whitelist=core/v1/ConfigMap</span>
 </code></pre>
-<p>Apply a configuration to a resource by file name or stdin. The resource name must be specified. This resource will be created if it doesn&#39;t exist yet. To use &#39;apply&#39;, always create the resource initially with either &#39;apply&#39; or &#39;create --save-config&#39;.<br><br> JSON and YAML formats are accepted.<br><br> Alpha Disclaimer: the --prune functionality is not yet complete. Do not use unless you are aware of what the current state is. See <a href="https://issues.k8s.io/34274">https://issues.k8s.io/34274</a>.</p>
+<p>Apply a configuration to a resource by file name or stdin. The resource name must be specified. This resource will be created if it doesn&#39;t exist yet. To use &#39;apply&#39;, always create the resource initially with either &#39;apply&#39; or &#39;create --save-config&#39;.</p>
+<p> JSON and YAML formats are accepted.</p>
+<p> Alpha Disclaimer: the --prune functionality is not yet complete. Do not use unless you are aware of what the current state is. See <a href="https://issues.k8s.io/34274">https://issues.k8s.io/34274</a>.</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl apply (-f FILENAME | -k DIRECTORY)</code></p>
 <h3 id="flags">Flags</h3>
@@ -3276,7 +3179,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>filename</td>
 <td>f</td>
 <td>[]</td>
-<td>The files that contain the configurations to apply. </td>
+<td>that contains the configuration to apply </td>
 </tr>
 <tr>
 <td>force</td>
@@ -3312,7 +3215,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>overwrite</td>
@@ -3324,13 +3227,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>prune</td>
 <td></td>
 <td>false</td>
-<td>Automatically delete resource objects, that do not appear in the configs and are created by either apply or create --save-config. Should be used with either -l or --all. </td>
-</tr>
-<tr>
-<td>prune-allowlist</td>
-<td></td>
-<td>[]</td>
-<td>Overwrite the default allowlist with &lt;group/version/kind&gt; for --prune </td>
+<td>Automatically delete resource objects, including the uninitialized ones, that do not appear in the configs and are created by either apply or create --save-config. Should be used with either -l or --all. </td>
 </tr>
 <tr>
 <td>prune-whitelist</td>
@@ -3354,7 +3251,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>selector</td>
 <td>l</td>
 <td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
+<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2) </td>
 </tr>
 <tr>
 <td>server-side</td>
@@ -3383,8 +3280,8 @@ viewing your workloads in a Kubernetes cluster.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 <tr>
 <td>wait</td>
@@ -3452,7 +3349,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>record</td>
@@ -3479,12 +3376,6 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates <span>[</span><a href="http://golang.org/pkg/text/template/#pkg-overview">http://golang.org/pkg/text/template/#pkg-overview</a><span>]</span>. </td>
 </tr>
 <tr>
-<td>validate</td>
-<td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
-</tr>
-<tr>
 <td>windows-line-endings</td>
 <td></td>
 <td>false</td>
@@ -3551,7 +3442,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>show-managed-fields</td>
@@ -3616,7 +3507,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>output</td>
 <td>o</td>
 <td>yaml</td>
-<td>Output format. Must be one of (yaml, json) </td>
+<td>Output format. Must be one of yaml&#124;json </td>
 </tr>
 <tr>
 <td>recursive</td>
@@ -3628,7 +3519,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>selector</td>
 <td>l</td>
 <td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
+<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2) </td>
 </tr>
 </tbody>
 </table>
@@ -3664,7 +3555,10 @@ viewing your workloads in a Kubernetes cluster.</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">kubectl annotate pods foo <span class="hljs-keyword">description</span>-
 </code></pre>
-<p>Update the annotations on one or more resources.<br><br> All Kubernetes objects support the ability to store additional data with the object as annotations. Annotations are key/value pairs that can be larger than labels and include arbitrary string values such as structured JSON. Tools and system extensions may use annotations to store their own data.<br><br> Attempting to set an annotation that already exists will fail unless --overwrite is set. If --resource-version is specified and does not match the current resource version on the server the command will fail.<br><br>Use &quot;kubectl api-resources&quot; for a complete list of supported resources.</p>
+<p>Update the annotations on one or more resources.</p>
+<p> All Kubernetes objects support the ability to store additional data with the object as annotations. Annotations are key/value pairs that can be larger than labels and include arbitrary string values such as structured JSON. Tools and system extensions may use annotations to store their own data.</p>
+<p> Attempting to set an annotation that already exists will fail unless --overwrite is set. If --resource-version is specified and does not match the current resource version on the server the command will fail.</p>
+<p>Use &quot;kubectl api-resources&quot; for a complete list of supported resources.</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl annotate [--overwrite] (-f FILENAME | TYPE NAME) KEY_1=VAL_1 ... KEY_N=VAL_N [--resource-version=version]</code></p>
 <h3 id="flags">Flags</h3>
@@ -3682,7 +3576,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>all</td>
 <td></td>
 <td>false</td>
-<td>Select all resources, in the namespace of the specified resource types. </td>
+<td>Select all resources, including uninitialized ones, in the namespace of the specified resource types. </td>
 </tr>
 <tr>
 <td>all-namespaces</td>
@@ -3742,7 +3636,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>overwrite</td>
@@ -3772,7 +3666,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>selector</td>
 <td>l</td>
 <td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
+<td>Selector (label query) to filter on, not including uninitialized ones, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). </td>
 </tr>
 <tr>
 <td>show-managed-fields</td>
@@ -3800,7 +3694,8 @@ viewing your workloads in a Kubernetes cluster.</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">kubectl autoscale rc foo <span class="hljs-attribute">--max</span>=5 <span class="hljs-attribute">--cpu-percent</span>=80
 </code></pre>
-<p>Creates an autoscaler that automatically chooses and sets the number of pods that run in a Kubernetes cluster.<br><br> Looks up a deployment, replica set, stateful set, or replication controller by name and creates an autoscaler that uses the given resource as a reference. An autoscaler can automatically increase or decrease number of pods deployed within the system as needed.</p>
+<p>Creates an autoscaler that automatically chooses and sets the number of pods that run in a Kubernetes cluster.</p>
+<p> Looks up a deployment, replica set, stateful set, or replication controller by name and creates an autoscaler that uses the given resource as a reference. An autoscaler can automatically increase or decrease number of pods deployed within the system as needed.</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl autoscale (-f FILENAME | TYPE NAME | TYPE/NAME) [--min=MINPODS] --max=MAXPODS [--cpu-percent=CPU]</code></p>
 <h3 id="flags">Flags</h3>
@@ -3872,7 +3767,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>record</td>
@@ -3943,7 +3838,14 @@ viewing your workloads in a Kubernetes cluster.</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">kubectl debug <span class="hljs-keyword">node</span><span class="hljs-title">/mynode</span> -it --<span class="hljs-attr">image=</span>busybox
 </code></pre>
-<p>Debug cluster resources using interactive debugging containers.<br><br> &#39;debug&#39; provides automation for common debugging tasks for cluster objects identified by resource and name. Pods will be used by default if no resource is specified.<br><br> The action taken by &#39;debug&#39; varies depending on what resource is specified. Supported actions include:<br><br>  <em>  Workload: Create a copy of an existing pod with certain attributes changed, for example changing the image tag to a new version.<br>  </em>  Workload: Add an ephemeral container to an already running pod, for example to add debugging utilities without restarting the pod.<br>  *  Node: Create a new pod that runs in the node&#39;s host namespaces and can access the node&#39;s filesystem.</p>
+<p>Debug cluster resources using interactive debugging containers.</p>
+<p> &#39;debug&#39; provides automation for common debugging tasks for cluster objects identified by resource and name. Pods will be used by default if no resource is specified.</p>
+<p> The action taken by &#39;debug&#39; varies depending on what resource is specified. Supported actions include:</p>
+<ul>
+<li>Workload: Create a copy of an existing pod with certain attributes changed, for example changing the image tag to a new version.</li>
+<li>Workload: Add an ephemeral container to an already running pod, for example to add debugging utilities without restarting the pod.</li>
+<li>Node: Create a new pod that runs in the node&#39;s host namespaces and can access the node&#39;s filesystem.</li>
+</ul>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl debug (POD | TYPE[[.VERSION].GROUP]/NAME) [ -- COMMAND [args...] ]</code></p>
 <h3 id="flags">Flags</h3>
@@ -4000,12 +3902,6 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>The image pull policy for the container. If left empty, this value will not be specified by the client and defaulted by the server. </td>
 </tr>
 <tr>
-<td>profile</td>
-<td></td>
-<td>legacy</td>
-<td>Debugging profile. </td>
-</tr>
-<tr>
 <td>quiet</td>
 <td>q</td>
 <td>false</td>
@@ -4067,7 +3963,12 @@ viewing your workloads in a Kubernetes cluster.</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">cat service.yaml <span class="hljs-string">| kubectl diff -f -</span>
 </code></pre>
-<p>Diff configurations specified by file name or stdin between the current online configuration, and the configuration as it would be if applied.<br><br> The output is always YAML.<br><br> KUBECTL_EXTERNAL_DIFF environment variable can be used to select your own diff command. Users can use external commands with params too, example: KUBECTL_EXTERNAL_DIFF=&quot;colordiff -N -u&quot;<br><br> By default, the &quot;diff&quot; command available in your path will be run with the &quot;-u&quot; (unified diff) and &quot;-N&quot; (treat absent files as empty) options.<br><br> Exit status: 0 No differences were found. 1 Differences were found. &gt;1 Kubectl or diff failed with an error.<br><br> Note: KUBECTL_EXTERNAL_DIFF, if used, is expected to follow that convention.</p>
+<p>Diff configurations specified by file name or stdin between the current online configuration, and the configuration as it would be if applied.</p>
+<p> The output is always YAML.</p>
+<p> KUBECTL_EXTERNAL_DIFF environment variable can be used to select your own diff command. Users can use external commands with params too, example: KUBECTL_EXTERNAL_DIFF=&quot;colordiff -N -u&quot;</p>
+<p> By default, the &quot;diff&quot; command available in your path will be run with the &quot;-u&quot; (unified diff) and &quot;-N&quot; (treat absent files as empty) options.</p>
+<p> Exit status: 0 No differences were found. 1 Differences were found. &gt;1 Kubectl or diff failed with an error.</p>
+<p> Note: KUBECTL_EXTERNAL_DIFF, if used, is expected to follow that convention.</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl diff -f FILENAME</code></p>
 <h3 id="flags">Flags</h3>
@@ -4106,18 +4007,6 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>Process the kustomization directory. This flag can&#39;t be used together with -f or -R. </td>
 </tr>
 <tr>
-<td>prune</td>
-<td></td>
-<td>false</td>
-<td>Include resources that would be deleted by pruning. Can be used with -l and default shows all resources would be pruned </td>
-</tr>
-<tr>
-<td>prune-allowlist</td>
-<td></td>
-<td>[]</td>
-<td>Overwrite the default whitelist with &lt;group/version/kind&gt; for --prune </td>
-</tr>
-<tr>
 <td>recursive</td>
 <td>R</td>
 <td>false</td>
@@ -4127,7 +4016,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>selector</td>
 <td>l</td>
 <td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
+<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2) </td>
 </tr>
 <tr>
 <td>server-side</td>
@@ -4135,25 +4024,19 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>false</td>
 <td>If true, apply runs in the server instead of the client. </td>
 </tr>
-<tr>
-<td>show-managed-fields</td>
-<td></td>
-<td>false</td>
-<td>If true, include managed fields in the diff. </td>
-</tr>
 </tbody>
 </table>
 <hr>
 <h1 id="edit">edit</h1>
 <blockquote class="code-block example">
-<p> Edit the service named &#39;registry&#39;</p>
+<p> Edit the service named &#39;docker-registry&#39;</p>
 </blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-builtin-name">edit</span> svc/registry
+<pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-builtin-name">edit</span> svc/docker-registry
 </code></pre>
 <blockquote class="code-block example">
 <p> Use an alternative editor</p>
 </blockquote>
-<pre class="code-block example"><code class="lang-shell"><span class="hljs-attribute">KUBE_EDITOR</span>=<span class="hljs-string">"nano"</span> kubectl <span class="hljs-builtin-name">edit</span> svc/registry
+<pre class="code-block example"><code class="lang-shell"><span class="hljs-attribute">KUBE_EDITOR</span>=<span class="hljs-string">"nano"</span> kubectl <span class="hljs-builtin-name">edit</span> svc/docker-registry
 </code></pre>
 <blockquote class="code-block example">
 <p> Edit the job &#39;myjob&#39; in JSON using the v1 API format</p>
@@ -4165,12 +4048,12 @@ viewing your workloads in a Kubernetes cluster.</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-keyword">edit</span> deployment/mydeployment -o yaml --<span class="hljs-keyword">save</span>-config
 </code></pre>
-<blockquote class="code-block example">
-<p> Edit the deployment/mydeployment&#39;s status subresource</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-builtin-name">edit</span> deployment mydeployment <span class="hljs-attribute">--subresource</span>=<span class="hljs-string">'status'</span>
-</code></pre>
-<p>Edit a resource from the default editor.<br><br> The edit command allows you to directly edit any API resource you can retrieve via the command-line tools. It will open the editor defined by your KUBE_EDITOR, or EDITOR environment variables, or fall back to &#39;vi&#39; for Linux or &#39;notepad&#39; for Windows. You can edit multiple objects, although changes are applied one at a time. The command accepts file names as well as command-line arguments, although the files you point to must be previously saved versions of resources.<br><br> Editing is done with the API version used to fetch the resource. To edit using a specific API version, fully-qualify the resource, version, and group.<br><br> The default format is YAML. To edit in JSON, specify &quot;-o json&quot;.<br><br> The flag --windows-line-endings can be used to force Windows line endings, otherwise the default for your operating system will be used.<br><br> In the event an error occurs while updating, a temporary file will be created on disk that contains your unapplied changes. The most common error when updating a resource is another editor changing the resource on the server. When this occurs, you will have to apply your changes to the newer version of the resource, or update your temporary saved copy to include the latest resource version.</p>
+<p>Edit a resource from the default editor.</p>
+<p> The edit command allows you to directly edit any API resource you can retrieve via the command-line tools. It will open the editor defined by your KUBE_EDITOR, or EDITOR environment variables, or fall back to &#39;vi&#39; for Linux or &#39;notepad&#39; for Windows. You can edit multiple objects, although changes are applied one at a time. The command accepts file names as well as command-line arguments, although the files you point to must be previously saved versions of resources.</p>
+<p> Editing is done with the API version used to fetch the resource. To edit using a specific API version, fully-qualify the resource, version, and group.</p>
+<p> The default format is YAML. To edit in JSON, specify &quot;-o json&quot;.</p>
+<p> The flag --windows-line-endings can be used to force Windows line endings, otherwise the default for your operating system will be used.</p>
+<p> In the event an error occurs while updating, a temporary file will be created on disk that contains your unapplied changes. The most common error when updating a resource is another editor changing the resource on the server. When this occurs, you will have to apply your changes to the newer version of the resource, or update your temporary saved copy to include the latest resource version.</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl edit (RESOURCE/NAME | -f FILENAME)</code></p>
 <h3 id="flags">Flags</h3>
@@ -4212,7 +4095,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>output-patch</td>
@@ -4245,12 +4128,6 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>If true, keep the managedFields when printing objects in JSON or YAML format. </td>
 </tr>
 <tr>
-<td>subresource</td>
-<td></td>
-<td></td>
-<td>If specified, edit will operate on the subresource of the requested object. Must be one of <span>[</span>status<span>]</span>. This flag is alpha and may change in the future. </td>
-</tr>
-<tr>
 <td>template</td>
 <td></td>
 <td></td>
@@ -4259,8 +4136,8 @@ viewing your workloads in a Kubernetes cluster.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 <tr>
 <td>windows-line-endings</td>
@@ -4407,7 +4284,13 @@ viewing your workloads in a Kubernetes cluster.</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-keyword">label</span><span class="bash"> pods foo bar-</span>
 </code></pre>
-<p>Update the labels on a resource.<br><br>  <em>  A label key and value must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores, up to 63 characters each.<br>  </em>  Optionally, the key can begin with a DNS subdomain prefix and a single &#39;/&#39;, like example.com/my-app.<br>  <em>  If --overwrite is true, then existing labels can be overwritten, otherwise attempting to overwrite a label will result in an error.<br>  </em>  If --resource-version is specified, then updates will use this resource version, otherwise the existing resource-version will be used.</p>
+<p>Update the labels on a resource.</p>
+<ul>
+<li>A label key and value must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores, up to  63 characters each.</li>
+<li>Optionally, the key can begin with a DNS subdomain prefix and a single &#39;/&#39;, like example.com/my-app.</li>
+<li>If --overwrite is true, then existing labels can be overwritten, otherwise attempting to overwrite a label will result in an error.</li>
+<li>If --resource-version is specified, then updates will use this resource version, otherwise the existing resource-version will be used.</li>
+</ul>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl label [--overwrite] (-f FILENAME | TYPE NAME) KEY_1=VAL_1 ... KEY_N=VAL_N [--resource-version=version]</code></p>
 <h3 id="flags">Flags</h3>
@@ -4425,7 +4308,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>all</td>
 <td></td>
 <td>false</td>
-<td>Select all resources, in the namespace of the specified resource types </td>
+<td>Select all resources, including uninitialized ones, in the namespace of the specified resource types </td>
 </tr>
 <tr>
 <td>all-namespaces</td>
@@ -4485,7 +4368,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>overwrite</td>
@@ -4515,7 +4398,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>selector</td>
 <td>l</td>
 <td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
+<td>Selector (label query) to filter on, not including uninitialized ones, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). </td>
 </tr>
 <tr>
 <td>show-managed-fields</td>
@@ -4558,12 +4441,8 @@ viewing your workloads in a Kubernetes cluster.</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">kubectl patch pod valid-pod --<span class="hljs-class"><span class="hljs-keyword">type</span></span>=<span class="hljs-symbol">'jso</span>n' -p='[{<span class="hljs-string">"op"</span>: <span class="hljs-string">"replace"</span>, <span class="hljs-string">"path"</span>: <span class="hljs-string">"/spec/containers/0/image"</span>, <span class="hljs-string">"value"</span>:<span class="hljs-string">"new image"</span>}]'
 </code></pre>
-<blockquote class="code-block example">
-<p> Update a deployment&#39;s replicas through the scale subresource using a merge patch.</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl patch deployment nginx-deployment --subresource=<span class="hljs-symbol">'scal</span>e' --<span class="hljs-class"><span class="hljs-keyword">type</span></span>=<span class="hljs-symbol">'merg</span>e' -p '{<span class="hljs-string">"spec"</span>:{<span class="hljs-string">"replicas"</span>:<span class="hljs-number">2</span>}}'
-</code></pre>
-<p>Update fields of a resource using strategic merge patch, a JSON merge patch, or a JSON patch.<br><br> JSON and YAML formats are accepted.<br><br> Note: Strategic merge patch is not supported for custom resources.</p>
+<p>Update fields of a resource using strategic merge patch, a JSON merge patch, or a JSON patch.</p>
+<p> JSON and YAML formats are accepted.</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl patch (-f FILENAME | TYPE NAME) [-p PATCH|--patch-file FILE]</code></p>
 <h3 id="flags">Flags</h3>
@@ -4617,7 +4496,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>patch</td>
@@ -4650,12 +4529,6 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>If true, keep the managedFields when printing objects in JSON or YAML format. </td>
 </tr>
 <tr>
-<td>subresource</td>
-<td></td>
-<td></td>
-<td>If specified, patch will operate on the subresource of the requested object. Must be one of <span>[</span>status scale<span>]</span>. This flag is alpha and may change in the future. </td>
-</tr>
-<tr>
 <td>template</td>
 <td></td>
 <td></td>
@@ -4691,7 +4564,9 @@ viewing your workloads in a Kubernetes cluster.</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">kubectl replace <span class="hljs-params">--force</span> -f <span class="hljs-string">./pod.json</span>
 </code></pre>
-<p>Replace a resource by file name or stdin.<br><br> JSON and YAML formats are accepted. If replacing an existing resource, the complete resource spec must be provided. This can be obtained by<br><br>  $ kubectl get TYPE NAME -o yaml</p>
+<p>Replace a resource by file name or stdin.</p>
+<p> JSON and YAML formats are accepted. If replacing an existing resource, the complete resource spec must be provided. This can be obtained by</p>
+<p>  $ kubectl get TYPE NAME -o yaml</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl replace -f FILENAME</code></p>
 <h3 id="flags">Flags</h3>
@@ -4733,7 +4608,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>filename</td>
 <td>f</td>
 <td>[]</td>
-<td>The files that contain the configurations to replace. </td>
+<td>to use to replace the resource. </td>
 </tr>
 <tr>
 <td>force</td>
@@ -4757,7 +4632,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>raw</td>
@@ -4784,12 +4659,6 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>If true, keep the managedFields when printing objects in JSON or YAML format. </td>
 </tr>
 <tr>
-<td>subresource</td>
-<td></td>
-<td></td>
-<td>If specified, replace will operate on the subresource of the requested object. Must be one of <span>[</span>status scale<span>]</span>. This flag is alpha and may change in the future. </td>
-</tr>
-<tr>
 <td>template</td>
 <td></td>
 <td></td>
@@ -4804,8 +4673,8 @@ viewing your workloads in a Kubernetes cluster.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 <tr>
 <td>wait</td>
@@ -4827,17 +4696,13 @@ viewing your workloads in a Kubernetes cluster.</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">kubectl rollout <span class="hljs-keyword">status</span> daemonset/foo
 </code></pre>
-<blockquote class="code-block example">
-<p> Restart a deployment</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl rollout <span class="hljs-built_in">restart</span> deployment/abc
-</code></pre>
-<blockquote class="code-block example">
-<p> Restart deployments with the app=nginx label</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl rollout <span class="hljs-keyword">restart</span> deployment <span class="hljs-comment">--selector=app=nginx</span>
-</code></pre>
-<p>Manage the rollout of one or many resources.<br>  <br> Valid resource types include:<br><br>  <em>  deployments<br>  </em>  daemonsets<br>  *  statefulsets</p>
+<p>Manage the rollout of a resource.</p>
+<p> Valid resource types include:</p>
+<ul>
+<li>deployments</li>
+<li>daemonsets</li>
+<li>statefulsets</li>
+</ul>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl rollout SUBCOMMAND</code></p>
 <hr>
@@ -4888,7 +4753,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>recursive</td>
@@ -4903,12 +4768,6 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>See the details, including podTemplate of the revision specified </td>
 </tr>
 <tr>
-<td>selector</td>
-<td>l</td>
-<td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
-</tr>
-<tr>
 <td>show-managed-fields</td>
 <td></td>
 <td>false</td>
@@ -4972,7 +4831,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>recursive</td>
@@ -4981,12 +4840,6 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory. </td>
 </tr>
 <tr>
-<td>selector</td>
-<td>l</td>
-<td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
-</tr>
-<tr>
 <td>show-managed-fields</td>
 <td></td>
 <td>false</td>
@@ -5012,13 +4865,8 @@ viewing your workloads in a Kubernetes cluster.</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">kubectl rollout <span class="hljs-built_in">restart</span> daemonset/abc
 </code></pre>
-<blockquote class="code-block example">
-<p> Restart deployments with the app=nginx label</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl rollout <span class="hljs-keyword">restart</span> deployment <span class="hljs-comment">--selector=app=nginx</span>
-</code></pre>
 <p>Restart a resource.</p>
-<p>  Resource rollout will be restarted.</p>
+<p>   Resource rollout will be restarted.</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl rollout restart RESOURCE</code></p>
 <h3 id="flags">Flags</h3>
@@ -5060,7 +4908,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>recursive</td>
@@ -5069,12 +4917,6 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory. </td>
 </tr>
 <tr>
-<td>selector</td>
-<td>l</td>
-<td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
-</tr>
-<tr>
 <td>show-managed-fields</td>
 <td></td>
 <td>false</td>
@@ -5138,7 +4980,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>recursive</td>
@@ -5147,12 +4989,6 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory. </td>
 </tr>
 <tr>
-<td>selector</td>
-<td>l</td>
-<td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
-</tr>
-<tr>
 <td>show-managed-fields</td>
 <td></td>
 <td>false</td>
@@ -5213,12 +5049,6 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>Pin to a specific revision for showing its status. Defaults to 0 (last revision). </td>
 </tr>
 <tr>
-<td>selector</td>
-<td>l</td>
-<td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
-</tr>
-<tr>
 <td>timeout</td>
 <td></td>
 <td>0s</td>
@@ -5291,7 +5121,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>recursive</td>
@@ -5300,12 +5130,6 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory. </td>
 </tr>
 <tr>
-<td>selector</td>
-<td>l</td>
-<td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
-</tr>
-<tr>
 <td>show-managed-fields</td>
 <td></td>
 <td>false</td>
@@ -5352,7 +5176,9 @@ viewing your workloads in a Kubernetes cluster.</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">kubectl scale <span class="hljs-attribute">--replicas</span>=3 statefulset/web
 </code></pre>
-<p>Set a new size for a deployment, replica set, replication controller, or stateful set.<br><br> Scale also allows users to specify one or more preconditions for the scale action.<br><br> If --current-replicas or --resource-version is specified, it is validated before the scale is attempted, and it is guaranteed that the precondition holds true when the scale is sent to the server.</p>
+<p>Set a new size for a deployment, replica set, replication controller, or stateful set.</p>
+<p> Scale also allows users to specify one or more preconditions for the scale action.</p>
+<p> If --current-replicas or --resource-version is specified, it is validated before the scale is attempted, and it is guaranteed that the precondition holds true when the scale is sent to the server.</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl scale [--resource-version=version] [--current-replicas=count] --replicas=COUNT (-f FILENAME | TYPE NAME)</code></p>
 <h3 id="flags">Flags</h3>
@@ -5406,7 +5232,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>record</td>
@@ -5436,7 +5262,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>selector</td>
 <td>l</td>
 <td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
+<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2) </td>
 </tr>
 <tr>
 <td>show-managed-fields</td>
@@ -5460,7 +5286,8 @@ viewing your workloads in a Kubernetes cluster.</p>
 </table>
 <hr>
 <h1 id="set">set</h1>
-<p>Configure application resources.<br><br> These commands help you make changes to existing application resources.</p>
+<p>Configure application resources.</p>
+<p> These commands help you make changes to existing application resources.</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl set SUBCOMMAND</code></p>
 <hr>
@@ -5614,7 +5441,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>overwrite</td>
@@ -5644,7 +5471,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>selector</td>
 <td>l</td>
 <td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
+<td>Selector (label query) to filter on </td>
 </tr>
 <tr>
 <td>show-managed-fields</td>
@@ -5702,7 +5529,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>all</td>
 <td></td>
 <td>false</td>
-<td>Select all resources, in the namespace of the specified resource types </td>
+<td>Select all resources, including uninitialized ones, in the namespace of the specified resource types </td>
 </tr>
 <tr>
 <td>allow-missing-template-keys</td>
@@ -5744,7 +5571,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>record</td>
@@ -5762,7 +5589,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>selector</td>
 <td>l</td>
 <td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
+<td>Selector (label query) to filter on, not including uninitialized ones, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2) </td>
 </tr>
 <tr>
 <td>show-managed-fields</td>
@@ -5820,7 +5647,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>all</td>
 <td></td>
 <td>false</td>
-<td>Select all resources, in the namespace of the specified resource types </td>
+<td>Select all resources, including uninitialized ones, in the namespace of the specified resource types </td>
 </tr>
 <tr>
 <td>allow-missing-template-keys</td>
@@ -5874,7 +5701,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>record</td>
@@ -5898,7 +5725,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 <td>selector</td>
 <td>l</td>
 <td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
+<td>Selector (label query) to filter on, not including uninitialized ones,supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2) </td>
 </tr>
 <tr>
 <td>show-managed-fields</td>
@@ -5923,7 +5750,7 @@ viewing your workloads in a Kubernetes cluster.</p>
 kubectl create deployment my-dep -o yaml <span class="hljs-attribute">--dry-run</span>=client | kubectl label --local -f - <span class="hljs-attribute">environment</span>=qa -o yaml | kubectl create -f -
 </code></pre>
 <p>Set the selector on a resource. Note that the new selector will overwrite the old selector if the resource had one prior to the invocation of &#39;set selector&#39;.</p>
-<p> A selector must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores, up to 63 characters. If --resource-version is specified, then updates will use this resource version, otherwise the existing resource-version will be used. Note: currently selectors can only be set on Service objects.</p>
+<p> A selector must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores, up to  63 characters. If --resource-version is specified, then updates will use this resource version, otherwise the existing resource-version will be used. Note: currently selectors can only be set on Service objects.</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl set selector (-f FILENAME | TYPE NAME) EXPRESSIONS [--resource-version=version]</code></p>
 <h3 id="flags">Flags</h3>
@@ -5977,7 +5804,7 @@ kubectl create deployment my-dep -o yaml <span class="hljs-attribute">--dry-run<
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>record</td>
@@ -6043,7 +5870,7 @@ kubectl create deployment my-dep -o yaml <span class="hljs-attribute">--dry-run<
 <td>all</td>
 <td></td>
 <td>false</td>
-<td>Select all resources, in the namespace of the specified resource types </td>
+<td>Select all resources, including uninitialized ones, in the namespace of the specified resource types </td>
 </tr>
 <tr>
 <td>allow-missing-template-keys</td>
@@ -6085,7 +5912,7 @@ kubectl create deployment my-dep -o yaml <span class="hljs-attribute">--dry-run<
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>record</td>
@@ -6148,7 +5975,7 @@ kubectl create deployment my-dep -o yaml <span class="hljs-attribute">--dry-run<
 <td>all</td>
 <td></td>
 <td>false</td>
-<td>Select all resources, in the namespace of the specified resource types </td>
+<td>Select all resources, including uninitialized ones, in the namespace of the specified resource types </td>
 </tr>
 <tr>
 <td>allow-missing-template-keys</td>
@@ -6196,7 +6023,7 @@ kubectl create deployment my-dep -o yaml <span class="hljs-attribute">--dry-run<
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>recursive</td>
@@ -6208,7 +6035,7 @@ kubectl create deployment my-dep -o yaml <span class="hljs-attribute">--dry-run<
 <td>selector</td>
 <td>l</td>
 <td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
+<td>Selector (label query) to filter on, not including uninitialized ones, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2) </td>
 </tr>
 <tr>
 <td>serviceaccount</td>
@@ -6228,12 +6055,6 @@ kubectl create deployment my-dep -o yaml <span class="hljs-attribute">--dry-run<
 <td></td>
 <td>Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates <span>[</span><a href="http://golang.org/pkg/text/template/#pkg-overview">http://golang.org/pkg/text/template/#pkg-overview</a><span>]</span>. </td>
 </tr>
-<tr>
-<td>user</td>
-<td></td>
-<td>[]</td>
-<td>Usernames to bind to the role </td>
-</tr>
 </tbody>
 </table>
 <hr>
@@ -6244,24 +6065,22 @@ kubectl create deployment my-dep -o yaml <span class="hljs-attribute">--dry-run<
 <pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-built_in">wait</span> <span class="hljs-comment">--for=condition=Ready pod/busybox1</span>
 </code></pre>
 <blockquote class="code-block example">
-<p> The default value of status condition is true; you can wait for other targets after an equal delimiter (compared after Unicode simple case folding, which is a more general form of case-insensitivity):</p>
+<p> The default value of status condition is true; you can set it to false</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-built_in">wait</span> --<span class="hljs-keyword">for</span>=condition=Ready=<span class="hljs-literal">false</span> pod/busybox1
 </code></pre>
 <blockquote class="code-block example">
-<p> Wait for the pod &quot;busybox1&quot; to contain the status phase to be &quot;Running&quot;.</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-built_in">wait</span> --<span class="hljs-keyword">for</span>=jsonpath=<span class="hljs-string">'{.status.phase}'</span>=Running pod/busybox1
-</code></pre>
-<blockquote class="code-block example">
 <p> Wait for the pod &quot;busybox1&quot; to be deleted, with a timeout of 60s, after having issued the &quot;delete&quot; command</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">kubectl delete pod/busybox1
 kubectl wait <span class="hljs-attribute">--for</span>=delete pod/busybox1 <span class="hljs-attribute">--timeout</span>=60s
 </code></pre>
-<p>Experimental: Wait for a specific condition on one or many resources.<br><br> The command takes multiple resources and waits until the specified condition is seen in the Status field of every given resource.<br><br> Alternatively, the command can wait for the given set of resources to be deleted by providing the &quot;delete&quot; keyword as the value to the --for flag.<br><br> A successful message will be printed to stdout indicating when the specified condition has been met. You can use -o option to change to output destination.</p>
+<p>Experimental: Wait for a specific condition on one or many resources.</p>
+<p> The command takes multiple resources and waits until the specified condition is seen in the Status field of every given resource.</p>
+<p> Alternatively, the command can wait for the given set of resources to be deleted by providing the &quot;delete&quot; keyword as the value to the --for flag.</p>
+<p> A successful message will be printed to stdout indicating when the specified condition has been met. You can use -o option to change to output destination.</p>
 <h3 id="usage">Usage</h3>
-<p><code>$ kubectl wait ([-f FILENAME] | resource.group/resource.name | resource.group [(-l label | --all)]) [--for=delete|--for condition=available|--for=jsonpath=&#39;{}&#39;=value]</code></p>
+<p><code>$ kubectl wait ([-f FILENAME] | resource.group/resource.name | resource.group [(-l label | --all)]) [--for=delete|--for condition=available]</code></p>
 <h3 id="flags">Flags</h3>
 <table>
 <thead>
@@ -6307,7 +6126,7 @@ kubectl wait <span class="hljs-attribute">--for</span>=delete pod/busybox1 <span
 <td>for</td>
 <td></td>
 <td></td>
-<td>The condition to wait on: <span>[</span>delete&#124;condition=condition-name<span>[</span>=condition-value<span>]</span>&#124;jsonpath=&#39;{JSONPath expression}&#39;=JSONPath Condition<span>]</span>. The default condition-value is true.  Condition values are compared after Unicode simple case folding, which is a more general form of case-insensitivity. </td>
+<td>The condition to wait on: <span>[</span>delete&#124;condition=condition-name<span>]</span>. The default status value of condition-name is true, you can set false with condition=condition-name=false </td>
 </tr>
 <tr>
 <td>local</td>
@@ -6319,7 +6138,7 @@ kubectl wait <span class="hljs-attribute">--for</span>=delete pod/busybox1 <span
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>recursive</td>
@@ -6472,7 +6291,7 @@ applications.</p>
 <pre class="code-block example"><code class="lang-shell">kubectl auth can-i --list --<span class="hljs-keyword">namespace</span>=<span class="hljs-symbol">foo</span>
 </code></pre>
 <p>Check whether an action is allowed.</p>
-<p> VERB is a logical Kubernetes API verb like &#39;get&#39;, &#39;list&#39;, &#39;watch&#39;, &#39;delete&#39;, etc. TYPE is a Kubernetes resource. Shortcuts and groups will be resolved. NONRESOURCEURL is a partial URL that starts with &quot;/&quot;. NAME is the name of a particular Kubernetes resource. This command pairs nicely with impersonation. See --as global flag.</p>
+<p> VERB is a logical Kubernetes API verb like &#39;get&#39;, &#39;list&#39;, &#39;watch&#39;, &#39;delete&#39;, etc. TYPE is a Kubernetes resource. Shortcuts and groups will be resolved. NONRESOURCEURL is a partial URL that starts with &quot;/&quot;. NAME is the name of a particular Kubernetes resource.</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl auth can-i VERB [TYPE | TYPE/NAME | NONRESOURCEURL]</code></p>
 <h3 id="flags">Flags</h3>
@@ -6571,7 +6390,7 @@ applications.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>recursive</td>
@@ -6663,12 +6482,6 @@ applications.</p>
 <td>false</td>
 <td>The copied file/directory&#39;s ownership and permissions will not be preserved in the container </td>
 </tr>
-<tr>
-<td>retries</td>
-<td></td>
-<td>0</td>
-<td>Set number of retries to complete a copy operation from a container. Specify 0 to disable or any negative value for infinite retrying. The default is 0 (no retry). </td>
-</tr>
 </tbody>
 </table>
 <hr>
@@ -6699,11 +6512,15 @@ applications.</p>
 <pre class="code-block example"><code class="lang-shell">kubectl describe po -l <span class="hljs-attribute">name</span>=myLabel
 </code></pre>
 <blockquote class="code-block example">
-<p> Describe all pods managed by the &#39;frontend&#39; replication controller # (rc-created pods get the name of the rc as a prefix in the pod name)</p>
+<p> Describe all pods managed by the &#39;frontend&#39; replication controller (rc-created pods # get the name of the rc as a prefix in the pod the name)</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell"><span class="hljs-attribute">kubectl describe pods frontend</span>
 </code></pre>
-<p>Show details of a specific resource or group of resources.<br><br> Print a detailed description of the selected resources, including related resources such as events or controllers. You may select a single object by name, all objects of that type, provide a name prefix, or label selector. For example:<br><br>  $ kubectl describe TYPE NAME_PREFIX<br>  <br> will first check for an exact match on TYPE and NAME_PREFIX. If no such resource exists, it will output details for every resource that has a name prefixed with NAME_PREFIX.<br><br>Use &quot;kubectl api-resources&quot; for a complete list of supported resources.</p>
+<p>Show details of a specific resource or group of resources.</p>
+<p> Print a detailed description of the selected resources, including related resources such as events or controllers. You may select a single object by name, all objects of that type, provide a name prefix, or label selector. For example:</p>
+<p>  $ kubectl describe TYPE NAME_PREFIX</p>
+<p> will first check for an exact match on TYPE and NAME_PREFIX. If no such resource exists, it will output details for every resource that has a name prefixed with NAME_PREFIX.</p>
+<p>Use &quot;kubectl api-resources&quot; for a complete list of supported resources.</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl describe (-f FILENAME | TYPE [NAME_PREFIX | -l label] | TYPE/NAME)</code></p>
 <h3 id="flags">Flags</h3>
@@ -6751,7 +6568,7 @@ applications.</p>
 <td>selector</td>
 <td>l</td>
 <td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
+<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2) </td>
 </tr>
 <tr>
 <td>show-events</td>
@@ -6762,109 +6579,6 @@ applications.</p>
 </tbody>
 </table>
 <hr>
-<h1 id="events">events</h1>
-<blockquote class="code-block example">
-<p> List recent events in the default namespace.</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell"><span class="hljs-attribute">kubectl events</span>
-</code></pre>
-<blockquote class="code-block example">
-<p> List recent events in all namespaces.</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl events <span class="hljs-comment">--all-namespaces</span>
-</code></pre>
-<blockquote class="code-block example">
-<p> List recent events for the specified pod, then wait for more events and list them as they arrive.</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell"><span class="hljs-comment">kubectl</span> <span class="hljs-comment">events</span> --<span class="hljs-comment">for</span> <span class="hljs-comment">pod/web</span><span class="hljs-literal">-</span><span class="hljs-comment">pod</span><span class="hljs-literal">-</span><span class="hljs-comment">13je7</span> --<span class="hljs-comment">watch</span>
-</code></pre>
-<blockquote class="code-block example">
-<p> List recent events in given format. Supported ones, apart from default, are json and yaml.</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell"><span class="hljs-attribute">kubectl events -oyaml</span>
-</code></pre>
-<blockquote class="code-block example">
-<p> List recent only events in given event types</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl events <span class="hljs-attribute">--types</span>=Warning,Normal
-</code></pre>
-<p>Display events<br><br> Prints a table of the most important information about events. You can request events for a namespace, for all namespace, or filtered to only those pertaining to a specified resource.</p>
-<h3 id="usage">Usage</h3>
-<p><code>$ kubectl events [(-o|--output=)json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file] [--for TYPE/NAME] [--watch] [--event=Normal,Warning]</code></p>
-<h3 id="flags">Flags</h3>
-<table>
-<thead>
-<tr>
-<th>Name</th>
-<th>Shorthand</th>
-<th>Default</th>
-<th>Usage</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>all-namespaces</td>
-<td>A</td>
-<td>false</td>
-<td>If present, list the requested object(s) across all namespaces. Namespace in current context is ignored even if specified with --namespace. </td>
-</tr>
-<tr>
-<td>allow-missing-template-keys</td>
-<td></td>
-<td>true</td>
-<td>If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. </td>
-</tr>
-<tr>
-<td>chunk-size</td>
-<td></td>
-<td>500</td>
-<td>Return large lists in chunks rather than all at once. Pass 0 to disable. This flag is beta and may change in the future. </td>
-</tr>
-<tr>
-<td>for</td>
-<td></td>
-<td></td>
-<td>Filter events to only those pertaining to the specified resource. </td>
-</tr>
-<tr>
-<td>no-headers</td>
-<td></td>
-<td>false</td>
-<td>When using the default output format, don&#39;t print headers. </td>
-</tr>
-<tr>
-<td>output</td>
-<td>o</td>
-<td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
-</tr>
-<tr>
-<td>show-managed-fields</td>
-<td></td>
-<td>false</td>
-<td>If true, keep the managedFields when printing objects in JSON or YAML format. </td>
-</tr>
-<tr>
-<td>template</td>
-<td></td>
-<td></td>
-<td>Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates <span>[</span><a href="http://golang.org/pkg/text/template/#pkg-overview">http://golang.org/pkg/text/template/#pkg-overview</a><span>]</span>. </td>
-</tr>
-<tr>
-<td>types</td>
-<td></td>
-<td>[]</td>
-<td>Output only events of given types. </td>
-</tr>
-<tr>
-<td>watch</td>
-<td>w</td>
-<td>false</td>
-<td>After listing the requested events, watch for more events. </td>
-</tr>
-</tbody>
-</table>
-<hr>
 <h1 id="exec">exec</h1>
 <blockquote class="code-block example">
 <p> Get output from running the &#39;date&#39; command from pod mypod, using the first container by default</p>
@@ -7083,7 +6797,7 @@ applications.</p>
 <td>selector</td>
 <td>l</td>
 <td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
+<td>Selector (label query) to filter on. </td>
 </tr>
 <tr>
 <td>since</td>
@@ -7148,7 +6862,9 @@ applications.</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">kubectl port-forward pod/mypod :<span class="hljs-number">5000</span>
 </code></pre>
-<p>Forward one or more local ports to a pod.<br><br> Use resource type/name such as deployment/mydeployment to select a pod. Resource type defaults to &#39;pod&#39; if omitted.<br><br> If there are multiple pods matching the criteria, a pod will be selected automatically. The forwarding session ends when the selected pod terminates, and a rerun of the command is needed to resume forwarding.</p>
+<p>Forward one or more local ports to a pod.</p>
+<p> Use resource type/name such as deployment/mydeployment to select a pod. Resource type defaults to &#39;pod&#39; if omitted.</p>
+<p> If there are multiple pods matching the criteria, a pod will be selected automatically. The forwarding session ends when the selected pod terminates, and a rerun of the command is needed to resume forwarding.</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl port-forward TYPE/NAME [options] [LOCAL_PORT:]REMOTE_PORT [...[LOCAL_PORT_N:]REMOTE_PORT_N]</code></p>
 <h3 id="flags">Flags</h3>
@@ -7247,12 +6963,6 @@ applications.</p>
 <td>Prefix to serve the proxied API under. </td>
 </tr>
 <tr>
-<td>append-server-path</td>
-<td></td>
-<td>false</td>
-<td>If true, enables automatic path appending of the kube context server path to each request. </td>
-</tr>
-<tr>
 <td>disable-filter</td>
 <td></td>
 <td>false</td>
@@ -7304,7 +7014,9 @@ applications.</p>
 </table>
 <hr>
 <h1 id="top">top</h1>
-<p>Display Resource (CPU/Memory) usage.<br><br> The top command allows you to see the resource consumption for nodes or pods.<br><br> This command requires Metrics Server to be correctly configured and working on the server.</p>
+<p>Display Resource (CPU/Memory) usage.</p>
+<p> The top command allows you to see the resource consumption for nodes or pods.</p>
+<p> This command requires Metrics Server to be correctly configured and working on the server.</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl top</code></p>
 <hr>
@@ -7344,13 +7056,7 @@ applications.</p>
 <td>selector</td>
 <td>l</td>
 <td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
-</tr>
-<tr>
-<td>show-capacity</td>
-<td></td>
-<td>false</td>
-<td>Print node resources based on Capacity instead of Allocatable(default) of the nodes. </td>
+<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2) </td>
 </tr>
 <tr>
 <td>sort-by</td>
@@ -7432,7 +7138,7 @@ applications.</p>
 <td>selector</td>
 <td>l</td>
 <td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
+<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2) </td>
 </tr>
 <tr>
 <td>sort-by</td>
@@ -7441,12 +7147,6 @@ applications.</p>
 <td>If non-empty, sort pods list using specified field. The field can be either &#39;cpu&#39; or &#39;memory&#39;. </td>
 </tr>
 <tr>
-<td>sum</td>
-<td></td>
-<td>false</td>
-<td>Print the sum of the resource usage </td>
-</tr>
-<tr>
 <td>use-protocol-buffers</td>
 <td></td>
 <td>true</td>
@@ -7466,102 +7166,6 @@ applications.</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl api-versions</code></p>
 <hr>
-<h1 id="api-resources">api-resources</h1>
-<blockquote class="code-block example">
-<p> Print the supported API resources</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell"><span class="hljs-attribute">kubectl api-resources</span>
-</code></pre>
-<blockquote class="code-block example">
-<p> Print the supported API resources with more information</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell"><span class="hljs-attribute">kubectl api-resources -o wide</span>
-</code></pre>
-<blockquote class="code-block example">
-<p> Print the supported API resources sorted by a column</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl api-<span class="hljs-built_in">resources</span> --<span class="hljs-built_in">sort</span>-by=<span class="hljs-built_in">name</span>
-</code></pre>
-<blockquote class="code-block example">
-<p> Print the supported namespaced resources</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell"><span class="hljs-attribute">kubectl</span> api-resources --namespaced=<span class="hljs-literal">true</span>
-</code></pre>
-<blockquote class="code-block example">
-<p> Print the supported non-namespaced resources</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell"><span class="hljs-attribute">kubectl</span> api-resources --namespaced=<span class="hljs-literal">false</span>
-</code></pre>
-<blockquote class="code-block example">
-<p> Print the supported API resources with a specific APIGroup</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl api-resources <span class="hljs-attribute">--api-group</span>=rbac.authorization.k8s.io
-</code></pre>
-<p>Print the supported API resources on the server.</p>
-<h3 id="usage">Usage</h3>
-<p><code>$ kubectl api-resources</code></p>
-<h3 id="flags">Flags</h3>
-<table>
-<thead>
-<tr>
-<th>Name</th>
-<th>Shorthand</th>
-<th>Default</th>
-<th>Usage</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>api-group</td>
-<td></td>
-<td></td>
-<td>Limit to resources in the specified API group. </td>
-</tr>
-<tr>
-<td>cached</td>
-<td></td>
-<td>false</td>
-<td>Use the cached list of resources if available. </td>
-</tr>
-<tr>
-<td>categories</td>
-<td></td>
-<td>[]</td>
-<td>Limit to resources that belong the the specified categories. </td>
-</tr>
-<tr>
-<td>namespaced</td>
-<td></td>
-<td>true</td>
-<td>If false, non-namespaced resources will be returned, otherwise returning namespaced resources by default. </td>
-</tr>
-<tr>
-<td>no-headers</td>
-<td></td>
-<td>false</td>
-<td>When using the default or custom-column output format, don&#39;t print headers (default print headers). </td>
-</tr>
-<tr>
-<td>output</td>
-<td>o</td>
-<td></td>
-<td>Output format. One of: (wide, name). </td>
-</tr>
-<tr>
-<td>sort-by</td>
-<td></td>
-<td></td>
-<td>If non-empty, sort list of resources using specified field. The field can be either &#39;name&#39; or &#39;kind&#39;. </td>
-</tr>
-<tr>
-<td>verbs</td>
-<td></td>
-<td>[]</td>
-<td>Limit to resources that support the specified verbs. </td>
-</tr>
-</tbody>
-</table>
-<hr>
 <h1 id="certificate">certificate</h1>
 <p>Modify certificate resources.</p>
 <h3 id="usage">Usage</h3>
@@ -7617,7 +7221,7 @@ applications.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>recursive</td>
@@ -7689,7 +7293,7 @@ applications.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>recursive</td>
@@ -7780,7 +7384,7 @@ applications.</p>
 <td>output</td>
 <td>o</td>
 <td>json</td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>output-directory</td>
@@ -7839,7 +7443,7 @@ applications.</p>
 <td>selector</td>
 <td>l</td>
 <td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
+<td>Selector (label query) to filter on </td>
 </tr>
 </tbody>
 </table>
@@ -7855,7 +7459,11 @@ applications.</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">kubectl drain foo <span class="hljs-attribute">--grace-period</span>=900
 </code></pre>
-<p>Drain node in preparation for maintenance.<br><br> The given node will be marked unschedulable to prevent new pods from arriving. &#39;drain&#39; evicts the pods if the API server supports <a href="https://kubernetes.io/docs/concepts/workloads/pods/disruptions/">https://kubernetes.io/docs/concepts/workloads/pods/disruptions/</a> eviction <a href="https://kubernetes.io/docs/concepts/workloads/pods/disruptions/">https://kubernetes.io/docs/concepts/workloads/pods/disruptions/</a> . Otherwise, it will use normal DELETE to delete the pods. The &#39;drain&#39; evicts or deletes all pods except mirror pods (which cannot be deleted through the API server).  If there are daemon set-managed pods, drain will not proceed without --ignore-daemonsets, and regardless it will not delete any daemon set-managed pods, because those pods would be immediately replaced by the daemon set controller, which ignores unschedulable markings.  If there are any pods that are neither mirror pods nor managed by a replication controller, replica set, daemon set, stateful set, or job, then drain will not delete any pods unless you use --force.  --force will also allow deletion to proceed if the managing resource of one or more pods is missing.<br><br> &#39;drain&#39; waits for graceful termination. You should not operate on the machine until the command completes.<br><br> When you are ready to put the node back into service, use kubectl uncordon, which will make the node schedulable again.<br><br><a href="https://kubernetes.io/images/docs/kubectl_drain.svg">https://kubernetes.io/images/docs/kubectl_drain.svg</a> Workflow<a href="https://kubernetes.io/images/docs/kubectl_drain.svg">https://kubernetes.io/images/docs/kubectl_drain.svg</a></p>
+<p>Drain node in preparation for maintenance.</p>
+<p> The given node will be marked unschedulable to prevent new pods from arriving. &#39;drain&#39; evicts the pods if the API server supports <a href="https://kubernetes.io/docs/concepts/workloads/pods/disruptions/">https://kubernetes.io/docs/concepts/workloads/pods/disruptions/</a> . Otherwise, it will use normal DELETE to delete the pods. The &#39;drain&#39; evicts or deletes all pods except mirror pods (which cannot be deleted through the API server).  If there are daemon set-managed pods, drain will not proceed without --ignore-daemonsets, and regardless it will not delete any daemon set-managed pods, because those pods would be immediately replaced by the daemon set controller, which ignores unschedulable markings.  If there are any pods that are neither mirror pods nor managed by a replication controller, replica set, daemon set, stateful set, or job, then drain will not delete any pods unless you use --force.  --force will also allow deletion to proceed if the managing resource of one or more pods is missing.</p>
+<p> &#39;drain&#39; waits for graceful termination. You should not operate on the machine until the command completes.</p>
+<p> When you are ready to put the node back into service, use kubectl uncordon, which will make the node schedulable again.</p>
+<p> <a href="https://kubernetes.io/images/docs/kubectl_drain.svg">https://kubernetes.io/images/docs/kubectl_drain.svg</a></p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl drain NODE</code></p>
 <h3 id="flags">Flags</h3>
@@ -7903,7 +7511,7 @@ applications.</p>
 <td>force</td>
 <td></td>
 <td>false</td>
-<td>Continue even if there are pods that do not declare a controller. </td>
+<td>Continue even if there are pods not managed by a ReplicationController, ReplicaSet, Job, DaemonSet or StatefulSet. </td>
 </tr>
 <tr>
 <td>grace-period</td>
@@ -7918,6 +7526,12 @@ applications.</p>
 <td>Ignore DaemonSet-managed pods. </td>
 </tr>
 <tr>
+<td>ignore-errors</td>
+<td></td>
+<td>false</td>
+<td>Ignore errors occurred between drain nodes in group. </td>
+</tr>
+<tr>
 <td>pod-selector</td>
 <td></td>
 <td></td>
@@ -7927,7 +7541,7 @@ applications.</p>
 <td>selector</td>
 <td>l</td>
 <td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
+<td>Selector (label query) to filter on </td>
 </tr>
 <tr>
 <td>skip-wait-for-delete-timeout</td>
@@ -7970,7 +7584,15 @@ applications.</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell"><span class="hljs-selector-tag">kubectl</span> <span class="hljs-selector-tag">taint</span> <span class="hljs-selector-tag">nodes</span> <span class="hljs-selector-tag">foo</span> <span class="hljs-selector-tag">bar</span><span class="hljs-selector-pseudo">:NoSchedule</span>
 </code></pre>
-<p>Update the taints on one or more nodes.<br><br>  <em>  A taint consists of a key, value, and effect. As an argument here, it is expressed as key=value:effect.<br>  </em>  The key must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores, up to 253 characters.<br>  <em>  Optionally, the key can begin with a DNS subdomain prefix and a single &#39;/&#39;, like example.com/my-app.<br>  </em>  The value is optional. If given, it must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores, up to 63 characters.<br>  <em>  The effect must be NoSchedule, PreferNoSchedule or NoExecute.<br>  </em>  Currently taint can only apply to node.</p>
+<p>Update the taints on one or more nodes.</p>
+<ul>
+<li>A taint consists of a key, value, and effect. As an argument here, it is expressed as key=value:effect.</li>
+<li>The key must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores, up to  253 characters.</li>
+<li>Optionally, the key can begin with a DNS subdomain prefix and a single &#39;/&#39;, like example.com/my-app.</li>
+<li>The value is optional. If given, it must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores, up to  63 characters.</li>
+<li>The effect must be NoSchedule, PreferNoSchedule or NoExecute.</li>
+<li>Currently taint can only apply to node.</li>
+</ul>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl taint NODE NAME KEY_1=VAL_1:TAINT_EFFECT_1 ... KEY_N=VAL_N:TAINT_EFFECT_N</code></p>
 <h3 id="flags">Flags</h3>
@@ -8012,7 +7634,7 @@ applications.</p>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>overwrite</td>
@@ -8024,7 +7646,7 @@ applications.</p>
 <td>selector</td>
 <td>l</td>
 <td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
+<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2) </td>
 </tr>
 <tr>
 <td>show-managed-fields</td>
@@ -8041,8 +7663,8 @@ applications.</p>
 <tr>
 <td>validate</td>
 <td></td>
-<td>strict</td>
-<td>Must be one of: strict (or true), warn, ignore (or false).<br>        &quot;true&quot; or &quot;strict&quot; will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not.<br>        &quot;warn&quot; will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as &quot;ignore&quot; otherwise.<br>        &quot;false&quot; or &quot;ignore&quot; will not perform any schema validation, silently dropping any unknown or duplicate fields. </td>
+<td>true</td>
+<td>If true, use a schema to validate the input before sending it </td>
 </tr>
 </tbody>
 </table>
@@ -8077,7 +7699,7 @@ applications.</p>
 <td>selector</td>
 <td>l</td>
 <td></td>
-<td>Selector (label query) to filter on, supports &#39;=&#39;, &#39;==&#39;, and &#39;!=&#39;.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. </td>
+<td>Selector (label query) to filter on </td>
 </tr>
 </tbody>
 </table>
@@ -8088,28 +7710,40 @@ applications.</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl alpha</code></p>
 <hr>
-<h2 id="-em-auth-em-"><em>auth</em></h2>
-<p>Inspect authorization</p>
-<h3 id="usage">Usage</h3>
-<p><code>$ kubectl alpha auth</code></p>
-<hr>
-<h2 id="-em-auth-whoami-em-"><em>auth whoami</em></h2>
+<h1 id="api-resources">api-resources</h1>
 <blockquote class="code-block example">
-<p> Get your subject attributes.</p>
+<p> Print the supported API resources</p>
 </blockquote>
-<pre class="code-block example"><code class="lang-shell"><span class="hljs-attribute">kubectl alpha auth whoami</span>
+<pre class="code-block example"><code class="lang-shell"><span class="hljs-attribute">kubectl api-resources</span>
 </code></pre>
 <blockquote class="code-block example">
-<p> Get your subject attributes in JSON format.</p>
+<p> Print the supported API resources with more information</p>
 </blockquote>
-<pre class="code-block example"><code class="lang-shell"><span class="hljs-attribute">kubectl alpha auth whoami -o json</span>
+<pre class="code-block example"><code class="lang-shell"><span class="hljs-attribute">kubectl api-resources -o wide</span>
 </code></pre>
-<p>Experimental: Check who you are and your attributes (groups, extra).</p>
-<p>  This command is helpful to get yourself aware of the current user attributes,
-  especially when dynamic authentication, e.g., token webhook, auth proxy, or OIDC provider,
-  is enabled in the Kubernetes cluster.</p>
+<blockquote class="code-block example">
+<p> Print the supported API resources sorted by a column</p>
+</blockquote>
+<pre class="code-block example"><code class="lang-shell">kubectl api-<span class="hljs-built_in">resources</span> --<span class="hljs-built_in">sort</span>-by=<span class="hljs-built_in">name</span>
+</code></pre>
+<blockquote class="code-block example">
+<p> Print the supported namespaced resources</p>
+</blockquote>
+<pre class="code-block example"><code class="lang-shell"><span class="hljs-attribute">kubectl</span> api-resources --namespaced=<span class="hljs-literal">true</span>
+</code></pre>
+<blockquote class="code-block example">
+<p> Print the supported non-namespaced resources</p>
+</blockquote>
+<pre class="code-block example"><code class="lang-shell"><span class="hljs-attribute">kubectl</span> api-resources --namespaced=<span class="hljs-literal">false</span>
+</code></pre>
+<blockquote class="code-block example">
+<p> Print the supported API resources with a specific APIGroup</p>
+</blockquote>
+<pre class="code-block example"><code class="lang-shell">kubectl api-resources <span class="hljs-attribute">--api-group</span>=extensions
+</code></pre>
+<p>Print the supported API resources on the server.</p>
 <h3 id="usage">Usage</h3>
-<p><code>$ kubectl alpha auth whoami</code></p>
+<p><code>$ kubectl api-resources</code></p>
 <h3 id="flags">Flags</h3>
 <table>
 <thead>
@@ -8122,28 +7756,46 @@ applications.</p>
 </thead>
 <tbody>
 <tr>
-<td>allow-missing-template-keys</td>
+<td>api-group</td>
+<td></td>
+<td></td>
+<td>Limit to resources in the specified API group. </td>
+</tr>
+<tr>
+<td>cached</td>
+<td></td>
+<td>false</td>
+<td>Use the cached list of resources if available. </td>
+</tr>
+<tr>
+<td>namespaced</td>
 <td></td>
 <td>true</td>
-<td>If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. </td>
+<td>If false, non-namespaced resources will be returned, otherwise returning namespaced resources by default. </td>
+</tr>
+<tr>
+<td>no-headers</td>
+<td></td>
+<td>false</td>
+<td>When using the default or custom-column output format, don&#39;t print headers (default print headers). </td>
 </tr>
 <tr>
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: wide&#124;name. </td>
 </tr>
 <tr>
-<td>show-managed-fields</td>
+<td>sort-by</td>
 <td></td>
-<td>false</td>
-<td>If true, keep the managedFields when printing objects in JSON or YAML format. </td>
+<td></td>
+<td>If non-empty, sort list of resources using specified field. The field can be either &#39;name&#39; or &#39;kind&#39;. </td>
 </tr>
 <tr>
-<td>template</td>
+<td>verbs</td>
 <td></td>
-<td></td>
-<td>Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates <span>[</span><a href="http://golang.org/pkg/text/template/#pkg-overview">http://golang.org/pkg/text/template/#pkg-overview</a><span>]</span>. </td>
+<td>[]</td>
+<td>Limit to resources that support the specified verbs. </td>
 </tr>
 </tbody>
 </table>
@@ -8192,66 +7844,28 @@ source <span class="hljs-variable">$HOME</span>/.bash_profile</span>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell"><span class="hljs-attribute">kubectl</span> completion zsh &gt; <span class="hljs-string">"<span class="hljs-variable">${fpath[1]}</span>/_kubectl"</span>
 </code></pre>
-<blockquote class="code-block example">
-<p> Load the kubectl completion code for fish[2] into the current shell</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl completion fish <span class="hljs-string">| source</span>
-</code></pre>
-<blockquote class="code-block example">
-<p> To load completions for each session, execute once:</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl completion fish &gt; ~<span class="hljs-regexp">/.config/</span>fish<span class="hljs-regexp">/completions/</span>kubectl.fish
-</code></pre>
-<blockquote class="code-block example">
-<p> Load the kubectl completion code for powershell into the current shell</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl completion powershell | <span class="hljs-keyword">Out</span>-<span class="hljs-keyword">String</span> | Invoke-<span class="hljs-keyword">Expression</span>
-</code></pre>
-<blockquote class="code-block example">
-<p> Set kubectl completion code for powershell to run on startup ## Save completion code to a script and execute in the profile</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl completion powershell &gt; $HOME\.kube\completion.ps1
-<span class="hljs-keyword">Add</span><span class="bash">-Content <span class="hljs-variable">$PROFILE</span> <span class="hljs-string">"<span class="hljs-variable">$HOME</span>\.kube\completion.ps1"</span></span>
-</code></pre>
-<blockquote class="code-block example#">
-<p> Execute completion code in the profile</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">Add-Content $PROFILE <span class="hljs-string">"if (Get-Command kubectl -ErrorAction SilentlyContinue) {</span>
-kubectl completion powershell <span class="hljs-string">| Out-String | Invoke-Expression</span>
-}<span class="hljs-string">"</span>
-</code></pre>
-<blockquote class="code-block example#">
-<p> Add completion code directly to the $PROFILE script</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell"><span class="hljs-attribute">kubectl</span> completion powershell &gt;&gt; <span class="hljs-variable">$PROFILE</span>
-</code></pre>
-<p>Output shell completion code for the specified shell (bash, zsh, fish, or powershell). The shell code must be evaluated to provide interactive completion of kubectl commands.  This can be done by sourcing it from the .bash_profile.<br><br> Detailed instructions on how to do this are available here:<br><br>  for macOS:<br>  <a href="https://kubernetes.io/docs/tasks/tools/install-kubectl-macos/#enable-shell-autocompletion">https://kubernetes.io/docs/tasks/tools/install-kubectl-macos/#enable-shell-autocompletion</a><br>  <br>  for linux:<br>  <a href="https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/#enable-shell-autocompletion">https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/#enable-shell-autocompletion</a><br>  <br>  for windows:<br>  <a href="https://kubernetes.io/docs/tasks/tools/install-kubectl-windows/#enable-shell-autocompletion">https://kubernetes.io/docs/tasks/tools/install-kubectl-windows/#enable-shell-autocompletion</a><br>  <br> Note for zsh users: <span>[</span>1<span>]</span> zsh completions are only supported in versions of zsh &gt;= 5.2.</p>
+<p>Output shell completion code for the specified shell (bash or zsh). The shell code must be evaluated to provide interactive completion of kubectl commands.  This can be done by sourcing it from the .bash_profile.</p>
+<p> Detailed instructions on how to do this are available here:</p>
+<p>  for macOS:
+  <a href="https://kubernetes.io/docs/tasks/tools/install-kubectl-macos/#enable-shell-autocompletion">https://kubernetes.io/docs/tasks/tools/install-kubectl-macos/#enable-shell-autocompletion</a></p>
+<p>  for linux:
+  <a href="https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/#enable-shell-autocompletion">https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/#enable-shell-autocompletion</a></p>
+<p>  for windows:
+  <a href="https://kubernetes.io/docs/tasks/tools/install-kubectl-windows/#enable-shell-autocompletion">https://kubernetes.io/docs/tasks/tools/install-kubectl-windows/#enable-shell-autocompletion</a></p>
+<p> Note for zsh users: <span>[</span>1<span>]</span> zsh completions are only supported in versions of zsh &gt;= 5.2.</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl completion SHELL</code></p>
 <hr>
 <h1 id="config">config</h1>
-<p>Modify kubeconfig files using subcommands like &quot;kubectl config set current-context my-context&quot;<br><br> The loading order follows these rules:<br><br>  1.  If the --kubeconfig flag is set, then only that file is loaded. The flag may only be set once and no merging takes place.<br>  2.  If $KUBECONFIG environment variable is set, then it is used as a list of paths (normal path delimiting rules for your system). These paths are merged. When a value is modified, it is modified in the file that defines the stanza. When a value is created, it is created in the first file that exists. If no files in the chain exist, then it creates the last file in the list.<br>  3.  Otherwise, ${HOME}/.kube/config is used and no merging takes place.</p>
+<p>Modify kubeconfig files using subcommands like &quot;kubectl config set current-context my-context&quot;</p>
+<p> The loading order follows these rules:</p>
+<ol>
+<li>If the --kubeconfig flag is set, then only that file is loaded. The flag may only be set once and no merging takes place.</li>
+<li>If $KUBECONFIG environment variable is set, then it is used as a list of paths (normal path delimiting rules for your system). These paths are merged. When a value is modified, it is modified in the file that defines the stanza. When a value is created, it is created in the first file that exists. If no files in the chain exist, then it creates the last file in the list.</li>
+<li>Otherwise, ${HOME}/.kube/config is used and no merging takes place.</li>
+</ol>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl config SUBCOMMAND</code></p>
-<h3 id="flags">Flags</h3>
-<table>
-<thead>
-<tr>
-<th>Name</th>
-<th>Shorthand</th>
-<th>Default</th>
-<th>Usage</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>kubeconfig</td>
-<td></td>
-<td></td>
-<td>use a particular kubeconfig file </td>
-</tr>
-</tbody>
-</table>
 <hr>
 <h2 id="-em-current-context-em-"><em>current-context</em></h2>
 <blockquote class="code-block example">
@@ -8338,7 +7952,7 @@ kubectl completion powershell <span class="hljs-string">| Out-String | Invoke-Ex
 <td>output</td>
 <td>o</td>
 <td></td>
-<td>Output format. One of: (name). </td>
+<td>Output format. One of: name </td>
 </tr>
 </tbody>
 </table>
@@ -8425,7 +8039,7 @@ kubectl completion powershell <span class="hljs-string">| Out-String | Invoke-Ex
 <pre class="code-block example"><code class="lang-shell">kubectl<span class="hljs-built_in"> config </span>set-cluster e2e --embed-certs <span class="hljs-attribute">--certificate-authority</span>=~/.kube/e2e/kubernetes.ca.crt
 </code></pre>
 <blockquote class="code-block example">
-<p> Disable cert checking for the e2e cluster entry</p>
+<p> Disable cert checking for the dev cluster entry</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">kubectl<span class="hljs-built_in"> config </span>set-cluster e2e <span class="hljs-attribute">--insecure-skip-tls-verify</span>=<span class="hljs-literal">true</span>
 </code></pre>
@@ -8434,11 +8048,6 @@ kubectl completion powershell <span class="hljs-string">| Out-String | Invoke-Ex
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">kubectl<span class="hljs-built_in"> config </span>set-cluster e2e <span class="hljs-attribute">--tls-server-name</span>=my-cluster-name
 </code></pre>
-<blockquote class="code-block example">
-<p> Set proxy url for the e2e cluster entry</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl<span class="hljs-built_in"> config </span>set-cluster e2e <span class="hljs-attribute">--proxy-url</span>=https://1.2.3.4
-</code></pre>
 <p>Set a cluster entry in kubeconfig.</p>
 <p> Specifying a name that already exists will merge new fields on top of existing values for those fields.</p>
 <h3 id="usage">Usage</h3>
@@ -8455,41 +8064,11 @@ kubectl completion powershell <span class="hljs-string">| Out-String | Invoke-Ex
 </thead>
 <tbody>
 <tr>
-<td>certificate-authority</td>
-<td></td>
-<td></td>
-<td>Path to certificate-authority file for the cluster entry in kubeconfig </td>
-</tr>
-<tr>
 <td>embed-certs</td>
 <td></td>
 <td>false</td>
 <td>embed-certs for the cluster entry in kubeconfig </td>
 </tr>
-<tr>
-<td>insecure-skip-tls-verify</td>
-<td></td>
-<td>false</td>
-<td>insecure-skip-tls-verify for the cluster entry in kubeconfig </td>
-</tr>
-<tr>
-<td>proxy-url</td>
-<td></td>
-<td></td>
-<td>proxy-url for the cluster entry in kubeconfig </td>
-</tr>
-<tr>
-<td>server</td>
-<td></td>
-<td></td>
-<td>server for the cluster entry in kubeconfig </td>
-</tr>
-<tr>
-<td>tls-server-name</td>
-<td></td>
-<td></td>
-<td>tls-server-name for the cluster entry in kubeconfig </td>
-</tr>
 </tbody>
 </table>
 <hr>
@@ -8515,29 +8094,11 @@ kubectl completion powershell <span class="hljs-string">| Out-String | Invoke-Ex
 </thead>
 <tbody>
 <tr>
-<td>cluster</td>
-<td></td>
-<td></td>
-<td>cluster for the context entry in kubeconfig </td>
-</tr>
-<tr>
 <td>current</td>
 <td></td>
 <td>false</td>
 <td>Modify the current context </td>
 </tr>
-<tr>
-<td>namespace</td>
-<td></td>
-<td></td>
-<td>namespace for the context entry in kubeconfig </td>
-</tr>
-<tr>
-<td>user</td>
-<td></td>
-<td></td>
-<td>user for the context entry in kubeconfig </td>
-</tr>
 </tbody>
 </table>
 <hr>
@@ -8627,18 +8188,6 @@ kubectl completion powershell <span class="hljs-string">| Out-String | Invoke-Ex
 <td>&#39;key=value&#39; arguments for the auth provider </td>
 </tr>
 <tr>
-<td>client-certificate</td>
-<td></td>
-<td></td>
-<td>Path to client-certificate file for the user entry in kubeconfig </td>
-</tr>
-<tr>
-<td>client-key</td>
-<td></td>
-<td></td>
-<td>Path to client-key file for the user entry in kubeconfig </td>
-</tr>
-<tr>
 <td>embed-certs</td>
 <td></td>
 <td>false</td>
@@ -8668,24 +8217,6 @@ kubectl completion powershell <span class="hljs-string">| Out-String | Invoke-Ex
 <td>[]</td>
 <td>&#39;key=value&#39; environment values for the exec credential plugin </td>
 </tr>
-<tr>
-<td>password</td>
-<td></td>
-<td></td>
-<td>password for the user entry in kubeconfig </td>
-</tr>
-<tr>
-<td>token</td>
-<td></td>
-<td></td>
-<td>token for the user entry in kubeconfig </td>
-</tr>
-<tr>
-<td>username</td>
-<td></td>
-<td></td>
-<td>username for the user entry in kubeconfig </td>
-</tr>
 </tbody>
 </table>
 <hr>
@@ -8722,7 +8253,7 @@ kubectl completion powershell <span class="hljs-string">| Out-String | Invoke-Ex
 <pre class="code-block example"><code class="lang-shell">kubectl<span class="hljs-built_in"> config </span>view
 </code></pre>
 <blockquote class="code-block example">
-<p> Show merged kubeconfig settings and raw certificate data and exposed secrets</p>
+<p> Show merged kubeconfig settings and raw certificate data</p>
 </blockquote>
 <pre class="code-block example"><code class="lang-shell">kubectl<span class="hljs-built_in"> config </span>view --raw
 </code></pre>
@@ -8774,13 +8305,13 @@ kubectl completion powershell <span class="hljs-string">| Out-String | Invoke-Ex
 <td>output</td>
 <td>o</td>
 <td>yaml</td>
-<td>Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). </td>
+<td>Output format. One of: json&#124;yaml&#124;name&#124;go-template&#124;go-template-file&#124;template&#124;templatefile&#124;jsonpath&#124;jsonpath-as-json&#124;jsonpath-file. </td>
 </tr>
 <tr>
 <td>raw</td>
 <td></td>
 <td>false</td>
-<td>Display raw byte data and sensitive data </td>
+<td>Display raw byte data </td>
 </tr>
 <tr>
 <td>show-managed-fields</td>
@@ -8808,7 +8339,11 @@ kubectl completion powershell <span class="hljs-string">| Out-String | Invoke-Ex
 </blockquote>
 <pre class="code-block example"><code class="lang-shell"><span class="hljs-selector-tag">kubectl</span> <span class="hljs-selector-tag">explain</span> <span class="hljs-selector-tag">pods</span><span class="hljs-selector-class">.spec</span><span class="hljs-selector-class">.containers</span>
 </code></pre>
-<p>List the fields for supported resources.<br><br> This command describes the fields associated with each supported API resource. Fields are identified via a simple JSONPath identifier:<br><br>  &lt;type&gt;.&lt;fieldName&gt;<span>[</span>.&lt;fieldName&gt;<span>]</span><br>  <br> Add the --recursive flag to display all of the fields at once without descriptions. Information about each field is retrieved from the server in OpenAPI format.<br><br>Use &quot;kubectl api-resources&quot; for a complete list of supported resources.</p>
+<p>List the fields for supported resources.</p>
+<p> This command describes the fields associated with each supported API resource. Fields are identified via a simple JSONPath identifier:</p>
+<p>  &lt;type&gt;.&lt;fieldName&gt;<span>[</span>.&lt;fieldName&gt;<span>]</span></p>
+<p> Add the --recursive flag to display all of the fields at once without descriptions. Information about each field is retrieved from the server in OpenAPI format.</p>
+<p>Use &quot;kubectl api-resources&quot; for a complete list of supported resources.</p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl explain RESOURCE</code></p>
 <h3 id="flags">Flags</h3>
@@ -8848,16 +8383,13 @@ kubectl completion powershell <span class="hljs-string">| Out-String | Invoke-Ex
 <p><code>$ kubectl options</code></p>
 <hr>
 <h1 id="plugin">plugin</h1>
-<p>Provides utilities for interacting with plugins.<br><br> Plugins provide extended functionality that is not part of the major command-line distribution. Please refer to the documentation and examples for more information about how write your own plugins.<br><br> The easiest way to discover and install plugins is via the kubernetes sub-project krew. To install krew, visit <a href="https://krew.sigs.k8s.io/docs/user-guide/setup/install/">https://krew.sigs.k8s.io/docs/user-guide/setup/install/</a> krew.sigs.k8s.io <a href="https://krew.sigs.k8s.io/docs/user-guide/setup/install/">https://krew.sigs.k8s.io/docs/user-guide/setup/install/</a></p>
+<p>Provides utilities for interacting with plugins.</p>
+<p> Plugins provide extended functionality that is not part of the major command-line distribution. Please refer to the documentation and examples for more information about how write your own plugins.</p>
+<p> The easiest way to discover and install plugins is via the kubernetes sub-project krew. To install krew, visit <a href="https://krew.sigs.k8s.io/docs/user-guide/setup/install/">https://krew.sigs.k8s.io/docs/user-guide/setup/install/</a></p>
 <h3 id="usage">Usage</h3>
 <p><code>$ kubectl plugin [flags]</code></p>
 <hr>
 <h2 id="-em-list-em-"><em>list</em></h2>
-<blockquote class="code-block example">
-<p> List all available plugins</p>
-</blockquote>
-<pre class="code-block example"><code class="lang-shell">kubectl <span class="hljs-keyword">plugin</span> <span class="hljs-keyword">list</span>
-</code></pre>
 <p>List all available plugin files on a user&#39;s PATH.</p>
 <p> Available plugin files are those that are: - executable - anywhere on the user&#39;s PATH - begin with &quot;kubectl-&quot;</p>
 <h3 id="usage">Usage</h3>
diff --git a/static/docs/reference/generated/kubectl/navData.js b/static/docs/reference/generated/kubectl/navData.js
index 636aa29b90f..e6f8f066deb 100644
--- a/static/docs/reference/generated/kubectl/navData.js
+++ b/static/docs/reference/generated/kubectl/navData.js
@@ -1 +1 @@
-(function(){navData = {"toc":[{"section":"version","subsections":[]},{"section":"plugin","subsections":[{"section":"-em-list-em-"}]},{"section":"options","subsections":[]},{"section":"explain","subsections":[]},{"section":"config","subsections":[{"section":"-em-view-em-"},{"section":"-em-use-context-em-"},{"section":"-em-unset-em-"},{"section":"-em-set-credentials-em-"},{"section":"-em-set-context-em-"},{"section":"-em-set-cluster-em-"},{"section":"-em-set-em-"},{"section":"-em-rename-context-em-"},{"section":"-em-get-users-em-"},{"section":"-em-get-contexts-em-"},{"section":"-em-get-clusters-em-"},{"section":"-em-delete-user-em-"},{"section":"-em-delete-context-em-"},{"section":"-em-delete-cluster-em-"},{"section":"-em-current-context-em-"}]},{"section":"completion","subsections":[]},{"section":"alpha","subsections":[{"section":"-em-auth-whoami-em-"},{"section":"-em-auth-em-"}]},{"section":"-strong-kubectl-settings-and-usage-strong-","subsections":[]},{"section":"uncordon","subsections":[]},{"section":"taint","subsections":[]},{"section":"drain","subsections":[]},{"section":"cordon","subsections":[]},{"section":"cluster-info","subsections":[{"section":"-em-dump-em-"}]},{"section":"certificate","subsections":[{"section":"-em-deny-em-"},{"section":"-em-approve-em-"}]},{"section":"api-resources","subsections":[]},{"section":"api-versions","subsections":[]},{"section":"-strong-cluster-management-strong-","subsections":[]},{"section":"top","subsections":[{"section":"-em-pod-em-"},{"section":"-em-node-em-"}]},{"section":"proxy","subsections":[]},{"section":"port-forward","subsections":[]},{"section":"logs","subsections":[]},{"section":"exec","subsections":[]},{"section":"events","subsections":[]},{"section":"describe","subsections":[]},{"section":"cp","subsections":[]},{"section":"auth","subsections":[{"section":"-em-reconcile-em-"},{"section":"-em-can-i-em-"}]},{"section":"attach","subsections":[]},{"section":"-strong-working-with-apps-strong-","subsections":[]},{"section":"wait","subsections":[]},{"section":"set","subsections":[{"section":"-em-subject-em-"},{"section":"-em-serviceaccount-em--1"},{"section":"-em-selector-em-"},{"section":"-em-resources-em-"},{"section":"-em-image-em-"},{"section":"-em-env-em-"}]},{"section":"scale","subsections":[]},{"section":"rollout","subsections":[{"section":"-em-undo-em-"},{"section":"-em-status-em-"},{"section":"-em-resume-em-"},{"section":"-em-restart-em-"},{"section":"-em-pause-em-"},{"section":"-em-history-em-"}]},{"section":"replace","subsections":[]},{"section":"patch","subsections":[]},{"section":"label","subsections":[]},{"section":"kustomize","subsections":[]},{"section":"edit","subsections":[]},{"section":"diff","subsections":[]},{"section":"debug","subsections":[]},{"section":"autoscale","subsections":[]},{"section":"annotate","subsections":[]},{"section":"apply","subsections":[{"section":"-em-view-last-applied-em-"},{"section":"-em-set-last-applied-em-"},{"section":"-em-edit-last-applied-em-"}]},{"section":"-strong-app-management-strong-","subsections":[]},{"section":"delete","subsections":[]},{"section":"expose","subsections":[]},{"section":"run","subsections":[]},{"section":"get","subsections":[]},{"section":"create","subsections":[{"section":"-em-token-em-"},{"section":"-em-serviceaccount-em-"},{"section":"-em-service-nodeport-em-"},{"section":"-em-service-loadbalancer-em-"},{"section":"-em-service-externalname-em-"},{"section":"-em-service-clusterip-em-"},{"section":"-em-service-em-"},{"section":"-em-secret-tls-em-"},{"section":"-em-secret-generic-em-"},{"section":"-em-secret-docker-registry-em-"},{"section":"-em-secret-em-"},{"section":"-em-rolebinding-em-"},{"section":"-em-role-em-"},{"section":"-em-quota-em-"},{"section":"-em-priorityclass-em-"},{"section":"-em-poddisruptionbudget-em-"},{"section":"-em-namespace-em-"},{"section":"-em-job-em-"},{"section":"-em-ingress-em-"},{"section":"-em-deployment-em-"},{"section":"-em-cronjob-em-"},{"section":"-em-configmap-em-"},{"section":"-em-clusterrolebinding-em-"},{"section":"-em-clusterrole-em-"}]},{"section":"-strong-getting-started-strong-","subsections":[]}],"flatToc":["version","-em-list-em-","plugin","options","explain","-em-view-em-","-em-use-context-em-","-em-unset-em-","-em-set-credentials-em-","-em-set-context-em-","-em-set-cluster-em-","-em-set-em-","-em-rename-context-em-","-em-get-users-em-","-em-get-contexts-em-","-em-get-clusters-em-","-em-delete-user-em-","-em-delete-context-em-","-em-delete-cluster-em-","-em-current-context-em-","config","completion","-em-auth-whoami-em-","-em-auth-em-","alpha","-strong-kubectl-settings-and-usage-strong-","uncordon","taint","drain","cordon","-em-dump-em-","cluster-info","-em-deny-em-","-em-approve-em-","certificate","api-resources","api-versions","-strong-cluster-management-strong-","-em-pod-em-","-em-node-em-","top","proxy","port-forward","logs","exec","events","describe","cp","-em-reconcile-em-","-em-can-i-em-","auth","attach","-strong-working-with-apps-strong-","wait","-em-subject-em-","-em-serviceaccount-em--1","-em-selector-em-","-em-resources-em-","-em-image-em-","-em-env-em-","set","scale","-em-undo-em-","-em-status-em-","-em-resume-em-","-em-restart-em-","-em-pause-em-","-em-history-em-","rollout","replace","patch","label","kustomize","edit","diff","debug","autoscale","annotate","-em-view-last-applied-em-","-em-set-last-applied-em-","-em-edit-last-applied-em-","apply","-strong-app-management-strong-","delete","expose","run","get","-em-token-em-","-em-serviceaccount-em-","-em-service-nodeport-em-","-em-service-loadbalancer-em-","-em-service-externalname-em-","-em-service-clusterip-em-","-em-service-em-","-em-secret-tls-em-","-em-secret-generic-em-","-em-secret-docker-registry-em-","-em-secret-em-","-em-rolebinding-em-","-em-role-em-","-em-quota-em-","-em-priorityclass-em-","-em-poddisruptionbudget-em-","-em-namespace-em-","-em-job-em-","-em-ingress-em-","-em-deployment-em-","-em-cronjob-em-","-em-configmap-em-","-em-clusterrolebinding-em-","-em-clusterrole-em-","create","-strong-getting-started-strong-"]};})();
\ No newline at end of file
+(function(){navData = {"toc":[{"section":"version","subsections":[]},{"section":"plugin","subsections":[{"section":"-em-list-em-"}]},{"section":"options","subsections":[]},{"section":"explain","subsections":[]},{"section":"config","subsections":[{"section":"-em-view-em-"},{"section":"-em-use-context-em-"},{"section":"-em-unset-em-"},{"section":"-em-set-credentials-em-"},{"section":"-em-set-context-em-"},{"section":"-em-set-cluster-em-"},{"section":"-em-set-em-"},{"section":"-em-rename-context-em-"},{"section":"-em-get-users-em-"},{"section":"-em-get-contexts-em-"},{"section":"-em-get-clusters-em-"},{"section":"-em-delete-user-em-"},{"section":"-em-delete-context-em-"},{"section":"-em-delete-cluster-em-"},{"section":"-em-current-context-em-"}]},{"section":"completion","subsections":[]},{"section":"api-resources","subsections":[]},{"section":"alpha","subsections":[]},{"section":"-strong-kubectl-settings-and-usage-strong-","subsections":[]},{"section":"uncordon","subsections":[]},{"section":"taint","subsections":[]},{"section":"drain","subsections":[]},{"section":"cordon","subsections":[]},{"section":"cluster-info","subsections":[{"section":"-em-dump-em-"}]},{"section":"certificate","subsections":[{"section":"-em-deny-em-"},{"section":"-em-approve-em-"}]},{"section":"api-versions","subsections":[]},{"section":"-strong-cluster-management-strong-","subsections":[]},{"section":"top","subsections":[{"section":"-em-pod-em-"},{"section":"-em-node-em-"}]},{"section":"proxy","subsections":[]},{"section":"port-forward","subsections":[]},{"section":"logs","subsections":[]},{"section":"exec","subsections":[]},{"section":"describe","subsections":[]},{"section":"cp","subsections":[]},{"section":"auth","subsections":[{"section":"-em-reconcile-em-"},{"section":"-em-can-i-em-"}]},{"section":"attach","subsections":[]},{"section":"-strong-working-with-apps-strong-","subsections":[]},{"section":"wait","subsections":[]},{"section":"set","subsections":[{"section":"-em-subject-em-"},{"section":"-em-serviceaccount-em--1"},{"section":"-em-selector-em-"},{"section":"-em-resources-em-"},{"section":"-em-image-em-"},{"section":"-em-env-em-"}]},{"section":"scale","subsections":[]},{"section":"rollout","subsections":[{"section":"-em-undo-em-"},{"section":"-em-status-em-"},{"section":"-em-resume-em-"},{"section":"-em-restart-em-"},{"section":"-em-pause-em-"},{"section":"-em-history-em-"}]},{"section":"replace","subsections":[]},{"section":"patch","subsections":[]},{"section":"label","subsections":[]},{"section":"kustomize","subsections":[]},{"section":"edit","subsections":[]},{"section":"diff","subsections":[]},{"section":"debug","subsections":[]},{"section":"autoscale","subsections":[]},{"section":"annotate","subsections":[]},{"section":"apply","subsections":[{"section":"-em-view-last-applied-em-"},{"section":"-em-set-last-applied-em-"},{"section":"-em-edit-last-applied-em-"}]},{"section":"-strong-app-management-strong-","subsections":[]},{"section":"delete","subsections":[]},{"section":"expose","subsections":[]},{"section":"run","subsections":[]},{"section":"get","subsections":[]},{"section":"create","subsections":[{"section":"-em-serviceaccount-em-"},{"section":"-em-service-nodeport-em-"},{"section":"-em-service-loadbalancer-em-"},{"section":"-em-service-externalname-em-"},{"section":"-em-service-clusterip-em-"},{"section":"-em-service-em-"},{"section":"-em-secret-tls-em-"},{"section":"-em-secret-generic-em-"},{"section":"-em-secret-docker-registry-em-"},{"section":"-em-secret-em-"},{"section":"-em-rolebinding-em-"},{"section":"-em-role-em-"},{"section":"-em-quota-em-"},{"section":"-em-priorityclass-em-"},{"section":"-em-poddisruptionbudget-em-"},{"section":"-em-namespace-em-"},{"section":"-em-job-em-"},{"section":"-em-ingress-em-"},{"section":"-em-deployment-em-"},{"section":"-em-cronjob-em-"},{"section":"-em-configmap-em-"},{"section":"-em-clusterrolebinding-em-"},{"section":"-em-clusterrole-em-"}]},{"section":"-strong-getting-started-strong-","subsections":[]}],"flatToc":["version","-em-list-em-","plugin","options","explain","-em-view-em-","-em-use-context-em-","-em-unset-em-","-em-set-credentials-em-","-em-set-context-em-","-em-set-cluster-em-","-em-set-em-","-em-rename-context-em-","-em-get-users-em-","-em-get-contexts-em-","-em-get-clusters-em-","-em-delete-user-em-","-em-delete-context-em-","-em-delete-cluster-em-","-em-current-context-em-","config","completion","api-resources","alpha","-strong-kubectl-settings-and-usage-strong-","uncordon","taint","drain","cordon","-em-dump-em-","cluster-info","-em-deny-em-","-em-approve-em-","certificate","api-versions","-strong-cluster-management-strong-","-em-pod-em-","-em-node-em-","top","proxy","port-forward","logs","exec","describe","cp","-em-reconcile-em-","-em-can-i-em-","auth","attach","-strong-working-with-apps-strong-","wait","-em-subject-em-","-em-serviceaccount-em--1","-em-selector-em-","-em-resources-em-","-em-image-em-","-em-env-em-","set","scale","-em-undo-em-","-em-status-em-","-em-resume-em-","-em-restart-em-","-em-pause-em-","-em-history-em-","rollout","replace","patch","label","kustomize","edit","diff","debug","autoscale","annotate","-em-view-last-applied-em-","-em-set-last-applied-em-","-em-edit-last-applied-em-","apply","-strong-app-management-strong-","delete","expose","run","get","-em-serviceaccount-em-","-em-service-nodeport-em-","-em-service-loadbalancer-em-","-em-service-externalname-em-","-em-service-clusterip-em-","-em-service-em-","-em-secret-tls-em-","-em-secret-generic-em-","-em-secret-docker-registry-em-","-em-secret-em-","-em-rolebinding-em-","-em-role-em-","-em-quota-em-","-em-priorityclass-em-","-em-poddisruptionbudget-em-","-em-namespace-em-","-em-job-em-","-em-ingress-em-","-em-deployment-em-","-em-cronjob-em-","-em-configmap-em-","-em-clusterrolebinding-em-","-em-clusterrole-em-","create","-strong-getting-started-strong-"]};})();
\ No newline at end of file
diff --git a/static/docs/reference/generated/kubectl/node_modules/jquery.scrollto/jquery.scrollTo.min.js b/static/docs/reference/generated/kubectl/node_modules/jquery.scrollto/jquery.scrollTo.min.js
index 65a020d92ad..3f7d1457532 100644
--- a/static/docs/reference/generated/kubectl/node_modules/jquery.scrollto/jquery.scrollTo.min.js
+++ b/static/docs/reference/generated/kubectl/node_modules/jquery.scrollto/jquery.scrollTo.min.js
@@ -1,7 +1,7 @@
-/**
- * Copyright (c) 2007-2015 Ariel Flesler - aflesler<a>gmail<d>com | http://flesler.blogspot.com
- * Licensed under MIT
- * @author Ariel Flesler
- * @version 2.1.2
- */
-;(function(f){"use strict";"function"===typeof define&&define.amd?define(["jquery"],f):"undefined"!==typeof module&&module.exports?module.exports=f(require("jquery")):f(jQuery)})(function($){"use strict";function n(a){return!a.nodeName||-1!==$.inArray(a.nodeName.toLowerCase(),["iframe","#document","html","body"])}function h(a){return $.isFunction(a)||$.isPlainObject(a)?a:{top:a,left:a}}var p=$.scrollTo=function(a,d,b){return $(window).scrollTo(a,d,b)};p.defaults={axis:"xy",duration:0,limit:!0};$.fn.scrollTo=function(a,d,b){"object"=== typeof d&&(b=d,d=0);"function"===typeof b&&(b={onAfter:b});"max"===a&&(a=9E9);b=$.extend({},p.defaults,b);d=d||b.duration;var u=b.queue&&1<b.axis.length;u&&(d/=2);b.offset=h(b.offset);b.over=h(b.over);return this.each(function(){function k(a){var k=$.extend({},b,{queue:!0,duration:d,complete:a&&function(){a.call(q,e,b)}});r.animate(f,k)}if(null!==a){var l=n(this),q=l?this.contentWindow||window:this,r=$(q),e=a,f={},t;switch(typeof e){case "number":case "string":if(/^([+-]=?)?\d+(\.\d+)?(px|%)?$/.test(e)){e= h(e);break}e=l?$(e):$(e,q);case "object":if(e.length===0)return;if(e.is||e.style)t=(e=$(e)).offset()}var v=$.isFunction(b.offset)&&b.offset(q,e)||b.offset;$.each(b.axis.split(""),function(a,c){var d="x"===c?"Left":"Top",m=d.toLowerCase(),g="scroll"+d,h=r[g](),n=p.max(q,c);t?(f[g]=t[m]+(l?0:h-r.offset()[m]),b.margin&&(f[g]-=parseInt(e.css("margin"+d),10)||0,f[g]-=parseInt(e.css("border"+d+"Width"),10)||0),f[g]+=v[m]||0,b.over[m]&&(f[g]+=e["x"===c?"width":"height"]()*b.over[m])):(d=e[m],f[g]=d.slice&& "%"===d.slice(-1)?parseFloat(d)/100*n:d);b.limit&&/^\d+$/.test(f[g])&&(f[g]=0>=f[g]?0:Math.min(f[g],n));!a&&1<b.axis.length&&(h===f[g]?f={}:u&&(k(b.onAfterFirst),f={}))});k(b.onAfter)}})};p.max=function(a,d){var b="x"===d?"Width":"Height",h="scroll"+b;if(!n(a))return a[h]-$(a)[b.toLowerCase()]();var b="client"+b,k=a.ownerDocument||a.document,l=k.documentElement,k=k.body;return Math.max(l[h],k[h])-Math.min(l[b],k[b])};$.Tween.propHooks.scrollLeft=$.Tween.propHooks.scrollTop={get:function(a){return $(a.elem)[a.prop]()}, set:function(a){var d=this.get(a);if(a.options.interrupt&&a._last&&a._last!==d)return $(a.elem).stop();var b=Math.round(a.now);d!==b&&($(a.elem)[a.prop](b),a._last=this.get(a))}};return p});
\ No newline at end of file
+/**
+ * Copyright (c) 2007 Ariel Flesler - aflesler ○ gmail • com | https://github.com/flesler
+ * Licensed under MIT
+ * @author Ariel Flesler
+ * @version 2.1.3
+ */
+;(function(factory){'use strict';if(typeof define==='function'&&define.amd){define(['jquery'],factory)}else if(typeof module!=='undefined'&&module.exports){module.exports=factory(require('jquery'))}else{factory(jQuery)}})(function($){'use strict';var $scrollTo=$.scrollTo=function(target,duration,settings){return $(window).scrollTo(target,duration,settings)};$scrollTo.defaults={axis:'xy',duration:0,limit:true};function isWin(elem){return!elem.nodeName||$.inArray(elem.nodeName.toLowerCase(),['iframe','#document','html','body'])!==-1}function isFunction(obj){return typeof obj==='function'}$.fn.scrollTo=function(target,duration,settings){if(typeof duration==='object'){settings=duration;duration=0}if(typeof settings==='function'){settings={onAfter:settings}}if(target==='max'){target=9e9}settings=$.extend({},$scrollTo.defaults,settings);duration=duration||settings.duration;var queue=settings.queue&&settings.axis.length>1;if(queue){duration/=2}settings.offset=both(settings.offset);settings.over=both(settings.over);return this.each(function(){if(target===null){return}var win=isWin(this),elem=win?this.contentWindow||window:this,$elem=$(elem),targ=target,attr={},toff;switch(typeof targ){case 'number':case 'string':if(/^([+-]=?)?\d+(\.\d+)?(px|%)?$/.test(targ)){targ=both(targ);break}targ=win?$(targ):$(targ,elem);case 'object':if(targ.length===0){return}if(targ.is||targ.style){toff=(targ=$(targ)).offset()}}var offset=isFunction(settings.offset)&&settings.offset(elem,targ)||settings.offset;$.each(settings.axis.split(''),function(i,axis){var Pos=axis==='x'?'Left':'Top',pos=Pos.toLowerCase(),key='scroll'+Pos,prev=$elem[key](),max=$scrollTo.max(elem,axis);if(toff){attr[key]=toff[pos]+(win?0:prev-$elem.offset()[pos]);if(settings.margin){attr[key]-=parseInt(targ.css('margin'+Pos),10)||0;attr[key]-=parseInt(targ.css('border'+Pos+'Width'),10)||0}attr[key]+=offset[pos]||0;if(settings.over[pos]){attr[key]+=targ[axis==='x'?'width':'height']()*settings.over[pos]}}else{var val=targ[pos];attr[key]=val.slice&&val.slice(-1)==='%'?parseFloat(val)/100*max:val}if(settings.limit&&/^\d+$/.test(attr[key])){attr[key]=attr[key]<=0?0:Math.min(attr[key],max)}if(!i&&settings.axis.length>1){if(prev===attr[key]){attr={}}else if(queue){animate(settings.onAfterFirst);attr={}}}});animate(settings.onAfter);function animate(callback){var opts=$.extend({},settings,{queue:true,duration:duration,complete:callback&&function(){callback.call(elem,targ,settings)}});$elem.animate(attr,opts)}})};$scrollTo.max=function(elem,axis){var Dim=axis==='x'?'Width':'Height',scroll='scroll'+Dim;if(!isWin(elem)){return elem[scroll]-$(elem)[Dim.toLowerCase()]()}var size='client'+Dim,doc=elem.ownerDocument||elem.document,html=doc.documentElement,body=doc.body;return Math.max(html[scroll],body[scroll])-Math.min(html[size],body[size])};function both(val){return isFunction(val)||$.isPlainObject(val)?val:{top:val,left:val}}$.Tween.propHooks.scrollLeft=$.Tween.propHooks.scrollTop={get:function(t){return $(t.elem)[t.prop]()},set:function(t){var curr=this.get(t);if(t.options.interrupt&&t._last&&t._last!==curr){return $(t.elem).stop()}var next=Math.round(t.now);if(curr!==next){$(t.elem)[t.prop](next);t._last=this.get(t)}}};return $scrollTo});
diff --git a/static/docs/reference/generated/kubectl/node_modules/jquery/dist/jquery.min.js b/static/docs/reference/generated/kubectl/node_modules/jquery/dist/jquery.min.js
index a1c07fd803b..c4c6022f298 100644
--- a/static/docs/reference/generated/kubectl/node_modules/jquery/dist/jquery.min.js
+++ b/static/docs/reference/generated/kubectl/node_modules/jquery/dist/jquery.min.js
@@ -1,2 +1,2 @@
-/*! jQuery v3.4.1 | (c) JS Foundation and other contributors | jquery.org/license */
-!function(e,t){"use strict";"object"==typeof module&&"object"==typeof module.exports?module.exports=e.document?t(e,!0):function(e){if(!e.document)throw new Error("jQuery requires a window with a document");return t(e)}:t(e)}("undefined"!=typeof window?window:this,function(C,e){"use strict";var t=[],E=C.document,r=Object.getPrototypeOf,s=t.slice,g=t.concat,u=t.push,i=t.indexOf,n={},o=n.toString,v=n.hasOwnProperty,a=v.toString,l=a.call(Object),y={},m=function(e){return"function"==typeof e&&"number"!=typeof e.nodeType},x=function(e){return null!=e&&e===e.window},c={type:!0,src:!0,nonce:!0,noModule:!0};function b(e,t,n){var r,i,o=(n=n||E).createElement("script");if(o.text=e,t)for(r in c)(i=t[r]||t.getAttribute&&t.getAttribute(r))&&o.setAttribute(r,i);n.head.appendChild(o).parentNode.removeChild(o)}function w(e){return null==e?e+"":"object"==typeof e||"function"==typeof e?n[o.call(e)]||"object":typeof e}var f="3.4.1",k=function(e,t){return new k.fn.init(e,t)},p=/^[\s\uFEFF\xA0]+|[\s\uFEFF\xA0]+$/g;function d(e){var t=!!e&&"length"in e&&e.length,n=w(e);return!m(e)&&!x(e)&&("array"===n||0===t||"number"==typeof t&&0<t&&t-1 in e)}k.fn=k.prototype={jquery:f,constructor:k,length:0,toArray:function(){return s.call(this)},get:function(e){return null==e?s.call(this):e<0?this[e+this.length]:this[e]},pushStack:function(e){var t=k.merge(this.constructor(),e);return t.prevObject=this,t},each:function(e){return k.each(this,e)},map:function(n){return this.pushStack(k.map(this,function(e,t){return n.call(e,t,e)}))},slice:function(){return this.pushStack(s.apply(this,arguments))},first:function(){return this.eq(0)},last:function(){return this.eq(-1)},eq:function(e){var t=this.length,n=+e+(e<0?t:0);return this.pushStack(0<=n&&n<t?[this[n]]:[])},end:function(){return this.prevObject||this.constructor()},push:u,sort:t.sort,splice:t.splice},k.extend=k.fn.extend=function(){var e,t,n,r,i,o,a=arguments[0]||{},s=1,u=arguments.length,l=!1;for("boolean"==typeof a&&(l=a,a=arguments[s]||{},s++),"object"==typeof a||m(a)||(a={}),s===u&&(a=this,s--);s<u;s++)if(null!=(e=arguments[s]))for(t in e)r=e[t],"__proto__"!==t&&a!==r&&(l&&r&&(k.isPlainObject(r)||(i=Array.isArray(r)))?(n=a[t],o=i&&!Array.isArray(n)?[]:i||k.isPlainObject(n)?n:{},i=!1,a[t]=k.extend(l,o,r)):void 0!==r&&(a[t]=r));return a},k.extend({expando:"jQuery"+(f+Math.random()).replace(/\D/g,""),isReady:!0,error:function(e){throw new Error(e)},noop:function(){},isPlainObject:function(e){var t,n;return!(!e||"[object Object]"!==o.call(e))&&(!(t=r(e))||"function"==typeof(n=v.call(t,"constructor")&&t.constructor)&&a.call(n)===l)},isEmptyObject:function(e){var t;for(t in e)return!1;return!0},globalEval:function(e,t){b(e,{nonce:t&&t.nonce})},each:function(e,t){var n,r=0;if(d(e)){for(n=e.length;r<n;r++)if(!1===t.call(e[r],r,e[r]))break}else for(r in e)if(!1===t.call(e[r],r,e[r]))break;return e},trim:function(e){return null==e?"":(e+"").replace(p,"")},makeArray:function(e,t){var n=t||[];return null!=e&&(d(Object(e))?k.merge(n,"string"==typeof e?[e]:e):u.call(n,e)),n},inArray:function(e,t,n){return null==t?-1:i.call(t,e,n)},merge:function(e,t){for(var n=+t.length,r=0,i=e.length;r<n;r++)e[i++]=t[r];return e.length=i,e},grep:function(e,t,n){for(var r=[],i=0,o=e.length,a=!n;i<o;i++)!t(e[i],i)!==a&&r.push(e[i]);return r},map:function(e,t,n){var r,i,o=0,a=[];if(d(e))for(r=e.length;o<r;o++)null!=(i=t(e[o],o,n))&&a.push(i);else for(o in e)null!=(i=t(e[o],o,n))&&a.push(i);return g.apply([],a)},guid:1,support:y}),"function"==typeof Symbol&&(k.fn[Symbol.iterator]=t[Symbol.iterator]),k.each("Boolean Number String Function Array Date RegExp Object Error Symbol".split(" "),function(e,t){n["[object "+t+"]"]=t.toLowerCase()});var h=function(n){var e,d,b,o,i,h,f,g,w,u,l,T,C,a,E,v,s,c,y,k="sizzle"+1*new Date,m=n.document,S=0,r=0,p=ue(),x=ue(),N=ue(),A=ue(),D=function(e,t){return e===t&&(l=!0),0},j={}.hasOwnProperty,t=[],q=t.pop,L=t.push,H=t.push,O=t.slice,P=function(e,t){for(var n=0,r=e.length;n<r;n++)if(e[n]===t)return n;return-1},R="checked|selected|async|autofocus|autoplay|controls|defer|disabled|hidden|ismap|loop|multiple|open|readonly|required|scoped",M="[\\x20\\t\\r\\n\\f]",I="(?:\\\\.|[\\w-]|[^\0-\\xa0])+",W="\\["+M+"*("+I+")(?:"+M+"*([*^$|!~]?=)"+M+"*(?:'((?:\\\\.|[^\\\\'])*)'|\"((?:\\\\.|[^\\\\\"])*)\"|("+I+"))|)"+M+"*\\]",$=":("+I+")(?:\\((('((?:\\\\.|[^\\\\'])*)'|\"((?:\\\\.|[^\\\\\"])*)\")|((?:\\\\.|[^\\\\()[\\]]|"+W+")*)|.*)\\)|)",F=new RegExp(M+"+","g"),B=new RegExp("^"+M+"+|((?:^|[^\\\\])(?:\\\\.)*)"+M+"+$","g"),_=new RegExp("^"+M+"*,"+M+"*"),z=new RegExp("^"+M+"*([>+~]|"+M+")"+M+"*"),U=new RegExp(M+"|>"),X=new RegExp($),V=new RegExp("^"+I+"$"),G={ID:new RegExp("^#("+I+")"),CLASS:new RegExp("^\\.("+I+")"),TAG:new RegExp("^("+I+"|[*])"),ATTR:new RegExp("^"+W),PSEUDO:new RegExp("^"+$),CHILD:new RegExp("^:(only|first|last|nth|nth-last)-(child|of-type)(?:\\("+M+"*(even|odd|(([+-]|)(\\d*)n|)"+M+"*(?:([+-]|)"+M+"*(\\d+)|))"+M+"*\\)|)","i"),bool:new RegExp("^(?:"+R+")$","i"),needsContext:new RegExp("^"+M+"*[>+~]|:(even|odd|eq|gt|lt|nth|first|last)(?:\\("+M+"*((?:-\\d)?\\d*)"+M+"*\\)|)(?=[^-]|$)","i")},Y=/HTML$/i,Q=/^(?:input|select|textarea|button)$/i,J=/^h\d$/i,K=/^[^{]+\{\s*\[native \w/,Z=/^(?:#([\w-]+)|(\w+)|\.([\w-]+))$/,ee=/[+~]/,te=new RegExp("\\\\([\\da-f]{1,6}"+M+"?|("+M+")|.)","ig"),ne=function(e,t,n){var r="0x"+t-65536;return r!=r||n?t:r<0?String.fromCharCode(r+65536):String.fromCharCode(r>>10|55296,1023&r|56320)},re=/([\0-\x1f\x7f]|^-?\d)|^-$|[^\0-\x1f\x7f-\uFFFF\w-]/g,ie=function(e,t){return t?"\0"===e?"\ufffd":e.slice(0,-1)+"\\"+e.charCodeAt(e.length-1).toString(16)+" ":"\\"+e},oe=function(){T()},ae=be(function(e){return!0===e.disabled&&"fieldset"===e.nodeName.toLowerCase()},{dir:"parentNode",next:"legend"});try{H.apply(t=O.call(m.childNodes),m.childNodes),t[m.childNodes.length].nodeType}catch(e){H={apply:t.length?function(e,t){L.apply(e,O.call(t))}:function(e,t){var n=e.length,r=0;while(e[n++]=t[r++]);e.length=n-1}}}function se(t,e,n,r){var i,o,a,s,u,l,c,f=e&&e.ownerDocument,p=e?e.nodeType:9;if(n=n||[],"string"!=typeof t||!t||1!==p&&9!==p&&11!==p)return n;if(!r&&((e?e.ownerDocument||e:m)!==C&&T(e),e=e||C,E)){if(11!==p&&(u=Z.exec(t)))if(i=u[1]){if(9===p){if(!(a=e.getElementById(i)))return n;if(a.id===i)return n.push(a),n}else if(f&&(a=f.getElementById(i))&&y(e,a)&&a.id===i)return n.push(a),n}else{if(u[2])return H.apply(n,e.getElementsByTagName(t)),n;if((i=u[3])&&d.getElementsByClassName&&e.getElementsByClassName)return H.apply(n,e.getElementsByClassName(i)),n}if(d.qsa&&!A[t+" "]&&(!v||!v.test(t))&&(1!==p||"object"!==e.nodeName.toLowerCase())){if(c=t,f=e,1===p&&U.test(t)){(s=e.getAttribute("id"))?s=s.replace(re,ie):e.setAttribute("id",s=k),o=(l=h(t)).length;while(o--)l[o]="#"+s+" "+xe(l[o]);c=l.join(","),f=ee.test(t)&&ye(e.parentNode)||e}try{return H.apply(n,f.querySelectorAll(c)),n}catch(e){A(t,!0)}finally{s===k&&e.removeAttribute("id")}}}return g(t.replace(B,"$1"),e,n,r)}function ue(){var r=[];return function e(t,n){return r.push(t+" ")>b.cacheLength&&delete e[r.shift()],e[t+" "]=n}}function le(e){return e[k]=!0,e}function ce(e){var t=C.createElement("fieldset");try{return!!e(t)}catch(e){return!1}finally{t.parentNode&&t.parentNode.removeChild(t),t=null}}function fe(e,t){var n=e.split("|"),r=n.length;while(r--)b.attrHandle[n[r]]=t}function pe(e,t){var n=t&&e,r=n&&1===e.nodeType&&1===t.nodeType&&e.sourceIndex-t.sourceIndex;if(r)return r;if(n)while(n=n.nextSibling)if(n===t)return-1;return e?1:-1}function de(t){return function(e){return"input"===e.nodeName.toLowerCase()&&e.type===t}}function he(n){return function(e){var t=e.nodeName.toLowerCase();return("input"===t||"button"===t)&&e.type===n}}function ge(t){return function(e){return"form"in e?e.parentNode&&!1===e.disabled?"label"in e?"label"in e.parentNode?e.parentNode.disabled===t:e.disabled===t:e.isDisabled===t||e.isDisabled!==!t&&ae(e)===t:e.disabled===t:"label"in e&&e.disabled===t}}function ve(a){return le(function(o){return o=+o,le(function(e,t){var n,r=a([],e.length,o),i=r.length;while(i--)e[n=r[i]]&&(e[n]=!(t[n]=e[n]))})})}function ye(e){return e&&"undefined"!=typeof e.getElementsByTagName&&e}for(e in d=se.support={},i=se.isXML=function(e){var t=e.namespaceURI,n=(e.ownerDocument||e).documentElement;return!Y.test(t||n&&n.nodeName||"HTML")},T=se.setDocument=function(e){var t,n,r=e?e.ownerDocument||e:m;return r!==C&&9===r.nodeType&&r.documentElement&&(a=(C=r).documentElement,E=!i(C),m!==C&&(n=C.defaultView)&&n.top!==n&&(n.addEventListener?n.addEventListener("unload",oe,!1):n.attachEvent&&n.attachEvent("onunload",oe)),d.attributes=ce(function(e){return e.className="i",!e.getAttribute("className")}),d.getElementsByTagName=ce(function(e){return e.appendChild(C.createComment("")),!e.getElementsByTagName("*").length}),d.getElementsByClassName=K.test(C.getElementsByClassName),d.getById=ce(function(e){return a.appendChild(e).id=k,!C.getElementsByName||!C.getElementsByName(k).length}),d.getById?(b.filter.ID=function(e){var t=e.replace(te,ne);return function(e){return e.getAttribute("id")===t}},b.find.ID=function(e,t){if("undefined"!=typeof t.getElementById&&E){var n=t.getElementById(e);return n?[n]:[]}}):(b.filter.ID=function(e){var n=e.replace(te,ne);return function(e){var t="undefined"!=typeof e.getAttributeNode&&e.getAttributeNode("id");return t&&t.value===n}},b.find.ID=function(e,t){if("undefined"!=typeof t.getElementById&&E){var n,r,i,o=t.getElementById(e);if(o){if((n=o.getAttributeNode("id"))&&n.value===e)return[o];i=t.getElementsByName(e),r=0;while(o=i[r++])if((n=o.getAttributeNode("id"))&&n.value===e)return[o]}return[]}}),b.find.TAG=d.getElementsByTagName?function(e,t){return"undefined"!=typeof t.getElementsByTagName?t.getElementsByTagName(e):d.qsa?t.querySelectorAll(e):void 0}:function(e,t){var n,r=[],i=0,o=t.getElementsByTagName(e);if("*"===e){while(n=o[i++])1===n.nodeType&&r.push(n);return r}return o},b.find.CLASS=d.getElementsByClassName&&function(e,t){if("undefined"!=typeof t.getElementsByClassName&&E)return t.getElementsByClassName(e)},s=[],v=[],(d.qsa=K.test(C.querySelectorAll))&&(ce(function(e){a.appendChild(e).innerHTML="<a id='"+k+"'></a><select id='"+k+"-\r\\' msallowcapture=''><option selected=''></option></select>",e.querySelectorAll("[msallowcapture^='']").length&&v.push("[*^$]="+M+"*(?:''|\"\")"),e.querySelectorAll("[selected]").length||v.push("\\["+M+"*(?:value|"+R+")"),e.querySelectorAll("[id~="+k+"-]").length||v.push("~="),e.querySelectorAll(":checked").length||v.push(":checked"),e.querySelectorAll("a#"+k+"+*").length||v.push(".#.+[+~]")}),ce(function(e){e.innerHTML="<a href='' disabled='disabled'></a><select disabled='disabled'><option/></select>";var t=C.createElement("input");t.setAttribute("type","hidden"),e.appendChild(t).setAttribute("name","D"),e.querySelectorAll("[name=d]").length&&v.push("name"+M+"*[*^$|!~]?="),2!==e.querySelectorAll(":enabled").length&&v.push(":enabled",":disabled"),a.appendChild(e).disabled=!0,2!==e.querySelectorAll(":disabled").length&&v.push(":enabled",":disabled"),e.querySelectorAll("*,:x"),v.push(",.*:")})),(d.matchesSelector=K.test(c=a.matches||a.webkitMatchesSelector||a.mozMatchesSelector||a.oMatchesSelector||a.msMatchesSelector))&&ce(function(e){d.disconnectedMatch=c.call(e,"*"),c.call(e,"[s!='']:x"),s.push("!=",$)}),v=v.length&&new RegExp(v.join("|")),s=s.length&&new RegExp(s.join("|")),t=K.test(a.compareDocumentPosition),y=t||K.test(a.contains)?function(e,t){var n=9===e.nodeType?e.documentElement:e,r=t&&t.parentNode;return e===r||!(!r||1!==r.nodeType||!(n.contains?n.contains(r):e.compareDocumentPosition&&16&e.compareDocumentPosition(r)))}:function(e,t){if(t)while(t=t.parentNode)if(t===e)return!0;return!1},D=t?function(e,t){if(e===t)return l=!0,0;var n=!e.compareDocumentPosition-!t.compareDocumentPosition;return n||(1&(n=(e.ownerDocument||e)===(t.ownerDocument||t)?e.compareDocumentPosition(t):1)||!d.sortDetached&&t.compareDocumentPosition(e)===n?e===C||e.ownerDocument===m&&y(m,e)?-1:t===C||t.ownerDocument===m&&y(m,t)?1:u?P(u,e)-P(u,t):0:4&n?-1:1)}:function(e,t){if(e===t)return l=!0,0;var n,r=0,i=e.parentNode,o=t.parentNode,a=[e],s=[t];if(!i||!o)return e===C?-1:t===C?1:i?-1:o?1:u?P(u,e)-P(u,t):0;if(i===o)return pe(e,t);n=e;while(n=n.parentNode)a.unshift(n);n=t;while(n=n.parentNode)s.unshift(n);while(a[r]===s[r])r++;return r?pe(a[r],s[r]):a[r]===m?-1:s[r]===m?1:0}),C},se.matches=function(e,t){return se(e,null,null,t)},se.matchesSelector=function(e,t){if((e.ownerDocument||e)!==C&&T(e),d.matchesSelector&&E&&!A[t+" "]&&(!s||!s.test(t))&&(!v||!v.test(t)))try{var n=c.call(e,t);if(n||d.disconnectedMatch||e.document&&11!==e.document.nodeType)return n}catch(e){A(t,!0)}return 0<se(t,C,null,[e]).length},se.contains=function(e,t){return(e.ownerDocument||e)!==C&&T(e),y(e,t)},se.attr=function(e,t){(e.ownerDocument||e)!==C&&T(e);var n=b.attrHandle[t.toLowerCase()],r=n&&j.call(b.attrHandle,t.toLowerCase())?n(e,t,!E):void 0;return void 0!==r?r:d.attributes||!E?e.getAttribute(t):(r=e.getAttributeNode(t))&&r.specified?r.value:null},se.escape=function(e){return(e+"").replace(re,ie)},se.error=function(e){throw new Error("Syntax error, unrecognized expression: "+e)},se.uniqueSort=function(e){var t,n=[],r=0,i=0;if(l=!d.detectDuplicates,u=!d.sortStable&&e.slice(0),e.sort(D),l){while(t=e[i++])t===e[i]&&(r=n.push(i));while(r--)e.splice(n[r],1)}return u=null,e},o=se.getText=function(e){var t,n="",r=0,i=e.nodeType;if(i){if(1===i||9===i||11===i){if("string"==typeof e.textContent)return e.textContent;for(e=e.firstChild;e;e=e.nextSibling)n+=o(e)}else if(3===i||4===i)return e.nodeValue}else while(t=e[r++])n+=o(t);return n},(b=se.selectors={cacheLength:50,createPseudo:le,match:G,attrHandle:{},find:{},relative:{">":{dir:"parentNode",first:!0}," ":{dir:"parentNode"},"+":{dir:"previousSibling",first:!0},"~":{dir:"previousSibling"}},preFilter:{ATTR:function(e){return e[1]=e[1].replace(te,ne),e[3]=(e[3]||e[4]||e[5]||"").replace(te,ne),"~="===e[2]&&(e[3]=" "+e[3]+" "),e.slice(0,4)},CHILD:function(e){return e[1]=e[1].toLowerCase(),"nth"===e[1].slice(0,3)?(e[3]||se.error(e[0]),e[4]=+(e[4]?e[5]+(e[6]||1):2*("even"===e[3]||"odd"===e[3])),e[5]=+(e[7]+e[8]||"odd"===e[3])):e[3]&&se.error(e[0]),e},PSEUDO:function(e){var t,n=!e[6]&&e[2];return G.CHILD.test(e[0])?null:(e[3]?e[2]=e[4]||e[5]||"":n&&X.test(n)&&(t=h(n,!0))&&(t=n.indexOf(")",n.length-t)-n.length)&&(e[0]=e[0].slice(0,t),e[2]=n.slice(0,t)),e.slice(0,3))}},filter:{TAG:function(e){var t=e.replace(te,ne).toLowerCase();return"*"===e?function(){return!0}:function(e){return e.nodeName&&e.nodeName.toLowerCase()===t}},CLASS:function(e){var t=p[e+" "];return t||(t=new RegExp("(^|"+M+")"+e+"("+M+"|$)"))&&p(e,function(e){return t.test("string"==typeof e.className&&e.className||"undefined"!=typeof e.getAttribute&&e.getAttribute("class")||"")})},ATTR:function(n,r,i){return function(e){var t=se.attr(e,n);return null==t?"!="===r:!r||(t+="","="===r?t===i:"!="===r?t!==i:"^="===r?i&&0===t.indexOf(i):"*="===r?i&&-1<t.indexOf(i):"$="===r?i&&t.slice(-i.length)===i:"~="===r?-1<(" "+t.replace(F," ")+" ").indexOf(i):"|="===r&&(t===i||t.slice(0,i.length+1)===i+"-"))}},CHILD:function(h,e,t,g,v){var y="nth"!==h.slice(0,3),m="last"!==h.slice(-4),x="of-type"===e;return 1===g&&0===v?function(e){return!!e.parentNode}:function(e,t,n){var r,i,o,a,s,u,l=y!==m?"nextSibling":"previousSibling",c=e.parentNode,f=x&&e.nodeName.toLowerCase(),p=!n&&!x,d=!1;if(c){if(y){while(l){a=e;while(a=a[l])if(x?a.nodeName.toLowerCase()===f:1===a.nodeType)return!1;u=l="only"===h&&!u&&"nextSibling"}return!0}if(u=[m?c.firstChild:c.lastChild],m&&p){d=(s=(r=(i=(o=(a=c)[k]||(a[k]={}))[a.uniqueID]||(o[a.uniqueID]={}))[h]||[])[0]===S&&r[1])&&r[2],a=s&&c.childNodes[s];while(a=++s&&a&&a[l]||(d=s=0)||u.pop())if(1===a.nodeType&&++d&&a===e){i[h]=[S,s,d];break}}else if(p&&(d=s=(r=(i=(o=(a=e)[k]||(a[k]={}))[a.uniqueID]||(o[a.uniqueID]={}))[h]||[])[0]===S&&r[1]),!1===d)while(a=++s&&a&&a[l]||(d=s=0)||u.pop())if((x?a.nodeName.toLowerCase()===f:1===a.nodeType)&&++d&&(p&&((i=(o=a[k]||(a[k]={}))[a.uniqueID]||(o[a.uniqueID]={}))[h]=[S,d]),a===e))break;return(d-=v)===g||d%g==0&&0<=d/g}}},PSEUDO:function(e,o){var t,a=b.pseudos[e]||b.setFilters[e.toLowerCase()]||se.error("unsupported pseudo: "+e);return a[k]?a(o):1<a.length?(t=[e,e,"",o],b.setFilters.hasOwnProperty(e.toLowerCase())?le(function(e,t){var n,r=a(e,o),i=r.length;while(i--)e[n=P(e,r[i])]=!(t[n]=r[i])}):function(e){return a(e,0,t)}):a}},pseudos:{not:le(function(e){var r=[],i=[],s=f(e.replace(B,"$1"));return s[k]?le(function(e,t,n,r){var i,o=s(e,null,r,[]),a=e.length;while(a--)(i=o[a])&&(e[a]=!(t[a]=i))}):function(e,t,n){return r[0]=e,s(r,null,n,i),r[0]=null,!i.pop()}}),has:le(function(t){return function(e){return 0<se(t,e).length}}),contains:le(function(t){return t=t.replace(te,ne),function(e){return-1<(e.textContent||o(e)).indexOf(t)}}),lang:le(function(n){return V.test(n||"")||se.error("unsupported lang: "+n),n=n.replace(te,ne).toLowerCase(),function(e){var t;do{if(t=E?e.lang:e.getAttribute("xml:lang")||e.getAttribute("lang"))return(t=t.toLowerCase())===n||0===t.indexOf(n+"-")}while((e=e.parentNode)&&1===e.nodeType);return!1}}),target:function(e){var t=n.location&&n.location.hash;return t&&t.slice(1)===e.id},root:function(e){return e===a},focus:function(e){return e===C.activeElement&&(!C.hasFocus||C.hasFocus())&&!!(e.type||e.href||~e.tabIndex)},enabled:ge(!1),disabled:ge(!0),checked:function(e){var t=e.nodeName.toLowerCase();return"input"===t&&!!e.checked||"option"===t&&!!e.selected},selected:function(e){return e.parentNode&&e.parentNode.selectedIndex,!0===e.selected},empty:function(e){for(e=e.firstChild;e;e=e.nextSibling)if(e.nodeType<6)return!1;return!0},parent:function(e){return!b.pseudos.empty(e)},header:function(e){return J.test(e.nodeName)},input:function(e){return Q.test(e.nodeName)},button:function(e){var t=e.nodeName.toLowerCase();return"input"===t&&"button"===e.type||"button"===t},text:function(e){var t;return"input"===e.nodeName.toLowerCase()&&"text"===e.type&&(null==(t=e.getAttribute("type"))||"text"===t.toLowerCase())},first:ve(function(){return[0]}),last:ve(function(e,t){return[t-1]}),eq:ve(function(e,t,n){return[n<0?n+t:n]}),even:ve(function(e,t){for(var n=0;n<t;n+=2)e.push(n);return e}),odd:ve(function(e,t){for(var n=1;n<t;n+=2)e.push(n);return e}),lt:ve(function(e,t,n){for(var r=n<0?n+t:t<n?t:n;0<=--r;)e.push(r);return e}),gt:ve(function(e,t,n){for(var r=n<0?n+t:n;++r<t;)e.push(r);return e})}}).pseudos.nth=b.pseudos.eq,{radio:!0,checkbox:!0,file:!0,password:!0,image:!0})b.pseudos[e]=de(e);for(e in{submit:!0,reset:!0})b.pseudos[e]=he(e);function me(){}function xe(e){for(var t=0,n=e.length,r="";t<n;t++)r+=e[t].value;return r}function be(s,e,t){var u=e.dir,l=e.next,c=l||u,f=t&&"parentNode"===c,p=r++;return e.first?function(e,t,n){while(e=e[u])if(1===e.nodeType||f)return s(e,t,n);return!1}:function(e,t,n){var r,i,o,a=[S,p];if(n){while(e=e[u])if((1===e.nodeType||f)&&s(e,t,n))return!0}else while(e=e[u])if(1===e.nodeType||f)if(i=(o=e[k]||(e[k]={}))[e.uniqueID]||(o[e.uniqueID]={}),l&&l===e.nodeName.toLowerCase())e=e[u]||e;else{if((r=i[c])&&r[0]===S&&r[1]===p)return a[2]=r[2];if((i[c]=a)[2]=s(e,t,n))return!0}return!1}}function we(i){return 1<i.length?function(e,t,n){var r=i.length;while(r--)if(!i[r](e,t,n))return!1;return!0}:i[0]}function Te(e,t,n,r,i){for(var o,a=[],s=0,u=e.length,l=null!=t;s<u;s++)(o=e[s])&&(n&&!n(o,r,i)||(a.push(o),l&&t.push(s)));return a}function Ce(d,h,g,v,y,e){return v&&!v[k]&&(v=Ce(v)),y&&!y[k]&&(y=Ce(y,e)),le(function(e,t,n,r){var i,o,a,s=[],u=[],l=t.length,c=e||function(e,t,n){for(var r=0,i=t.length;r<i;r++)se(e,t[r],n);return n}(h||"*",n.nodeType?[n]:n,[]),f=!d||!e&&h?c:Te(c,s,d,n,r),p=g?y||(e?d:l||v)?[]:t:f;if(g&&g(f,p,n,r),v){i=Te(p,u),v(i,[],n,r),o=i.length;while(o--)(a=i[o])&&(p[u[o]]=!(f[u[o]]=a))}if(e){if(y||d){if(y){i=[],o=p.length;while(o--)(a=p[o])&&i.push(f[o]=a);y(null,p=[],i,r)}o=p.length;while(o--)(a=p[o])&&-1<(i=y?P(e,a):s[o])&&(e[i]=!(t[i]=a))}}else p=Te(p===t?p.splice(l,p.length):p),y?y(null,t,p,r):H.apply(t,p)})}function Ee(e){for(var i,t,n,r=e.length,o=b.relative[e[0].type],a=o||b.relative[" "],s=o?1:0,u=be(function(e){return e===i},a,!0),l=be(function(e){return-1<P(i,e)},a,!0),c=[function(e,t,n){var r=!o&&(n||t!==w)||((i=t).nodeType?u(e,t,n):l(e,t,n));return i=null,r}];s<r;s++)if(t=b.relative[e[s].type])c=[be(we(c),t)];else{if((t=b.filter[e[s].type].apply(null,e[s].matches))[k]){for(n=++s;n<r;n++)if(b.relative[e[n].type])break;return Ce(1<s&&we(c),1<s&&xe(e.slice(0,s-1).concat({value:" "===e[s-2].type?"*":""})).replace(B,"$1"),t,s<n&&Ee(e.slice(s,n)),n<r&&Ee(e=e.slice(n)),n<r&&xe(e))}c.push(t)}return we(c)}return me.prototype=b.filters=b.pseudos,b.setFilters=new me,h=se.tokenize=function(e,t){var n,r,i,o,a,s,u,l=x[e+" "];if(l)return t?0:l.slice(0);a=e,s=[],u=b.preFilter;while(a){for(o in n&&!(r=_.exec(a))||(r&&(a=a.slice(r[0].length)||a),s.push(i=[])),n=!1,(r=z.exec(a))&&(n=r.shift(),i.push({value:n,type:r[0].replace(B," ")}),a=a.slice(n.length)),b.filter)!(r=G[o].exec(a))||u[o]&&!(r=u[o](r))||(n=r.shift(),i.push({value:n,type:o,matches:r}),a=a.slice(n.length));if(!n)break}return t?a.length:a?se.error(e):x(e,s).slice(0)},f=se.compile=function(e,t){var n,v,y,m,x,r,i=[],o=[],a=N[e+" "];if(!a){t||(t=h(e)),n=t.length;while(n--)(a=Ee(t[n]))[k]?i.push(a):o.push(a);(a=N(e,(v=o,m=0<(y=i).length,x=0<v.length,r=function(e,t,n,r,i){var o,a,s,u=0,l="0",c=e&&[],f=[],p=w,d=e||x&&b.find.TAG("*",i),h=S+=null==p?1:Math.random()||.1,g=d.length;for(i&&(w=t===C||t||i);l!==g&&null!=(o=d[l]);l++){if(x&&o){a=0,t||o.ownerDocument===C||(T(o),n=!E);while(s=v[a++])if(s(o,t||C,n)){r.push(o);break}i&&(S=h)}m&&((o=!s&&o)&&u--,e&&c.push(o))}if(u+=l,m&&l!==u){a=0;while(s=y[a++])s(c,f,t,n);if(e){if(0<u)while(l--)c[l]||f[l]||(f[l]=q.call(r));f=Te(f)}H.apply(r,f),i&&!e&&0<f.length&&1<u+y.length&&se.uniqueSort(r)}return i&&(S=h,w=p),c},m?le(r):r))).selector=e}return a},g=se.select=function(e,t,n,r){var i,o,a,s,u,l="function"==typeof e&&e,c=!r&&h(e=l.selector||e);if(n=n||[],1===c.length){if(2<(o=c[0]=c[0].slice(0)).length&&"ID"===(a=o[0]).type&&9===t.nodeType&&E&&b.relative[o[1].type]){if(!(t=(b.find.ID(a.matches[0].replace(te,ne),t)||[])[0]))return n;l&&(t=t.parentNode),e=e.slice(o.shift().value.length)}i=G.needsContext.test(e)?0:o.length;while(i--){if(a=o[i],b.relative[s=a.type])break;if((u=b.find[s])&&(r=u(a.matches[0].replace(te,ne),ee.test(o[0].type)&&ye(t.parentNode)||t))){if(o.splice(i,1),!(e=r.length&&xe(o)))return H.apply(n,r),n;break}}}return(l||f(e,c))(r,t,!E,n,!t||ee.test(e)&&ye(t.parentNode)||t),n},d.sortStable=k.split("").sort(D).join("")===k,d.detectDuplicates=!!l,T(),d.sortDetached=ce(function(e){return 1&e.compareDocumentPosition(C.createElement("fieldset"))}),ce(function(e){return e.innerHTML="<a href='#'></a>","#"===e.firstChild.getAttribute("href")})||fe("type|href|height|width",function(e,t,n){if(!n)return e.getAttribute(t,"type"===t.toLowerCase()?1:2)}),d.attributes&&ce(function(e){return e.innerHTML="<input/>",e.firstChild.setAttribute("value",""),""===e.firstChild.getAttribute("value")})||fe("value",function(e,t,n){if(!n&&"input"===e.nodeName.toLowerCase())return e.defaultValue}),ce(function(e){return null==e.getAttribute("disabled")})||fe(R,function(e,t,n){var r;if(!n)return!0===e[t]?t.toLowerCase():(r=e.getAttributeNode(t))&&r.specified?r.value:null}),se}(C);k.find=h,k.expr=h.selectors,k.expr[":"]=k.expr.pseudos,k.uniqueSort=k.unique=h.uniqueSort,k.text=h.getText,k.isXMLDoc=h.isXML,k.contains=h.contains,k.escapeSelector=h.escape;var T=function(e,t,n){var r=[],i=void 0!==n;while((e=e[t])&&9!==e.nodeType)if(1===e.nodeType){if(i&&k(e).is(n))break;r.push(e)}return r},S=function(e,t){for(var n=[];e;e=e.nextSibling)1===e.nodeType&&e!==t&&n.push(e);return n},N=k.expr.match.needsContext;function A(e,t){return e.nodeName&&e.nodeName.toLowerCase()===t.toLowerCase()}var D=/^<([a-z][^\/\0>:\x20\t\r\n\f]*)[\x20\t\r\n\f]*\/?>(?:<\/\1>|)$/i;function j(e,n,r){return m(n)?k.grep(e,function(e,t){return!!n.call(e,t,e)!==r}):n.nodeType?k.grep(e,function(e){return e===n!==r}):"string"!=typeof n?k.grep(e,function(e){return-1<i.call(n,e)!==r}):k.filter(n,e,r)}k.filter=function(e,t,n){var r=t[0];return n&&(e=":not("+e+")"),1===t.length&&1===r.nodeType?k.find.matchesSelector(r,e)?[r]:[]:k.find.matches(e,k.grep(t,function(e){return 1===e.nodeType}))},k.fn.extend({find:function(e){var t,n,r=this.length,i=this;if("string"!=typeof e)return this.pushStack(k(e).filter(function(){for(t=0;t<r;t++)if(k.contains(i[t],this))return!0}));for(n=this.pushStack([]),t=0;t<r;t++)k.find(e,i[t],n);return 1<r?k.uniqueSort(n):n},filter:function(e){return this.pushStack(j(this,e||[],!1))},not:function(e){return this.pushStack(j(this,e||[],!0))},is:function(e){return!!j(this,"string"==typeof e&&N.test(e)?k(e):e||[],!1).length}});var q,L=/^(?:\s*(<[\w\W]+>)[^>]*|#([\w-]+))$/;(k.fn.init=function(e,t,n){var r,i;if(!e)return this;if(n=n||q,"string"==typeof e){if(!(r="<"===e[0]&&">"===e[e.length-1]&&3<=e.length?[null,e,null]:L.exec(e))||!r[1]&&t)return!t||t.jquery?(t||n).find(e):this.constructor(t).find(e);if(r[1]){if(t=t instanceof k?t[0]:t,k.merge(this,k.parseHTML(r[1],t&&t.nodeType?t.ownerDocument||t:E,!0)),D.test(r[1])&&k.isPlainObject(t))for(r in t)m(this[r])?this[r](t[r]):this.attr(r,t[r]);return this}return(i=E.getElementById(r[2]))&&(this[0]=i,this.length=1),this}return e.nodeType?(this[0]=e,this.length=1,this):m(e)?void 0!==n.ready?n.ready(e):e(k):k.makeArray(e,this)}).prototype=k.fn,q=k(E);var H=/^(?:parents|prev(?:Until|All))/,O={children:!0,contents:!0,next:!0,prev:!0};function P(e,t){while((e=e[t])&&1!==e.nodeType);return e}k.fn.extend({has:function(e){var t=k(e,this),n=t.length;return this.filter(function(){for(var e=0;e<n;e++)if(k.contains(this,t[e]))return!0})},closest:function(e,t){var n,r=0,i=this.length,o=[],a="string"!=typeof e&&k(e);if(!N.test(e))for(;r<i;r++)for(n=this[r];n&&n!==t;n=n.parentNode)if(n.nodeType<11&&(a?-1<a.index(n):1===n.nodeType&&k.find.matchesSelector(n,e))){o.push(n);break}return this.pushStack(1<o.length?k.uniqueSort(o):o)},index:function(e){return e?"string"==typeof e?i.call(k(e),this[0]):i.call(this,e.jquery?e[0]:e):this[0]&&this[0].parentNode?this.first().prevAll().length:-1},add:function(e,t){return this.pushStack(k.uniqueSort(k.merge(this.get(),k(e,t))))},addBack:function(e){return this.add(null==e?this.prevObject:this.prevObject.filter(e))}}),k.each({parent:function(e){var t=e.parentNode;return t&&11!==t.nodeType?t:null},parents:function(e){return T(e,"parentNode")},parentsUntil:function(e,t,n){return T(e,"parentNode",n)},next:function(e){return P(e,"nextSibling")},prev:function(e){return P(e,"previousSibling")},nextAll:function(e){return T(e,"nextSibling")},prevAll:function(e){return T(e,"previousSibling")},nextUntil:function(e,t,n){return T(e,"nextSibling",n)},prevUntil:function(e,t,n){return T(e,"previousSibling",n)},siblings:function(e){return S((e.parentNode||{}).firstChild,e)},children:function(e){return S(e.firstChild)},contents:function(e){return"undefined"!=typeof e.contentDocument?e.contentDocument:(A(e,"template")&&(e=e.content||e),k.merge([],e.childNodes))}},function(r,i){k.fn[r]=function(e,t){var n=k.map(this,i,e);return"Until"!==r.slice(-5)&&(t=e),t&&"string"==typeof t&&(n=k.filter(t,n)),1<this.length&&(O[r]||k.uniqueSort(n),H.test(r)&&n.reverse()),this.pushStack(n)}});var R=/[^\x20\t\r\n\f]+/g;function M(e){return e}function I(e){throw e}function W(e,t,n,r){var i;try{e&&m(i=e.promise)?i.call(e).done(t).fail(n):e&&m(i=e.then)?i.call(e,t,n):t.apply(void 0,[e].slice(r))}catch(e){n.apply(void 0,[e])}}k.Callbacks=function(r){var e,n;r="string"==typeof r?(e=r,n={},k.each(e.match(R)||[],function(e,t){n[t]=!0}),n):k.extend({},r);var i,t,o,a,s=[],u=[],l=-1,c=function(){for(a=a||r.once,o=i=!0;u.length;l=-1){t=u.shift();while(++l<s.length)!1===s[l].apply(t[0],t[1])&&r.stopOnFalse&&(l=s.length,t=!1)}r.memory||(t=!1),i=!1,a&&(s=t?[]:"")},f={add:function(){return s&&(t&&!i&&(l=s.length-1,u.push(t)),function n(e){k.each(e,function(e,t){m(t)?r.unique&&f.has(t)||s.push(t):t&&t.length&&"string"!==w(t)&&n(t)})}(arguments),t&&!i&&c()),this},remove:function(){return k.each(arguments,function(e,t){var n;while(-1<(n=k.inArray(t,s,n)))s.splice(n,1),n<=l&&l--}),this},has:function(e){return e?-1<k.inArray(e,s):0<s.length},empty:function(){return s&&(s=[]),this},disable:function(){return a=u=[],s=t="",this},disabled:function(){return!s},lock:function(){return a=u=[],t||i||(s=t=""),this},locked:function(){return!!a},fireWith:function(e,t){return a||(t=[e,(t=t||[]).slice?t.slice():t],u.push(t),i||c()),this},fire:function(){return f.fireWith(this,arguments),this},fired:function(){return!!o}};return f},k.extend({Deferred:function(e){var o=[["notify","progress",k.Callbacks("memory"),k.Callbacks("memory"),2],["resolve","done",k.Callbacks("once memory"),k.Callbacks("once memory"),0,"resolved"],["reject","fail",k.Callbacks("once memory"),k.Callbacks("once memory"),1,"rejected"]],i="pending",a={state:function(){return i},always:function(){return s.done(arguments).fail(arguments),this},"catch":function(e){return a.then(null,e)},pipe:function(){var i=arguments;return k.Deferred(function(r){k.each(o,function(e,t){var n=m(i[t[4]])&&i[t[4]];s[t[1]](function(){var e=n&&n.apply(this,arguments);e&&m(e.promise)?e.promise().progress(r.notify).done(r.resolve).fail(r.reject):r[t[0]+"With"](this,n?[e]:arguments)})}),i=null}).promise()},then:function(t,n,r){var u=0;function l(i,o,a,s){return function(){var n=this,r=arguments,e=function(){var e,t;if(!(i<u)){if((e=a.apply(n,r))===o.promise())throw new TypeError("Thenable self-resolution");t=e&&("object"==typeof e||"function"==typeof e)&&e.then,m(t)?s?t.call(e,l(u,o,M,s),l(u,o,I,s)):(u++,t.call(e,l(u,o,M,s),l(u,o,I,s),l(u,o,M,o.notifyWith))):(a!==M&&(n=void 0,r=[e]),(s||o.resolveWith)(n,r))}},t=s?e:function(){try{e()}catch(e){k.Deferred.exceptionHook&&k.Deferred.exceptionHook(e,t.stackTrace),u<=i+1&&(a!==I&&(n=void 0,r=[e]),o.rejectWith(n,r))}};i?t():(k.Deferred.getStackHook&&(t.stackTrace=k.Deferred.getStackHook()),C.setTimeout(t))}}return k.Deferred(function(e){o[0][3].add(l(0,e,m(r)?r:M,e.notifyWith)),o[1][3].add(l(0,e,m(t)?t:M)),o[2][3].add(l(0,e,m(n)?n:I))}).promise()},promise:function(e){return null!=e?k.extend(e,a):a}},s={};return k.each(o,function(e,t){var n=t[2],r=t[5];a[t[1]]=n.add,r&&n.add(function(){i=r},o[3-e][2].disable,o[3-e][3].disable,o[0][2].lock,o[0][3].lock),n.add(t[3].fire),s[t[0]]=function(){return s[t[0]+"With"](this===s?void 0:this,arguments),this},s[t[0]+"With"]=n.fireWith}),a.promise(s),e&&e.call(s,s),s},when:function(e){var n=arguments.length,t=n,r=Array(t),i=s.call(arguments),o=k.Deferred(),a=function(t){return function(e){r[t]=this,i[t]=1<arguments.length?s.call(arguments):e,--n||o.resolveWith(r,i)}};if(n<=1&&(W(e,o.done(a(t)).resolve,o.reject,!n),"pending"===o.state()||m(i[t]&&i[t].then)))return o.then();while(t--)W(i[t],a(t),o.reject);return o.promise()}});var $=/^(Eval|Internal|Range|Reference|Syntax|Type|URI)Error$/;k.Deferred.exceptionHook=function(e,t){C.console&&C.console.warn&&e&&$.test(e.name)&&C.console.warn("jQuery.Deferred exception: "+e.message,e.stack,t)},k.readyException=function(e){C.setTimeout(function(){throw e})};var F=k.Deferred();function B(){E.removeEventListener("DOMContentLoaded",B),C.removeEventListener("load",B),k.ready()}k.fn.ready=function(e){return F.then(e)["catch"](function(e){k.readyException(e)}),this},k.extend({isReady:!1,readyWait:1,ready:function(e){(!0===e?--k.readyWait:k.isReady)||(k.isReady=!0)!==e&&0<--k.readyWait||F.resolveWith(E,[k])}}),k.ready.then=F.then,"complete"===E.readyState||"loading"!==E.readyState&&!E.documentElement.doScroll?C.setTimeout(k.ready):(E.addEventListener("DOMContentLoaded",B),C.addEventListener("load",B));var _=function(e,t,n,r,i,o,a){var s=0,u=e.length,l=null==n;if("object"===w(n))for(s in i=!0,n)_(e,t,s,n[s],!0,o,a);else if(void 0!==r&&(i=!0,m(r)||(a=!0),l&&(a?(t.call(e,r),t=null):(l=t,t=function(e,t,n){return l.call(k(e),n)})),t))for(;s<u;s++)t(e[s],n,a?r:r.call(e[s],s,t(e[s],n)));return i?e:l?t.call(e):u?t(e[0],n):o},z=/^-ms-/,U=/-([a-z])/g;function X(e,t){return t.toUpperCase()}function V(e){return e.replace(z,"ms-").replace(U,X)}var G=function(e){return 1===e.nodeType||9===e.nodeType||!+e.nodeType};function Y(){this.expando=k.expando+Y.uid++}Y.uid=1,Y.prototype={cache:function(e){var t=e[this.expando];return t||(t={},G(e)&&(e.nodeType?e[this.expando]=t:Object.defineProperty(e,this.expando,{value:t,configurable:!0}))),t},set:function(e,t,n){var r,i=this.cache(e);if("string"==typeof t)i[V(t)]=n;else for(r in t)i[V(r)]=t[r];return i},get:function(e,t){return void 0===t?this.cache(e):e[this.expando]&&e[this.expando][V(t)]},access:function(e,t,n){return void 0===t||t&&"string"==typeof t&&void 0===n?this.get(e,t):(this.set(e,t,n),void 0!==n?n:t)},remove:function(e,t){var n,r=e[this.expando];if(void 0!==r){if(void 0!==t){n=(t=Array.isArray(t)?t.map(V):(t=V(t))in r?[t]:t.match(R)||[]).length;while(n--)delete r[t[n]]}(void 0===t||k.isEmptyObject(r))&&(e.nodeType?e[this.expando]=void 0:delete e[this.expando])}},hasData:function(e){var t=e[this.expando];return void 0!==t&&!k.isEmptyObject(t)}};var Q=new Y,J=new Y,K=/^(?:\{[\w\W]*\}|\[[\w\W]*\])$/,Z=/[A-Z]/g;function ee(e,t,n){var r,i;if(void 0===n&&1===e.nodeType)if(r="data-"+t.replace(Z,"-$&").toLowerCase(),"string"==typeof(n=e.getAttribute(r))){try{n="true"===(i=n)||"false"!==i&&("null"===i?null:i===+i+""?+i:K.test(i)?JSON.parse(i):i)}catch(e){}J.set(e,t,n)}else n=void 0;return n}k.extend({hasData:function(e){return J.hasData(e)||Q.hasData(e)},data:function(e,t,n){return J.access(e,t,n)},removeData:function(e,t){J.remove(e,t)},_data:function(e,t,n){return Q.access(e,t,n)},_removeData:function(e,t){Q.remove(e,t)}}),k.fn.extend({data:function(n,e){var t,r,i,o=this[0],a=o&&o.attributes;if(void 0===n){if(this.length&&(i=J.get(o),1===o.nodeType&&!Q.get(o,"hasDataAttrs"))){t=a.length;while(t--)a[t]&&0===(r=a[t].name).indexOf("data-")&&(r=V(r.slice(5)),ee(o,r,i[r]));Q.set(o,"hasDataAttrs",!0)}return i}return"object"==typeof n?this.each(function(){J.set(this,n)}):_(this,function(e){var t;if(o&&void 0===e)return void 0!==(t=J.get(o,n))?t:void 0!==(t=ee(o,n))?t:void 0;this.each(function(){J.set(this,n,e)})},null,e,1<arguments.length,null,!0)},removeData:function(e){return this.each(function(){J.remove(this,e)})}}),k.extend({queue:function(e,t,n){var r;if(e)return t=(t||"fx")+"queue",r=Q.get(e,t),n&&(!r||Array.isArray(n)?r=Q.access(e,t,k.makeArray(n)):r.push(n)),r||[]},dequeue:function(e,t){t=t||"fx";var n=k.queue(e,t),r=n.length,i=n.shift(),o=k._queueHooks(e,t);"inprogress"===i&&(i=n.shift(),r--),i&&("fx"===t&&n.unshift("inprogress"),delete o.stop,i.call(e,function(){k.dequeue(e,t)},o)),!r&&o&&o.empty.fire()},_queueHooks:function(e,t){var n=t+"queueHooks";return Q.get(e,n)||Q.access(e,n,{empty:k.Callbacks("once memory").add(function(){Q.remove(e,[t+"queue",n])})})}}),k.fn.extend({queue:function(t,n){var e=2;return"string"!=typeof t&&(n=t,t="fx",e--),arguments.length<e?k.queue(this[0],t):void 0===n?this:this.each(function(){var e=k.queue(this,t,n);k._queueHooks(this,t),"fx"===t&&"inprogress"!==e[0]&&k.dequeue(this,t)})},dequeue:function(e){return this.each(function(){k.dequeue(this,e)})},clearQueue:function(e){return this.queue(e||"fx",[])},promise:function(e,t){var n,r=1,i=k.Deferred(),o=this,a=this.length,s=function(){--r||i.resolveWith(o,[o])};"string"!=typeof e&&(t=e,e=void 0),e=e||"fx";while(a--)(n=Q.get(o[a],e+"queueHooks"))&&n.empty&&(r++,n.empty.add(s));return s(),i.promise(t)}});var te=/[+-]?(?:\d*\.|)\d+(?:[eE][+-]?\d+|)/.source,ne=new RegExp("^(?:([+-])=|)("+te+")([a-z%]*)$","i"),re=["Top","Right","Bottom","Left"],ie=E.documentElement,oe=function(e){return k.contains(e.ownerDocument,e)},ae={composed:!0};ie.getRootNode&&(oe=function(e){return k.contains(e.ownerDocument,e)||e.getRootNode(ae)===e.ownerDocument});var se=function(e,t){return"none"===(e=t||e).style.display||""===e.style.display&&oe(e)&&"none"===k.css(e,"display")},ue=function(e,t,n,r){var i,o,a={};for(o in t)a[o]=e.style[o],e.style[o]=t[o];for(o in i=n.apply(e,r||[]),t)e.style[o]=a[o];return i};function le(e,t,n,r){var i,o,a=20,s=r?function(){return r.cur()}:function(){return k.css(e,t,"")},u=s(),l=n&&n[3]||(k.cssNumber[t]?"":"px"),c=e.nodeType&&(k.cssNumber[t]||"px"!==l&&+u)&&ne.exec(k.css(e,t));if(c&&c[3]!==l){u/=2,l=l||c[3],c=+u||1;while(a--)k.style(e,t,c+l),(1-o)*(1-(o=s()/u||.5))<=0&&(a=0),c/=o;c*=2,k.style(e,t,c+l),n=n||[]}return n&&(c=+c||+u||0,i=n[1]?c+(n[1]+1)*n[2]:+n[2],r&&(r.unit=l,r.start=c,r.end=i)),i}var ce={};function fe(e,t){for(var n,r,i,o,a,s,u,l=[],c=0,f=e.length;c<f;c++)(r=e[c]).style&&(n=r.style.display,t?("none"===n&&(l[c]=Q.get(r,"display")||null,l[c]||(r.style.display="")),""===r.style.display&&se(r)&&(l[c]=(u=a=o=void 0,a=(i=r).ownerDocument,s=i.nodeName,(u=ce[s])||(o=a.body.appendChild(a.createElement(s)),u=k.css(o,"display"),o.parentNode.removeChild(o),"none"===u&&(u="block"),ce[s]=u)))):"none"!==n&&(l[c]="none",Q.set(r,"display",n)));for(c=0;c<f;c++)null!=l[c]&&(e[c].style.display=l[c]);return e}k.fn.extend({show:function(){return fe(this,!0)},hide:function(){return fe(this)},toggle:function(e){return"boolean"==typeof e?e?this.show():this.hide():this.each(function(){se(this)?k(this).show():k(this).hide()})}});var pe=/^(?:checkbox|radio)$/i,de=/<([a-z][^\/\0>\x20\t\r\n\f]*)/i,he=/^$|^module$|\/(?:java|ecma)script/i,ge={option:[1,"<select multiple='multiple'>","</select>"],thead:[1,"<table>","</table>"],col:[2,"<table><colgroup>","</colgroup></table>"],tr:[2,"<table><tbody>","</tbody></table>"],td:[3,"<table><tbody><tr>","</tr></tbody></table>"],_default:[0,"",""]};function ve(e,t){var n;return n="undefined"!=typeof e.getElementsByTagName?e.getElementsByTagName(t||"*"):"undefined"!=typeof e.querySelectorAll?e.querySelectorAll(t||"*"):[],void 0===t||t&&A(e,t)?k.merge([e],n):n}function ye(e,t){for(var n=0,r=e.length;n<r;n++)Q.set(e[n],"globalEval",!t||Q.get(t[n],"globalEval"))}ge.optgroup=ge.option,ge.tbody=ge.tfoot=ge.colgroup=ge.caption=ge.thead,ge.th=ge.td;var me,xe,be=/<|&#?\w+;/;function we(e,t,n,r,i){for(var o,a,s,u,l,c,f=t.createDocumentFragment(),p=[],d=0,h=e.length;d<h;d++)if((o=e[d])||0===o)if("object"===w(o))k.merge(p,o.nodeType?[o]:o);else if(be.test(o)){a=a||f.appendChild(t.createElement("div")),s=(de.exec(o)||["",""])[1].toLowerCase(),u=ge[s]||ge._default,a.innerHTML=u[1]+k.htmlPrefilter(o)+u[2],c=u[0];while(c--)a=a.lastChild;k.merge(p,a.childNodes),(a=f.firstChild).textContent=""}else p.push(t.createTextNode(o));f.textContent="",d=0;while(o=p[d++])if(r&&-1<k.inArray(o,r))i&&i.push(o);else if(l=oe(o),a=ve(f.appendChild(o),"script"),l&&ye(a),n){c=0;while(o=a[c++])he.test(o.type||"")&&n.push(o)}return f}me=E.createDocumentFragment().appendChild(E.createElement("div")),(xe=E.createElement("input")).setAttribute("type","radio"),xe.setAttribute("checked","checked"),xe.setAttribute("name","t"),me.appendChild(xe),y.checkClone=me.cloneNode(!0).cloneNode(!0).lastChild.checked,me.innerHTML="<textarea>x</textarea>",y.noCloneChecked=!!me.cloneNode(!0).lastChild.defaultValue;var Te=/^key/,Ce=/^(?:mouse|pointer|contextmenu|drag|drop)|click/,Ee=/^([^.]*)(?:\.(.+)|)/;function ke(){return!0}function Se(){return!1}function Ne(e,t){return e===function(){try{return E.activeElement}catch(e){}}()==("focus"===t)}function Ae(e,t,n,r,i,o){var a,s;if("object"==typeof t){for(s in"string"!=typeof n&&(r=r||n,n=void 0),t)Ae(e,s,n,r,t[s],o);return e}if(null==r&&null==i?(i=n,r=n=void 0):null==i&&("string"==typeof n?(i=r,r=void 0):(i=r,r=n,n=void 0)),!1===i)i=Se;else if(!i)return e;return 1===o&&(a=i,(i=function(e){return k().off(e),a.apply(this,arguments)}).guid=a.guid||(a.guid=k.guid++)),e.each(function(){k.event.add(this,t,i,r,n)})}function De(e,i,o){o?(Q.set(e,i,!1),k.event.add(e,i,{namespace:!1,handler:function(e){var t,n,r=Q.get(this,i);if(1&e.isTrigger&&this[i]){if(r.length)(k.event.special[i]||{}).delegateType&&e.stopPropagation();else if(r=s.call(arguments),Q.set(this,i,r),t=o(this,i),this[i](),r!==(n=Q.get(this,i))||t?Q.set(this,i,!1):n={},r!==n)return e.stopImmediatePropagation(),e.preventDefault(),n.value}else r.length&&(Q.set(this,i,{value:k.event.trigger(k.extend(r[0],k.Event.prototype),r.slice(1),this)}),e.stopImmediatePropagation())}})):void 0===Q.get(e,i)&&k.event.add(e,i,ke)}k.event={global:{},add:function(t,e,n,r,i){var o,a,s,u,l,c,f,p,d,h,g,v=Q.get(t);if(v){n.handler&&(n=(o=n).handler,i=o.selector),i&&k.find.matchesSelector(ie,i),n.guid||(n.guid=k.guid++),(u=v.events)||(u=v.events={}),(a=v.handle)||(a=v.handle=function(e){return"undefined"!=typeof k&&k.event.triggered!==e.type?k.event.dispatch.apply(t,arguments):void 0}),l=(e=(e||"").match(R)||[""]).length;while(l--)d=g=(s=Ee.exec(e[l])||[])[1],h=(s[2]||"").split(".").sort(),d&&(f=k.event.special[d]||{},d=(i?f.delegateType:f.bindType)||d,f=k.event.special[d]||{},c=k.extend({type:d,origType:g,data:r,handler:n,guid:n.guid,selector:i,needsContext:i&&k.expr.match.needsContext.test(i),namespace:h.join(".")},o),(p=u[d])||((p=u[d]=[]).delegateCount=0,f.setup&&!1!==f.setup.call(t,r,h,a)||t.addEventListener&&t.addEventListener(d,a)),f.add&&(f.add.call(t,c),c.handler.guid||(c.handler.guid=n.guid)),i?p.splice(p.delegateCount++,0,c):p.push(c),k.event.global[d]=!0)}},remove:function(e,t,n,r,i){var o,a,s,u,l,c,f,p,d,h,g,v=Q.hasData(e)&&Q.get(e);if(v&&(u=v.events)){l=(t=(t||"").match(R)||[""]).length;while(l--)if(d=g=(s=Ee.exec(t[l])||[])[1],h=(s[2]||"").split(".").sort(),d){f=k.event.special[d]||{},p=u[d=(r?f.delegateType:f.bindType)||d]||[],s=s[2]&&new RegExp("(^|\\.)"+h.join("\\.(?:.*\\.|)")+"(\\.|$)"),a=o=p.length;while(o--)c=p[o],!i&&g!==c.origType||n&&n.guid!==c.guid||s&&!s.test(c.namespace)||r&&r!==c.selector&&("**"!==r||!c.selector)||(p.splice(o,1),c.selector&&p.delegateCount--,f.remove&&f.remove.call(e,c));a&&!p.length&&(f.teardown&&!1!==f.teardown.call(e,h,v.handle)||k.removeEvent(e,d,v.handle),delete u[d])}else for(d in u)k.event.remove(e,d+t[l],n,r,!0);k.isEmptyObject(u)&&Q.remove(e,"handle events")}},dispatch:function(e){var t,n,r,i,o,a,s=k.event.fix(e),u=new Array(arguments.length),l=(Q.get(this,"events")||{})[s.type]||[],c=k.event.special[s.type]||{};for(u[0]=s,t=1;t<arguments.length;t++)u[t]=arguments[t];if(s.delegateTarget=this,!c.preDispatch||!1!==c.preDispatch.call(this,s)){a=k.event.handlers.call(this,s,l),t=0;while((i=a[t++])&&!s.isPropagationStopped()){s.currentTarget=i.elem,n=0;while((o=i.handlers[n++])&&!s.isImmediatePropagationStopped())s.rnamespace&&!1!==o.namespace&&!s.rnamespace.test(o.namespace)||(s.handleObj=o,s.data=o.data,void 0!==(r=((k.event.special[o.origType]||{}).handle||o.handler).apply(i.elem,u))&&!1===(s.result=r)&&(s.preventDefault(),s.stopPropagation()))}return c.postDispatch&&c.postDispatch.call(this,s),s.result}},handlers:function(e,t){var n,r,i,o,a,s=[],u=t.delegateCount,l=e.target;if(u&&l.nodeType&&!("click"===e.type&&1<=e.button))for(;l!==this;l=l.parentNode||this)if(1===l.nodeType&&("click"!==e.type||!0!==l.disabled)){for(o=[],a={},n=0;n<u;n++)void 0===a[i=(r=t[n]).selector+" "]&&(a[i]=r.needsContext?-1<k(i,this).index(l):k.find(i,this,null,[l]).length),a[i]&&o.push(r);o.length&&s.push({elem:l,handlers:o})}return l=this,u<t.length&&s.push({elem:l,handlers:t.slice(u)}),s},addProp:function(t,e){Object.defineProperty(k.Event.prototype,t,{enumerable:!0,configurable:!0,get:m(e)?function(){if(this.originalEvent)return e(this.originalEvent)}:function(){if(this.originalEvent)return this.originalEvent[t]},set:function(e){Object.defineProperty(this,t,{enumerable:!0,configurable:!0,writable:!0,value:e})}})},fix:function(e){return e[k.expando]?e:new k.Event(e)},special:{load:{noBubble:!0},click:{setup:function(e){var t=this||e;return pe.test(t.type)&&t.click&&A(t,"input")&&De(t,"click",ke),!1},trigger:function(e){var t=this||e;return pe.test(t.type)&&t.click&&A(t,"input")&&De(t,"click"),!0},_default:function(e){var t=e.target;return pe.test(t.type)&&t.click&&A(t,"input")&&Q.get(t,"click")||A(t,"a")}},beforeunload:{postDispatch:function(e){void 0!==e.result&&e.originalEvent&&(e.originalEvent.returnValue=e.result)}}}},k.removeEvent=function(e,t,n){e.removeEventListener&&e.removeEventListener(t,n)},k.Event=function(e,t){if(!(this instanceof k.Event))return new k.Event(e,t);e&&e.type?(this.originalEvent=e,this.type=e.type,this.isDefaultPrevented=e.defaultPrevented||void 0===e.defaultPrevented&&!1===e.returnValue?ke:Se,this.target=e.target&&3===e.target.nodeType?e.target.parentNode:e.target,this.currentTarget=e.currentTarget,this.relatedTarget=e.relatedTarget):this.type=e,t&&k.extend(this,t),this.timeStamp=e&&e.timeStamp||Date.now(),this[k.expando]=!0},k.Event.prototype={constructor:k.Event,isDefaultPrevented:Se,isPropagationStopped:Se,isImmediatePropagationStopped:Se,isSimulated:!1,preventDefault:function(){var e=this.originalEvent;this.isDefaultPrevented=ke,e&&!this.isSimulated&&e.preventDefault()},stopPropagation:function(){var e=this.originalEvent;this.isPropagationStopped=ke,e&&!this.isSimulated&&e.stopPropagation()},stopImmediatePropagation:function(){var e=this.originalEvent;this.isImmediatePropagationStopped=ke,e&&!this.isSimulated&&e.stopImmediatePropagation(),this.stopPropagation()}},k.each({altKey:!0,bubbles:!0,cancelable:!0,changedTouches:!0,ctrlKey:!0,detail:!0,eventPhase:!0,metaKey:!0,pageX:!0,pageY:!0,shiftKey:!0,view:!0,"char":!0,code:!0,charCode:!0,key:!0,keyCode:!0,button:!0,buttons:!0,clientX:!0,clientY:!0,offsetX:!0,offsetY:!0,pointerId:!0,pointerType:!0,screenX:!0,screenY:!0,targetTouches:!0,toElement:!0,touches:!0,which:function(e){var t=e.button;return null==e.which&&Te.test(e.type)?null!=e.charCode?e.charCode:e.keyCode:!e.which&&void 0!==t&&Ce.test(e.type)?1&t?1:2&t?3:4&t?2:0:e.which}},k.event.addProp),k.each({focus:"focusin",blur:"focusout"},function(e,t){k.event.special[e]={setup:function(){return De(this,e,Ne),!1},trigger:function(){return De(this,e),!0},delegateType:t}}),k.each({mouseenter:"mouseover",mouseleave:"mouseout",pointerenter:"pointerover",pointerleave:"pointerout"},function(e,i){k.event.special[e]={delegateType:i,bindType:i,handle:function(e){var t,n=e.relatedTarget,r=e.handleObj;return n&&(n===this||k.contains(this,n))||(e.type=r.origType,t=r.handler.apply(this,arguments),e.type=i),t}}}),k.fn.extend({on:function(e,t,n,r){return Ae(this,e,t,n,r)},one:function(e,t,n,r){return Ae(this,e,t,n,r,1)},off:function(e,t,n){var r,i;if(e&&e.preventDefault&&e.handleObj)return r=e.handleObj,k(e.delegateTarget).off(r.namespace?r.origType+"."+r.namespace:r.origType,r.selector,r.handler),this;if("object"==typeof e){for(i in e)this.off(i,t,e[i]);return this}return!1!==t&&"function"!=typeof t||(n=t,t=void 0),!1===n&&(n=Se),this.each(function(){k.event.remove(this,e,n,t)})}});var je=/<(?!area|br|col|embed|hr|img|input|link|meta|param)(([a-z][^\/\0>\x20\t\r\n\f]*)[^>]*)\/>/gi,qe=/<script|<style|<link/i,Le=/checked\s*(?:[^=]|=\s*.checked.)/i,He=/^\s*<!(?:\[CDATA\[|--)|(?:\]\]|--)>\s*$/g;function Oe(e,t){return A(e,"table")&&A(11!==t.nodeType?t:t.firstChild,"tr")&&k(e).children("tbody")[0]||e}function Pe(e){return e.type=(null!==e.getAttribute("type"))+"/"+e.type,e}function Re(e){return"true/"===(e.type||"").slice(0,5)?e.type=e.type.slice(5):e.removeAttribute("type"),e}function Me(e,t){var n,r,i,o,a,s,u,l;if(1===t.nodeType){if(Q.hasData(e)&&(o=Q.access(e),a=Q.set(t,o),l=o.events))for(i in delete a.handle,a.events={},l)for(n=0,r=l[i].length;n<r;n++)k.event.add(t,i,l[i][n]);J.hasData(e)&&(s=J.access(e),u=k.extend({},s),J.set(t,u))}}function Ie(n,r,i,o){r=g.apply([],r);var e,t,a,s,u,l,c=0,f=n.length,p=f-1,d=r[0],h=m(d);if(h||1<f&&"string"==typeof d&&!y.checkClone&&Le.test(d))return n.each(function(e){var t=n.eq(e);h&&(r[0]=d.call(this,e,t.html())),Ie(t,r,i,o)});if(f&&(t=(e=we(r,n[0].ownerDocument,!1,n,o)).firstChild,1===e.childNodes.length&&(e=t),t||o)){for(s=(a=k.map(ve(e,"script"),Pe)).length;c<f;c++)u=e,c!==p&&(u=k.clone(u,!0,!0),s&&k.merge(a,ve(u,"script"))),i.call(n[c],u,c);if(s)for(l=a[a.length-1].ownerDocument,k.map(a,Re),c=0;c<s;c++)u=a[c],he.test(u.type||"")&&!Q.access(u,"globalEval")&&k.contains(l,u)&&(u.src&&"module"!==(u.type||"").toLowerCase()?k._evalUrl&&!u.noModule&&k._evalUrl(u.src,{nonce:u.nonce||u.getAttribute("nonce")}):b(u.textContent.replace(He,""),u,l))}return n}function We(e,t,n){for(var r,i=t?k.filter(t,e):e,o=0;null!=(r=i[o]);o++)n||1!==r.nodeType||k.cleanData(ve(r)),r.parentNode&&(n&&oe(r)&&ye(ve(r,"script")),r.parentNode.removeChild(r));return e}k.extend({htmlPrefilter:function(e){return e.replace(je,"<$1></$2>")},clone:function(e,t,n){var r,i,o,a,s,u,l,c=e.cloneNode(!0),f=oe(e);if(!(y.noCloneChecked||1!==e.nodeType&&11!==e.nodeType||k.isXMLDoc(e)))for(a=ve(c),r=0,i=(o=ve(e)).length;r<i;r++)s=o[r],u=a[r],void 0,"input"===(l=u.nodeName.toLowerCase())&&pe.test(s.type)?u.checked=s.checked:"input"!==l&&"textarea"!==l||(u.defaultValue=s.defaultValue);if(t)if(n)for(o=o||ve(e),a=a||ve(c),r=0,i=o.length;r<i;r++)Me(o[r],a[r]);else Me(e,c);return 0<(a=ve(c,"script")).length&&ye(a,!f&&ve(e,"script")),c},cleanData:function(e){for(var t,n,r,i=k.event.special,o=0;void 0!==(n=e[o]);o++)if(G(n)){if(t=n[Q.expando]){if(t.events)for(r in t.events)i[r]?k.event.remove(n,r):k.removeEvent(n,r,t.handle);n[Q.expando]=void 0}n[J.expando]&&(n[J.expando]=void 0)}}}),k.fn.extend({detach:function(e){return We(this,e,!0)},remove:function(e){return We(this,e)},text:function(e){return _(this,function(e){return void 0===e?k.text(this):this.empty().each(function(){1!==this.nodeType&&11!==this.nodeType&&9!==this.nodeType||(this.textContent=e)})},null,e,arguments.length)},append:function(){return Ie(this,arguments,function(e){1!==this.nodeType&&11!==this.nodeType&&9!==this.nodeType||Oe(this,e).appendChild(e)})},prepend:function(){return Ie(this,arguments,function(e){if(1===this.nodeType||11===this.nodeType||9===this.nodeType){var t=Oe(this,e);t.insertBefore(e,t.firstChild)}})},before:function(){return Ie(this,arguments,function(e){this.parentNode&&this.parentNode.insertBefore(e,this)})},after:function(){return Ie(this,arguments,function(e){this.parentNode&&this.parentNode.insertBefore(e,this.nextSibling)})},empty:function(){for(var e,t=0;null!=(e=this[t]);t++)1===e.nodeType&&(k.cleanData(ve(e,!1)),e.textContent="");return this},clone:function(e,t){return e=null!=e&&e,t=null==t?e:t,this.map(function(){return k.clone(this,e,t)})},html:function(e){return _(this,function(e){var t=this[0]||{},n=0,r=this.length;if(void 0===e&&1===t.nodeType)return t.innerHTML;if("string"==typeof e&&!qe.test(e)&&!ge[(de.exec(e)||["",""])[1].toLowerCase()]){e=k.htmlPrefilter(e);try{for(;n<r;n++)1===(t=this[n]||{}).nodeType&&(k.cleanData(ve(t,!1)),t.innerHTML=e);t=0}catch(e){}}t&&this.empty().append(e)},null,e,arguments.length)},replaceWith:function(){var n=[];return Ie(this,arguments,function(e){var t=this.parentNode;k.inArray(this,n)<0&&(k.cleanData(ve(this)),t&&t.replaceChild(e,this))},n)}}),k.each({appendTo:"append",prependTo:"prepend",insertBefore:"before",insertAfter:"after",replaceAll:"replaceWith"},function(e,a){k.fn[e]=function(e){for(var t,n=[],r=k(e),i=r.length-1,o=0;o<=i;o++)t=o===i?this:this.clone(!0),k(r[o])[a](t),u.apply(n,t.get());return this.pushStack(n)}});var $e=new RegExp("^("+te+")(?!px)[a-z%]+$","i"),Fe=function(e){var t=e.ownerDocument.defaultView;return t&&t.opener||(t=C),t.getComputedStyle(e)},Be=new RegExp(re.join("|"),"i");function _e(e,t,n){var r,i,o,a,s=e.style;return(n=n||Fe(e))&&(""!==(a=n.getPropertyValue(t)||n[t])||oe(e)||(a=k.style(e,t)),!y.pixelBoxStyles()&&$e.test(a)&&Be.test(t)&&(r=s.width,i=s.minWidth,o=s.maxWidth,s.minWidth=s.maxWidth=s.width=a,a=n.width,s.width=r,s.minWidth=i,s.maxWidth=o)),void 0!==a?a+"":a}function ze(e,t){return{get:function(){if(!e())return(this.get=t).apply(this,arguments);delete this.get}}}!function(){function e(){if(u){s.style.cssText="position:absolute;left:-11111px;width:60px;margin-top:1px;padding:0;border:0",u.style.cssText="position:relative;display:block;box-sizing:border-box;overflow:scroll;margin:auto;border:1px;padding:1px;width:60%;top:1%",ie.appendChild(s).appendChild(u);var e=C.getComputedStyle(u);n="1%"!==e.top,a=12===t(e.marginLeft),u.style.right="60%",o=36===t(e.right),r=36===t(e.width),u.style.position="absolute",i=12===t(u.offsetWidth/3),ie.removeChild(s),u=null}}function t(e){return Math.round(parseFloat(e))}var n,r,i,o,a,s=E.createElement("div"),u=E.createElement("div");u.style&&(u.style.backgroundClip="content-box",u.cloneNode(!0).style.backgroundClip="",y.clearCloneStyle="content-box"===u.style.backgroundClip,k.extend(y,{boxSizingReliable:function(){return e(),r},pixelBoxStyles:function(){return e(),o},pixelPosition:function(){return e(),n},reliableMarginLeft:function(){return e(),a},scrollboxSize:function(){return e(),i}}))}();var Ue=["Webkit","Moz","ms"],Xe=E.createElement("div").style,Ve={};function Ge(e){var t=k.cssProps[e]||Ve[e];return t||(e in Xe?e:Ve[e]=function(e){var t=e[0].toUpperCase()+e.slice(1),n=Ue.length;while(n--)if((e=Ue[n]+t)in Xe)return e}(e)||e)}var Ye=/^(none|table(?!-c[ea]).+)/,Qe=/^--/,Je={position:"absolute",visibility:"hidden",display:"block"},Ke={letterSpacing:"0",fontWeight:"400"};function Ze(e,t,n){var r=ne.exec(t);return r?Math.max(0,r[2]-(n||0))+(r[3]||"px"):t}function et(e,t,n,r,i,o){var a="width"===t?1:0,s=0,u=0;if(n===(r?"border":"content"))return 0;for(;a<4;a+=2)"margin"===n&&(u+=k.css(e,n+re[a],!0,i)),r?("content"===n&&(u-=k.css(e,"padding"+re[a],!0,i)),"margin"!==n&&(u-=k.css(e,"border"+re[a]+"Width",!0,i))):(u+=k.css(e,"padding"+re[a],!0,i),"padding"!==n?u+=k.css(e,"border"+re[a]+"Width",!0,i):s+=k.css(e,"border"+re[a]+"Width",!0,i));return!r&&0<=o&&(u+=Math.max(0,Math.ceil(e["offset"+t[0].toUpperCase()+t.slice(1)]-o-u-s-.5))||0),u}function tt(e,t,n){var r=Fe(e),i=(!y.boxSizingReliable()||n)&&"border-box"===k.css(e,"boxSizing",!1,r),o=i,a=_e(e,t,r),s="offset"+t[0].toUpperCase()+t.slice(1);if($e.test(a)){if(!n)return a;a="auto"}return(!y.boxSizingReliable()&&i||"auto"===a||!parseFloat(a)&&"inline"===k.css(e,"display",!1,r))&&e.getClientRects().length&&(i="border-box"===k.css(e,"boxSizing",!1,r),(o=s in e)&&(a=e[s])),(a=parseFloat(a)||0)+et(e,t,n||(i?"border":"content"),o,r,a)+"px"}function nt(e,t,n,r,i){return new nt.prototype.init(e,t,n,r,i)}k.extend({cssHooks:{opacity:{get:function(e,t){if(t){var n=_e(e,"opacity");return""===n?"1":n}}}},cssNumber:{animationIterationCount:!0,columnCount:!0,fillOpacity:!0,flexGrow:!0,flexShrink:!0,fontWeight:!0,gridArea:!0,gridColumn:!0,gridColumnEnd:!0,gridColumnStart:!0,gridRow:!0,gridRowEnd:!0,gridRowStart:!0,lineHeight:!0,opacity:!0,order:!0,orphans:!0,widows:!0,zIndex:!0,zoom:!0},cssProps:{},style:function(e,t,n,r){if(e&&3!==e.nodeType&&8!==e.nodeType&&e.style){var i,o,a,s=V(t),u=Qe.test(t),l=e.style;if(u||(t=Ge(s)),a=k.cssHooks[t]||k.cssHooks[s],void 0===n)return a&&"get"in a&&void 0!==(i=a.get(e,!1,r))?i:l[t];"string"===(o=typeof n)&&(i=ne.exec(n))&&i[1]&&(n=le(e,t,i),o="number"),null!=n&&n==n&&("number"!==o||u||(n+=i&&i[3]||(k.cssNumber[s]?"":"px")),y.clearCloneStyle||""!==n||0!==t.indexOf("background")||(l[t]="inherit"),a&&"set"in a&&void 0===(n=a.set(e,n,r))||(u?l.setProperty(t,n):l[t]=n))}},css:function(e,t,n,r){var i,o,a,s=V(t);return Qe.test(t)||(t=Ge(s)),(a=k.cssHooks[t]||k.cssHooks[s])&&"get"in a&&(i=a.get(e,!0,n)),void 0===i&&(i=_e(e,t,r)),"normal"===i&&t in Ke&&(i=Ke[t]),""===n||n?(o=parseFloat(i),!0===n||isFinite(o)?o||0:i):i}}),k.each(["height","width"],function(e,u){k.cssHooks[u]={get:function(e,t,n){if(t)return!Ye.test(k.css(e,"display"))||e.getClientRects().length&&e.getBoundingClientRect().width?tt(e,u,n):ue(e,Je,function(){return tt(e,u,n)})},set:function(e,t,n){var r,i=Fe(e),o=!y.scrollboxSize()&&"absolute"===i.position,a=(o||n)&&"border-box"===k.css(e,"boxSizing",!1,i),s=n?et(e,u,n,a,i):0;return a&&o&&(s-=Math.ceil(e["offset"+u[0].toUpperCase()+u.slice(1)]-parseFloat(i[u])-et(e,u,"border",!1,i)-.5)),s&&(r=ne.exec(t))&&"px"!==(r[3]||"px")&&(e.style[u]=t,t=k.css(e,u)),Ze(0,t,s)}}}),k.cssHooks.marginLeft=ze(y.reliableMarginLeft,function(e,t){if(t)return(parseFloat(_e(e,"marginLeft"))||e.getBoundingClientRect().left-ue(e,{marginLeft:0},function(){return e.getBoundingClientRect().left}))+"px"}),k.each({margin:"",padding:"",border:"Width"},function(i,o){k.cssHooks[i+o]={expand:function(e){for(var t=0,n={},r="string"==typeof e?e.split(" "):[e];t<4;t++)n[i+re[t]+o]=r[t]||r[t-2]||r[0];return n}},"margin"!==i&&(k.cssHooks[i+o].set=Ze)}),k.fn.extend({css:function(e,t){return _(this,function(e,t,n){var r,i,o={},a=0;if(Array.isArray(t)){for(r=Fe(e),i=t.length;a<i;a++)o[t[a]]=k.css(e,t[a],!1,r);return o}return void 0!==n?k.style(e,t,n):k.css(e,t)},e,t,1<arguments.length)}}),((k.Tween=nt).prototype={constructor:nt,init:function(e,t,n,r,i,o){this.elem=e,this.prop=n,this.easing=i||k.easing._default,this.options=t,this.start=this.now=this.cur(),this.end=r,this.unit=o||(k.cssNumber[n]?"":"px")},cur:function(){var e=nt.propHooks[this.prop];return e&&e.get?e.get(this):nt.propHooks._default.get(this)},run:function(e){var t,n=nt.propHooks[this.prop];return this.options.duration?this.pos=t=k.easing[this.easing](e,this.options.duration*e,0,1,this.options.duration):this.pos=t=e,this.now=(this.end-this.start)*t+this.start,this.options.step&&this.options.step.call(this.elem,this.now,this),n&&n.set?n.set(this):nt.propHooks._default.set(this),this}}).init.prototype=nt.prototype,(nt.propHooks={_default:{get:function(e){var t;return 1!==e.elem.nodeType||null!=e.elem[e.prop]&&null==e.elem.style[e.prop]?e.elem[e.prop]:(t=k.css(e.elem,e.prop,""))&&"auto"!==t?t:0},set:function(e){k.fx.step[e.prop]?k.fx.step[e.prop](e):1!==e.elem.nodeType||!k.cssHooks[e.prop]&&null==e.elem.style[Ge(e.prop)]?e.elem[e.prop]=e.now:k.style(e.elem,e.prop,e.now+e.unit)}}}).scrollTop=nt.propHooks.scrollLeft={set:function(e){e.elem.nodeType&&e.elem.parentNode&&(e.elem[e.prop]=e.now)}},k.easing={linear:function(e){return e},swing:function(e){return.5-Math.cos(e*Math.PI)/2},_default:"swing"},k.fx=nt.prototype.init,k.fx.step={};var rt,it,ot,at,st=/^(?:toggle|show|hide)$/,ut=/queueHooks$/;function lt(){it&&(!1===E.hidden&&C.requestAnimationFrame?C.requestAnimationFrame(lt):C.setTimeout(lt,k.fx.interval),k.fx.tick())}function ct(){return C.setTimeout(function(){rt=void 0}),rt=Date.now()}function ft(e,t){var n,r=0,i={height:e};for(t=t?1:0;r<4;r+=2-t)i["margin"+(n=re[r])]=i["padding"+n]=e;return t&&(i.opacity=i.width=e),i}function pt(e,t,n){for(var r,i=(dt.tweeners[t]||[]).concat(dt.tweeners["*"]),o=0,a=i.length;o<a;o++)if(r=i[o].call(n,t,e))return r}function dt(o,e,t){var n,a,r=0,i=dt.prefilters.length,s=k.Deferred().always(function(){delete u.elem}),u=function(){if(a)return!1;for(var e=rt||ct(),t=Math.max(0,l.startTime+l.duration-e),n=1-(t/l.duration||0),r=0,i=l.tweens.length;r<i;r++)l.tweens[r].run(n);return s.notifyWith(o,[l,n,t]),n<1&&i?t:(i||s.notifyWith(o,[l,1,0]),s.resolveWith(o,[l]),!1)},l=s.promise({elem:o,props:k.extend({},e),opts:k.extend(!0,{specialEasing:{},easing:k.easing._default},t),originalProperties:e,originalOptions:t,startTime:rt||ct(),duration:t.duration,tweens:[],createTween:function(e,t){var n=k.Tween(o,l.opts,e,t,l.opts.specialEasing[e]||l.opts.easing);return l.tweens.push(n),n},stop:function(e){var t=0,n=e?l.tweens.length:0;if(a)return this;for(a=!0;t<n;t++)l.tweens[t].run(1);return e?(s.notifyWith(o,[l,1,0]),s.resolveWith(o,[l,e])):s.rejectWith(o,[l,e]),this}}),c=l.props;for(!function(e,t){var n,r,i,o,a;for(n in e)if(i=t[r=V(n)],o=e[n],Array.isArray(o)&&(i=o[1],o=e[n]=o[0]),n!==r&&(e[r]=o,delete e[n]),(a=k.cssHooks[r])&&"expand"in a)for(n in o=a.expand(o),delete e[r],o)n in e||(e[n]=o[n],t[n]=i);else t[r]=i}(c,l.opts.specialEasing);r<i;r++)if(n=dt.prefilters[r].call(l,o,c,l.opts))return m(n.stop)&&(k._queueHooks(l.elem,l.opts.queue).stop=n.stop.bind(n)),n;return k.map(c,pt,l),m(l.opts.start)&&l.opts.start.call(o,l),l.progress(l.opts.progress).done(l.opts.done,l.opts.complete).fail(l.opts.fail).always(l.opts.always),k.fx.timer(k.extend(u,{elem:o,anim:l,queue:l.opts.queue})),l}k.Animation=k.extend(dt,{tweeners:{"*":[function(e,t){var n=this.createTween(e,t);return le(n.elem,e,ne.exec(t),n),n}]},tweener:function(e,t){m(e)?(t=e,e=["*"]):e=e.match(R);for(var n,r=0,i=e.length;r<i;r++)n=e[r],dt.tweeners[n]=dt.tweeners[n]||[],dt.tweeners[n].unshift(t)},prefilters:[function(e,t,n){var r,i,o,a,s,u,l,c,f="width"in t||"height"in t,p=this,d={},h=e.style,g=e.nodeType&&se(e),v=Q.get(e,"fxshow");for(r in n.queue||(null==(a=k._queueHooks(e,"fx")).unqueued&&(a.unqueued=0,s=a.empty.fire,a.empty.fire=function(){a.unqueued||s()}),a.unqueued++,p.always(function(){p.always(function(){a.unqueued--,k.queue(e,"fx").length||a.empty.fire()})})),t)if(i=t[r],st.test(i)){if(delete t[r],o=o||"toggle"===i,i===(g?"hide":"show")){if("show"!==i||!v||void 0===v[r])continue;g=!0}d[r]=v&&v[r]||k.style(e,r)}if((u=!k.isEmptyObject(t))||!k.isEmptyObject(d))for(r in f&&1===e.nodeType&&(n.overflow=[h.overflow,h.overflowX,h.overflowY],null==(l=v&&v.display)&&(l=Q.get(e,"display")),"none"===(c=k.css(e,"display"))&&(l?c=l:(fe([e],!0),l=e.style.display||l,c=k.css(e,"display"),fe([e]))),("inline"===c||"inline-block"===c&&null!=l)&&"none"===k.css(e,"float")&&(u||(p.done(function(){h.display=l}),null==l&&(c=h.display,l="none"===c?"":c)),h.display="inline-block")),n.overflow&&(h.overflow="hidden",p.always(function(){h.overflow=n.overflow[0],h.overflowX=n.overflow[1],h.overflowY=n.overflow[2]})),u=!1,d)u||(v?"hidden"in v&&(g=v.hidden):v=Q.access(e,"fxshow",{display:l}),o&&(v.hidden=!g),g&&fe([e],!0),p.done(function(){for(r in g||fe([e]),Q.remove(e,"fxshow"),d)k.style(e,r,d[r])})),u=pt(g?v[r]:0,r,p),r in v||(v[r]=u.start,g&&(u.end=u.start,u.start=0))}],prefilter:function(e,t){t?dt.prefilters.unshift(e):dt.prefilters.push(e)}}),k.speed=function(e,t,n){var r=e&&"object"==typeof e?k.extend({},e):{complete:n||!n&&t||m(e)&&e,duration:e,easing:n&&t||t&&!m(t)&&t};return k.fx.off?r.duration=0:"number"!=typeof r.duration&&(r.duration in k.fx.speeds?r.duration=k.fx.speeds[r.duration]:r.duration=k.fx.speeds._default),null!=r.queue&&!0!==r.queue||(r.queue="fx"),r.old=r.complete,r.complete=function(){m(r.old)&&r.old.call(this),r.queue&&k.dequeue(this,r.queue)},r},k.fn.extend({fadeTo:function(e,t,n,r){return this.filter(se).css("opacity",0).show().end().animate({opacity:t},e,n,r)},animate:function(t,e,n,r){var i=k.isEmptyObject(t),o=k.speed(e,n,r),a=function(){var e=dt(this,k.extend({},t),o);(i||Q.get(this,"finish"))&&e.stop(!0)};return a.finish=a,i||!1===o.queue?this.each(a):this.queue(o.queue,a)},stop:function(i,e,o){var a=function(e){var t=e.stop;delete e.stop,t(o)};return"string"!=typeof i&&(o=e,e=i,i=void 0),e&&!1!==i&&this.queue(i||"fx",[]),this.each(function(){var e=!0,t=null!=i&&i+"queueHooks",n=k.timers,r=Q.get(this);if(t)r[t]&&r[t].stop&&a(r[t]);else for(t in r)r[t]&&r[t].stop&&ut.test(t)&&a(r[t]);for(t=n.length;t--;)n[t].elem!==this||null!=i&&n[t].queue!==i||(n[t].anim.stop(o),e=!1,n.splice(t,1));!e&&o||k.dequeue(this,i)})},finish:function(a){return!1!==a&&(a=a||"fx"),this.each(function(){var e,t=Q.get(this),n=t[a+"queue"],r=t[a+"queueHooks"],i=k.timers,o=n?n.length:0;for(t.finish=!0,k.queue(this,a,[]),r&&r.stop&&r.stop.call(this,!0),e=i.length;e--;)i[e].elem===this&&i[e].queue===a&&(i[e].anim.stop(!0),i.splice(e,1));for(e=0;e<o;e++)n[e]&&n[e].finish&&n[e].finish.call(this);delete t.finish})}}),k.each(["toggle","show","hide"],function(e,r){var i=k.fn[r];k.fn[r]=function(e,t,n){return null==e||"boolean"==typeof e?i.apply(this,arguments):this.animate(ft(r,!0),e,t,n)}}),k.each({slideDown:ft("show"),slideUp:ft("hide"),slideToggle:ft("toggle"),fadeIn:{opacity:"show"},fadeOut:{opacity:"hide"},fadeToggle:{opacity:"toggle"}},function(e,r){k.fn[e]=function(e,t,n){return this.animate(r,e,t,n)}}),k.timers=[],k.fx.tick=function(){var e,t=0,n=k.timers;for(rt=Date.now();t<n.length;t++)(e=n[t])()||n[t]!==e||n.splice(t--,1);n.length||k.fx.stop(),rt=void 0},k.fx.timer=function(e){k.timers.push(e),k.fx.start()},k.fx.interval=13,k.fx.start=function(){it||(it=!0,lt())},k.fx.stop=function(){it=null},k.fx.speeds={slow:600,fast:200,_default:400},k.fn.delay=function(r,e){return r=k.fx&&k.fx.speeds[r]||r,e=e||"fx",this.queue(e,function(e,t){var n=C.setTimeout(e,r);t.stop=function(){C.clearTimeout(n)}})},ot=E.createElement("input"),at=E.createElement("select").appendChild(E.createElement("option")),ot.type="checkbox",y.checkOn=""!==ot.value,y.optSelected=at.selected,(ot=E.createElement("input")).value="t",ot.type="radio",y.radioValue="t"===ot.value;var ht,gt=k.expr.attrHandle;k.fn.extend({attr:function(e,t){return _(this,k.attr,e,t,1<arguments.length)},removeAttr:function(e){return this.each(function(){k.removeAttr(this,e)})}}),k.extend({attr:function(e,t,n){var r,i,o=e.nodeType;if(3!==o&&8!==o&&2!==o)return"undefined"==typeof e.getAttribute?k.prop(e,t,n):(1===o&&k.isXMLDoc(e)||(i=k.attrHooks[t.toLowerCase()]||(k.expr.match.bool.test(t)?ht:void 0)),void 0!==n?null===n?void k.removeAttr(e,t):i&&"set"in i&&void 0!==(r=i.set(e,n,t))?r:(e.setAttribute(t,n+""),n):i&&"get"in i&&null!==(r=i.get(e,t))?r:null==(r=k.find.attr(e,t))?void 0:r)},attrHooks:{type:{set:function(e,t){if(!y.radioValue&&"radio"===t&&A(e,"input")){var n=e.value;return e.setAttribute("type",t),n&&(e.value=n),t}}}},removeAttr:function(e,t){var n,r=0,i=t&&t.match(R);if(i&&1===e.nodeType)while(n=i[r++])e.removeAttribute(n)}}),ht={set:function(e,t,n){return!1===t?k.removeAttr(e,n):e.setAttribute(n,n),n}},k.each(k.expr.match.bool.source.match(/\w+/g),function(e,t){var a=gt[t]||k.find.attr;gt[t]=function(e,t,n){var r,i,o=t.toLowerCase();return n||(i=gt[o],gt[o]=r,r=null!=a(e,t,n)?o:null,gt[o]=i),r}});var vt=/^(?:input|select|textarea|button)$/i,yt=/^(?:a|area)$/i;function mt(e){return(e.match(R)||[]).join(" ")}function xt(e){return e.getAttribute&&e.getAttribute("class")||""}function bt(e){return Array.isArray(e)?e:"string"==typeof e&&e.match(R)||[]}k.fn.extend({prop:function(e,t){return _(this,k.prop,e,t,1<arguments.length)},removeProp:function(e){return this.each(function(){delete this[k.propFix[e]||e]})}}),k.extend({prop:function(e,t,n){var r,i,o=e.nodeType;if(3!==o&&8!==o&&2!==o)return 1===o&&k.isXMLDoc(e)||(t=k.propFix[t]||t,i=k.propHooks[t]),void 0!==n?i&&"set"in i&&void 0!==(r=i.set(e,n,t))?r:e[t]=n:i&&"get"in i&&null!==(r=i.get(e,t))?r:e[t]},propHooks:{tabIndex:{get:function(e){var t=k.find.attr(e,"tabindex");return t?parseInt(t,10):vt.test(e.nodeName)||yt.test(e.nodeName)&&e.href?0:-1}}},propFix:{"for":"htmlFor","class":"className"}}),y.optSelected||(k.propHooks.selected={get:function(e){var t=e.parentNode;return t&&t.parentNode&&t.parentNode.selectedIndex,null},set:function(e){var t=e.parentNode;t&&(t.selectedIndex,t.parentNode&&t.parentNode.selectedIndex)}}),k.each(["tabIndex","readOnly","maxLength","cellSpacing","cellPadding","rowSpan","colSpan","useMap","frameBorder","contentEditable"],function(){k.propFix[this.toLowerCase()]=this}),k.fn.extend({addClass:function(t){var e,n,r,i,o,a,s,u=0;if(m(t))return this.each(function(e){k(this).addClass(t.call(this,e,xt(this)))});if((e=bt(t)).length)while(n=this[u++])if(i=xt(n),r=1===n.nodeType&&" "+mt(i)+" "){a=0;while(o=e[a++])r.indexOf(" "+o+" ")<0&&(r+=o+" ");i!==(s=mt(r))&&n.setAttribute("class",s)}return this},removeClass:function(t){var e,n,r,i,o,a,s,u=0;if(m(t))return this.each(function(e){k(this).removeClass(t.call(this,e,xt(this)))});if(!arguments.length)return this.attr("class","");if((e=bt(t)).length)while(n=this[u++])if(i=xt(n),r=1===n.nodeType&&" "+mt(i)+" "){a=0;while(o=e[a++])while(-1<r.indexOf(" "+o+" "))r=r.replace(" "+o+" "," ");i!==(s=mt(r))&&n.setAttribute("class",s)}return this},toggleClass:function(i,t){var o=typeof i,a="string"===o||Array.isArray(i);return"boolean"==typeof t&&a?t?this.addClass(i):this.removeClass(i):m(i)?this.each(function(e){k(this).toggleClass(i.call(this,e,xt(this),t),t)}):this.each(function(){var e,t,n,r;if(a){t=0,n=k(this),r=bt(i);while(e=r[t++])n.hasClass(e)?n.removeClass(e):n.addClass(e)}else void 0!==i&&"boolean"!==o||((e=xt(this))&&Q.set(this,"__className__",e),this.setAttribute&&this.setAttribute("class",e||!1===i?"":Q.get(this,"__className__")||""))})},hasClass:function(e){var t,n,r=0;t=" "+e+" ";while(n=this[r++])if(1===n.nodeType&&-1<(" "+mt(xt(n))+" ").indexOf(t))return!0;return!1}});var wt=/\r/g;k.fn.extend({val:function(n){var r,e,i,t=this[0];return arguments.length?(i=m(n),this.each(function(e){var t;1===this.nodeType&&(null==(t=i?n.call(this,e,k(this).val()):n)?t="":"number"==typeof t?t+="":Array.isArray(t)&&(t=k.map(t,function(e){return null==e?"":e+""})),(r=k.valHooks[this.type]||k.valHooks[this.nodeName.toLowerCase()])&&"set"in r&&void 0!==r.set(this,t,"value")||(this.value=t))})):t?(r=k.valHooks[t.type]||k.valHooks[t.nodeName.toLowerCase()])&&"get"in r&&void 0!==(e=r.get(t,"value"))?e:"string"==typeof(e=t.value)?e.replace(wt,""):null==e?"":e:void 0}}),k.extend({valHooks:{option:{get:function(e){var t=k.find.attr(e,"value");return null!=t?t:mt(k.text(e))}},select:{get:function(e){var t,n,r,i=e.options,o=e.selectedIndex,a="select-one"===e.type,s=a?null:[],u=a?o+1:i.length;for(r=o<0?u:a?o:0;r<u;r++)if(((n=i[r]).selected||r===o)&&!n.disabled&&(!n.parentNode.disabled||!A(n.parentNode,"optgroup"))){if(t=k(n).val(),a)return t;s.push(t)}return s},set:function(e,t){var n,r,i=e.options,o=k.makeArray(t),a=i.length;while(a--)((r=i[a]).selected=-1<k.inArray(k.valHooks.option.get(r),o))&&(n=!0);return n||(e.selectedIndex=-1),o}}}}),k.each(["radio","checkbox"],function(){k.valHooks[this]={set:function(e,t){if(Array.isArray(t))return e.checked=-1<k.inArray(k(e).val(),t)}},y.checkOn||(k.valHooks[this].get=function(e){return null===e.getAttribute("value")?"on":e.value})}),y.focusin="onfocusin"in C;var Tt=/^(?:focusinfocus|focusoutblur)$/,Ct=function(e){e.stopPropagation()};k.extend(k.event,{trigger:function(e,t,n,r){var i,o,a,s,u,l,c,f,p=[n||E],d=v.call(e,"type")?e.type:e,h=v.call(e,"namespace")?e.namespace.split("."):[];if(o=f=a=n=n||E,3!==n.nodeType&&8!==n.nodeType&&!Tt.test(d+k.event.triggered)&&(-1<d.indexOf(".")&&(d=(h=d.split(".")).shift(),h.sort()),u=d.indexOf(":")<0&&"on"+d,(e=e[k.expando]?e:new k.Event(d,"object"==typeof e&&e)).isTrigger=r?2:3,e.namespace=h.join("."),e.rnamespace=e.namespace?new RegExp("(^|\\.)"+h.join("\\.(?:.*\\.|)")+"(\\.|$)"):null,e.result=void 0,e.target||(e.target=n),t=null==t?[e]:k.makeArray(t,[e]),c=k.event.special[d]||{},r||!c.trigger||!1!==c.trigger.apply(n,t))){if(!r&&!c.noBubble&&!x(n)){for(s=c.delegateType||d,Tt.test(s+d)||(o=o.parentNode);o;o=o.parentNode)p.push(o),a=o;a===(n.ownerDocument||E)&&p.push(a.defaultView||a.parentWindow||C)}i=0;while((o=p[i++])&&!e.isPropagationStopped())f=o,e.type=1<i?s:c.bindType||d,(l=(Q.get(o,"events")||{})[e.type]&&Q.get(o,"handle"))&&l.apply(o,t),(l=u&&o[u])&&l.apply&&G(o)&&(e.result=l.apply(o,t),!1===e.result&&e.preventDefault());return e.type=d,r||e.isDefaultPrevented()||c._default&&!1!==c._default.apply(p.pop(),t)||!G(n)||u&&m(n[d])&&!x(n)&&((a=n[u])&&(n[u]=null),k.event.triggered=d,e.isPropagationStopped()&&f.addEventListener(d,Ct),n[d](),e.isPropagationStopped()&&f.removeEventListener(d,Ct),k.event.triggered=void 0,a&&(n[u]=a)),e.result}},simulate:function(e,t,n){var r=k.extend(new k.Event,n,{type:e,isSimulated:!0});k.event.trigger(r,null,t)}}),k.fn.extend({trigger:function(e,t){return this.each(function(){k.event.trigger(e,t,this)})},triggerHandler:function(e,t){var n=this[0];if(n)return k.event.trigger(e,t,n,!0)}}),y.focusin||k.each({focus:"focusin",blur:"focusout"},function(n,r){var i=function(e){k.event.simulate(r,e.target,k.event.fix(e))};k.event.special[r]={setup:function(){var e=this.ownerDocument||this,t=Q.access(e,r);t||e.addEventListener(n,i,!0),Q.access(e,r,(t||0)+1)},teardown:function(){var e=this.ownerDocument||this,t=Q.access(e,r)-1;t?Q.access(e,r,t):(e.removeEventListener(n,i,!0),Q.remove(e,r))}}});var Et=C.location,kt=Date.now(),St=/\?/;k.parseXML=function(e){var t;if(!e||"string"!=typeof e)return null;try{t=(new C.DOMParser).parseFromString(e,"text/xml")}catch(e){t=void 0}return t&&!t.getElementsByTagName("parsererror").length||k.error("Invalid XML: "+e),t};var Nt=/\[\]$/,At=/\r?\n/g,Dt=/^(?:submit|button|image|reset|file)$/i,jt=/^(?:input|select|textarea|keygen)/i;function qt(n,e,r,i){var t;if(Array.isArray(e))k.each(e,function(e,t){r||Nt.test(n)?i(n,t):qt(n+"["+("object"==typeof t&&null!=t?e:"")+"]",t,r,i)});else if(r||"object"!==w(e))i(n,e);else for(t in e)qt(n+"["+t+"]",e[t],r,i)}k.param=function(e,t){var n,r=[],i=function(e,t){var n=m(t)?t():t;r[r.length]=encodeURIComponent(e)+"="+encodeURIComponent(null==n?"":n)};if(null==e)return"";if(Array.isArray(e)||e.jquery&&!k.isPlainObject(e))k.each(e,function(){i(this.name,this.value)});else for(n in e)qt(n,e[n],t,i);return r.join("&")},k.fn.extend({serialize:function(){return k.param(this.serializeArray())},serializeArray:function(){return this.map(function(){var e=k.prop(this,"elements");return e?k.makeArray(e):this}).filter(function(){var e=this.type;return this.name&&!k(this).is(":disabled")&&jt.test(this.nodeName)&&!Dt.test(e)&&(this.checked||!pe.test(e))}).map(function(e,t){var n=k(this).val();return null==n?null:Array.isArray(n)?k.map(n,function(e){return{name:t.name,value:e.replace(At,"\r\n")}}):{name:t.name,value:n.replace(At,"\r\n")}}).get()}});var Lt=/%20/g,Ht=/#.*$/,Ot=/([?&])_=[^&]*/,Pt=/^(.*?):[ \t]*([^\r\n]*)$/gm,Rt=/^(?:GET|HEAD)$/,Mt=/^\/\//,It={},Wt={},$t="*/".concat("*"),Ft=E.createElement("a");function Bt(o){return function(e,t){"string"!=typeof e&&(t=e,e="*");var n,r=0,i=e.toLowerCase().match(R)||[];if(m(t))while(n=i[r++])"+"===n[0]?(n=n.slice(1)||"*",(o[n]=o[n]||[]).unshift(t)):(o[n]=o[n]||[]).push(t)}}function _t(t,i,o,a){var s={},u=t===Wt;function l(e){var r;return s[e]=!0,k.each(t[e]||[],function(e,t){var n=t(i,o,a);return"string"!=typeof n||u||s[n]?u?!(r=n):void 0:(i.dataTypes.unshift(n),l(n),!1)}),r}return l(i.dataTypes[0])||!s["*"]&&l("*")}function zt(e,t){var n,r,i=k.ajaxSettings.flatOptions||{};for(n in t)void 0!==t[n]&&((i[n]?e:r||(r={}))[n]=t[n]);return r&&k.extend(!0,e,r),e}Ft.href=Et.href,k.extend({active:0,lastModified:{},etag:{},ajaxSettings:{url:Et.href,type:"GET",isLocal:/^(?:about|app|app-storage|.+-extension|file|res|widget):$/.test(Et.protocol),global:!0,processData:!0,async:!0,contentType:"application/x-www-form-urlencoded; charset=UTF-8",accepts:{"*":$t,text:"text/plain",html:"text/html",xml:"application/xml, text/xml",json:"application/json, text/javascript"},contents:{xml:/\bxml\b/,html:/\bhtml/,json:/\bjson\b/},responseFields:{xml:"responseXML",text:"responseText",json:"responseJSON"},converters:{"* text":String,"text html":!0,"text json":JSON.parse,"text xml":k.parseXML},flatOptions:{url:!0,context:!0}},ajaxSetup:function(e,t){return t?zt(zt(e,k.ajaxSettings),t):zt(k.ajaxSettings,e)},ajaxPrefilter:Bt(It),ajaxTransport:Bt(Wt),ajax:function(e,t){"object"==typeof e&&(t=e,e=void 0),t=t||{};var c,f,p,n,d,r,h,g,i,o,v=k.ajaxSetup({},t),y=v.context||v,m=v.context&&(y.nodeType||y.jquery)?k(y):k.event,x=k.Deferred(),b=k.Callbacks("once memory"),w=v.statusCode||{},a={},s={},u="canceled",T={readyState:0,getResponseHeader:function(e){var t;if(h){if(!n){n={};while(t=Pt.exec(p))n[t[1].toLowerCase()+" "]=(n[t[1].toLowerCase()+" "]||[]).concat(t[2])}t=n[e.toLowerCase()+" "]}return null==t?null:t.join(", ")},getAllResponseHeaders:function(){return h?p:null},setRequestHeader:function(e,t){return null==h&&(e=s[e.toLowerCase()]=s[e.toLowerCase()]||e,a[e]=t),this},overrideMimeType:function(e){return null==h&&(v.mimeType=e),this},statusCode:function(e){var t;if(e)if(h)T.always(e[T.status]);else for(t in e)w[t]=[w[t],e[t]];return this},abort:function(e){var t=e||u;return c&&c.abort(t),l(0,t),this}};if(x.promise(T),v.url=((e||v.url||Et.href)+"").replace(Mt,Et.protocol+"//"),v.type=t.method||t.type||v.method||v.type,v.dataTypes=(v.dataType||"*").toLowerCase().match(R)||[""],null==v.crossDomain){r=E.createElement("a");try{r.href=v.url,r.href=r.href,v.crossDomain=Ft.protocol+"//"+Ft.host!=r.protocol+"//"+r.host}catch(e){v.crossDomain=!0}}if(v.data&&v.processData&&"string"!=typeof v.data&&(v.data=k.param(v.data,v.traditional)),_t(It,v,t,T),h)return T;for(i in(g=k.event&&v.global)&&0==k.active++&&k.event.trigger("ajaxStart"),v.type=v.type.toUpperCase(),v.hasContent=!Rt.test(v.type),f=v.url.replace(Ht,""),v.hasContent?v.data&&v.processData&&0===(v.contentType||"").indexOf("application/x-www-form-urlencoded")&&(v.data=v.data.replace(Lt,"+")):(o=v.url.slice(f.length),v.data&&(v.processData||"string"==typeof v.data)&&(f+=(St.test(f)?"&":"?")+v.data,delete v.data),!1===v.cache&&(f=f.replace(Ot,"$1"),o=(St.test(f)?"&":"?")+"_="+kt+++o),v.url=f+o),v.ifModified&&(k.lastModified[f]&&T.setRequestHeader("If-Modified-Since",k.lastModified[f]),k.etag[f]&&T.setRequestHeader("If-None-Match",k.etag[f])),(v.data&&v.hasContent&&!1!==v.contentType||t.contentType)&&T.setRequestHeader("Content-Type",v.contentType),T.setRequestHeader("Accept",v.dataTypes[0]&&v.accepts[v.dataTypes[0]]?v.accepts[v.dataTypes[0]]+("*"!==v.dataTypes[0]?", "+$t+"; q=0.01":""):v.accepts["*"]),v.headers)T.setRequestHeader(i,v.headers[i]);if(v.beforeSend&&(!1===v.beforeSend.call(y,T,v)||h))return T.abort();if(u="abort",b.add(v.complete),T.done(v.success),T.fail(v.error),c=_t(Wt,v,t,T)){if(T.readyState=1,g&&m.trigger("ajaxSend",[T,v]),h)return T;v.async&&0<v.timeout&&(d=C.setTimeout(function(){T.abort("timeout")},v.timeout));try{h=!1,c.send(a,l)}catch(e){if(h)throw e;l(-1,e)}}else l(-1,"No Transport");function l(e,t,n,r){var i,o,a,s,u,l=t;h||(h=!0,d&&C.clearTimeout(d),c=void 0,p=r||"",T.readyState=0<e?4:0,i=200<=e&&e<300||304===e,n&&(s=function(e,t,n){var r,i,o,a,s=e.contents,u=e.dataTypes;while("*"===u[0])u.shift(),void 0===r&&(r=e.mimeType||t.getResponseHeader("Content-Type"));if(r)for(i in s)if(s[i]&&s[i].test(r)){u.unshift(i);break}if(u[0]in n)o=u[0];else{for(i in n){if(!u[0]||e.converters[i+" "+u[0]]){o=i;break}a||(a=i)}o=o||a}if(o)return o!==u[0]&&u.unshift(o),n[o]}(v,T,n)),s=function(e,t,n,r){var i,o,a,s,u,l={},c=e.dataTypes.slice();if(c[1])for(a in e.converters)l[a.toLowerCase()]=e.converters[a];o=c.shift();while(o)if(e.responseFields[o]&&(n[e.responseFields[o]]=t),!u&&r&&e.dataFilter&&(t=e.dataFilter(t,e.dataType)),u=o,o=c.shift())if("*"===o)o=u;else if("*"!==u&&u!==o){if(!(a=l[u+" "+o]||l["* "+o]))for(i in l)if((s=i.split(" "))[1]===o&&(a=l[u+" "+s[0]]||l["* "+s[0]])){!0===a?a=l[i]:!0!==l[i]&&(o=s[0],c.unshift(s[1]));break}if(!0!==a)if(a&&e["throws"])t=a(t);else try{t=a(t)}catch(e){return{state:"parsererror",error:a?e:"No conversion from "+u+" to "+o}}}return{state:"success",data:t}}(v,s,T,i),i?(v.ifModified&&((u=T.getResponseHeader("Last-Modified"))&&(k.lastModified[f]=u),(u=T.getResponseHeader("etag"))&&(k.etag[f]=u)),204===e||"HEAD"===v.type?l="nocontent":304===e?l="notmodified":(l=s.state,o=s.data,i=!(a=s.error))):(a=l,!e&&l||(l="error",e<0&&(e=0))),T.status=e,T.statusText=(t||l)+"",i?x.resolveWith(y,[o,l,T]):x.rejectWith(y,[T,l,a]),T.statusCode(w),w=void 0,g&&m.trigger(i?"ajaxSuccess":"ajaxError",[T,v,i?o:a]),b.fireWith(y,[T,l]),g&&(m.trigger("ajaxComplete",[T,v]),--k.active||k.event.trigger("ajaxStop")))}return T},getJSON:function(e,t,n){return k.get(e,t,n,"json")},getScript:function(e,t){return k.get(e,void 0,t,"script")}}),k.each(["get","post"],function(e,i){k[i]=function(e,t,n,r){return m(t)&&(r=r||n,n=t,t=void 0),k.ajax(k.extend({url:e,type:i,dataType:r,data:t,success:n},k.isPlainObject(e)&&e))}}),k._evalUrl=function(e,t){return k.ajax({url:e,type:"GET",dataType:"script",cache:!0,async:!1,global:!1,converters:{"text script":function(){}},dataFilter:function(e){k.globalEval(e,t)}})},k.fn.extend({wrapAll:function(e){var t;return this[0]&&(m(e)&&(e=e.call(this[0])),t=k(e,this[0].ownerDocument).eq(0).clone(!0),this[0].parentNode&&t.insertBefore(this[0]),t.map(function(){var e=this;while(e.firstElementChild)e=e.firstElementChild;return e}).append(this)),this},wrapInner:function(n){return m(n)?this.each(function(e){k(this).wrapInner(n.call(this,e))}):this.each(function(){var e=k(this),t=e.contents();t.length?t.wrapAll(n):e.append(n)})},wrap:function(t){var n=m(t);return this.each(function(e){k(this).wrapAll(n?t.call(this,e):t)})},unwrap:function(e){return this.parent(e).not("body").each(function(){k(this).replaceWith(this.childNodes)}),this}}),k.expr.pseudos.hidden=function(e){return!k.expr.pseudos.visible(e)},k.expr.pseudos.visible=function(e){return!!(e.offsetWidth||e.offsetHeight||e.getClientRects().length)},k.ajaxSettings.xhr=function(){try{return new C.XMLHttpRequest}catch(e){}};var Ut={0:200,1223:204},Xt=k.ajaxSettings.xhr();y.cors=!!Xt&&"withCredentials"in Xt,y.ajax=Xt=!!Xt,k.ajaxTransport(function(i){var o,a;if(y.cors||Xt&&!i.crossDomain)return{send:function(e,t){var n,r=i.xhr();if(r.open(i.type,i.url,i.async,i.username,i.password),i.xhrFields)for(n in i.xhrFields)r[n]=i.xhrFields[n];for(n in i.mimeType&&r.overrideMimeType&&r.overrideMimeType(i.mimeType),i.crossDomain||e["X-Requested-With"]||(e["X-Requested-With"]="XMLHttpRequest"),e)r.setRequestHeader(n,e[n]);o=function(e){return function(){o&&(o=a=r.onload=r.onerror=r.onabort=r.ontimeout=r.onreadystatechange=null,"abort"===e?r.abort():"error"===e?"number"!=typeof r.status?t(0,"error"):t(r.status,r.statusText):t(Ut[r.status]||r.status,r.statusText,"text"!==(r.responseType||"text")||"string"!=typeof r.responseText?{binary:r.response}:{text:r.responseText},r.getAllResponseHeaders()))}},r.onload=o(),a=r.onerror=r.ontimeout=o("error"),void 0!==r.onabort?r.onabort=a:r.onreadystatechange=function(){4===r.readyState&&C.setTimeout(function(){o&&a()})},o=o("abort");try{r.send(i.hasContent&&i.data||null)}catch(e){if(o)throw e}},abort:function(){o&&o()}}}),k.ajaxPrefilter(function(e){e.crossDomain&&(e.contents.script=!1)}),k.ajaxSetup({accepts:{script:"text/javascript, application/javascript, application/ecmascript, application/x-ecmascript"},contents:{script:/\b(?:java|ecma)script\b/},converters:{"text script":function(e){return k.globalEval(e),e}}}),k.ajaxPrefilter("script",function(e){void 0===e.cache&&(e.cache=!1),e.crossDomain&&(e.type="GET")}),k.ajaxTransport("script",function(n){var r,i;if(n.crossDomain||n.scriptAttrs)return{send:function(e,t){r=k("<script>").attr(n.scriptAttrs||{}).prop({charset:n.scriptCharset,src:n.url}).on("load error",i=function(e){r.remove(),i=null,e&&t("error"===e.type?404:200,e.type)}),E.head.appendChild(r[0])},abort:function(){i&&i()}}});var Vt,Gt=[],Yt=/(=)\?(?=&|$)|\?\?/;k.ajaxSetup({jsonp:"callback",jsonpCallback:function(){var e=Gt.pop()||k.expando+"_"+kt++;return this[e]=!0,e}}),k.ajaxPrefilter("json jsonp",function(e,t,n){var r,i,o,a=!1!==e.jsonp&&(Yt.test(e.url)?"url":"string"==typeof e.data&&0===(e.contentType||"").indexOf("application/x-www-form-urlencoded")&&Yt.test(e.data)&&"data");if(a||"jsonp"===e.dataTypes[0])return r=e.jsonpCallback=m(e.jsonpCallback)?e.jsonpCallback():e.jsonpCallback,a?e[a]=e[a].replace(Yt,"$1"+r):!1!==e.jsonp&&(e.url+=(St.test(e.url)?"&":"?")+e.jsonp+"="+r),e.converters["script json"]=function(){return o||k.error(r+" was not called"),o[0]},e.dataTypes[0]="json",i=C[r],C[r]=function(){o=arguments},n.always(function(){void 0===i?k(C).removeProp(r):C[r]=i,e[r]&&(e.jsonpCallback=t.jsonpCallback,Gt.push(r)),o&&m(i)&&i(o[0]),o=i=void 0}),"script"}),y.createHTMLDocument=((Vt=E.implementation.createHTMLDocument("").body).innerHTML="<form></form><form></form>",2===Vt.childNodes.length),k.parseHTML=function(e,t,n){return"string"!=typeof e?[]:("boolean"==typeof t&&(n=t,t=!1),t||(y.createHTMLDocument?((r=(t=E.implementation.createHTMLDocument("")).createElement("base")).href=E.location.href,t.head.appendChild(r)):t=E),o=!n&&[],(i=D.exec(e))?[t.createElement(i[1])]:(i=we([e],t,o),o&&o.length&&k(o).remove(),k.merge([],i.childNodes)));var r,i,o},k.fn.load=function(e,t,n){var r,i,o,a=this,s=e.indexOf(" ");return-1<s&&(r=mt(e.slice(s)),e=e.slice(0,s)),m(t)?(n=t,t=void 0):t&&"object"==typeof t&&(i="POST"),0<a.length&&k.ajax({url:e,type:i||"GET",dataType:"html",data:t}).done(function(e){o=arguments,a.html(r?k("<div>").append(k.parseHTML(e)).find(r):e)}).always(n&&function(e,t){a.each(function(){n.apply(this,o||[e.responseText,t,e])})}),this},k.each(["ajaxStart","ajaxStop","ajaxComplete","ajaxError","ajaxSuccess","ajaxSend"],function(e,t){k.fn[t]=function(e){return this.on(t,e)}}),k.expr.pseudos.animated=function(t){return k.grep(k.timers,function(e){return t===e.elem}).length},k.offset={setOffset:function(e,t,n){var r,i,o,a,s,u,l=k.css(e,"position"),c=k(e),f={};"static"===l&&(e.style.position="relative"),s=c.offset(),o=k.css(e,"top"),u=k.css(e,"left"),("absolute"===l||"fixed"===l)&&-1<(o+u).indexOf("auto")?(a=(r=c.position()).top,i=r.left):(a=parseFloat(o)||0,i=parseFloat(u)||0),m(t)&&(t=t.call(e,n,k.extend({},s))),null!=t.top&&(f.top=t.top-s.top+a),null!=t.left&&(f.left=t.left-s.left+i),"using"in t?t.using.call(e,f):c.css(f)}},k.fn.extend({offset:function(t){if(arguments.length)return void 0===t?this:this.each(function(e){k.offset.setOffset(this,t,e)});var e,n,r=this[0];return r?r.getClientRects().length?(e=r.getBoundingClientRect(),n=r.ownerDocument.defaultView,{top:e.top+n.pageYOffset,left:e.left+n.pageXOffset}):{top:0,left:0}:void 0},position:function(){if(this[0]){var e,t,n,r=this[0],i={top:0,left:0};if("fixed"===k.css(r,"position"))t=r.getBoundingClientRect();else{t=this.offset(),n=r.ownerDocument,e=r.offsetParent||n.documentElement;while(e&&(e===n.body||e===n.documentElement)&&"static"===k.css(e,"position"))e=e.parentNode;e&&e!==r&&1===e.nodeType&&((i=k(e).offset()).top+=k.css(e,"borderTopWidth",!0),i.left+=k.css(e,"borderLeftWidth",!0))}return{top:t.top-i.top-k.css(r,"marginTop",!0),left:t.left-i.left-k.css(r,"marginLeft",!0)}}},offsetParent:function(){return this.map(function(){var e=this.offsetParent;while(e&&"static"===k.css(e,"position"))e=e.offsetParent;return e||ie})}}),k.each({scrollLeft:"pageXOffset",scrollTop:"pageYOffset"},function(t,i){var o="pageYOffset"===i;k.fn[t]=function(e){return _(this,function(e,t,n){var r;if(x(e)?r=e:9===e.nodeType&&(r=e.defaultView),void 0===n)return r?r[i]:e[t];r?r.scrollTo(o?r.pageXOffset:n,o?n:r.pageYOffset):e[t]=n},t,e,arguments.length)}}),k.each(["top","left"],function(e,n){k.cssHooks[n]=ze(y.pixelPosition,function(e,t){if(t)return t=_e(e,n),$e.test(t)?k(e).position()[n]+"px":t})}),k.each({Height:"height",Width:"width"},function(a,s){k.each({padding:"inner"+a,content:s,"":"outer"+a},function(r,o){k.fn[o]=function(e,t){var n=arguments.length&&(r||"boolean"!=typeof e),i=r||(!0===e||!0===t?"margin":"border");return _(this,function(e,t,n){var r;return x(e)?0===o.indexOf("outer")?e["inner"+a]:e.document.documentElement["client"+a]:9===e.nodeType?(r=e.documentElement,Math.max(e.body["scroll"+a],r["scroll"+a],e.body["offset"+a],r["offset"+a],r["client"+a])):void 0===n?k.css(e,t,i):k.style(e,t,n,i)},s,n?e:void 0,n)}})}),k.each("blur focus focusin focusout resize scroll click dblclick mousedown mouseup mousemove mouseover mouseout mouseenter mouseleave change select submit keydown keypress keyup contextmenu".split(" "),function(e,n){k.fn[n]=function(e,t){return 0<arguments.length?this.on(n,null,e,t):this.trigger(n)}}),k.fn.extend({hover:function(e,t){return this.mouseenter(e).mouseleave(t||e)}}),k.fn.extend({bind:function(e,t,n){return this.on(e,null,t,n)},unbind:function(e,t){return this.off(e,null,t)},delegate:function(e,t,n,r){return this.on(t,e,n,r)},undelegate:function(e,t,n){return 1===arguments.length?this.off(e,"**"):this.off(t,e||"**",n)}}),k.proxy=function(e,t){var n,r,i;if("string"==typeof t&&(n=e[t],t=e,e=n),m(e))return r=s.call(arguments,2),(i=function(){return e.apply(t||this,r.concat(s.call(arguments)))}).guid=e.guid=e.guid||k.guid++,i},k.holdReady=function(e){e?k.readyWait++:k.ready(!0)},k.isArray=Array.isArray,k.parseJSON=JSON.parse,k.nodeName=A,k.isFunction=m,k.isWindow=x,k.camelCase=V,k.type=w,k.now=Date.now,k.isNumeric=function(e){var t=k.type(e);return("number"===t||"string"===t)&&!isNaN(e-parseFloat(e))},"function"==typeof define&&define.amd&&define("jquery",[],function(){return k});var Qt=C.jQuery,Jt=C.$;return k.noConflict=function(e){return C.$===k&&(C.$=Jt),e&&C.jQuery===k&&(C.jQuery=Qt),k},e||(C.jQuery=C.$=k),k});
+/*! jQuery v3.6.0 | (c) OpenJS Foundation and other contributors | jquery.org/license */
+!function(e,t){"use strict";"object"==typeof module&&"object"==typeof module.exports?module.exports=e.document?t(e,!0):function(e){if(!e.document)throw new Error("jQuery requires a window with a document");return t(e)}:t(e)}("undefined"!=typeof window?window:this,function(C,e){"use strict";var t=[],r=Object.getPrototypeOf,s=t.slice,g=t.flat?function(e){return t.flat.call(e)}:function(e){return t.concat.apply([],e)},u=t.push,i=t.indexOf,n={},o=n.toString,v=n.hasOwnProperty,a=v.toString,l=a.call(Object),y={},m=function(e){return"function"==typeof e&&"number"!=typeof e.nodeType&&"function"!=typeof e.item},x=function(e){return null!=e&&e===e.window},E=C.document,c={type:!0,src:!0,nonce:!0,noModule:!0};function b(e,t,n){var r,i,o=(n=n||E).createElement("script");if(o.text=e,t)for(r in c)(i=t[r]||t.getAttribute&&t.getAttribute(r))&&o.setAttribute(r,i);n.head.appendChild(o).parentNode.removeChild(o)}function w(e){return null==e?e+"":"object"==typeof e||"function"==typeof e?n[o.call(e)]||"object":typeof e}var f="3.6.0",S=function(e,t){return new S.fn.init(e,t)};function p(e){var t=!!e&&"length"in e&&e.length,n=w(e);return!m(e)&&!x(e)&&("array"===n||0===t||"number"==typeof t&&0<t&&t-1 in e)}S.fn=S.prototype={jquery:f,constructor:S,length:0,toArray:function(){return s.call(this)},get:function(e){return null==e?s.call(this):e<0?this[e+this.length]:this[e]},pushStack:function(e){var t=S.merge(this.constructor(),e);return t.prevObject=this,t},each:function(e){return S.each(this,e)},map:function(n){return this.pushStack(S.map(this,function(e,t){return n.call(e,t,e)}))},slice:function(){return this.pushStack(s.apply(this,arguments))},first:function(){return this.eq(0)},last:function(){return this.eq(-1)},even:function(){return this.pushStack(S.grep(this,function(e,t){return(t+1)%2}))},odd:function(){return this.pushStack(S.grep(this,function(e,t){return t%2}))},eq:function(e){var t=this.length,n=+e+(e<0?t:0);return this.pushStack(0<=n&&n<t?[this[n]]:[])},end:function(){return this.prevObject||this.constructor()},push:u,sort:t.sort,splice:t.splice},S.extend=S.fn.extend=function(){var e,t,n,r,i,o,a=arguments[0]||{},s=1,u=arguments.length,l=!1;for("boolean"==typeof a&&(l=a,a=arguments[s]||{},s++),"object"==typeof a||m(a)||(a={}),s===u&&(a=this,s--);s<u;s++)if(null!=(e=arguments[s]))for(t in e)r=e[t],"__proto__"!==t&&a!==r&&(l&&r&&(S.isPlainObject(r)||(i=Array.isArray(r)))?(n=a[t],o=i&&!Array.isArray(n)?[]:i||S.isPlainObject(n)?n:{},i=!1,a[t]=S.extend(l,o,r)):void 0!==r&&(a[t]=r));return a},S.extend({expando:"jQuery"+(f+Math.random()).replace(/\D/g,""),isReady:!0,error:function(e){throw new Error(e)},noop:function(){},isPlainObject:function(e){var t,n;return!(!e||"[object Object]"!==o.call(e))&&(!(t=r(e))||"function"==typeof(n=v.call(t,"constructor")&&t.constructor)&&a.call(n)===l)},isEmptyObject:function(e){var t;for(t in e)return!1;return!0},globalEval:function(e,t,n){b(e,{nonce:t&&t.nonce},n)},each:function(e,t){var n,r=0;if(p(e)){for(n=e.length;r<n;r++)if(!1===t.call(e[r],r,e[r]))break}else for(r in e)if(!1===t.call(e[r],r,e[r]))break;return e},makeArray:function(e,t){var n=t||[];return null!=e&&(p(Object(e))?S.merge(n,"string"==typeof e?[e]:e):u.call(n,e)),n},inArray:function(e,t,n){return null==t?-1:i.call(t,e,n)},merge:function(e,t){for(var n=+t.length,r=0,i=e.length;r<n;r++)e[i++]=t[r];return e.length=i,e},grep:function(e,t,n){for(var r=[],i=0,o=e.length,a=!n;i<o;i++)!t(e[i],i)!==a&&r.push(e[i]);return r},map:function(e,t,n){var r,i,o=0,a=[];if(p(e))for(r=e.length;o<r;o++)null!=(i=t(e[o],o,n))&&a.push(i);else for(o in e)null!=(i=t(e[o],o,n))&&a.push(i);return g(a)},guid:1,support:y}),"function"==typeof Symbol&&(S.fn[Symbol.iterator]=t[Symbol.iterator]),S.each("Boolean Number String Function Array Date RegExp Object Error Symbol".split(" "),function(e,t){n["[object "+t+"]"]=t.toLowerCase()});var d=function(n){var e,d,b,o,i,h,f,g,w,u,l,T,C,a,E,v,s,c,y,S="sizzle"+1*new Date,p=n.document,k=0,r=0,m=ue(),x=ue(),A=ue(),N=ue(),j=function(e,t){return e===t&&(l=!0),0},D={}.hasOwnProperty,t=[],q=t.pop,L=t.push,H=t.push,O=t.slice,P=function(e,t){for(var n=0,r=e.length;n<r;n++)if(e[n]===t)return n;return-1},R="checked|selected|async|autofocus|autoplay|controls|defer|disabled|hidden|ismap|loop|multiple|open|readonly|required|scoped",M="[\\x20\\t\\r\\n\\f]",I="(?:\\\\[\\da-fA-F]{1,6}"+M+"?|\\\\[^\\r\\n\\f]|[\\w-]|[^\0-\\x7f])+",W="\\["+M+"*("+I+")(?:"+M+"*([*^$|!~]?=)"+M+"*(?:'((?:\\\\.|[^\\\\'])*)'|\"((?:\\\\.|[^\\\\\"])*)\"|("+I+"))|)"+M+"*\\]",F=":("+I+")(?:\\((('((?:\\\\.|[^\\\\'])*)'|\"((?:\\\\.|[^\\\\\"])*)\")|((?:\\\\.|[^\\\\()[\\]]|"+W+")*)|.*)\\)|)",B=new RegExp(M+"+","g"),$=new RegExp("^"+M+"+|((?:^|[^\\\\])(?:\\\\.)*)"+M+"+$","g"),_=new RegExp("^"+M+"*,"+M+"*"),z=new RegExp("^"+M+"*([>+~]|"+M+")"+M+"*"),U=new RegExp(M+"|>"),X=new RegExp(F),V=new RegExp("^"+I+"$"),G={ID:new RegExp("^#("+I+")"),CLASS:new RegExp("^\\.("+I+")"),TAG:new RegExp("^("+I+"|[*])"),ATTR:new RegExp("^"+W),PSEUDO:new RegExp("^"+F),CHILD:new RegExp("^:(only|first|last|nth|nth-last)-(child|of-type)(?:\\("+M+"*(even|odd|(([+-]|)(\\d*)n|)"+M+"*(?:([+-]|)"+M+"*(\\d+)|))"+M+"*\\)|)","i"),bool:new RegExp("^(?:"+R+")$","i"),needsContext:new RegExp("^"+M+"*[>+~]|:(even|odd|eq|gt|lt|nth|first|last)(?:\\("+M+"*((?:-\\d)?\\d*)"+M+"*\\)|)(?=[^-]|$)","i")},Y=/HTML$/i,Q=/^(?:input|select|textarea|button)$/i,J=/^h\d$/i,K=/^[^{]+\{\s*\[native \w/,Z=/^(?:#([\w-]+)|(\w+)|\.([\w-]+))$/,ee=/[+~]/,te=new RegExp("\\\\[\\da-fA-F]{1,6}"+M+"?|\\\\([^\\r\\n\\f])","g"),ne=function(e,t){var n="0x"+e.slice(1)-65536;return t||(n<0?String.fromCharCode(n+65536):String.fromCharCode(n>>10|55296,1023&n|56320))},re=/([\0-\x1f\x7f]|^-?\d)|^-$|[^\0-\x1f\x7f-\uFFFF\w-]/g,ie=function(e,t){return t?"\0"===e?"\ufffd":e.slice(0,-1)+"\\"+e.charCodeAt(e.length-1).toString(16)+" ":"\\"+e},oe=function(){T()},ae=be(function(e){return!0===e.disabled&&"fieldset"===e.nodeName.toLowerCase()},{dir:"parentNode",next:"legend"});try{H.apply(t=O.call(p.childNodes),p.childNodes),t[p.childNodes.length].nodeType}catch(e){H={apply:t.length?function(e,t){L.apply(e,O.call(t))}:function(e,t){var n=e.length,r=0;while(e[n++]=t[r++]);e.length=n-1}}}function se(t,e,n,r){var i,o,a,s,u,l,c,f=e&&e.ownerDocument,p=e?e.nodeType:9;if(n=n||[],"string"!=typeof t||!t||1!==p&&9!==p&&11!==p)return n;if(!r&&(T(e),e=e||C,E)){if(11!==p&&(u=Z.exec(t)))if(i=u[1]){if(9===p){if(!(a=e.getElementById(i)))return n;if(a.id===i)return n.push(a),n}else if(f&&(a=f.getElementById(i))&&y(e,a)&&a.id===i)return n.push(a),n}else{if(u[2])return H.apply(n,e.getElementsByTagName(t)),n;if((i=u[3])&&d.getElementsByClassName&&e.getElementsByClassName)return H.apply(n,e.getElementsByClassName(i)),n}if(d.qsa&&!N[t+" "]&&(!v||!v.test(t))&&(1!==p||"object"!==e.nodeName.toLowerCase())){if(c=t,f=e,1===p&&(U.test(t)||z.test(t))){(f=ee.test(t)&&ye(e.parentNode)||e)===e&&d.scope||((s=e.getAttribute("id"))?s=s.replace(re,ie):e.setAttribute("id",s=S)),o=(l=h(t)).length;while(o--)l[o]=(s?"#"+s:":scope")+" "+xe(l[o]);c=l.join(",")}try{return H.apply(n,f.querySelectorAll(c)),n}catch(e){N(t,!0)}finally{s===S&&e.removeAttribute("id")}}}return g(t.replace($,"$1"),e,n,r)}function ue(){var r=[];return function e(t,n){return r.push(t+" ")>b.cacheLength&&delete e[r.shift()],e[t+" "]=n}}function le(e){return e[S]=!0,e}function ce(e){var t=C.createElement("fieldset");try{return!!e(t)}catch(e){return!1}finally{t.parentNode&&t.parentNode.removeChild(t),t=null}}function fe(e,t){var n=e.split("|"),r=n.length;while(r--)b.attrHandle[n[r]]=t}function pe(e,t){var n=t&&e,r=n&&1===e.nodeType&&1===t.nodeType&&e.sourceIndex-t.sourceIndex;if(r)return r;if(n)while(n=n.nextSibling)if(n===t)return-1;return e?1:-1}function de(t){return function(e){return"input"===e.nodeName.toLowerCase()&&e.type===t}}function he(n){return function(e){var t=e.nodeName.toLowerCase();return("input"===t||"button"===t)&&e.type===n}}function ge(t){return function(e){return"form"in e?e.parentNode&&!1===e.disabled?"label"in e?"label"in e.parentNode?e.parentNode.disabled===t:e.disabled===t:e.isDisabled===t||e.isDisabled!==!t&&ae(e)===t:e.disabled===t:"label"in e&&e.disabled===t}}function ve(a){return le(function(o){return o=+o,le(function(e,t){var n,r=a([],e.length,o),i=r.length;while(i--)e[n=r[i]]&&(e[n]=!(t[n]=e[n]))})})}function ye(e){return e&&"undefined"!=typeof e.getElementsByTagName&&e}for(e in d=se.support={},i=se.isXML=function(e){var t=e&&e.namespaceURI,n=e&&(e.ownerDocument||e).documentElement;return!Y.test(t||n&&n.nodeName||"HTML")},T=se.setDocument=function(e){var t,n,r=e?e.ownerDocument||e:p;return r!=C&&9===r.nodeType&&r.documentElement&&(a=(C=r).documentElement,E=!i(C),p!=C&&(n=C.defaultView)&&n.top!==n&&(n.addEventListener?n.addEventListener("unload",oe,!1):n.attachEvent&&n.attachEvent("onunload",oe)),d.scope=ce(function(e){return a.appendChild(e).appendChild(C.createElement("div")),"undefined"!=typeof e.querySelectorAll&&!e.querySelectorAll(":scope fieldset div").length}),d.attributes=ce(function(e){return e.className="i",!e.getAttribute("className")}),d.getElementsByTagName=ce(function(e){return e.appendChild(C.createComment("")),!e.getElementsByTagName("*").length}),d.getElementsByClassName=K.test(C.getElementsByClassName),d.getById=ce(function(e){return a.appendChild(e).id=S,!C.getElementsByName||!C.getElementsByName(S).length}),d.getById?(b.filter.ID=function(e){var t=e.replace(te,ne);return function(e){return e.getAttribute("id")===t}},b.find.ID=function(e,t){if("undefined"!=typeof t.getElementById&&E){var n=t.getElementById(e);return n?[n]:[]}}):(b.filter.ID=function(e){var n=e.replace(te,ne);return function(e){var t="undefined"!=typeof e.getAttributeNode&&e.getAttributeNode("id");return t&&t.value===n}},b.find.ID=function(e,t){if("undefined"!=typeof t.getElementById&&E){var n,r,i,o=t.getElementById(e);if(o){if((n=o.getAttributeNode("id"))&&n.value===e)return[o];i=t.getElementsByName(e),r=0;while(o=i[r++])if((n=o.getAttributeNode("id"))&&n.value===e)return[o]}return[]}}),b.find.TAG=d.getElementsByTagName?function(e,t){return"undefined"!=typeof t.getElementsByTagName?t.getElementsByTagName(e):d.qsa?t.querySelectorAll(e):void 0}:function(e,t){var n,r=[],i=0,o=t.getElementsByTagName(e);if("*"===e){while(n=o[i++])1===n.nodeType&&r.push(n);return r}return o},b.find.CLASS=d.getElementsByClassName&&function(e,t){if("undefined"!=typeof t.getElementsByClassName&&E)return t.getElementsByClassName(e)},s=[],v=[],(d.qsa=K.test(C.querySelectorAll))&&(ce(function(e){var t;a.appendChild(e).innerHTML="<a id='"+S+"'></a><select id='"+S+"-\r\\' msallowcapture=''><option selected=''></option></select>",e.querySelectorAll("[msallowcapture^='']").length&&v.push("[*^$]="+M+"*(?:''|\"\")"),e.querySelectorAll("[selected]").length||v.push("\\["+M+"*(?:value|"+R+")"),e.querySelectorAll("[id~="+S+"-]").length||v.push("~="),(t=C.createElement("input")).setAttribute("name",""),e.appendChild(t),e.querySelectorAll("[name='']").length||v.push("\\["+M+"*name"+M+"*="+M+"*(?:''|\"\")"),e.querySelectorAll(":checked").length||v.push(":checked"),e.querySelectorAll("a#"+S+"+*").length||v.push(".#.+[+~]"),e.querySelectorAll("\\\f"),v.push("[\\r\\n\\f]")}),ce(function(e){e.innerHTML="<a href='' disabled='disabled'></a><select disabled='disabled'><option/></select>";var t=C.createElement("input");t.setAttribute("type","hidden"),e.appendChild(t).setAttribute("name","D"),e.querySelectorAll("[name=d]").length&&v.push("name"+M+"*[*^$|!~]?="),2!==e.querySelectorAll(":enabled").length&&v.push(":enabled",":disabled"),a.appendChild(e).disabled=!0,2!==e.querySelectorAll(":disabled").length&&v.push(":enabled",":disabled"),e.querySelectorAll("*,:x"),v.push(",.*:")})),(d.matchesSelector=K.test(c=a.matches||a.webkitMatchesSelector||a.mozMatchesSelector||a.oMatchesSelector||a.msMatchesSelector))&&ce(function(e){d.disconnectedMatch=c.call(e,"*"),c.call(e,"[s!='']:x"),s.push("!=",F)}),v=v.length&&new RegExp(v.join("|")),s=s.length&&new RegExp(s.join("|")),t=K.test(a.compareDocumentPosition),y=t||K.test(a.contains)?function(e,t){var n=9===e.nodeType?e.documentElement:e,r=t&&t.parentNode;return e===r||!(!r||1!==r.nodeType||!(n.contains?n.contains(r):e.compareDocumentPosition&&16&e.compareDocumentPosition(r)))}:function(e,t){if(t)while(t=t.parentNode)if(t===e)return!0;return!1},j=t?function(e,t){if(e===t)return l=!0,0;var n=!e.compareDocumentPosition-!t.compareDocumentPosition;return n||(1&(n=(e.ownerDocument||e)==(t.ownerDocument||t)?e.compareDocumentPosition(t):1)||!d.sortDetached&&t.compareDocumentPosition(e)===n?e==C||e.ownerDocument==p&&y(p,e)?-1:t==C||t.ownerDocument==p&&y(p,t)?1:u?P(u,e)-P(u,t):0:4&n?-1:1)}:function(e,t){if(e===t)return l=!0,0;var n,r=0,i=e.parentNode,o=t.parentNode,a=[e],s=[t];if(!i||!o)return e==C?-1:t==C?1:i?-1:o?1:u?P(u,e)-P(u,t):0;if(i===o)return pe(e,t);n=e;while(n=n.parentNode)a.unshift(n);n=t;while(n=n.parentNode)s.unshift(n);while(a[r]===s[r])r++;return r?pe(a[r],s[r]):a[r]==p?-1:s[r]==p?1:0}),C},se.matches=function(e,t){return se(e,null,null,t)},se.matchesSelector=function(e,t){if(T(e),d.matchesSelector&&E&&!N[t+" "]&&(!s||!s.test(t))&&(!v||!v.test(t)))try{var n=c.call(e,t);if(n||d.disconnectedMatch||e.document&&11!==e.document.nodeType)return n}catch(e){N(t,!0)}return 0<se(t,C,null,[e]).length},se.contains=function(e,t){return(e.ownerDocument||e)!=C&&T(e),y(e,t)},se.attr=function(e,t){(e.ownerDocument||e)!=C&&T(e);var n=b.attrHandle[t.toLowerCase()],r=n&&D.call(b.attrHandle,t.toLowerCase())?n(e,t,!E):void 0;return void 0!==r?r:d.attributes||!E?e.getAttribute(t):(r=e.getAttributeNode(t))&&r.specified?r.value:null},se.escape=function(e){return(e+"").replace(re,ie)},se.error=function(e){throw new Error("Syntax error, unrecognized expression: "+e)},se.uniqueSort=function(e){var t,n=[],r=0,i=0;if(l=!d.detectDuplicates,u=!d.sortStable&&e.slice(0),e.sort(j),l){while(t=e[i++])t===e[i]&&(r=n.push(i));while(r--)e.splice(n[r],1)}return u=null,e},o=se.getText=function(e){var t,n="",r=0,i=e.nodeType;if(i){if(1===i||9===i||11===i){if("string"==typeof e.textContent)return e.textContent;for(e=e.firstChild;e;e=e.nextSibling)n+=o(e)}else if(3===i||4===i)return e.nodeValue}else while(t=e[r++])n+=o(t);return n},(b=se.selectors={cacheLength:50,createPseudo:le,match:G,attrHandle:{},find:{},relative:{">":{dir:"parentNode",first:!0}," ":{dir:"parentNode"},"+":{dir:"previousSibling",first:!0},"~":{dir:"previousSibling"}},preFilter:{ATTR:function(e){return e[1]=e[1].replace(te,ne),e[3]=(e[3]||e[4]||e[5]||"").replace(te,ne),"~="===e[2]&&(e[3]=" "+e[3]+" "),e.slice(0,4)},CHILD:function(e){return e[1]=e[1].toLowerCase(),"nth"===e[1].slice(0,3)?(e[3]||se.error(e[0]),e[4]=+(e[4]?e[5]+(e[6]||1):2*("even"===e[3]||"odd"===e[3])),e[5]=+(e[7]+e[8]||"odd"===e[3])):e[3]&&se.error(e[0]),e},PSEUDO:function(e){var t,n=!e[6]&&e[2];return G.CHILD.test(e[0])?null:(e[3]?e[2]=e[4]||e[5]||"":n&&X.test(n)&&(t=h(n,!0))&&(t=n.indexOf(")",n.length-t)-n.length)&&(e[0]=e[0].slice(0,t),e[2]=n.slice(0,t)),e.slice(0,3))}},filter:{TAG:function(e){var t=e.replace(te,ne).toLowerCase();return"*"===e?function(){return!0}:function(e){return e.nodeName&&e.nodeName.toLowerCase()===t}},CLASS:function(e){var t=m[e+" "];return t||(t=new RegExp("(^|"+M+")"+e+"("+M+"|$)"))&&m(e,function(e){return t.test("string"==typeof e.className&&e.className||"undefined"!=typeof e.getAttribute&&e.getAttribute("class")||"")})},ATTR:function(n,r,i){return function(e){var t=se.attr(e,n);return null==t?"!="===r:!r||(t+="","="===r?t===i:"!="===r?t!==i:"^="===r?i&&0===t.indexOf(i):"*="===r?i&&-1<t.indexOf(i):"$="===r?i&&t.slice(-i.length)===i:"~="===r?-1<(" "+t.replace(B," ")+" ").indexOf(i):"|="===r&&(t===i||t.slice(0,i.length+1)===i+"-"))}},CHILD:function(h,e,t,g,v){var y="nth"!==h.slice(0,3),m="last"!==h.slice(-4),x="of-type"===e;return 1===g&&0===v?function(e){return!!e.parentNode}:function(e,t,n){var r,i,o,a,s,u,l=y!==m?"nextSibling":"previousSibling",c=e.parentNode,f=x&&e.nodeName.toLowerCase(),p=!n&&!x,d=!1;if(c){if(y){while(l){a=e;while(a=a[l])if(x?a.nodeName.toLowerCase()===f:1===a.nodeType)return!1;u=l="only"===h&&!u&&"nextSibling"}return!0}if(u=[m?c.firstChild:c.lastChild],m&&p){d=(s=(r=(i=(o=(a=c)[S]||(a[S]={}))[a.uniqueID]||(o[a.uniqueID]={}))[h]||[])[0]===k&&r[1])&&r[2],a=s&&c.childNodes[s];while(a=++s&&a&&a[l]||(d=s=0)||u.pop())if(1===a.nodeType&&++d&&a===e){i[h]=[k,s,d];break}}else if(p&&(d=s=(r=(i=(o=(a=e)[S]||(a[S]={}))[a.uniqueID]||(o[a.uniqueID]={}))[h]||[])[0]===k&&r[1]),!1===d)while(a=++s&&a&&a[l]||(d=s=0)||u.pop())if((x?a.nodeName.toLowerCase()===f:1===a.nodeType)&&++d&&(p&&((i=(o=a[S]||(a[S]={}))[a.uniqueID]||(o[a.uniqueID]={}))[h]=[k,d]),a===e))break;return(d-=v)===g||d%g==0&&0<=d/g}}},PSEUDO:function(e,o){var t,a=b.pseudos[e]||b.setFilters[e.toLowerCase()]||se.error("unsupported pseudo: "+e);return a[S]?a(o):1<a.length?(t=[e,e,"",o],b.setFilters.hasOwnProperty(e.toLowerCase())?le(function(e,t){var n,r=a(e,o),i=r.length;while(i--)e[n=P(e,r[i])]=!(t[n]=r[i])}):function(e){return a(e,0,t)}):a}},pseudos:{not:le(function(e){var r=[],i=[],s=f(e.replace($,"$1"));return s[S]?le(function(e,t,n,r){var i,o=s(e,null,r,[]),a=e.length;while(a--)(i=o[a])&&(e[a]=!(t[a]=i))}):function(e,t,n){return r[0]=e,s(r,null,n,i),r[0]=null,!i.pop()}}),has:le(function(t){return function(e){return 0<se(t,e).length}}),contains:le(function(t){return t=t.replace(te,ne),function(e){return-1<(e.textContent||o(e)).indexOf(t)}}),lang:le(function(n){return V.test(n||"")||se.error("unsupported lang: "+n),n=n.replace(te,ne).toLowerCase(),function(e){var t;do{if(t=E?e.lang:e.getAttribute("xml:lang")||e.getAttribute("lang"))return(t=t.toLowerCase())===n||0===t.indexOf(n+"-")}while((e=e.parentNode)&&1===e.nodeType);return!1}}),target:function(e){var t=n.location&&n.location.hash;return t&&t.slice(1)===e.id},root:function(e){return e===a},focus:function(e){return e===C.activeElement&&(!C.hasFocus||C.hasFocus())&&!!(e.type||e.href||~e.tabIndex)},enabled:ge(!1),disabled:ge(!0),checked:function(e){var t=e.nodeName.toLowerCase();return"input"===t&&!!e.checked||"option"===t&&!!e.selected},selected:function(e){return e.parentNode&&e.parentNode.selectedIndex,!0===e.selected},empty:function(e){for(e=e.firstChild;e;e=e.nextSibling)if(e.nodeType<6)return!1;return!0},parent:function(e){return!b.pseudos.empty(e)},header:function(e){return J.test(e.nodeName)},input:function(e){return Q.test(e.nodeName)},button:function(e){var t=e.nodeName.toLowerCase();return"input"===t&&"button"===e.type||"button"===t},text:function(e){var t;return"input"===e.nodeName.toLowerCase()&&"text"===e.type&&(null==(t=e.getAttribute("type"))||"text"===t.toLowerCase())},first:ve(function(){return[0]}),last:ve(function(e,t){return[t-1]}),eq:ve(function(e,t,n){return[n<0?n+t:n]}),even:ve(function(e,t){for(var n=0;n<t;n+=2)e.push(n);return e}),odd:ve(function(e,t){for(var n=1;n<t;n+=2)e.push(n);return e}),lt:ve(function(e,t,n){for(var r=n<0?n+t:t<n?t:n;0<=--r;)e.push(r);return e}),gt:ve(function(e,t,n){for(var r=n<0?n+t:n;++r<t;)e.push(r);return e})}}).pseudos.nth=b.pseudos.eq,{radio:!0,checkbox:!0,file:!0,password:!0,image:!0})b.pseudos[e]=de(e);for(e in{submit:!0,reset:!0})b.pseudos[e]=he(e);function me(){}function xe(e){for(var t=0,n=e.length,r="";t<n;t++)r+=e[t].value;return r}function be(s,e,t){var u=e.dir,l=e.next,c=l||u,f=t&&"parentNode"===c,p=r++;return e.first?function(e,t,n){while(e=e[u])if(1===e.nodeType||f)return s(e,t,n);return!1}:function(e,t,n){var r,i,o,a=[k,p];if(n){while(e=e[u])if((1===e.nodeType||f)&&s(e,t,n))return!0}else while(e=e[u])if(1===e.nodeType||f)if(i=(o=e[S]||(e[S]={}))[e.uniqueID]||(o[e.uniqueID]={}),l&&l===e.nodeName.toLowerCase())e=e[u]||e;else{if((r=i[c])&&r[0]===k&&r[1]===p)return a[2]=r[2];if((i[c]=a)[2]=s(e,t,n))return!0}return!1}}function we(i){return 1<i.length?function(e,t,n){var r=i.length;while(r--)if(!i[r](e,t,n))return!1;return!0}:i[0]}function Te(e,t,n,r,i){for(var o,a=[],s=0,u=e.length,l=null!=t;s<u;s++)(o=e[s])&&(n&&!n(o,r,i)||(a.push(o),l&&t.push(s)));return a}function Ce(d,h,g,v,y,e){return v&&!v[S]&&(v=Ce(v)),y&&!y[S]&&(y=Ce(y,e)),le(function(e,t,n,r){var i,o,a,s=[],u=[],l=t.length,c=e||function(e,t,n){for(var r=0,i=t.length;r<i;r++)se(e,t[r],n);return n}(h||"*",n.nodeType?[n]:n,[]),f=!d||!e&&h?c:Te(c,s,d,n,r),p=g?y||(e?d:l||v)?[]:t:f;if(g&&g(f,p,n,r),v){i=Te(p,u),v(i,[],n,r),o=i.length;while(o--)(a=i[o])&&(p[u[o]]=!(f[u[o]]=a))}if(e){if(y||d){if(y){i=[],o=p.length;while(o--)(a=p[o])&&i.push(f[o]=a);y(null,p=[],i,r)}o=p.length;while(o--)(a=p[o])&&-1<(i=y?P(e,a):s[o])&&(e[i]=!(t[i]=a))}}else p=Te(p===t?p.splice(l,p.length):p),y?y(null,t,p,r):H.apply(t,p)})}function Ee(e){for(var i,t,n,r=e.length,o=b.relative[e[0].type],a=o||b.relative[" "],s=o?1:0,u=be(function(e){return e===i},a,!0),l=be(function(e){return-1<P(i,e)},a,!0),c=[function(e,t,n){var r=!o&&(n||t!==w)||((i=t).nodeType?u(e,t,n):l(e,t,n));return i=null,r}];s<r;s++)if(t=b.relative[e[s].type])c=[be(we(c),t)];else{if((t=b.filter[e[s].type].apply(null,e[s].matches))[S]){for(n=++s;n<r;n++)if(b.relative[e[n].type])break;return Ce(1<s&&we(c),1<s&&xe(e.slice(0,s-1).concat({value:" "===e[s-2].type?"*":""})).replace($,"$1"),t,s<n&&Ee(e.slice(s,n)),n<r&&Ee(e=e.slice(n)),n<r&&xe(e))}c.push(t)}return we(c)}return me.prototype=b.filters=b.pseudos,b.setFilters=new me,h=se.tokenize=function(e,t){var n,r,i,o,a,s,u,l=x[e+" "];if(l)return t?0:l.slice(0);a=e,s=[],u=b.preFilter;while(a){for(o in n&&!(r=_.exec(a))||(r&&(a=a.slice(r[0].length)||a),s.push(i=[])),n=!1,(r=z.exec(a))&&(n=r.shift(),i.push({value:n,type:r[0].replace($," ")}),a=a.slice(n.length)),b.filter)!(r=G[o].exec(a))||u[o]&&!(r=u[o](r))||(n=r.shift(),i.push({value:n,type:o,matches:r}),a=a.slice(n.length));if(!n)break}return t?a.length:a?se.error(e):x(e,s).slice(0)},f=se.compile=function(e,t){var n,v,y,m,x,r,i=[],o=[],a=A[e+" "];if(!a){t||(t=h(e)),n=t.length;while(n--)(a=Ee(t[n]))[S]?i.push(a):o.push(a);(a=A(e,(v=o,m=0<(y=i).length,x=0<v.length,r=function(e,t,n,r,i){var o,a,s,u=0,l="0",c=e&&[],f=[],p=w,d=e||x&&b.find.TAG("*",i),h=k+=null==p?1:Math.random()||.1,g=d.length;for(i&&(w=t==C||t||i);l!==g&&null!=(o=d[l]);l++){if(x&&o){a=0,t||o.ownerDocument==C||(T(o),n=!E);while(s=v[a++])if(s(o,t||C,n)){r.push(o);break}i&&(k=h)}m&&((o=!s&&o)&&u--,e&&c.push(o))}if(u+=l,m&&l!==u){a=0;while(s=y[a++])s(c,f,t,n);if(e){if(0<u)while(l--)c[l]||f[l]||(f[l]=q.call(r));f=Te(f)}H.apply(r,f),i&&!e&&0<f.length&&1<u+y.length&&se.uniqueSort(r)}return i&&(k=h,w=p),c},m?le(r):r))).selector=e}return a},g=se.select=function(e,t,n,r){var i,o,a,s,u,l="function"==typeof e&&e,c=!r&&h(e=l.selector||e);if(n=n||[],1===c.length){if(2<(o=c[0]=c[0].slice(0)).length&&"ID"===(a=o[0]).type&&9===t.nodeType&&E&&b.relative[o[1].type]){if(!(t=(b.find.ID(a.matches[0].replace(te,ne),t)||[])[0]))return n;l&&(t=t.parentNode),e=e.slice(o.shift().value.length)}i=G.needsContext.test(e)?0:o.length;while(i--){if(a=o[i],b.relative[s=a.type])break;if((u=b.find[s])&&(r=u(a.matches[0].replace(te,ne),ee.test(o[0].type)&&ye(t.parentNode)||t))){if(o.splice(i,1),!(e=r.length&&xe(o)))return H.apply(n,r),n;break}}}return(l||f(e,c))(r,t,!E,n,!t||ee.test(e)&&ye(t.parentNode)||t),n},d.sortStable=S.split("").sort(j).join("")===S,d.detectDuplicates=!!l,T(),d.sortDetached=ce(function(e){return 1&e.compareDocumentPosition(C.createElement("fieldset"))}),ce(function(e){return e.innerHTML="<a href='#'></a>","#"===e.firstChild.getAttribute("href")})||fe("type|href|height|width",function(e,t,n){if(!n)return e.getAttribute(t,"type"===t.toLowerCase()?1:2)}),d.attributes&&ce(function(e){return e.innerHTML="<input/>",e.firstChild.setAttribute("value",""),""===e.firstChild.getAttribute("value")})||fe("value",function(e,t,n){if(!n&&"input"===e.nodeName.toLowerCase())return e.defaultValue}),ce(function(e){return null==e.getAttribute("disabled")})||fe(R,function(e,t,n){var r;if(!n)return!0===e[t]?t.toLowerCase():(r=e.getAttributeNode(t))&&r.specified?r.value:null}),se}(C);S.find=d,S.expr=d.selectors,S.expr[":"]=S.expr.pseudos,S.uniqueSort=S.unique=d.uniqueSort,S.text=d.getText,S.isXMLDoc=d.isXML,S.contains=d.contains,S.escapeSelector=d.escape;var h=function(e,t,n){var r=[],i=void 0!==n;while((e=e[t])&&9!==e.nodeType)if(1===e.nodeType){if(i&&S(e).is(n))break;r.push(e)}return r},T=function(e,t){for(var n=[];e;e=e.nextSibling)1===e.nodeType&&e!==t&&n.push(e);return n},k=S.expr.match.needsContext;function A(e,t){return e.nodeName&&e.nodeName.toLowerCase()===t.toLowerCase()}var N=/^<([a-z][^\/\0>:\x20\t\r\n\f]*)[\x20\t\r\n\f]*\/?>(?:<\/\1>|)$/i;function j(e,n,r){return m(n)?S.grep(e,function(e,t){return!!n.call(e,t,e)!==r}):n.nodeType?S.grep(e,function(e){return e===n!==r}):"string"!=typeof n?S.grep(e,function(e){return-1<i.call(n,e)!==r}):S.filter(n,e,r)}S.filter=function(e,t,n){var r=t[0];return n&&(e=":not("+e+")"),1===t.length&&1===r.nodeType?S.find.matchesSelector(r,e)?[r]:[]:S.find.matches(e,S.grep(t,function(e){return 1===e.nodeType}))},S.fn.extend({find:function(e){var t,n,r=this.length,i=this;if("string"!=typeof e)return this.pushStack(S(e).filter(function(){for(t=0;t<r;t++)if(S.contains(i[t],this))return!0}));for(n=this.pushStack([]),t=0;t<r;t++)S.find(e,i[t],n);return 1<r?S.uniqueSort(n):n},filter:function(e){return this.pushStack(j(this,e||[],!1))},not:function(e){return this.pushStack(j(this,e||[],!0))},is:function(e){return!!j(this,"string"==typeof e&&k.test(e)?S(e):e||[],!1).length}});var D,q=/^(?:\s*(<[\w\W]+>)[^>]*|#([\w-]+))$/;(S.fn.init=function(e,t,n){var r,i;if(!e)return this;if(n=n||D,"string"==typeof e){if(!(r="<"===e[0]&&">"===e[e.length-1]&&3<=e.length?[null,e,null]:q.exec(e))||!r[1]&&t)return!t||t.jquery?(t||n).find(e):this.constructor(t).find(e);if(r[1]){if(t=t instanceof S?t[0]:t,S.merge(this,S.parseHTML(r[1],t&&t.nodeType?t.ownerDocument||t:E,!0)),N.test(r[1])&&S.isPlainObject(t))for(r in t)m(this[r])?this[r](t[r]):this.attr(r,t[r]);return this}return(i=E.getElementById(r[2]))&&(this[0]=i,this.length=1),this}return e.nodeType?(this[0]=e,this.length=1,this):m(e)?void 0!==n.ready?n.ready(e):e(S):S.makeArray(e,this)}).prototype=S.fn,D=S(E);var L=/^(?:parents|prev(?:Until|All))/,H={children:!0,contents:!0,next:!0,prev:!0};function O(e,t){while((e=e[t])&&1!==e.nodeType);return e}S.fn.extend({has:function(e){var t=S(e,this),n=t.length;return this.filter(function(){for(var e=0;e<n;e++)if(S.contains(this,t[e]))return!0})},closest:function(e,t){var n,r=0,i=this.length,o=[],a="string"!=typeof e&&S(e);if(!k.test(e))for(;r<i;r++)for(n=this[r];n&&n!==t;n=n.parentNode)if(n.nodeType<11&&(a?-1<a.index(n):1===n.nodeType&&S.find.matchesSelector(n,e))){o.push(n);break}return this.pushStack(1<o.length?S.uniqueSort(o):o)},index:function(e){return e?"string"==typeof e?i.call(S(e),this[0]):i.call(this,e.jquery?e[0]:e):this[0]&&this[0].parentNode?this.first().prevAll().length:-1},add:function(e,t){return this.pushStack(S.uniqueSort(S.merge(this.get(),S(e,t))))},addBack:function(e){return this.add(null==e?this.prevObject:this.prevObject.filter(e))}}),S.each({parent:function(e){var t=e.parentNode;return t&&11!==t.nodeType?t:null},parents:function(e){return h(e,"parentNode")},parentsUntil:function(e,t,n){return h(e,"parentNode",n)},next:function(e){return O(e,"nextSibling")},prev:function(e){return O(e,"previousSibling")},nextAll:function(e){return h(e,"nextSibling")},prevAll:function(e){return h(e,"previousSibling")},nextUntil:function(e,t,n){return h(e,"nextSibling",n)},prevUntil:function(e,t,n){return h(e,"previousSibling",n)},siblings:function(e){return T((e.parentNode||{}).firstChild,e)},children:function(e){return T(e.firstChild)},contents:function(e){return null!=e.contentDocument&&r(e.contentDocument)?e.contentDocument:(A(e,"template")&&(e=e.content||e),S.merge([],e.childNodes))}},function(r,i){S.fn[r]=function(e,t){var n=S.map(this,i,e);return"Until"!==r.slice(-5)&&(t=e),t&&"string"==typeof t&&(n=S.filter(t,n)),1<this.length&&(H[r]||S.uniqueSort(n),L.test(r)&&n.reverse()),this.pushStack(n)}});var P=/[^\x20\t\r\n\f]+/g;function R(e){return e}function M(e){throw e}function I(e,t,n,r){var i;try{e&&m(i=e.promise)?i.call(e).done(t).fail(n):e&&m(i=e.then)?i.call(e,t,n):t.apply(void 0,[e].slice(r))}catch(e){n.apply(void 0,[e])}}S.Callbacks=function(r){var e,n;r="string"==typeof r?(e=r,n={},S.each(e.match(P)||[],function(e,t){n[t]=!0}),n):S.extend({},r);var i,t,o,a,s=[],u=[],l=-1,c=function(){for(a=a||r.once,o=i=!0;u.length;l=-1){t=u.shift();while(++l<s.length)!1===s[l].apply(t[0],t[1])&&r.stopOnFalse&&(l=s.length,t=!1)}r.memory||(t=!1),i=!1,a&&(s=t?[]:"")},f={add:function(){return s&&(t&&!i&&(l=s.length-1,u.push(t)),function n(e){S.each(e,function(e,t){m(t)?r.unique&&f.has(t)||s.push(t):t&&t.length&&"string"!==w(t)&&n(t)})}(arguments),t&&!i&&c()),this},remove:function(){return S.each(arguments,function(e,t){var n;while(-1<(n=S.inArray(t,s,n)))s.splice(n,1),n<=l&&l--}),this},has:function(e){return e?-1<S.inArray(e,s):0<s.length},empty:function(){return s&&(s=[]),this},disable:function(){return a=u=[],s=t="",this},disabled:function(){return!s},lock:function(){return a=u=[],t||i||(s=t=""),this},locked:function(){return!!a},fireWith:function(e,t){return a||(t=[e,(t=t||[]).slice?t.slice():t],u.push(t),i||c()),this},fire:function(){return f.fireWith(this,arguments),this},fired:function(){return!!o}};return f},S.extend({Deferred:function(e){var o=[["notify","progress",S.Callbacks("memory"),S.Callbacks("memory"),2],["resolve","done",S.Callbacks("once memory"),S.Callbacks("once memory"),0,"resolved"],["reject","fail",S.Callbacks("once memory"),S.Callbacks("once memory"),1,"rejected"]],i="pending",a={state:function(){return i},always:function(){return s.done(arguments).fail(arguments),this},"catch":function(e){return a.then(null,e)},pipe:function(){var i=arguments;return S.Deferred(function(r){S.each(o,function(e,t){var n=m(i[t[4]])&&i[t[4]];s[t[1]](function(){var e=n&&n.apply(this,arguments);e&&m(e.promise)?e.promise().progress(r.notify).done(r.resolve).fail(r.reject):r[t[0]+"With"](this,n?[e]:arguments)})}),i=null}).promise()},then:function(t,n,r){var u=0;function l(i,o,a,s){return function(){var n=this,r=arguments,e=function(){var e,t;if(!(i<u)){if((e=a.apply(n,r))===o.promise())throw new TypeError("Thenable self-resolution");t=e&&("object"==typeof e||"function"==typeof e)&&e.then,m(t)?s?t.call(e,l(u,o,R,s),l(u,o,M,s)):(u++,t.call(e,l(u,o,R,s),l(u,o,M,s),l(u,o,R,o.notifyWith))):(a!==R&&(n=void 0,r=[e]),(s||o.resolveWith)(n,r))}},t=s?e:function(){try{e()}catch(e){S.Deferred.exceptionHook&&S.Deferred.exceptionHook(e,t.stackTrace),u<=i+1&&(a!==M&&(n=void 0,r=[e]),o.rejectWith(n,r))}};i?t():(S.Deferred.getStackHook&&(t.stackTrace=S.Deferred.getStackHook()),C.setTimeout(t))}}return S.Deferred(function(e){o[0][3].add(l(0,e,m(r)?r:R,e.notifyWith)),o[1][3].add(l(0,e,m(t)?t:R)),o[2][3].add(l(0,e,m(n)?n:M))}).promise()},promise:function(e){return null!=e?S.extend(e,a):a}},s={};return S.each(o,function(e,t){var n=t[2],r=t[5];a[t[1]]=n.add,r&&n.add(function(){i=r},o[3-e][2].disable,o[3-e][3].disable,o[0][2].lock,o[0][3].lock),n.add(t[3].fire),s[t[0]]=function(){return s[t[0]+"With"](this===s?void 0:this,arguments),this},s[t[0]+"With"]=n.fireWith}),a.promise(s),e&&e.call(s,s),s},when:function(e){var n=arguments.length,t=n,r=Array(t),i=s.call(arguments),o=S.Deferred(),a=function(t){return function(e){r[t]=this,i[t]=1<arguments.length?s.call(arguments):e,--n||o.resolveWith(r,i)}};if(n<=1&&(I(e,o.done(a(t)).resolve,o.reject,!n),"pending"===o.state()||m(i[t]&&i[t].then)))return o.then();while(t--)I(i[t],a(t),o.reject);return o.promise()}});var W=/^(Eval|Internal|Range|Reference|Syntax|Type|URI)Error$/;S.Deferred.exceptionHook=function(e,t){C.console&&C.console.warn&&e&&W.test(e.name)&&C.console.warn("jQuery.Deferred exception: "+e.message,e.stack,t)},S.readyException=function(e){C.setTimeout(function(){throw e})};var F=S.Deferred();function B(){E.removeEventListener("DOMContentLoaded",B),C.removeEventListener("load",B),S.ready()}S.fn.ready=function(e){return F.then(e)["catch"](function(e){S.readyException(e)}),this},S.extend({isReady:!1,readyWait:1,ready:function(e){(!0===e?--S.readyWait:S.isReady)||(S.isReady=!0)!==e&&0<--S.readyWait||F.resolveWith(E,[S])}}),S.ready.then=F.then,"complete"===E.readyState||"loading"!==E.readyState&&!E.documentElement.doScroll?C.setTimeout(S.ready):(E.addEventListener("DOMContentLoaded",B),C.addEventListener("load",B));var $=function(e,t,n,r,i,o,a){var s=0,u=e.length,l=null==n;if("object"===w(n))for(s in i=!0,n)$(e,t,s,n[s],!0,o,a);else if(void 0!==r&&(i=!0,m(r)||(a=!0),l&&(a?(t.call(e,r),t=null):(l=t,t=function(e,t,n){return l.call(S(e),n)})),t))for(;s<u;s++)t(e[s],n,a?r:r.call(e[s],s,t(e[s],n)));return i?e:l?t.call(e):u?t(e[0],n):o},_=/^-ms-/,z=/-([a-z])/g;function U(e,t){return t.toUpperCase()}function X(e){return e.replace(_,"ms-").replace(z,U)}var V=function(e){return 1===e.nodeType||9===e.nodeType||!+e.nodeType};function G(){this.expando=S.expando+G.uid++}G.uid=1,G.prototype={cache:function(e){var t=e[this.expando];return t||(t={},V(e)&&(e.nodeType?e[this.expando]=t:Object.defineProperty(e,this.expando,{value:t,configurable:!0}))),t},set:function(e,t,n){var r,i=this.cache(e);if("string"==typeof t)i[X(t)]=n;else for(r in t)i[X(r)]=t[r];return i},get:function(e,t){return void 0===t?this.cache(e):e[this.expando]&&e[this.expando][X(t)]},access:function(e,t,n){return void 0===t||t&&"string"==typeof t&&void 0===n?this.get(e,t):(this.set(e,t,n),void 0!==n?n:t)},remove:function(e,t){var n,r=e[this.expando];if(void 0!==r){if(void 0!==t){n=(t=Array.isArray(t)?t.map(X):(t=X(t))in r?[t]:t.match(P)||[]).length;while(n--)delete r[t[n]]}(void 0===t||S.isEmptyObject(r))&&(e.nodeType?e[this.expando]=void 0:delete e[this.expando])}},hasData:function(e){var t=e[this.expando];return void 0!==t&&!S.isEmptyObject(t)}};var Y=new G,Q=new G,J=/^(?:\{[\w\W]*\}|\[[\w\W]*\])$/,K=/[A-Z]/g;function Z(e,t,n){var r,i;if(void 0===n&&1===e.nodeType)if(r="data-"+t.replace(K,"-$&").toLowerCase(),"string"==typeof(n=e.getAttribute(r))){try{n="true"===(i=n)||"false"!==i&&("null"===i?null:i===+i+""?+i:J.test(i)?JSON.parse(i):i)}catch(e){}Q.set(e,t,n)}else n=void 0;return n}S.extend({hasData:function(e){return Q.hasData(e)||Y.hasData(e)},data:function(e,t,n){return Q.access(e,t,n)},removeData:function(e,t){Q.remove(e,t)},_data:function(e,t,n){return Y.access(e,t,n)},_removeData:function(e,t){Y.remove(e,t)}}),S.fn.extend({data:function(n,e){var t,r,i,o=this[0],a=o&&o.attributes;if(void 0===n){if(this.length&&(i=Q.get(o),1===o.nodeType&&!Y.get(o,"hasDataAttrs"))){t=a.length;while(t--)a[t]&&0===(r=a[t].name).indexOf("data-")&&(r=X(r.slice(5)),Z(o,r,i[r]));Y.set(o,"hasDataAttrs",!0)}return i}return"object"==typeof n?this.each(function(){Q.set(this,n)}):$(this,function(e){var t;if(o&&void 0===e)return void 0!==(t=Q.get(o,n))?t:void 0!==(t=Z(o,n))?t:void 0;this.each(function(){Q.set(this,n,e)})},null,e,1<arguments.length,null,!0)},removeData:function(e){return this.each(function(){Q.remove(this,e)})}}),S.extend({queue:function(e,t,n){var r;if(e)return t=(t||"fx")+"queue",r=Y.get(e,t),n&&(!r||Array.isArray(n)?r=Y.access(e,t,S.makeArray(n)):r.push(n)),r||[]},dequeue:function(e,t){t=t||"fx";var n=S.queue(e,t),r=n.length,i=n.shift(),o=S._queueHooks(e,t);"inprogress"===i&&(i=n.shift(),r--),i&&("fx"===t&&n.unshift("inprogress"),delete o.stop,i.call(e,function(){S.dequeue(e,t)},o)),!r&&o&&o.empty.fire()},_queueHooks:function(e,t){var n=t+"queueHooks";return Y.get(e,n)||Y.access(e,n,{empty:S.Callbacks("once memory").add(function(){Y.remove(e,[t+"queue",n])})})}}),S.fn.extend({queue:function(t,n){var e=2;return"string"!=typeof t&&(n=t,t="fx",e--),arguments.length<e?S.queue(this[0],t):void 0===n?this:this.each(function(){var e=S.queue(this,t,n);S._queueHooks(this,t),"fx"===t&&"inprogress"!==e[0]&&S.dequeue(this,t)})},dequeue:function(e){return this.each(function(){S.dequeue(this,e)})},clearQueue:function(e){return this.queue(e||"fx",[])},promise:function(e,t){var n,r=1,i=S.Deferred(),o=this,a=this.length,s=function(){--r||i.resolveWith(o,[o])};"string"!=typeof e&&(t=e,e=void 0),e=e||"fx";while(a--)(n=Y.get(o[a],e+"queueHooks"))&&n.empty&&(r++,n.empty.add(s));return s(),i.promise(t)}});var ee=/[+-]?(?:\d*\.|)\d+(?:[eE][+-]?\d+|)/.source,te=new RegExp("^(?:([+-])=|)("+ee+")([a-z%]*)$","i"),ne=["Top","Right","Bottom","Left"],re=E.documentElement,ie=function(e){return S.contains(e.ownerDocument,e)},oe={composed:!0};re.getRootNode&&(ie=function(e){return S.contains(e.ownerDocument,e)||e.getRootNode(oe)===e.ownerDocument});var ae=function(e,t){return"none"===(e=t||e).style.display||""===e.style.display&&ie(e)&&"none"===S.css(e,"display")};function se(e,t,n,r){var i,o,a=20,s=r?function(){return r.cur()}:function(){return S.css(e,t,"")},u=s(),l=n&&n[3]||(S.cssNumber[t]?"":"px"),c=e.nodeType&&(S.cssNumber[t]||"px"!==l&&+u)&&te.exec(S.css(e,t));if(c&&c[3]!==l){u/=2,l=l||c[3],c=+u||1;while(a--)S.style(e,t,c+l),(1-o)*(1-(o=s()/u||.5))<=0&&(a=0),c/=o;c*=2,S.style(e,t,c+l),n=n||[]}return n&&(c=+c||+u||0,i=n[1]?c+(n[1]+1)*n[2]:+n[2],r&&(r.unit=l,r.start=c,r.end=i)),i}var ue={};function le(e,t){for(var n,r,i,o,a,s,u,l=[],c=0,f=e.length;c<f;c++)(r=e[c]).style&&(n=r.style.display,t?("none"===n&&(l[c]=Y.get(r,"display")||null,l[c]||(r.style.display="")),""===r.style.display&&ae(r)&&(l[c]=(u=a=o=void 0,a=(i=r).ownerDocument,s=i.nodeName,(u=ue[s])||(o=a.body.appendChild(a.createElement(s)),u=S.css(o,"display"),o.parentNode.removeChild(o),"none"===u&&(u="block"),ue[s]=u)))):"none"!==n&&(l[c]="none",Y.set(r,"display",n)));for(c=0;c<f;c++)null!=l[c]&&(e[c].style.display=l[c]);return e}S.fn.extend({show:function(){return le(this,!0)},hide:function(){return le(this)},toggle:function(e){return"boolean"==typeof e?e?this.show():this.hide():this.each(function(){ae(this)?S(this).show():S(this).hide()})}});var ce,fe,pe=/^(?:checkbox|radio)$/i,de=/<([a-z][^\/\0>\x20\t\r\n\f]*)/i,he=/^$|^module$|\/(?:java|ecma)script/i;ce=E.createDocumentFragment().appendChild(E.createElement("div")),(fe=E.createElement("input")).setAttribute("type","radio"),fe.setAttribute("checked","checked"),fe.setAttribute("name","t"),ce.appendChild(fe),y.checkClone=ce.cloneNode(!0).cloneNode(!0).lastChild.checked,ce.innerHTML="<textarea>x</textarea>",y.noCloneChecked=!!ce.cloneNode(!0).lastChild.defaultValue,ce.innerHTML="<option></option>",y.option=!!ce.lastChild;var ge={thead:[1,"<table>","</table>"],col:[2,"<table><colgroup>","</colgroup></table>"],tr:[2,"<table><tbody>","</tbody></table>"],td:[3,"<table><tbody><tr>","</tr></tbody></table>"],_default:[0,"",""]};function ve(e,t){var n;return n="undefined"!=typeof e.getElementsByTagName?e.getElementsByTagName(t||"*"):"undefined"!=typeof e.querySelectorAll?e.querySelectorAll(t||"*"):[],void 0===t||t&&A(e,t)?S.merge([e],n):n}function ye(e,t){for(var n=0,r=e.length;n<r;n++)Y.set(e[n],"globalEval",!t||Y.get(t[n],"globalEval"))}ge.tbody=ge.tfoot=ge.colgroup=ge.caption=ge.thead,ge.th=ge.td,y.option||(ge.optgroup=ge.option=[1,"<select multiple='multiple'>","</select>"]);var me=/<|&#?\w+;/;function xe(e,t,n,r,i){for(var o,a,s,u,l,c,f=t.createDocumentFragment(),p=[],d=0,h=e.length;d<h;d++)if((o=e[d])||0===o)if("object"===w(o))S.merge(p,o.nodeType?[o]:o);else if(me.test(o)){a=a||f.appendChild(t.createElement("div")),s=(de.exec(o)||["",""])[1].toLowerCase(),u=ge[s]||ge._default,a.innerHTML=u[1]+S.htmlPrefilter(o)+u[2],c=u[0];while(c--)a=a.lastChild;S.merge(p,a.childNodes),(a=f.firstChild).textContent=""}else p.push(t.createTextNode(o));f.textContent="",d=0;while(o=p[d++])if(r&&-1<S.inArray(o,r))i&&i.push(o);else if(l=ie(o),a=ve(f.appendChild(o),"script"),l&&ye(a),n){c=0;while(o=a[c++])he.test(o.type||"")&&n.push(o)}return f}var be=/^([^.]*)(?:\.(.+)|)/;function we(){return!0}function Te(){return!1}function Ce(e,t){return e===function(){try{return E.activeElement}catch(e){}}()==("focus"===t)}function Ee(e,t,n,r,i,o){var a,s;if("object"==typeof t){for(s in"string"!=typeof n&&(r=r||n,n=void 0),t)Ee(e,s,n,r,t[s],o);return e}if(null==r&&null==i?(i=n,r=n=void 0):null==i&&("string"==typeof n?(i=r,r=void 0):(i=r,r=n,n=void 0)),!1===i)i=Te;else if(!i)return e;return 1===o&&(a=i,(i=function(e){return S().off(e),a.apply(this,arguments)}).guid=a.guid||(a.guid=S.guid++)),e.each(function(){S.event.add(this,t,i,r,n)})}function Se(e,i,o){o?(Y.set(e,i,!1),S.event.add(e,i,{namespace:!1,handler:function(e){var t,n,r=Y.get(this,i);if(1&e.isTrigger&&this[i]){if(r.length)(S.event.special[i]||{}).delegateType&&e.stopPropagation();else if(r=s.call(arguments),Y.set(this,i,r),t=o(this,i),this[i](),r!==(n=Y.get(this,i))||t?Y.set(this,i,!1):n={},r!==n)return e.stopImmediatePropagation(),e.preventDefault(),n&&n.value}else r.length&&(Y.set(this,i,{value:S.event.trigger(S.extend(r[0],S.Event.prototype),r.slice(1),this)}),e.stopImmediatePropagation())}})):void 0===Y.get(e,i)&&S.event.add(e,i,we)}S.event={global:{},add:function(t,e,n,r,i){var o,a,s,u,l,c,f,p,d,h,g,v=Y.get(t);if(V(t)){n.handler&&(n=(o=n).handler,i=o.selector),i&&S.find.matchesSelector(re,i),n.guid||(n.guid=S.guid++),(u=v.events)||(u=v.events=Object.create(null)),(a=v.handle)||(a=v.handle=function(e){return"undefined"!=typeof S&&S.event.triggered!==e.type?S.event.dispatch.apply(t,arguments):void 0}),l=(e=(e||"").match(P)||[""]).length;while(l--)d=g=(s=be.exec(e[l])||[])[1],h=(s[2]||"").split(".").sort(),d&&(f=S.event.special[d]||{},d=(i?f.delegateType:f.bindType)||d,f=S.event.special[d]||{},c=S.extend({type:d,origType:g,data:r,handler:n,guid:n.guid,selector:i,needsContext:i&&S.expr.match.needsContext.test(i),namespace:h.join(".")},o),(p=u[d])||((p=u[d]=[]).delegateCount=0,f.setup&&!1!==f.setup.call(t,r,h,a)||t.addEventListener&&t.addEventListener(d,a)),f.add&&(f.add.call(t,c),c.handler.guid||(c.handler.guid=n.guid)),i?p.splice(p.delegateCount++,0,c):p.push(c),S.event.global[d]=!0)}},remove:function(e,t,n,r,i){var o,a,s,u,l,c,f,p,d,h,g,v=Y.hasData(e)&&Y.get(e);if(v&&(u=v.events)){l=(t=(t||"").match(P)||[""]).length;while(l--)if(d=g=(s=be.exec(t[l])||[])[1],h=(s[2]||"").split(".").sort(),d){f=S.event.special[d]||{},p=u[d=(r?f.delegateType:f.bindType)||d]||[],s=s[2]&&new RegExp("(^|\\.)"+h.join("\\.(?:.*\\.|)")+"(\\.|$)"),a=o=p.length;while(o--)c=p[o],!i&&g!==c.origType||n&&n.guid!==c.guid||s&&!s.test(c.namespace)||r&&r!==c.selector&&("**"!==r||!c.selector)||(p.splice(o,1),c.selector&&p.delegateCount--,f.remove&&f.remove.call(e,c));a&&!p.length&&(f.teardown&&!1!==f.teardown.call(e,h,v.handle)||S.removeEvent(e,d,v.handle),delete u[d])}else for(d in u)S.event.remove(e,d+t[l],n,r,!0);S.isEmptyObject(u)&&Y.remove(e,"handle events")}},dispatch:function(e){var t,n,r,i,o,a,s=new Array(arguments.length),u=S.event.fix(e),l=(Y.get(this,"events")||Object.create(null))[u.type]||[],c=S.event.special[u.type]||{};for(s[0]=u,t=1;t<arguments.length;t++)s[t]=arguments[t];if(u.delegateTarget=this,!c.preDispatch||!1!==c.preDispatch.call(this,u)){a=S.event.handlers.call(this,u,l),t=0;while((i=a[t++])&&!u.isPropagationStopped()){u.currentTarget=i.elem,n=0;while((o=i.handlers[n++])&&!u.isImmediatePropagationStopped())u.rnamespace&&!1!==o.namespace&&!u.rnamespace.test(o.namespace)||(u.handleObj=o,u.data=o.data,void 0!==(r=((S.event.special[o.origType]||{}).handle||o.handler).apply(i.elem,s))&&!1===(u.result=r)&&(u.preventDefault(),u.stopPropagation()))}return c.postDispatch&&c.postDispatch.call(this,u),u.result}},handlers:function(e,t){var n,r,i,o,a,s=[],u=t.delegateCount,l=e.target;if(u&&l.nodeType&&!("click"===e.type&&1<=e.button))for(;l!==this;l=l.parentNode||this)if(1===l.nodeType&&("click"!==e.type||!0!==l.disabled)){for(o=[],a={},n=0;n<u;n++)void 0===a[i=(r=t[n]).selector+" "]&&(a[i]=r.needsContext?-1<S(i,this).index(l):S.find(i,this,null,[l]).length),a[i]&&o.push(r);o.length&&s.push({elem:l,handlers:o})}return l=this,u<t.length&&s.push({elem:l,handlers:t.slice(u)}),s},addProp:function(t,e){Object.defineProperty(S.Event.prototype,t,{enumerable:!0,configurable:!0,get:m(e)?function(){if(this.originalEvent)return e(this.originalEvent)}:function(){if(this.originalEvent)return this.originalEvent[t]},set:function(e){Object.defineProperty(this,t,{enumerable:!0,configurable:!0,writable:!0,value:e})}})},fix:function(e){return e[S.expando]?e:new S.Event(e)},special:{load:{noBubble:!0},click:{setup:function(e){var t=this||e;return pe.test(t.type)&&t.click&&A(t,"input")&&Se(t,"click",we),!1},trigger:function(e){var t=this||e;return pe.test(t.type)&&t.click&&A(t,"input")&&Se(t,"click"),!0},_default:function(e){var t=e.target;return pe.test(t.type)&&t.click&&A(t,"input")&&Y.get(t,"click")||A(t,"a")}},beforeunload:{postDispatch:function(e){void 0!==e.result&&e.originalEvent&&(e.originalEvent.returnValue=e.result)}}}},S.removeEvent=function(e,t,n){e.removeEventListener&&e.removeEventListener(t,n)},S.Event=function(e,t){if(!(this instanceof S.Event))return new S.Event(e,t);e&&e.type?(this.originalEvent=e,this.type=e.type,this.isDefaultPrevented=e.defaultPrevented||void 0===e.defaultPrevented&&!1===e.returnValue?we:Te,this.target=e.target&&3===e.target.nodeType?e.target.parentNode:e.target,this.currentTarget=e.currentTarget,this.relatedTarget=e.relatedTarget):this.type=e,t&&S.extend(this,t),this.timeStamp=e&&e.timeStamp||Date.now(),this[S.expando]=!0},S.Event.prototype={constructor:S.Event,isDefaultPrevented:Te,isPropagationStopped:Te,isImmediatePropagationStopped:Te,isSimulated:!1,preventDefault:function(){var e=this.originalEvent;this.isDefaultPrevented=we,e&&!this.isSimulated&&e.preventDefault()},stopPropagation:function(){var e=this.originalEvent;this.isPropagationStopped=we,e&&!this.isSimulated&&e.stopPropagation()},stopImmediatePropagation:function(){var e=this.originalEvent;this.isImmediatePropagationStopped=we,e&&!this.isSimulated&&e.stopImmediatePropagation(),this.stopPropagation()}},S.each({altKey:!0,bubbles:!0,cancelable:!0,changedTouches:!0,ctrlKey:!0,detail:!0,eventPhase:!0,metaKey:!0,pageX:!0,pageY:!0,shiftKey:!0,view:!0,"char":!0,code:!0,charCode:!0,key:!0,keyCode:!0,button:!0,buttons:!0,clientX:!0,clientY:!0,offsetX:!0,offsetY:!0,pointerId:!0,pointerType:!0,screenX:!0,screenY:!0,targetTouches:!0,toElement:!0,touches:!0,which:!0},S.event.addProp),S.each({focus:"focusin",blur:"focusout"},function(e,t){S.event.special[e]={setup:function(){return Se(this,e,Ce),!1},trigger:function(){return Se(this,e),!0},_default:function(){return!0},delegateType:t}}),S.each({mouseenter:"mouseover",mouseleave:"mouseout",pointerenter:"pointerover",pointerleave:"pointerout"},function(e,i){S.event.special[e]={delegateType:i,bindType:i,handle:function(e){var t,n=e.relatedTarget,r=e.handleObj;return n&&(n===this||S.contains(this,n))||(e.type=r.origType,t=r.handler.apply(this,arguments),e.type=i),t}}}),S.fn.extend({on:function(e,t,n,r){return Ee(this,e,t,n,r)},one:function(e,t,n,r){return Ee(this,e,t,n,r,1)},off:function(e,t,n){var r,i;if(e&&e.preventDefault&&e.handleObj)return r=e.handleObj,S(e.delegateTarget).off(r.namespace?r.origType+"."+r.namespace:r.origType,r.selector,r.handler),this;if("object"==typeof e){for(i in e)this.off(i,t,e[i]);return this}return!1!==t&&"function"!=typeof t||(n=t,t=void 0),!1===n&&(n=Te),this.each(function(){S.event.remove(this,e,n,t)})}});var ke=/<script|<style|<link/i,Ae=/checked\s*(?:[^=]|=\s*.checked.)/i,Ne=/^\s*<!(?:\[CDATA\[|--)|(?:\]\]|--)>\s*$/g;function je(e,t){return A(e,"table")&&A(11!==t.nodeType?t:t.firstChild,"tr")&&S(e).children("tbody")[0]||e}function De(e){return e.type=(null!==e.getAttribute("type"))+"/"+e.type,e}function qe(e){return"true/"===(e.type||"").slice(0,5)?e.type=e.type.slice(5):e.removeAttribute("type"),e}function Le(e,t){var n,r,i,o,a,s;if(1===t.nodeType){if(Y.hasData(e)&&(s=Y.get(e).events))for(i in Y.remove(t,"handle events"),s)for(n=0,r=s[i].length;n<r;n++)S.event.add(t,i,s[i][n]);Q.hasData(e)&&(o=Q.access(e),a=S.extend({},o),Q.set(t,a))}}function He(n,r,i,o){r=g(r);var e,t,a,s,u,l,c=0,f=n.length,p=f-1,d=r[0],h=m(d);if(h||1<f&&"string"==typeof d&&!y.checkClone&&Ae.test(d))return n.each(function(e){var t=n.eq(e);h&&(r[0]=d.call(this,e,t.html())),He(t,r,i,o)});if(f&&(t=(e=xe(r,n[0].ownerDocument,!1,n,o)).firstChild,1===e.childNodes.length&&(e=t),t||o)){for(s=(a=S.map(ve(e,"script"),De)).length;c<f;c++)u=e,c!==p&&(u=S.clone(u,!0,!0),s&&S.merge(a,ve(u,"script"))),i.call(n[c],u,c);if(s)for(l=a[a.length-1].ownerDocument,S.map(a,qe),c=0;c<s;c++)u=a[c],he.test(u.type||"")&&!Y.access(u,"globalEval")&&S.contains(l,u)&&(u.src&&"module"!==(u.type||"").toLowerCase()?S._evalUrl&&!u.noModule&&S._evalUrl(u.src,{nonce:u.nonce||u.getAttribute("nonce")},l):b(u.textContent.replace(Ne,""),u,l))}return n}function Oe(e,t,n){for(var r,i=t?S.filter(t,e):e,o=0;null!=(r=i[o]);o++)n||1!==r.nodeType||S.cleanData(ve(r)),r.parentNode&&(n&&ie(r)&&ye(ve(r,"script")),r.parentNode.removeChild(r));return e}S.extend({htmlPrefilter:function(e){return e},clone:function(e,t,n){var r,i,o,a,s,u,l,c=e.cloneNode(!0),f=ie(e);if(!(y.noCloneChecked||1!==e.nodeType&&11!==e.nodeType||S.isXMLDoc(e)))for(a=ve(c),r=0,i=(o=ve(e)).length;r<i;r++)s=o[r],u=a[r],void 0,"input"===(l=u.nodeName.toLowerCase())&&pe.test(s.type)?u.checked=s.checked:"input"!==l&&"textarea"!==l||(u.defaultValue=s.defaultValue);if(t)if(n)for(o=o||ve(e),a=a||ve(c),r=0,i=o.length;r<i;r++)Le(o[r],a[r]);else Le(e,c);return 0<(a=ve(c,"script")).length&&ye(a,!f&&ve(e,"script")),c},cleanData:function(e){for(var t,n,r,i=S.event.special,o=0;void 0!==(n=e[o]);o++)if(V(n)){if(t=n[Y.expando]){if(t.events)for(r in t.events)i[r]?S.event.remove(n,r):S.removeEvent(n,r,t.handle);n[Y.expando]=void 0}n[Q.expando]&&(n[Q.expando]=void 0)}}}),S.fn.extend({detach:function(e){return Oe(this,e,!0)},remove:function(e){return Oe(this,e)},text:function(e){return $(this,function(e){return void 0===e?S.text(this):this.empty().each(function(){1!==this.nodeType&&11!==this.nodeType&&9!==this.nodeType||(this.textContent=e)})},null,e,arguments.length)},append:function(){return He(this,arguments,function(e){1!==this.nodeType&&11!==this.nodeType&&9!==this.nodeType||je(this,e).appendChild(e)})},prepend:function(){return He(this,arguments,function(e){if(1===this.nodeType||11===this.nodeType||9===this.nodeType){var t=je(this,e);t.insertBefore(e,t.firstChild)}})},before:function(){return He(this,arguments,function(e){this.parentNode&&this.parentNode.insertBefore(e,this)})},after:function(){return He(this,arguments,function(e){this.parentNode&&this.parentNode.insertBefore(e,this.nextSibling)})},empty:function(){for(var e,t=0;null!=(e=this[t]);t++)1===e.nodeType&&(S.cleanData(ve(e,!1)),e.textContent="");return this},clone:function(e,t){return e=null!=e&&e,t=null==t?e:t,this.map(function(){return S.clone(this,e,t)})},html:function(e){return $(this,function(e){var t=this[0]||{},n=0,r=this.length;if(void 0===e&&1===t.nodeType)return t.innerHTML;if("string"==typeof e&&!ke.test(e)&&!ge[(de.exec(e)||["",""])[1].toLowerCase()]){e=S.htmlPrefilter(e);try{for(;n<r;n++)1===(t=this[n]||{}).nodeType&&(S.cleanData(ve(t,!1)),t.innerHTML=e);t=0}catch(e){}}t&&this.empty().append(e)},null,e,arguments.length)},replaceWith:function(){var n=[];return He(this,arguments,function(e){var t=this.parentNode;S.inArray(this,n)<0&&(S.cleanData(ve(this)),t&&t.replaceChild(e,this))},n)}}),S.each({appendTo:"append",prependTo:"prepend",insertBefore:"before",insertAfter:"after",replaceAll:"replaceWith"},function(e,a){S.fn[e]=function(e){for(var t,n=[],r=S(e),i=r.length-1,o=0;o<=i;o++)t=o===i?this:this.clone(!0),S(r[o])[a](t),u.apply(n,t.get());return this.pushStack(n)}});var Pe=new RegExp("^("+ee+")(?!px)[a-z%]+$","i"),Re=function(e){var t=e.ownerDocument.defaultView;return t&&t.opener||(t=C),t.getComputedStyle(e)},Me=function(e,t,n){var r,i,o={};for(i in t)o[i]=e.style[i],e.style[i]=t[i];for(i in r=n.call(e),t)e.style[i]=o[i];return r},Ie=new RegExp(ne.join("|"),"i");function We(e,t,n){var r,i,o,a,s=e.style;return(n=n||Re(e))&&(""!==(a=n.getPropertyValue(t)||n[t])||ie(e)||(a=S.style(e,t)),!y.pixelBoxStyles()&&Pe.test(a)&&Ie.test(t)&&(r=s.width,i=s.minWidth,o=s.maxWidth,s.minWidth=s.maxWidth=s.width=a,a=n.width,s.width=r,s.minWidth=i,s.maxWidth=o)),void 0!==a?a+"":a}function Fe(e,t){return{get:function(){if(!e())return(this.get=t).apply(this,arguments);delete this.get}}}!function(){function e(){if(l){u.style.cssText="position:absolute;left:-11111px;width:60px;margin-top:1px;padding:0;border:0",l.style.cssText="position:relative;display:block;box-sizing:border-box;overflow:scroll;margin:auto;border:1px;padding:1px;width:60%;top:1%",re.appendChild(u).appendChild(l);var e=C.getComputedStyle(l);n="1%"!==e.top,s=12===t(e.marginLeft),l.style.right="60%",o=36===t(e.right),r=36===t(e.width),l.style.position="absolute",i=12===t(l.offsetWidth/3),re.removeChild(u),l=null}}function t(e){return Math.round(parseFloat(e))}var n,r,i,o,a,s,u=E.createElement("div"),l=E.createElement("div");l.style&&(l.style.backgroundClip="content-box",l.cloneNode(!0).style.backgroundClip="",y.clearCloneStyle="content-box"===l.style.backgroundClip,S.extend(y,{boxSizingReliable:function(){return e(),r},pixelBoxStyles:function(){return e(),o},pixelPosition:function(){return e(),n},reliableMarginLeft:function(){return e(),s},scrollboxSize:function(){return e(),i},reliableTrDimensions:function(){var e,t,n,r;return null==a&&(e=E.createElement("table"),t=E.createElement("tr"),n=E.createElement("div"),e.style.cssText="position:absolute;left:-11111px;border-collapse:separate",t.style.cssText="border:1px solid",t.style.height="1px",n.style.height="9px",n.style.display="block",re.appendChild(e).appendChild(t).appendChild(n),r=C.getComputedStyle(t),a=parseInt(r.height,10)+parseInt(r.borderTopWidth,10)+parseInt(r.borderBottomWidth,10)===t.offsetHeight,re.removeChild(e)),a}}))}();var Be=["Webkit","Moz","ms"],$e=E.createElement("div").style,_e={};function ze(e){var t=S.cssProps[e]||_e[e];return t||(e in $e?e:_e[e]=function(e){var t=e[0].toUpperCase()+e.slice(1),n=Be.length;while(n--)if((e=Be[n]+t)in $e)return e}(e)||e)}var Ue=/^(none|table(?!-c[ea]).+)/,Xe=/^--/,Ve={position:"absolute",visibility:"hidden",display:"block"},Ge={letterSpacing:"0",fontWeight:"400"};function Ye(e,t,n){var r=te.exec(t);return r?Math.max(0,r[2]-(n||0))+(r[3]||"px"):t}function Qe(e,t,n,r,i,o){var a="width"===t?1:0,s=0,u=0;if(n===(r?"border":"content"))return 0;for(;a<4;a+=2)"margin"===n&&(u+=S.css(e,n+ne[a],!0,i)),r?("content"===n&&(u-=S.css(e,"padding"+ne[a],!0,i)),"margin"!==n&&(u-=S.css(e,"border"+ne[a]+"Width",!0,i))):(u+=S.css(e,"padding"+ne[a],!0,i),"padding"!==n?u+=S.css(e,"border"+ne[a]+"Width",!0,i):s+=S.css(e,"border"+ne[a]+"Width",!0,i));return!r&&0<=o&&(u+=Math.max(0,Math.ceil(e["offset"+t[0].toUpperCase()+t.slice(1)]-o-u-s-.5))||0),u}function Je(e,t,n){var r=Re(e),i=(!y.boxSizingReliable()||n)&&"border-box"===S.css(e,"boxSizing",!1,r),o=i,a=We(e,t,r),s="offset"+t[0].toUpperCase()+t.slice(1);if(Pe.test(a)){if(!n)return a;a="auto"}return(!y.boxSizingReliable()&&i||!y.reliableTrDimensions()&&A(e,"tr")||"auto"===a||!parseFloat(a)&&"inline"===S.css(e,"display",!1,r))&&e.getClientRects().length&&(i="border-box"===S.css(e,"boxSizing",!1,r),(o=s in e)&&(a=e[s])),(a=parseFloat(a)||0)+Qe(e,t,n||(i?"border":"content"),o,r,a)+"px"}function Ke(e,t,n,r,i){return new Ke.prototype.init(e,t,n,r,i)}S.extend({cssHooks:{opacity:{get:function(e,t){if(t){var n=We(e,"opacity");return""===n?"1":n}}}},cssNumber:{animationIterationCount:!0,columnCount:!0,fillOpacity:!0,flexGrow:!0,flexShrink:!0,fontWeight:!0,gridArea:!0,gridColumn:!0,gridColumnEnd:!0,gridColumnStart:!0,gridRow:!0,gridRowEnd:!0,gridRowStart:!0,lineHeight:!0,opacity:!0,order:!0,orphans:!0,widows:!0,zIndex:!0,zoom:!0},cssProps:{},style:function(e,t,n,r){if(e&&3!==e.nodeType&&8!==e.nodeType&&e.style){var i,o,a,s=X(t),u=Xe.test(t),l=e.style;if(u||(t=ze(s)),a=S.cssHooks[t]||S.cssHooks[s],void 0===n)return a&&"get"in a&&void 0!==(i=a.get(e,!1,r))?i:l[t];"string"===(o=typeof n)&&(i=te.exec(n))&&i[1]&&(n=se(e,t,i),o="number"),null!=n&&n==n&&("number"!==o||u||(n+=i&&i[3]||(S.cssNumber[s]?"":"px")),y.clearCloneStyle||""!==n||0!==t.indexOf("background")||(l[t]="inherit"),a&&"set"in a&&void 0===(n=a.set(e,n,r))||(u?l.setProperty(t,n):l[t]=n))}},css:function(e,t,n,r){var i,o,a,s=X(t);return Xe.test(t)||(t=ze(s)),(a=S.cssHooks[t]||S.cssHooks[s])&&"get"in a&&(i=a.get(e,!0,n)),void 0===i&&(i=We(e,t,r)),"normal"===i&&t in Ge&&(i=Ge[t]),""===n||n?(o=parseFloat(i),!0===n||isFinite(o)?o||0:i):i}}),S.each(["height","width"],function(e,u){S.cssHooks[u]={get:function(e,t,n){if(t)return!Ue.test(S.css(e,"display"))||e.getClientRects().length&&e.getBoundingClientRect().width?Je(e,u,n):Me(e,Ve,function(){return Je(e,u,n)})},set:function(e,t,n){var r,i=Re(e),o=!y.scrollboxSize()&&"absolute"===i.position,a=(o||n)&&"border-box"===S.css(e,"boxSizing",!1,i),s=n?Qe(e,u,n,a,i):0;return a&&o&&(s-=Math.ceil(e["offset"+u[0].toUpperCase()+u.slice(1)]-parseFloat(i[u])-Qe(e,u,"border",!1,i)-.5)),s&&(r=te.exec(t))&&"px"!==(r[3]||"px")&&(e.style[u]=t,t=S.css(e,u)),Ye(0,t,s)}}}),S.cssHooks.marginLeft=Fe(y.reliableMarginLeft,function(e,t){if(t)return(parseFloat(We(e,"marginLeft"))||e.getBoundingClientRect().left-Me(e,{marginLeft:0},function(){return e.getBoundingClientRect().left}))+"px"}),S.each({margin:"",padding:"",border:"Width"},function(i,o){S.cssHooks[i+o]={expand:function(e){for(var t=0,n={},r="string"==typeof e?e.split(" "):[e];t<4;t++)n[i+ne[t]+o]=r[t]||r[t-2]||r[0];return n}},"margin"!==i&&(S.cssHooks[i+o].set=Ye)}),S.fn.extend({css:function(e,t){return $(this,function(e,t,n){var r,i,o={},a=0;if(Array.isArray(t)){for(r=Re(e),i=t.length;a<i;a++)o[t[a]]=S.css(e,t[a],!1,r);return o}return void 0!==n?S.style(e,t,n):S.css(e,t)},e,t,1<arguments.length)}}),((S.Tween=Ke).prototype={constructor:Ke,init:function(e,t,n,r,i,o){this.elem=e,this.prop=n,this.easing=i||S.easing._default,this.options=t,this.start=this.now=this.cur(),this.end=r,this.unit=o||(S.cssNumber[n]?"":"px")},cur:function(){var e=Ke.propHooks[this.prop];return e&&e.get?e.get(this):Ke.propHooks._default.get(this)},run:function(e){var t,n=Ke.propHooks[this.prop];return this.options.duration?this.pos=t=S.easing[this.easing](e,this.options.duration*e,0,1,this.options.duration):this.pos=t=e,this.now=(this.end-this.start)*t+this.start,this.options.step&&this.options.step.call(this.elem,this.now,this),n&&n.set?n.set(this):Ke.propHooks._default.set(this),this}}).init.prototype=Ke.prototype,(Ke.propHooks={_default:{get:function(e){var t;return 1!==e.elem.nodeType||null!=e.elem[e.prop]&&null==e.elem.style[e.prop]?e.elem[e.prop]:(t=S.css(e.elem,e.prop,""))&&"auto"!==t?t:0},set:function(e){S.fx.step[e.prop]?S.fx.step[e.prop](e):1!==e.elem.nodeType||!S.cssHooks[e.prop]&&null==e.elem.style[ze(e.prop)]?e.elem[e.prop]=e.now:S.style(e.elem,e.prop,e.now+e.unit)}}}).scrollTop=Ke.propHooks.scrollLeft={set:function(e){e.elem.nodeType&&e.elem.parentNode&&(e.elem[e.prop]=e.now)}},S.easing={linear:function(e){return e},swing:function(e){return.5-Math.cos(e*Math.PI)/2},_default:"swing"},S.fx=Ke.prototype.init,S.fx.step={};var Ze,et,tt,nt,rt=/^(?:toggle|show|hide)$/,it=/queueHooks$/;function ot(){et&&(!1===E.hidden&&C.requestAnimationFrame?C.requestAnimationFrame(ot):C.setTimeout(ot,S.fx.interval),S.fx.tick())}function at(){return C.setTimeout(function(){Ze=void 0}),Ze=Date.now()}function st(e,t){var n,r=0,i={height:e};for(t=t?1:0;r<4;r+=2-t)i["margin"+(n=ne[r])]=i["padding"+n]=e;return t&&(i.opacity=i.width=e),i}function ut(e,t,n){for(var r,i=(lt.tweeners[t]||[]).concat(lt.tweeners["*"]),o=0,a=i.length;o<a;o++)if(r=i[o].call(n,t,e))return r}function lt(o,e,t){var n,a,r=0,i=lt.prefilters.length,s=S.Deferred().always(function(){delete u.elem}),u=function(){if(a)return!1;for(var e=Ze||at(),t=Math.max(0,l.startTime+l.duration-e),n=1-(t/l.duration||0),r=0,i=l.tweens.length;r<i;r++)l.tweens[r].run(n);return s.notifyWith(o,[l,n,t]),n<1&&i?t:(i||s.notifyWith(o,[l,1,0]),s.resolveWith(o,[l]),!1)},l=s.promise({elem:o,props:S.extend({},e),opts:S.extend(!0,{specialEasing:{},easing:S.easing._default},t),originalProperties:e,originalOptions:t,startTime:Ze||at(),duration:t.duration,tweens:[],createTween:function(e,t){var n=S.Tween(o,l.opts,e,t,l.opts.specialEasing[e]||l.opts.easing);return l.tweens.push(n),n},stop:function(e){var t=0,n=e?l.tweens.length:0;if(a)return this;for(a=!0;t<n;t++)l.tweens[t].run(1);return e?(s.notifyWith(o,[l,1,0]),s.resolveWith(o,[l,e])):s.rejectWith(o,[l,e]),this}}),c=l.props;for(!function(e,t){var n,r,i,o,a;for(n in e)if(i=t[r=X(n)],o=e[n],Array.isArray(o)&&(i=o[1],o=e[n]=o[0]),n!==r&&(e[r]=o,delete e[n]),(a=S.cssHooks[r])&&"expand"in a)for(n in o=a.expand(o),delete e[r],o)n in e||(e[n]=o[n],t[n]=i);else t[r]=i}(c,l.opts.specialEasing);r<i;r++)if(n=lt.prefilters[r].call(l,o,c,l.opts))return m(n.stop)&&(S._queueHooks(l.elem,l.opts.queue).stop=n.stop.bind(n)),n;return S.map(c,ut,l),m(l.opts.start)&&l.opts.start.call(o,l),l.progress(l.opts.progress).done(l.opts.done,l.opts.complete).fail(l.opts.fail).always(l.opts.always),S.fx.timer(S.extend(u,{elem:o,anim:l,queue:l.opts.queue})),l}S.Animation=S.extend(lt,{tweeners:{"*":[function(e,t){var n=this.createTween(e,t);return se(n.elem,e,te.exec(t),n),n}]},tweener:function(e,t){m(e)?(t=e,e=["*"]):e=e.match(P);for(var n,r=0,i=e.length;r<i;r++)n=e[r],lt.tweeners[n]=lt.tweeners[n]||[],lt.tweeners[n].unshift(t)},prefilters:[function(e,t,n){var r,i,o,a,s,u,l,c,f="width"in t||"height"in t,p=this,d={},h=e.style,g=e.nodeType&&ae(e),v=Y.get(e,"fxshow");for(r in n.queue||(null==(a=S._queueHooks(e,"fx")).unqueued&&(a.unqueued=0,s=a.empty.fire,a.empty.fire=function(){a.unqueued||s()}),a.unqueued++,p.always(function(){p.always(function(){a.unqueued--,S.queue(e,"fx").length||a.empty.fire()})})),t)if(i=t[r],rt.test(i)){if(delete t[r],o=o||"toggle"===i,i===(g?"hide":"show")){if("show"!==i||!v||void 0===v[r])continue;g=!0}d[r]=v&&v[r]||S.style(e,r)}if((u=!S.isEmptyObject(t))||!S.isEmptyObject(d))for(r in f&&1===e.nodeType&&(n.overflow=[h.overflow,h.overflowX,h.overflowY],null==(l=v&&v.display)&&(l=Y.get(e,"display")),"none"===(c=S.css(e,"display"))&&(l?c=l:(le([e],!0),l=e.style.display||l,c=S.css(e,"display"),le([e]))),("inline"===c||"inline-block"===c&&null!=l)&&"none"===S.css(e,"float")&&(u||(p.done(function(){h.display=l}),null==l&&(c=h.display,l="none"===c?"":c)),h.display="inline-block")),n.overflow&&(h.overflow="hidden",p.always(function(){h.overflow=n.overflow[0],h.overflowX=n.overflow[1],h.overflowY=n.overflow[2]})),u=!1,d)u||(v?"hidden"in v&&(g=v.hidden):v=Y.access(e,"fxshow",{display:l}),o&&(v.hidden=!g),g&&le([e],!0),p.done(function(){for(r in g||le([e]),Y.remove(e,"fxshow"),d)S.style(e,r,d[r])})),u=ut(g?v[r]:0,r,p),r in v||(v[r]=u.start,g&&(u.end=u.start,u.start=0))}],prefilter:function(e,t){t?lt.prefilters.unshift(e):lt.prefilters.push(e)}}),S.speed=function(e,t,n){var r=e&&"object"==typeof e?S.extend({},e):{complete:n||!n&&t||m(e)&&e,duration:e,easing:n&&t||t&&!m(t)&&t};return S.fx.off?r.duration=0:"number"!=typeof r.duration&&(r.duration in S.fx.speeds?r.duration=S.fx.speeds[r.duration]:r.duration=S.fx.speeds._default),null!=r.queue&&!0!==r.queue||(r.queue="fx"),r.old=r.complete,r.complete=function(){m(r.old)&&r.old.call(this),r.queue&&S.dequeue(this,r.queue)},r},S.fn.extend({fadeTo:function(e,t,n,r){return this.filter(ae).css("opacity",0).show().end().animate({opacity:t},e,n,r)},animate:function(t,e,n,r){var i=S.isEmptyObject(t),o=S.speed(e,n,r),a=function(){var e=lt(this,S.extend({},t),o);(i||Y.get(this,"finish"))&&e.stop(!0)};return a.finish=a,i||!1===o.queue?this.each(a):this.queue(o.queue,a)},stop:function(i,e,o){var a=function(e){var t=e.stop;delete e.stop,t(o)};return"string"!=typeof i&&(o=e,e=i,i=void 0),e&&this.queue(i||"fx",[]),this.each(function(){var e=!0,t=null!=i&&i+"queueHooks",n=S.timers,r=Y.get(this);if(t)r[t]&&r[t].stop&&a(r[t]);else for(t in r)r[t]&&r[t].stop&&it.test(t)&&a(r[t]);for(t=n.length;t--;)n[t].elem!==this||null!=i&&n[t].queue!==i||(n[t].anim.stop(o),e=!1,n.splice(t,1));!e&&o||S.dequeue(this,i)})},finish:function(a){return!1!==a&&(a=a||"fx"),this.each(function(){var e,t=Y.get(this),n=t[a+"queue"],r=t[a+"queueHooks"],i=S.timers,o=n?n.length:0;for(t.finish=!0,S.queue(this,a,[]),r&&r.stop&&r.stop.call(this,!0),e=i.length;e--;)i[e].elem===this&&i[e].queue===a&&(i[e].anim.stop(!0),i.splice(e,1));for(e=0;e<o;e++)n[e]&&n[e].finish&&n[e].finish.call(this);delete t.finish})}}),S.each(["toggle","show","hide"],function(e,r){var i=S.fn[r];S.fn[r]=function(e,t,n){return null==e||"boolean"==typeof e?i.apply(this,arguments):this.animate(st(r,!0),e,t,n)}}),S.each({slideDown:st("show"),slideUp:st("hide"),slideToggle:st("toggle"),fadeIn:{opacity:"show"},fadeOut:{opacity:"hide"},fadeToggle:{opacity:"toggle"}},function(e,r){S.fn[e]=function(e,t,n){return this.animate(r,e,t,n)}}),S.timers=[],S.fx.tick=function(){var e,t=0,n=S.timers;for(Ze=Date.now();t<n.length;t++)(e=n[t])()||n[t]!==e||n.splice(t--,1);n.length||S.fx.stop(),Ze=void 0},S.fx.timer=function(e){S.timers.push(e),S.fx.start()},S.fx.interval=13,S.fx.start=function(){et||(et=!0,ot())},S.fx.stop=function(){et=null},S.fx.speeds={slow:600,fast:200,_default:400},S.fn.delay=function(r,e){return r=S.fx&&S.fx.speeds[r]||r,e=e||"fx",this.queue(e,function(e,t){var n=C.setTimeout(e,r);t.stop=function(){C.clearTimeout(n)}})},tt=E.createElement("input"),nt=E.createElement("select").appendChild(E.createElement("option")),tt.type="checkbox",y.checkOn=""!==tt.value,y.optSelected=nt.selected,(tt=E.createElement("input")).value="t",tt.type="radio",y.radioValue="t"===tt.value;var ct,ft=S.expr.attrHandle;S.fn.extend({attr:function(e,t){return $(this,S.attr,e,t,1<arguments.length)},removeAttr:function(e){return this.each(function(){S.removeAttr(this,e)})}}),S.extend({attr:function(e,t,n){var r,i,o=e.nodeType;if(3!==o&&8!==o&&2!==o)return"undefined"==typeof e.getAttribute?S.prop(e,t,n):(1===o&&S.isXMLDoc(e)||(i=S.attrHooks[t.toLowerCase()]||(S.expr.match.bool.test(t)?ct:void 0)),void 0!==n?null===n?void S.removeAttr(e,t):i&&"set"in i&&void 0!==(r=i.set(e,n,t))?r:(e.setAttribute(t,n+""),n):i&&"get"in i&&null!==(r=i.get(e,t))?r:null==(r=S.find.attr(e,t))?void 0:r)},attrHooks:{type:{set:function(e,t){if(!y.radioValue&&"radio"===t&&A(e,"input")){var n=e.value;return e.setAttribute("type",t),n&&(e.value=n),t}}}},removeAttr:function(e,t){var n,r=0,i=t&&t.match(P);if(i&&1===e.nodeType)while(n=i[r++])e.removeAttribute(n)}}),ct={set:function(e,t,n){return!1===t?S.removeAttr(e,n):e.setAttribute(n,n),n}},S.each(S.expr.match.bool.source.match(/\w+/g),function(e,t){var a=ft[t]||S.find.attr;ft[t]=function(e,t,n){var r,i,o=t.toLowerCase();return n||(i=ft[o],ft[o]=r,r=null!=a(e,t,n)?o:null,ft[o]=i),r}});var pt=/^(?:input|select|textarea|button)$/i,dt=/^(?:a|area)$/i;function ht(e){return(e.match(P)||[]).join(" ")}function gt(e){return e.getAttribute&&e.getAttribute("class")||""}function vt(e){return Array.isArray(e)?e:"string"==typeof e&&e.match(P)||[]}S.fn.extend({prop:function(e,t){return $(this,S.prop,e,t,1<arguments.length)},removeProp:function(e){return this.each(function(){delete this[S.propFix[e]||e]})}}),S.extend({prop:function(e,t,n){var r,i,o=e.nodeType;if(3!==o&&8!==o&&2!==o)return 1===o&&S.isXMLDoc(e)||(t=S.propFix[t]||t,i=S.propHooks[t]),void 0!==n?i&&"set"in i&&void 0!==(r=i.set(e,n,t))?r:e[t]=n:i&&"get"in i&&null!==(r=i.get(e,t))?r:e[t]},propHooks:{tabIndex:{get:function(e){var t=S.find.attr(e,"tabindex");return t?parseInt(t,10):pt.test(e.nodeName)||dt.test(e.nodeName)&&e.href?0:-1}}},propFix:{"for":"htmlFor","class":"className"}}),y.optSelected||(S.propHooks.selected={get:function(e){var t=e.parentNode;return t&&t.parentNode&&t.parentNode.selectedIndex,null},set:function(e){var t=e.parentNode;t&&(t.selectedIndex,t.parentNode&&t.parentNode.selectedIndex)}}),S.each(["tabIndex","readOnly","maxLength","cellSpacing","cellPadding","rowSpan","colSpan","useMap","frameBorder","contentEditable"],function(){S.propFix[this.toLowerCase()]=this}),S.fn.extend({addClass:function(t){var e,n,r,i,o,a,s,u=0;if(m(t))return this.each(function(e){S(this).addClass(t.call(this,e,gt(this)))});if((e=vt(t)).length)while(n=this[u++])if(i=gt(n),r=1===n.nodeType&&" "+ht(i)+" "){a=0;while(o=e[a++])r.indexOf(" "+o+" ")<0&&(r+=o+" ");i!==(s=ht(r))&&n.setAttribute("class",s)}return this},removeClass:function(t){var e,n,r,i,o,a,s,u=0;if(m(t))return this.each(function(e){S(this).removeClass(t.call(this,e,gt(this)))});if(!arguments.length)return this.attr("class","");if((e=vt(t)).length)while(n=this[u++])if(i=gt(n),r=1===n.nodeType&&" "+ht(i)+" "){a=0;while(o=e[a++])while(-1<r.indexOf(" "+o+" "))r=r.replace(" "+o+" "," ");i!==(s=ht(r))&&n.setAttribute("class",s)}return this},toggleClass:function(i,t){var o=typeof i,a="string"===o||Array.isArray(i);return"boolean"==typeof t&&a?t?this.addClass(i):this.removeClass(i):m(i)?this.each(function(e){S(this).toggleClass(i.call(this,e,gt(this),t),t)}):this.each(function(){var e,t,n,r;if(a){t=0,n=S(this),r=vt(i);while(e=r[t++])n.hasClass(e)?n.removeClass(e):n.addClass(e)}else void 0!==i&&"boolean"!==o||((e=gt(this))&&Y.set(this,"__className__",e),this.setAttribute&&this.setAttribute("class",e||!1===i?"":Y.get(this,"__className__")||""))})},hasClass:function(e){var t,n,r=0;t=" "+e+" ";while(n=this[r++])if(1===n.nodeType&&-1<(" "+ht(gt(n))+" ").indexOf(t))return!0;return!1}});var yt=/\r/g;S.fn.extend({val:function(n){var r,e,i,t=this[0];return arguments.length?(i=m(n),this.each(function(e){var t;1===this.nodeType&&(null==(t=i?n.call(this,e,S(this).val()):n)?t="":"number"==typeof t?t+="":Array.isArray(t)&&(t=S.map(t,function(e){return null==e?"":e+""})),(r=S.valHooks[this.type]||S.valHooks[this.nodeName.toLowerCase()])&&"set"in r&&void 0!==r.set(this,t,"value")||(this.value=t))})):t?(r=S.valHooks[t.type]||S.valHooks[t.nodeName.toLowerCase()])&&"get"in r&&void 0!==(e=r.get(t,"value"))?e:"string"==typeof(e=t.value)?e.replace(yt,""):null==e?"":e:void 0}}),S.extend({valHooks:{option:{get:function(e){var t=S.find.attr(e,"value");return null!=t?t:ht(S.text(e))}},select:{get:function(e){var t,n,r,i=e.options,o=e.selectedIndex,a="select-one"===e.type,s=a?null:[],u=a?o+1:i.length;for(r=o<0?u:a?o:0;r<u;r++)if(((n=i[r]).selected||r===o)&&!n.disabled&&(!n.parentNode.disabled||!A(n.parentNode,"optgroup"))){if(t=S(n).val(),a)return t;s.push(t)}return s},set:function(e,t){var n,r,i=e.options,o=S.makeArray(t),a=i.length;while(a--)((r=i[a]).selected=-1<S.inArray(S.valHooks.option.get(r),o))&&(n=!0);return n||(e.selectedIndex=-1),o}}}}),S.each(["radio","checkbox"],function(){S.valHooks[this]={set:function(e,t){if(Array.isArray(t))return e.checked=-1<S.inArray(S(e).val(),t)}},y.checkOn||(S.valHooks[this].get=function(e){return null===e.getAttribute("value")?"on":e.value})}),y.focusin="onfocusin"in C;var mt=/^(?:focusinfocus|focusoutblur)$/,xt=function(e){e.stopPropagation()};S.extend(S.event,{trigger:function(e,t,n,r){var i,o,a,s,u,l,c,f,p=[n||E],d=v.call(e,"type")?e.type:e,h=v.call(e,"namespace")?e.namespace.split("."):[];if(o=f=a=n=n||E,3!==n.nodeType&&8!==n.nodeType&&!mt.test(d+S.event.triggered)&&(-1<d.indexOf(".")&&(d=(h=d.split(".")).shift(),h.sort()),u=d.indexOf(":")<0&&"on"+d,(e=e[S.expando]?e:new S.Event(d,"object"==typeof e&&e)).isTrigger=r?2:3,e.namespace=h.join("."),e.rnamespace=e.namespace?new RegExp("(^|\\.)"+h.join("\\.(?:.*\\.|)")+"(\\.|$)"):null,e.result=void 0,e.target||(e.target=n),t=null==t?[e]:S.makeArray(t,[e]),c=S.event.special[d]||{},r||!c.trigger||!1!==c.trigger.apply(n,t))){if(!r&&!c.noBubble&&!x(n)){for(s=c.delegateType||d,mt.test(s+d)||(o=o.parentNode);o;o=o.parentNode)p.push(o),a=o;a===(n.ownerDocument||E)&&p.push(a.defaultView||a.parentWindow||C)}i=0;while((o=p[i++])&&!e.isPropagationStopped())f=o,e.type=1<i?s:c.bindType||d,(l=(Y.get(o,"events")||Object.create(null))[e.type]&&Y.get(o,"handle"))&&l.apply(o,t),(l=u&&o[u])&&l.apply&&V(o)&&(e.result=l.apply(o,t),!1===e.result&&e.preventDefault());return e.type=d,r||e.isDefaultPrevented()||c._default&&!1!==c._default.apply(p.pop(),t)||!V(n)||u&&m(n[d])&&!x(n)&&((a=n[u])&&(n[u]=null),S.event.triggered=d,e.isPropagationStopped()&&f.addEventListener(d,xt),n[d](),e.isPropagationStopped()&&f.removeEventListener(d,xt),S.event.triggered=void 0,a&&(n[u]=a)),e.result}},simulate:function(e,t,n){var r=S.extend(new S.Event,n,{type:e,isSimulated:!0});S.event.trigger(r,null,t)}}),S.fn.extend({trigger:function(e,t){return this.each(function(){S.event.trigger(e,t,this)})},triggerHandler:function(e,t){var n=this[0];if(n)return S.event.trigger(e,t,n,!0)}}),y.focusin||S.each({focus:"focusin",blur:"focusout"},function(n,r){var i=function(e){S.event.simulate(r,e.target,S.event.fix(e))};S.event.special[r]={setup:function(){var e=this.ownerDocument||this.document||this,t=Y.access(e,r);t||e.addEventListener(n,i,!0),Y.access(e,r,(t||0)+1)},teardown:function(){var e=this.ownerDocument||this.document||this,t=Y.access(e,r)-1;t?Y.access(e,r,t):(e.removeEventListener(n,i,!0),Y.remove(e,r))}}});var bt=C.location,wt={guid:Date.now()},Tt=/\?/;S.parseXML=function(e){var t,n;if(!e||"string"!=typeof e)return null;try{t=(new C.DOMParser).parseFromString(e,"text/xml")}catch(e){}return n=t&&t.getElementsByTagName("parsererror")[0],t&&!n||S.error("Invalid XML: "+(n?S.map(n.childNodes,function(e){return e.textContent}).join("\n"):e)),t};var Ct=/\[\]$/,Et=/\r?\n/g,St=/^(?:submit|button|image|reset|file)$/i,kt=/^(?:input|select|textarea|keygen)/i;function At(n,e,r,i){var t;if(Array.isArray(e))S.each(e,function(e,t){r||Ct.test(n)?i(n,t):At(n+"["+("object"==typeof t&&null!=t?e:"")+"]",t,r,i)});else if(r||"object"!==w(e))i(n,e);else for(t in e)At(n+"["+t+"]",e[t],r,i)}S.param=function(e,t){var n,r=[],i=function(e,t){var n=m(t)?t():t;r[r.length]=encodeURIComponent(e)+"="+encodeURIComponent(null==n?"":n)};if(null==e)return"";if(Array.isArray(e)||e.jquery&&!S.isPlainObject(e))S.each(e,function(){i(this.name,this.value)});else for(n in e)At(n,e[n],t,i);return r.join("&")},S.fn.extend({serialize:function(){return S.param(this.serializeArray())},serializeArray:function(){return this.map(function(){var e=S.prop(this,"elements");return e?S.makeArray(e):this}).filter(function(){var e=this.type;return this.name&&!S(this).is(":disabled")&&kt.test(this.nodeName)&&!St.test(e)&&(this.checked||!pe.test(e))}).map(function(e,t){var n=S(this).val();return null==n?null:Array.isArray(n)?S.map(n,function(e){return{name:t.name,value:e.replace(Et,"\r\n")}}):{name:t.name,value:n.replace(Et,"\r\n")}}).get()}});var Nt=/%20/g,jt=/#.*$/,Dt=/([?&])_=[^&]*/,qt=/^(.*?):[ \t]*([^\r\n]*)$/gm,Lt=/^(?:GET|HEAD)$/,Ht=/^\/\//,Ot={},Pt={},Rt="*/".concat("*"),Mt=E.createElement("a");function It(o){return function(e,t){"string"!=typeof e&&(t=e,e="*");var n,r=0,i=e.toLowerCase().match(P)||[];if(m(t))while(n=i[r++])"+"===n[0]?(n=n.slice(1)||"*",(o[n]=o[n]||[]).unshift(t)):(o[n]=o[n]||[]).push(t)}}function Wt(t,i,o,a){var s={},u=t===Pt;function l(e){var r;return s[e]=!0,S.each(t[e]||[],function(e,t){var n=t(i,o,a);return"string"!=typeof n||u||s[n]?u?!(r=n):void 0:(i.dataTypes.unshift(n),l(n),!1)}),r}return l(i.dataTypes[0])||!s["*"]&&l("*")}function Ft(e,t){var n,r,i=S.ajaxSettings.flatOptions||{};for(n in t)void 0!==t[n]&&((i[n]?e:r||(r={}))[n]=t[n]);return r&&S.extend(!0,e,r),e}Mt.href=bt.href,S.extend({active:0,lastModified:{},etag:{},ajaxSettings:{url:bt.href,type:"GET",isLocal:/^(?:about|app|app-storage|.+-extension|file|res|widget):$/.test(bt.protocol),global:!0,processData:!0,async:!0,contentType:"application/x-www-form-urlencoded; charset=UTF-8",accepts:{"*":Rt,text:"text/plain",html:"text/html",xml:"application/xml, text/xml",json:"application/json, text/javascript"},contents:{xml:/\bxml\b/,html:/\bhtml/,json:/\bjson\b/},responseFields:{xml:"responseXML",text:"responseText",json:"responseJSON"},converters:{"* text":String,"text html":!0,"text json":JSON.parse,"text xml":S.parseXML},flatOptions:{url:!0,context:!0}},ajaxSetup:function(e,t){return t?Ft(Ft(e,S.ajaxSettings),t):Ft(S.ajaxSettings,e)},ajaxPrefilter:It(Ot),ajaxTransport:It(Pt),ajax:function(e,t){"object"==typeof e&&(t=e,e=void 0),t=t||{};var c,f,p,n,d,r,h,g,i,o,v=S.ajaxSetup({},t),y=v.context||v,m=v.context&&(y.nodeType||y.jquery)?S(y):S.event,x=S.Deferred(),b=S.Callbacks("once memory"),w=v.statusCode||{},a={},s={},u="canceled",T={readyState:0,getResponseHeader:function(e){var t;if(h){if(!n){n={};while(t=qt.exec(p))n[t[1].toLowerCase()+" "]=(n[t[1].toLowerCase()+" "]||[]).concat(t[2])}t=n[e.toLowerCase()+" "]}return null==t?null:t.join(", ")},getAllResponseHeaders:function(){return h?p:null},setRequestHeader:function(e,t){return null==h&&(e=s[e.toLowerCase()]=s[e.toLowerCase()]||e,a[e]=t),this},overrideMimeType:function(e){return null==h&&(v.mimeType=e),this},statusCode:function(e){var t;if(e)if(h)T.always(e[T.status]);else for(t in e)w[t]=[w[t],e[t]];return this},abort:function(e){var t=e||u;return c&&c.abort(t),l(0,t),this}};if(x.promise(T),v.url=((e||v.url||bt.href)+"").replace(Ht,bt.protocol+"//"),v.type=t.method||t.type||v.method||v.type,v.dataTypes=(v.dataType||"*").toLowerCase().match(P)||[""],null==v.crossDomain){r=E.createElement("a");try{r.href=v.url,r.href=r.href,v.crossDomain=Mt.protocol+"//"+Mt.host!=r.protocol+"//"+r.host}catch(e){v.crossDomain=!0}}if(v.data&&v.processData&&"string"!=typeof v.data&&(v.data=S.param(v.data,v.traditional)),Wt(Ot,v,t,T),h)return T;for(i in(g=S.event&&v.global)&&0==S.active++&&S.event.trigger("ajaxStart"),v.type=v.type.toUpperCase(),v.hasContent=!Lt.test(v.type),f=v.url.replace(jt,""),v.hasContent?v.data&&v.processData&&0===(v.contentType||"").indexOf("application/x-www-form-urlencoded")&&(v.data=v.data.replace(Nt,"+")):(o=v.url.slice(f.length),v.data&&(v.processData||"string"==typeof v.data)&&(f+=(Tt.test(f)?"&":"?")+v.data,delete v.data),!1===v.cache&&(f=f.replace(Dt,"$1"),o=(Tt.test(f)?"&":"?")+"_="+wt.guid+++o),v.url=f+o),v.ifModified&&(S.lastModified[f]&&T.setRequestHeader("If-Modified-Since",S.lastModified[f]),S.etag[f]&&T.setRequestHeader("If-None-Match",S.etag[f])),(v.data&&v.hasContent&&!1!==v.contentType||t.contentType)&&T.setRequestHeader("Content-Type",v.contentType),T.setRequestHeader("Accept",v.dataTypes[0]&&v.accepts[v.dataTypes[0]]?v.accepts[v.dataTypes[0]]+("*"!==v.dataTypes[0]?", "+Rt+"; q=0.01":""):v.accepts["*"]),v.headers)T.setRequestHeader(i,v.headers[i]);if(v.beforeSend&&(!1===v.beforeSend.call(y,T,v)||h))return T.abort();if(u="abort",b.add(v.complete),T.done(v.success),T.fail(v.error),c=Wt(Pt,v,t,T)){if(T.readyState=1,g&&m.trigger("ajaxSend",[T,v]),h)return T;v.async&&0<v.timeout&&(d=C.setTimeout(function(){T.abort("timeout")},v.timeout));try{h=!1,c.send(a,l)}catch(e){if(h)throw e;l(-1,e)}}else l(-1,"No Transport");function l(e,t,n,r){var i,o,a,s,u,l=t;h||(h=!0,d&&C.clearTimeout(d),c=void 0,p=r||"",T.readyState=0<e?4:0,i=200<=e&&e<300||304===e,n&&(s=function(e,t,n){var r,i,o,a,s=e.contents,u=e.dataTypes;while("*"===u[0])u.shift(),void 0===r&&(r=e.mimeType||t.getResponseHeader("Content-Type"));if(r)for(i in s)if(s[i]&&s[i].test(r)){u.unshift(i);break}if(u[0]in n)o=u[0];else{for(i in n){if(!u[0]||e.converters[i+" "+u[0]]){o=i;break}a||(a=i)}o=o||a}if(o)return o!==u[0]&&u.unshift(o),n[o]}(v,T,n)),!i&&-1<S.inArray("script",v.dataTypes)&&S.inArray("json",v.dataTypes)<0&&(v.converters["text script"]=function(){}),s=function(e,t,n,r){var i,o,a,s,u,l={},c=e.dataTypes.slice();if(c[1])for(a in e.converters)l[a.toLowerCase()]=e.converters[a];o=c.shift();while(o)if(e.responseFields[o]&&(n[e.responseFields[o]]=t),!u&&r&&e.dataFilter&&(t=e.dataFilter(t,e.dataType)),u=o,o=c.shift())if("*"===o)o=u;else if("*"!==u&&u!==o){if(!(a=l[u+" "+o]||l["* "+o]))for(i in l)if((s=i.split(" "))[1]===o&&(a=l[u+" "+s[0]]||l["* "+s[0]])){!0===a?a=l[i]:!0!==l[i]&&(o=s[0],c.unshift(s[1]));break}if(!0!==a)if(a&&e["throws"])t=a(t);else try{t=a(t)}catch(e){return{state:"parsererror",error:a?e:"No conversion from "+u+" to "+o}}}return{state:"success",data:t}}(v,s,T,i),i?(v.ifModified&&((u=T.getResponseHeader("Last-Modified"))&&(S.lastModified[f]=u),(u=T.getResponseHeader("etag"))&&(S.etag[f]=u)),204===e||"HEAD"===v.type?l="nocontent":304===e?l="notmodified":(l=s.state,o=s.data,i=!(a=s.error))):(a=l,!e&&l||(l="error",e<0&&(e=0))),T.status=e,T.statusText=(t||l)+"",i?x.resolveWith(y,[o,l,T]):x.rejectWith(y,[T,l,a]),T.statusCode(w),w=void 0,g&&m.trigger(i?"ajaxSuccess":"ajaxError",[T,v,i?o:a]),b.fireWith(y,[T,l]),g&&(m.trigger("ajaxComplete",[T,v]),--S.active||S.event.trigger("ajaxStop")))}return T},getJSON:function(e,t,n){return S.get(e,t,n,"json")},getScript:function(e,t){return S.get(e,void 0,t,"script")}}),S.each(["get","post"],function(e,i){S[i]=function(e,t,n,r){return m(t)&&(r=r||n,n=t,t=void 0),S.ajax(S.extend({url:e,type:i,dataType:r,data:t,success:n},S.isPlainObject(e)&&e))}}),S.ajaxPrefilter(function(e){var t;for(t in e.headers)"content-type"===t.toLowerCase()&&(e.contentType=e.headers[t]||"")}),S._evalUrl=function(e,t,n){return S.ajax({url:e,type:"GET",dataType:"script",cache:!0,async:!1,global:!1,converters:{"text script":function(){}},dataFilter:function(e){S.globalEval(e,t,n)}})},S.fn.extend({wrapAll:function(e){var t;return this[0]&&(m(e)&&(e=e.call(this[0])),t=S(e,this[0].ownerDocument).eq(0).clone(!0),this[0].parentNode&&t.insertBefore(this[0]),t.map(function(){var e=this;while(e.firstElementChild)e=e.firstElementChild;return e}).append(this)),this},wrapInner:function(n){return m(n)?this.each(function(e){S(this).wrapInner(n.call(this,e))}):this.each(function(){var e=S(this),t=e.contents();t.length?t.wrapAll(n):e.append(n)})},wrap:function(t){var n=m(t);return this.each(function(e){S(this).wrapAll(n?t.call(this,e):t)})},unwrap:function(e){return this.parent(e).not("body").each(function(){S(this).replaceWith(this.childNodes)}),this}}),S.expr.pseudos.hidden=function(e){return!S.expr.pseudos.visible(e)},S.expr.pseudos.visible=function(e){return!!(e.offsetWidth||e.offsetHeight||e.getClientRects().length)},S.ajaxSettings.xhr=function(){try{return new C.XMLHttpRequest}catch(e){}};var Bt={0:200,1223:204},$t=S.ajaxSettings.xhr();y.cors=!!$t&&"withCredentials"in $t,y.ajax=$t=!!$t,S.ajaxTransport(function(i){var o,a;if(y.cors||$t&&!i.crossDomain)return{send:function(e,t){var n,r=i.xhr();if(r.open(i.type,i.url,i.async,i.username,i.password),i.xhrFields)for(n in i.xhrFields)r[n]=i.xhrFields[n];for(n in i.mimeType&&r.overrideMimeType&&r.overrideMimeType(i.mimeType),i.crossDomain||e["X-Requested-With"]||(e["X-Requested-With"]="XMLHttpRequest"),e)r.setRequestHeader(n,e[n]);o=function(e){return function(){o&&(o=a=r.onload=r.onerror=r.onabort=r.ontimeout=r.onreadystatechange=null,"abort"===e?r.abort():"error"===e?"number"!=typeof r.status?t(0,"error"):t(r.status,r.statusText):t(Bt[r.status]||r.status,r.statusText,"text"!==(r.responseType||"text")||"string"!=typeof r.responseText?{binary:r.response}:{text:r.responseText},r.getAllResponseHeaders()))}},r.onload=o(),a=r.onerror=r.ontimeout=o("error"),void 0!==r.onabort?r.onabort=a:r.onreadystatechange=function(){4===r.readyState&&C.setTimeout(function(){o&&a()})},o=o("abort");try{r.send(i.hasContent&&i.data||null)}catch(e){if(o)throw e}},abort:function(){o&&o()}}}),S.ajaxPrefilter(function(e){e.crossDomain&&(e.contents.script=!1)}),S.ajaxSetup({accepts:{script:"text/javascript, application/javascript, application/ecmascript, application/x-ecmascript"},contents:{script:/\b(?:java|ecma)script\b/},converters:{"text script":function(e){return S.globalEval(e),e}}}),S.ajaxPrefilter("script",function(e){void 0===e.cache&&(e.cache=!1),e.crossDomain&&(e.type="GET")}),S.ajaxTransport("script",function(n){var r,i;if(n.crossDomain||n.scriptAttrs)return{send:function(e,t){r=S("<script>").attr(n.scriptAttrs||{}).prop({charset:n.scriptCharset,src:n.url}).on("load error",i=function(e){r.remove(),i=null,e&&t("error"===e.type?404:200,e.type)}),E.head.appendChild(r[0])},abort:function(){i&&i()}}});var _t,zt=[],Ut=/(=)\?(?=&|$)|\?\?/;S.ajaxSetup({jsonp:"callback",jsonpCallback:function(){var e=zt.pop()||S.expando+"_"+wt.guid++;return this[e]=!0,e}}),S.ajaxPrefilter("json jsonp",function(e,t,n){var r,i,o,a=!1!==e.jsonp&&(Ut.test(e.url)?"url":"string"==typeof e.data&&0===(e.contentType||"").indexOf("application/x-www-form-urlencoded")&&Ut.test(e.data)&&"data");if(a||"jsonp"===e.dataTypes[0])return r=e.jsonpCallback=m(e.jsonpCallback)?e.jsonpCallback():e.jsonpCallback,a?e[a]=e[a].replace(Ut,"$1"+r):!1!==e.jsonp&&(e.url+=(Tt.test(e.url)?"&":"?")+e.jsonp+"="+r),e.converters["script json"]=function(){return o||S.error(r+" was not called"),o[0]},e.dataTypes[0]="json",i=C[r],C[r]=function(){o=arguments},n.always(function(){void 0===i?S(C).removeProp(r):C[r]=i,e[r]&&(e.jsonpCallback=t.jsonpCallback,zt.push(r)),o&&m(i)&&i(o[0]),o=i=void 0}),"script"}),y.createHTMLDocument=((_t=E.implementation.createHTMLDocument("").body).innerHTML="<form></form><form></form>",2===_t.childNodes.length),S.parseHTML=function(e,t,n){return"string"!=typeof e?[]:("boolean"==typeof t&&(n=t,t=!1),t||(y.createHTMLDocument?((r=(t=E.implementation.createHTMLDocument("")).createElement("base")).href=E.location.href,t.head.appendChild(r)):t=E),o=!n&&[],(i=N.exec(e))?[t.createElement(i[1])]:(i=xe([e],t,o),o&&o.length&&S(o).remove(),S.merge([],i.childNodes)));var r,i,o},S.fn.load=function(e,t,n){var r,i,o,a=this,s=e.indexOf(" ");return-1<s&&(r=ht(e.slice(s)),e=e.slice(0,s)),m(t)?(n=t,t=void 0):t&&"object"==typeof t&&(i="POST"),0<a.length&&S.ajax({url:e,type:i||"GET",dataType:"html",data:t}).done(function(e){o=arguments,a.html(r?S("<div>").append(S.parseHTML(e)).find(r):e)}).always(n&&function(e,t){a.each(function(){n.apply(this,o||[e.responseText,t,e])})}),this},S.expr.pseudos.animated=function(t){return S.grep(S.timers,function(e){return t===e.elem}).length},S.offset={setOffset:function(e,t,n){var r,i,o,a,s,u,l=S.css(e,"position"),c=S(e),f={};"static"===l&&(e.style.position="relative"),s=c.offset(),o=S.css(e,"top"),u=S.css(e,"left"),("absolute"===l||"fixed"===l)&&-1<(o+u).indexOf("auto")?(a=(r=c.position()).top,i=r.left):(a=parseFloat(o)||0,i=parseFloat(u)||0),m(t)&&(t=t.call(e,n,S.extend({},s))),null!=t.top&&(f.top=t.top-s.top+a),null!=t.left&&(f.left=t.left-s.left+i),"using"in t?t.using.call(e,f):c.css(f)}},S.fn.extend({offset:function(t){if(arguments.length)return void 0===t?this:this.each(function(e){S.offset.setOffset(this,t,e)});var e,n,r=this[0];return r?r.getClientRects().length?(e=r.getBoundingClientRect(),n=r.ownerDocument.defaultView,{top:e.top+n.pageYOffset,left:e.left+n.pageXOffset}):{top:0,left:0}:void 0},position:function(){if(this[0]){var e,t,n,r=this[0],i={top:0,left:0};if("fixed"===S.css(r,"position"))t=r.getBoundingClientRect();else{t=this.offset(),n=r.ownerDocument,e=r.offsetParent||n.documentElement;while(e&&(e===n.body||e===n.documentElement)&&"static"===S.css(e,"position"))e=e.parentNode;e&&e!==r&&1===e.nodeType&&((i=S(e).offset()).top+=S.css(e,"borderTopWidth",!0),i.left+=S.css(e,"borderLeftWidth",!0))}return{top:t.top-i.top-S.css(r,"marginTop",!0),left:t.left-i.left-S.css(r,"marginLeft",!0)}}},offsetParent:function(){return this.map(function(){var e=this.offsetParent;while(e&&"static"===S.css(e,"position"))e=e.offsetParent;return e||re})}}),S.each({scrollLeft:"pageXOffset",scrollTop:"pageYOffset"},function(t,i){var o="pageYOffset"===i;S.fn[t]=function(e){return $(this,function(e,t,n){var r;if(x(e)?r=e:9===e.nodeType&&(r=e.defaultView),void 0===n)return r?r[i]:e[t];r?r.scrollTo(o?r.pageXOffset:n,o?n:r.pageYOffset):e[t]=n},t,e,arguments.length)}}),S.each(["top","left"],function(e,n){S.cssHooks[n]=Fe(y.pixelPosition,function(e,t){if(t)return t=We(e,n),Pe.test(t)?S(e).position()[n]+"px":t})}),S.each({Height:"height",Width:"width"},function(a,s){S.each({padding:"inner"+a,content:s,"":"outer"+a},function(r,o){S.fn[o]=function(e,t){var n=arguments.length&&(r||"boolean"!=typeof e),i=r||(!0===e||!0===t?"margin":"border");return $(this,function(e,t,n){var r;return x(e)?0===o.indexOf("outer")?e["inner"+a]:e.document.documentElement["client"+a]:9===e.nodeType?(r=e.documentElement,Math.max(e.body["scroll"+a],r["scroll"+a],e.body["offset"+a],r["offset"+a],r["client"+a])):void 0===n?S.css(e,t,i):S.style(e,t,n,i)},s,n?e:void 0,n)}})}),S.each(["ajaxStart","ajaxStop","ajaxComplete","ajaxError","ajaxSuccess","ajaxSend"],function(e,t){S.fn[t]=function(e){return this.on(t,e)}}),S.fn.extend({bind:function(e,t,n){return this.on(e,null,t,n)},unbind:function(e,t){return this.off(e,null,t)},delegate:function(e,t,n,r){return this.on(t,e,n,r)},undelegate:function(e,t,n){return 1===arguments.length?this.off(e,"**"):this.off(t,e||"**",n)},hover:function(e,t){return this.mouseenter(e).mouseleave(t||e)}}),S.each("blur focus focusin focusout resize scroll click dblclick mousedown mouseup mousemove mouseover mouseout mouseenter mouseleave change select submit keydown keypress keyup contextmenu".split(" "),function(e,n){S.fn[n]=function(e,t){return 0<arguments.length?this.on(n,null,e,t):this.trigger(n)}});var Xt=/^[\s\uFEFF\xA0]+|[\s\uFEFF\xA0]+$/g;S.proxy=function(e,t){var n,r,i;if("string"==typeof t&&(n=e[t],t=e,e=n),m(e))return r=s.call(arguments,2),(i=function(){return e.apply(t||this,r.concat(s.call(arguments)))}).guid=e.guid=e.guid||S.guid++,i},S.holdReady=function(e){e?S.readyWait++:S.ready(!0)},S.isArray=Array.isArray,S.parseJSON=JSON.parse,S.nodeName=A,S.isFunction=m,S.isWindow=x,S.camelCase=X,S.type=w,S.now=Date.now,S.isNumeric=function(e){var t=S.type(e);return("number"===t||"string"===t)&&!isNaN(e-parseFloat(e))},S.trim=function(e){return null==e?"":(e+"").replace(Xt,"")},"function"==typeof define&&define.amd&&define("jquery",[],function(){return S});var Vt=C.jQuery,Gt=C.$;return S.noConflict=function(e){return C.$===S&&(C.$=Gt),e&&C.jQuery===S&&(C.jQuery=Vt),S},"undefined"==typeof e&&(C.jQuery=C.$=S),S});

From 7e6eb03b7ea80b1635ecc7baa3f8330b35f12def Mon Sep 17 00:00:00 2001
From: ahg-g <ahg@google.com>
Date: Thu, 30 Mar 2023 00:18:04 +0000
Subject: [PATCH 066/272] Graduate JobMutableNodeSchedulingDirectives to GA

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

diff --git a/content/en/docs/concepts/workloads/controllers/job.md b/content/en/docs/concepts/workloads/controllers/job.md
index 7d83ca69992..aa0866de252 100644
--- a/content/en/docs/concepts/workloads/controllers/job.md
+++ b/content/en/docs/concepts/workloads/controllers/job.md
@@ -631,14 +631,7 @@ 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 >}}
+{{< feature-state for_k8s_version="v1.27" state="stable" >}}
 
 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.
@@ -653,7 +646,7 @@ pod-to-node assignment to kube-scheduler. This is allowed only for suspended Job
 been unsuspended before.
 
 The fields in a Job's pod template that can be updated are node affinity, node selector, 
-tolerations, labels and annotations.
+tolerations, labels, annotations and [scheduling gates](/docs/concepts/scheduling-eviction/pod-scheduling-readiness/).
 
 ### Specifying your own Pod 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 15f1a1cdfb9..e54bcdfa420 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
@@ -112,7 +112,6 @@ For a reference to old feature gates that are removed, please refer to
 | `InTreePluginPortworxUnregister` | `false` | Alpha | 1.23 | |
 | `InTreePluginRBDUnregister` | `false` | Alpha | 1.23 | |
 | `InTreePluginvSphereUnregister` | `false` | Alpha | 1.21 | |
-| `JobMutableNodeSchedulingDirectives` | `true` | Beta | 1.23 | |
 | `JobPodFailurePolicy` | `false` | Alpha | 1.25 | 1.25 |
 | `JobPodFailurePolicy` | `true` | Beta | 1.26 | |
 | `JobReadyPods` | `false` | Alpha | 1.23 | 1.23 |
@@ -283,6 +282,8 @@ For a reference to old feature gates that are removed, please refer to
 | `EphemeralContainers` | `true` | Beta | 1.23 | 1.24 |
 | `EphemeralContainers` | `true` | GA | 1.25 | - |
 | `ExecProbeTimeout` | `true` | GA | 1.20 | - |
+| `JobMutableNodeSchedulingDirectives` | `true` | Beta | 1.23 | 1.26 |
+| `JobMutableNodeSchedulingDirectives` | `true` | GA | 1.27 | |
 | `JobTrackingWithFinalizers` | `false` | Alpha | 1.22 | 1.22 |
 | `JobTrackingWithFinalizers` | `false` | Beta | 1.23 | 1.24 |
 | `JobTrackingWithFinalizers` | `true` | Beta | 1.25 | 1.25 |

From 7b6e694dc77b01e54a4a50a03b44276d76a4b32a Mon Sep 17 00:00:00 2001
From: Kevin Hannon <kannon1992@gmail.com>
Date: Tue, 14 Feb 2023 14:12:16 -0500
Subject: [PATCH 067/272] labels and job updates to mention new labels

---
 .../concepts/workloads/controllers/job.md     | 64 +++++++++++--------
 .../labels-annotations-taints/_index.md       | 41 ++++++++++++
 2 files changed, 77 insertions(+), 28 deletions(-)

diff --git a/content/en/docs/concepts/workloads/controllers/job.md b/content/en/docs/concepts/workloads/controllers/job.md
index 7d83ca69992..e077f5fc132 100644
--- a/content/en/docs/concepts/workloads/controllers/job.md
+++ b/content/en/docs/concepts/workloads/controllers/job.md
@@ -54,22 +54,22 @@ Check on the status of the Job with `kubectl`:
 
 {{< tabs name="Check status of Job" >}}
 {{< tab name="kubectl describe job pi" codelang="bash" >}}
-Name:             pi
-Namespace:        default
-Selector:         controller-uid=0cd26dd5-88a2-4a5f-a203-ea19a1d5d578
-Labels:           controller-uid=0cd26dd5-88a2-4a5f-a203-ea19a1d5d578
-                  job-name=pi
-Annotations:      batch.kubernetes.io/job-tracking: 
-Parallelism:      1
-Completions:      1
-Completion Mode:  NonIndexed
-Start Time:       Fri, 28 Oct 2022 13:05:18 +0530
-Completed At:     Fri, 28 Oct 2022 13:05:21 +0530
-Duration:         3s
-Pods Statuses:    0 Active / 1 Succeeded / 0 Failed
+Name:           pi
+Namespace:      default
+Selector:       batch.kubernetes.io/controller-uid=c9948307-e56d-4b5d-8302-ae2d7b7da67c
+Labels:         batch.kubernetes.io/controller-uid=c9948307-e56d-4b5d-8302-ae2d7b7da67c
+                batch.kubernetes.io/job-name=pi
+                ...
+Annotations:    batch.kubernetes.io/job-tracking: ""
+Parallelism:    1
+Completions:    1
+Start Time:     Mon, 02 Dec 2019 15:20:11 +0200
+Completed At:   Mon, 02 Dec 2019 15:21:16 +0200
+Duration:       65s
+Pods Statuses:  0 Running / 1 Succeeded / 0 Failed
 Pod Template:
-  Labels:  controller-uid=0cd26dd5-88a2-4a5f-a203-ea19a1d5d578
-           job-name=pi
+  Labels:  batch.kubernetes.io/controller-uid=c9948307-e56d-4b5d-8302-ae2d7b7da67c
+           batch.kubernetes.io/job-name=pi
   Containers:
    pi:
     Image:      perl:5.34.0
@@ -93,15 +93,13 @@ Events:
 apiVersion: batch/v1
 kind: Job
 metadata:
-  annotations:
-    batch.kubernetes.io/job-tracking: ""
-    kubectl.kubernetes.io/last-applied-configuration: |
-      {"apiVersion":"batch/v1","kind":"Job","metadata":{"annotations":{},"name":"pi","namespace":"default"},"spec":{"backoffLimit":4,"template":{"spec":{"containers":[{"command":["perl","-Mbignum=bpi","-wle","print bpi(2000)"],"image":"perl:5.34.0","name":"pi"}],"restartPolicy":"Never"}}}}
+  annotations: batch.kubernetes.io/job-tracking: ""
+             ...  
   creationTimestamp: "2022-11-10T17:53:53Z"
   generation: 1
   labels:
-    controller-uid: 204fb678-040b-497f-9266-35ffa8716d14
-    job-name: pi
+    batch.kubernetes.io/controller-uid: 863452e6-270d-420e-9b94-53a54146c223
+    batch.kubernetes.io/job-name: pi
   name: pi
   namespace: default
   resourceVersion: "4751"
@@ -113,14 +111,14 @@ spec:
   parallelism: 1
   selector:
     matchLabels:
-      controller-uid: 204fb678-040b-497f-9266-35ffa8716d14
+      batch.kubernetes.io/controller-uid: 863452e6-270d-420e-9b94-53a54146c223
   suspend: false
   template:
     metadata:
       creationTimestamp: null
       labels:
-        controller-uid: 204fb678-040b-497f-9266-35ffa8716d14
-        job-name: pi
+        batch.kubernetes.io/controller-uid: 863452e6-270d-420e-9b94-53a54146c223
+        batch.kubernetes.io/job-name: pi
     spec:
       containers:
       - command:
@@ -152,7 +150,7 @@ To view completed Pods of a Job, use `kubectl get pods`.
 To list all the Pods that belong to a Job in a machine readable form, you can use a command like this:
 
 ```shell
-pods=$(kubectl get pods --selector=job-name=pi --output=jsonpath='{.items[*].metadata.name}')
+pods=$(kubectl get pods --selector=batch.kubernetes.io/job-name=pi --output=jsonpath='{.items[*].metadata.name}')
 echo $pods
 ```
 
@@ -171,6 +169,12 @@ View the standard output of one of the pods:
 kubectl logs $pods
 ```
 
+Another way to view the logs of a Job:
+
+```shell
+kubectl logs jobs/pi
+```
+
 The output is similar to this:
 
 ```
@@ -192,6 +196,10 @@ characters.
 
 A Job also needs a [`.spec` section](https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status).
 
+### Job Labels
+
+Job labels will have `batch.kubernetes.io/` prefix for `job-name` and `controller-uid`.
+
 ### Pod Template
 
 The `.spec.template` is the only required field of the `.spec`.
@@ -696,12 +704,12 @@ metadata:
 spec:
   selector:
     matchLabels:
-      controller-uid: a8f3d00d-c6d2-11e5-9f87-42010af00002
+      batch.kubernetes.io/controller-uid: a8f3d00d-c6d2-11e5-9f87-42010af00002
   ...
 ```
 
 Then you create a new Job with name `new` and you explicitly specify the same selector.
-Since the existing Pods have label `controller-uid=a8f3d00d-c6d2-11e5-9f87-42010af00002`,
+Since the existing Pods have label `batch.kubernetes.io/controller-uid=a8f3d00d-c6d2-11e5-9f87-42010af00002`,
 they are controlled by Job `new` as well.
 
 You need to specify `manualSelector: true` in the new Job since you are not using
@@ -716,7 +724,7 @@ spec:
   manualSelector: true
   selector:
     matchLabels:
-      controller-uid: a8f3d00d-c6d2-11e5-9f87-42010af00002
+      batch.kubernetes.io/controller-uid: a8f3d00d-c6d2-11e5-9f87-42010af00002
   ...
 ```
 
diff --git a/content/en/docs/reference/labels-annotations-taints/_index.md b/content/en/docs/reference/labels-annotations-taints/_index.md
index 5f64d1f7acc..6468e520ebc 100644
--- a/content/en/docs/reference/labels-annotations-taints/_index.md
+++ b/content/en/docs/reference/labels-annotations-taints/_index.md
@@ -664,6 +664,47 @@ Kubernetes 1.27 and newer will ignore this annotation and always track Jobs
 using finalizers.
 {{< /note >}}
 
+### job-name (deprecated) {#job-name}
+
+Example: `job-name: "pi"`
+
+Used on: Jobs and Pods controlled by Jobs
+
+{{< note >}}
+Starting from Kubernetes 1.27, this label is deprecated.
+Kubernetes 1.27 and newer ignore this label and use the prefixed `job-name` label.
+{{< /note >}}
+
+### controller-uid (deprecated) {#controller-uid}
+
+Example: `controller-uid: "$UID"`
+
+Used on: Jobs and Pods controlled by Jobs
+
+{{< note >}}
+Starting from Kubernetes 1.27, this label is deprecated.
+Kubernetes 1.27 and newer ignore this label and use the prefixed `controller-uid` label.
+{{< /note >}}
+
+### batch.kubernetes.io/job-name {#batchkubernetesio-job-name}
+
+Example: `batch.kubernetes.io/job-name: "pi"`
+
+Used on: Jobs and Pods controlled by Jobs
+
+This label is used as a user-friendly way to get Pods corresponding to a Job.
+The `job-name` comes from the `name` of the Job and allows for an easy way to get Pods corresponding to the Job.
+
+### batch.kubernetes.io/controller-uid {#batchkubernetesio-controller-uid}
+
+Example: `batch.kubernetes.io/controller-uid: "$UID"`
+
+Used on: Jobs and Pods controlled by Jobs
+
+This label is used as a programmatic way to get all Pods corresponding to a Job.  
+The `controller-uid` is a unique identifer that gets set in the `selector` field so the Job controller
+can get all the corresponding Pods.
+
 ### scheduler.alpha.kubernetes.io/defaultTolerations {#scheduleralphakubernetesio-defaulttolerations}
 
 Example: `scheduler.alpha.kubernetes.io/defaultTolerations: '[{"operator": "Equal", "value": "value1", "effect": "NoSchedule", "key": "dedicated-node"}]'`

From a4eca1afc6b324f81ae35d76d8fd84ad3934ac04 Mon Sep 17 00:00:00 2001
From: Vinay Kulkarni <vinaykul@users.noreply.github.com>
Date: Thu, 30 Mar 2023 19:59:48 -0700
Subject: [PATCH 068/272] Documentation for in-place pod resize feature
 (#39845)

* Documentation for in-place pod resize feature

Fix issues from review feedback

Update content/en/docs/tasks/configure-pod-container/resize-container-resources.md

Co-authored-by: Qiming Teng <tengqm@outlook.com>

Better wording and formatting of overview section

Add descriptions about allocatedResources, resources, and resize fields

Update content/en/docs/tasks/configure-pod-container/resize-container-resources.md

Co-authored-by: Qiming Teng <tengqm@outlook.com>

Update content/en/docs/tasks/configure-pod-container/resize-container-resources.md

Co-authored-by: Qiming Teng <tengqm@outlook.com>

Apply suggestions from code review

Co-authored-by: Qiming Teng <tengqm@outlook.com>

* Simplify the changes by using bullet points

* Apply suggestions from code review

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

---------

Co-authored-by: Qiming Teng <tengqm@outlook.com>
Co-authored-by: Tim Bannister <tim@scalefactory.com>
---
 .../assign-cpu-resource.md                    |   2 +-
 .../assign-memory-resource.md                 |   5 +-
 .../resize-container-resources.md             | 261 ++++++++++++++++++
 content/en/examples/pods/qos/qos-pod-5.yaml   |  16 ++
 4 files changed, 279 insertions(+), 5 deletions(-)
 create mode 100644 content/en/docs/tasks/configure-pod-container/resize-container-resources.md
 create mode 100644 content/en/examples/pods/qos/qos-pod-5.yaml

diff --git a/content/en/docs/tasks/configure-pod-container/assign-cpu-resource.md b/content/en/docs/tasks/configure-pod-container/assign-cpu-resource.md
index 6f4b885e543..6f4c44e3494 100644
--- a/content/en/docs/tasks/configure-pod-container/assign-cpu-resource.md
+++ b/content/en/docs/tasks/configure-pod-container/assign-cpu-resource.md
@@ -275,4 +275,4 @@ kubectl delete namespace cpu-example
 
 * [Configure Quotas for API Objects](/docs/tasks/administer-cluster/quota-api-object/)
 
-
+* [Resize CPU and Memory Resources assigned to Containers](/docs/tasks/configure-pod-container/resize-container-resources/)
diff --git a/content/en/docs/tasks/configure-pod-container/assign-memory-resource.md b/content/en/docs/tasks/configure-pod-container/assign-memory-resource.md
index d923d6356c1..a0dcae50526 100644
--- a/content/en/docs/tasks/configure-pod-container/assign-memory-resource.md
+++ b/content/en/docs/tasks/configure-pod-container/assign-memory-resource.md
@@ -358,7 +358,4 @@ kubectl delete namespace mem-example
 
 * [Configure Quotas for API Objects](/docs/tasks/administer-cluster/quota-api-object/)
 
-
-
-
-
+* [Resize CPU and Memory Resources assigned to Containers](/docs/tasks/configure-pod-container/resize-container-resources/)
diff --git a/content/en/docs/tasks/configure-pod-container/resize-container-resources.md b/content/en/docs/tasks/configure-pod-container/resize-container-resources.md
new file mode 100644
index 00000000000..77e1b30d960
--- /dev/null
+++ b/content/en/docs/tasks/configure-pod-container/resize-container-resources.md
@@ -0,0 +1,261 @@
+---
+title: Resize CPU and Memory Resources assigned to Containers
+content_type: task
+weight: 30
+min-kubernetes-server-version: 1.27
+---
+
+
+<!-- overview -->
+
+{{< feature-state state="alpha" for_k8s_version="v1.27" >}}
+
+This page assumes that you are familiar with [Quality of Service](/docs/tasks/configure-pod-container/quality-service-pod/)
+for Kubernetes Pods.
+
+This page shows how to resize CPU and memory resources assigned to containers
+of a running pod without restarting the pod or its containers. A Kubernetes node
+allocates resources for a pod based on its `requests`, and restricts the pod's
+resource usage based on the `limits` specified in the pod's containers.
+
+For in-place resize of pod resources:
+- Container's resource `requests` and `limits` are _mutable_ for CPU
+  and memory resources.
+- `allocatedResources` field in `containerStatuses` of the Pod's status reflects
+  the resources allocated to the pod's containers.
+- `resources` field in `containerStatuses` of the Pod's status reflects the
+  actual resource `requests` and `limits` that are configured on the running
+  containers as reported by the container runtime.
+- `resize` field in the Pod's status shows the status of the last requested
+  pending resize. It can have the following values:
+  - `Proposed`: This value indicates an acknowledgement of the requested resize
+    and that the request was validated and recorded.
+  - `InProgress`: This value indicates that the node has accepted the resize
+    request and is in the process of applying it to the pod's containers.
+  - `Deferred`: This value means that the requested resize cannot be granted at
+    this time, and the node will keep retrying. The resize may be granted when
+    other pods leave and free up node resources.
+  - `Infeasible`: is a signal that the node cannot accommodate the requested
+    resize. This can happen if the requested resize exceeds the maximum
+    resources the node can ever allocate for a pod.
+
+
+## {{% heading "prerequisites" %}}
+
+
+{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
+
+
+## Container Resize Policies
+
+Resize policies allow for a more fine-grained control over how pod's containers
+are resized for CPU and memory resources. For example, the container's
+application may be able to handle CPU resources resized without being restarted,
+but resizing memory may require that the application hence the containers be restarted.
+
+To enable this, the Container specification allows users to specify a `resizePolicy`.
+The following restart policies can be specified for resizing CPU and memory:
+* `NotRequired`: Resize the container's resources while it is running.
+* `RestartContainer`: Restart the container and apply new resources upon restart.
+
+If `resizePolicy[*].restartPolicy` is not specified, it defaults to `NotRequired`.
+
+{{< note >}}
+If the Pod's `restartPolicy` is `Never`, container's resize restart policy must be
+set to `NotRequired` for all Containers in the Pod.
+{{< /note >}}
+
+Below example shows a Pod whose Container's CPU can be resized without restart, but
+memory resize memory requires the container to be restarted.
+
+```yaml
+apiVersion: v1
+kind: Pod
+metadata:
+  name: qos-demo-5
+  namespace: qos-example
+spec:
+  containers:
+  - name: qos-demo-ctr-5
+    image: nginx
+    resizePolicy:
+    - resourceName: cpu
+      restartPolicy: NotRequired
+    - resourceName: memory
+      restartPolicy: RestartContainer
+    resources:
+      limits:
+        memory: "200Mi"
+        cpu: "700m"
+      requests:
+        memory: "200Mi"
+        cpu: "700m"
+```
+
+{{< note >}}
+In the above example, if desired requests or limits for both CPU _and_ memory
+have changed, the container will be restarted in order to resize its memory.
+{{< /note >}}
+
+<!-- steps -->
+
+
+## Create a pod with resource requests and limits
+
+You can create a Guaranteed or Burstable [Quality of Service](/docs/tasks/configure-pod-container/quality-service-pod/)
+class pod by specifying requests and/or limits for a pod's containers.
+
+Consider the following manifest for a Pod that has one Container.
+
+{{< codenew file="pods/qos/qos-pod-5.yaml" >}}
+
+Create the pod in the `qos-example` namespace:
+
+```shell
+kubectl create namespace qos-example
+kubectl create -f https://k8s.io/examples/pods/qos/qos-pod-5.yaml
+```
+
+This pod is classified as a Guaranteed QoS class requesting 700m CPU and 200Mi
+memory.
+
+View detailed information about the pod:
+
+```shell
+kubectl get pod qos-demo-5 --output=yaml --namespace=qos-example
+```
+
+Also notice that the values of `resizePolicy[*].restartPolicy` defaulted to
+`NotRequired`, indicating that CPU and memory can be resized while container
+is running.
+
+```yaml
+spec:
+  containers:
+    ...
+    resizePolicy:
+    - resourceName: cpu
+      restartPolicy: NotRequired
+    - resourceName: memory
+      restartPolicy: NotRequired
+    resources:
+      limits:
+        cpu: 700m
+        memory: 200Mi
+      requests:
+        cpu: 700m
+        memory: 200Mi
+...
+  containerStatuses:
+...
+    name: qos-demo-ctr-5
+    ready: true
+...
+    allocatedResources:
+      cpu: 700m
+      memory: 200Mi
+    resources:
+      limits:
+        cpu: 700m
+        memory: 200Mi
+      requests:
+        cpu: 700m
+        memory: 200Mi
+    restartCount: 0
+    started: true
+...
+  qosClass: Guaranteed
+```
+
+
+## Updating the pod's resources
+
+Let's say the CPU requirements have increased, and 0.8 CPU is now desired. This
+is typically determined, and may be programmatically applied, by an entity such as
+[VerticalPodAutoscaler](https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler#readme) (VPA).
+
+{{< note >}}
+While you can change a Pod's requests and limits to express new desired
+resources, you cannot change the QoS class in which the Pod was created.
+{{< /note >}}
+
+Now, patch the Pod's Container with CPU requests & limits both set to `800m`:
+
+```shell
+kubectl -n qos-example patch pod qos-demo-5 --patch '{"spec":{"containers":[{"name":"qos-demo-ctr-5", "resources":{"requests":{"cpu":"800m"}, "limits":{"cpu":"800m"}}}]}}'
+```
+
+Query the Pod's detailed information after the Pod has been patched.
+
+```shell
+kubectl get pod qos-demo-5 --output=yaml --namespace=qos-example
+```
+
+The Pod's spec below reflects the updated CPU requests and limits.
+
+```yaml
+spec:
+  containers:
+    ...
+    resources:
+      limits:
+        cpu: 800m
+        memory: 200Mi
+      requests:
+        cpu: 800m
+        memory: 200Mi
+...
+  containerStatuses:
+...
+    allocatedResources:
+      cpu: 800m
+      memory: 200Mi
+    resources:
+      limits:
+        cpu: 800m
+        memory: 200Mi
+      requests:
+        cpu: 800m
+        memory: 200Mi
+    restartCount: 0
+    started: true
+```
+
+Observe that the `allocatedResources` values have been updated to reflect the new
+desired CPU requests. This indicates that node was able to accommodate the
+increased CPU resource needs.
+
+In the Container's status, updated CPU resource values shows that new CPU
+resources have been applied. The Container's `restartCount` remains unchanged,
+indicating that container's CPU resources were resized without restarting the container.
+
+
+## Clean up
+
+Delete your namespace:
+
+```shell
+kubectl delete namespace qos-example
+```
+
+
+## {{% heading "whatsnext" %}}
+
+
+### For application developers
+
+* [Assign Memory Resources to Containers and Pods](/docs/tasks/configure-pod-container/assign-memory-resource/)
+
+* [Assign CPU Resources to Containers and Pods](/docs/tasks/configure-pod-container/assign-cpu-resource/)
+
+### For cluster administrators
+
+* [Configure Default Memory Requests and Limits for a Namespace](/docs/tasks/administer-cluster/manage-resources/memory-default-namespace/)
+
+* [Configure Default CPU Requests and Limits for a Namespace](/docs/tasks/administer-cluster/manage-resources/cpu-default-namespace/)
+
+* [Configure Minimum and Maximum Memory Constraints for a Namespace](/docs/tasks/administer-cluster/manage-resources/memory-constraint-namespace/)
+
+* [Configure Minimum and Maximum CPU Constraints for a Namespace](/docs/tasks/administer-cluster/manage-resources/cpu-constraint-namespace/)
+
+* [Configure Memory and CPU Quotas for a Namespace](/docs/tasks/administer-cluster/manage-resources/quota-memory-cpu-namespace/)
diff --git a/content/en/examples/pods/qos/qos-pod-5.yaml b/content/en/examples/pods/qos/qos-pod-5.yaml
new file mode 100644
index 00000000000..c9b0c00c7ee
--- /dev/null
+++ b/content/en/examples/pods/qos/qos-pod-5.yaml
@@ -0,0 +1,16 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: qos-demo-5
+  namespace: qos-example
+spec:
+  containers:
+  - name: qos-demo-ctr-5
+    image: nginx
+    resources:
+      limits:
+        memory: "200Mi"
+        cpu: "700m"
+      requests:
+        memory: "200Mi"
+        cpu: "700m"

From 2ffb0371883a9e254aa60c99b35ab4b8017ab24a Mon Sep 17 00:00:00 2001
From: Rodrigo Campos <rata@users.noreply.github.com>
Date: Fri, 31 Mar 2023 00:01:48 -0300
Subject: [PATCH 069/272] Document user namespace changes in v1.27 (KEP-127)
 (#39860)

* content: Update user namespaces version requirements

Also, with the new implementation, the fsGroup was dropped. So removed
the mention to those limitations.

Signed-off-by: Rodrigo Campos <rodrigoca@microsoft.com>

* content: Add reference to the userns task in the concepts page

Signed-off-by: Rodrigo Campos <rodrigoca@microsoft.com>

---------

Signed-off-by: Rodrigo Campos <rodrigoca@microsoft.com>
---
 .../workloads/pods/user-namespaces.md         | 39 +++++++++++--------
 .../user-namespaces.md                        | 10 +++--
 2 files changed, 29 insertions(+), 20 deletions(-)

diff --git a/content/en/docs/concepts/workloads/pods/user-namespaces.md b/content/en/docs/concepts/workloads/pods/user-namespaces.md
index 0217490aa87..ec734c53d90 100644
--- a/content/en/docs/concepts/workloads/pods/user-namespaces.md
+++ b/content/en/docs/concepts/workloads/pods/user-namespaces.md
@@ -29,22 +29,36 @@ mitigate some future vulnerabilities too.
 <!-- body -->
 ## {{% heading "prerequisites" %}}
 
-{{% thirdparty-content single="true" %}}
-<!-- if adding another runtime in the future, omit the single setting -->
+{{% thirdparty-content %}}
 
-This is a Linux only feature. In addition, support is needed in the 
+This is a Linux-only feature and support is needed in Linux for idmap mounts on
+the filesystems used. This means:
+
+* On the node, the filesystem you use for `/var/lib/kubelet/pods/`, or the
+  custom directory you configure for this, needs idmap mount support.
+* All the filesystems used in the pod's volumes must support idmap mounts.
+
+In practice this means you need at least Linux 6.3, as tmpfs started supporting
+idmap mounts in that version. This is usually needed as several Kubernetes
+features use tmpfs (the service account token that is mounted by default uses a
+tmpfs, Secrets use a tmpfs, etc.)
+
+Some popular filesystems that support idmap mounts in Linux 6.3 are: btrfs,
+ext4, xfs, fat, tmpfs, overlayfs.
+
+In addition, support is needed in the 
 {{< glossary_tooltip text="container runtime" term_id="container-runtime" >}}
 to use this feature with Kubernetes stateless pods:
 
-* CRI-O: v1.25 has support for user namespaces.
+* CRI-O: version 1.25 (and later) supports user namespaces for containers.
 
-* containerd: support is planned for the 1.7 release. See containerd
-  issue [#7063][containerd-userns-issue] for more details.
+Please note that containerd v1.7 supports user namespaces for containers,
+compatible with Kubernetes {{< skew currentVersion >}}. It should not be used
+with Kubernetes 1.27 (and later).
 
 Support for this in [cri-dockerd is not planned][CRI-dockerd-issue] yet.
 
 [CRI-dockerd-issue]: https://github.com/Mirantis/cri-dockerd/issues/74
-[containerd-userns-issue]: https://github.com/containerd/containerd/issues/7063
 
 ## Introduction
 
@@ -152,13 +166,6 @@ volume types are allowed:
  * downwardAPI
  * emptyDir
 
-To guarantee that the pod can read the files of such volumes, volumes are
-created as if you specified `.spec.securityContext.fsGroup` as `0` for the Pod.
-If it is specified to a different value, this other value will of course be
-honored instead.
+## {{% heading "whatsnext" %}}
 
-As a by-product of this, folders and files for these volumes will have
-permissions for the group, even if `defaultMode` or `mode` to specific items of
-the volumes were specified without permissions to groups. For example, it is not
-possible to mount these volumes in a way that its files have permissions only
-for the owner.
+* Take a look at [Use a User Namespace With a Pod](/docs/tasks/configure-pod-container/user-namespaces/)
diff --git a/content/en/docs/tasks/configure-pod-container/user-namespaces.md b/content/en/docs/tasks/configure-pod-container/user-namespaces.md
index 6c4c01234cb..85cd1298a07 100644
--- a/content/en/docs/tasks/configure-pod-container/user-namespaces.md
+++ b/content/en/docs/tasks/configure-pod-container/user-namespaces.md
@@ -43,11 +43,13 @@ this is true when user namespaces are used.
 * You need to be able to exec into pods
 * Feature gate `UserNamespacesStatelessPodsSupport` need to be enabled.
 
-In addition, support is needed in the
-{{< glossary_tooltip text="container runtime" term_id="container-runtime" >}}
-to use this feature with Kubernetes stateless pods:
+The cluster that you're using **must** include at least one node that meets the
+[requirements](/docs/concepts/workloads/pods/user-namespaces/#before-you-begin)
+for using user namespaces with Pods.
 
-* CRI-O: v1.25 has support for user namespaces.
+If you have a mixture of nodes and only some of the nodes provide user namespace support for
+Pods, you also need to ensure that the user namespace Pods are
+[scheduled](/docs/concepts/scheduling-eviction/assign-pod-node/) to suitable nodes.
 
 Please note that **if your container runtime doesn't support user namespaces, the
 `hostUsers` field in the pod spec will be silently ignored and the pod will be

From e239a7dd33f0941c295cd632b9f9c7ba887eac1c Mon Sep 17 00:00:00 2001
From: Kermit Alexander II <kermitalexandr@google.com>
Date: Thu, 30 Mar 2023 22:41:48 -0500
Subject: [PATCH 070/272] Documentation for messageExpression update to
 KEP-2876 (#40019)

* Add messageExpression documentation.

* Apply feedback on wording.

* Add info about casting to string.

* Use "evaluates to an error" to avoid ambiguous wording around "fails."

* Revise wording around string casting.
---
 .../custom-resource-definitions.md            | 31 +++++++++++++++++++
 1 file changed, 31 insertions(+)

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 c439aa35dfd..2bcf40bef85 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
@@ -1035,6 +1035,37 @@ xref: [CEL types](https://github.com/google/cel-spec/blob/v0.6.0/doc/langdef.md#
 [OpenAPI types](https://swagger.io/specification/#data-types),
 [Kubernetes Structural Schemas](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#specifying-a-structural-schema).
 
+#### The messageExpression field
+
+Similar to the `message` field, which defines the string reported for a validation rule failure, 
+`messageExpression` allows you to use a CEL expression to construct the message string.
+This allows you to insert more descriptive information into the validation failure message. 
+`messageExpression` must evaluate a string and may use the same variables that are available to the `rule` 
+field. For example:
+
+```yaml
+x-kubernetes-validations:
+- rule: "self.x <= self.maxLimit"
+  messageExpression: '"x exceeded max limit of " + string(self.maxLimit)'
+```
+
+Keep in mind that CEL string concatenation (`+` operator) does not auto-cast to string. If
+you have a non-string scalar, use the `string(<value>)` function to cast the scalar to a string
+like shown in the above example.
+
+`messageExpression` must evaluate to a string, and this is checked while the CRD is being written. Note that it is possible
+to set `message` and `messageExpression` on the same rule, and if both are present, `messageExpression`
+will be used. However, if `messageExpression` evaluates to an error, the string defined in `message` 
+will be used instead, and the `messageExpression` error will be logged. This fallback will also occur if
+the CEL expression defined in `messageExpression` generates an empty string, or a string containing line 
+breaks.
+
+If one of the above conditions are met and no `message` has been set, then the default validation failure
+message will be used instead.
+
+`messageExpression` is a CEL expression, so the restrictions listed in [Resource use by validation functions](#resource-use-by-validation-functions) apply. If evaluation halts due to resource constraints 
+during `messageExpression` execution, then no further validation rules will be executed.
+
 #### Validation functions {#available-validation-functions}
 
 Functions available include:

From 17ad96c7929cf69f81de1d4a5b2d1bf386f751a5 Mon Sep 17 00:00:00 2001
From: Jeffrey Ying <jeffrey.ying86@live.com>
Date: Thu, 30 Mar 2023 23:49:48 -0400
Subject: [PATCH 071/272] Doc update for KEP-3352 Aggregated Discovery (#40024)

* Add documentation for aggregated discovery

* Update feature gate

* Update content/en/docs/concepts/overview/kubernetes-api.md

---------

Co-authored-by: Qiming Teng <tengqm@outlook.com>
---
 .../docs/concepts/overview/kubernetes-api.md  | 24 +++++++++++++++++++
 .../feature-gates.md                          |  3 ++-
 2 files changed, 26 insertions(+), 1 deletion(-)

diff --git a/content/en/docs/concepts/overview/kubernetes-api.md b/content/en/docs/concepts/overview/kubernetes-api.md
index 27e4829ba55..f522be1ea9e 100644
--- a/content/en/docs/concepts/overview/kubernetes-api.md
+++ b/content/en/docs/concepts/overview/kubernetes-api.md
@@ -158,6 +158,30 @@ Refer to the table below for accepted request headers.
 Kubernetes stores the serialized state of objects by writing them into
 {{< glossary_tooltip term_id="etcd" >}}.
 
+## API Discovery
+
+A list of all group versions supported by a cluster is published at
+the `/api` and `/apis` endpoints. Each group version also advertises
+the list of resources supported via `/apis/<group>/<version>` (for
+example: `/apis/rbac.authorization.k8s.io/v1alpha1`). These endpoints
+are used by kubectl to fetch the list of resources supported by a
+cluster.
+
+### Aggregated Discovery
+
+{{< feature-state state="beta"  for_k8s_version="v1.27" >}}
+
+Kubernetes offers beta support for aggregated discovery, publishing
+all resources supported by a cluster through two endpoints (`/api` and
+`/apis`) compared to one for every group version. Requesting this
+endpoint drastically reduces the number of requests sent to fetch the
+discovery for the average Kubernetes cluster. This may be accessed by
+requesting the respective endpoints with an Accept header indicating
+the aggregated discovery resource:
+`Accept: application/json;v=v2beta1;g=apidiscovery.k8s.io;as=APIGroupDiscoveryList`.
+
+The endpoint also supports ETag and protobuf encoding.
+
 ## API groups and versioning
 
 To make it easier to eliminate fields or restructure resource representations,
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 c2f1cd6e789..9eac31ae775 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
@@ -68,7 +68,8 @@ For a reference to old feature gates that are removed, please refer to
 | `APIServerIdentity` | `true` | Beta | 1.26 | |
 | `APIServerTracing` | `false` | Alpha | 1.22 | 1.26 |
 | `APIServerTracing` | `true` | Beta | 1.27 | |
-| `AggregatedDiscoveryEndpoint` | `false` | Alpha | 1.26 | |
+| `AggregatedDiscoveryEndpoint` | `false` | Alpha | 1.26 | 1.26 |
+| `AggregatedDiscoveryEndpoint` | `true` | Beta | 1.27 | |
 | `AnyVolumeDataSource` | `false` | Alpha | 1.18 | 1.23 |
 | `AnyVolumeDataSource` | `true` | Beta | 1.24 | |
 | `AppArmor` | `true` | Beta | 1.4 | |

From cb656b40c235642bffddc00a146ddca2323d5366 Mon Sep 17 00:00:00 2001
From: Rita Zhang <rita.z.zhang@gmail.com>
Date: Thu, 30 Mar 2023 23:21:49 -0700
Subject: [PATCH 072/272] Add docs to accompany KMS v2beta1 changes (#39110)

* Tracking commit for v1.27 docs

* feat: KMS v2beta1

Signed-off-by: Rita Zhang <rita.z.zhang@gmail.com>

---------

Signed-off-by: Rita Zhang <rita.z.zhang@gmail.com>
Co-authored-by: carolina valencia <krol3@users.noreply.github.com>
---
 .../tasks/administer-cluster/encrypt-data.md  |   3 +-
 .../tasks/administer-cluster/kms-provider.md  | 199 ++++++++++++++----
 2 files changed, 157 insertions(+), 45 deletions(-)

diff --git a/content/en/docs/tasks/administer-cluster/encrypt-data.md b/content/en/docs/tasks/administer-cluster/encrypt-data.md
index bbd12a326b0..c884810d20e 100644
--- a/content/en/docs/tasks/administer-cluster/encrypt-data.md
+++ b/content/en/docs/tasks/administer-cluster/encrypt-data.md
@@ -145,7 +145,8 @@ Name | Encryption | Strength | Speed | Key Length | Other Considerations
 `secretbox` | XSalsa20 and Poly1305 | Strong | Faster | 32-byte | A newer standard and may not be considered acceptable in environments that require high levels of review.
 `aesgcm` | AES-GCM with random nonce | Must be rotated every 200k writes | Fastest | 16, 24, or 32-byte | Is not recommended for use except when an automated key rotation scheme is implemented.
 `aescbc` | AES-CBC with [PKCS#7](https://datatracker.ietf.org/doc/html/rfc2315) padding | Weak | Fast | 32-byte | Not recommended due to CBC's vulnerability to padding oracle attacks.
-`kms` | Uses envelope encryption scheme: Data is encrypted by data encryption keys (DEKs) using AES-CBC with [PKCS#7](https://datatracker.ietf.org/doc/html/rfc2315) padding (prior to v1.25), using AES-GCM starting from v1.25, DEKs are encrypted by key encryption keys (KEKs) according to configuration in Key Management Service (KMS) | Strongest | Fast | 32-bytes |  The recommended choice for using a third party tool for key management. Simplifies key rotation, with a new DEK generated for each encryption, and KEK rotation controlled by the user. [Configure the KMS provider](/docs/tasks/administer-cluster/kms-provider/).
+`kms v1` | Uses envelope encryption scheme: Data is encrypted by data encryption keys (DEKs) using AES-CBC with [PKCS#7](https://datatracker.ietf.org/doc/html/rfc2315) padding (prior to v1.25), using AES-GCM starting from v1.25, DEKs are encrypted by key encryption keys (KEKs) according to configuration in Key Management Service (KMS) | Strongest | Slow (_compared to `kms v2`_) | 32-bytes |  Simplifies key rotation, with a new DEK generated for each encryption, and KEK rotation controlled by the user. [Configure the KMS V1 provider](/docs/tasks/administer-cluster/kms-provider#configuring-the-kms-provider-kms-v1).
+`kms v2` | Uses envelope encryption scheme: Data is encrypted by data encryption keys (DEKs) using AES-GCM, DEKs are encrypted by key encryption keys (KEKs) according to configuration in Key Management Service (KMS) | Strongest | Fast | 32-bytes |  The recommended choice for using a third party tool for key management. Available in beta from `v1.27`. A new DEK is generated at startup and reused for encryption. The DEK is rotated when the KEK is rotated. [Configure the KMS V2 provider](/docs/tasks/administer-cluster/kms-provider#configuring-the-kms-provider-kms-v2).
 {{< /table >}}
 
 Each provider supports multiple keys - the keys are tried in order for decryption, and if the provider
diff --git a/content/en/docs/tasks/administer-cluster/kms-provider.md b/content/en/docs/tasks/administer-cluster/kms-provider.md
index 21e89321e6c..7cf67fbf853 100644
--- a/content/en/docs/tasks/administer-cluster/kms-provider.md
+++ b/content/en/docs/tasks/administer-cluster/kms-provider.md
@@ -7,14 +7,17 @@ content_type: task
 weight: 370
 ---
 <!-- overview -->
-This page shows how to configure a Key Management Service (KMS) provider and plugin to enable secret data encryption. Currently there are two KMS API versions. KMS v1 will continue to work while v2 develops in maturity. If you are not sure which KMS API version to pick, choose v1. 
+This page shows how to configure a Key Management Service (KMS) provider and plugin to enable secret data encryption.
+Currently there are two KMS API versions. New integrations that only need to support Kubernetes v1.27+ 
+should use KMS v2 as it offers significantly better performance characteristics than v1
+(note the `Caution` sections below for specific cases when KMS v2 must not be used.)
 
 ## {{% heading "prerequisites" %}}
 
 {{< include "task-tutorial-prereqs.md" >}}
 
 The version of Kubernetes that you need depends on which KMS API version
-you have selected. 
+you have selected.
 
 - If you selected KMS API v1, any supported Kubernetes version will work fine.
 - If you selected KMS API v2, you should use Kubernetes v{{< skew currentVersion >}}
@@ -24,36 +27,61 @@ you have selected.
 {{< version-check >}}
 
 ### KMS v1
+{{< feature-state for_k8s_version="v1.12" state="beta" >}}
+
 * Kubernetes version 1.10.0 or later is required
 
 * Your cluster must use etcd v3 or later
 
-{{< feature-state for_k8s_version="v1.12" state="beta" >}}
-
 ### KMS v2
-* Kubernetes version 1.25.0 or later is required
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
 
-* Set kube-apiserver feature gate: `--feature-gates=KMSv2=true` to configure a KMS v2 provider
+* For version 1.25 and 1.26, enabling the feature via kube-apiserver feature gate is required.
+Set `--feature-gates=KMSv2=true` to configure a KMS v2 provider.
 
 * Your cluster must use etcd v3 or later
 
-{{< feature-state for_k8s_version="v1.25" state="alpha" >}}
+{{< caution >}}
+The KMS v2 API and implementation changed in incompatible ways in-between the alpha release in v1.25
+and the beta release in v1.27.  Attempting to upgrade from old versions with the alpha feature
+enabled will result in data loss.
+{{< /caution >}}
 
 <!-- steps -->
 
 The KMS encryption provider uses an envelope encryption scheme to encrypt data in etcd.
-The data is encrypted using a data encryption key (DEK); a new DEK is generated for each encryption.
+The data is encrypted using a data encryption key (DEK).
 The DEKs are encrypted with a key encryption key (KEK) that is stored and managed in a remote KMS.
-The KMS provider uses gRPC to communicate with a specific KMS plugin.
+With KMS v1, a new DEK is generated for each encryption.
+With KMS v2, a new DEK is generated on server startup and when the KMS plugin informs the API server
+that a KEK rotation has occurred (see `Understanding key_id and Key Rotation` section below).
+The KMS provider uses gRPC to communicate with a specific KMS plugin over a UNIX domain socket.
 The KMS plugin, which is implemented as a gRPC server and deployed on the same host(s)
 as the Kubernetes control plane, is responsible for all communication with the remote KMS.
 
+{{< caution >}}
+If you are running virtual machine (VM) based nodes that leverage VM state store with this feature, you must not use KMS v2.
+
+With KMS v2, the API server uses AES-GCM with a 12 byte nonce (8 byte atomic counter and 4 bytes random data) for encryption. 
+The following issues could occur if the VM is saved and restored:
+1. The counter value may be lost or corrupted if the VM is saved in an inconsistent state or restored improperly. 
+   This can lead to a situation where the same counter value is used twice, resulting in the same nonce being used 
+   for two different messages.
+2. If the VM is restored to a previous state, the counter value may be set back to its previous value, 
+resulting in the same nonce being used again.
+
+Although both of these cases are partially mitigated by the 4 byte random nonce, this can compromise 
+the security of the encryption.
+{{< /caution >}}
+
 ## Configuring the KMS provider
 
 To configure a KMS provider on the API server, include a provider of type `kms` in the
 `providers` array in the encryption configuration file and set the following properties:
 
 ### KMS v1 {#configuring-the-kms-provider-kms-v1}
+
+* `apiVersion`: API Version for KMS provider. Leave this value empty or set it to `v1`.
 * `name`: Display name of the KMS plugin. Cannot be changed once set.
 * `endpoint`: Listen address of the gRPC server (KMS plugin). The endpoint is a UNIX domain socket.
 * `cachesize`: Number of data encryption keys (DEKs) to be cached in the clear.
@@ -63,15 +91,17 @@ To configure a KMS provider on the API server, include a provider of type `kms`
   returning an error (default is 3 seconds).
 
 ### KMS v2 {#configuring-the-kms-provider-kms-v2}
-* `apiVersion`: API Version for KMS provider (Allowed values: v2, v1 or empty. Any other value will result in an error.)  Must be set to v2 to use the KMS v2 APIs.
+
+* `apiVersion`: API Version for KMS provider. Set this to `v2`.
 * `name`: Display name of the KMS plugin. Cannot be changed once set.
 * `endpoint`: Listen address of the gRPC server (KMS plugin). The endpoint is a UNIX domain socket.
-* `cachesize`: Number of data encryption keys (DEKs) to be cached in the clear.
-  When cached, DEKs can be used without another call to the KMS;
-  whereas DEKs that are not cached require a call to the KMS to unwrap.
 * `timeout`: How long should `kube-apiserver` wait for kms-plugin to respond before
   returning an error (default is 3 seconds).
 
+KMS v2 does not support the `cachesize` property. All data encryption keys (DEKs) will be cached in
+the clear once the server has unwrapped them via a call to the KMS. Once cached, DEKs can be used
+to perform decryption indefinitely without making a call to the KMS.
+
 See [Understanding the encryption at rest configuration](/docs/tasks/administer-cluster/encrypt-data).
 
 ## Implementing a KMS plugin
@@ -80,7 +110,7 @@ To implement a KMS plugin, you can develop a new plugin gRPC server or enable a
 already provided by your cloud provider.
 You then integrate the plugin with the remote KMS and deploy it on the Kubernetes master.
 
-### Enabling the KMS supported by your cloud provider 
+### Enabling the KMS supported by your cloud provider
 
 Refer to your cloud provider for instructions on enabling the cloud provider-specific KMS plugin.
 
@@ -90,21 +120,26 @@ You can develop a KMS plugin gRPC server using a stub file available for Go. For
 you use a proto file to create a stub file that you can use to develop the gRPC server code.
 
 #### KMS v1 {#developing-a-kms-plugin-gRPC-server-kms-v1}
+
 * Using Go: Use the functions and data structures in the stub file:
-  [api.pb.go](https://github.com/kubernetes/kubernetes/blob/release-1.25/staging/src/k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v1beta1/api.pb.go)
-  to develop the gRPC server code 
+  [api.pb.go](https://github.com/kubernetes/kms/blob/release-{{< skew currentVersion >}}/apis/v1beta1/api.pb.go)
+  to develop the gRPC server code
 
 * Using languages other than Go: Use the protoc compiler with the proto file:
-  [api.proto](https://github.com/kubernetes/kubernetes/blob/release-1.25/staging/src/k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v1beta1/api.proto)
+  [api.proto](https://github.com/kubernetes/kms/blob/release-{{< skew currentVersion >}}/apis/v1beta1/api.proto)
   to generate a stub file for the specific language
 
 #### KMS v2 {#developing-a-kms-plugin-gRPC-server-kms-v2}
-* Using Go: Use the functions and data structures in the stub file:
-  [api.pb.go](https://github.com/kubernetes/kubernetes/blob/release-1.25/staging/src/k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v2alpha1/api.pb.go)
-  to develop the gRPC server code 
+
+* Using Go: A high level
+  [library](https://github.com/kubernetes/kms/blob/release-{{< skew currentVersion >}}/pkg/service/interface.go)
+  is provided to make the process easier.  Low level implementations
+  can use the functions and data structures in the stub file:
+  [api.pb.go](https://github.com/kubernetes/kms/blob/release-{{< skew currentVersion >}}/apis/v2/api.pb.go)
+  to develop the gRPC server code
 
 * Using languages other than Go: Use the protoc compiler with the proto file:
-  [api.proto](https://github.com/kubernetes/kubernetes/blob/release-1.25/staging/src/k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v2alpha1/api.proto)
+  [api.proto](https://github.com/kubernetes/kms/blob/release-{{< skew currentVersion >}}/apis/v2/api.proto)
   to generate a stub file for the specific language
 
 Then use the functions and data structures in the stub file to develop the server code.
@@ -112,35 +147,106 @@ Then use the functions and data structures in the stub file to develop the serve
 #### Notes
 
 ##### KMS v1 {#developing-a-kms-plugin-gRPC-server-notes-kms-v1}
+
 * kms plugin version: `v1beta1`
 
   In response to procedure call Version, a compatible KMS plugin should return `v1beta1` as `VersionResponse.version`.
 
 * message version: `v1beta1`
 
-  All messages from KMS provider have the version field set to current version v1beta1.
+  All messages from KMS provider have the version field set to `v1beta1`.
 
 * protocol: UNIX domain socket (`unix`)
 
   The plugin is implemented as a gRPC server that listens at UNIX domain socket. The plugin deployment should create a file on the file system to run the gRPC unix domain socket connection. The API server (gRPC client) is configured with the KMS provider (gRPC server) unix domain socket endpoint in order to communicate with it. An abstract Linux socket may be used by starting the endpoint with `/@`, i.e. `unix:///@foo`. Care must be taken when using this type of socket as they do not have concept of ACL (unlike traditional file based sockets). However, they are subject to Linux networking namespace, so will only be accessible to containers within the same pod unless host networking is used.
 
 ##### KMS v2 {#developing-a-kms-plugin-gRPC-server-notes-kms-v2}
-* kms plugin version: `v2alpha1`
 
-  In response to procedure call Status, a compatible KMS plugin should return `v2alpha1` as `StatusResponse.Version`, "ok" as `StatusResponse.Healthz` and a keyID (KMS KEK ID) as `StatusResponse.KeyID`
+* KMS plugin version: `v2beta1`
+
+  In response to procedure call `Status`, a compatible KMS plugin should return `v2beta1` as `StatusResponse.version`,
+  "ok" as `StatusResponse.healthz` and a `key_id` (remote KMS KEK ID) as `StatusResponse.key_id`.
+
+  The API server polls the `Status` procedure call approximately every minute when everything is healthy,
+  and every 10 seconds when the plugin is not healthy.  Plugins must take care to optimize this call as it will be
+  under constant load.
+
+* Encryption
+
+  The `EncryptRequest` procedure call provides the plaintext and a UID for logging purposes.  The response must include
+  the ciphertext, the `key_id` for the KEK used, and, optionally, any metadata that the KMS plugin needs to aid in
+  future `DecryptRequest` calls (via the `annotations` field).  The plugin must guarantee that any distinct plaintext
+  results in a distinct response `(ciphertext, key_id, annotations)`.
+
+  If the plugin returns a non-empty `annotations` map, all map keys must be fully qualified domain names such as
+  `example.com`. An example use case of `annotation` is `{"kms.example.io/remote-kms-auditid":"<audit ID used by the remote KMS>"}`
+
+  The API server does not perform the `EncryptRequest` procedure call at a high rate.  Plugin implementations should
+  still aim to keep each request's latency at under 100 milliseconds.
+
+* Decryption
+
+  The `DecryptRequest` procedure call provides the `(ciphertext, key_id, annotations)` from `EncryptRequest` and a UID
+  for logging purposes.  As expected, it is the inverse of the `EncryptRequest` call.  Plugins must verify that the
+  `key_id` is one that they understand - they must not attempt to decrypt data unless they are sure that it was
+  encrypted by them at an earlier time.
+
+  The API server may perform thousands of `DecryptRequest` procedure calls on startup to fill its watch cache.  Thus
+  plugin implementations must perform these calls as quickly as possible, and should aim to keep each request's latency
+  at under 10 milliseconds.
+
+* Understanding `key_id` and Key Rotation
+
+  The `key_id` is the public, non-secret name of the remote KMS KEK that is currently in use.  It may be logged
+  during regular operation of the API server, and thus must not contain any private data.  Plugin implementations
+  are encouraged to use a hash to avoid leaking any data.  The KMS v2 metrics take care to hash this value before
+  exposing it via the `/metrics` endpoint.
+
+  The API server considers the `key_id` returned from the `Status` procedure call to be authoritative.  Thus, a change
+  to this value signals to the API server that the remote KEK has changed, and data encrypted with the old KEK should
+  be marked stale when a no-op write is performed (as described below).  If an `EncryptRequest` procedure call returns a
+  `key_id` that is different from `Status`, the response is thrown away and the plugin is considered unhealthy.  Thus
+  implementations must guarantee that the `key_id` returned from `Status` will be the same as the one returned by
+  `EncryptRequest`.  Furthermore, plugins must ensure that the `key_id` is stable and does not flip-flop between values
+  (i.e. during a remote KEK rotation).
+
+  Plugins must not re-use `key_id`s, even in situations where a previously used remote KEK has been reinstated.  For
+  example, if a plugin was using `key_id=A`, switched to `key_id=B`, and then went back to `key_id=A` - instead of
+  reporting `key_id=A` the plugin should report some derivative value such as `key_id=A_001` or use a new value such
+  as `key_id=C`.
+
+  Since the API server polls `Status` about every minute, `key_id` rotation is not immediate.  Furthermore, the API
+  server will coast on the last valid state for about three minutes.  Thus if a user wants to take a passive approach
+  to storage migration (i.e. by waiting), they must schedule a migration to occur at `3 + N + M` minutes after the
+  remote KEK has been rotated (`N` is how long it takes the plugin to observe the `key_id` change and `M` is the
+  desired buffer to allow config changes to be processed - a minimum `M` of five minutes is recommend).  Note that no
+  API server restart is required to perform KEK rotation.
+
+  {{< caution >}}  
+  Because you don't control the number of writes performed with the DEK, we recommend rotating the KEK at least every 90 days.
+  {{< /caution >}}
 
 * protocol: UNIX domain socket (`unix`)
 
-  The plugin is implemented as a gRPC server that listens at UNIX domain socket. The plugin deployment should create a file on the file system to run the gRPC unix domain socket connection. The API server (gRPC client) is configured with the KMS provider (gRPC server) unix domain socket endpoint in order to communicate with it. An abstract Linux socket may be used by starting the endpoint with `/@`, i.e. `unix:///@foo`. Care must be taken when using this type of socket as they do not have concept of ACL (unlike traditional file based sockets). However, they are subject to Linux networking namespace, so will only be accessible to containers within the same pod unless host networking is used. 
+  The plugin is implemented as a gRPC server that listens at UNIX domain socket. 
+  The plugin deployment should create a file on the file system to run the gRPC unix domain socket connection. 
+  The API server (gRPC client) is configured with the KMS provider (gRPC server) unix 
+  domain socket endpoint in order to communicate with it. 
+  An abstract Linux socket may be used by starting the endpoint with `/@`, i.e. `unix:///@foo`. 
+  Care must be taken when using this type of socket as they do not have concept of ACL 
+  (unlike traditional file based sockets). 
+  However, they are subject to Linux networking namespace, so will only be accessible to 
+  containers within the same pod unless host networking is used.
 
 ### Integrating a KMS plugin with the remote KMS
 
 The KMS plugin can communicate with the remote KMS using any protocol supported by the KMS.
-All configuration data, including authentication credentials the KMS plugin uses to communicate with the remote KMS, 
+All configuration data, including authentication credentials the KMS plugin uses to communicate with the remote KMS,
 are stored and managed by the KMS plugin independently.
-The KMS plugin can encode the ciphertext with additional metadata that may be required before sending it to the KMS for decryption.
+The KMS plugin can encode the ciphertext with additional metadata that may be required before sending it to the KMS
+for decryption (KMS v2 makes this process easier by providing a dedicated `annotations` field).
 
-### Deploying the KMS plugin 
+### Deploying the KMS plugin
 
 Ensure that the KMS plugin runs on the same host(s) as the Kubernetes master(s).
 
@@ -196,25 +302,24 @@ defined in a CustomResourceDefinition, your cluster must be running Kubernetes v
              apiVersion: v2
              name: myKmsPluginFoo
              endpoint: unix:///tmp/socketfile.sock
-             cachesize: 100
              timeout: 3s
          - kms:
+             apiVersion: v2
              name: myKmsPluginBar
              endpoint: unix:///tmp/socketfile.sock
-             cachesize: 100
              timeout: 3s
    ```
 
 Setting `--encryption-provider-config-automatic-reload` to `true` collapses all health checks to a single health check endpoint. Individual health checks are only available when KMS v1 providers are in use and the encryption config is not auto-reloaded.
 
-Following table summarizes the health check endpoints for each KMS version:
+The following table summarizes the health check endpoints for each KMS version:
 
-| KMS configurations        | Without Automatic Reload           | With Automatic Reload  |
-| ------------------------- |------------------------------------| -----------------------|
-| KMS v1 only               | Individual Healthchecks            | Single Healthcheck     |
-| KMS v2 only               | Single Healthcheck                 | Single Healthcheck     |
-| Both KMS v1 and v2        | Individual Healthchecks            | Single Healthcheck     |
-| No KMS                    | None                               | Single Healthcheck     |
+| KMS configurations | Without Automatic Reload | With Automatic Reload |
+| ------------------ | ------------------------ | --------------------- |
+| KMS v1 only        | Individual Healthchecks  | Single Healthcheck    |
+| KMS v2 only        | Single Healthcheck       | Single Healthcheck    |
+| Both KMS v1 and v2 | Individual Healthchecks  | Single Healthcheck    |
+| No KMS             | None                     | Single Healthcheck    |
 
 `Single Healthcheck` means that the only health check endpoint is `/healthz/kms-providers`.
 
@@ -222,6 +327,10 @@ Following table summarizes the health check endpoints for each KMS version:
 
 These healthcheck endpoint paths are hard coded and generated/controlled by the server. The indices for individual healthchecks corresponds to the order in which the KMS encryption config is processed.
 
+At a high level, restarting an API server when a KMS plugin is unhealthy is unlikely to make the situation better.
+It can make the situation significantly worse by throwing away the API server's DEK cache.  Thus the general
+recommendation is to ignore the API server KMS healthz checks for liveness purposes, i.e. `/livez?exclude=kms-providers`.
+
 Until the steps defined in [Ensuring all secrets are encrypted](#ensuring-all-secrets-are-encrypted) are performed, the `providers` list should end with the `identity: {}` provider to allow unencrypted data to be read.  Once all resources are encrypted, the `identity` provider should be removed to prevent the API server from honoring unencrypted data.
 
 For details about the `EncryptionConfiguration` format, please check the
@@ -229,8 +338,9 @@ For details about the `EncryptionConfiguration` format, please check the
 
 ## Verifying that the data is encrypted
 
-Data is encrypted when written to etcd. After restarting your `kube-apiserver`, 
-any newly created or updated Secret or other resource types configured in `EncryptionConfiguration` should be encrypted when stored. To verify,
+When encryption at rest is correctly configured, resources are encrypted on write.
+After restarting your `kube-apiserver`, any newly created or updated Secret or other resource types
+configured in `EncryptionConfiguration` should be encrypted when stored. To verify,
 you can use the `etcdctl` command line program to retrieve the contents of your secret data.
 
 1. Create a new secret called `secret1` in the `default` namespace:
@@ -259,7 +369,8 @@ you can use the `etcdctl` command line program to retrieve the contents of your
 
 ## Ensuring all secrets are encrypted
 
-Because secrets are encrypted on write, performing an update on a secret encrypts that content.
+When encryption at rest is correctly configured, resources are encrypted on write.
+Thus we can perform an in-place no-op update to ensure that data is encrypted.
 
 The following command reads all secrets and then updates them to apply server side encryption.
 If an error occurs due to a conflicting write, retry the command.
@@ -283,9 +394,9 @@ To switch from a local encryption provider to the `kms` provider and re-encrypt
          - secrets
        providers:
          - kms:
+             apiVersion: v2
              name : myKmsPlugin
              endpoint: unix:///tmp/socketfile.sock
-             cachesize: 100
          - aescbc:
              keys:
                - name: key1
@@ -304,7 +415,7 @@ To switch from a local encryption provider to the `kms` provider and re-encrypt
 
 To disable encryption at rest:
 
-1. Place the `identity` provider as the first entry in the configuration file: 
+1. Place the `identity` provider as the first entry in the configuration file:
 
    ```yaml
    apiVersion: apiserver.config.k8s.io/v1
@@ -315,12 +426,12 @@ To disable encryption at rest:
        providers:
          - identity: {}
          - kms:
+             apiVersion: v2
              name : myKmsPlugin
              endpoint: unix:///tmp/socketfile.sock
-             cachesize: 100
    ```
 
-1. Restart all `kube-apiserver` processes. 
+1. Restart all `kube-apiserver` processes.
 
 1. Run the following command to force all secrets to be decrypted.
 

From c2bfdc268549f459fe2a54085eec54a230250ae2 Mon Sep 17 00:00:00 2001
From: Dan Winship <danwinship@redhat.com>
Date: Fri, 31 Mar 2023 11:15:49 -0400
Subject: [PATCH 073/272] Add docs for CloudDualStackNodeIPs docs (KEP-3705)
 (#40188)

* Document KEP-3705 CloudDualStackNodeIPs

* Clarify --node-ip docs, reference dual-stack docs

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

---------

Co-authored-by: Tim Bannister <tim@scalefactory.com>
---
 content/en/docs/concepts/architecture/nodes.md         | 10 +++++++++-
 .../en/docs/concepts/services-networking/dual-stack.md |  7 +++++++
 .../command-line-tools-reference/feature-gates.md      |  4 ++++
 3 files changed, 20 insertions(+), 1 deletion(-)

diff --git a/content/en/docs/concepts/architecture/nodes.md b/content/en/docs/concepts/architecture/nodes.md
index 944083bc4d0..97193697dac 100644
--- a/content/en/docs/concepts/architecture/nodes.md
+++ b/content/en/docs/concepts/architecture/nodes.md
@@ -93,7 +93,15 @@ For self-registration, the kubelet is started with the following options:
   {{< glossary_tooltip text="taints" term_id="taint" >}} (comma separated `<key>=<value>:<effect>`).
 
   No-op if `register-node` is false.
-- `--node-ip` - IP address of the node.
+- `--node-ip` - Optional comma-separated list of the IP addresses for the node.
+  You can only specify a single address for each address family.
+  For example, in a single-stack IPv4 cluster, you set this value to be the IPv4 address that the
+  kubelet should use for the node.
+  See [configure IPv4/IPv6 dual stack](/docs/concepts/services-networking/dual-stack/#configure-ipv4-ipv6-dual-stack)
+  for details of running a dual-stack cluster.
+
+  If you don't provide this argument, the kubelet uses the node's default IPv4 address, if any;
+  if the node has no IPv4 addresses then the kubelet uses the node's default IPv6 address.
 - `--node-labels` - {{< glossary_tooltip text="Labels" term_id="label" >}} to add when registering the node
   in the cluster (see label restrictions enforced by the
   [NodeRestriction admission plugin](/docs/reference/access-authn-authz/admission-controllers/#noderestriction)).
diff --git a/content/en/docs/concepts/services-networking/dual-stack.md b/content/en/docs/concepts/services-networking/dual-stack.md
index 6c05516b033..1fad8507788 100644
--- a/content/en/docs/concepts/services-networking/dual-stack.md
+++ b/content/en/docs/concepts/services-networking/dual-stack.md
@@ -79,6 +79,13 @@ An example of an IPv6 CIDR: `fdXY:IJKL:MNOP:15::/64` (this shows the format but
 address - see [RFC 4193](https://tools.ietf.org/html/rfc4193))
 {{< /note >}}
 
+{{< feature-state for_k8s_version="v1.27" state="alpha" >}}
+
+When using an external cloud provider, you can pass a dual-stack `--node-ip` value to
+kubelet if you enable the `CloudDualStackNodeIPs` feature gate in both kubelet and the
+external cloud provider. This is only supported for cloud providers that support dual
+stack clusters.
+
 ## Services
 
 You can create {{< glossary_tooltip text="Services" term_id="service" >}} which can use IPv4, IPv6, or both.
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 ca1cc6749b8..2dc8bef9ef5 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,6 +83,7 @@ For a reference to old feature gates that are removed, please refer to
 | `CSINodeExpandSecret` | `false` | Alpha | 1.25 | 1.26 |
 | `CSINodeExpandSecret` | `true` | Beta | 1.27 | |
 | `CSIVolumeHealth` | `false` | Alpha | 1.21 | |
+| `CloudDualStackNodeIPs` | false | Alpha | 1.27 | |
 | `ComponentSLIs` | `false` | Alpha | 1.26 | |
 | `ContainerCheckpoint` | `false` | Alpha | 1.25 | |
 | `ContextualLogging` | `false` | Alpha | 1.24 | |
@@ -398,6 +399,9 @@ Each feature gate is designed for enabling/disabling a specific feature:
   {{< glossary_tooltip text="PVC" term_id="persistent-volume-claim" >}}.
 - `AppArmor`: Enable use of AppArmor mandatory access control for Pods running on Linux nodes.
   See [AppArmor Tutorial](/docs/tutorials/security/apparmor/) for more details.
+- `CloudDualStackNodeIPs`: Enables dual-stack `kubelet --node-ip` with external cloud providers.
+  See [Configure IPv4/IPv6 dual-stack](/docs/concepts/services-networking/dual-stack/#configure-ipv4-ipv6-dual-stack)
+  for more details.
 - `ContainerCheckpoint`: Enables the kubelet `checkpoint` API.
   See [Kubelet Checkpoint API](/docs/reference/node/kubelet-checkpoint-api/) for more details.
 - `CPUManager`: Enable container level CPU affinity support, see

From 0c9ba63075dd5cc1e57c041ce4089ddbfc2de22b Mon Sep 17 00:00:00 2001
From: Jefftree <jeffrey.ying86@live.com>
Date: Mon, 27 Mar 2023 17:02:45 +0000
Subject: [PATCH 074/272] Address comments

---
 content/en/docs/concepts/overview/kubernetes-api.md       | 4 ++--
 .../custom-resources/custom-resource-definitions.md       | 8 ++++++--
 2 files changed, 8 insertions(+), 4 deletions(-)

diff --git a/content/en/docs/concepts/overview/kubernetes-api.md b/content/en/docs/concepts/overview/kubernetes-api.md
index 725d47778bd..8aaa0452f9d 100644
--- a/content/en/docs/concepts/overview/kubernetes-api.md
+++ b/content/en/docs/concepts/overview/kubernetes-api.md
@@ -84,7 +84,7 @@ packages that define the API objects.
 
 {{< feature-state state="stable"  for_k8s_version="v1.27" >}}
 
-Kubernetes {{< param "version" >}} offers stable support for publishing its APIs as OpenAPI v3.
+Kubernetes supports publishing a description of its APIs as OpenAPI v3.
 
 A discovery endpoint `/openapi/v3` is provided to see a list of all
 group/versions available. This endpoint only returns JSON. These
@@ -149,7 +149,7 @@ Refer to the table below for accepted request headers.
   </tbody>
 </table>
 
-A golang implementation to fetch the OpenAPI V3 is provided in the package `k8s.io/client-go/openapi3`.
+A Golang implementation to fetch the OpenAPI V3 is provided in the package `k8s.io/client-go/openapi3`.
 
 ## Persistence
 
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 de6106e50a4..6f65907c7fd 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
@@ -1350,7 +1350,10 @@ default.
 
 CustomResourceDefinition [OpenAPI v3 validation schemas](#validation) which are
 [structural](#specifying-a-structural-schema) and [enable pruning](#field-pruning) are published
-as [OpenAPI v3](/docs/concepts/overview/kubernetes-api/#openapi-and-swagger-definitions) and OpenAPI v2 from Kubernetes API server. It is recommended to use the OpenAPI v3 document as it is a lossless representation of the CustomResourceDefinition OpenAPI v3 validation schema while OpenAPI v2 represents a lossy conversion.
+as [OpenAPI v3](/docs/concepts/overview/kubernetes-api/#openapi-and-swagger-definitions) and
+OpenAPI v2 from Kubernetes API server. It is recommended to use the OpenAPI v3 document
+as it is a lossless representation of the CustomResourceDefinition OpenAPI v3 validation schema
+while OpenAPI v2 represents a lossy conversion.
 
 The [kubectl](/docs/reference/kubectl/) command-line tool consumes the published schema to perform
 client-side validation (`kubectl create` and `kubectl apply`), schema explanation (`kubectl explain`)
@@ -1358,7 +1361,8 @@ on custom resources. The published schema can be consumed for other purposes as
 
 #### Compatibility with OpenAPI V2
 
-For compatibility with OpenAPI V2, the OpenAPI v3 validation schema performs a lossy conversion to the OpenAPI v2 schema. The schema show up in `definitions` and `paths` fields in the
+For compatibility with OpenAPI V2, the OpenAPI v3 validation schema performs a lossy conversion
+to the OpenAPI v2 schema. The schema show up in `definitions` and `paths` fields in the
 [OpenAPI v2 spec](/docs/concepts/overview/kubernetes-api/#openapi-and-swagger-definitions).
 
 The following modifications are applied during the conversion to keep backwards compatibility with

From d922bb21227f0a0c7e8761d45f70760570087452 Mon Sep 17 00:00:00 2001
From: Joseph Anttila Hall <jkh@google.com>
Date: Wed, 15 Mar 2023 21:05:24 -0700
Subject: [PATCH 075/272] Konnectivity example refresh.

---
 content/en/examples/admin/konnectivity/konnectivity-agent.yaml | 2 +-
 .../en/examples/admin/konnectivity/konnectivity-server.yaml    | 3 ++-
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/content/en/examples/admin/konnectivity/konnectivity-agent.yaml b/content/en/examples/admin/konnectivity/konnectivity-agent.yaml
index 0eb47e1c58b..cbcbf89114a 100644
--- a/content/en/examples/admin/konnectivity/konnectivity-agent.yaml
+++ b/content/en/examples/admin/konnectivity/konnectivity-agent.yaml
@@ -22,7 +22,7 @@ spec:
         - key: "CriticalAddonsOnly"
           operator: "Exists"
       containers:
-        - image: us.gcr.io/k8s-artifacts-prod/kas-network-proxy/proxy-agent:v0.0.16
+        - image: us.gcr.io/k8s-artifacts-prod/kas-network-proxy/proxy-agent:v0.0.37
           name: konnectivity-agent
           command: ["/proxy-agent"]
           args: [
diff --git a/content/en/examples/admin/konnectivity/konnectivity-server.yaml b/content/en/examples/admin/konnectivity/konnectivity-server.yaml
index 9f583740bd8..4dfbf5db9d1 100644
--- a/content/en/examples/admin/konnectivity/konnectivity-server.yaml
+++ b/content/en/examples/admin/konnectivity/konnectivity-server.yaml
@@ -8,12 +8,13 @@ spec:
   hostNetwork: true
   containers:
   - name: konnectivity-server-container
-    image: registry.k8s.io/kas-network-proxy/proxy-server:v0.0.32
+    image: registry.k8s.io/kas-network-proxy/proxy-server:v0.0.37
     command: ["/proxy-server"]
     args: [
             "--logtostderr=true",
             # This needs to be consistent with the value set in egressSelectorConfiguration.
             "--uds-name=/etc/kubernetes/konnectivity-server/konnectivity-server.socket",
+            "--delete-existing-uds-file",
             # The following two lines assume the Konnectivity server is
             # deployed on the same machine as the apiserver, and the certs and
             # key of the API Server are at the specified location.

From 528e1138e99fd24b0350a0ca3cbe5c2bec5fd998 Mon Sep 17 00:00:00 2001
From: Kensei Nakada <handbomusic@gmail.com>
Date: Sat, 1 Apr 2023 15:34:10 +0900
Subject: [PATCH 076/272] add min domains

---
 .../2023-04-11-topology-spread-features.md    | 30 +++++++++++++++++--
 1 file changed, 28 insertions(+), 2 deletions(-)

diff --git a/content/en/blog/_posts/2023-04-11-topology-spread-features.md b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
index 8d38440562c..290a5ac2b73 100644
--- a/content/en/blog/_posts/2023-04-11-topology-spread-features.md
+++ b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
@@ -6,7 +6,7 @@ slug: topology-spread-new-features
 evergreen: true
 ---
 
-**Authors:** [Alex Wang](https://github.com/denkensk)(), [Kante Yin](https://github.com/kerthcet)(), [Kensei Nakada](https://github.com/sanposhiho)(Mercari)
+**Authors:** [Alex Wang](https://github.com/denkensk)(Shopee), [Kante Yin](https://github.com/kerthcet)(DaoCloud), [Kensei Nakada](https://github.com/sanposhiho)(Mercari)
 
 In Kubernetes v1.19, [Pod Topology Spread Constraints](https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/) went to GA. 
 It is the feature to control how Pods are spread to each failure-domain (regions, zones, nodes etc).
@@ -19,7 +19,33 @@ This blog post is going to introduce each feature and the usecase/issue behind t
 
 ## KEP-3022: min domains in Pod Topology Spread
 
-TODO(sanposhiho): write it
+Pod Topology Spread has the `maxSkew` parameter to define the degree to which Pods may be unevenly distributed. 
+
+But, there wasn't a way to control the number of domains over which we should spread. 
+Some users want to force spreading Pods over a minimum number of domains, and if there aren't enough already present, make the cluster-autoscaler provision them.
+
+Then, we introduced the `minDomains` parameter in the Pod Topology Spread. 
+Via `minDomains` parameter, you can define the minimum number of domains. 
+
+For example, there are 3 Nodes with the enough capacity, 
+and newly created replicaset has the following `topologySpreadConstraints` in template.
+
+```yaml
+topologySpreadConstraints:
+- maxSkew: 1
+  minDomains: 5 # requires 5 Nodes at least.
+  whenUnsatisfiable: DoNotSchedule # minDomains is valid only when DoNotSchedule is used.
+  topologyKey: kubernetes.io/hostname 
+  labelSelector:
+    matchLabels:
+        foo: bar
+```
+
+This case, 3 Pods will be scheduled to those 3 Nodes,
+but other 2 Pods from this replicaset will be unschedulable until more Nodes join the cluster.
+
+The cluster autoscaler provisions new Nodes based on these unschedulable Pods,
+and as a result, the replicas are finally spread over 5 Nodes.
 
 ## KEP-3094: Take taints/tolerations into consideration when calculating PodTopologySpread skew
 

From 48b77c022678c8322bb6fec08b1e6d0ad96a5ba7 Mon Sep 17 00:00:00 2001
From: harshitasao <harshitasao@gmail.com>
Date: Sun, 2 Apr 2023 01:11:55 +0530
Subject: [PATCH 077/272] Added v1.27 Release blog article

---
 .../_posts/2023-04-11-kubernetes-1.27-blog.md | 209 ++++++++++++++++++
 .../kubernetes-1.27.png                       | Bin 0 -> 232585 bytes
 2 files changed, 209 insertions(+)
 create mode 100644 content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
 create mode 100644 static/images/blog/2023-04-11-kubernetes-1.27-blog/kubernetes-1.27.png

diff --git a/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md b/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
new file mode 100644
index 00000000000..da60ef0330d
--- /dev/null
+++ b/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
@@ -0,0 +1,209 @@
+---
+layout: blog
+title: "Kubernetes v1.27: Chill Vibes"
+date: 2023-04-11
+slug: kubernetes-v1-27-release
+
+**Authors**: [Kubernetes 1.26 Release Team](https://github.com/kubernetes/sig-release/blob/master/releases/release-1.27/release-team.md)
+
+Announcing the release of Kubernetes v1.27, the first release of 2023!
+
+This release consist of sixty enhancements. Eighteen of those enhancements are entering Alpha, Tweentynine are graduating to Beta, and Thirteen are graduating to Stable.
+
+## Release theme and logo
+
+**Kubernetes v1.27: Chill Vibes**
+
+The theme for Kubernetes v1.27 is *Chill Vibes*.
+
+{{< figure src="/images/blog/2023-04-11-kubernetes-1.27-blog/kubernetes-1.27.png" alt="Kubernetes 1.27 Chill Vibes logo" class="release-logo" >}}
+
+
+It's a little silly, but there were some important shifts in this release that helped inspire the theme. Throughout a typical Kubernetes release cycle, there are several deadlines that features need to meet to remain included. If a feature misses any of these deadlines, there is an exception process they can go through. Handling these exceptions is a very normal part of the release. But v1.27 is the first release that anyone can remember where we didn't receive a single exception request after the enhancements freeze. Even as the release progressed, things remained much calmer than any of us are used to.
+
+There's a specific reason we were able to enjoy a more calm release this time around, and that's all the work that folks put in beind the scenes to improve how we manage the release. That's what this theme celebrates, people putting in the work to make things better for the community.
+
+Special thinks to [Britnee Laverack](https://www.instagram.com/artsyfie/) for creating the logo. Britnee also design the logo for [Kubernetes 1.24: Stargazer](https://kubernetes.io/blog/2022/05/03/kubernetes-1-24-release-announcement/#release-theme-and-logo).
+
+# What's New (Major Themes)
+
+### Freeze `k8s.gcr.io` image registry
+
+Replacing the old image registry, [k8s.gcr.io](https://cloud.google.com/container-registry/) with [registry.k8s.io](https://github.com/kubernetes/registry.k8s.io) which has been generally available for several months. The Kubernetes project created and runs the `registry.k8s.io` image registry, which is fully controlled by the community.
+This mean that all subsequent image releases would not be available on the old registry. Freezing  the `k8s.gcr.io` image registry by not pushing any new digests or tags after this release.
+
+What does this change mean for contributors:
+
+* If you are a maintainer of a subproject, you will need to update your manifests and Helm charts to use the new registry.
+
+What does this change mean for end users:
+
+* This Kubernetes release will not be published to the old registry.
+
+* Patch releases for v1.24, v1.25, and v1.26 will no longer be published to the old registry from April. 
+
+* Starting in v1.25, the default image registry has been set to `registry.k8s.io`. This value is overridable in kubeadm and kubelet but setting it to `k8s.gcr.io` will fail for new releases after April as they won’t be present in the old registry.
+
+* If you want to increase the reliability of your cluster and remove dependency on the community-owned registry or you are running Kubernetes in networks where external traffic is restricted, you should consider hosting local image registry mirrors. Some cloud vendors may offer hosted solutions for this.
+
+
+## SeccompDefault graduates to stable
+
+To use seccomp profile defaulting, you must run the kubelet with the `--seccomp-default` [command line flag](/docs/reference/command-line-tools-reference/kubelet) enabled for each node where you want to use it. 
+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.
+
+You can find more detailed information about a possible upgrade and downgrade strategy in the related Kubernetes Enhancement Proposal (KEP): [Enable seccomp by default](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2413-seccomp-by-default).
+
+## Pod Scheduling Readiness goes to beta 
+
+Pods were considered ready for scheduling once created. Kubernetes scheduler does its due diligence to find nodes to place all pending Pods. However, in a real-world case, some Pods may stay in a "miss-essential-resources" state for a long period. These Pods actually churn the scheduler (and downstream integrators like Cluster AutoScaler) in an unnecessary manner.
+
+By specifying/removing a Pod's `.spec.schedulingGates`, you can control when a Pod is ready to be considered for scheduling.
+
+The `schedulingGates` field contains a list of strings, and each string literal is perceived as a criteria that Pod should be satisfied before considered schedulable. This field can be initialized only when a Pod is created (either by the client, or mutated during admission). After creation, each schedulingGate can be removed in an arbitrary order, but addition of a new scheduling gate is disallowed.
+
+## Node Service Log Viewer
+
+This feature helps cluster administrators debug issues with services running on nodes by allowing them to query service logs. To use the feature, ensure that the `NodeLogQuery` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled for that node, and that the kubelet configuration options `enableSystemLogHandler` and `enableSystemLogQuery` are both set to true. On Linux we assume that service logs are available either via journald. On Windows we assume that service logs are available in the application log provider. On both operating systems, logs are also available by reading files within `/var/log/`.
+
+A node level administrator can try out this alpha feature on all their nodes, or on just a subset. Provided you're authorized to do so.
+
+## ReadWriteOncePod PersistentVolume Access Mode goes to beta 
+
+ReadWriteOncePod is a new access mode for [PersistentVolumes](/docs/concepts/storage/persistent-volumes/#persistent-volumes) (PVs) and [PersistentVolumeClaims](/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims) (PVCs) introduced in Kubernetes v1.22. This access mode enables you to restrict volume access to a single pod in the cluster, ensuring that only one pod can write to the volume at a time. This can be particularly useful for stateful workloads that require single-writer access to storage.
+
+The ReadWriteOncePod beta adds support for [scheduler preemption](/docs/concepts/scheduling-eviction/pod-priority-preemption/) of pods using ReadWriteOncePod PVCs. Scheduler preemption allows higher-priority pods to preempt lower-priority pods, so that they can start running on the same node. With this release, pods using ReadWriteOncePod PVCs can also be preempted if a higher-priority pod requires the same PVC. For more context [see here](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/2485-read-write-once-pod-pv-access-mode).
+
+
+## Respect PodTopologySpread after rolling upgrades
+
+`matchLabelKeys` is a list of pod label keys to select the pods over which spreading will be calculated. The keys are used to lookup values from the pod labels, those key-value labels are ANDed with `labelSelector` to select the group of existing pods over which spreading will be calculated for the incoming pod. Keys that don't exist in the pod labels will be ignored. A null or empty list means only match against the `labelSelector`.
+
+With `matchLabelKeys`, users don't need to update the `pod.spec` between different revisions. The controller/operator just needs to set different values to the same `label` key for different revisions. The scheduler will assume the values automatically based on `matchLabelKeys`. For example, if users use Deployment, they can use the label keyed with `pod-template-hash`, which is added automatically by the Deployment controller, to distinguish between different revisions in a single Deployment.
+
+
+## Speed up SELinux volume relabeling using mounts
+
+In this release, how SELinux labels are applied to volumes used by Pods is graduating to beta. This feature speeds up container startup by mounting volumes with the correct SELinux label instead of changing each file on the volumes recursively. Linux kernel with SELinux support allows the first mount of a volume to set SELinux label on the whole volume using `-o context=` mount option. This way, all files will have assigned the given label in a constant time, without recursively walking through the whole volumes.
+
+`context` mount option cannot be applied to bind-mounts or re-mounts of already mounted volumes. Since it's a CSI driver that does the first mount of a volume, it must be the CSI driver who actually applies this mount option. We added a new field `SELinuxMount` to CSI Driver object, so CSI drivers can announce if they support `-o context` mount option.
+
+If Kubernetes knows SELinux label of a Pod **and** CSI driver responsible for a pod's volume announces `SELinuxMount: true` **and** the volume has Access Mode `ReadWriteOncePod`, then it will ask the CSI driver to mount the volume with mount option `context=` **and** it will tell the container runtime not to relabel content of the volume - all files already have the right label. Get more information on the KEP: [Speed up SELinux volume relabeling using mounts](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1710-selinux-relabeling)
+
+## Robust VolumeManager reconstruction goes to beta
+
+This is a VolumeManager refactoring that allows kubelet to populate additional information about how existing volumes are mounted during the kubelet startup. In general, this makes volume cleanup more robust. 
+By adding `NewVolumeManagerReconstruction` feature gate and enabling it by default to enable improved discovery of mounted volumes during kubelet startup.
+
+Before Kubernetes v1.25, the kubelet used different default behavior for discovering mounted volumes during the kubelet startup. If you disable this feature gate (it's enabled by default), you select the legacy discovery behavior.
+
+In Kubernetes v1.25 and v1.26, this behavior toggle was part of the `SELinuxMountReadWriteOncePod` feature gate.
+
+## `JobMutableNodeSchedulingDirectives` graduates to GA
+
+This was introduced in v1.22 and started as a beta level, now it's stable. 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 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 and [scheduling gates](/docs/concepts/scheduling-eviction/pod-scheduling-readiness/). Find more details in KEP: [Allow updating scheduling directives of jobs](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/2926-job-mutable-scheduling-directives)
+
+## Mutable Pod Scheduling Directives goes to beta
+
+This allows a pod to make pod scheduling directives (nodeSelector, affinity) mutable as long as the pod is gated.  It gives the ability to mutate a pods scheduling directives before it is allowed to be scheduled, and gives an external resource controller the ability to influence pod placement while at the same time offload actual pod-to-node assignment to kube-scheduler.
+
+This opens the door for a new pattern of adding scheduling features to Kubernetes.  Specifically, building lightweight schedulers that implement features not supported by kube-scheduler, while relying on the existing kube-scheduler to support all upstream features and handle the pod-to-node binding. This pattern should be the preferred one if the custom feature doesn't require implementing a schedule plugin, which entails re-building and maintaining a custom kube-scheduler binary.
+
+## DownwardAPIHugePages graduates to stable 
+
+Support for `requests.hugepages-<pagesize>` and `limits.hugepages-<pagesize>` is being added to the downward API to be consistent with other resources like cpu, memory, and ephemeral storage. You can find more details in the KEP: [Downward API HugePages](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2053-downward-api-hugepages).
+
+# Other Updates
+
+## Graduations to stable
+
+This release includes a total of thirteen enhancements promoted to Stable:
+
+* [Mutable scheduling directives for suspended Jobs](https://github.com/kubernetes/enhancements/issues/2926)
+* [Add downward API support for hugepages](https://github.com/kubernetes/enhancements/issues/2053)
+* [Kubelet option to enable seccomp by default](https://github.com/kubernetes/enhancements/issues/2413)
+* [Default container annotation that to be used by kubectl](https://github.com/kubernetes/enhancements/issues/2227)
+* [TimeZone support in CronJob](https://github.com/kubernetes/enhancements/issues/3140)
+* [Expose metrics about resource requests and limits that represent the pod model](https://github.com/kubernetes/enhancements/issues/1748)
+* [Server Side Unknown Field Validation](https://github.com/kubernetes/enhancements/issues/2885)
+* [Node Topology Manager](https://github.com/kubernetes/enhancements/issues/693)
+* [Freeze k8s.gcr.io image registry](https://github.com/kubernetes/enhancements/issues/3720)
+* [Add gRPC probe to Pod.Spec.Container.{Liveness,Readiness,Startup} Probe](https://github.com/kubernetes/enhancements/issues/2727)
+* [Add configurable grace period to probes](https://github.com/kubernetes/enhancements/issues/2238)
+* [OpenAPI v3](https://github.com/kubernetes/enhancements/issues/2896)
+* [Stay on supported go versions](https://github.com/kubernetes/enhancements/issues/3744)
+
+## Deprecations and removals
+
+This release saw several removals:
+
+* [Removal of `storage.k8s.io/v1beta1` from CSIStorageCapacity](https://github.com/kubernetes/kubernetes/pull/108445)
+* [Removal of support for deprecated seccomp annotations](https://github.com/kubernetes/kubernetes/pull/114947)
+* [Removal of `--master-service-namespace` command line argument](https://github.com/kubernetes/kubernetes/pull/112797)
+* [Removal of the `ControllerManagerLeaderMigration` feature gate](https://github.com/kubernetes/kubernetes/pull/113534)
+* [Removal of `--enable-taint-manager` command line argument](https://github.com/kubernetes/kubernetes/pull/111411)
+* [Removal of `--pod-eviction-timeout` command line argument](https://github.com/kubernetes/kubernetes/pull/113710)
+* [Removal of the `CSI Migration` feature gate](https://github.com/kubernetes/kubernetes/pull/110410)
+* [Removal of `CSIInlineVolume` feature gate](https://github.com/kubernetes/kubernetes/pull/111258)
+* [Removal of `EphemeralContainers` feature gate](https://github.com/kubernetes/kubernetes/pull/111402)
+* [Removal of `LocalStorageCapacityIsolation` feature gate](https://github.com/kubernetes/kubernetes/pull/111513)
+* [Removal of `NetworkPolicyEndPort` feature gate](https://github.com/kubernetes/kubernetes/pull/110868)
+* [Removal of `StatefulSetMinReadySeconds` feature gate](https://github.com/kubernetes/kubernetes/pull/110896)
+* [Removal of `IdentifyPodOS` feature gate](https://github.com/kubernetes/kubernetes/pull/111229)
+* [Removal of `DaemonSetUpdateSurge` feature gate](https://github.com/kubernetes/kubernetes/pull/111194)
+
+
+
+## Release notes
+
+The complete details of the Kubernetes v1.27 release are available in our [release notes](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.27.md).
+
+
+## Availability
+
+Kubernetes v1.27 is available for download on [GitHub](https://github.com/kubernetes/kubernetes/releases/tag/v1.27.0). To get started with Kubernetes, you can run local Kubernetes clusters using [minikube](https://minikube.sigs.k8s.io/docs/), [kind](https://kind.sigs.k8s.io/), etc. You can also easily install v1.27 using [kubeadm](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/).
+ 
+## Release team
+
+Kubernetes is only possible with the support, commitment, and hard work of its community. Each release team is made up of dedicated community volunteers who work together to build the many pieces that make up the Kubernetes releases you rely on. This requires the specialized skills of people from all corners of our community, from the code itself to its documentation and project management.
+
+Special thanks to our Release Lead Xander Grzywinski for guiding us through a smooth and successful release cycle and to all members of the release team for supporting one another and working so hard to produce the v1.27 release for the community.
+
+## Ecosystem updates
+
+* KubeCon + CloudNativeCon Europe 2023 will take place in Amsterdam, The Netherlands, from 17 – 21 April 2023! You can find more information about the conference and registration on the [event site](https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/).
+* cdCon +  GitOpsCon will be held in Vancouver, Canada, on May 8th and 9th, 2023!  More information about the conference and registration can be found on the [event site](https://events.linuxfoundation.org/cdcon-gitopscon/).
+
+## Project velocity
+
+The [CNCF K8s DevStats](https://k8s.devstats.cncf.io/d/12/dashboards?orgId=1&refresh=15m) project aggregates a number of interesting data points related to the velocity of Kubernetes and various sub-projects. This includes everything from individual contributions to the number of companies that are contributing, and is an illustration of the depth and breadth of effort that goes into evolving this ecosystem.
+
+In the v1.27 release cycle, which [ran for 14 weeks](https://github.com/kubernetes/sig-release/tree/master/releases/release-1.27) (January 9 to April 11), we saw contributions from [1020 companies](https://k8s.devstats.cncf.io/d/9/companies-table?orgId=1&var-period_name=v1.26.0%20-%20now&var-metric=contributions) and [1603 individuals](https://k8s.devstats.cncf.io/d/66/developer-activity-counts-by-companies?orgId=1&var-period_name=v1.26.0%20-%20now&var-metric=contributions&var-repogroup_name=Kubernetes&var-repo_name=kubernetes%2Fkubernetes&var-country_name=All&var-companies=All).
+
+## Upcoming Release Webinar
+
+Join members of the Kubernetes v1.27 release team on <date> to learn about the major features of this release, as well as deprecations and removals to help plan for upgrades. For more information and registration, visit the [event page](#) on the CNCF Online Programs site.
+
+## Get Involved
+
+The simplest way to get involved with Kubernetes is by joining one of the many [Special Interest Groups](https://github.com/kubernetes/community/blob/master/sig-list.md) (SIGs) that align with your interests.
+
+Have something you’d like to broadcast to the Kubernetes community? Share your voice at our weekly [community meeting](https://github.com/kubernetes/community/tree/master/communication), and through the channels below:
+
+* Find out more about contributing to Kubernetes at the [Kubernetes Contributors website](https://www.kubernetes.dev/).
+
+* Follow us on Twitter [@Kubernetesio](https://twitter.com/kubernetesio) for the latest updates.
+
+* Join the community discussion on [Discuss](https://discuss.kubernetes.io/).
+
+* Join the community on [Slack](https://communityinviter.com/apps/kubernetes/community).
+
+* Post questions (or answer questions) on [Server Fault](https://serverfault.com/questions/tagged/kubernetes).
+
+* [Share](https://docs.google.com/forms/d/e/1FAIpQLScuI7Ye3VQHQTwBASrgkjQDSS5TP0g3AXfFhwSM9YpHgxRKFA/viewform) your Kubernetes story.
+
+* Read more about what’s happening with Kubernetes on the [blog](https://kubernetes.io/blog/).
+
+* Learn more about the [Kubernetes Release Team](https://github.com/kubernetes/sig-release/tree/master/release-team).
\ No newline at end of file
diff --git a/static/images/blog/2023-04-11-kubernetes-1.27-blog/kubernetes-1.27.png b/static/images/blog/2023-04-11-kubernetes-1.27-blog/kubernetes-1.27.png
new file mode 100644
index 0000000000000000000000000000000000000000..cbfceda4b8bdde712a0914657155c51004fdde24
GIT binary patch
literal 232585
zcmeEu_g7R|({7_OIHE9$1OuYd<SYV`RTOA)kQ^mSP7T;(M-deSJmf5?ksKu_5yb`p
zC5mKez$QwQ^WEq0zTdj{54gX5vz80jxKEwEtDbu5soF<hYN#okId$<A3WYj@QM{*x
zLQ#E#f1Ugb{GY^ItvD2l;)$J{oQ8*%!riNw`*NZ};-aE_H~586D9$&YZ|anf-}xt`
z39WRG^{)!WhiB3DbZqh`f9j*Rj=fjBzGV*y(_V|1;=l86p*aud3(>|?`_vWm1(bI*
zPn7l>ewY6!Zu{(nQ2E!cs;1EkUbY`Dc5)gte4rXKzC#^BHR`cS?Yt{2YJ7|IiB22q
zDRF}#yU2g!q0p3SnnC_SO<<w5csh@{-MK584+^hJU6XomsG&N>u%yvbYCWm_u$Z0k
ze51(v<6tutHJz;vE53^~Px`qQ)cRfPpT|_h(#OV45o}(yFZ+LuyLGN+=tV34iW;^h
zjIOm4o%!sfU~|b=ik&~b0z7lX-2k%f7v-Ys<w}3Qrq{~inxKEr*-v*aDuctyiZfyV
za9B@T{CDvK?-S`O1i`V|4~>-5svozcZibQ1{<t!EU9Yp7rTJUk?<Aeha$2W(S1*J9
zUy`nk6h%}b_)h`oq-v3bXM=Q)QbINy9+?)bEqJF*`MxM3=$U+2y0Z3VyE5A);g{|H
zxxJl}DAZLH=H8tLkCPWhaTQtKcb0Z-)uq)*SdP(@bUE8&5=6G<hY-fhD$+yegz4nt
z^AV;Lnio#osZry6tYdu3bj>tbQ)+Yih2rhMxP-nwL*cHSd8iZ>|3U4lhquqzY{buN
zDUr{z>NXDgi+215@^pN?z4ICyboJBchMKC*0Yv=ofB)-&|MkHCe-8vvBylpsuc0o?
z&7a1oN&TvnAYh@~x|-30d8(+9$E}OcS(jYwd`BmP_l@9%Pi<~fp-|>oH$6q(5Q*qn
z^iV31qGnY;zycCE9`JJrEylJj4|PC(>-<$IPQ}BL6SF74V}E@OqCugWGy41b@oORE
z;WqNH%hM}gBKjSn!!OKFcXFcqt`ov52bsAqz!hQS!_o5Zef_zZ)M#Setg}(*U(9tz
zQO5BH@dq!_X^(tIJ*}g_Qggox-zZQhCPP(|lxRuXnc-J|@r4y<%i;qC33WeBtMXlG
z!K$z`$0fiIx$NA0Dh`}8G>gWWPbT-+^vb3O1VG;GHCc<E<wy3gh&|4t+<akZ&vobH
zws^3|^Py=HEoqjc=Ix^AF7+m`)T}7<_BaZqaZg*%DC#DOc9vEkxtwVfBAQ?ht`n$+
zO}(p;7xVi3g$2tQRJ8TzFmq@DWpY@Hc&3#t)TBZlbSkbZ!=46z%&Uv6nlaJV>xkN`
zS_|=rdz2;{5>?N!uT5IE_Z@xGA`O<6ykmmT8ZV}5;-p6Yg%(gMOLy(6t`Q}Sqj4U?
z^Nm^(u=f~_BZoac*w=pn6CgtHi28cI>w<SVW-OLi_0x1PCL9<EdUzB`^Tb+-Yx|RX
z!5BRC?4QLhb@EQ-pnn+_6amy}R>V+SL2iBwCP0Re4;9q19R40#Q-7!4sld4T`#8ol
zjwt6;oW#croPqk-f`m=eVa{HHpw7O%j!x=199b;B;#Ma?P{lYmCJh%l6-)ZHPVuJH
z@k#y)z(JiDH8uD4k;N~?ah-?b?pgjf_pj~yKZkuL2s_v{I<eLeB3>Y+T|HESir+UZ
z%~1LQ09=Bk(1edrvY2<ESN&K+lS~4U4Y;!e*>^PY3?(oiucWP)4<#oZyghh_R#!Vb
zFF8JB#<rbZIk?Epd<-mLL)^(^=fTm>0uggPs@gaVv~Jp0k0u|mZ65+iP@Sp*%bNea
z0dGZ67i=Yg_>vSs>Q*@{@7wk=Qz7?M4(>aU{sF7>IguEC*45UF0!w5Qi9;COIKGQY
z%ZlVzm4ha_5^y5SBvHT#2i^31FGbkQk;TjM5grU>q?ZZochokeFM5U?y|NyGSF_1Y
zPtUv1EC<dGiaIrWI*OKKyA*_{0XgPZDkMB3Pw_>uXgjF>21e(Wt^No^w1xIehUaaR
z+u+S#MesZ!`Do7mIws{H@}RFp{9}eHxfi&r@hHr%kUcGh;ETFc$sL$f?ON-T#xcZg
zr{eh-8W<~gkXSTpKAM};!~_Tsrj)8qKN(jiCjwXUA+BsgLXT3gTk2VojU;+Q$vU@k
zD)<Ss6%9+|o@-zut`(<$!#~0jYZEbKZA^eP;d7bDeUqev7Y8qoR@_8Z2wqh+Da0J!
z+zC~xI$t3`PzNRov*p0E69-5jnuA0<*GDl2QiRGLKFS7u0t^dRBnZ{TcqPD3sOEP=
zr5=NWRW8G8jF?ys9QN}n)sM7DtKAK!q_GCe*`njwmaxG_rZ&bu;5Q{84SZDKq-^ft
z3-*)P@4nxZhd9TNBPtsNA7vg5UNVL0QYPnQ8=b;EhSb3(ULgDalXB|`U^f(XR&G9v
zD)|r}Xt(KB&Oy)~Hr;%4bTW11WF<l1Es9VThj=DdnW74fb041P=SBSI-NrToJZ(+^
z-m;3h@`jiO4qqZc*ahiXjBI3t8HqM;N#)>ZG|>QKnqpPy+I80`j%b!tE0J@wCPuj$
zZ1(mYRTF73!Z>>Z*JxRDkt(?r;LlJ3jR63Da}YyuB>_<PeAH!GZ=*C~HM$C>Y?ra=
z17(a%4AH@<_)-<i3veDLE(Fn>ApMtB51}O<<tpBi{3t1aQZu7398LgGgi3S-hWxu`
zmz&ThB(rt~!><&ma`*tE{%Pv{QAmaz_R1HS6i{++bMqC@ICbbuwh_Y*dQ4;fqNiTh
zAl=t9GZAX!tP!C^m*nDE$(ASRWmWP3dbX;;dGnYQ2Y9lr`N%*<ZhkpbFH0Ec;iF!N
zBAIphk6&e}$jx8J1n?55A*n}^5&q}BIJRfehmphvz%%;Q0182M58;XxbgieaKNfu$
zOI&~-?{q5m{ZK0NWyEf^En7BGmV?k^>HihyY6lIXaUtC*;0Y#v<n&B8Kw*K1tQa*u
z;7ikQ8?|CAow7gr`d4bEDz=YP8HxnTydm~G74K>w2;4cs@G}rMVM0h$vVN^K#iBa-
z8OU04<H2zd7+wMoBqd3JwofJ5E~}CAz@MbU(QB?2hH0ib(td7k1kH#x&;yT}#1JPz
z8TE7te3zRa6;&^@uRWV-?y|%2XIu*=6!T;xz0F?$G{&P@6w5NO9mjTDp;|y*OFNf9
zCMl8g(8Vfce(4_>nv<aVdQicXLx5Yuj>sJY;frjb0+qmbCb-tcFUxW4399Z}FLpn+
z{c)&^8c8O`4ljdh_Gs*|EEE(mbqrYmgIB8JeJcyflCsMoJ~uxX-K~Duw~e>Zp`N0{
zq>gUX<|`p@xCA4%`6OT-3Bu>KkWX|G)hUrys!RUooA!4TC~2E~t0LyA#+_?AHaFLN
z2RUja2x7ygVs(FpR`YZ7<Jh;K_ApZ~Z~@;A;)~|cE-LQMq_>o7pU}e!E92JxQ^T0F
zJUCj^6$4K;%?kz$4zH|ST=v@SW$9U7^6EcpHeMG0nSd{1hw9k~5z)>DxAi!-jiH<v
z8ZKhaPt(oWY*yfm&o9OFz>iaQbM^)h6<VB?K=RnMMT?8<Yx?=u)RvY=Zb}uIB@lTq
zMVIhz8gldLF*31P+@mf3{)i*G0VaKS6hVY1zh>f#baQ0GS;Qm957r4QwT?eV<B1)Z
zMr_<}aYci(`pdWYqDr<JPJ$a-YTA=p5dtM9)lDF9<`tUO#dlPUf&Fg~*m_(hDCQGP
zBA%Ycknrjv2SHu^5G|fbk|i&G+=+vXzi-sat!}phMDY=tTIY8@&Ee5vXq?gTyeW`b
zIE-l&V2J}kLMX&5`K!CBY0*>NWJ?8jZDlH06vV~<=H`XI95&n|Xf?cAw#J;{qpcZK
zJQIFrzXzSBN)85U>~de!P0#gVjH&dyHp{V*L?RtVCYk608ROJt&4D<33K>ToC`j&U
zLxmnqp4!mVbJ7%C<>X`FiZbC0RALnIPR**u!8f#nvRCQ5Mb#d*?X|O20)W$-zf0)@
zz0<=o!*Z+S?qAa#n6YHyKE~^EC;i`vwLc??#Zi5vG<n&oMb9)AD>N`W-UTy3SVK)W
zSF!tS`d%_xS;<R?VS}yamV$VmnCJR$G>hsDahKo`J*udBRze!vcGaC^2A4Ve8wBmB
zdSRqcRE4h#0j90?hSS@;02E?wLS~fI4e!%4w&!2}D=8U&@b?TYh|a#If1C8{IaQN}
zYXlxf{)oC;(Zph?zG%@iuDgxyre{AIhZ&x~BE}K{6lOCsocGO&K>GMYZEU!^P#Xs*
z61f?gu7``t<QjCElKUN)7OQw*7EV3j+9+?Iew{tErk>oC2M9G~nZsdjE)b2=8=fyp
zTAl^^gvl1!BGB5NT03&vQ@t#m-CRZ|R%b#n2mVWy9E5E)%g^8LV^XXBnc7|iW!2et
z^h2<Z3<$BC6-;^zg)r`uQzbu>InYD8H&3<Ka1nm?oVEPbjSzt^LIi^P$ZNiXG`+D;
zH(f<L6QN#K^XR;wb3oyuXOpG`*h<j0kO?fHC&qxkL<pN~IK!Q%+iupOK|&h}n1FID
z9QD<<zhRfY15r;QmSR$cyoXIIPhQ24y)mid8?_&i8XhkTzwK=`zDN{}^8rS*qY8M8
zPPlR`E0KYcl+=J(Eoj>s*}pNYny(~EswK#Bo2H>Yk}NT)BOA5D2)zg%*53g#kM{-0
zHa46)Fty1xq*ZxxLh@${G5LQ~618P5q9$trBeQxZ-w3pT*sMcQOL1m5QvuzEF~TGz
zr~%UGDp1N&0tC5Jv#8635onw?39vGXAr`5run1PgB(5o}Dlm3Y+|u2J9spj_LO7ox
zmJSZSrrq3JHM(0V@MfSEM98><db*nb*#k~EBpOTQV598Y2f#!QTLK8Aplck*_I}S<
z@RDexNG<7T>nTS`iR^#h+l?yV1S^UI>Hv`|DS#y!&*7Zf5>+)(%?>o!n9UAM*zmmn
z6vgnlA9GNP1YjE0vq5MK;<Y!#CJsBuk=y7*$;22aTMY=&akjxJWC^+(@RSk6$Sz*&
zN^_fQkPYX7oVFcSSk3XE1f^q4qlpSo0eA9oji1Y)9DDy?3zz^=-iKJ!0&fLcO<oRq
z=q5-=iwg(4d@BXJGwcZ<xSYV38!XCYm98|+B{+3}Y93~gceinH{FyXWP56|_3v230
zfqJlkjo2RWhp5wtqz#J)N>uHzVtX~JKp^?J;DWP~djRtG=TBiL$lpf%Bn;XXjI{%b
zA*OQC(^naGlHg@H4NE{Zd@oMuX4}q1UjotOl@Bz6(Hk@gyE*9oqoo^*#VTY=OzinC
z3jKm2HS%{P3a4q|&GTLdSl}k)N9~zIFI&V>p`*K?C>bGXaAe>b=&bHRIXSY)vgzP-
zoH#QQu#S2j3UBWD18qHFOllmF5lYs+MP=Uim3{m6(dIiI!0RTu00F%BAI7I)$h4T$
zG~%-s3@X!p5lB=1QJ`Aakvw6dkr4*Scn%s&4nQ;zBZqhqcvtnUWFkw{p4#xdj0xQA
z1(m@E)&N9mi^hS7sFxKuo@v&fXWLFevw$Yqk;DXE$&d=~3{<zdvl!DDP!`y!XHl*p
z-RSLp^r3|!pb91dI4t_+9v`>oqolI2)Tqt5OpIyoMlCJU0+>I9v1R@Ql!FO$QvxwW
zsS4%VR4)L!HQ}SYHiHes+ah^X%(1=fmg^PtX(5npI|dP-NLC~6#{nfagKkPD=0Kn?
zr7#zy;n+?>7d!cmP9vh6i5HH-X>g?ZsCsUKGQ<lo(7g8}jR;t)anW-y7Vclo1>u7u
zy@C?C4BZ5D#pGp>3`^+1Na7}tpO(nU!(YQE57z{R2C5e%9L88#f@SU1*9gn#?J3Z{
zaKW8x^LM!2YSy%emC9<=o*|?SU?X_>K$zgdzP$>T2_Vb%En)oZ=H})T(A^mFB}^B{
zj%L?dAnBs&Gr<S}IY6}wyfs%A5qL&I!UXVuzKkm9)8szJ^yfycGD5n4QefRSAp<(9
z1$1CMF*n-?rH`e-AC5<kgRpfT8A1v`H6u`QYGfXaX{;6Al?D|$T!e0lC%V8h24s40
zR2IE0m)sX+A)<GbBR|;GqwRZ8nuG7?eIz>7!mv+A?rZDODwEqVSBz>YgWiZF5e1^^
z@&EPc+isW|JOE9~5P;{e9yHxRQBUE~O^HNRSWUxlGatce|APuD1qp!N$=sfYF6)7#
ztyHjr?lll;zMF5sDpqg+bUJ=JaSp`*C%2(0Hk>se08Y5o5e$dD6PArHQd1&7M|bm#
z9z%J%89|4Vgk{kDRQ7<8KWeHK?4?;Bu#6o9NOBs@0|49Hu&o5alOKg6c}WeQ$ubjk
zC(2|hOcyUOwE5i;lEuJ%>8K&H-#*yQOgN7?hd^y;SpY0iAkAYAx+@3QkBr=ajj#f_
z`4WA|O1KnNz?Xa+_4E$_DB#Sbqczu&H6ZGRn1d#?Iv22V+)D>ytZY~sMcgY7qb%qR
z0JasN)a_ApK7dcNpN}#W2adFZ^njUghur)H1bhu0m`cP1YopB57nI1qDhC^oe!iI#
zR*xmW0c>K3v(TO{G#%`LdixBtXG0)`j1ajm1besS9Z>tt=)gC`QUIH`B`)lMAOioJ
z?LnX5j;lGN55x%4L*tyFY+%PcJ~@q;12Cflm#m;qpOH1aef@IKo;9Qp?MxAL%~N|P
z=ll4to4_N@{<Z+>=CCMWCkU{C2nfSQgtm6k0zhVTBF8=&G=<)UQFYjd)2XFIF(eeT
z;Y<NL=^)$vfw<q^BhB+59|%&bJb+(bU8>%uR~?uBi{IuFxaJ5}0O0WvjH0CQuBT98
zuYkk|7@qe+$cITD>A@$K0Q)SU8QUJypq{Svq0@k1;zBm^{0&@yPse})i{9Qx3vhx6
zu`Zp#1l0Vu+c}MZMGk<)1KR6G4=Y!JD!26jng#K3II{5sj^QsLqZG+4YwD>2JOBt&
zGqGq{(9kpqFazjnB*IHFz()BANl{YySZdcbd=9&?v`9=sZmx>Ds<n?j*{DfOG6`Lt
zkfLfc8}Lw+;CLu@LvnM!sxftUHN@7o{BYvKWhw0AYlqx|T?g!hZUCYI1R&Wk!*YUt
z3MiogbWW`E6E_hN@q}q*n=(HVRG?pm=85Gekh7J`u{JwKmRny<KCig=%SwyIs;k*p
zSR9y|j>%-P+<MHpOM4}`jyZAny=3E9;2-l1mRr%sLzcGQOYd&jZjSkjV}G2a-TWRG
zB?T*MWPGFXFMKdckkt<$GbQpo2H!r={F@Z<t14nrxy+peN%}YadI3gsU!%KB{_&-~
z{3W$vx6IdBW4yt|%z3oVWodB38kim`cL}8F?h2TtdiuRe7A~O=hv)YqU@gl7mj?z=
z8#&l;%Fr_Z=&{fth(szdsgZKfEBNx0zN6f0dSw6Av_Xxd9jX4lL-*O^yGsqb?j26P
z9#c!wHEx@!BNet09Ry+LgG03J&_?Z1?lHjAs~}2%<Um#OASPTO`B-QRnN4{{o?Mf@
z_u_-!5VUejT*fi{a-U1nsO$XFNUisHl}s<Qyh<Dq3~D#m5${vOBj@INpx^DFaSXYq
zhfgp}m)8V3<DhFhmDn#H(3w|YRC9e^x8Tdy3iVt1yfn-*$w|&EeX~o&b=$GVfgOdV
z`NGE<6SBaxya|DAybFBh86fIFm*oqsp31rHMn^|yP-lS?Eigy{maT#1p%NQU@FFdV
z*SIp@<;LX0+|bodBWJ#pV{LO9Ab+=6(?a2{2O+9e7#^6O&uqgN<g}xr44QnVtK`YU
z>T%sF;yN<UG?yi!X|ZNstPgQcr1MPAnlR*y|BmPcSzz8hjY#SMe!z74)E98@cAD(1
zD+|ox=mrZrpNr(XkL1N9B>#az8;6F5{C;)BO$(dt`oPAhqxLiai6f&^!AE1AKn}bG
zN+y=59<}#)@_f8l6dm1AwU;VvjBkF>dev>d3~N)1We9C%EUsriJlGbPDWR3OT^Wu6
zBfnC_>rY{2Yz~HRKcR!!6xlp1_356qz6WZ?-n-@j#-fErQFd__vz#XW`)6?7IkIUD
zR5a0QPb@vJ61qVLdBj40eS#x*8*oGXTHC5>w$X$>UrIt3erhMDqv~=MKSzPll>5Tz
zzSnh|#8F017)U)_f+qtLiPm7UVg~cngg%byBr3>qps!z@9j6Vk0V9t<KF?&Ww@vrG
zZnN#!nJRnOnb(5}djhsVY)ISoE83YkldWz34`_(RfgObJCiLMPzGbg!(uu}dLTP-X
z$2JG&raQ_!r=BN!wXBGfw$>9;6M0iwnIxnnlc@P?ZklaH<SXYiUo}o3Cj8GF;XBNT
zt`C4);)za}RQ+1YrBK4lmyQz7i&gTg>-i}+Y#$rfufFnI3pL|Pp?F#%Mo<Stwv3dk
z%g9~FrV(IeRdP2xw>q|IGXy0#jz0FQbRLP+7Q2#`E!>+OHF0He#M5Lfa3vfN(mU*_
z(=85B^*~COBYe1oh~Z6TZ9Um!(D(9!+Uafk5oE&Rvx7$gziLGi;{TL|e446Fav{_S
z%)!`2-1>%iA5jaiTN}x0;5v5`G$h&>(==i~aH}GK+)#zHQ`b*-iz}|bJ{K5QR$$Lv
zjvDpdoE}YEavxQ#0ujFR*c)O2b!G`c$!0K|;>%zH=7||gB$9v`uS<hPT?t8I(_i^G
ztoqBWvpvk;(p-^<-t^yq{Puskz&5t5phF<a29adkQiI_?k`H8uDtQb|%RPE*UbpCr
zfsrU|!e+Fc9+)s?PEF~gl0E!n>@zI_2e%O-+JUGPAk&=&SR}ee0Qwgr_(G0cqb*y8
z?;Q=gM%*pnU!p|@CK6N(eG3bYGF~J-kCiSSB@kFp;{8FVsDhMTUkiZu31?8gr7;Iw
zgv1`cu(WCASmIhI2eANb1LTa->}|KSngz1oUQcmsSJ0hm5kfhbQyn0l@P^yB<|-iM
zYcL0*1Qim)=QhBij>8o~w$3s_Iga{iFaH+Mn@}{XC(rr)S&g&t@~Xt1x}5(M6Ogg!
z>B0q<F;~5@H^)#DYCxjlAhFmbb3Xtqr^+;UE%+FCb`Is)W{o<>LC=%?_No8<765l>
zD?mv97y@H;&jK2E@=ZxQ1$6jxxGhC`&M3@SBym=`N^mDuMSZp)N_09|TfKcHUoWQX
z$^GfMd6zGB0z1YVEK>Rslz&Y|M8TuT5CpMkm?z;Yk(&fFpdLsJ^22{S3|j5x?)T0J
zYionRe6L-aF>*f$W}L0u-$k}ijFtsrx&eVI99g)feUBMSCHg8=2`1X$@$NIR2X?Ek
z9rWV5p1g7EO&un8QOhPJZI0-|ub0CFlq`CRMbm&Ie1`92%)>y>$Oht?Y*ZWky&NRF
zqwIQCa)Y&p4L(IQWV^(6ys>_@<-gqgw1kz=3yKE|yn&z<cwE7x4SF9=f^Sr^A+R6>
zM1inqTI6C*YP9P7Ky25O(vs!o5B0kl{DUK|mN22FU>ZSp9~X!0Aqw8ZX#k8L=vfW}
zGhm^_>k~QI_a~S5ZdRv(gfPI?=dKTOA>_txQ>fT%_cfetaXGRX%g7Bv7z+@o&G7&k
zR8f0!kaf0^{+?)&NlJ**aAL1mN+f`Vz}u{k<>lK|-Tp#mwR4H^^Lkmb8D_}M6qCT%
z<S`TzD;Rfi5)PxR%COX-!(5jJW*_FbbQ0R?UQnElf-Ay8Pw~vJ6g@b<s&DL{-OoRA
z0NmLz(W#p3D?#I&qaS{Whzq^x6-$eRUk?ghTo=XCCtLnHDVC<bnJ<df65z>>qbJSb
zC*8nQ16HbLAgO-c1g@h>sTZFG&-QniY_l+gGV2+~1U3<SdM*f_97J!YRt|16UIgtX
zJj4q+D=L=S#7}Tgsw&yyHM$WM;wUXX>nzRI5ewuBMR*Gvc$hluci3|iQrf*k3pf$Y
zD_~(N-#7C308BS^YJ)#nuam8DzmKbRK2-<0BsaH5yjkc*hVb1Y)kE}7IGlXVzhPDm
zdt0-zw+Zd}kr)^vz{#fTos2wYX6S^4CbN%)LCQtdHyDk{*~muOasfiNk!K%~i<nT&
zFA^?wA6_LWgPq<gFnfO^LSlXm<ZdbUlwbsZ&0f24$;TI6id*s!M^ytDmw;Riy8?&x
zBxr<g5Lh^HZX|~1<B9Ygt6zkxrWc|_W7H@ZUYt!i>+Zk9x?_uUmYHxl6udt3c~w@G
z{BIB6=_-2VxS6J8oZ%I}c1!{`*NaIqt!b~_@5_s>N1zYh1Ol`d3B~ux(Hp><g20>N
z1odd=hmZM^5(qdD{~9B8!djmd>GIpFtP-rm&uDcZa&nN|&4hJR$rq$)5rCwcu+$&z
zY<#%;?Q&-7opNjlYgp1{b4BB=m=1Do@d7U>R<7DRaUM;`z`SG&4g*6ez6c++=LxZJ
zCAa*On3()k+(^Csqq;0#M;tF#%JI|baG{JdcGDr9W_sp=-Yx>ey&9O3ORACQb3sV>
zFsUGMCvO1UQKi<4A5MRDGI$S^<Yn_0on2is{%H+pv)yh7m^+L?-{e%hstw0f6Yi&Y
z@4^Lpdl%ge;P)p!KK{#vB(*QB-9KYJdGr8;7+%VS(9Z6un<VEq;^g4eWyYj}_HZ6?
zcqo#(Z$OAJ&>^Ve*+xuPj0TE3rmpzuA~k_h{~2Jt_`sc3Tk`897p|0JPyei}$<q0&
zBT!s{%L+VnQq7i4m8}B~d^lZ}jaxY04Ob^P!Zkp-&$7q{XgZI17{RX(#E_r<cUG!z
zj9huTjw7FBbVGZONDS>sz=^ow${9OaUqv<jIy{y}@R$ug$NlHum&h^s-qRE5a@ige
z`Y8!Sis34!ompl{?@nZ_!T?wO=If<kJT<NaR4{XNmFLvTcB8@ragWuP35m(PDaXSi
zt%Zffx3|`}d-?~7e+oL^++Q9+JHVH%2f$E_GvHK)zY#m%`ucgGJsT2DyCG1$sm4y-
zuve{>ZIotFtoGoT26gWD8#mGhW8s>Qg&HKimUa{ox46OG@aY<SQGgU7Ny%HI>ucYG
zE4YD5zh${9+x@(lY>yxz*S$F%algl+|7BDTm+?wc9@v9F9)^eD9$XpZz~q)ik-Uj9
z&hb@AshMt-nmVgfnObrU=vCN=d(TSSG^}EPKtyCiG3=7P@RT}!q&Ye*w%kmCI-QFz
zN{uJ_V`5{SA5Jni`RJsU>@PSPG!=p5{fxwS@5lX`gMm?4H*A0b`SAP!($@>tBf9|V
zWfd}xwDJVRF;JF}AVn^45})mhx-r=*E_lNEr-#wl#&_y+P$OVsu0rE1Ko^ZP{Y+|O
zZ;qpoi^v#o5h)5b@GzxjyH)Dp?vO#H6&`!4ImLLpbAGjpTA&N44;Ud1QGVbeq0tal
zw@flHOTrhR7>rD!l>^v7*Q;#h)mD$Lu1dQ7uO|fSWj5Cjzl1dXnFhSYDcQ^Ny%<pn
zr{Upvb0io7_(QZDI9K?|<LYC{ZPLFBcvBMiQ;z*%_J2G4M!;kpNJ?`JekJ&#bM&a7
zT+xOv&J{t65Ch!S#WUK{q7UR!s{5F@xXbVWkk_$Y6xHf#V<j?X4Ks#mAzkl&K*Y7h
zVbKQvwk{Je*#Mh{>k51U&4w9!LwpH}8WXL|bQT=Jfnrkw3Cf88fXT0TPX`ZD%wTIy
zy72WbOj#g!oP{5zPh_49Ux%x*ZP%e?HEM&mt86}zr4}F3VmyCxB_v|!F6$@j@);!(
z2rq#TF9F5&whzR=_A#(whV(kov%-L+;H$ywgfuiv!83!ct@o~!trMkY7J7xHr)~A0
zd~)&f5<T>rwDpKNoASL>l3)p_zXqoM+XmqcV8Fi$F?B19)yD9UzbeS`Mg;yb`0QbB
zrJ|xj^vz#15Ea%2s>IqF@)q@cUkYPa1G!V61YOM<difR0qss<BIOnQKvPH=3V&fdB
z<OjM;4wD)rBO-Qrmm3aK{41909EYGnlZy^7nQhfSV-$~ZMfRpw*s&Parj)I7sWYm@
z^)meI)mHP>@6kG$EzRfjGJP%jSULsWRqAV{mK~+_!{qA@<KC}t3U{-pU1c{#ce>1^
zPOk<ukgu0|j&JIHj+OG*FPgv7KS=wnBs7{FmL=`Gxqd>G3Zy&A{4YL1@WYMa&#ocb
zUk)0?GPKIy@ru1Nw~=e7oxLEMYCsuTd#bFwqPjlg4e3I!CMv&AG4D|>-=V$BcnOIY
zJd8U17Ss~dKMKX+l>3!gH+l{Jxun`p?^BX*Qj>52pNYC{{D6^u?(4S~vAVh{3I>eD
z!`b~BKd`6Kcr^@Nga1caL1qAV)a^Y@fEv_`sG#xLH)|ponO*~P>8f6?K;QD(DyNu~
zH;bsA7o*PFZqAkAo3x4HW&GB-8pAWe?=PN82>-Vg8>sBGO%2T1svt-E$E>~_nEQu{
zqN$smqzyR>r%(>?baeMiIuGYA#++tAMW%97Q};bEc_{I@Htg%yx%4DIck$nR%{oJD
z(r5qd&K<evAG7lSN2p&@PoaP@>`DC&oATW9N_m&@(atYkD7)p@&x_<*6TD@?P`kaN
zD25jMzQegZA^d4;v;ax=Sb*6R(pA_=ze3syfEf$kiA`x<k_+3)lHV!9TJ`#E+d4y0
zJ%aosC5ni>6;1NWcX`~0jTYhg(xoM*Q$sGhf%W3Vxw96%LVH&9#RjHVx!iJ;fWJNq
z`jLtFU5=uu*raEWtwz=MiKi$%<J@ElGj~^~C^IGMoRXV!IR9&PJ1;i^u<7<=F|U|c
zPgAY(ZhFaI9672AcP;XwqKAjY_R{cA;a$FvJ_V>3C3No3ZaZ3<FSixTp#Sk<)%?tJ
ziP8R_oN-Z2O2?b~qi1LHHe1;4t56v{{ba7e{9dGN$T5$bTjOx+*-UJ#YTI3l+M4Xj
z`lc$Et+z+Vw+Qv#2Zk-KPHf`Xq`7kYfnioLVL6wjvGhfHYZxVWJ6!ANHSZm#)5d3x
zXmDQEmGca)=Z|v~O%jbePioD+Q}{f-?{&V<+w96c!dT-ZMeiMW%dO#~pbbF<J)rxu
z>j+(ms~85REq$#M#@vS0Vy0&k!;hgb>G{r~<nkM;ZTeA!nr)T?-^#&E=|+a9c99dt
zQ0mDof82l0&y1XZV3!#akx298w>UG+Xzy6ou2)6-A~rGnI0^%MqjJWlS7^ZMmnS6_
zlgGuSWjo3s{4nygJ)8ebKNUNiS6NpPI}E3`{9WSKa_}BkeZ()AN|)6stM<phht-0g
zyML#V#3Xie+Y;FMsbiMk-qPAlV|fe;_yki43RQXsbQhqkQ#84RWCh+#IsQE#IC)|q
z1%y`!gcthRdBzjZI`Xam)NijO)y>66F@uXYB2Qv|Spv}8!bJpynn$v#q&eUF;X!^D
zvHB1FV4tpbVcL(OJKs;Bcr^^-i#yrw<1LK`BO+V_RbvM;eQRi$2WQ??h)rx-C(!^p
zMl~BEIgqh7#~h#5J1r^nChM|S-IAS44>RAHvZ3mM^QZ!M4}S~q^x}f&H>)cA`qPGu
zwX&S(t=-g~p|u1^+9M%=B2ZZjh+Dq<Hf2>M(L8zGvG#avAW5=j`7+AlEm}a~{d6|G
zk^axsO*65do!o!mc25khz02}WfSWB;vjj~q{1Y;0Uam9fVQhW+5|hs>tLIWzqfI$v
z0Q<F_yPYubW_2H!(Y7-!YA3H2?RZ>?(@uAVf#s$ajCMBzJkhkiaRvk!KHF8F`tQ_0
zlimSoq}W3TCF9G@Efe#2)+&?gqDd?906tuWf|AN-bm)Q6-uFv)0#$8IUYFJT6*r4m
z|0etYPWTUYu22FX2Au(D^1>WmwJRs_>dV%3;)j#wJ=J}MEpZfA)x4a?x$F3ZieEL3
zo%F`Ii(jtIb~8%uxr%wOxKj=5Clo59tu7e+xU`xCUAf78Y<||WZtYJO&3l(2D~VI6
zteBCnr$u!262ske#O7|tW$m<+9l~)`rt6^;P0Kl|A+U*mj!-;*{?G1G<QfOw!+igh
zM>&19XHMR$Qz{A+K^4T|#CTc(K1#g`rqg48rkq`hBIGWjYt*UsWCAi_6PU1L@O6U3
ziM>WGj9Da6Fokkn+sHIe!ONS6<D&z-lfssTf@l6O?Cb+3pR;JkrX_vzu3^1qrR;Nk
zVsnKN4);|If<66A!03@{>d@m^DME$IP!^TMFcJG_<TxsRz*O5wqD6=AFTH^^x4KJn
zTLJ%G8oEXbJc_ruB_|M*sDjaD%uh>+69cy1A4TPtj@>>sq@|nT=<-WsmcOtxD0O=M
zU3#9>XS>K_V}Jt=LXZ475P_WFA~=CGbWlgStS=cdS_G2bbD$p%>SJaQn}I~`UZFAb
zLXd#=qsj3mYl^qh{@(Ie;fIj{okjwB2?R6-Ixv7bu?z*TJ4oN;Mr9;UP+Ywu;*uBr
zF;(9M!&_L;5M-L1R7n1}o(X^F6=&p{7)4V=lN@XXgDy2K1iwMY1206cQDWEtz?^PK
zJ2yD##R0m8`KkK(=_;dP?sk>7>J}e~Z)~}Icb451T5$S3>PZOl%@+|*7>|drjXDEQ
zu*>pjM=UJqVobwHoT#8nkH#T=%HP>B6SXppMfDHB=PL4ckrpxpPH#92I1RY4RzD9K
z_b$#F7fLzq0K%0Ihf+-VBlbM1`C|0UbRMtlAU2G}@KjOJ{1mfSU80!IXU;QPr!(OX
z9D~qzVJe#7h6`F&lQ3*T+pwT&X)cTI9~7k0F~i+^HsF!8_uD4Cwe~M!m6n0bW?dWV
zKMx~3HZdo2jZ0*lUR|g&iF;i`uP&J;1m3*oPea}7ASn{v8K2Hyn&ig-)d1M>)t!sw
zUSfT@_=+Fcum@{|pm9BLa&VlWd8F?Bu{;(q&I(--NjWa&)w@wxTUUswJi*n7LJhRd
zyXWS;YsQ|&^pM;0uD|(GJNSM8Jz%n=>-u96)+I)q8Ah))mw>U`=MeGoM*?KON>7gJ
zZ1eh%qbR6#?^1>xR23*t_i~Hs`>-c4TIh3{t|Apno+51b+X;U@UwtEPTBQtF7ZiL4
z2ZNWSTe&kF=!V`S<{p$s+@(|ObzGXCYu%<4{|`W$bmPpkS~12Ix*4|9k?!YmZ`ZvM
zS`tm-n{MQ=t{#Q>1H1jTZIkTjh}S~Sw;YA;$;uKP$is+w<sKuIkmmP8PNJiAnfKRY
z>SvR~uR{lGE#32>mYeoM3qs6PLH7ZybQorm!mnWr4Go6A)y}BK{Ou9vTd^RTB*i~V
zf4GkiA9$8<KJxl0Hvd;g4zO^KhjTUZBna*6tYXCs?zp#L`O^HO{>oQ3dNs|z<bJv+
zEjgTfV4lz@-JqTRLQZ7tj=1B)-tVY;cGe<U)R|Lw%ST4IT%c738@i@lAGrsZ(v`0Y
zDbkx=xDp{@FJ`u4DVn6}Ih~!DX!fnum>d}XcZO!qOHjjEkEpZy95av|R~ISwWa_e-
zqM|J&sEfKlp*`pltsU>tzbEP+Kzzaz;5fd<@Be#bcRhvVTqyrolu6Mh_s@ERr^kEJ
z$=ENhbwxW<qWI?47RxYqfOph6S~!1EB!6g0l=+z6Y{{^|cvIqSZ{qa>nr@dtzgzQp
zvYRY)-g8YUzG(r1!+6(cakp;YXeawTh)uJVc<!hf_OO`utKLJk%3!;%j~5SC^Gk;u
ze@;2*%F&CMg$lNVj6f;guCN1`tN;r7BAY)3T9s!B-SPl1dkbKu6soH5<j&*^lQbs3
zoV$ah8xdcM#)2jMz46LyMO-m89QQ<yDe`yl<k#L3eRxw&+cVo;SXi_^K;*pWf%v`r
zf~%XgbQC}U*>@<5)KzDdCe++wS2p<1=}s?R06ud9KFi4hA5Vy+P`VJYKh`y>)B!~C
znaw5p9-XJ27muFZ_W4j^bSOw>*xy`j%9{!`I{(s56g7~`BPMHyPNV@EMm4DWn&II5
z?LcWDwn6Q)OlEhI0w-!$LF$R?1=x|1T{37Ad+)VB@@gS+w4S>axz*pW=b0E@-CD~o
zm7X^hW9jOfl8gAQ&c6qB@o7#_KzE#No|7|vA5`9rUiX-`wt2@%Xsb4xr&-Id$!WlJ
zCT(4GcybpLXnmB{9ZZt|h&@`(%k$7$#IGkU&!*gOt<5;6<%M#l%I%D)<b(?hI6vOk
zYRzPv{fT{?ZfewUyxomgKb|J2U*6W{bvUKVm~pnF3-+lU!@qaVsHhl3a~@RcMd#iW
z@a|-3dS7r4pfWKzDdJ&X#kUbHql2dafxSlvB!!EGQJ`-B1mtgOa%HruVfOFO)7amg
zVv8C&nomfail`4Sl+Bo%dZC8r|9;vDRhG?BKfM?IS(nT=L>IKqeTp2G>Jm{&X`<z1
z;2z;-Hh*$+u+Cc{G;e#%DL8^^uW|j51)v4htOYBn+Y&n^SvI}bT-mC6bE`%w<YI!)
zi@6O|v3qk_+!2~z?-I}>1+Fz2r7`;?;q^RtM=#x8Yp4DiKwHAKQ!M_eM!cQyq9}AU
z>vZ=|h3clyAX7d#rzw%QYA<H{V499-GI9wn89^05%6lpAyd_<(hCuBy@><deo^1L1
zT$|R9O#j|Gi^{{&Plo#|pUehiU(3APjvSJVqu5itql=f~_c(6h$RJ&zt!HXakYRVs
zI&M<yN7-TI{4;&8KqZteJ4F^$MjgByd@d5A7Zfi6-N{Dkg(w%TOTs=n4?Z=KiJ47e
z9u93KzkfMA<=)ldp}O;wx(R<M8Bi7bQKgeorF_UyzV6#1!~U7{N-11hwM#|N!Ox!|
z-d>y?^QD5CKMBy9X74rdiXbdPs##H+%J#y{$7C(4hOpz|x=X5`=x6RG_yi0v4hp9w
zkop284`ude`<x5!ef4ZQ7RjwT_S9LE$_E!<`XKm`_JXKUA05j5M!nA#o>`vb@2nv2
zzxEm>kAzbXJpyzFP+8b9fmRY!MOa%0OD%8GHPHj7J!eZ>SrJ^QOy6dJze}xl`bmK}
z6x~;^w?^8xs{k(;#`=wq*E7)XQ+t%H&nz*!OI(g!h{Io@-tw1%6&;GHS@JH(SQ9_v
zI0cLAcNUy~-~m75Ew6r1DVq8H&2Q?n*o$YGUH_C0tu51e&&$n@=ff%NF@O9Yy=+`f
zEPdHvN1o)jY~tmq)JZRcN<G}2)Um$r_6vs{=f82229J`p=PYstGB|?~x}g(Gv!|%w
z^jc!xUZw5!F&~SC#&-j0`!l=Pjoi&go^Dceyy-8L4{z)Q1sv}AdRhe}T|eLRq}o+t
zft%1F;$9gO*q$GHis;3zcf7RUa@Ij96lmG<Y+ClL1X_UV8~=&SM_xWa5IvxT#AX#M
z-4LT?(0i0u)Cal)a6F3F1?PYB&|P8~zmk0ETa7<U->)sVGt7I@x{MsrCN<h#Asl(e
z`Da6DI>qL8%boJvBl5n9sB$sCC?(Y3&Zw%k?T?tOzjyypND?U-cD$ID(%ZUF&$jzX
z&frebT)Q&gX!$KMBmNvY#x{1|Q8CrWXnLUT59^S|^R`4f+$3um0?{ABCJjQ$pU=nh
zy+P9O_q~rg{$5*)i8RxWkN1aM_VoDF({?8VyCW|5e0$P%{^he6lQFg==~}gK=B<VM
z9(+EyB2AI8Yt!Ph89!;8-&5+zNeJIOHz=G!6XMlBXjp5D&ZrK&^8LpH<1Eln#V#9}
zM&@YTD)>Oyl0E<Cn1rEy$6<MuOZ7Mwmibpr1Y1D)$SMdLALJ%I#d}PY<z*Zj9sI7e
za#_#Qu11A1mIo99ySW0qfRulK+9f}drO$Tnu*k@2_4V|aGifV{rTusP{U&VJ7~`(=
ze|xna%#P9u(6t%q{<@|w*=P*eD~0mTKZ*zeDm{L&q3&T4Ea)5$&u{8CFK7M@J_-Yq
z79x%w6v`4BkhT0^L;}r|zn|BE;xa>O{V+QBZtvYg`v<Ijc(?I;cYw;-RZ*WYZCkEk
zFJbYb<i@k>Z!{jvVtQ_usIV*s#vS<l;SecJWLytG1)v3ZSeI;Va2a(=llI0mA$g&v
zc*n(bU%8iA)*hM^zRu(44kKOQ%2V#C`%l_YE}I_%9sD{!rYeEvNr%ZZ+VQ??aZ#VS
zj7`S1V&rv2O*IUd=KJ@)bvW$&P<(WMc4PlJjr3Rsp<G?*&7bGp{+$WgojXyXP4Ajm
zaQfxxKRjKIky@u+IfehCT%3P-pQ;ue!$@qi8rSFi`f_nlFsTzS=2>|mK``>zfkN}L
z<pTI}A54l6YHkN5;1eWcFF}>%Sga>onlEQs)qy>ae)l4)JEC4Zk9jB6XSr4{_}_Ag
z)pfH6-Q%A2_`@N+sC%<9+lxCNshjdR<d=Ibeq34)xLw;3;lb#$aO!uB(9obg(6#R3
z7KbHC;Nyg+CX4Qp7tU3v1w%59Nd1eXLHPQ?+HCC}JL_pMQ}TH{OJnWJh5q$3T%gZh
zqGILE2al%$c5c6j&j*Wn!{&&G{voE@ZAOD5p8{9~y55sEyP6aZh1_!fJ$vN}g(&x!
zNqgzsV}TCkaGoo#EJpkfd_a?2Tb!u_B&V}2{)O3@E&r4w`pyl9n<Ygq&_mK-WL+c_
zYGDZjlrrT|So!Do!PdR95mNtrqB)zg-@U01S>tx<!~IEo5<9`W6}JLLAn7LI(L&l3
z-=+=K#XkFIJg0-!+dINsD5N_sCDCBxde5%beJcECISeQhxZ^eMR-q8ZL;&fMDg```
zvUq{K{sO=uA4wbUal1DEy(T>dJInL+cY?#WyH-<lr|{jfg%cw|!7us8bH;WB0#dff
ztcIyFE`(IGw0e^!k0pOl0&+B-#hEu7ehPf%yRc*|AfUL%zjpWd{R3trvHa57>r1oj
zHKWkje+p##<4uqTS<rZ7pQFUR+WB{dlbx<$@?<eMR=O+Ncn4k3=n~Ledt27VYl5<Y
z98vXqZ7|>t&+13bWyUvhhZ2<vP2L9$61T?Ry?Auxgfm)TiFL%X_X$5{di$l>ZLxl~
zKs``Aq|77DWk3<GzIO%AxwG&D<SHBJO8KCJW^6dN>U}}HTY-KQ%h&h!J!Q9ANyYY_
zb}cRU^u+o%)8@A8)Ykpy2jAD;q+bsJ5+scUrx@tEG>CP4n17wY>V%e#sg0lHw{nXg
zPfTOeE|oVFnpX||3Ygt<Fs<8Q<FH)Mi75i_L;hU=@V9(=G%~Xkj*?F6sMc{GsA&0(
z+qKby^z>W~*X<RGJfX{~=8s!gI#V3+OwZGK+(keB_vg<Mftn#Q!x^F7`=u>BtD4JI
z|E$cFe{>lP5jcRl_;oZDsft=iuACj0>M}OwK@VkJEq0*M{hDZN-9Du>@_h2&1>Pa2
z8Fovn>QNY2{2?FppQG0lD4GOh0&fG)1l|0|16rNPHBh+tF)YF<tSQz$BR=y*YSz`3
zVh0Q_dCt9j#C9HZbgvlx<w-O$?pbTez|Sz=lo8H(Lozs{uIgZJp|n3mw=;7uM}FZ_
zlheb6-?9#K3sDRKe>sTBVsAgClHp1k%`PZoE*r|^dBGPV?PFJ@6EZXZzF+d4vBKIX
z+|`)mOBZ?<erbK}2D90IO(VMUeJ9Z*epMAapNB#=w)ZTx-O@qHd2RD$?QwKkO0KY6
zro0FGjTD9z44ws!21;2M`NzQ20>d}4IfV9C?{UJHXYqj118A0s2R-M{y}VaZQI-)r
zJrS{AUhrumMwY?YM2GXT>FU_SI=$J8jrA*z>2FOB*1Ybw<X;;5$Sqo@o#cGT8dD*4
z(ev8ANRsr^9TLQ$^DD8!O7`l|qNLx0wp}XA05ve`1tZU{_|%o2T$zT)bB-$AKi-X=
z@ti9dwvc$9)q3Embek2L+gO@U5Jm>>ifk_>Wx*ub+-Z#a)vWyJ=)k=dDa^g=XFK`$
z9BdwHu6A@7`n^9X({$PIy<lTO@bp`Tr#!FjSqMMyE4x+8V-(_hMg7IE8Z0h)FL?Q&
zXeVv=h5gcj2mQd|Gsnu`&;3mFi@v3;AO1Th+{LA_7kw(ZoFSVMit4?R_5o**`a@j<
zLtKuzFFu54-TS6GTxD<Jtd>KiprU~JD;pXUAgLeC-?jcmdP6%v7I9gom|<00jGl?7
z5!OR4g~aqYB}PM0m^w7kRKK1aILmkwbV;sZr=}dvdJ%sc@6%l}YbtviC!10oIFd5v
z=QO(NHtn?1kr!tuSr$I;bbnm8l2xcp=6LDGLTS_-sg7yY0|=#xx`#$8-6xBR=2mhV
zFZBwG&dn}0>VWxeuTa1vk@Ev_W<QF*+g-VC_|y*b9^9p<#M8ioo~%<6u(ZFiORp&<
zhOexT{#A30y5j>24<xYnXPhziDSpbNSD#duX(;=r=dh9!<5<A2O6t=)WT`1{f4|<?
z7Om}Bp23&JlIYTxzAZlr`6|-VOYs!@4<(k|hQQ>)O+1HJc4KtXIY&Eq$RII3DPr4T
ze$q>VF7GivMlHm|W$sZgU3cTV3403_W{f!w3Q+D@{(ttS1?JH>s7sOiMhY8q3~}c7
zVqF~(+iF|kT$^ZO+_SYXLVK7HpECHhB}4b_wchUoPW=Y&sE1{nCfC!a?U?=Qhg$BH
z&UO~-Ecyp#f9>(=*r*pfq}*N&yc+lV-*Y`5Lvy<3vbFt%WM^mht9XQIEJxA;rsKm+
zFTdCppVtI>2+W+4z~s{Qx%}GeI5Qz;)(gCIWRu@dkD9RDAR4&OERaD1I9mBg`Md*v
zV{qgy=#TZzx0~_A=4cI$KHm1tFbrI&iO`Qm2gKsL=6;V+MeEec87=R}*HeC{{kk>N
z*SRx5<d-&HGZ{_vRirT@ORG>6C`d_s^AHyPr6m=Y)l)z6jOQ&!&;G1z5tx=0Cgo#^
zEo{A-=S-ewjYpjy6+`~b1n4(BHN$XDY&ykawV*a^EOx47czt8kguAmtgqe*ixaFa0
z7hk>M)wJFp`Jc$!*?m_!8s@kMgPqcb|LnvBpI!GW`q*;MhUg5ox3v9kM7%$CVOB%&
zFnh~ru1f|Cf*lE|w==~1yzg`~OValW&+&8s3XTOCoEU0Jx6>X<HRV2FIQqTkZRJIW
zM*dHCIWG^yrH&VuURaWAdZL3l1HhLoa+J$nSh(A>TI0xg?A*H8xqiNT5MZ_E%UZ$n
z9GjaG!kH@x;;LN&oabJ~hckGy#vHmlm>2Nd^yX8t82I{Wne^vyDEnV0mw_2cnd^Es
zm<PMT#BX$#oAcuwO9SfkfpUcgIo8@c`v-UJjb49@p|{>%*=>w{<o#MXuGku5MN?<8
z>0M#J>>*%p9g}-$a58!=1PbT^pN)g!Lqev&7`BN`PmE6=D0zJvIz_RaI(SQTmLfU>
z7WwMkj~?60f7I>;>R!FWVmpG`$G#$ZsB&_>LzqznH#5(`e#3>lrYC~i$>+B7f6!kS
zs7IrY{ZyA-ViYJ#E-71B^{H6HICbCZekYU_HuNbwJ`LcFaaGtfYEiXd_HaZkM`>yc
z^+A5x)_SgJK;C~<qnO0`a_M`}_~tBd<7J^EH`*W?um?1@qL{-Du-6CiDcN;~msHyn
znO2oM;;5&4doQLYe*e-Jru*v~TSAyTw=7ftj>q`HnNSFw`kggx@b{bU{ET`3ylT?%
zGD+c#pDr@V+3K|WjP$qgYvtBvdarH2Wn=}3m-4@rWcH$OD?L6;a{V&zWye*0u1dJr
z7F3vpO5$T8zOl@B-;z#ZpnI@#z61jX20$CbJcAZSBt(J~n#A9Gt><;e<hT74C(v!;
zGnq=yowBpCpLw-Je$Z4t!mWJa%qgELr^oxhS}~m)vMvuZT5mp{h`K2C2ct8-v&-#p
zNI7(Q>D@-s>FIg8<FbW!ci#q70ylQWS8#Iu6X+py;A4~+cWLvOd-!0IAmti-QN&u%
z!OZs>_Cf1NJ#gVdA-J9z9P^j{&o!>1F5*Hh;6gPFi%1G9^XSmecP$INy+XfigqZr8
zTcg2^q&=wBbRJ<A<4j5N+=0SCRX46vgqER04rXNvlm+$@?3ebm=|%psDp%Nace-wz
z9znbRulv(B&xqa7xp%JUk*!A)@)n~{Oid$MdiRUjB|qkWPZ+9B^A#cJ-u9MQsBJ1&
zHS=3yE4;Bi?Q?Li=gLu|Y88{}bPt9kxJo^Qz`at}8)wiL<@pW+;bUR{Q2gC$=9JI$
z-KNICy^2)X07FoaZr+g2{AB(OTc7nle!5p>@-xSmF3=-RgdPsJ+{0WyH}GIwOvLZE
z8*a6VJJUSrytVg2S*CuQXO8JbtV8{wulw-7?H%okiKU&2X38JvnQwXU<84QVe!f*v
z$7-_-I6Rsoue0FkXRPw`i#}t+Ji#?+49RVN<V!s8Zb2ou?HmGgDjDRqGsx;56)e;r
z1KFg|!;%EH4{mlm6_lTnm|~6eY36!bv;O+b;b~`~6czU5H3e{P0MD!Sv+L69rX4-#
z%s=h*U4Bz~#5IPzjYf5D@70uAzxRuuJ7*VqHs323pAIzAX_LvplX*pS^zv?r4JUpJ
z`eYMlG3;*&y26a)t;2)v4WFrinf|`$^NHal55Xkg)6P$egX%db+g9LjE~X)uFSl=G
zz+E@=!9|H%g!y_(b&A^P_;>aYaCf29Hxm~t5Mh-T-<Q3DQSB6n5056#csT2R(J7f+
zFOM_*)^lFf1FERKnI2`feWAt!{5w<QW?Xd{l5^6t<fZQ~>wRzDTyc?D+nd#ioq7O9
zrj>fJgn4&^$crWN1#MMgx;m}cLkB{aVp#rp$jNUvqAtHsleJga&#bAk4rt4+hFu@i
zn@8C$8s-Wp{%@ev=#_T<&1!vIC9b-#^8Q_!;K62#;X|CY&aAwAzekZ-H;ZgGqgv|s
zg!Hqo)w=ENtUqDv`)tb{%sb4uErur)iHiDdhwB{YO&{K9o)7+47&OR~s;S$xWjxLh
zPdR!{I!-w8rp_J>A1|N%R?DVm^>Q-%%*?cxL`>3T%<Hquf(vUCFM!PaY~_O76EKJ~
zuLK%df$6&C{&6>1K=U*qOOAGmbNQFS#Vh!10b3ua@kX%~n|x2_8@Rr|{~vhEA?Uz1
z@pH9dUtoK{J+Bizq5qGpgm69>(@V(SC`!+@8&ec}B)aJwyl8OARMvCJ$S{Eg4BG4s
zF3T2WnpNu!(U1PDot+{RonHEM6QHzStCj9|kGF&+#J954&Yb2Mp4YMT3<gu;=%j?R
z{;uZ7!IuOUm7B3;=WwGo?EFNlc$P_1lLwLKv~6H)Do=?@d#q&vEYH0O8n1F%ZcP2p
z%$4vADfcB{YSj2!CL+J5-nb#RoNrQ6-E97b><{ld<I?WNAv^r<0{yf+gc=1H2N_Gn
zMKo5M(8HfodtcwXD{+t=LjO0PQ8MrPiP^tyx^H<TvXC^@raRrMGyS^0*bLs?P)+3b
zt254L?b$N`1L3(pHK7;d<DpI)?Eu~93tSqma_%qgUH6&!jR|g<j9&-@n*{~pv(@q?
zH}T67t~1FhGIRZn)=}+bk2CBgY6bzRfV)2V5d)zzjQi%snZVAYX-)!i!}fPRNY*NJ
z0|C^HNjLHJ0h5%!eW}R5zZQTGR_21~Y}dYikCKqSl~I}?Uij=TK66q>n9}9@-L9fD
z#c8*;tyPovys7E38>e$+&amu+#pZPL<k-h8baB>wa#HJ@9m&gW37Ix+yz1?GyF4^h
zLQ*PkEHv&sjlzTEq?B_h`HGHo9;<WW-a_oYwmu`Z<?p}$_-FwxUfOo3&KsMExHqCl
z$9f`5#+Su1@&wJ=_-Q!5o=D8MbI9cjtgmv3uhWFPFcBnk&w(j?N6gwY^s0wiZ|gpD
zA$Lc&F!NLhzjs0eNn;%6Kl|nH+OPkItgis7a(ll<36&BhBt%NOR7zU9yIZ<J;Lt77
zjf8Y}cZVPi(jeU}UDDq^;JyF*n~(9%VTPH@e)oQ2t@W(^g0B8!Z9J3Koi3hPF)ZMV
z61{!0kOQF(307yQ@y4o@v8|)(BqmGu?ym*><KohKreymV1H@NhhMSS<)ak&v0|BL@
z@dceR(@RA_UJ_6dH~oUk+tNXpVts8?V^+$|%Ag=~E*_g)l+nc>ag4>8s%;$ank-$i
zs$H>WgJ?r$Ad&nlkrksL11j$2zOuV<-g8+X_dSBjeL{6cv+9NTm0%YJe}Qw*7}Dnw
zk8zCnMs-6;tA7q8w&SSV^jw?yiZ?P&aRgjBsj#6UWt8~^e9V^}9h=Q$Is=31H;r+<
z^<s1F%hpAb6d0&bo>{EEG0|hPF~-YAPpe(nwoYf_Vn;{jJU=#`BQ6#BG?ss}b)$xC
zt&b6ILMb{Q%rL>S0a3bqojy}sR0zVP*y+;eFYN91uxAC6$W|acu|}MV23TXg9Vez|
z;CpIUiB~)Q9?;%T)~X;6HrR__j(jhN#FD3%aLVz;bC(^Qr0V0}9!|ebXL*<%Jt;On
zvEbRcvcE!=U!lRQ261m{3sLXK;z;pM&^V-f8BW5O{^@<%_ijpj*7@SqF$K(3z24Oo
zQnG@BtAi0$%~H1?j=(bk%vO~y^CxWVj3xyhO*WT`x@XOus`}awz|!gXhK(%e_mS@L
zI#@Uhbm7Lp4rVLz6m%n0FsuUJF-jH&w*jgzB+oSBzKwn_Uq3kx2VK>r89-4C^~_!l
zmEf2rwO$+)P=5d%iQ94i*~(u-lNO6KKeXSQ9KoI~iX(s`^J19qCvQJSlYkgbe~<F-
zC{B*zPp{KbyN&T{2a7Wo0)S$%Y9}~x9&%h&@^Tc3eBg)P9=jTzd{`pp*T#uuU^okZ
zSO<m>iG{(|*bYW?uNs1^o0FoWrw%*8=C|EHga5tqMFASBSWNvue{+2z0^oqa7KU?V
z!@F2Q7b2lf7uRep4h>X2r|6;Il!Pl?W5OqU7A~%zB(s|iN3h6RLj(DF<Jc}yf{$Gk
zap0#{`irB?@apq#nDTcKC0;Zs@C+E})4U4jY{&plu$YU}Xx*fB)XM`sfaSEXkdylN
z%&8+@Z9p_mh)<u6+oqkjC;5pSYNW$_1An}g_K?Xk;QGw<EB30Jgkyx{=_v{U^L+<{
z+<`4#a02eYQv=`(DpbdD7m7EN!5S{o2W<6x=q-R8l2Xmq>Yxw+CXhdd7A%#kS8#ZZ
z=)}y0T6=pQYUK7O#oPZAZMd{FdUjLVQ2K2~K?Jj-HH%2V?!aw8w%~|BsL_~0PLQ|e
zBr%Wxh;d_^)P<APRGlircFWejeo%c6NK86IdGwyMp_nc&Bw4K3E(MPwrFu+0zk!f`
zcfA7-M31pENXz--Q<Yl}=qp9TMDG;OFTiW}&bIcFV;T}I4~DcSYw>rpAILo5_O5NZ
zQ|@(AVD;kUbSTCyc9N-Y1dik@wy4I9+AYmou7@*za-55SBT)UKw8rFmF)xp?DPv$&
z&igYh=M34Y+BENdO35tk-jdZMaeja>Zer{h_4*}Kc?}ejI?iGYTe*e{^FwzhA4`gY
z@@N0Jxx}>Y>EJJ?SgMry+3`rMuSCFwmH<L0?wttz@hM93->uinz0Cu<@$0Wz!>cT(
zXu2%s^Lb0^rb%*8<p7|!pUA-*tsC$0*NpWlt{P<uoB#9?sG`G}t{pgx&dt#!4`c@g
zA&Y2@|29dI^d=ZCGqoALlzMTUkrn7B>rLXG-{4<-RYG#@aGN5ji7N{%M|E3OJ)6S)
zmod*8K^Lb*@B+I%QdRgwj)NsLt3vrspjhgt*8lnwHQ4B*P7f%KM`{sG+V}Eu*YM>S
z34o5+KxC!fEXY6{QIXXE4eizBET#gHHi(qk@VALCu}8g!p0M?e3<lK8zS!ofKR7vR
zgQ}27=!;J87#PNehEm7J6>DdA^WFOROZW}VpBlHTSoEichXwfFsIrbobz_~&uvme~
z@2-)tw1miU;+`-k6h3(w(ks^)0`DPIr20aY;tm*?Br0<INgs>-rM#T#%LxXFcunQe
z7fI)ytLP}QEq6fe9n=mCBP@T%Zut)^WH>@uW7<-IlL7_v8F9ED0$CQs`lB#_>7d00
z^YFe73=eoJSa~xu(rhgATwTh-qNuK}Zgh0?weRu;ivwnzkU~!Lgi(p;`tPU4V=~yY
zi_E?qRCC$>!&>qOgPoC_M+F&v23S}pV=<_?RSojhES5@DEUs)iR=S41g0%BTSv!#A
zbv=hlRulr&?%uvZ;J|Y_-4FrdLBFLa;<r1u&TA?tLu;wIGqSR0*<^Ul22V#ON7WWF
zfey{)Xe<l>Gmxq<()EPNcq|K}8R9`B0-Ac(z)ty_XKv~;GT~s=@>*KWyRF*(ml2}J
zI4Csc3eDR*-oII8^q;W5W0XB13XbZ}F<Tgjdh0GN%MVruv4W_xZ<|8#%5P)Mg&(VX
zEF(yP(Yq?&z7|fEJr_F@7o?5PA3h~|C|IjCMgnNtG@xxW-cXXR4u3Z_d^|^*I|cER
zug<NJHfJ)u)Yk-@Vzebp5*gVT;>6t19cJc3owogI?{d6YEfS8qsG&i9b{618Thmcz
z1*c2-+~(o-OhJ^IU8P@1&&J%e4T}(1-1$Qm{CW^>)aTmMRiAht&y>os&2i^IOSMcG
zfvv^s;%|^-%jt+J@8yYK=FEV4#D!>&a_;nB#OyV;L@{vd#2n*Axc!A%&otb9z$pDg
z5D)~bGw4No7!paN9MvTo^$mSzewuP~*FHzw1hpT^-sZPCQvvQ(RYvW2OB(TAR`6?9
zAPd)tt<}{xI@eow<!_H8Djbgt&ad5OU5@&xC@4xGdmQWE@^-ifdkzz@UdEHELFh?H
zLTLKe=Cf-PrXx!s;vr)qAobYBxpQjU^%XEydL6y2j)WzEf|Gf^s^5D`-Q7QA-oKsP
ziuTmCEgk3?fxRlWnEEDpl6z{_ppx(|KGxV!G6AUTHh!*2+q4tB_y-1t@=p5tsQLlC
z+>%Ik76>>!r%u3`2Wr#x@>e!1V_|T>70(fIgnd`EM?S4u3RSjEX3rVQVEr;<9vd6W
zt*=)jB`qb8(b(q9pk>Qo5Mwc&ag8Ug+R&6NaxfijK6&ei6_N|tr(Z!t-B7;uxDXVq
zgboGssGpbZ`~Ui;raInr9F*xiH#FR`M<fC?F>xW`$55elX_#<g=*mxNctG^x+daxk
zTP$@0y0Li6Ub)DHn#d-n5@SbIbd-^OTNQBWm>Ebu8c3RGYU_lo@HTfCu49DoBa`x%
zDfexSiZ7~xP<PwVM|t(<i?{#q*I5fCIk~U9&9`oqm6ep#)YKM+)2}gEFBMW>FgE`l
zj3_@GBbcoT%jakCerigoTmKF#l%nBXwhf7H-FvRovMY5kB#71%(%Ei&lLADu=$#39
zjnpdIc$(<}6T{_E&!pt2T($VB&Z`8ykJZzWiHl>K-=BeO?S|rj=G`4U=0qUY!w6GA
zD-6t6i||o%HhwA_R{Xm1OrD5}hO)e`uzYMzRv&a3W=um)%8Y9ctJ9PThQQ|Qs>DH7
zAZ%k(Q+XjFsQQM6c>PNy-eW7*A&R^Mn?Lfj$}N(Co=b1AH|lMEoANt0TY>S|7)3&I
z+uu+t(z2Iqr=U10uymJl2b_n#Gl=0Giy6D+r{b_+_a%gcDS%^YN?zS)vkh0INM_hP
zBI&P4^%~mrJwyoJ;1iDROljuFwhOr4{=iAZ!5ufDFk^cjF{-|6j>vAq(%`nX#Gsl~
z`%ydXc=5k&XT+)qLvwJelzU_o9hRzjC%va=Cf5jQ)27zml<v%8RnkSkJN-6=&-Dew
z>67x=u91Sib`w)=xU>&hHWMq0<)mBv)^_Bg<nL~Hpw7PKZrd!$f7`#u)f@-ht|vdr
z>8UW*_V|l0^zWoUn4%W_kDws>0sf~ltYVcZ-lylx3EZ!730iOP;YH|lY&Nb=8xh%=
zl^cS;*lyV1t7^O~XI2jA?dcf~!Dk<xnxeA*j0qbP6Eik4lAe_Gik9|zgKIIU)ycf^
z>}wB=apmuV&qMCAH-BE}PXt&L70U_j80=O`zJ=ljA$rvjPpCUHxxqI3_mdmv6)n(W
z$aFYb8*}S;&nj3tkAw71phao4lTV{qHCn#bUhAp(If#mu{5uUet3e23K-a{=coG7a
z;aA(hiASF#7RPb)y8XzutG8Fq&@ekLE^bA*q;&P@=!nf>KPBWPYg$xP6wB2WP~Pxe
zm)!KDY>l=Xlfzh=nYS3o#oPqZN%ug*S$4WvnP7awnhB~MnE1-<p&S9>JrTEL_hyw{
z758})Q1;7_0^f3{dmrpfRFpR<g3eJ{(l;OV+VS;uLPqFcNig7ty8^%>vXX$dML=X^
zJ;BY4B6=O0+~URF2y<QU8DR&7M+BCN4()XZeYtrxHOd+q8dFWK&aJk}Qc_aeEuOG!
zZdWzDse^G73QXKNJ!;$qe%Uh-FRS*;0(@V|3G81w$q5Da9J06-!aQ#~xZweFr_qQ;
z+<fX4sm~$X0FB?As?7&(;*dJBBF@w?WEsA$N00G2E=&SbljrSkMQDM@%71?|<M{*V
zM5pD8kifx9VZ;&dr<OI~F_$}=`46rTsHmwyIm@I~tNIplh@h*h%l2u(Lo$&qQ&?}u
zHma=bovp2HZc&ls@Vu!*t?D|yrDE5!S^TwU^+M@U1fvcPn(4(?nWtu36Ct#aNiv3f
z!Rq=%kXOG9x;0Cg%dszakH-5I-g1*nGRa46Z?ua6Ip7^W=`%)=I)&l#zm&iOI*s<r
z_n0^Qdi-F76=p{H*X|hqW<5&-*K^gO^Szr8Z+}@a35npk`g#Qw6=Sv@JY;0#4d^D?
zgZEU7D<~=DgL)j#Y+kq2*~@WFH8Q_3e8_ylP9Xg&2~(k|gj39Gthv}7RdQ=%abP3d
zpnG{`)x0bgxFZ)bnA&@R+ok8YhIW#A+~7rwPF?f#=IE)YX%<&T9f*mFv&k2jnw_w`
zl)shup)OOHu)B{R^Nn>gs}BjkOJFrK<eiZCa%T%~1fS_;GXS@P`E*roe!dtfDQVVn
z!}nU7b;v@?0~F+fV(OZzDn-!2!M4}$b}BeZ=8Gne)@CZA)Spq99SNc<5h;11*0`w^
zAERt$2i)*AwZ`V0^10w|S7%)|l$CriXX<9~|7bu|1%I3+foaXk%*FaT5o1*^U*9H5
zlXc#bO_cZ#u<o9D0@aP|{`kf3?7K_ByEcSRzU-*P(Oq;07i(#Zwy$&RXs4~LeR@Co
z>sL-u5#8$QYHWy&Hy9C&WJ{Ue-dyA2;i(<5)z21PTsT3)prquJhM~p5t0AnDtv>5)
zK@DJ^vngab#r*u!`nv6yKKE0d)?U#?bkFRv%#QCbB=0tWJFri<fLF-br61f`!O92-
zox~3LbXJqFRWyxTel0gtbitPR>gABm8zZ&=<5wcw)SJuqQISPDKrMbhpVsoqSkAJ6
zsVN-_I5TFx^+YLdK5o4oUAU1_{zk!Ct4>#0Rh5^X&ZnX>6ii#KN`Wzau-s`2c3eVA
zs@O4cWK-V8rkstPJ?iUMblVWW-)xmGfn@6Sn58NsO!Z?nJbN^*q5?lF-8KD+(_cI~
zKBn$Wo9mpPE9lrlM0(ynpmcV&an&_Npr{f$9aq&`ZEGWbDygq{?I!-9^L6F#*@-rB
zXAl+{On380j>Z8nRAa%iUbE8pIsA_oKuCe(DZJrGlf&+b)9TSVl#mp&)V*C*R0E3+
zClP||FYxpa41m>6?<hJu*W3O6l?v!e@8K^D#m04&Lcyluuf6srQzNw9uf~#Gd*e^C
zU%1N@#%3Q2A8@U*jo&yDp8|M}dZOXylw7D!Dxw7DZj;`>ASvs>2g>9xI7uD>%x`Q?
z2N6Em!#B8oWFpl8_0Wq}VQY7+um;Qz&LigZ*&cb|;Za`}%M|Xp-$>DjM!1xfmqS@d
zbTn42`cN=w_0;figp-pK<j=k~Ep6d7>Ka(5Ed-KNSSVpp&2Dg>P!$%}I6rQ^p^~WH
zsARLND8SCR)75H+Ut6NVZWFRW>picK#aU%9rEC5(G{n@JuFe<t-HZhoha1VH{fScv
z>fdWq1N*EUy1V!lVy7n8cyn@j2?j!N%`{M)4<l@IN5UH#)MRz~=@Ir3@{45q*XNoJ
zP6BmtIS)gz$V5@k&(F8Ewq*JEyk4T3c7&<vTUbawdiqM<(y~}lQE|M1j)g@jF)`7^
z!XjjQeZ>lHZ0%1RmQwO~_kMiE!c-Ax&GbL3w%R8ZXJf0i&epl<LtS^8QA_5&mk-$|
z1Dcu>gv~Yhj5_dpiXtCT?^z)YjkLLn|LSGd*Tc^o=9IMKwb;QEQpBDh6}SIyWc}^V
z)&E1iWzR;~sd)1xjD=an6)d2t`;GI}6e89Xl$0_`N-<UD(`50qb;QMESy@@o%8~fq
ziZ|63<2ND_60}%@beu%7D>r!mVr3+TsX8uSF5I_br2xpsdy@9s^&`OWv4ArhdsdcE
zrGONn!zq|$$oS?h&e$t(O>inMqkU--+ctTAyn>VLGAlkFZwulEQ4beZ)q1cSeq0{G
zWx@6s?D9uMC__Pe`c!O6hYikS8>x=P_-(!J^0pzp@zSUgjd)~DUS8fPSWaBrMqr&H
z9zOoq&Gn`2T3@U!re{xYFLb3-Q&ZSkYRzWrL2SqLajKNVIE^YihR61r?yiS+oUD$4
zbDCEbcKXf4zO-gMvIXs_6!il(?;7d~Yv<A!4_L}Sx;|(ut>XnvE_yFM1V}BFg=zBH
z2tE=*Z+Bu~-R8-GyFz4}9BL;EYr2bL2Z!cO80fxkv81cI?@r$)3y3_Qh^AE=ot-TV
z2-pa$QLKk-Mx5@=7bCqGS4x?wF#ZZ{D;gU3>3ZW`_QCmLw?ewqm|NwID)}L4Ij4bL
zsqXmG>9^R;a-K`sE4^Gq^*NaB!(e1D`83$fp|Rg!<ds(7%+D29YFz{E@59$%bN~=h
zIb;A*o!=yBh#-U^xkq<wAW|*t^z%-=Zuzp}ItG>;!P~MoO$LUFtT5{HW%l*ajnhyI
z;$e^ho!dYwzki!Sx$))c&era(qKphgU|M-&dwT?IF%u(WMG>gSw$Ps#8yg2jv<sG+
zO1C?y^Yt>-Ew~61Ia|nI!jsSeGa-?yV_$JHovUnctYLbC75>Dq&907odZ}emF%)8Y
z`!88KIE@cqvzeMkuATtFpsu&KPkJOv^hC2p4^-s6=g=sC$)JR09^p8s58(Dosd2_u
zb=p+wp4!lCVv^rWR9^tcMkgn88yYwO(na&<hir{f?#wr9EiW&dY8qBgj|~o{fDVI+
zf$`&w_U|a?pZV(Ug*U4R8rE~gC7cX-*I2}wz#MAcW7D^3DB7H*YRT;lL87Ih2aqB7
z#cR`E(NUG^_PP%~$P$ujU;s6d4kTvU>8IS*K#&1!O*%idqG@h%2l(kGKuD<E19v}`
zyHy)JbW7&L81(#7{cSQ2(|*inf<CAz?R?P-47q!E?D8us71-^5ODifyZ@yQ0?9Iz&
z_xqcs8yF8r6*r=-1Hv&poCXNT>Pp7AM)z0}dfxbxL^YF%Fy~NWW_$Td3E#4l39mir
zTvOiAXcrBIq>5&w$>;QmT-A#@dTxqYS4{?i=<V~rmm;vDV`!%>!KJF&m#Dp`ZJ~OO
zoF@6X<KN4->z|XfV~9?XY>M2E9Ubm^wvKUVMzGQ<%nwfq5`|{`_6xtCT+q4Vx5)5t
zBA{oTp4vHb_%l6c#YW!h3MYXAVXSd0-?GkS8PGypxRT$!d#Celuz_~2ZK}da`m$3M
zlgd$;*%?A_FQkZg5(67*Qf?@{M|18Ys)3G0D!~n$J#2N~t$u+E2bNoAVq4AwS`3W(
z8fV}w$sxcjK{Nf-5}boT;|m1nfCIlhBl&N5q^`Kb1BvnZ<Ul+s%)-T5xjoei&CLEq
zt>=qMM#rgE{)3pr#KNCHB`Yf`x?(>H)U~$@oE#r->@T*dY6`8J7#L)+v9UpUM>Tt0
z$ZtI~WCUB#U+~!=!hwN-Wnl7ByPi%};GPeRPHYf*8l?^Q)7yrBjZWip+KH%|9JY#!
zD08lEQfgm8rJ$A6>nQPFp0+g2i|Owmg)LpNt*y}AHULhof=vptMka7G_6&r|yE|dm
zk6hCnaJ+Az3&KYrkdi9mk$X&(<`>@}1-xfgO$gZ7pSPuc&#h;i=Riq8Aq|Q&E-tQK
z^|VB1ZR^ZT0yJDsPESp2@n=J8Yipsc2e9my#&4z^t*m5xQSpZt+k7#R5$5-gP^F5h
zcF(^YR_}%@(7W5~;ZIBlBq>(u?tFzAp8WGWp=rPGDRV`YYcJXCoVukIu}#zQl^7WR
z`#UAq9m;}%UH@nPns6Z1-u^j0Qf=s&h+#Y&2WanR_U<YaVbb&bMxfzkMA!!`v4#z<
z9qtCDInYTYU)srH4Ty<}je$A{%JP@(g@lBJQBT-Mkfk3_yxUBh>FaWGgrVXRl%}{!
zmcC(U&yUe^QxOV%)wm0bkh+SKcr#VM(nAGxBNZm(#bcTiT@SjXLv7^I39mTi{{%JI
zZSPh{3eYFKFHf~yg?9wr)A)AdJ{1&iCN})*<A*VA;j+zi{@~71PJWT#z$<orwg3@s
zQhzA^hZz>#YAy#W4+3XEFR}%6f|fA>Gs(pK+ce@+6t4B>Pqqi=tBh@pd!|0VmDkWH
z+}*V>pQ->Cty!>faE740=k&LV!1&v(y0kQ2=!2B$i~VjT4fFSZg8%;02Xd(-^$A#n
z;)AsbFpTevRM{%0`O3ZbXi9D$w$_|FdMB0&u<euL`T6EuTO5mO=zV5=N4a&@h9eT)
zi>;faoU>YR=M9YDX@$R3B6_!7T-i4j*Jf5E>TuELLiU<oby$GMAT%F@{+R=s7yFk}
z{D5#7m7iNqIUJ}D|Jb}0j$3jxH!p;0jhdPkfW{o3ok4+iox{OW-T2t(XbvC^3JMBu
zMWdB{e0|;jc<?a(^;|`%OchNza}!y9Kg}uMiJ!~7O$Ki@2>D&G_vN;+GA6GANQ6^k
zR8e^ix?Z%F9*MtxJzmCs_(bfnh|dSY-gp*z^fF}ej|(Uw2$BZEgh-6BG+v#|%)!Ct
zX1YpIqNZYn<Krf|m3y)xnR#_bLg^Mel{0E}l`h<@Y@M{T>$%13cDkEt&Fkj}hyCEy
ziR3j5{V0_SF%5=k4xFDiZGu(3?Wbv<C?vtQ{QBLn!bx>xqmo4Zp-^@)D^9fGmkrM*
zh3MM{4lEvf)c9Zgz}H4a$p>;`;xwZ_CBqN=HXPDY+SI=n3%I<D!rs^ZePyWE|C%LA
z)H^N?_t%b{p1wXM{(4w=__OzklHyXnZg5S6j{#%xnY9qIu&}@wX%7Ks{Qf1XdaboU
z6=$#@iR!>NtMRJ=<$1~uzkM`2#`B0%4EP7!$}W$RR2tAjR}(rV*0^%M?31sccXu7r
zWMRd$s**f@_^KpHz)es!QkGK4#M5GQ^V8X+Q|z#G4X!BS5bL{;)!+>LR=0;VgZ|(N
zDE#*y+Y=KLM<@u@3m|=b{=vF}o!`oca{UR-s@t2T6Pw2Q?|;Oa$#sd(bH+><nVHiH
z3sH=XOBGt-A3jiTaCjz}jSgxXQL$Y97&vyXegi&1K|u`kj*!JgZSX98KY#XA8LFz{
zf@B>8r&+1mxMx~E-Hxrq4VTO&7d<hY+u%UF?rZcGh3CVD&>?vMelo%BpTq56zYzD_
z{#3I}q}CR^7R`-hXs+|wYrM$H;G8qBP9dfj%HqfHPtC>Q*xOZL^O3Fkw1a)dl<9@`
z416UbNT#4adlo)3hZ4Qc|CT!Coha1+?2Wm)+xb&{@z+liC4I{c2hu7lF)1l2MLQ=u
z_s-Irn+fP*kn;2MiHb)|DveA`K98ArPnw13wEjYS4EN^!`^VWM{+XHkWHC|^QBm;m
z{XSDusyXs`B+1<)Qp8W^TgG;%g7W9#WoUQKrtt<Br^}zVWlXiuuW|;eE<4CJI$s;U
z@NJ_Tn9l1(FXMQWA(hM$jaAMO`oIwJXum^%M3IG4R7mFYgBE(2KSKXL2i68ZKmTi%
zSM!n>ZPC`r5fyG7*AjjYlEsZP7;uA)%*_SF#E>9tiNjW>2TqL}o131~I~{8V8=W^>
zCr-*VSl}NvvJVAW5DHiFQ&(5ljo-h2OvSmh1;fL`mrR=F<mDl5p4Zm0LRgdAGR2Yw
zn@-Rv>NcxWhee$kIs{w3SW0q-h@ZSm>T$-x^q~~FZ1<{-VuFPF+ON1t$Z%N{7KX?Y
zuZmC(j>rW$sObg=8B@r9CQPX;L#97Np~4rSl=6UQgPsVfzn&912lz%nMW~*XU?Rj)
z>5+4^pJcLDV!*-Fo<IXvN%@lr7M=7i5ebP#x0ls|=xTdNrw$yS>Ss50cYP+dQ5+My
z^}v}3*w`>ssG5Ta^V!)khuGVv=jS863UxtG%*@OzncktGd}1EwXkvnh>I(~Sn{Sh%
z^(6t}{GrTa6UVs(nViJ-uZ{z$!Yt&yZl!`40$07JsC`9W+=h9r?8sg<<zjB>N<Q+l
zkDu0b*}kHFR;Z9K?{KWB#yj_fpxEUGrs;Y~YVpbPz$siAEaC0UIo)~4V<M0~!~rs;
zCtt~+-`GoeuCmJXsdioFWSq!Zx~XKn4o6yjZ;@G0SonR_Iu!&Om)3^d#pdQF^aP5F
zxgjj}#8Wdf{Dy|)PR`D4PF_530P6tH0#rhz&GXXIx6q={=ydYSu&CkG@SDrB7=`m?
zGI93elgCuX^SoNK-EA@C+<v0huaml5QCX+-!9m3(9Z+jWt*aQI&rOa;l&k`DUdM)h
zFjXJ7rJU4>4N6`4Dyf5w5kIJDgAX0xTB;*ac|ox8W0)sEYZ|c%q(Ti2rV$1=>L)M1
z?>XaSjrvhy*Muc)+jX_XJ2FHmH#e@|cFtX$R>@fa2Z5RfEeD<-2v=-bSy{pA-`lJq
z!x0@cGpT84G~OV<HqX=dCQ(Hp0>}>@ysNJd`J#a$02>$g^T_6pD;I}Oll%%Y`3iR&
zm9aepI7h^J!R0rv2F{-iGi{gs&d%sJr@vVwFV^mSF?DM>A{zwW0m1wY{VMLWO>vWd
z?bv=X*?Tq3&*1UW!u&F(4tE!(>2EOD-(9m}8M-;_x=eV9`V!uq6!U#?P`7y4Ym@ek
zNo!w3WV^WG6h1cMOLj#C26H?Lh@^mq8xaEogN0A;-@JQ1_gY6r=9w8Y9u*Z;8ahn}
z4GoRDyO$?LK-uryA)~?3QMmlE05B~~8MwT5Q?L2-08|n%lX%u>@X-*KWZ)W?4zEnw
zaeg99(~TvgiM(-ME|@zh$ESZLRIAVJ30ahj&}4E|cx-K0@6j;^$*bBigmNB&Rr#Jc
zEsf9|4*H&+mT6qm^f14bkAucCTC#rNXhE%LZN%S+p0Qc4e}41|5&C3l$-17B-~_GD
z^)q47hKB4aynl%|G98}8mw(&4Eei7goDaGUsL*b1H@Qs~6l7#%;Q2nSiaM-{2nfJ~
z=L-l3NQ<PY5|@%{Tm1A90+FxcJaOVwRaO01s{D}=*NdyUyxa>2={2(!W@ctx5#OsT
z{Za{BVCqJn%g^50enYa1Xvnr{eD?E1a3*%`2Rnn7mnNqB8MRa&{g-2PA4>SpnPCLE
z&oSV2>u(&dPGCCU;vqYf?9j-Ie4-NIC|8V1-#dK$@LeM%MM%zrhDR;nm5ui?DRI}W
zgv&zg0&!cGMb`<_()+Q%YlBXf>93o_MI@`7U)rmw;gyw@Nv<-rz2)FQ_HFY7Z!ip-
zc>LJ|+J4QLS5{W|-)j7>aXEkY67>-oIl2Bc11TxIVm@YnfB)bngeUpTfn#H9i`U+s
zrK-AGzqd5Teg_fZW`g96!C2biO)&|n&;{nB;)1FDo;;MNdQCpg!}Fg7_q)RwFCM1(
zQ6Gu%B=^3_To_WD4oj1|I^-Y>sCmzdKaN`|>TN%%`Vo0C*-BP1Z^&b-l>=Eqz^&8u
zrSm^c_<QMH%CXKoAOx?8<A;1x((>GiT=Sc-EY|Ee?6P@B#wMOVlu}yy%-r0Z2*1-c
z?x80P!lOrv5Vq0^j0VD)OvQW|Ev=`ZD;*ynL(6>{g{HgL_n8D2^2@Bu%<l%}si~<C
zOe)znj<&bAKh>%O67Dr%&$e1_ctCv7?943=Z=Ta|X8J}?US#gbSFC#ZynT9K_%yJF
zwh+mLh>&l1;~5OLt*V36AI<^B`28+gbKxO!Ayy8qdYDj_hOcnDT+<#i$G<KZ!a@uS
zsiejqUKfSfiLKQhX{6qU5<^>nOoH}(bS@mT$^^wxUKC`U=&p0q%0;w6*ziG&4Ngtr
z4qMG+cds9%78gGSx|XsU(lx4Xp<>|Lnt^hm;y3Xu=%aalfPsaD{lu22tf?7oJ`di3
z2EY}_z7LNVDYi2+NkJt-Mnxq?lg=`m`(~GVMzG88G&xJryxz=fNEca=O!4?nb-VL^
zbIk6KOKUf{{PTzMe*Md7@H`%sc`xZtP+y*((3C%E{>Be#CbGDs_sLbE?N|;qou4dj
zfX_^YeB_#*wvL<3CPlUc`~nxu`adyBdmp0_AVv`<c6nc?VV9d1bcUq9TRKT<=P8hA
zqSH+?m6eqR&lv#VhY#fCneo)zoFIrd0HqfW9C$Si-(Z7G8yp^f==B|~{Y$B~q2c-k
z9`g9ag#L7ONeP-=Jw7HTCJ`q$J3A5xZ~!I!-devn=vjR+bZu{^H^voE#(vAd*kLAe
zc`iVEW4xRAXX3p6KyS{*NF2u#%}c;Z!-}Y`ldPo1ZMn#i2TfW@-D7%t;PqJPifIyU
zP=BBAm5Zr9j@cOI5E8$PE;z`JhxjmaPwrp{e`L$&=BQ*S?1clBXBwsfylIe_O}J%s
z>-Ir1-JyTS%^s&mf34=^b5KB20Zt4K4!#RkW)_yA$w~jYIZcPQ_jcfxSDQ&?T5j$W
z)k5ZgC%SE?r_5jj2FJ#{3kzu{Pig7teL<13va%8$kdl;aUHr6g2;Qo!?-$)rPQZI$
z-u$RiGAX@QZfx6u>I_F7k6h;v@8W#S7FlZGqiN?Ou>N6Loo$H!$o`f$5hU2>bija5
zglHEiOxDB!SvK6R=r+`;$?_3|Sr0H0+2=8x_tx%Oc*Fy8C?pon>x@MG!0+oQjs>pd
zbp)wZ9dfX<<AJuo#Ka_>D_{1TGG=T{p+=n!(4MxvGv5X}5)xSOW6;;$o*8%;{rdH*
z<_5tlF%e(o6a((T-&Wq=k7C@vu|WZ9PgZuee)lI_1Lqsma!z;O)_5*&-f2tT%y2v2
z?{V`%&9S>5LJXcs0puv_YId!;k`WvJ)j*NWN2ki(Wuut`XSiJ9yw;&}(uaaP&8S>4
zdfBns#gaJ?9Ug`TW=8bUJs$B<c4>n`uXcYBk1!uGKGY7Y_!-eZ&}F*y@E~JoJt1~#
zvUyac)Ipj_K|$dGIEcRfN@tf)Z)@wr1W9r_%?9l8p?RPJfKCob3hJiCu0wTM*~6G#
zZ=@G=UrrFbz5+r3gi}ykh)76CHjY4E^6~LO^HNzkjMPg94pVggRH)1J1`V!~gB&Yz
z!(d-;uDola<9tuz^C#5M#o+IYDFab@hD)jOs;MERESNHX_+@@@U#-{{SopZ@2z~zJ
z1-jdfI;e=yuc4MF5YXi!(okpy{B?c`Zka#tvH7^uV;a$O1SWjHc22`Wm$@WHMn*op
ze~FEck7BA}W%c&A9eYnt545ZG4GgqxLUfFbgsbY?D^+QM+V`<iRh#)yvh?ZY^~T<w
zZ|`dB)>a-34hA{Gn}eS9x93yI=~uh-#QD3NXmG~l*y;ys%VJ7gUrgHcIl?db^o*ac
zoKc~k!#;q7O2E0&(Q~5gm8mEvkw4}^8&p;CiMd3G3bCG=d-4wm&iFwP3ouAp&ZbfI
z6|2X*9NVL3vxJByK@)B-9z;>LqCDKVP{gxiUT;+e4Xqj^fu^RWUNOEv484|5+hWU#
zo{<psUS2`L7w{u(ZSBa2_UPPPN>K2Ef`hxOvNel++jTs_zwc;Qf2@lq0{^yZ3yYp;
z60BU?+?<-TW}@=L2Oq++#W_uJTXiSb!}I3C^tll=Zhv5C{;vJB#Bh$Y>F_5@aicQ9
zQ1~^MJB<6;vQkOovK(8F@gZy%t9_HH$|m96fmkown}KgI!jlQ+Z)%2F{fwGVDo(q4
zZD4xS2YeNh^5v;UCnnNCA&89)mueL90%-5mE9isFsBgGS0iuwVg#bz#=+iRd*z6sh
zor?f&F)@)&Cy{-9^0zUYco8V=9yl!6)ep_iq7+Y1tA!}9ofT>Si4FY_9}(Dd*&I?4
z!A^MMy32{jv@x0Uop$XNN5b{HpgdZ~)?t5snJ>=AhyDYRdWMS{r&vZ~!;<(ZztUy$
zrPbs;?r;>VgbB<J%uUQN50ugSt#mw01Run<SS>i2d}u=`X(`{;7cKdlG>>(Ug_03B
zRe}Y*va-l3Dl5IA6&w-nAvQL)2MC?vVcD+jQ4=O0sSS>g|6e0s8qO30S)twdo$%Z7
zF$6#nuq%A{yfR>jiU88-=Em)hiwIMr<LuA1mvlFmmnl;8LSxtN@N!KGhe_OO+=0o3
z$?db7mP<E%EGg)AdcvZev07@K!xsl~w^5)Hv`qEsPNOT!saTa^ZnRYD&Zt1y?=zX!
z`-U6tB)$p5UokJb#^-@{?!H8idV_a0SBaiHw0&Y^Yz&Q;A)}x_m1*BW<E^fK0d2eh
zOE@M<X7d5ERiH=>npWDkH_U&o-N3-Q1>}&vzCe|$jkPuK##pWO;XLNur`!S@0Mx|0
z&ilA4nk31*IB2=`jDS~E5}j)A@>aXAD5haOkeX$=Ju3cSw=c#@sSXMEJ3XH)n~~Md
zpTmZt8kn;RMqbR;<`)>vWpe#p1HzqsWiIYT9iETar)XONlt}yMjDFmoQTy_=zm6Zp
zMoHLhxZhKEtZQ~`_XC?ww^_Y+ses(y<GN=}q7XAn%k=tsJm6l~ci<o@2GqGknFjjo
zn#G}j;Fpw_+gzg{;Ncz4hHA*m!vPotkZ@R1a%`+8;3oU~C1yC!``26uE^cb^bK9#^
z)2@35v!lf3j&5mYy$z#xTb3ueJNk1QrJuNrd`@WSOi21v)c|MD45A?Gd4RiwetWlK
z%8TWxT>06*^*I6^30lk$)r9IZAACp$$+O|JnsCPRVMPdb;Pi&`;mr<TGVoXk0aObD
zikB_qlF{7EtYyb8y}FvEfW5rmfB`D00PYb?cF;@;zUNg^dI4rYrIn=fuD<|G03?fo
ziVE<1sHy}MCvowvXriG)iKdVw%lVL?o=4I*A>6*>k@Uvg&rDq07rCxFho=vk64tff
zYJ7n~4e3d3szI|v4gT2cyp!X?gZ618R&+*QF89+rHVG#0bBD^?rBcfrVd<xz|8jin
zCipmzI<4bF7Uz60TGF7pX`oBTzEM28?wYu)TDTBIA)Nar+~3{p3F?=GghZc&WKlsu
z%c}Kat2fgAB_DSP8v_ISeJhnF{m%IVU{#=4@M~!i*x9Yr-m0R(0i4$Y8V)%*c?MHk
zTN}u$Z=kr4^1bUdb|4Vl{X=4ej8pd8P}Y2@duCla=3Nf~YS%|AS6JQhBjwp+s4{_*
z^`rUuXH@4}%Qus|yzZMb=SB5Vs65b$_L|%+R2+P2ZyQxZ9vUe?AAlkGc3ZjMiDC)L
z<#E7&@Zb+{DL<~CeRT-1s<E5fE1-aZzK7O6m~C)$cnDHLMnM77#uCBLXLVKo9*p|@
z(=I0_z&MPElauqVU3z(W0VuAlt{zDWI~!(s{XW3*23cP9E6ru5sp5g>jG?sgw@7{N
zG`*^ls*t^=LxxQ7iX{S%-=HfhM%^=`*D*hCH=*#lJ1>1!7G)s<8cDd#Z1~HSw=d6~
z_HfynRYDIBt^etca&mHD&#>|EkW4j1M4o`|C@LnF4mfRJfB$#D`5YYH7qDO_@aK=E
z)z;#G8cZg)Up5X3!<{~6v!7@Bj~4*R)YP<0FJ&2X{-VCC+U+G(rDpW?Va1UH)gBJU
z_L|;gD22*(uc@WB0c-BX%2@*Y{E6jX3LXJ&B0+;+OsIa<2Bs+oz{om-stp@uDR-eC
z+nlai-zTp`R@T;fUWk$b4F|OIZ*g&mrW#;h0ZBzfM7$%Z{|60sjQ@+9j~zkh1FAY8
zsSX^kCatAEeHQg9t8em1=pZM`VJ!QtQk2|!X_L%XWG51R?HAGSO|5jWyz2%wH_I{!
zEYk|q{ktvoz6)&c%=FpA=N{G6iC%s%$;^*p23**ePN;4XErzawgZwkl1)jywX+T8`
z(AMNifWiShiBN^3rzZdum$%H!2mq_+D;4)tWlx&<00~P@4jo8XgX=6TEQ_G8jf}uT
z`x+`@vZyY9JEyy6Uz{(|V-uCr0+x`aMpk-4zP1rKzt+X0NBf0G#Vy-Ml=!O^;xH84
z_Dy0*%Tgfa{QNNP+ZHd#JrVd47($19UVa(-%HL88Zz}~FnoQP{!-~IJny4T)&xd+?
zJ^*1^0ANIeWT9d@0OH`B!2}jGVLSl91_#jqNX5d!(wk=a7uibZd&Lw3breb+_x56T
zl58V<JHkABoSS`)1MIp^Xq(3vJ%q~Kk;~(<k<h%i$X&fQ@SD>hK_jCsyDmz}!$fz>
zTp=7dw*VOyNi&BEm1ebtlxT7}CN9=>(>UfQCwVL_>4C$g6cF7*w*OISp=-Nx<EB%u
zfr;tG9LGcc+}+>r4N$ACEfXA(!(?4e&1103si{P84<Afghq<_@^<q0+#H2D{rW|@U
z^O_9NhN))QTa2dLq`$JyuwBxKEpAO&GKS^<&KQG9uIA~+0`r&UpeaM!r_B3ZB{mq4
z|7w45M7F76rFtV@zf)6F`$r+DsseP45qAiXIp8VTfYd>$sb=wu#>PgVS>84Kr6nD}
zOe3SBypOMrj~T(H3JMA7_kI{!o&DCa(9DIvw}vA>dln<yZ5rONE~QlXXEP7;Our%I
zG>9b?Gh)rbB&|e0J1#sq+$VNbAu~N8njOYP<1ZSv{&>fx7r_SxY!%AbFUj0chsK{Q
z-e$8ELH@keO-&(SP<ecE0yrf3ifwLgu92xJpRO(mW89Bh=8ok9pkRGJJ*_gk1WuAx
zi|X{06vB*kax$|0aWzYAYirpmWJq0AG+pZL47+xZslckMmKV`c&<dxPauW)-Y8_^C
z*fsi0_?nOE!rL2uA!90P$*Q}q>_<Vgk9wEhBA~auZ21N%l5k5@PqWX2^s56@lqO4J
zzIqDXtcB>97@%Lgeg7VNJaJM*MFpyc78ZJoW<s;3q^SuNV56ocu0Jk^;%A8WDh?Q;
z7#cou)x;183JPig<;u=ZF&Y_zeOPpl7bMOD4U<xu%iP7zWmfLbvolYlT6C}dPY=(p
z|BRn2Ek<n)9KDye15)6ZztNZ>dNqUsr4+rcqK^oPKT>D%$U0i=2Pc|1a<Q;H0)oF-
z3>^<fd)UP4`g$AKqr5z-fK8pw;o;#E7VIwD>KfHTK|VfM(0s!H)IL7{K<M%PI}b=M
z8d}=!2v41XtslJ`H<$6@j%!4bvnS+(Su3Jb15cTnSZ-l7)k_!c#cnjSBKiG!(iNA*
zwYe^Uy9pz7`hg2n1cH9a-swVV(g%O+h})lhqrFJ@azbqK#ZXVoCZfAr1pK0)&`{sX
zA|P7=91VPWGNM>&28M=E9R2RybC4#IX(OA1Gc(9Qpp1-+1OlZC7l;X<Lu<RbYJjb~
zjHcrZ&J>d(sXm9LsJ*`RRE?oBZVpKx=#C7cC>_OEC6)7Zdvuo(&tx9n#~hDsh1w_#
z7`r@@DVt`TUL08i`n~=-abMlWTszyp<<6%PT%y1Q-5j`>pzA79uYCwo)c?u3WF6Cg
z5ZKd;E2sicUq3W91|Ql<qJ|nk55`WOhKmok2rfhY&bmf^rniPM!V}3T2b8}HPn*!T
zna+nqj<h)6kFbdDhj7xr9_Ufwf2OE?@{RHW|H-z%Xl_yzZGTguz%wW>eg6{h(#MX8
zqM5wFB?CROs3^=Rvr+>H1Ov<p0BtPWF=mb*0?-}6dn3m0&F#~_etAsq2!f*2Fqc6A
zq3{bhEf!V1m7gm|)9c}lG=k&#puqFWsk4{@f0a?0ZHjgcbY_QyC(!26&U9B!Fc87)
zCZpt}f}JRjgj<JoY#PPOO{|08V}7p_5a|W$+LE%e=Z9?fqymUs8Cjz2%xtgV9(rzD
zzEM_>+`BpN>l25PhOsf8Oj&qWH+_A0pfA6mQwRT#7}`he)t~@lzoR12)GA8mEwxbW
z;OF<x&U(YGf(T*qP=iTOVtWi-P&me&K1Bijh<u&%R%xH|2_BqucKDv*<iB+bXcu6M
zG>e76ScwJ;DM&Eg%uy$5eox5Vom-vmg`(0bI~zAW{ZkNaV8Dy^Wx=Kyc$cAw0v9&|
zGzHO@t9yUaGEVjeTqUz!^ZVyhP{WdWy~0zQ78PPevHwei+gb1S29gFOLR^pO$e%os
zeTpLl9y!eX4P0&89*XqWIToRvUchSu20XgX?8nau|0~r-*!*DoA9h=1`7f5?bGq3Y
z%ZDlecz9oFVM(KZ*L9{aybx??8h`Jjz7rAT@ArHnwv_`CEJ=aC%s5j7fdLhOm^k;o
z>c6pHp0Wz!&w!B`)M;8ke^&g0pTGpd9Uckt1s`lXn4#^TyATxv3j%c336g(w>&LC`
zkL3d>Gza$G@%r}syu6R)lhV@CXv0TP_yRC$LP8{1OV%(uH@)%orFBva`D2;q@8!NF
z)4*St<L_Xd0Cv+reK%8H!ny}XKAqL*lt!fBMcjT3E<X>O5Q2%ylC|k+X}<#k_URMa
z-J}Ij=limWvgvo=Q2h^~yeXOc_~|*AJcAh}2puqahKCkS^*YECfL3j6Yyfck5p8&`
zV1)erc9Jaw^ls$-IOx`>@d&cX1|t+WRz-$9H#dffgMs{=byLXR#}76*JH%%S2sCT1
z02F_&@xpDx(=LurO!NlCzN<@E+1}s<21X00mOzyGJrN`X#=~F>Y8(!9lr7)9_Xi~t
z;2*#$K^6VXwRd*;_RSm6)4c&$R(U6FP0_Sk9x=`xajhF0fkqk{*XmLu*bx<Cg}V!L
zw=cv2x_9f?PzD+#6^tP?cnYw}=jn}I=Y9sF9jCsiS1MBX1Z(-h?;z9{9ToK*ETyLA
z{fwWLv4O!FkW*KnH4*%Ba3c*nxFcm?@AvPNzk;(C_-l5LNPW}dxnV2mn3hhevum{#
zo%O`|BVYb}t>k&b^3M<n<8Co*-O$D%s`#K1hnjUS*rAcoB2{z`adUELNCwR8z#PT5
zshKbZltGX%KuZhn2%-jm*#SgnjrD4PnKN#%U`16`T4p9ZTO!@Y5fonR?g|1PS5@`=
z2K!?G0+09SDy^7`_Id`bC`x1*>uw1t0Wd}Z??)3A@~>it3YFmNHT?Z*MCySHA!3Yo
zt{B)LYmPWlxNo-qs&b(EsjDM9YJr#lzDpop5HT>w$#ytEM<t-o#m3@Ho{CFI2tes3
z9$xAY+-;Sat}ZOl0ycJb+JF8GF=M4TkDNVEP94T3)^ykEz<ZNZr4RN+{U^p+o0YNr
zCialx(2xZs8xV*@{|ZFm_x*yrRs#qS-Cf1qKU6!so)s&>kINM8aXVQy6I@?kLm7~U
z28yE;D1m=<{{A(;^7g>{W?G|O1cDh&Tu~7VV1E-+(^T2q&s@zwi3H0ANEV0^0ODKA
z=ALw!-+cVB4KKs*+%W(>F&7iWqlnZGkBVFg4(R_mH@N$qk_FHN<Ab%jkvN9#8d3&+
zvHF%Xmh|3j!o;?Kl+@E13l?S;K5jO};)!%{I9P$C8TGZxi398PZq<LLrsB*l*Zu_r
z8SCq7YYPxItIc6jzcdOpR8fmnd-o@wsSXKXuXs<TQZQZKkr9h>spJ~y#Y!lv&r7q3
zR?I%Q2b&n#cV%bD%0i9}M&{k2@lk0w?)g|M?(Oq{<F*O+o&P9bc!yj-7Aq_)G_tU`
zlVjIUoS>Rm^)w3Tn$u1H%)cq0Y@S0^!I!829P~zeK86{+VALDq#65TVV<i-)2KqyH
zeij7*cl~>S&yDI;z~Ml@!gcNtWhYRLGCXQqr9@P<cHMCYVF1s&NBzD7FD`x<IXSU`
z<~cYx2vezw@4}NXJu~wKG)bUUfb@Qxbsy`Fj*ehT@h=qUiS{%q23!G=$M0%>v(v^6
zuCm1x&TmCpAuI+N-pK}dPu|-%1$O2@d6&%0y>8XHc)iY_-Iq`A)v4$2&^XQl+b{T3
z(_zv-@C7|F+T$+`%;e;c?qzv2IHD!w107r26KHzZsi|kmrUK0x{4h2)mM8heJpurA
zI5|0n6n03aB8x*$e&)r2lUEN?eXSOBM`(M^K2LsZxfqWgmPw;T`G5oSD)(;oXytpy
z0`Z53EZ)MDP$ha%O!i@2hh&@_S-L(bX1}E^VDk3%hN|Q_Ibp|B2Rho?5AG!aKmrzC
z;|3!DrK3c(P*_3&<)Y!gZJ$^SA?+(507@Py0S?#btOGoxT}OLJ&otzcVuG7`zlwJH
zRh8eT5Wkh*{VLiKKIB6lr|FfM7kE#6B3n996XU~1Oy{5nLleM;WMpK16yr#N2?G=Y
zvawN3Cpk5Odr!1L?|Oq9%##cyS$_kZnOU!w2lAXxkW^NTxH*bcq0!%9gcJvGADGBh
zG6~O{ioY<qwfzp*hqPV}_)A84Or{NpPH7)|FW6@zefD55{0S9gfDwIoyFIWsh8{XO
zww7&*ApUR1{{M!nJQx8zmrbaIho(45eXa-(9lYO$&xn?nrzqww#B4G~VvnWWH|8|q
zdvuo$KG+13BFldbVG1?4*;L`-mG9~{7yWne>8C}m>6hjQbsi;3-Z_sff%6EI4WOW<
zDCUFl^?z6e*Q7O?Hx+3$PS(}9--KaajEwHeW-tFx%2<v}SZqkQH)&=%|A-2hq(jk@
zz`e+|GcsiHtmR?i1_nUmH&8S#m~^`mt~CTKLlzc*+k1EGMeO4q5TQN(`0*nQ01RSc
zhnUa*ZPVU_aLFqgs;W@6U|}J}?5qG?AnmZJIkMsg_IyD2n+AE>#~$l)^u`axK!e)&
znYedIb#FDJczNIUQr^LMgJLF%g_m31Qrry!XKDrSm+Gs@GghzfFoEr#0UO0eM#z1p
zn>4V__m@vMHPKBsK`lQZN(%~*?<_x{J|I7R%7@{&!bC}3xnhT1ZUP`=K_XwR8*V4T
z?N9d({|u^u{*G<fn8=W461XrYFm-=LCk)hk{Dzhd0wOS_)od}F)QnK)_<X+RhPr$b
zN;aSnx>9xXTxaHgu>EwCzP>(K1qB`Ij`B5>!T@JWlZ#3fGQX_C%n_!@_I&bLfw+j@
z#{0=!gKsEK1(xR2_@r^FV9%if!V>a*{RY`EM5!X?{D{Ajb?Kxxo%^%BE-nrZ4ipRl
zKhWK<s<iY$^>i?F=-7CefJpuLVP1Z|cJ*{PxGOLm_iuyljqntviyhnh%vH#^bfR!U
zO)=X4$dT&T;%<U8Iii4y1@i@Y7IXs|9^J11^*<{>gGX6Ia$`6=Nh2^V8d(1Rh~P&o
zgCTESJo{YXe}v6z;1iL}mA)U)1Lm4C5SZo%s#q&Pa@yKF(a8MP)WFaKs0IJ-(K}M2
zw2$|M>skA&`;FERs&9YXk_SOe(<_NPm-M4@{jq&QO`pDe;Hxi=Q4g9Clu0u(zMh_4
zQZ2-~FF0@Fy^<d;oLvsh&p!qD3d}53-k}NbNiKf{G!$q;L+^vkcFK@N-ls}p1Pmw8
z<iI_65PNe*i*Rp7NULeP+w;>h&s*0I7`ADmzUNn=j|yW#Nc^~z8RjCG<Y?-gPN;ya
z(b3VNH!W8@(WX<{0{(q`1Lr!oeUg@){m7ykFFroLY?Uw|dYJu2didgOEh&cb$un=>
z?4cAw27I|d>jo=QvMAs+dN+``rz(5TRb+Dhz*+-PJ{1T+aN_6Hf=;3jm<JbTd(_f6
z58sgm(Eg(eM(hczeeH(YZvb>Ks+>w0aOQxzQvhw~wHsiQslZfrM=^1A`mw#U#+8vf
zf$GAnI>Gm{+Ok!0@i~4z2Mc>R5@cZt<D&O3KtRO2JKm{nJCOLKbsjx_nKRkMn)H5}
z@_24!x@o@%1BmG~>fiwQ0JgcwQ*bxyuS9=eVE#eiV59>rFo`|@N|G2~)9W?9mO=xH
zr-}utCc#TZHbKUJcDeO_mrbAmAWg0BIwj-ee2#zz^J?XwX7T^fvHp41o;8@b0Ae90
z2g~!Ai>Dq)Uf^7T-~ji~pM6%!KYyia-d8mK`N2i~aKfA1>X1L8CH|jk$wygZCA-PV
z`;ou$ga#LygR+LS#{;!^rPbX3au^tZr5R!Lfv-kX?}06@V!4~l@T=Y}vVzNwkK+YB
zk)k;4?CbytdINXi#YLUjB^D+o)Kij{Mx3#32y9Xy`Zy8>zq&^*z(paP7ZQA}==6%^
zj-o_)CXmKRjs&X&{*p9_>R%Z_{l34~$3>xjh}>8^%EVNMDaoW1ddlUAv4>`&Fz`KR
zGLmR=bMikk4cpNQQ$27U2PCkJygbJ65fny)hW_na7%gnLY|rim`ePG~AKL_dSCq$8
z1R+T`sLbcCs_0t@;@LkGzr`jE!aMy%8Mm#^p(sQBzO&YYMG2^!_OZac^*9M~Cf$Ag
zQBDns#pL7Mu0Y`${KlB3$~(c{iwib@34uGWw7i_8H|aCsLSHNcRO7uH>vwfM23Y{?
zVtU;lG8m&e{1Q6Ogc>wG2<)@j0Y>Hzr|9aFX5(edd`R)2#l8^QPyXlE$4)i-G~{dX
zjL*#LrY=mBhC9Xoz=to`{@LnHmSM>%oqzj;@v~NRfwhXJrVp4jwzR-pxjB~Qg8BRZ
z4isL{YkmQpWoapm2FFiFK;SZlD2MoV{AMU2CPik)Q7+Ko(=hulIL8d=zK~B*1I)vd
z-ySV)`7V$L^B<(~x6>`ne&NsNUsn5Y6Gi_~NX@S{O-h?uV5`}Us$j#?hp&RD_Y&9S
zxR~$5hv<UvxcGQ4@QX9WVh95cF;qYe0>d`|dfvo}gVulU@^`uppfhw~{vBc71q@HY
z7SaA*7$3C&m?IqHJa!X1IZ=sCutFZjLEx_dmU_Ra4WsJE;5*1x1-p_A<4yhkR_|N6
zW7gl;RHQrPh$b`}yFYXm6jyc|zL+#3WpjE11L6~qp$7+6lc$W>$bW}@-#<RSXaE2o
z7;eB}a=Z#PWA)RK0Kz6LoWhUo<gW8)qiDqviAdbH<-Cs%4Smeex3W27fBHiLT)q9Z
z?q;gb+TrgiG8~K}Oc|IOMHWD&mnrbCUsna40C^7o4@4m16dj({!1hd=>k~Pmo#uzy
zCaJ89PCPt3FThF1@|E<bNB(Po**F3P66$gV-rWhjY5P`mkxYgcM2%OweiL|KXe;6#
z0WQNYi)nz+9Q`^(fdbzH+6O7*@6f>G1ptxXeqX@(Fu5<Z_*UhO+8>oam9Y`0NRJW3
zH(zyB+*(9lBngDODQ9I&0AvK@anNvqeX*;`Qcw^9AR}<c<Gyg!)ggjn0%p;ZyDH=X
zwhB+LFf+tWxns|0<Xe;SU!h7w6A)g0xiFT>vLQ~?(b9BclmG1DA+D7C;~U~%jN~0~
zhfyDJG$m5__`R{Hk#XCkG|QOtsZE;~{D67YwD%QG-XLguE>L9t9o0kb4@DNT!)|WP
z1W+vtgf*C#WHg@k{8!gksrrwu-!peE35g3*seJQd4&&eg($9t~L2}7W>Gxd>LL5K^
zEUh!g@_jVLRQRO0RDY>42G#v}eR`Nkf#Cn9u+b+nkh{%kit`)wmBfdz)8suaTLijX
zZjXaR6?uOt5-}FMaVMZH0oZVFaun_<Q~K9N!t3Pb<b(^<!u0g?GJV1T@~E?G(hPAu
z?x;&-dFS!K$J%x3TVI?8yN^GjS3hb7p(82|AB*F!ni2!mOxJ(fALL*|)usT)`||@q
zjZqFa6gnF9;-jYPv;5en|BtP&j*GhcwgyC6LO^=xmR89Dq)SRdBn6RDLO{B^yOfY_
zkcOc<rD5pq?idDmzv%Pa`~L2|^YIV#51A8t?X}k4=bR71_q4b_qboPV8E|~A2)7zF
zt);FIM=KeXqJY$9XK$Yl6tZV$XQTC8N`r$jfC2--vuFNi@Qx1T1?OEh1x2|ZKN*8f
za=c$<tx4U9%<|7js*#lL-6S8Ka%&0YOKkWGjN~&7C`fA>Hi;-a`ia)!`%hKf`wuL~
zt^qzK3qZDmoxHciVJpqFU$#k}n>6Fd*Bt@{{OW3Cw=3k(1-xVx@S}=PZi`Uhv;4Jg
z7z#yA8)CdZM-cs6q_wP}eaIQ78BB&BKOzHDR#CD1W&oc)1CW6XX1Ay(sgJGC8mg=Z
z)M~QO&m$Sf;+j}f@V5!bFnGq|!g1fk{R>BbJ;S(1k>6Um@lr@%pV8Rf3CifhHJ@+X
zacfk7fR0mXZ9kCf)0}<Gyom;cp&bICe+g)gG_Kdy0m@rI-y_g8DWim=hYgg5fc}IB
z)@5cU3$U(Z_Ts&Lpyd%DLuw*nPj3gx^cRamaVV<?(d{$FqBEehY@LA<Zz2Fin2yx)
zUlhUr&o;M#B{N~?Ba!taU0Zw{yr+G3A`*Un<{&et(&Ar&mty!xBYw!p?#xW9&lad;
z0rUiLdfGl>-04xI4Fv#o4WL<~sI(N-EtM%rZSIsPda_yMGGIzSf>Jk-Qe>8*)z`T;
zW}C}aQ-E<)mftUFJ4ojr1QPno2{i!OPQYK~@!09DzS!j4eTPn~RjX08{H!u=q@E4O
z^X8eb>~u<lz3yfoPYyWc3R##Ga2lYpvQo4Zit6U>;z9--E&{4q-rX^g*@#heT2&FE
zChWnEZehpVC-xzz!en}~uA{!NvaxL-S72zr{)7Tt*%%j&_k{4FSOR=7{@P9}$O0-z
z!+Qgn)+-UeGFiJmFPr>IQ3bjRUMtfUUf_L9bwWG6z4z_sxNpXN)Oz@u_s8#tQWRhU
zzWBbhX!+UFGNS@eJdKS<&W+LB`1IvK592$4DXt4Q=Uy%7e+%I|0G$jojz@e~6#2^S
zR-+*Dt{`njcRN`ocPgRf@~7s%nE2P=2Bd)s(ugyoiqM_eXR-oL%_}X(C+h$ztC6m~
z^1z*ba@el0$;)}&MHJ!6{@?8e`D(8(b+xp-033So<u7mOjp^j<oJ>4ONR7UA?6T#A
z^o$lEbrY<6cZj)NvQoc!z(J<GJvAOX(kBf~OIA7|JpVm0%@*`DG;)T3v&-iB1mS&l
z1+K~qv?)2Wmd_)bOJf_o<wihfcnr``z>~6wfUvf{{$Nr9hcUcy;j<xrevco-*^?))
z3HV!O2{3lMQGQNlOEuh`t}lufIG@5w{fuyo7VUM?-A`<#`OVj(x*JjJS;6C*mkn~J
zYp^o3dm&n<+udD79o_dp-{71pLMQ+|^mBrb{^X7_01SZ?QWy7dPyq@5!_=PibT*FB
z*yr}o%ZF4yWn(Hc<t)UuDLi~ve%#@6Cp3k0d1psX>NYwP0&#3)WE8EJ#x(6+CQJNp
zF95;9SsGp3W=*y|?Hk)-p+&c$zE&}~bvo$4SAcOWXe~a)T(JX5_W^B;|2^B{`w&Gc
zUkjCiDr*V~9`i1?8df9au9<^j$<kZg2^3ku0=w;Zz4v?zCu|w2uB7}k`Lt<dl#~Gg
z&sbZ_%7W6$$$4Y=RWC+Y0&lvM>K)dULdWW%k^Opki&q23%`@{xhhcl%b8+r@t~lpc
zPIZSen{)!bw1U60?0il0|8<jX{s3|GkIMe2Af~}U&eA5V(;20*?{^3rn8Ju?=CXpY
zaV_FDRIVnTFqUJpk2@RG|GxrAD#xc!1EdWa%bPW;Z)QWT_)_N=%N#u#c_BAVpzV)9
z^af$~E52l<pnlJS&`@ND_7FK4F@H=AIm<sg=5e5V7Mq9<kOO{2pEEr>6{d5NFU>)C
zbcN;{h8KE&#gj<k^43`~gN`Ausz>mKTGnMQ;drC!DQv0of~$SH7316|W^?&X4ki28
zr8~ox1niun3nt;5S1N8-j?D3=MiyxJUG9&~m&F8}exT=iJ@>k+jb9DB33dB)F~L}g
zD;vWY=a!6g;pWBJHk{U<Np;=oo&$G$CJ-u;e2!sPkka0rad<mLPkx14>ZWraYrQY-
z`|EHO<`eL0<~Gi;;|w-}9lzaXGeoIgfKN}ABITo&S-GoWs8#}4(hr}1vdi3*B_5t{
z%d_&$Ccoei3Qi6Y;7~}8E9;>9Qf{8xn#*v`k;%HmvhuEKl<vLb+U|093W+7TdDml`
zd+Ay~$gg|xxwlb=pcVI3>kBeU-c*6wWA_y=oDW0y`xQSZ`I2w*Ov3H#P_9!Zca>@6
zhMCVk|3gk5|539{b$=L?VL)GVIKa3iuZKBWD=#2ef*3NaPGrw1zoo-;Jus`-)&0Ri
zPxU2lG^z4vnr-%v=ZMk?;nL&P)X#Rh*#w8J51(z<d%wxSMEx|S#4_fE+jkbZfMvaO
z$TfA?8^oNY&|D#td-PY~(Ws(4NXiVli4n^Y1SS=rsi+fFWrcpN+2mO+Pw8)yDG&4a
z#z;~>l-QNNQFc1iq^FR76T9`Ii~OSonE2Q^r7z@%>P_hc5aS<~kBZl&pY7DsfzI8>
z6|P%p7cQ;b8&(hGn~!Bd`-(w-y-K_&?mtqCzSI!G9B5`y*&E#(_<3}4nE7!H`g0aS
z=k$Qh^>>Y?H&eKBhj1aPqglKRpMryXNR|h0YL5#di@JdaWn*spGo09MYQmk?aA%Pt
zf!0F>5!VKnTImL951Ly(RmM^NAjNcGb2C#=lm4Ua23D1dfYpxH^aIwNNqDQ8BlF`~
zjk3@MvuR^Y^d<iI`!#Lh;OYpR^sNo0{>VrsuC1}YNDWwZAoPbCsPa1pML~KgWtIES
zy`}{=)E~;tcjrdHFSq0dX8~hX%A!n_6S;G|BvZ1XNqPF#e;T=pW!c@X`>#7>sMmI@
z$p@$_zap`R?5Ka18p1?zM~u<!fn&ayv39FQ`Y71)4y%ZgOmtxyM;1qhU=tWLt4xyO
zUA8wRQp=G1PW#30ZvlMi?rYfTpmWd(-r)_|m2$}0mSPraJ=v{6u(cmVgq|mkimE*}
z!w#!1`&*^9-9O%e0Q#SWUQ>UlDF#c^g#MUkqJ$xwl)|}??;&dx6A-o7##^NkSQH3o
z)n^fx%D6Hbu=LFT$+mKyw4*+r8+w>;RC+tHY&2fBS=h=ru9U1Ga*%gv1QI+5ylkhp
zbCeXoF5Zw3pbtlGL<P(L<J&X-<!udrDDSa?ui5?+HEgigTz<1B?o@n3CLp#7fG*j1
z9Dd;ZQ3MuA&<fC93KW&@9{CMXXt7Zq{K84tmIjj*DTu&;Ulx4k!+~2VvnY~O(jx&Y
zTaIY2A7K`FS}D58b?{IoAQ=0*w>SVGiLx_9$Y&Li>g>FvaoMn<qM>q<PpQLwiQ|F#
zTd9%7j3$9eFYDPnhS4{`u)?&*%zL5Jco9Oy=yP~Ky3Bk|n<ki{u*f#9^nA3m6#Z+*
zO*)O+P>7^*)?rD*F+qq~u>Q2!A9xN7R3!UnZqtFel_UQ{O>vZ8UV%Oi-ugUuA?0Qn
zIl96bzUsgPPV4lQGpal<Fuf1XI#*i1w;tl(>*o8=!awEf%onpApy_Mfal<7EvvJ6l
zPm*aaqkGp|dN#i$0sWH}fzu6Ve*#xd49MOuJ-M@OaaC6Ekn{kKhtGmSDL%8}(Nk_B
zr%3xf)fMkN;#SaZgGTFuE|`!c?(%gS=sKN~(7%w0dtmXZqcyWPf^||nSvf&3=TM9A
zQ<S@rg_$I5Xq6(&A@gl0582sp!Gv6Q<e#wtqTugfqu){^gaOt&lTAJnXl=mt(K=C@
zr_*|O`JNej13DX}GycQ;l8VPacX`TO45!cs%;R2fq6?3eT12xTKZuYq%<S2A0J96P
zbFEm4UG7JNSERAwRJ?y^<9{t*?t^Mm`Ko-Q8O3`}#6$)|2(_^4`<3Z=cH%M&E7Z+%
zK57=v=IZ;!7{y(_yNFrLEV6PQ#+=zRR-#krqqNn9D4~%@Sugp~7*-|;vrP5*;is0h
z`0iJ;432P+``Y}Ljc`=co_ttdN$ynq-{!QyEw#Ths~D9=C@(>P7-og&rzspUx*Q?e
z?DYBp1+`2-{^v%In3``waMgs=d{&gUXYWL0cLh)MA$QRFi83^JL(#Jf!rg%6cX_J@
zW3Fu{xcz4_!DsW_ZdUP)`oiflB93F%cQm(K=m(hxQX(&++>b7e51}*=GF_n~yppAu
zEq9eLksnv;uFEIgTn*}NG+?hRQv8G8hJSY&Q_er%(GOs`8EaYRis_DU9ww4&x=QU;
z0KgttB-rl(z}7BABB`lIwtK8@nO^u01VU%WP$JWH7abHJ2#DT}`;V@iE<+wk+A#US
z7JAQohEkPtLim~#L`q~tsugf-Xmsa@WV(XR_>v{=x6N7M%0``5UHbZNlz07c`mJ&M
zJxY8(r=q^M{W<hNlQH(E=b4HBI6y-pi)sFXNlseCE2B(Fd_N_wA?@d6`p^9s)0-<?
zj2U5Oaj}domcMoM@0We4pI}{Q*RA#44w&b=P-j|SG4OciLd4a&jWJB6yZ&$kETqjw
zKKRQa=8+`q4k{o-2s)5}g{_yl^1|E&Gf?hbmiKRjd7EQ`?q8h~Gzpy3efm~T<H#0F
zDAe}H65q1>XUgE|gm|6EJ|+n3?UYij>mt5=H9)F~d-a&U<{q(#ve9!cM?adHItm_a
zbxp4J{%yzZVc(XwY*pi-?M>fNV<*hZ?C=-kIL>)hw?Yo3^)CgHozr@^%X3B8aCMYo
z7UlC?D}wDC5r?Vtr?;@xGH{f;`}MOxX%HKN!e^ot;ABQ9@P;FCysKGma_CwM?cBow
z_drFWzsS)+`5sRN3oojCS*&yTZBO%wiSji#+Cgo1OxgW1!Qh&ZmwTu|+dou-8&9pr
z>gJ`ab_46BNkDg<*Dd|&LH|DU*yXdG*AFs8LFDSaG(fkws2T-*+}Dl|P!$bCs%0V!
zXm0apZmomdudGy)>POn`jhc%+K^)H)N$ol#bCEo_k5yb<Ha-+xzol_}qbf%lVf|pj
z(g>*krJ(p8rjim|G5~(7$Ku#iUG8Wijxah&f01J^poB9Fx*t8sifecSe8EwmmF#ie
zI1J!siMKq&>VnY1dAG;c2l|I>-y}cir?c+49r&W3lLe#(@Fg{QV8N$o+#G1Y$u6Tf
z`?xC-un|dEYyC(B>_<>({mA{0s-s7>{g=s=(*zN(!=Xh~C8`sTXWM7Q_5!Bk=GjI)
z%qO&b4-*-vi1^P;0@>Cuo(dKPfeW#qF8UNDHTwm6u7S_ZvL7g%>0Ne0WHgjUTrT4%
zf7}@e7s6xb*910Jiks)mo4b#Xhddf<_7<SQY1Rv{1th(O;{<5`Ss=rhcmpd%q;i(N
z2SYT?ZCBI*BgL*e#32)qqGA;XO05=!#nd9rP%;a)tM=o?ma!0rHnL%<O4O9p@eT-T
z%HiCDD9uRxgEdV2z?RHNWDFGk`23Ew0D$c-xP$TZSfrLuSGdW@)G-zoNnH7!EJ4AE
z%N;9n98gG&AZWk{Tk1YXa=b)7pC5HqDr+iLM!iVbalxDe<L^kn$(4SQ)Kt%b?Rp%z
zz?Tdx^m&5`DR>X~sy@d+s5EoTu{lK$X<Bw2M%+IGy8GH08OCF6#bo7+kaU5v;qnmO
zp9>d09gAoHKSV14cJzY?38ob@Ak(s4{F6ihuSM%Zp||4ab-t$Z<yNz(MPH1uQbtVP
zxmizv8{Nt|X={KW59}hL78<fTZ|GQqyTI1odCT(~DsN8}iw=Bma7OQ0qX)%`8th;(
zz>#*j$&n_UWwbOvpiX9yY;%}VY1#5jJp6~m;*B|D!fAh#nw{l%+LZ!dsvf*~Z{EQ`
zd((~mZnG1mwUIfRbew@+r9Jw&#mgL%&n7Q|xW89U57x@gY%GK>R5sR_!7O5CU;H+g
z;`u&3JRM}z{pw3dJX`PgSP88ku^o*>Xr9EIm#8+Lww{lkh6vFeyS|sF8gyAW1ykkA
zxE{GJ`dt0Eh*-M1`h-k(S8JNyTQ+;nPCZ|{hxlNSv%P~8J^17sHVD7Abdm8?GO*kk
zgI$_}2{ji`x~DMB5>=>jzvApHI$>CVV8Wr3b1w#Dv%XA#_5E>s9WI-);hdrVo(1AU
z4Y7_N9qjnjaP0F~A>$@{%Fr!E&2Kr<{!`0?c9JdRNtmqlqwV`kJ4OY4c=fcpQ8Ch}
z+j#v2tc=Qb8ISsK-Hs2!?kc=o#)NYzrCwmq1>C#swwv0NymbS~=<{pI7d)a^YL<S8
z4^u=VPvHD@tkaa6qD08|5fSh5!F!zk(%Z*-_$I1p%EXb)J9?kp4j&gmF8eu&>t3>E
zCrqmZ!__b8+?v!Kt)&+xde|D;acH!w2$fjVBJ0PE?DIl~`GfiC?LA4c(`g09)~R&!
ze9jVex1&%^wq!Kt{kRvUKSqL%yO4|{OM3b@?XAvwj8vj`B@Qp2Ed^VwV{K-CVlimN
zfq_~V7vTu(bs7x6SOtH_(O3Hlwz&O~hX3`giGSjcL>ru3WUgG?OP!xzw(mfaPh7=_
zRVweEOkHddJ{LKP@LUo}U;>*T+z5QamNmHu?=zv6Ko|i-TkmX)@5l)A`n`ajuZb;X
z=$;~UOCez#iesO{S^-~5Ozf{O99W1dA<62;p%EBWr;YtkebR9~MF!s3&tVL{lf8dr
zmSpm3Q1n^T{3(j-!Q{>Gf!-?)DBTx%YjlTif2^+&@6NP`Rz_nG%9ccBR${Jz^7Nf%
z-sc;pfwwhpQ<aDnnC4H|Ki{{!R6DqnAZ5u?_|#weT5&x^HZ9F4xg#g}hi68nHufMr
z_3NjtYdQx=5g6lm0wDM2erdr|;$VXBsO@&Y2kn>zI8)15DVBfoe~L^smxds#2bL12
zV~+r9;&Zmm97`<_X&P8E9R`|tE-aPntfo@tD>wo?K48=TmaBa#kmvSo;+_cQr6XJW
zosMhvP4Si3rv6Wh0=n$Fhg%;1rcBcX&W97<eL`5nL8h|hkkWJ*3{~0Y6rb}NMKyKE
zpfba7v-{WnZGwu%ebWmynWVgprc#=?gVW}`&)$eT?3>mgGOR|QbO?(wj^tpv-Me`R
z1q=)k)II2l-wfMP&>W;jZGV509e}jY7w>?R)JO}S<0>J}K<k*8-wM7NpCJP~>cL$y
zyRk=JGK+r=;|0;lAsuBlbwGw(w41_0L|hO`g)TVf+M%it_aQZ|yQ<Tn<Moo7pNra&
zqdKv~^_@sDHnO+G5r}`T_h5S`zhkxVAP$Hgmd021my%w~Nuh_=$*c#?GNqD}R3<&y
z#LYcUb<-tM@T&&qCoffVtYa-DHO$;bHxm-2f4!>bAvp8*{^CnSlEAZ<C#s8AP>6J{
zycA}AQZ!&s*k40S?93`S_VQ9bVk8MP9mnnsO`zEv>5F>^gC?-3szy3mM;sI@g>bJ3
ziZzNqL#8XL<)<(m1eyo~krHH*fp-on1xIJ+`-eB#!kvZVJsqA>aNOb}v`o985V^bJ
zYP#RNQV4VC0tdwZNR@-zcGn-LflIsdI2eI-bAMH#b@+5N$mQRCi11*bodRo^fkj1a
zv4X6j>%=N2D1x)>kSmngtKq4B>56`SC=dq3c22s~`yGw>o9x&@58X~Kdw=r2*!FaL
zyPqWoYH2T(1C#@{@#eRqQntVAZhw7Myl0I=^s_*jB&#sqA)<yB49ok*3n9<KT%Y$p
zWMz@jTwBlI3j@_5xL)~;UkWE6z<=FOpr?%4)4(jO_a;9i-<0as-mPUG)v0P1uM%oL
zxm&)tIbOZfY~R-Z3S61S_o_b{V|e;cr<Vj~yviZc18})dOvK(Zd(JyUUrW3Yp?fE^
z-$My|tgt|>@aYgi!u*i-)%$Xl+5>y0_xDl?7irz&66Pt%l`qyc_Qj{GrQd#Eott7&
zxGGovLgqQKgh{DP*B0dkAukB<J|#gqAJ$1X(8gm3V8j7ye9P`vX~Z2ttY+y5&nQt}
zsL@rOQ{txBPWKckN9m+mpG9eVEileppPW!=9w}~%cWP8zA1hsurj|;ZAsm{@s&k&*
ztIj9T^m6BY*%dgm_Toy=2;_jH`+6wJszq=*BH6h911G~G?i^U%dsE7xjqulpxMEC(
zWhH0!;C*KY$}XM!X6nygSMC<tRsjo=e_DIYKKw!L4?E_4i`WJs3--8pzZty{iVg~U
zDB+K>5P5aNuf+4-DO9@>K!GNjLdrIY%b-|6els(zdsw$Y<wnj6X#|uxySSAeYl<8?
zp7>c*gJ+1Q?5D+p5cQi_i^n@<7s^oVF_SGh96k93s8B-|1P!c;I<4B_dQ!Per7I&Q
zD4|(GK}q;Epnl{fkD27Eo7x-)LGe!T@y>wWv{T8Rgc7|3RN&32E@~vz(fVLbD`w1w
z4O@-=l_0PhY4&p;7x~YUVJummIMeHbR9L+Z{EH`QKh5lTsXPfMLBx_&+jUGczwZ#S
z-te8X)9Sj9&rHsiIN&|Vd5QM`?gN;b2>E_;iTEzlfkHyU8TY7t!(4J<n1c$PM@Wn8
zZR%LEdg$nHkMM@|(l*ELkRunVF=b}9Pme7?VzTpT*<Xa4Ken9rVl?pSV9Fv)R3j2g
zidMaFQTrKwBwj2ECUB-D&Owb}B+KdEkt3p^kx8K0P|cZXJrWY41O7tUpYOJInjQe$
zC4iGsSo?Tg>uX?1p5$PEoIE7pfL?8RfLefnc0y9B1O7eVV@hk&Ir-~kSF%X7Lpk68
z!mQ_35e+hS`5;Pegi;lc!bhFa#7{)HAqOQ=V@H-#SRgemmk%=SPcM+|u(30(>~s#f
zN7r+UzcfP6*}Wg~whZQ@2ZIjlt>)W1E`+#;Ajo2*zK&cM3Ts$iY%>{XkNslbXZyaK
zRaxU6^igxKW2?9w?TX=H3Z!=RFNs4xNzZJa%Q5KKXe>|lpd>zVSDQxpfU7!wvbo$i
zY=pWq^1+#JO`Yu=WReIfWYw+Ggt&fDj|9y}vE$-pNw2LhYh%#Qs!X5T-4zEHx7Ss!
zM2k7u<<QTkV~u1Aj`*#tzKh<Mz-jR;wQGFh-qCz3al_+*et9%e+Z`ZFT<=B<Hfcf$
z$;7(I2*d5QbfHFOuh&?f9uZVFAeF8&Ht^RBSQ!!I4lYT@YwVXv=$fovV09+?bK)_}
z?*YJ7{PPQ$@A*6p8+WN_-lO@xc--B=wH7Lbn3j#CXJKE!)AqdvX?+&t*I4_^s3tXF
zElp0oxRNjSv$G%uwCS5-=`wnvjg29{VrYraJfEN3>@OCBcmjUQ0Z}lw0#0Y!jC><&
z0(XL7XWXd-%F>KWHmedIm*8j|Yt;~OR)E|ncE<W{$DWjCY&svtZ~FQ5GO;o`_W}BO
zBh+mbYRJx$$9PbzCWh{=SF7-k@DNm|F3Z)8)3i{R1_ox&sOsEdmy6k7>(CaxUkqI#
zl-+8aD{X7<8#t>U83U(o-uaVcF`8L_Myf&aKYQ5wBQujX!T%%ly%C+89^#&j&fgPr
z+UR!=$rtZ#jYny9&#Tb=JR7aq`fA(|CX>xW7o4#pYl*BG-rdinwHlNU_E+h+vkr!p
zb|jUNt|jR()r2FruPog^ek%uTdyPbpMgC=N{iyh+bjRe^M0V8S*46hE+h5&)pqF^O
zt+G~qNdOs9mtNHw1#|O7=#7FQ@6wNT);7g9Vid0AE`N9-Lx!w`j@=!*EIYyO45}?5
z%NEVzi++?eg|*Kn8wf`vyLuT(Y$odvrMr1EM@J*XPMLhpki!%eSEQ_(7mTy|t=`W%
zb3E{8;1l%>NX`-xBsnEHaD0TXXC*#?rqtZX43RuAEb>+9rD`kRMYY6HfbvDEm!lKT
zieSaCQ5x0!z&mKq&dzbY35aUmNp)&I@LdcaGb(&o@ZbS_rt0v=5rI=)0*1cZXd<!g
zcCs&D4VKucYt{yiM1giBaem{mDDJ|d(fqEtE~S-Bcwq|ikizK2EnHnElQJ>8-<D^A
zif5Zrhb`*RzPwW-n<u)jyF=2#TwEKFnq;x`?jECX+>(cvfBE&1L*BWBxz`)G{hAM4
zhRFIE+{5!Gt86s;_jXcSTnXr5Z!cC=pI84M!yQ8?|2teBm~@oj3G&`xjJ5HX*DZ-N
zH{rgmfqN$uOpAA~MbQ-OD3so2S4I}O{8pk0{WM=9vSYi{vGrcZR^#V@fVXP}PlmQO
zUS2oaSi2WwrG{8{`-G~v<jlI~c|hyVmO!Nvq<~hJUs%WU1ol;#(t+36w*xXFP86y)
zs*3@obf%z*w~jcFiYSq+Z`)o3az)dKn~bg6b4`!SZ;mOA=qWL1%_anoh&+Oqca^A2
zrWF$_<f2n8xDC3GkJ)ND>quW-D1Ic<H7l|+J8^WYb*z_vz%m>F%X0q@EUQ7-F!`cI
zlOZ{{MkcXvbZB5()fQJp5j~PR>e^-?WjUc2`^8NJ=`B!7DZ94J&x7pp^yEW;{}KT~
ze1V*tV!?Cv!0>s+6WZ>*aI|(reuXsbmiF{7wLwA|JmB7vv!lAc2p^Nj;@j5J0#s{8
z?>7OqxkSqxZfTcZA_C_G95+I^g?;AGuPm1<^|t{V6#-jif+P2wl{ovUSAva<H}8kf
zPl#4QX&7l12)9J;o@KMrk#C(C6{^=9P)RRMR<p~BYY$4=%v~7wP?Shnb>G9i5C*Fj
zC+kD)uEj014`mxe{uH7|+y3ye_Hls4fDvN;L^8uCE1Z)6_s1cdC_2*)qEF*vH+YDP
zd$gxLM}Hr7j7u=;h$oDxF>k*nR(N+ad`X3cxtliS_V(J*#+24M_e9x@%)5Qfi<=~T
z@2AGM+@acmdbEJyC_s3*WCuL5k_;p#$z$zCV+K;z6U^M%KI3`%-#6&ds8R~_9>hEn
z5zkeyM|_s6cj%)k#q4}h=*EH$Fs6>@7og_kL6U9j`i*$PmoiA3S(fG*_->m`m?rv|
zUs*0&OnVibOFrm>^oVD}Ev?WsW(5phIs(r>k5W-t!@Ax)Y;pbS>hsiz`ag9<8a7NI
z{{S)lA{YDRI3~jOB5_P0llZ$Ffk=@v%)}fBS5hM;u0JsJ#0uqK8y^U)TrqXpHJ3<q
zxm#tVw5|(0yfQx*E*N)E4ezseV2W1}pBrb+yh8h7hEX7@nJMUY0UpD%NrkY2PsnAt
z^eT9CtE3?UGMeG&>Un&c(_tk|IGt5A2?m;AEQd_YYgb8L2#bW~w@lW}x6ijh*y}Ne
z68GyZ^IOR*A*4k8j+<O(ska()t7E@;M*SBm7QIc*o_%FG^lgoWn^U+g&<Ke*qe{8*
zzx#6Nt93Q{ZhPeuH>vf>`}zkUGXggG=Kt8_s+w;tQI2XJ5_V;+>@Vk;NRcbz&?YX0
zPga^7t;xulFNq{~7d_jmN_{F0pEnGqzL=1+{cZ5==f+*Bc-GaY;5vraOVx$M99R>E
zqgI_?Z>Wk;JZcLC3s_xYtBEc-(%-VhX~(faF=~|3-?I7{rO&)s+qRC%dT@1+1((|A
zx4t@-))m!%wK|i4jL_;oGY$kbX-z~QsA8mSt-7PS&)qAJA5YQgz&b5(j|A}fOe||r
zI5IZRpv#w`wDl|4#G$>VlOz1<{wC56ALPmn0IDj5Cu5Wy0<HT|vwX@C1YK#?2Jn05
zKk+-OBxeqL$?6ZFG2^1OY&3;>x2B29xYtr>tEP^9<dBe^p9Q=I_fQ84pCNFpznmF+
zG31c7hh-+ufy4&0#k0DXo1CP;Pm|lwX%az!26qRBjoP-1>+)VmzCk<+Gr(s(&v^1B
zkfFaU)67Mc?Cof*!Gr1a3Fj<yIfOVe(n52|z$@`>loDCHeQ<s3`}M2Gz~k3c2(l8d
z)zn*^TvN70wmlHs7BcdT%0er_K3<cQ-C%cNJ{P6T&2de{51yH>g1*$(^FA}+{^1wp
zWDLvQUoCL3#J=BV(eK60>RP)bbevp>n19(_zoUO3sg+b*fAlhy{Y&6hF5&zKmMS0Q
zNqNzG+Cv5-L_!f1x;SSZGW!M;<@yDqw5xE8YV<ul%!QuBsX~%I`@Neu>I{svw>grP
z0-$^;JN*eKu_wz7RcNb$Dq#*Q(n?aiV;Y+bbVo)Lgp)>_Mj2X`eRQ2}Jil&%x&9HU
z&soy3ZOhWm7>^4wk|{j7CzaNSuR9+m>=G!v*55gVdLY?A*Bc=(;(;8!h=0j{YSwT{
zZ<hwc07S#bxX+4a+5UwGgr=m^L7!tV`=8&EkY(xbA9VV<d~k2VKl1?ynZ<t+G8BN2
z4Lv#%Ie*B}%ul0<v<72(DDEiW8#D@9n%M%h&-vAvW?{m7ebpcKCT-EK=FIZrMvZ<K
z-s4Zg)kKD1-=h_3U#R%4((W4I3#(206oPzD=C9%%QCBcWCn#2e4Fs=Tuab#hyXIAB
zQ$!asuk0j2M%KOKh9u{;C1ioTY@En3ZnSQ5?7OwN>xSIkBoyW{`pRxylNfTcTid-W
z-nR97bJztYV$fUc+i2>B@fw0ysxY~9v_-+h9g#7|op(+6D^_>+pmQqgAxSOQ1M$26
zzX!>Ie5Cm&eq%}KaL89Vs7=ly63f-vO!5_Mq!6|5SYoYis6P8ya5<l9$sp>#H_u+v
z`daV{z9b?h*rMw?hlt4@%F*2$_0l?V?%gK}Y>u$-z!E!SVRnaffLmg!M;7hL;5^>O
zjigDCz|qw^cov~ENr5Xi5>_I_W~alhZ9`d57k4T>fCu5QXZ}tNDJRp-V+gFrZ!{^u
zZKf0mbd*J;WWR;KjHL6J+uV|kh7;Ev)4>MaP%ql-f325_l^60}edyrd6d)&=_s8f*
z2>wkgzb0t&O|$-nb0>Km$W&L~fK2t}KQomNkf{=ot^yx2l`)dI!Bc*tAzGI`e#g(d
zOT0w6uhMaU5q%N8zQAc+Vd|bL-b7@MjDOE;V?lXM{hU9)iQjNJ=}dcsyBcG&OM_-n
zC`fhJlym0^YJ0kY4xZ%@c@}DSCw>;I;Ap1magXtQuK2DsRxx&IoJ%Ha{fH6AHfZ`B
zl&V?B0r?ilt}ibr5s{03`(xfC*v8}4%7n*VGw0}?-P|e>M(<(k@WkTJ`;~}grfDP#
zOTuV3+F&Av<ZqT8$3buMsxN33Uo@@xoB>yM5U0L-iU{Kc*k=9Nf2t|~r1cP&#2*$p
zRyOp`W-a^<FFYvIdKMV!dhUxfTogXJU6r!icFyk=oRc<mZ{k!N_9V%at2W1+6S#7_
z+`c7~>W0bVPcW5*XAE;=QwIgoj}z){S0HbT9wicxsD@bQ@)01`062w}L5pN*Ow9h+
z0|#}k568EF415uNpj=r}sE=dJ3(*KH*^yGpz`w1|C0B~rOIojZ`s~QXdOM+1T5T3i
z^Ylo7%W<0vOZS?Pe0}zVO)MigfzhBdDCiB}u1<h@wdERV3c$QRnC)(N4|hb@HkSgK
z_~L(Ka|3Bh=AY39g*JUy3m3w!KgD9Gs21ZEQ2nk%9NME-jk!K6jK;jwDKXUhLS3#x
z>vAToEm=Lof#lS%W4Gma+1~WWbLqM-$aSBfc8s;;Spi}zNj`QH(K}I5wwzI^sjo*G
zOUxMqHlFSRX8zHK^ec6zu%mOp*(*RN>~EA-#3#v+MmYjPcO+$N%=S+D@&_l$FIqit
zZj=8p{mBMNnhWxyVv$yv8=jt$smB$KOxtzIUeC!XO1tTyEJfA!Eg$T1%SQdui>(lR
zR`Hz^qOkQXzwA;B|4TXm(=srSTSoWIH3q`rL_Ic5hQg<lb6Srp-d}Zkty!zsGAI^u
zr|6j^b^SOQMR$!yb*Nm^9@KB*qT~011(j{OrO(-o7M>`quXLtA+4@G5F)EA|(91)S
zB~R0!CV=Z8?L0uG>)UP4whMa6H}$2Y3ZNAe*b`3=4AZbjvXxsXA^zNE5nEE4{#)tO
zG>{QOqQokE3f$U*g0|%miVBaX-tf2hwI{PRU10aJBLSC@hdsSukHz1A(em*(pdwT}
zu){;Yh}WBtJTNR?h3qm_xA{Fv(fg@dfNQij11bW0_kShb29%cihol>bP*Fp6E#B<u
zwDU|ST#$-nfcdux=k!Cy1tc-5P$us(s3|^2PS$LGm-GX0Czr0jrL)kr;|FV6lt!n#
z@+Z{&Yf0F#W8_)g?<XmOPum$K4#P?YTGk`MaIdej4tR}O_3(O~C34@blkTU;O>^fO
z3bMx@_YO^GO4b*t;Vy7Po|oUq+}Q5Xp-c2@Y76L@{MQo#C~nuLpjj_rE9!?qaRCG>
zU)b^qR=Sm)!UF(f0st((lJe)QXXV*n`}rZA?jkgZ9|{0==D<pwUqiZn%iezX#|uSK
zV%6_Mrr&;A?^~!;F2AvUqSG<%DE*x!yMfRlv*>Q#IiU;z%?^Tj+@{Rd<)-z{lG1mA
zFYaq($qqJ-urk|jxIrofbYW`@ifuBnGptKE${PPA!a@Jc&OW0?v83zx_{|JQ1xlI=
zF*L0ww9|L4U30``<45B6t=EI)^PGvFWrrqK*}6_M1-bBg#KQh~ct+W$g+|uIjkK8$
zTk?KxW>PT!UlXfiPyE5i%;y_dzQ^@k+|@<J+m=Q{EbK+D=tT<wP6$l{KOl$nq5=Ps
zNlm^W$1^}HJ0ne-_5_(u;kx0-(GB>McyjF>(TLWONE;*D7CO=fHOM;yoBbGjY4`Yx
zl83K+eQs;KL#i)*z1Si5GxCtu03XTX+L|??^3W24$Z%!Pu%%Vy!WuZEAKm8fWg8kh
zwcAY}I!gS}Gqp%@GiJj)p_=4S`N*v8pV}A`cyL`%ZjrRia+wO<gjJu3U%5HIgl1e$
z9xoFWx@*q<BWw9%)OO(4V)-O^fG)4Hvj749>+`05tHGe0Q;ExIL^}07-+<w<eHLY-
z>yzBl#fN0mWAWKs>uK@XAI|jeA_tJ}=wmKHA22DOixjJ;S}V$^rrq*oyCL`Edma|h
z4+Ab~*U#K-AIEL+Sk6U68r(&48iXBP$Gjl$Dey}_^cqxrOI`+@*2VeM#PnNL0?sK;
z9k@p5vqt7GwgN6g8T;G!h?g?jGaCbRe!F@R-*1`<97r&~16Gj#ifwIuE#b5F@x9m1
z<Ck`|MnZNnQDXhn5ObZ6c@&C$?Ou*dc{pigS|J2;Q9`caXhX#;Dsd-;=9=JOS_u(;
zy^yrC`O;%K^HU&<Pa5}aBJ>LiE?h~CwHI+dRA#-1h@@-C+2Xv|NcFS91E!++>m$Ze
zwjh!2{jfJ|mj5H`lAGsw;I>dc#PFw2uSkGdpzXE{fpI`BedZ0la6`6BPl6^%lN8Wp
zqJ3qD)R+{~tn0WAzO`?EGZG>$S8~pY*XaRq@^QYqungT4Nz5Uk4|O2#49gWpKK$tM
zePaMid(j2Npq;*8{2YUyf#`q(9CGWIU_j7B;(fM+PWqveKxf4@he{W_TYX6K4MTpr
zty3~Vly}Gxm---utMFGvN$*nER|krAfSZ~-BZB6E<dUZE0#6|}a}hW=mQUhL`~`0j
z$*8?3#zlE6XG^l&O%{^YN-<6J0oUt=I-i50o<;jHD=%PkQG^1+$Gm_1=ag4yWup6z
z6tE?j1;&*Z5tc{*o3GFATZkkNdD`6&b|HTir@^u;SQMJ7QHRWf8%Y;huS1-Y+!1K|
z)JTy?DmjKY$?n7F(W<<5`(|d!N5+)CJPsbt46#VWW*($phT!yYP{~ihAERuCT_=yy
z-oW7d*Suu{^^{6ypWA#nuHBM}eu(uWgPw!K=C7d!xOaI}VDjgMZ?_!d?IQ}wbg#Y4
zWiPkgCQJYqY&;ocA$!@Ay-HgWkR*OaBvrGb`KWaCyJ(Eb8N=ZHQAusL35HK^c-#|x
ziRJGBh#wMfeMzRU-a5)3$4sr&K69q+5VPCpdedOH{T)E^KIqi=)BE~A)!D!elD{_Z
z*SvIh5zkK#lR&_biPu>-&D8t*wX7by+}Dbz!=6zm5_@pR%~1F|FUgK;8pGrU^2!w_
zJUkC%I`q{T%TPs#_c8>Zc5wTb8!#uP7e<#!{lofqDz)V`*~Y@MCq`Q*rPil)N>odi
zS;m9ern5I3t){)QF!+#_r9^n|6Qvg4oTm3e^O~qNBDUq3+`DKX7D2x+PW!lMOz~!E
z*oEq0b1L##((Jn>!XOJPyKDXlO623`+t?jM8LT04zwqZ-laBItDg9$x<Y*GykDV3l
zn#nJ(6pYFVGcKa;J+nV^sNSk1v@dnc%BQuwzxn<6TD&6uVwUggaWF6?=H+Gio$3F;
zX4&%&4@{s4GD6NjuG~!4!Uasq`{3sc_;M#-y+2%^9bShQNmh@;bdmxPz%)V;sc)D-
zvcVDbSM&yL>))}Vj11xwdzpiNWF<;k1ta>`%}Zs)vi+{AEdh6!A}z&4cc94HjFQoE
zU5_y1dg0WwYg9S*Rkn$prLpabmHY((p~Ysz1<{R$^qd)C&wzf#4E9`F0*?OaipW?m
z2gm)3#Q80*csrc1q%X1#l9%<sKIy@wh+0*9OAV7<r{2fC?M<J*T0Kgw)#n8=VdY&V
z^}%sc4scO2DmJ+&a5LDPJ6XvUrRP`!DF3dfu!YatA@&xLwP=2u`NbRdxt*3}%mknw
zqAm^ui{wArgaFgyyEIV5e+?KaR*$WvfYkU*@JDCS7E2oTfbIS(|8<qKZ6Ro?I<kkl
z|K?aG9a^AraBixICqkF5WvD=VI!p`$3a+l&Dug39#P?MW5FOQx*ur+VoUirAxEC`R
zv8L{})QJ^(IqL5^i$#3qw<d&M?Nlw}%xfR5w2)q9kH@F!DNOP?AALWG$?M%2!5$T-
zZI>@+^|4d`R4nj1cq&z=EX!pJ%oA)Nd=+9Y>%cFO(004M>^4G=CM!zV$2b*q5cT}(
zEDVSK%(?3B3{;DvFT0hj0Niz3=5lHId7*&>#Rqm{(w5*;=!Lrc3Yz7bf?-Q}S9FH1
z_6{gMvr@1x9JJYP65T@EtGaUHtNwdp+WwswD3U2a`!YH^K2)$k`fOFA6MR1ZP(Lhx
z7Igh&7$0+}y-c_0NGP$y?-Sa~Je2OoNKd;6mSOL#`5mvDnbWNNT@)D+H76O))ZL%D
zzy0w3)0t9O=IPYth{Hj>S&~&*!NR=<Q21WR8uIuB7t(v{#18izJ~*JX-du9fJ?G=9
zR1LS_5z`&~BBbh$p<aDw@UuAZ2O;&hkGv3gtOhTn;Q#{6i_?L!L*3V=ZRzNSJ(oOP
zAtr)f{cn{5woXn9f>zK*JSOfL9Y5Gv%#}t}Y`)ODzNWQ_7(y098=sss97+WPhtzq(
zDbAlQk%GEnna_DiCf-@Cve7H0_XtIw=;YVVP5YR<e|D?C8NvIiYVKbiQucAMc>o~C
zXh6<|BGeWDJ_Tk{`zJ|t6-1U03>9@XPjZ)&l-wkXJHescq0#pcu#o;oPY}k?dW=|v
zQNSi{ABn_SO7IfL)1?b%u2<V_wH5#d^GfN)5Zgk;Ue}969%PR`PM)qGuGw3S44pPh
z8rcN36>l`R569_e8#i@!7*rb0W@=Jl<zx*KMf-AmxhHw<e?-RoNjodUwj7~(zd*WQ
zMqL%E6N>El#fkSwW|}$noixGx>ae+NS~{8TNDVvc0-n)}1UpR~@t67?_EiES_)kVs
z+y#ZlE=-Y1!+lRhYB5vGw9%6*D&rCoR+n0RnAq6fY&Cf0t5%YMyrA!*zdotD*mZn+
z%+vGoO_q=*cgeT&mHY}KySi_rx9Mg1>(u|G<>0@?CzJ>5A#Zu}fITvwKk)z)rL3;w
zS&$*NCRl#PZiYV0A*#eDl%UogjWgu8;<chm!{<d8>p)K>`;;M9s8!Sr);uD+d1jQ0
zxynwIm6Z^{Yd~{I1?v~V=#5OBc$&iiu>tVd;B2D;*j!xi?1vJR0Y)pEcJIFvQ(L3s
zl4Q(`Tc=YGvvspAM{7Qq^OrYTm(}+u;|fIhwyED<*slm^Y?4OlIw55vE1*Nf#%cU{
ztE1_=JR@C-rhxlUnMV9uM)2k8T8DqFeoWcy@7j|e57L9#mXCa@-hpGXR6lK0$nEWf
zDX$Q6GndHv_k$kGP792*fc7m#rxFRBoh_-cx{y=n-~31IK*Wha{|c>)cYjN>k>XFz
zjS-vy+9IR$DHE?h7(<y5UdqJy!zCeip8WAv^u=kfUFxGiJqS4NNC!iaSlSU(p!;-e
zqCdA68jp+=$+`R;drX?qr@tNbQkT+Rv27dJ-%-BktJgRNKlfBbiA^XdafVC<XHu_;
z86ZkI#!Y^GroF9`msMhP*N`L$1pS#io<uD7eMA-gq7$f}v%0sYRKjvi%DJiSGe-4p
z!;eqh_c$QFH}Z<@AHEh|N<p`z5-9U{cDF3gdg$lXtx|)gh`=nh2{=p}@-HMPkBwLF
ztD70`h{Q0K_8e+jH{TQASnhV3zA)UKES{>fWgPfqJF~HWR3w?ZjfjjD9=j<J>4Jen
z(12Fh`oq8Plf&^h##BKMGrf|R0Zrpm<0qQ`VwC(>ixHsGHDdTO+W}GH^fwhU3&yDm
zp-yz;3lSm|l#LL5iOcH@oT2sAR(venp5J|9mKx6rBvg*_(Bif+kvWA)u%Ia?qeqIN
z^>fxvLe@?>OUKSpf^Zk08tNC7A<}6ryYt(9vLSBj$bZq`>k`dO>K&SnPl#~GNaao{
z2R#Mwbd+{NnkU|<U2fg$)i4^G9eF-i(PMbmoaN_%eW`w#m+oU)5$u{fx)qoyO57`T
zUIGm-DzP1i^jqfXHw}mursN^CS8mL)^IOYn?*k3uDQ1YkQ#B>;y$qcr;ck@993ffo
z3Imv^sW9~r|80GwxZOk=`tq*Oq=$o8Y5P$aBag6<e%)7k;AzMRIQ-0GUQ??y14DD<
zVA@yjv=J?EO>_4_C2o{aIR0Eh(~EP!U|9Zfn?-Q-sJBG1{3q6qF2X~ta75uMM*N{D
z4zQ&KMA5V-WI-EI(;qwfq792!SX+ZfY2GQgE^fgS@3Uu3-dDT9RQN`MNmBc5QQz`_
z+idxLL!8mq$8fQC*5p}G^EWUiNzjm&PMnud6k6Ah4aRA$KN^a>zrD%OEBpAyF0BLL
z(4qOq;g!Ghd2Kb&cNXnQaijW+y1Q9iuU0O)4Ms5r36c6r=R8;N3;2|-*{IN$*1h7c
zbTz>!Lfg};?p!_G&er;}nAikWZH7mZCR+vc^SPAy-<v0VGUM$M>c>{U%Z~(sVB$34
zif4%W!otuyBAdkuf}`bu8VkH5fmLA>=H8*9Zs7H`vajoX{LLD`eRruMaHN64#Q>mQ
z<ja{exz4`Sy&H^eq@;)$ipMIK)jwUW?RXqlXv=*m1XDJ8+wbvD-BIQFUw@=0-QOAC
z^IA(k+BDTzi|w7dhWGdKr)tj#TTErx;TdWJR-Pq|b}rt_b>@nAsWdb~&?2Q&PKxEa
zjobd_PO?-?i8uJpyrNfOh%xT0?$cFd-O`hii%P0=q4VZlVYwm@I)P8n<`O)9b(a|7
z`;nKwr!=g|Dy%+~-no(yP!1B5pdz6(@ckl<aQM=d2Tiq033-!h_Vh9#wRNFQo>LTw
zO41>-`~4_52p0^``A$sjY$}fqaEW{3AncL*+sPlp2l;_FdZ_GoyfbOHj&rLC7!}i@
zDS{3ULCQ%wR<SSf9Jt@6JDft?!h$txiBW<0_q$`pd+&@VRtjdoJBpkb91A+|7uCl7
z`lZ{pJI;dPx=pE*{Pss10LDrE?;HR;eAU|gX!xm0<UX3;Mz$0GT)&P(FUnSsL#k35
zA<0h*zs)h)Xf25D^?KHha9Y)=j;dWuH(4sJYpb$jX)Wf2&KM(0zjC9$m>b8AHg<E_
z$AJXDG`oXNzp`~1OlHsJT@O+1F@27iK`n~~jL+`fAu<;p47LjFuI{s?FQJlXA#Ms3
zkN}H74Co`I1y8&ooT7HhdW+>V`eyi<;oHw7-9RQVG`X`!7{!|3ie{nHY&sb8s$Fqh
zYuZZp3d9}}_Ym!X1}&_!cM(}OvmM;T!1a>vCg0244LCQi!p?Wg91ivP$ny_nh4E#h
zt?%GY<bvO@KoQcmp(D{gFE8%}ziP|{sNMH{#<y%JK0_b>G%qu&-=w7TrM+L%D$DHE
z{M^{o_-NL@-2I3#6wq`e8_MF1WTG4Jtd#iVa=6fVY@C6*78geO<^}40Y~D4_a1~^z
zs?8Sfj<e**wJUqpD@kx@BHux5xvoLU_6nPJQ|x`4tuau3BZqHIzSePwms~Jb1v-g*
z5<u<0+tc*ysF%8UZ$Ur>9>|zw_Cp_x^o9m}GMbubQB6_zmaV~8(^&2^jJFIzW4a+G
z&b%%7J<0nlET7vQv-ap-ZB{c9W=MYv@21QMInuGQ%ka3{m>mYIlV7@>r(QEyHecZY
zl73H4PR<&5J6cVxV=+Cg2zaLS1uw6WHRr{}tW+i*@T_S|IECO65w_0pd<eQch3f6G
zR;mq>hX#z#{4)jfJ=MX~`YxY+Be+w`uBI4Z7)Af|cXa+!7zTtt<)g@l-lm{Drk-v{
z-`DY2LfZbmOONM5y(pVpgPQi=q(n*^?dn}6k|LENFdlE&f>NdJQVS1g2akll!g@S~
zzJk<E8j_KNhYPbXM*Pg<mu~&L?dvd(ZnaTI*4aayjbo^<fmW1*`Yp%f2cl789QRpl
z|Hpme*|p>(x@*Z@O@Te`)ASu-%`fhtb1K6I&({d6!mO!#1?|gsRYxcr->!H4K4v%K
zM8u|b2uL%I%L*6*Mbzmac8BoXX8gwaxBeXS0tA<h$gb?kcN+qt-+we#5IwD*4+pzk
z{H(72HmDgvLP^;TJi~3hKT}20U98tg3Ou|kZfRMvb1kd?tONzrk>&KIuZrMD!0|<N
zx5}6OH_qWi`gOq-UuslKBu#)@1>al#V|)G!Vgu>^Fn5IG8Zo?Wfb1KJ8$W)frcSjO
zmF>X)BGU<Nn9$46ZnN%0%eat#gGwl2D5CajaDVj>X=?umhk+v<CtA|wYlW9GC{&JE
zNTv?)OD_AUTw8C3T#AtvWbM-6+(6S7J=^K;I7kf`(`6Z!HFW=R|7~8c#vY=`7|VfY
zS54T(r3w>M1ja<wqw{5ERM6o}Xr|9gG>Im3V|4A!tv1?q#$Vip4qdq5m0kj|vn0Wh
zM`CRzRt@;=O*$Qgr&pUJZYztcpk`tcER+ZBQ}1x-Zy&yhyLowI13d4WEMSizoW`+H
z+twyV&S#APyw<`q$a~P=Ing41l&G1dqg_=+X2s_8)OaJ^cgSsdg)rGd|7^M<vn=0O
z^^oSFeJs$hH`(LO!;1?DOUmMIjGo4T)0Wj~%K0;=2$`&aMOjy;2mG5TY+6_e9c43p
zOk(`BtnGALKSmp(TQ}$g%#s8+@lFOi+b5{9U`&u(NK+4g*$Y5D)*X!|_JS7jVZCxN
zoFza0yZ>u@S=pzxD?0v%)f6qhi~e>;E?vVmXSQ3-N12ra35xu2F2C;1MU-H0xf`@Q
z%TxRvMw2JQCR%;qE~t*FBhzr)kh;?FYG3DJef84#aIluVmR$APLPvWxqw)u`RClq7
znbJLp0EiKIoImwFBLoho-~8&Dd0J%y-A^O!PO|zUv!zG$1GonHVXh=4C2ie{ccG=L
zz_Y!;b*mx#UFKDWmk0Ax4Ng2*DB=S)QBn<(wc!C=#&T}c*HstVd}?q4j5nD!X{T^M
zdDF&;q?0Q9HOtTDW&i9tfOX)@KClkky!56gEpmV)P-Xeu-`Q1wQKYK@I90Y6N4f$V
zoT3qELzyN&=pRHuW&My3&L^xPTBxYB_p*~|>eBh!ch$P;MW1T;aWRI(OVeK4>ky`5
zir0GSHaQ?7(}|*a#Ye4QmHu#9Mt>KHz0m7EXMTs}UwSLdcADM3AtHidac}}`#Mw7W
z8Qd0h>9!dQ7*7d*cB9!CA@7zUorm`#!6BI-A}Ln<0xK^3NNedk`v%Av9dIj^jo+5p
zt^_J>B=X$>te$H*!s9$vJK!G0ZS$VBj!bU}xWMU`$Gv-zUZeA1DewTcFK{iyToXmT
zxHg&>a8>KxbOq`+mlOU2PY05j4)G(Bw;tjx&$^A_W+N3nT!Ra-^L7U`?DlrKu5T#p
zU%jeQ+x}al7*Y7AhZ7JA2?%t}Qfw;Ur`Vnql|JtVW{zOv<E}0?J^g}*B3+$by_93g
zgN@@y^eSO3Q7eV18{i-k7MG#RPE0Kt*yuUaJDYwNqldwDv6O|F$^+@oMQw1zg11B?
z@O~*liS){KUl!9*VU4xcy|xkc_VxVO(l1_kJT~jH6ti+Tp4>a05FxGjZ!dr&DnK3d
ziR<T+<FBLR^iL5c8(@O6Y0a;4DJe_8$iX|bX4)i+5O}%YLD9ym+Rk?I>96d&HFPLA
z-ZV@~_Awz%y|qTiiA{Z-I)W~G2T5r2FzhK+-?EQiyT`c=daB6?S-GxQwK%#hL0v5w
z+a&FnKKv{T6DDGb>Gh=${AK{aA7|3W#cvx>1ZsB#W%u>zCLUVHf_PIy134-VNW#nv
z)`SBAv)as_nO{9Q=73W6r%Z1iS*!2>4Mzi9N-2$=g}S|m=}id9fU%zcuP#gaTRq_f
zM1BO~RIvj^Y!a53fw39aD>b%ufEp9mO5D&SbRp<gHCG6TLa~S1H*<M}B4#v&3cy0(
z<vLfdJn(PHv*RtO`NfftdH%&PCb5YlXfHG%QEyHc1N%Z2<;7)jH;2H1XKc=){^ilj
zO7JZg-_0PP%p@k7cd-V-*V-$GEN>~~ituHV`TKW?R%aPl-lfqiN6d-euE_Aa&zBL_
zFks>rIUIA7x$-GH;$0G^y^bG=Q4S36fogL}uu9+{V_l7(UmCJ_5t3QLk9~+Cu-U9b
zE9&?EkF)m-YJ%&!KtoY_6O<0pMWl%IE+8PNpduhuM0zLmu2iK-Q55M2igb|{s#K+g
zB25w?AcUHP8ansH=Xu}n{c&gR%;kqOnsJ8N+2@?K*Is+CYCD>}jp-QRt1RD~$bTCw
z?&VG7QU=?BE<!WG3L^_YWE2hilH2>^>FnKQN#*cxp53vZR&Vf<m_F6>ao^c})_;zo
zJ)1v?FFG$THvp{H_^)ioLC~B#m7tp^6dAT$B~y_DB3~*4Zb^SFU3q*y<5C3wTetM5
zF|SOki__iohwh*n=KX&O{CTb9-C_`x4lcx!HS)V3cTE^f_2~0#CvSQD^kumJRY~yp
z^m+JF$_CN(6P?h9ar|Ux`d7K;FIX?I^@>@$|9qr0R?P~i=){Aq?mnZ+^XzoWi9cJQ
z^_#z9P+SekTbY|z%R}^ZQ3r32Y12#v?KT9-zO{U_KRAu$;O_P8itlLOK0mv}aCm(8
z%<{u*M8bjoeE*QwajgwiAfSB)#Jp$1DejU0@^0w76jM$|$t!rr)g~0Z#pR}SdB_2K
zu)@Q1W6#)SP2(oTTd^Lor(65ck?q^Xn}Y%uvzaelns0kf0{peIx1E8L_#AK&UtWvj
z6a>p!z-liW^k7z{$<iK{du+V#bGPlchP7d5$8i3X)){C)BMz}FreyBVas-99@gL{e
zoU$scGgF+J{oNvcNvUAw9D&(A{!$_w27#pC{TPt!T5Ub?n+?%eL))kK>WR!|MUI}{
zSI!^FM1eRz+jf?!;2`f`pVzC-|G_|cE-b4gk(WK%Y{-<*roQmq%_Z+n%SAN*XaJXV
z(w558NOYc4ROC=7TCLLy_iAyv5NBdr*CYWUy3CRpHzdNksz6s$t4AM=i?fp?tyF0w
z^Gk0g_G^p(klK|j`(C2DfV$9ZCMxqwGfV3jb*t?Aa!hAw&<6a8#8irkmBLASy=OIz
zvPQu>?;vZL_fP6fc_N8W;`u9Qf2<15^pz!->fX>NKkOx=zvEfcis1!=Q6)x`-5$B?
zS6{i_L-<~5TeLcKciRGLA0M#}J+PpfiO6u84E(u^FWvHa6s+H;U;J6!yG?|36DvCl
zq1beXdYmM2huiPi>EdhX!5;Q?WFs>T4b2ZYJZIEdKI<NbN-zu9X$E%AUGFI~sUoHW
z3div>GqM8D)6>)YPgc7mJ(;+Yn8j?QFQ?4z&A)OM$Y!5<X`ag1ca4Nzy}dBeE&gsd
zrq+to(!q7@r1@WfI>0}b<4-8Jd3`?Toz6mz3uk<WMvT%@6I`W5Dt#ZbraM}t%%5ax
zxz2EGT6b=;1mzIQpjIcc<=>nOUZotCpd2cE|6^o>m+9UskFxKYmNop1<i=mFSzJ7E
zjzpuJg`G15l<1o6&Uan!H2-R$b{Qhfk=Zv;lV?UnoAv^^ao#a7z>i!lrQKrXDeSFh
z>qXVZ2C7fd#+Q}(<7;K}Hr^+FM|0gC&2+Mz=DM{z)2erP{Jc+9`)HIqE^x-_dcl`(
zEF~g+m9>Ga<A%mh?)sd&`ihbXIcNH9oZLA0<EB>p`+G?ZzZ$y_EN{<6wMhHtJ2Q4S
z{cO#9QY9>*KleOkwEo7KWF+|y?8WDYUGZW1JN9IC^Rg#F3oR`{`wC*m`)aTJ^2B*a
z!RF^GdpOtRMzOes3L|ha0eem}<vfXjq0RN4#l=MwI7cQ8UW=LIjC7!VHdcJXQoDZs
zg1=4Fr8sL!cd<}PSLRc8iwKPsVFT_QaGM{*|K~f1R2|?4vsi@dT$N<58lX45hqm{L
zY9~tDwo-VT_44GURf%96-0&vs!A`7Z2h_H}@z=<P8e0dnD@5eNp$UMvLD?nnF<SVi
zbZEN!9nNeKjetk~T*2o$pd#(i2y#puSEddvATM1ZyvLNZ0UZ0oWypFt*tM;TcVF=z
zTo2y$a|qiD<DJuU?^)c_u4sGW%O7$&b%r3#36jHX(l*jKf9ci8JA^IvRa)B$xLnfn
z&)ItS@pI4ZbE|o8$mutmB~RKmWKmNyKK`&EKEWHgd=^GdtX&#~LY2~31!^5P{T<;}
zik$i_m9DpB)j^9@F{pLrRHp-2@#oJVaAXFi8OJi@o3MawL9oj2y5xl;8fm*~Rz*Kd
zCrEO1&4Ln_Wh-lXh@TDO>&4>JD}yX78jd|^YrpK9=11Dsl(-#0K#Tqx(0_&s0Iz#?
z6Jj;dNNcJPNpE6d`2r-hK}OvUenjBOUYHhtJ-$H;eXz6q17g8?Tjc0whsCs~D6*X6
z0&8~3VANAf2Fn2s1JMW-8-Fg=&XRWTjlu2DIHmfR4S`o}{l)St*qi*uLeX0(8yB9u
z#tQp44B3(pOX$#l$0^gB4|1lE{=BR%TXB5n$B}BxEaY<DL~0xsSx>bw_$%F)3?e+&
z(bknSXS6-5PPzXeyTS|p$)IY1?{>~C7$>L?`E&NsJZ9LT?QrqUXREpkyUxaWp#!>U
z7w?LPaVi>4U<{LF4UBz?dX{x_cFb@+7#jatd*veHqJ1|z3Lx>A&l^dv5=I;K-`iQy
z9_Bg39{DY-eCPDEa{hWoEOxqnYN$6(SeQT498?v0awy+A4!j{j=!a)!R2J&NoW2cq
zrrAR-CG26pIXeeOXR-~mb;TJqP|Ire-aItq?uDt)eOP-MNSUchCnZyJeE;8C#P0tp
zURBaLdyva<Im1udy1&>?npSfJJcc&9h=@vUGv~q)A=#S#<tDHY%l7RbM-08M+J(Bn
z?T!&M1`jQoW;W<4cz;FDeaCTpm*61kpY##C9WJ5sJrTcBX+;@&PZ4=;f3K!_dG{lF
zK$@tPtl7Th<)F=3$__{SllEFd3V#z+1{FhjPPOuHJ*qAB=Z9}=M5;jc-qEs=YZ^P=
zdqCEFBYGueYwCUDNKccD(#)e6z7XfR)CXpvf!B+Fu72mU6}PErR{X-KjL75)9RQOS
zDn7f)6y`VEqqxr~z-;1(***vGa+`$ti1=a<6xCBopC+~fo8>&`Ne8o)saj{bq2|CC
zf|g4u7WlczmkC|`UmQpZfz%$e{X*cSpS^Lr9S~Z5B-jgUg~T0c^+E?y6F^Te{a-1Y
zgWx}m9-$aM4}mXRkcnE_r84Y_q}%lMUY!(uU)?EAw0X8|Ed~HglBPJ4wx1(cqyu^-
z!tRlYDE9<qv%v1i#w+NrPcLyk5!>X#{w*9{B@@0e3gG}87AO#k6xg=;3-YB2b&D@o
zmC~)IR|dU=fBDevrfhtFZLY34(eRG8cd>liz=PKDaE~V(fUb8n=RdBXE0WUZ6esZ3
zlOLkI$^EmIl}^tAjkRw(x_m!1OzUTnAAiV3`NA2Uh0v+!$~NO-<#c6<n<(b@SE3-9
zik`12?JFeLNp?FscBWt>WXiP1<xs{%x^nf)f$aj$HhZp0=7*ABTu)xvgE1ubM!NZ~
zWLP~qYgr*tul0CT%18lkRBrzA<Ot8Fsv0&};d8KM+q6GVuzR@P12z*P0?=7t9dm@v
zld0na{@WLTsc3A0c2fJ|$jpoO`>=~8n3D@G=bRt5WczGgO!GYx>3?V;443Zt%J#u@
zq)~{BKt$iq5bY1MB_NqhLZ9ej+dR@E)tfI;&2?9D-O{*YPRVA#I=tLp47RPbH3jBZ
z^W@5xtBquSM?b{HE`rAZei2R9*mUcPF<n^cx{~qkPi;#fJ9NOh?er&&Jsh+;2K~Jp
z8o@*hUu+(Hga5Ruz)T;l_8B5C7h@fWQIi;>$x%Exib|#oJ~)<PDGkse1L`?W@l%rX
zmM`6{F9I!sE4G!?TF2|L*UzNUS(CW%*;K@VV`Y95X;5uxPxb)2hxP{BWZ8Gsq(aS(
z9l6Gli`t;>-@l8#l*#(#-lo_kI-*<^{CTdcA*{BS0?sx(gbv@q6XE6|_QW@I<?tsK
z?=nnqJVKDms;b;acx+Ga8xi!eDKJiu3*MIit~oY|4C+t%-il5(2g#O>|1nN}=L{D6
z5k5RTI<n`czFc<*F`79!XX5qcK}&7OylvV}@I^ta8c6czGXR}?{maB=(EKBhAe7#0
zZKBO<xm|^@dio&Q@>}=s)y@>YF1I^EYpm+k^-#h;g(c7qX`ljr*=qVf^SIMrIQ@oX
zF(p!|EY=OY_TE8%N*Qea1QxV!FAr`H?GLRn7HpdXD^u{N+8wMl7i^gt6zZ{B69LPX
z`FMpGC1!f+!H9~=;HNkw$<{t2a|MdzY|E9YG=Qaqt%W>7Sb16%jK|a;9Dlk#BC}l!
zlg5Y80Hsm-j*lDXDfQuCnE1-}=zxpl)9FJtj!DzFXyon{5o%wuPds<%!dh>Ut;l9Y
zfx_~VIfq4kpWUYqL>GJ)t-2!wgzi7deixb$6^Zpj#N4ncS;)5k)=Xg>c7}$UI0n8O
zuv`CKL$$lR3s&bt14Y4pR2$&u44frX_PEYL!vBW`G1b2cmQGp*Z{7mi%;izgzTV!-
z-AC9ihwo;n8<#$s>+MZKudE&j#-CQDp>+$=0n_IDAI`(&|BCm=kf#+dZ+|p+z0o$4
z;9Qme40T$Wu{4S}zkEX!sd7>hh=mT|%voRbrN47s*^5P|%;J^4YFJdwHGQd8`Wj@8
z3@E4W0pH8A&ns~yZI6}xX8^2B1ni`2@EU&PzYFJU9r`k-WVo?|cpWa3nB8sPvN^h9
zbDr^)^X!Yoqceu~ciAUt$~LmYr~OtoO=~8<u7e4%U93DAPYM;uiHhuCsI&6NaPcuo
z^qmvfqk4BgWz1B~MS*kQL(ulrqYKm{Hr^ktSjD?4+$R<eH9a#hPf#~rLG~`0cZS^h
zG?yN~f8^|*boNX*yn1$uIw$DaUX_ArYpC)b1_|t}uYa0I=BGfzb9$<5dgeAeEysY(
zBN-^+J2Ir5m%e2i0;`Wq<)BMK_cFsL*6uEw1M0Im2>*1UJ0TAZQz`*P{AJ?kU$gb^
z6nD&+_Rb*DZO?k4g*R<LZ|1{)N>G`9Zt@|}n_-500ARb__Qr=QXA7Fux5m+LLyGQP
z!cMduV?tD>M>g^x7CuWH*N|KaMZ?dz*z#8wjm(X%+)Hgl@_{QmX@LU%i91FC9?{nw
zbK`KXix;n$&aV@_j5Al$#QKzzqiDV_qN0u)5*RZ3qEw+<94ZHIxIbG76r8i&#cGUM
zghhCJ(paibk8*eYQFC5ysG&Q91c<PwWN&wma(^FMv??lSk{60>Gm^hE+kEj>fcz*~
z3dQKcvW}{(`O8^vH?5v$po<t6)itM)I2?7;{T>2MZE->aYIzN)$s?!#QtJIDy~LcH
zoWP%;dv5MY|MmZ4)SpNSG;FjhIk>xP1EW`9PRFPKDzMy^7OqC$jTZvl<8tW3w>C|4
zyN-{`3UbeSesBka84aL5WC|wq@fiaz{k5NAqC1sJ19d$Kr_*OF!~hIue8aIswk^FG
zn{2SVSh^H-)Zvuj4rR&hX~qYnpaN3#>V#^s0sFkXlLwrz2Y)!cLeyE)L@<V|i7~YO
z8va}jv+|L46Aeuh4LtAG$oOwF)N9n32klVNaHv2T!cN?06OOMzAk<6Ou1)WHf&qc>
zrOjt@LGZcmhuqPBwx9Gh-cvtmh|PiDh<*zo^zE%rWwi&qk!^c4(*7QBUqsl1ubj*G
zkb;7C@3PAwZxg+{E>K+vXN>6EoE{Wi_UqxkYEKE!Az(Yz+R!77X;*-GPte}_O;=aZ
zPL5Vbx8Pt7?L?06HO>=u9Cd-aPV3WkbimvP3N8UHEiGI-m3VG*voZ<_>=Hfa+K9k@
zUMDVYcJ>Y`@uqNgSvLse%igJIZ*3EM`)AH?J$mYpF6CJ*%#Q{76tNP=;Cc|*wLtTC
z1ZMdP!++ED@DjufC;%?KePk<8@7%%mR~r#^DRb&{N`gBmr-vH=j%@>fj>kz_YVVdu
zHW*S%6#Eu)&9XHviaGz{C7XM-)@Ly%3|>38&H6n>W6>#<QA_lLeQBz5m@OJ%)l}a7
z{vB+On0fcv{&AfIV}Uf?SkM`5SB?97PxE8`edPrS(^R_oa^+JoFwyg-C~zm$wtD_~
zV=XGdZ#IfXq@<n9&^nNqbA|0@pxOnw5vvGQZ`XDl(-~fKJPZ{>xVv}6G`gNhJlS3v
z`1@8Ftz}yFVet#UiXY1PtTF|+On!H@w&tPbkP8P}sR?Ke)OG|cXKHFXhZou_%0M8@
z*JoR~fe(8|PlyWly=<kIqo4G(2SnrTO6B(Tul)8PZ-4#!1IMkli23XaUi)=<HOh}t
z#xJ-4#T*c<BCbP_#imjJGX=YBpm9<Su`C4HD#3)dvzhJo`FyQ6v(QiYK9oJzSsa;d
z?$4zl4ODMoD|`Fx&_^-#`Abvn+a4TZIr-#2r8}SrgFBjv@WTC$?IE-}sQtucwk^@U
zxyny%{DqI_i6Qr_VA1$6j4C}H)JXU(_puODX{bc`Ce*ffDh@i^YSW@oByVi|FhLg4
zOopFrpz-}6U6r`Qn(mXsbz@O>-eZ<cY04soViplyO=Z!B{SLr%1k+IAg7HIOgh~ig
zetteE96+()`R4}%umJDku=yX6SHR1-bIZVc+JB`m9W3YvXZx8XDp3*B2G~7oDK_aI
zbFk2rkjR~#o$*lCe%ex}eO^kVRyO+LW~1nEMga?}NSkApr)TZ~rmjvdPL5e2ECfWB
z-15(Zl?&MBBqINU8K2iJ{epaZuI6zGkNTE^e;S#tU!WPXAw}n*ev&RfxDuaGcN9GH
z){QP|_f@@>bWCi0=6rrHOvC4@6}N`OBrTUd6x}eMvXSTJ#Z&y&#dyPqEBL-)P*#iz
z^YHhE;A1;u?it)qxOS+F-LrwR?%u}M*vv1D7Zk)T#LiX|Sg=Z8`fAV-9c~>OL4I=y
ze%S9Bi+x2onKgVN(U&d2d>&~%3207M6Tx>}!l&J{M}r=J25qNvS=wih3A3(XS^Q*c
zn5t2Qr80Vg;I$0yLbur#PG~$mF>rF7thT3H-}{9>$QA+SZ{QZy^7Hcp_}ZfJ5}~{1
z>s!0D34EwP!?K{d`bJ*B-CA`}Q(XKbrW$J))?~j!Tk!2@yHXKuofxr`3GmkYS)RYQ
z<~ImVsF2XWB_yIOL<wlcKIYg)9n^nnp_TXjFjF{`FF{6h7~fZ?9fKY<zU{WM_ZhPt
z%f{CMeS{CVf=Hx>OS?V1$VN4`{bhSG?tEk8o2->B>=xIGmw$PSv4*Jv+y?9CMjnGE
z7oRG(3{^QThaPMTeO#eGeZ+lCEhvc8Nh|Z<bi$lae$|x`2zL95;B&3V6`Z{LG<XN;
zI%^PtZ(8C)Gz6UNOxPG|2NL(eL=yF0&+R<kd}b_~jWr{4S8F8kyPZNTx0^8b`uHL2
zt+nL)N}C>97Z5zbhfaNAa9}e!x4*d{7j~*d{CrYGHtoNHv8>U+2Pm%wkDcZF=1u+#
zDQS~ABwbxyavpP#t0E%ONsUN1LU$Z&hS%|T6VSVN5$qgd`znIb38a1R_=T#_!YX{g
zM}DzEiW>AmnBZNVgrlvw(*1W3nD7vtafG)HH_~Q=o#&|xvY@FQD}6E{-^DXLr_>!F
zj15sS3+GbNd-cO@!3t(Ef>DVvpfMIjishPqv9Pq`WFsozh^0z6c*MD+&iPTqO3??<
z6q`SA2>MdK%|R%UHMwTY+!ulATg$h|u?dOGP^lNtMMYYb9r4+=&2bT(w*}w0O29Ad
za!`_z&1cEX&fWQJwn4siQ2k-!7dC7NQdzDt<RNZN<b9&Ik8B{0I^O>)&fl2RlEWk-
zTp__KMUc$YbF&pYS`#hpJpN?1CFIA?pYKQ4fG!=_#>_7d7XU}D>pk)uv<ROGi^)ps
zj?D4YSHLiB8x3Co0S7MU6j{#IQy%Cnzo(-`cQe8!QurxAFxv>w%2(*rF5d*qSXHjh
zR9r5pmsxDMhFQC^aTr$V?^cxe_4Pwg`xbvX{u|QmCo5;pZ@^oW51Qy_&X6;Zr&6ty
zUpedRT4)6VphqO$rn*ZqYWnCIbRN#U%KK>NJwsoeh(h7>WeoJuhL<I^{4+Y^PaI5R
zH^uC`@^T;FkI9EB9cOwK`)=R>VoiLKo8665Vv3FPxblS|JI3<v?N^O!=B(LNM8O;A
zur|NYZR!VnuOHTsfpYQcwZyMX=#iy$#Ta9@U1XSryYm+jT=s<2+zispnm+om!icoG
zcbS{FW1vB6&+}Q|UkiVRD6fn^Ht`ZWcHjmX4l{2g=z~G?=h36FOsf)LQWHbRtz~6p
z^%ofduul-6UAxqmIgv&XA`p0AVDm_k1&~<L-4BF_w%d(bqCSD0<$w=nVPVnHF3td%
z+4d#qloKe!gyFUyl#)iu!y<l8rv_TLi36-Z^E#2R`z<zh>G#Nq@l|k%c6kH7cK~u~
zhE;Glb+No3)hJW?{O7xyeM=A6_}M_SaZsZpm14+#^2l78Yjv?N4@5@rzEWEI_j;!l
zUtyL*%3I;3<}iy#F}(Dk8QQTKT8}Vb;fB?2`P?5A5dXv#&QG29_?rTphrR|Kpr&)C
z8sx{tJ@I%p?rb}A*s1KTs9x<gy;>W^EkW#uQqK!QJdyOd;d!FA!e+V5rh)FlI}?`z
z^_bso6@0&z7o|>>7QJ{uYzo3Gm0~;fHS!`hapQ;Cv&S>v%=-GFXYZ<&(EY5AiFR6i
zdO7&DTh|8U;qtSrx4ZZ3TV~1FNG}U~B+toJ3JUTsPfATcob)sEFQ4s^`N}yHv5jL)
zB|qMiJN*+k>lJD%sO4~_G?@GiT_}a)`-7JaMVLuEwj=9<xX@09U&*VHr%mWhr2jWN
zz7eS${AHxA`wkAD+4<(Xx)QX3O&obI^oQb9pp|m$sOmx1?N)a?JHc8v<STH7)JDI3
zoGAe&<_QT20B!twhkj&e*oMUyR8~q9?{*f{)iHywUd|7biLRl#bPZUmYI}NCt!;uu
z{RGHiKX@njFxvRso5uT|v-Zi!imDjr#T~A;OyJt``*WS_MY-V3l@Qmn8<?kmzh^<B
zzr{4G101tj2FZ9}K_)O;+E1-i=__#c75XEL2__=IqlT}?2mHbXXAW;*cFCuu%^TrS
z3|t~a^&^fn+fpIxjn4M4F$VV_#3UXu^*phPt8Vsp*)}40G#m<tUY1mv&<L>i7vl+k
z9bOcL7iR9B_{o|rQgNc$4iygnpd8}A+>xWsOM%iD-jaPfe3BC(KG3{98kgNiBey+T
zCy@Jf#r702wU0BijGGvDi9C;DSyQP>#tbQr!0`iJH;l(o-uhmGly_8KrnfY+c7$-I
z`fBr#5(uA->A&U<#dyl|5rkF#;K7WJDZpYa4GbWFneXlG{W#8;1T40I+dwWTmw{VG
z_W07$Qhrg<dEgM|r_4ot{$Jy4;D*JYZw_B7^}o^UteWtxG`}9qsU9)E3)=WF^rD&Z
z@oA4f);UNL^N-Zxf8%-qLh-&!=i$VB%2Pz^lI1gf)b(PiM_q>#kt`%Ta(gO%G(&HO
zHw?HQh{VG14V$k)(q&eNRh|1?3oX6pb;M(BwN@Y6`NOYZ6j^u!S$|J1>=J#34|8!V
z>EIyrMkDR5Xf)8*>7fJUl<*Q?kv1M~&6LCyXOpui-3c20jG+;Oro$`~!y`wvJHhka
zdb3l}s2RPNA}$$^q59`e*Xd>=$Ml$ayu!TkmqVJ8G2xMEZ9lUQ{Fij4#dc<q?#Hl`
zUU84TDg2$^Crj`gIuN*k?InQ|OK?rAU8ZjXK`zKn&CX67_#kV8g!$m^qE=+>;n}x<
z=WJk5^SO4F96ELxm$vQ%b}$l(2^<8??ct%Ja0~{cnZ{NZFowM~HJ;Rwp3IJ~p>#VY
zt*!`THvKWmg>m-}w3>#`x5yK~+%W$W!uBgEl8q?~Q3y38w)JjOQKnQ5T@4^NZ4X`;
zrmOpv{W-r(!Hq2EPMUN__`*&YYM=;t7;-$otv0-*Y;E-sLc4Bym3|M}akJLb{N2sQ
z4NnRk<$a@wec&DC^B*n1Yt8y2^N`z_S?IvJ`m|(J!!Hdt{2;UrXTHLg$fsmHqXN-+
z-g<oKw~08tgf<qo{`T!!TKSp8C6`?l(f#o$drwRh9e>`J74&Y+ht1@=W?CrKR&&g9
zFI~36i1KlR+VqB(64X{y;XIY#+6sRnHR^|K$@M^?a?gqDKY#wb3G5e*N==e?f_(h^
z_~^+&i5Ako4gTeMMh4rTKY#d}i(bM!7tRwuhlp9VtOsn&cg5W|GmCpcjK>a`)wuyj
zzd7(vn{VGUQPm#nr@8G*d?UTHb_KTQ%7i!;j*M4{QoDb$(^8v0-y;0Kk<|c^4Y|<P
zTwES;q2!|kH=R+1y7gcwA+R-@rx~x?o8d?pe3veA!E}$#LZPj|H^=PJq?n6uj0i)s
zYlzEHcFfvDsll|IRY=G4(8S+F+%MR&*OFGn?*aNgEI%3z;q9r7!Ageu)1p|WRI26>
z{)w$hlhLYYTYj%yTH?*GO&)rt8MewUNxROP#w0&4=QomW?(gmGJetALhhiC2B}YcO
zX-CGAF<R(`&6C3OYlrM=A0f29qTSV;&K@CGPRpl$dM*5-+w844<uAqq|6`LnH%=M%
z8IBqfh5Ml71qS2seA<bZS*W#?E9&c60DI7We6Wda$hroePC0+vWgsAUWpL$>;|7qp
z5TXj4YbF*tIy&UMm+66<sFGFC2nEfeqH0ut^9)U1VV9pMYbT<_O2ZN_e)-uihJ7B0
zJh%q7e|-hH3QD-Ef6HRK&&rJ@Ib=AUFKfA-Q<dL{&C<oCNo4Y0>Zylk$2P--px%mz
zJ(-CT+3F`K6ATN|4I%L~47y8m&WSn5Kg=tZzMV+1e_;@39zmXDZ=4gymaV6@j8FU>
zkoc1vzUy;1ac|YC^0}hM<Vjv@XJyYxw9r-25_0fsCdlJk0{XXMiD7iip(mTSiydK)
z<=kmcckr{}7Hh^gPhN7!Y8q?78l#poAX+cj*xaslK`Y9&;5uITy~Omin;Zw}kH~5D
z9g>#c85$Yo*VbMF9-_A!V^BLQql97vP`BXlXJsY0PS;wGeR+hM^((q8EO0MV4m9g%
zpLlo-jsA|0r*@h8dJZVohNK2|GgF21^Q)>DNJvOtUhx}oXt`sEIFn~8^JmoLn6`w3
zlh54T91}{OW>niht8uxf+FX&~jsPYly!nmYzm7l9fRq(LW+TU}NN}1Up8FI$mCj?7
zrKW~&S06b1)-edr{@e^7nEp-TEwEARr=TcaMvAmKzwAWT0J}%CIbd%cwdj<>&5+G5
z62Er!c{Owvy72OILsR%r2Xx`0WIMFkSC}V~p|%9ou!(5@9*oFBFFm{t2;%PzyI&}$
z@!{Vd7^>+6ugA@5=I+V~KGeD=d=+zcjq)nDxAN(9Sh2dtXZr`v8E#G!6`fYiesC5W
zWYmGduVjpY#t!a-wmQ!f%|qOpbKhoMNy(6E#`OmMYg$>ZXRq{jb98%asHmt2Sx0!7
z%&kDcqF^uuZ*Ol+Wo`23fW{#xntuS7^}xG~W5dJG2_O0d<XpS|=us3wMKpd5|5F7x
zA%j+ihP}OglWkF&I3Hac_wfZvW>so(yevhhE@{yHtyN};60Ag;s`&9fzyj_s>+XT@
z^5*}%FgvXW;NNn2jnnNFCkTdu7%4px%*OS&^-^D-?n4X8yCRme_G=eROSs>))?4^x
z;)3HbP`<d@KnqSJT35ow+`S(I6*#7K=PvKw(rqivaptVsQ)5nKi*GYWt|9g(mnG?D
z_0`Dp>|(=J#4Jb6W(p13w+;5Y7&0WRKG(NH$xjYgzT57@EIXi!vAfcYmF-ZTfi;?>
z`26xk7Qu%eAL(S_$4s*K&Pe6A$9ehSfeXW9;}yA$C&sC!aBuHTC+5&ga*-nqQT6uL
z!W^>~6Lb1-`1h5e$F8dOOCL=6a~+A<_}?!1eOJX&OF`1lzoJjuj0$<lufZp`-9OEv
z@iMFQHF(LuleUl-!=(;fYSk+?q~zpcqodCsA5OGtxx4R(9RlB-`Klf+4Zv=UjLdTo
zW%GkB$NqqOXaumVhG(G!1O)tdhPA7FH%uoO4nU$4z7Puw<U8bn9~CP{_dt4BbUEX!
z#=T9pXG`fFM>*%bO$84rG1}PmiOUOveLCDL#NnTkT1OtIx262W<0(!r!q@}}XMm9U
z?j*Pf!-<=W>2Hz~CtSa1Ia=TRqL=4r)6~kPxtBOSes_Kby;mu!dtx+Qck(dA-B$W@
ztxt9ds=`b4NM&jDh6gLYJkd=S6N9rE-cwFjPnzCsn{pveLv2epUyCHoy-m(TpK`e1
z8H4UM)-qi{jp3BClQ&Qrz5K*P2+T%L1oxqH<g;(sl0SXf52L#1uwA9{`25{sTk-^i
z#X|Zg7+Ia+LMk@&1|>A%q|ZVNwnj&F@-F1?xt<VgQ;Sw-C-K?Bfw3{qPz`l~<n9TP
zF>NRp=YW;&vNX0CZ@E5MMFOY}istgvv<uovT(^J$Q*?B6es+3#dJK^D&u0f=ZaXP&
zlAn)|^ZG;nR|X(C@9665E92zkWbo+GVxSTeWnNhsO$;q(I}Yc;+nbdlNp-dI52}Lq
z(=!Xigf4eWWYY)LvwiW<o%e8|T&ch5fBQS3CU=PbUELTc5?(|IaH^^Zd&O)MZInEQ
z@77B}K?<Tk-aVBhIo0n$IUNkS)ApaIS7oub(LL==2?uiKm=aRB-GqGiB;H(&t|uWR
zZ})dR&fJN-m~-W!fD*UOv&M#dVHgPRIXw8Bs1TfYOwtQ&Q!jq_*(sxb>Y!o258reV
z?`mG4I)7a=y_YSWp7X(6w*hVThDk&byB__6R;=KChaK9`qlAkTYbxSmV%>n;kqA3I
zjx=|_mM(6k1<+UmyKH{;!uCO>=Yp0CqTaLDH<LsyC`b{&1<-?2E*q7i0r$$}S6eDc
zNkknPK{N+Gazn!2#6G}MR=+Z~+0@YIZFIQBE9OVv)<}mHReTd0N5BaT0*wFE3QnL_
zxBxMJXh9ZWZ2mf?N2aW!w7<CFOawX5bbfg-5laeai+lJ6(fY*tZvcepA+pP;rftS+
z%!z&N(`(q8N^0IuNGS|v6--<Ed|h)qoIJ{APangUXJ50G!(B2$4&pc-sOb{j?U+Q#
zM;;t%1envnkrB|7eK`ws_ruq{U$~o0lHg}Y`f8)I1=8%BFa26r<)<DW^4YA%sXV8*
z(4G5jz?I$bmA19H=E~}HNXp_<q}AN-VQgne*7~{&f%XwGF8}7rmrM=Zyc`@H+NP>)
zT3_0(j1&@T>aFeVR8xH=K&>SZEa>a%f-KD}EoniQ-bX1Ecv7#ft$CgvAIOz71ucpq
zp7)ZSQoKKiyWrVi1@S*aHQO>XdS3sVQP2K?tOQ_1fUG~*u;v*GpsbpcW*@(dOh3F|
zBgH8oq?Y9D9n^Vn-8)Co3A&*&5n(IBH17V{?T_fj#0~8Vs<q_UIplSi@^RI9AMeI8
z5~Szdx)6BOR4A>QE_t5cmzZukxBw~rD;}k!yluqj58w1T#J*{<>`Id-ds67mXzu&G
zre|U*_+&rp16~_!0EJ^{1;3ysv-<qgFox^^AI?NS@pozHiyW9P_cL38%NmR=(M66X
zKwU{FN&EZzNsX9=S*Y`YzdZ2gX5mbjxo%}>ND9h;t*tFW{RC{R38W%8aNnPR=l=LO
zm@u09Gew}hM_XIlb02379OVLA_Pig}|6wp(KP3Bz?$_&F3?-in<Crn?6=h)NBZNzr
z|1aNtV-nnOLPUrUs|r_S9#NqeTBIMLo+MlmE(#4VKR<0mPSaE6*$!O{Ui0czSzNLf
zXp_O%M*mQ6Xt|I*jS(qbW6gt^wwoMfci4J2zNXK3gE2eGrV`0b4<9O(CF`6Ba6?d0
zuur)KZ4!|SZ^oP*-R6+rrgX6Tp`+iC)4Xuke>7xzhj#6{!f=Ob(_!xwp1>;{8D^uG
zp0p(Yak08iNGtoJ3m5io`J8sqEiCoH@A#hpCpLluuKi#psnH?^(EtTGr3Q@Ve?cX0
z+^F(dGb(*teLkb;ma_QRy)1>O?ryCeJU+-Y{q5W6yB}n%JECcDw*oZg`@~!0!9%mN
zyDO0Y%h4XwTUXGuRDtTdrqj9DLOaJ8gMS<Fp;7-YveZ1DFb3}ds|z@cXh@UHn9tC@
zjJR36XdgoHW9$W?0HQ;GRKWf!FOcakMfM;<%F8{^FR#i63c*;fHO9Y^jqo{Y@|tKv
zD$P>&7GBI}C#v%lC0C2Q9986<1R|yp!upXM8zdGP%AxCDj_~6}9lXmzXB@C;(ZF{r
zs?5+0Q1iw>MxHWkf<1f2X1diGmxEovMk39AoL}q3>aUW?vGkl7@ynWYVOF{vSj%vG
zON$si5)2<~;ktr9qjpP!-7%vDFqF#!m{KoY?5@Y7WVe~7mw+1tf4fBhJa0sdp91Fk
z$Kc>S0C;>heoF&iM1Y3;EgM~?B-arQjG&oS-cw=Knh5?EIMJPEOYsI@Pb02OZ>i=L
zqWR~&!szC(v{+GgozAYmbjSQZcl`P3>c+zoh)NpBF$Eq{j9D|WNMB#K>U)Rw3rv|G
zJ_%h>OZtj$aK<+TINCGs`y<i4+30o!yDYoNDfNbLV{crQ-Nvqdyioq3U^*cQ6z{cW
z3V3B>?K(a3Vjg~eDRO`+gRWpCVHRhm<krm&ONrRtYXOcbeo0wqn{_`f*Jq7vne5Tg
z+PI9QP)cM-{~f!G-h*viLsAo!9`m5~H!$h;{+kLbABbK>OyjVv&a!F&%0QVkcXx^R
zxXFf70n6_uj!h5SJ6dkpXV-Tg85#L|;ZIf)IXXI0lynUY4bc<iL_o#D%k)a+Y0I~7
zOoVEuDd6YEcv8>Y++{*vhEeFAnyz~z0-mMF9NNllYl{iXhC$J^85tQK>yy{v6N0%e
zM?wZ)F(gC5p6;sj#FZ%A%-34dv|EH6l(PP(x~T-!jVkS2H7Fbr2U0XiE+!GZ0Z;;5
z47yD|R1l3`EimFH1k+2LPd~<WtP`&yn>6*pXSe%Mo;VQ$wJl>?|1kXRVn)gLR@O{*
zo1%gQw{(=T7Ndk>hbun)Iwq*xO2o<E?fmX4bbCC2>*$BCh*DB;pN2n@xds0)7<-^F
z)Svo3IkEM)qi%kf^Miz4teEYctYw?1<qIfby1TM(=cW>!5NwGR&c5|{O3TB+OZv{3
z1~eBThXMiuJdr_44|EA4O|Xuk4fLLWZ4(9{K!*Skg#Cpa7Gk1A0V<nN9|9nvR5sAt
z+g|HBT?tyMA$<@<VF57o6%CB!!NC{0F96q3*X!UtvzPE&#Hu?mhT8mqgtvDD^=Vx&
zVIw@F$@c#jHauj%0sxI<DIVN%k&_{lP?)M=e&o4jH=8C#rd$nq!OWh1{T>SV8(X_`
zT9WS3U8}|Iq1j&gW;i!<IQ4Yd@P=Kk3r7S*lRVt+9JZYe={Aiw$I39b%T18?lre0g
zhBp#%N`F|8V)4zBHWcuv#}9#8Jtlc$4`+V$?A&jw=IGgjeXwMt+)s56a=I*<v>N25
zrz3DJNnsF~S(F>5Pe~EkImrV{3x~XTppol*E*oo-&@x;~F&4ZPla$xGU3Wdp%+N5>
zqS4nH)gHwNOJ_E&u)Jkq!Aa;l?Q#GM(bZKa!aNiBxn1Fy4?M{u!D;;<>mFzdnCjKB
zk}B6}nP;{QVIdXf4KKh)U`|IU-*Cjyaq4sM9M!w#^<Db*kfej_O$)dgNzBUMb<o1;
zh{x816dbGh1cP|tpX^?ZMte^{St}EN=qT&@yRAK~yUQ_QEDwYCe5fypK7OFK8kF<F
z0%fOTzn<gL#I4qxTIpkA#tM^+w}kL2IUvW2#h#oSzK{{XN%Zb0gWbmzxpqOFk^DBr
z-PTVv*oJRTW9kwlo5GCQBJOq`6!0vo^4@dXl~t=;-!hffPIn6&vD2z&?wPG4FI$g>
z6eUDN7}a&RmE}?R6ca{{T(UnX*>aYL0`0ROGR{Y;k7I?^Z>W2ppt-`+!u2C@ZB2}m
zDroA^5LbcFQ>U6fcD4LQ=$gwNRKWic!^`fpI@!SXSV~4_9(1B@vW@TGCjyUfdwV<K
z5e7cMK#0EpQZRc$%%l<mjx%UemG>MS9ug*bGUcIyGm<}VIe62f!#1_AtSG(M`mG=I
zIFPZ8F6H6Hzj-P9PhQsU88WLS`<7Wgx24j3U~ztUKeJ%E$7*i#_b|MUv#Kt((Jx12
zptPHILF<Xz(wM|TaQg6uQv@tF_En+JqoBvV6?S{}N@BPCt)SLXhisAH7Std=Y(euB
zdl!+sHkH$y*oj*usuNX`)o{Nvg)>*)8z=LVP|HCPw<;&%k2g~H&s6s;uf0<=qZ=+8
zW~`;Rz)JW<FY^dP?wZbSjUc#ho|&v#2kqy%h{krwPbfv9As(0my7&O||9vv{4j=em
z0POAfcr=(@qNbzMR<6j+C4}Y8n>V-1gt!3L>)_~k6O04{J&AG|Xp!6k%-dUWD@>pg
zKs$g9CZHWwR3z@1S>>XQWqQ*Zxci<+I`I&|%GN7_ba=Rb{9G=xnwRYS$9Jw~RZJz!
z0%1)e_ebQ^cb6H0<REdyM~EN2naEkl)4`_r@PYa_9-Y&6d8pib?+Wsx9z|x{VkfGR
zc%k6j1Y=!Y`JVk+>r>-JbG=Bsa(dvttCCsuf|0IT1Zy@s0LaoAN7-x4X>O>7gWtWk
z!GZ~??E5Y#d8wC2vSl}|Eot5Gd)mPV4oh-D#U$9{U+K6g)lj-|(TaGke3B&{zq)(g
zP?2-fMr5n_D)|%6v%Ocd4--zZv?ctvy?-r$c3jLXwx<cms<$rqd!gFTfu|PH5~8>&
zzp}DI7?UH65ahtObvAB8_tqavNlE3_)lG~lfb&hz0E5<@j=sL1GWz&nn}B^l=b2Zx
z&@-((jJTzrSX{3h;xBW1@vn<Pz|w~3IN|65ip>H^{v_zj+T|z6`CFfhP2a9cI%u(C
zD@b0>9w{ALi8OI3s?`y@n_<}R_sD@a`0M7LN}aF0vHO+MwRXzc(!<gr^V_q#&dc!o
z#1BmP=FX9-OK8=JD7LSON7M5v{YFxcWdS5Z_vcNEpR|dgcHLUfM+4`a(n09jaV*X}
z?wIyq1Rs`&Jr1_&T#(xSco4i_f^VTo+CY%2WvG%tN|lHCY6V}Tu+|g~>X(^_b8l}W
zVo!#MI2s-$x@XQV7S|S>wQy=EGxKr5|4ZCn-vqgZ!MK3{g3=)=VCL0D5rc;hBfyx_
z#|f$XvTg_hX};K(u3TZ!<bNHE3*0xD;~JlV`A|JqgD{J0g*IOakO{`wI;>PTU7Pap
zcYl2O@$NsN>!Jnw|9KTC&o2wt<(H<R<nOW%@2Sw8$?oA0`%J6WyQ_P_zQNbmL)^}<
z8s*a}r&g<bo8cP_ByH;ePoqO8{3fQNgjJe{<6}v|G|@smS2va8x#Po@!PmOsoT5s8
zEk|v^ZrwsZ*Oj>Wl>AN(9sIXR6oH5W@<fWI^Ha-ah<PhA!mk<Ag7ZtOX5<W4ng4!x
zK#!WWSAU>BN~+Fdz3xw6#SNo&+`rdYr%JqQPN^A*2J}CmtvZ$lJ{0(>3HAQ?K`7Y?
zLJ-o3;ZGLK%*-|u<reQ$!$Kddz3lm4*g_d#su;BA0*VQsA8Fs+$KfPsITa#nYh~aQ
zMf=wfr?)Fm2f~ou+gD=<;Lbt)uiRsJ*pOLb^bOO}!m0G5VzCH^URGIdKQ~F*$;Mtj
z7+k0l-|!6v=gYTRcn2YsTC+~~`Z(mm>Z^l&ExqMBz3glAs}btmc(_DtW32;v3DNTm
z;P6>&Y55#NrDz2&D<yGEiM=`dJs7{Pls@ikY$?fXW-Q+G-Ns&x6k-*6h_0VOMyQ@N
z_vBf}(<2dyH_yZ_?a?C-X}bKOFQbb-=t(g3#x}eiTBf%=7~`JiDk&}11bQt>Dk?^t
zOONm2jw7LscXBdZCl7#cHvwiijeWtTy%N^ZeF^Z|9GHS&;o#W$Cd0=^Vpi*N6Ks!?
zx(iiC|M{8f;NsHR)~3eWD?k_dHaf+J8wXqGBoqw+iX4O+{{G0{<;3~v4=md5$cWq^
zsX$g<YPoVoen(0<el*0*V@<^`vMt&3^+jLyg7>aO^)2FG8)6#J&F})h9Cqt03H(jj
z1+)iVK3+nFl&1zK{ZUOv$6>rQ;9bEi504ZB?Fr<Dk}Pq%$DpfEJbTt!IVi$hXSabI
zVUkaI1{Yikgv&Q9dTJG$ZT*0V_v-<inWTPfG)BMmY(qzX6rtfAa;K5L{dmSFdb#`P
z{zoQq^*L2>mtDi22J~!9@~JZbQtj%5eE9lR@;UsMg|RU+P+$!W4>Rm?@Q{v|Tf~)_
z)$!iAabrdLuA#Oz8R5gRvBdyaz|{G!Pd<NKjcEJ;+}`gS8^;U|4*K_fq%i$+Mja`>
zCtC<{P-&_w75Mk4-DM(h9lTG;0$=S*(GcP!|M(%E8}`!t<!u+HhhII=3y}4Vnc8zs
z6Sc!3<&ix`c4c;pdzU9Q@C_2gZVq<-T-ofdJ~?{i<OB67DlpFRnLp}I<TuqL$m>2+
zt=%OXU*3DY8w~;J+bp}}Yzq*t`lKbd^DK1o#lF8H{0+0<VZE=kk}+&BYgQlcYMLN_
zE}(uGNyXbi1tb?GpXjXi7yN9DjG`~*lZ+cts#6SikX_#47INsu5?xSF{k-<M{d4@u
zfU}=l>kACkS;EeacQwgx^tQlpz!%^-Km6-g<U&u9hSqWE<4a=Z<N!#>Lznn#vi(72
zYIAmaA{TP_4P676Ox)24*qh{|tRf*14hq*yr2xqpNnu)3Q<<gmV~dKunfLLg|I}8}
z(rB=Lj$!yCV9*XF!@n9%TpvZW7Ey}yF@J<nXAE~At*QNiU~uAt42X8FZ>v?}yj)d>
znnWg?%YzUOE#|svUG3&x|EDE+(+s)nYmvVT%VxCSWi8f<xfDX2;ofVeD4Yr12kUjH
z+eVn!&Y+)gq<pf)YEY$fJLOQ+)*;1R{coTavwNf7zFwqV-(fVGhJmJsz!RR#EUVPD
zLyua}OKWfD2Djg}LwiD~gU;3-2XDW((o(u-_^5$i|Fi;c<9jplG<JwgjAiy{b?012
zBx$>97)s6JDgQ@Qfv9_3sMb@D)gJe@_7^JuvXl$ru@V2jSjxqgfxB0j)XmJ;33nO_
zh0;vZ^EBDYsK|GiVsE;3un34GI-wFS0@%p+uOuNDScZErE0FBm{#NvqrvsYNo==Kq
z_|!mJ#(+8?74e8%tNkqFgqJT(bgC94^1(vQ@bVX`@d29nhRB%^t``@bMUdzR?-nLH
zZU)rb$nba2EIyzc>0r$T)Kakc^1?h1zxo4;U5h>CI!h7TFmG-Da+O5~!IEurixWk<
z^|rduy^`yVZjN>eQ=zQf$1xT2#rjImr=kKRe)ku)WD!Hw(BRP=f|TCJh<lgrF=f-u
zD!kNox_TY(lbtH8%>VEFB!i>lLwt_U@9Aj<a?&9ra>FsJ$PtX0cE1%hd!39@p*;q@
zOmb4<dO)H8L?Ksbdoh1Gdm_kUujSb<bwU-IM*a}*Zb|?Y?=6Wzi!JV*ur4K4C3JDi
zF#Tqlhnr%Ww$^GOzV^oYBiLkuM(iaFo9Kd8D0W$e+0MkxqO%1rpZ4VLmAi|Kh$D0C
zHCb4HN7g(_4QZZ)V{t6_iSTD5XU&PjN%=Z9sf+}Rfr_eII-yHF;GWG!P`Rp}t#{Bf
zf3D^urD9Opn;4i!Za8Ca*|2L%KK!_CtgzXssuEQZwnfn|_9IGElk5rmqT4hbXFcC2
zxa`^J{8A@h<7a<}=(_pOOi#xF?g!|`efziHidnn@OgFEpsw&WYEC3zk=ZXsLprA%{
z4VWM#oXD$Jy_9E0M+pswOw}-z!K=c_msEFb)jCgul)|~W0IhcY-<zx}?yvP35rQn_
z!GW>pgti=G^6e@3<j<NTrMGLhA`!avC3ZhOB3mA~THaN|H?$Zx6jh`je)gM$!ENjL
zkpAYX#x(0Z{PZK*b?nJCtS`*msVn`)b<O<6=D{)pf&6X6N!;N$nKMi7Lql}Ac^Bi^
zK2!GLAF})Ja@a!+BEx1P<$IAW+zOXB`wMroF*lt5P;W^FGMYAC{U1`1Ga=CO{(Xky
zP}SbPzEmT<rs$ZMVbHAwk3DI`O?~I>?QKG1OhE5#Jr_48XBVm?1_(1&4}Pbavo=r}
z7<jf$*mB?25+!7W=F7jcWwDU+%c*v^rh@xL-oY$vG+!=KTNT!%@0%dehnv@D?Jrc#
z?3+(=KTPqmfqOa2G{Wv}s4$Pm=(IFF<o%Bp0K~(?H%A1C3gl#?SGgT|)H86zZu5J$
zc|1?JV0tWJI!p9u2`Z^lrB!Dpo`uIDW<s*}2Z5Rl_UN6lVYstwb3$0r`vt^eA{eNC
zDP-_Ehh%$$U!88akSm|>_<TmoF!gbf^ZOV@ozkIfeXSKpI21jYmzPJRtgL(={<FWI
zFx6OPH^AobyEF8yU`O%8PeYTFv7ijpUn6inj-!Gufb&twf$wIfTZOWMLEz=JH9gJZ
zv?qF8GjWr%$ny~YRZzDK^1sm_geHytZ;?k1xkp4!>~WT^ryDDk6YVPUwg^Ve>wg^M
zW;?~dp}pat#mvxCnk&b#qkD9^xYQ6>Ul#LSeZy;l#Et?rd4!mGlO2oMe*GF%%;*GC
z=7GZ@r}~3gI^;}<*f)cHo0G6w43y=QUiGPoR-K}i5ZEc;<fRCwQORjz$4*DPAOGp{
zTrGINzFtVHw3%epGjTSrapgyrZSzg7kknVF-S5s|l~bcN+tF6)MoU?w#?*+W07ih0
z)4{n2Or$3!aDCuVB!gZjj_tzY?;2;&Ve1$xF$S2r7JxYn;w6w^Pb^GSSZM>W4T!{f
z(bN?FMhAH>W|vLaIz070)n7owdlzRlNWhM;Dez{ogg+`Sw^5jGa=Bi64a$92SE`}=
z$XP8dca$~!YSsd(I?|?aGuHJ-ec5${Oc4h|t7f8mooRaq9finxZNgJo_UZ)fG&iWS
zp%Hui*tqMB4jI*2Cn?xuAwx1dvP?^@BFTW+j+K}Pl0o0Sw=^zY7&(NGuYqCSIA6`_
zdwq!(UMK~WRlCpD3#NAskd*K;<&lC!H|9M9%c~VJ2lZ1SD&Gg8z{&8k=We%a6Q&?6
z;&tXnS@$6e=dS#7`>R4ZYB$~P?GqL2Lx)<;+-cEssoFDhs8>8Llpz!=Ehw<}8f@~2
zAfqGbGRdRV@54nzMY{+sB=?!7NTlL0zy*Xk00I#<vH(W|E&;IG_l=B}0*?o?6djzL
z+JP!l$?AjPL~mVl?BlMI=4%HrfZ00b{r9dBpj0GmT>s(0L_L&hXJjWhE?%tT!>aib
z#e%1)k3!D~dwQfDwJR&hYL|;VFWr2{I%swi>YrK75L<FHK(Y~TeSU$Q6}hMzS8CV@
zukmniy2M46<f+)naJKBbDDBhS<m%lRIIZcMtsT0nhi1z6J<<JD!<F<k`pWuFm+>Yl
zESS>jsFN(YB4+u)8Eeez{UqZipB!ddZmmGOr$BD@Kf(lw)c}H^y2^$O(~O^qM98wL
z=g|}7A0R+a9UOj){w^)O<}zJNQ({~}+baL#rY<m!P0TAUrtrh?w`}KJ5c%}1c><?I
zI(OsW0^~~G-vT5VbtSy+6D)Sc=_KWrPSV#pp<(2ps7XTnuU(Vh?^D1lJfd5%dl6&o
z%Q!gx<~5>LyP^38a+zB;!mFkWxo)lvHvehvsiX(SioRKk5eI~_tv?oOd*t(Z;#Y^O
zW4v3^cu2WlTZ#BvP_2|~BN?*wJ!ZExu>o8IirhirL<(JhcA`Y~arQaw#;Tj7TTr|A
zs%BXc2Xe#BmzUPa<zLyd`cM?F0OpNwXn?BVZ@<vM!Xg0(xcI;i5B_d6;NS^DB2ctt
zj{}7TU^)q*c>MTrIoiCz>l`?X;B4t@7E4ipXXoRDKv<~1`;^+h<cO}+-%idmxr|lf
zq7v^MI*~q`vzVa#Uz-X~6)7~+8m|ug9`Dh;?E1~*1KJc-C83=bqg}~9^;NWDLX{%v
zt}$Cf)UOGXqjdIyX$Eb)yp&o*EVy(ykmcAAv0VlXk1z*O{X&hzZSV%|;1I5H`<|`z
zu`>Z~sgZ-wvBQgcU?G8kWne?dx<V`@)2a1^>WIcp)8nbv59X%PbpbG~VGq8MuP;2u
zhG%D!2$)vE$Ekn&>eZ`rAl*$&SSC(VivK@#mYFZ>?qp~l#QE}+42{-mc0gJ(KYINI
z!WR<%zPPL`xk9%e9S}eJxS3=jl`7Zxu25P~nHQ4Y``AXp6qaC)SmyWBi%!6JSjXGf
znKmVyI^Li(ei1-auwu4?kWm=h1<*Co8!C=tfx!nNX9|zZo!Xn~#uD6{STA$bJG0SC
zT5@i$=oYF-Z^i^9ywj>{^v%(xg4_O?xbiX!eV&K(6t_tR7TxVs+-^|0t14vG5U+Z;
z{&2rHCyc&MW81SO%&p%!isSp&(jtmkMerDd4jw@%%$2A@-11+pjIqV|YeHfoq5W4@
zR>s1~x%*8<R+bsewwSa8H>_<wk%%21Hv$66C(oYoGc1nqe`z|~woDJ+2W+kTjkCY<
zg$J=`DSF`biKc=C68$NJy<V}q+tqHEt|qmZAm0*F>W!o>9s52XI4Qb2=$&WT@w*Qp
zqi8`1Oe+>Ukmy9z()hmL!T^za!`=OiZhv3avLkcA5OH|x1%X=hUI2&;C$hYDxMUX=
z@8;KHZGAkvu@HkM=3U7`fB8*QQu(oz30+~H5I{5FA~a~#ezuQj&7Dtx2bjvb|CykF
zpGSe*1}!`S%nUj5{RJHv9jyx3wktKOqiqpxssU@B?FoWKK(Xqt1*>p_HK|FUZO5am
zjNHux%vk|=ufZhi%PVgL9|H+1FJDD}Uy2H3_VxpL!jr4{kFX#X0s+df)F5AD?sJuV
zV>Ne#-fS=BOV}HI>AS28`|-nYY8s*2WdVan!LA%udQ4z^Y9NI{rfsVVvR6}4xW^d<
zhy;xHozLJLtcWEfV|dgYP>nx5dg|?b`==Y>1I&6^+!d`{>ZyS|s2&$2dT@fo$ONkZ
zL+(j-v1P~Yw{P<gN45oVh0%xY)?fusETuxsS+3mNGgvPej%tb!cwd%{9YrD&00Y0b
zw|5<GR`v88&{MolO<g$PN?io%O+tKv55A&nfV5wWz*$gInkUWvhqtnfue+n0cdO=X
zdM!m&sj04inw;cs@xt`iY+Cb+jD(v0=hd#b2NuN18oy!#;{~exDD^u{XqF(|oU?A2
z+hPfc9+7xa*~Asu;h?TJ7|%jt>oIGLba~9i;GlOMhZW@j^_QrkS!2o|e1qU_t+zEM
zM64gpKX5XUuom42XP62p&$%46?fm~R_SI2QM_s#sAf<Gtlz<2b(k-bVf`D`=NQrbe
zB1oqK(hVXd-6`FnATe~u&<r)qJ%hgAz26`2TGzGELDtgW`JH`sJo|a}u{>_2=KjvV
zW<Z-jpE?7Re+LE$Zi|(h+-g2N9=1P`KZY7IhPB2{dUcM6o-?(e@R~^azI}@hY#&J|
z@o(Gk%=^EvRCB(^{qcXWRDz)gwwlK!WvaNR01~)+`Et?2%gv1f5KWMkoOEW0Gi?0V
zBiq4-=y>t&{#Yv%pZ_?8*iSc3p#Tr%Ocm59Tx%<<#)~Oa0H9(M9%$+hWWsa)l;@$p
z`@9!ip3Ku-6ZMm3-lket54HS}w26s{LoV^GL^G|Kn>8&C=CNiF><?sJdh0ShYSi0i
z0>x_2k^kGI`t^S4P}6W~z(rxD=_Da!op=s5%OY0Obk@5krj>i{<+i>}*SdZUXZ`G9
zR4+=ZF&h*<i@}p#8hD`^<IcEtq>?TX0W|X2EiIB;!c$XIf2ysiHH&pI2oF9b6oB~m
z-{7Y~IPBy9%j!!|D*|o9Ca&|3AUQZI!A6=v{r1f)D#qW}0G><L;O0_s#s(=l)@$NE
zo)`mfF)!N_6I14TN)ZmF0q@=uxeLRMF*ki$1XQHi06*o8*sH2SgRMabW7eg<NW(Cy
zh1pY12ENriHMVCpWYEY-=?SYMxv5Ki-<NMYaLJ~;xqhva<OdHq&a|z#q!rG&AzZ{x
zK9i3^$i*v}{YQSBW%{00=6D^u-}}Vb+fZMx3IL(V$jFTvax|;Sl1`9x$0TlM=6c6E
zJAwO;OYjT~4ALewU%h$*rigy!@Apnl0!`^(zkg=}CDk0SW$4$I^QguCo}=;=G(V&J
z1vEE?pJR+<EX#h^Lea-iP1=%%f-yOp+Rc94Ov<*S7ahf!>qI7dzH~p&T-K{1UhWKu
zkDP2zi~cP3Oj@4#4Ry>$D<m|)Pc4QznxHob-#2WrsNFW8&IfC}W>|JPos{0#Y$EKT
zUab3qmPC<#IeVSM)G(Y|*)_?UaVd7{j?$Zun)qSfvm>e$zHts%yy|~;Jn3X~HFr$%
z#{Fx4+&h~6x_$=_FAHQeVB{FRW5@Y_Xbh40Jd>Zl0}TRF#=kk9FJ8*Y&i(-?4J->T
z)9r8HzKyIwz=n6}-B)Ij{&^Kae^9^W3aCO#P`XEdUEbdc?D;>Bw}-jErZMSIqxVvP
zzL{<Ld5D@x5dq%>-qK1%gsqmkwfQq?%J~w>d%s!@Tau<mt<hK2T7ssFic70CagL_P
z-a98m9{rq57#YAm&}8Gh$C82Vo$kQE5Fqum&rYFU^|Lp;cFx--g}&-?Rt$5(#Ozxs
z$wrL07<~{=y*H8Q@GD!-S~A3`FKlsW<VW}R*z<dpd=KZ~aw=92{3W9<N}1FYX~aE9
zl$Dh!sHj3cA{raTkey-JtYcKZr%E1(aDX(NQCCL^lB2W<GjsE7pbvQU>Qza%OeO(f
z1>0?mFx<gEGIy+JFFm)iu$(fCrx9(e*^w&Wx@i_E3f$yFD;+4}sG9NJ&3g|<j~QrM
zw$ckSOMs~ks94`!v`KKHp2u5tT$V+(df!mqUB}}A*<sNlz6gdo=1Q<16VNJlH>k>Y
z6jlXDPQ2ECSbnKbj3PbuU42tRP;}M=ayfgZArhGgS)Z^HH-yy%Z{)?rxJC&yi(}w8
zIPR}ux-57OBkups9U<X!U7Zof@ZQW${hHw3dGZIeA^`Sc2h{1`wt-kxz-BfWkjNN0
zt+%d;mHrEJj8}iS?*C<uS%wleI}PX^*#JB+CP3{b4Z1)03qC^&%B)-**pn#rXKy4z
z9UPJUM1xL#Nmsyj>aI!7tYF#@=uX(~t>yUy5om@8-H+4TXmjm2b2)Na4|ZEWb75Pa
z2^5w#e99>{ZGiK15Nz|zrGDs!Cm?q6o5~6{JBZI%36HX)f%$aCdybo?<?_a0!}r{d
zeXbVBQPDp#M8PsPpP%vm_;&g@ZQ@~!WRzPG$n8L(ECi&|U#*ZO<zJ{}eq5Y&956p$
z8W}~Mp1KTM_4oH9>mLn`6^}-szCy}we6PJyUX5vJmTl8Bcx@WS^8o_WM0}CQ-v!^g
z!HgY5&=&CgiZsX_YK&pRgUm59jlWUX+qWcKd*uhaoZk38oVdgh7jt#_fScWKfM1^*
zlc?mWj3$4pfp-{U?bSfpzU>(o#7)A}Y`~^dW9H(nBz23AV=xNLIkVh53MRjA@0lJX
z8JYs8;~9gfyQS&pI^rDECk>wIEW8FZQ1+ah3-2`l=7CWqw!RHsNqiuE0ewy-C0x+w
z%r4=0@W3COWWajRKe;~+S}Mp{KA=hZ`q74^wU3Vka(va>UZTlm&>uz4=FrvC6E{kR
zay5sG4b;In4HKGJDXVU}QOfuKX8A`zORxwiAo!^J`StM)FYAYcOplb*4Q{_Qmff*0
zrWyOVwgS;Z{6;Q~Nb~`bqMD7;Dyv8{MAvp!8wCDiA0>7IB3_zUy}{M$gWc10V~kld
zSe?&{rw^*0=1OH>iY>_{bu<kZ%W*k(m>6%*!!ICrMtXB{huhm}5$XB-u+}XJNmnQh
zki?FRj}xC<0fzK@NIj|5MA3&l<y65hLaAVQD$rAH?CrrSxi~rRCJR`%f4WP(aCELe
z?0&wQfXwcio1107D5~qPLb;_a(yll6r$F%PqJ!LMV4cWssC=?Eryo%-0%jlk(v6MJ
zB1RJ}bO}b$wAM{Vr-!nED_8omJ<t__n@GE)+EpV%e=f0ju$y%51p(h!n4Q@;6)F`t
zrCar#xuA-pOkx({QZ~2v;9H6bGbIb8`&UXDRcLpcU{77nvV2UJ_DmP$<l<<9Cr>O)
z21Vu7lO&<7*<O6jKdMj|Vvx+H7POs{1=vQeQbJZ5M?fo>wo(R?*SF@~%`F#i0o8{J
zG(YT4wq6ZeC2;C}LYlas;N-~}=++`n`)cT=&jBAi$8@-Jhb79*;I!=@oXR)#w}_>N
zew29fie~=BcnnjpGTVCm+?x1@Z<pya@36aP)b^fg{d9DcxI*u)p@xNl5bchZq*Gz2
zgtfRoMKMn|)?JO8?UHM)PrqDZ36`q>t2>e-8k&NwnG^5cj(W3q^i_1&1TGO$<4Ef^
zyo}E)#d^kz`^a}WNW3We8wH#lO&JyGkuz1<wi0u5bN^IXk%Ll{+&A+XFCb$BWx+y6
z2yrx*Z8&BBe?=*vHUI*{#Zvi9c8z3?H2?HRp3*#wzrJ`)>N{>NHR;+w`_)t+G7B?J
zxlG@t7n1+64H@}5(qT{Wd8YWD_!YgQR|An0Zj+Ul@$w7{xCXX1!d7rnX@hpHy-04b
zYj9GgqJEg6%1+2O(iSu0SwMK%f%MnXtm#zSJqbaPskj79%Da*VFbP*(M->)<;zrCM
z6+7eo=bFvS+~TRFCzXrcl2=p!cmXPk&!0a67XQMW=UzljV-9wpw2;R!8<ND8naQAH
zRZ(9412AR4NLG<6&m_=vKn^qq)M!9A{QNC;lPe~%1?zlOw2A9-{6EMz&JEVb);@kY
zZ36}39<<gz5QPPGbf9xha<Va9H1j1c(KGF?%Rh)t!LlYx-$dHdXGd-<&&d5c*nQ{d
z27bqi@)PU=swqJ<8>SukS|xFkWj&mLrdRsua`fYBt5nciM_|YZL`%Wl>rezZUiT{o
zFa$>XqR4o_;KZ|xJDP#!{J@ikhD8i^?u7*Q!9K=-Ul|XG_kiXfSyQ+l<>fm|V}X@X
z%~V^<Xlll93u~3=KLOSatd;oX14v-J*cGYURntW;GNHVCgJh21zVWu9d0_N}NgnnG
zPjV!NnMGoM&D20=S~xfee8|k7g9A!bmku^Z6NH_kt%GIG^bhBc4NzY?Z?A^YEhvaM
z?@Z}Uyc$q4o?V`~RAkRy-v;8YXr4L94r9<cO^%&}Z8npkyXBw^@%*LN741fT-maDA
zYdJZ}7e)&!3yBt^B`q+g>)lgt3aINmQ)5;Z8eo_N2CBOzJ-4;xMlyw=v%<qx<PWux
zg2SaH<H=<p&POU|hEjxyZ4;fykreurvAc!|?$oz#xJ`VWf4j66r?=dUzK7N7X~Yl6
zosvK`m>kHr(<Varp=U0W@ZsMwr#x%b?mHLH-mSYI!-wNSX_jZKvmvz0GlSti;Rn0Y
z?<V-%XU<%jDh%l7>F~O9t$7=OF<-RT?t0sBX~?g1zmP}hQUGpGli53w;lV<j4=}N7
z0*QlFTh`SJK4;Ul1e4P-1rrIQzI&iot-wUb&Blh*o0^)Mq7^C?jsE}3ChNmE-Q7wj
zS<;a$R>6PqBNylI2AcVTlbCGhB|69#GkPg>nciR^B}}GX`8|!fcw~AOF?;npG|*%Q
zA?D!KFgHxc(@e{Vj%7W2ushNovEFs&lHIj`<|0LLSr~-Qcb6y1Rxmv<rdO$eucNyL
zb`IHT<NU1+Bu`vM4KY9<MD$8xUruFxUhL?Ozl`|W`u}3LBy1cKtpVW|lEGqIS`$9D
ze)I-@aq_3qk{Cb&2E)Q&JODDtKp?5XYMWdMHLt15*Jr7Z&easz1J3k`l#ppZqayZ=
zhanl%K`}s?UH6J*XXPLcTO-Q_*16f%<JLWm(5J-Rt49bIIhukKcG?T|112~chzCs2
zo2@~|3j8I(;=Wi;xV50dAL>9Xsn1x?-ncZ(eB8DBW=ldf>dnQXpEn%^KfG_ccVxdO
z(&k)tbk5hfT?RR8uoX`|_8k2c{i^bgJFaVoSM!~SrFLHg_t6n4hh_%ITLI|V%f`)M
zGh6!sl=?vB>S@^Ec3_O`s%K=ho}7UWIspg}2TPrxJ#LxfP*WqAn-igbx&3ke&!eyZ
zATG7P)oh)Ihf(q@&`U`A3Fg(u7nHnP^s?eM&9Zz!8(|}6yk3qFMsY?sZVIi@ZHhn(
zZ*R#93IaF#v)Z*bMyCO66|wtQ_|X;!5J3$f-BBKv;k`IJC1B=b2e!=r6gVO#LxqHd
zF?ie~-!em@?z2-$K+7Fp21CIM(i{D@YdisG7wVxzcPL<1zkTLPh=Z5;KeE1~&l);c
zfUk+1*WY+NrWDO3S!0s;-zs-i#=cz3EV~1lo`-gbW_zZOKY72tJe*>Vzo}=w@ZPvm
z3vgqGiE5P{klWl-d^mh*p|V2v^3WKZ#-B{T2B&kxd#a@!EkA9J#n&p#PB(Yg`IJ=N
zZk{3bH1%qTPO3xHx&IMvriE7Fm~_-vmRLpDl26oKP^07&E7Pqx8_btxN7_d9z6C>_
zgn7rt59S0V!iRk>6$-clV;`Cu@|%&CMxI}(+F=<4folxs!6cAkU4GN~<NLWC2g}{a
zj(*z{TjeG|v_#4~z84l|S|)7^v#O-YnwT(ws*UI+m-1s$n0tS_`TW&lSj$CeR21{S
zTJ_7{TGhnzsWYlNq+PfoMv_DHw<!Tjdhi@89oWN<W3;rxLo;UPwGQhRm+80_-+SQ0
z5hCHE+g;b|Ti={fomHH)L9R~P4EzZP*gfx&28m_^isC(jMW~~tb8gVvFH*B@@uomj
zq<7La;$6~c{PkU%D<gaeKC{1@4#!Cqw9T(4QKb6NiSG-5nUP%j1$-X_EIKhUF(+wh
z@;`bvXLm!r|LEO{bV|Da7oEfM-B6RQoX3l21M6Y0>2YkYHhTZFgKGbFFbH+_w(8d{
z>AdgX9bD4KHOLk6bEi*InX9!8zv4fj=g1!Yy`Ht>OBWXxo7~&vgkALWL#;-;uc@uG
zo=~yAHb{X))4yDsp#jhO#*_9ZWql=o0=4ZEJ72ZFDwJU`;D~hz`-PpsVPL}uefzxc
zcF<=Z+awxy+#04rJA3e0BPj34T~WR!ExP;qN+K`60h57%z(h?A4Frg>F}2BMAQ(e3
zd3ryyE^~g)t2<0hKXmdrC^VuOT~RfN?fY9&3jcL7zd>x5hwYSHv-s5@PaxZ4@w-Zj
zYe-*1;()6u_vL5EUG<2jzMpSu=t?-2ha>WiwNE7l@xETBC$Im3Ns@b<ahba9T!8PX
z1wk>6iC$^<hQZmZ!J$O0<?_fyECcgs=wNrKh78Lx{T>0~2dnXX4)|R#O-WDklC;FI
zC2mWNZ8YFhCml?Jo7$UjpQRv82y|>|gdLE08U^Kn00!70Y5*61120^h4kvH~R2wou
zcyHX?gaBO3r&$h#KkZMVJvwh5P43wgr2wjLY8cu*;7PMA|MspU*4-aTxmI~SVIT8?
zUWOCJh*}0rnXGP_Z4~YJ+Pq+jdVfx4=IZ*Mp=suNy({83;kp|Ap3RPL2`pu%t40BQ
zXp4VQxI9xV;D%~J#K1lv5-`eX%U6`lP)}px<#~l3ATE}mi*_IHxzBpt119mid%j>+
zdkx~^<ClpiAzIq!V1_|>;%T6VYT9N~h3M3OVJpNedJJ`jkt5UVZL)bO=`!}23-h$0
zbk|i!f@lQmKmMaK_FqF3<Ibt~D|pA!T|>M{^P#$auv)KHeAMgJ)9xJyj<<Mw7<706
zxug8hazx#EfeGShzvtA>?LAm;%5pWLE>HhwH9{CD)x~mduU|B;TwJe@onM)Fh|hM_
zh>}g8O4dwZTh2rqCQ|LCm`Zxj5gebD0CD=`mX5d*YT!_aWU=TU&|jIWSoJBSC#yl$
zYi#G`y}iZ3(g51S%?;R~3NK&AY#*eh(II)ofY)iS`RwsCpwyR98V)(XI$q@Hp>lhM
z_O~vQ9jCep=2YXr9z{-fN+i%;8+^A)R1C#Ed?YBz4Lk|t)h~Sm?}4{fpSIKWvPXaF
zRQ)I>;c9CnOjY977Nly)c50qEl?<}KYkH?%_`7(Pv8&oVV%CfJ16gz4XaE%CsuI3f
zJ;98DI`VH1VwPvHpB|m>Hw%h~x14wRg7Qc)I&0NdR@baKh?EFkj?PfY^xO6>B^{kS
z82SJ(8iG5w0m*lGSOEan@eg&DJiMHoNRR_ntgH&xt;X-L@_l*l);=EVUg|@KX5j@U
z4-`K89{Oq&Gx<MU0A%%Gq4;;bWp1c<Myxft-hu-ExyfCaz^(PNyn=2COGwuQCuc;Y
z{jviwczUe0LHO|Csf{VZG2mW~zz5(l7epHob)G>rc22+b@EcO!fofu6(})nTG=pn{
zMUv*ssCK=f$J)DQNNUoO!}<w8?(B(lsmLG*;nKp9ICsgCpm(agjrd^|)3ItZZvRbB
zbUr(?VdQgeie&1RmU0v3j@_x~LDY<RCGw=FyRSdw#T-Uyjf&MILH5B%Np5s8!Nvz-
zekwWj!3B(i`ERED#{h$dB#7s-RsAR16YM_`;yq0F<F?-j4#0a^JyfiYJ!{dsLH2%O
zQ<`vjy`Cge4zWf!!lxOssplTfTN{C-`{>!(g)A<N_9WaI$BP~uUkR^$SGqPM@7)Gq
zgi9KYTlfn~{YfLb?7VjTM^&|Cjrh3oMqew%M@tPFJ^_6*82$D8Xxg+t{tXy0-!nMq
zEDnYcI|FVl=t8mp<n_~-S0bC?37(2os1e-%U{Qt0@CKY1CHaX|a|RpRqe$VSa9613
z7XwX7OyZEFJRzzXe$7c;#i$N;PVVy8@Yz7ml;i@KTEkE-rAt%|qK==%@T<X=+B{4j
zf|%W~bDaTZ7|8{yLzRbH*Xt<l2J>{(EfMR+^JqR-AkCgOG6il&9(K+*eL1^XB`UCF
z<a>duzflVW>1=p{Lst}2j)kg?TQF9yi0Jr;eo9+ug&&x!*~4#q%skt-)bHZqA!q9&
z2gv0dpMI2Zh3bO=l3(KD>gZbjmlj9umDs*J7U!vCzZtBC!DNFGg$CqbGo3l4$UAdo
z`Q&PcQISeIH5%XC$CW_BeIJEG-JoCNM{N!T?)pvsNzqC4QdF;z7U;KShbYM-Ps}Vh
zch(bI{!n$%YH6HOk@txYT7pSv+ksX2wI{*+J`fis&#yMhhJrZdL*#vqL~9`v-7%Ss
zCpiH=s_(k^Q8ya6skd_pM#5`ogZJ$LuMs$+zA$6`d5@BbiU>FBxJx0;pS|Z70lxMw
zZJxVq>AJKVC_sgMURSX{KggY1PZIj^4qj#hJYhrRl)h(xL&0VAFvLjd?NYTZf648_
zXv)S=o#wfKUlcfj`(sMni*@U1G71Vo`Bk77jTCFrxh<fstSdBYy}aqqBY*z0u+(AO
zGBk?&F?|@l2a$Bg^;!W2xg<8{FMJdgI^SGJ-?7je#bFZT9}%RIsmuelHCf%DLt{kz
z(bp}aV72zSy$yjmQ4hbZ_s?NIjwjPw*DIQS@5LA+ChT)}^%Yst1>4`FNYf94AY<c{
zojj>^%UT5(h$+Cwaj^peVhW<pJtE-mLcX3#l2_xsvfPtMe?m9ajEXq)_4#nBB?`n*
zotAGiaMumbP<Ri?vK(NN48Ds)*hW^r1TndnQ)?eNkSZPczWnNA(mq-5v`K{2=*~56
zTBZ`90X_nf791V7Dv@;!U>{@&4Gu-XHj^5s&;BzkLQhHM7kfTA5no$;uZ7s<kO!Pl
znddJSpm`H@mJUynqt%iid9v!`zYy0n719L(<6DVpl%;8ZL?5jGS@vOwu$%5r{RJO(
z<`okVXD*I(XflUX@y$$Zqg^zhh>^rRa-E!8f02~87$Vq0mVS0v1D3?nW4C9Ta=tke
z&F@JGq6?9O(uDGru4S%J2#m?`3@zSrn321fb*&1hZULdKyUuZ4Y~Hoa9|Or~<Kl7=
zpPQTv0u89;fyBpYrOG7A9z$XzTs|Y?Np)H+@4Vbrz_fz7mZ_VTGE|yo5!qeg5x!P5
zAO6mgYkONYc1u^ynvbMCYe~3g&}EN|DT%5vAZa<u&Xsze?z)r^HLNGsjJ5iQX>Ysz
z-EH-5J6BWvh9i>9NJ}mG4C=u}HOd+r>RlU`$RKrlhTnux&B^-cE)#}r9)^JuCw4-p
zz~p)<t}^{1oxj8(L}JMRi;`{_FBdP<X(V}AebW##Bhs&iYUU?BGPz2qigK<2vDh3_
zsD*&gh(gx=UT6Vr#;w-az}!Es8(20c$H4d%Ge$)P?cp6T`^z{Z2HQoK98+a4&$x_I
zg2_tdT4A+NFL%_<>8Hn+paBp158TaXj5f3T6Lo3H$zhj!E%adQ9~ih6Qp7|d3jki^
zSYIb+XLlbuSreVpKd#Y<Ms!E#?lneIHY%wHn_7`AW0X%7k-8~aS@k=AsXAfns7245
z3Dw&IOQ_jW4WhSrgNc+n_}@Z^3*@`|f}QxoNVnFFcL)!NIoheF=(uDyY|(!hVp{IJ
zq{GbIWDrBSi^gECP*abn^EN$e`JASr0+*WQP{tBFSeslLzCNE<19s6SHK`<Y3Nh&6
zm<a{hJt?Iyv3F^DtJDQ=<s#h*9_`P=N+X7G!MCEz|F`;X8VAjY|I%tFE=p&sFKTB2
z|K6JAV2ahenk4+CG%m9GW=v}T3t*BD-#T*xomLz!Cxh;ZRVC1QczKAe_sd$6#CqP5
z@H~XiVKd}y1z}tBlo{Q1)Ep;QocCzpkMzPcJcg4Y#{$eXO<0}Z9ak4z%iA+s&U~v>
zMDpErhhqG1ier+Rxf_7b|FIhfb*p21X3FdZPD*M5)pF;={k=gV_0C&*-^<>QqBVLQ
z{08y+8N;Y&E;cuOMxI1dBDgOo4Wud8=%p+p31zp7wFCV#H6IS2-L1EEVFZ+$!`1$@
z((3<I<gM@s*BTp$G{C|@YRRh2J$e=|)<|x6tx~&ifuD&nSU}5~HaF?=fYSNzIhUJ0
z%ST4QL@HFfYfisyac>G5x)*?h)yqK3V2u`Wt^(^~wny#hZLT4S9>UVCMV}qQedp&#
zHuVZmO4c2(i{gC0bc{;ImXx>-;qH%x<>|(CV&^Me>MFaao^&5w;y7LbVEZho9lNJS
zS-VDB%U9fz{tFwaLM6GGq9(*itKD`B)A#i^H;yYkPIso<t`52n{+LA7eOd=&bO5r_
z3Tr`le_H>dQL$FsS>*mZZGr@HrgEb0l8(HYY&5)G97!Q#GwU|myi=m9R*!+4NM!op
z>*s`^y7M|DQj5dgw)V%<SOFwhXQgvZ*7N=|6N$y2mI<|-y$H%&>-?sQIgjBT#ZB$S
zjsxD~zq_p`!@Zst&~>G)NbkNCoY+G3bhCBzcC`m-SwRZxFAo&Bm`TLpm376`pj_mn
zrYzLgCNfFO$m+5xpi%|zQF?a0{JY3W$t7Ig$Ocw1L5-pGp!x}uTAv2i-?^$|&+g0#
zg$zxU8apkB9QMNrrqL1DvKC+YUHR8+&zN#d$+OngP+}g_KSUPhKvG5LvB5BqCO&gB
z31?}_JiQZO`1e)^lChqAw(6ut;95>O8cVcnOxMJSkK{=lk1m%wd3a)CBlmaIApC|#
z;9majnI)><WPW{QLF@YXk4h&)KqCn?=Dp<ve`xLpbt$%()IfWEM8m-7Z^Xnbhz1Q7
z`JLfjgkm5?zid-PQoW5^fXbL7#?6#M-p5~T6i9F(<ZA9$f__b)Il}ejVvsfS_J-mD
zl<2#t(OfVJWR*V>YlKO{)zC@I)yR)4K<Z!zt#RZ}5<t|-dk8K{X`igywtNE6#5u0j
zeJ}RR^Ju+#!dz;JJ6LzUO9kXoz#!PbZaU99VPu>RjnD2EftiHE;xHN{-40;E*pt#E
zg;#;1FM)O&AjVI=7+zCj1%xXY-rm>hHhSZ8GfU|)=1qlh`1W_~7#9k?k~6J(TkFW9
z32qkzrbE`R<Zu)S;q-UZdZHJ}QP@@ADbSp10|vU%b`<|u@4T{c{(|eNTI%#MNF{dd
z_uxIf&3EK#_zi(}0q2Vu`ifHHGImc{G$zOG8Hzk{262WX?p7}0j6}q250xe^LvS_y
zZ0_cn`_XB>)D6F2VjXcV6a}4B=2+g~W-a`sE!%Ye`1rutu?XVk_>r;bmLIoSwk7;V
z?6@yVt1@$P(4!<S*pT9s<KyFC{{I;VLwj*~iJ<q~qcxv=m3Aq)Ct>cfr<~2Z1&M9A
zs~z9QNBzDIB~!*&_gk|h5!N#<L53@}T86;nS-z+3oe5>wv?lu$A3fs~%HQ`}KkR*w
zEy1LmF1&qRHlypgr@kIO^kx0>T-$MI+Nx<AVl`yw*q9D)-g9~p7+s|84c`rp(=eZH
zIp{%1Z*CYiZKgMPdh87~m;?|=V=)8_7_(&%gAdFcr^hGwMSJg>uv`7{o6=GgU)ww0
zdH^ELE)D}>3N9+-{bPQ8@p@6?&>XZM93Dy*@lRjsAL%d}hCvm2xZz*9UpFjOEq^la
zp6Kp`$%RSbV{b(2LWc@uUq1<x3R=zaf<=kq)a?nP8>6Z!j!!VrJqP>AmT{RwJ|gG)
zafSW+NB9~UqyNN(?$yo*R-9cNc9aJ^AKKusrHv9>M#H(_!>$wInQ~*6Z#o{N(=}dL
zdYXb+RRV-tpPw@C|58_391`7=m3;jAv*U9}Xib(Syx}pFTRq!C{P-36DPnkMb6YaS
zb{?!4EIV;fJJ7`sxqio3QJme@_iqqo#DOj!qWzbDFTZ%z<toDB!y@)4k|>IoDqI_1
zv8j))5dA@W39WD`TD3J(ylAe_O9-}gINFz7cIcA?qBe`8onVi*Z3YPoU)nC#nFmah
zCymGZasypHl0^58s=KX1hqGYGdiLM<*2f=fY6K;O&427>l?-2AzCH>>GA~@4k7#Fo
z5pW86`t-c+fVaa-lin<a*UAdbc;DEYHc3&6+@IV$I~fhh2sT(mEbcsK<*f<~oQ;5$
z4{vqP>XO71pAM7vm1DTL3dl@q#<a~Y$>x4el#$)vbZsggv5D4c?NF68yx0sXyOiYq
znfP%rX-#J;lz%ZW3xDyT47RWiYYC^n-VXwkC^gc=SeQkVCR(WFR+TAXHTN-J3cDHo
zIIo7L&H2Lv@86hCj;g8@EBN$u!U=XPf%{r36aMus4Xx0}MIQOMm~)jb*Wsg_%TIjP
z;)8DY`fK%m&K8~&(`qSFmrRi~Mb;9rv9Y$*n{`xW`vtt|5jI0b!^LKsS$um+OC+pF
z(1&HHrP^1yZHj`$DZwA5@!p_<CLz711i6m(Kdllw@awyO9A{kaq`R5vR^JaL&s;n7
zZLfE|Ml(GrJX~R5m@3;S=QjP_a=t%FaNxSE=k5@6WAD+z7#L1S!(YM49zkWx-Cue$
z!N<Z(tw9wBd0Nc%Amg42`7?Houy2*uxm9$eqc)rCB&nO?J4!<~%-vbvN{$L#_0=uN
zdmfssbQp>`&QR~~>`ofLw?kCEj}t8EzL>Aaw6Zyq2<4bL0#C7N3Aq4+xV}Gz(x(fB
z9#%wQChzS*H@ziF!37z}{p3~1@OuG1MC)hzLHCyyvyoOfr67y$QZ1_?fj>j8Y)5{!
z<oxTG{7QXmq^Q>PlO`FotYfmvI5j9jR@i-=6GN$^G>FcgY<vt6w`TO|Q`S~GZorZ|
zdSSfN!eBzWk%eH-!?)iM&vve(`uDH!=R<lIO~!vPe|z76l`OH(rfGPY9-J_-KByoa
zJL<D&UcNQ&wZTnrpan}lKm7N~>TdsgWwNd+drBzMnGbMdnDR00T%3wVYzTO_L%#Sz
zJm!bmC`0PG2#hgaIg|Pnc0{@f4tahef1-2h8_TRK!A^)VvyMvNasY(fXDwaKIDu`q
zV2cH|Hl0e6m)6fCQWHOMJ{gSN725mRwBfNV*&3R#I;bS=L}qZxqAj;d3FD@N1dT14
ze;oXYVl$j?^v`>-82{%WC!81*^P`k-Rnk{{=o=%docK*LeOH>VoKU3mjL?fd(t?bY
zu%0ZPR_D_UU4itHTWeOpZZOk>Fil7OdxoLTA%~;mnf&JHW=3VK2bX$=d<{ahvq@WX
zZuUbH_Ah9tRbM2#_`A^eZ!TXD2uY4!xkhcbos`gbSq87;iy<mcMu$XI86_$;!BD&m
zarPq>F-*U$K8F+vp^xI+D%=KwiNkE+X&!`d6*yDZZTt+g-Z%n|?iqGQHY@FjiDG&M
zdsFJ$uzB2XIqVOydU48@w9hAO%}&nWi|+>otEAl#@Xc??uMsUB`e!yl3nr&Go(!+C
zY;C`tVd4oZGmDO8X<P7np_pmMM;LV|Pq7}t17h=xwWcrvJ~!I;pV-P;KC{n++^e98
z``Qs=-V&CIsKmj9BKG`}`ljNw?fHs*@vD7SFdo+Lgt;HZJbX`PbU^y_;Zal3+cV)W
z;mst@!J9Kk-y_}Q|A}w|`QP^@ihILvZ8zwa-X77h0Hn>4KNJ&Am6<u;zKxU+EIm>u
z+#tFje@gp-4$tic`G=BjbIh#XrsbtL1{h;ysvS&~q=B%mc#1cxe)p+UjdF-(ci4&x
z(|8<N8=jQTl5G5Tp$Vk~JN)XnYJzbDelSY7@u2pr{E+7dHW*FDD_3)L50O44rAGo1
zA6V1FNMf;gUSi*&bth7AxxV#9G2{F4Sc-B8sf_82oCV~NhmAk5B8a{}JNqre8`4*=
z&#4ipjEUWSm3s&@WA)52bnaWV&MNfucq})zg-b4f6Bystd)18K4UicM4Nyk}tbDfH
zI;)FFw4wD;JkPl$mYSAwYtDDj<(Gz;q2Sl(jukdM@k6aY=PFiqPOzFh)BXn!y0iMP
zQS^M)Dfvn+i?4*9l94EtUQl&}f|&e%;~7Z=eYnW+AT-TzP39&xG2l`GpN<StTs5~G
zc}g9w-DA*1bfQx(`;GkBM^a&#$LqS$^*oyN+<hclau^CIXxdLmXU-)HWIN9LpRc}A
zu}t8-bSikr{WECp^pkYMleK&5%jR|)*OKjr3ASzVNzIm1p>e-nZ=SYvtl{s<LJn(I
zdS!U$LlP#kea`hNsK%YnwqFk7w6?7OWW8}x(rdiW7jL|jWm$eHV&|e{!Wt!>>`$Ek
zV=;lqSG&b*oMu$6ywpMo?6WL|B+$$r2l2p$1VeF)f#-`h^0vwBqfNiIiH=p2%D67{
zv#RR4S)SE9yQT<+#4sA7I9^NXy3eF>ZEstyK<MKkl3ymo-|-B(j1G-ytD6XC&uyE;
zVxJrt<rq~s5&B#uEAa5~>RM>^&=_B0P#<We`$*0?jq2+EIeWlm<%S*9{oVe3(F613
zvMiimrC!uj6SLtl#KW(>_NC~=?;k~w+Mbht`Nh>=>$}?8^o{Dw^jBsBNQhcu1iNqI
zD^_Cm->}wGsWbmu_x3`P^d%298wZ!Xf{Xz;Jm}{nBQnwgUN1E<Rv^#OkE3m;ur^TJ
zrX*LwT3@!;2w^@)g&cNyn6HYw$C#P5Z{~CpIGIF6g~V0Lpw%~%JwY{SN2@Ovi<#3-
zYQ)}1e1yO_c6<1#?~wQEA|xN=T8X!c4C=9r;2oa(%{BTVNqr8%73p7eiEDE*@yRDz
z{Ixz&*?BO+#!wDosrX9jD4jV<I!9tyAMtqcMVU*j-RgW5_Twy6Qcl3rY37={Rn6pO
z(6yb4k))v1%~qB#yuoq334b5=P`^H?B(6ZsvuCZK*VJc24+&53z7G3Uk!oe+Nf=+v
zPd<H@H%w=0>J#E1#&uD$`HKC$LDO^J+dZ`tdWypfu!$?0nvyeA#Vjjj^XEG72SuLU
z2HKuSDle1da(EIEP6lvT&zh~mNpJc+0e%8!3zSy;!xgf>M(#-U?{rOr#Ejl>{<nv)
z-)i7#?nrpJ%4>J4$9+nn;AQCS4>+NF#7>#9p@~1hXt3d`z;Y7zH>j+;VzUuFoH@)_
zZNqYckmD-)A8ks;iFe^t=Z8v7GEUrjxj7}5aruCbX{6$3Il8hl|5@ixQRLf|`;rj9
zFg<Ay!0oj!@8#5;{KLb(p-xcB)4Hxsct<=V^F2-BGJfXX=AKE;k{Giwsqp1X{n5}h
zWqR3H-KG>`cHBh7GQu;Aj_Ku}__duj$;+w6s}cD3-Z5^C)YN-=u;2KM00Ojoh8CDN
z0p9kE%dZf3x8wan=TErBx9<-tsRIUl^ar1{jifX0`xx>V4O^v^!P}L!TfBHq8!KBz
zN}|ym=f0cPLPM4IFTw;eD=V@5gog9c#}uE|J~P+R<1nl_#-j6H`$$pJhyve5+<g#l
z72)*cRd?>6s}HPp7jX@vuCRO_eu1yqoV*D-r=ME-zxzTCW?r+zN;n-1T8hfvSbC4x
z2lm;URFb<H{~m9OY34yY126_=+h9dT5e1G{u^*(Y6+ShX4WK@VYo`@^E9^q#k=~xy
zgFhk3TF1b6_Di&svywVTif{7wg19X(lZ&wV?iTnWtNpGOx2#TNqG`vWVDO}kFn*X`
z(o3IHo`;^-sTLAv2$?*2M^}x9zqlHx*5Rk)+TaO4kaF}w$PyhjDsAN4m+QkXIha*F
zuNr#s_E7h=C9W86T=H9qRubq<*unL@xKNmMtujP^{VLO&ozH~$v-ZSnK&aYW&;7u+
zcsX|XIr5Y8Zi$0~6R&YxM?WPOjHu_?!PI_iv(I}swDBFb@eO)>cj4AHysF%mr*iR@
z_>e9#ryX{cXNS)VCxOO3Nk3OmaJ=P_zW1|GL4{<R)B#T$xF4H8KI}H$u#>anhPhBB
z!D4v>Q;bGjS}c9nB}r~#H-~PbvVKuFlPlWy=UI4SEeI6(?(Uaj)%eb=ds6S0m_Kn0
zV=~uJU=rf4Mr@CGT(hcbOay;`!x&A4#1hGinxQToO5429`4Pl08}-!ZoqZ!@YW<b`
zKduS$QJ^UD{2caLqm;0N!~3BrC^Dnq{^YNsfC2k21NzJ^NqoJV6twA5md|2F^D?Ak
zW(vl8xW#zfGY@-R^*;u=?tv|Pdz+0bbUEvU<6xR|8~HV&re$uPzkgaPw)194Gn3>s
zD~bjiCs$V_hhdN{Vkv<l{VU2ZlJ6>rJFjlFbV$KZgr=@O%;r}tS<D?j;VVIK(zqY`
zE{-ty^1~hPRm3K-%)HcXczA^Rj)*_sCw6Cp#LsrUjq_hDxf}ksY?#xY|9!#e7j=t`
zqmnz&?6n(3a)L{HA9Fe%!(-|D=}l5^?dKRrPT2Oa9LGbX@c+Pq%*j4n?{Hv_su|r9
zM-vyC3;z=tDg|R2C4Yf_(VkOKa=Vmft6Qm*j=hqD8K3X>?}hJS0?YBVwjJb>PQ-IQ
zopRbWMZ|HYxmZROc!ucpQW@dfs^JpTc&up4lr*N$s#O*ii;~ixj+dvGCec!xJ#@d)
zuINY}hR2l-pNn;dW`AE+t4x6re(UAAb0V2o!O1JCgDkH}&95`e#ur<j^lpUp;?0jj
z#xIM#&gA|cGOrJ4A~##smDYUS3vyIz6fSn;dL15oxad>l(|AQTO<MlCS3@ewL(~`J
znDw;T|Flb&gq$=G-HDrD6yrELFmNErG_@9<0AtGhO5|BGs-gAKdfm3QVa^Q$7^Cyq
zS%hs@HLl<r9nZ(1OZMn60eJmUvK+3w3PT39j2hO4u~GlYt5?C@#(w}wNJ!=vb6-%p
z^k4zKF|X#wgRxcNH1XG+p)V`mQYQ&|V-d?J@Hi|brdY>J$-uvFkJg^jf(npG#zNva
z;q=zM(b;m40!SIAF#SD}X;P@E$im9q)LU!Y2PK^inSaL|U>6zu(gdZ4KMVEfW9kpi
zHn<zVNmn<T*9rB1<Z&=(TuP`*;p=MmXlQ*|-r2`;Y1&uJG+?kC!8jUjy4<~4(Kh#N
zc$JdqOLZNnzD=*hFp)Q#7OFUdi=x{-k`K_xU5j_^V3wzl%Y~DhE`MZb1%CF$@$e&^
z*~pOCAwKhT8V<ux^{ck>;}@{k$H!q5qL73NPBk}8BVW-Xx3%81B>ZcP(C$-K(JLW8
z$+_{#bo|MG34q{_+kdxA5tKWR1&ylCeNak~d$u;xt1cwY7d{<&DBU34bM+?aNo(;5
zzgzv@s}vfsuutzE!;96Lql=rE(dnC^@2>VIqh8xt)PhVHQwhCaL>EXES*uG7BXK8+
zJF?bp2j}_)NKqyS65>M}@oeuaT4uRQ><1iKBxAGbdmjV}Ij=p$qm`taVij=5;Viwz
zz8|J*SG4<>qTo+Tg{T}Ur?&f`@9X!k=`WzycZTSE_{{Zk9`V^;5G>`MP{N{=Q=~f+
zgVdbQJzQ0|$E}ci6hJ`a_b+c31vxt_s=kqhq}eT={`RFjWTHsMd~^>@+(O|p(F&Xn
zyNxr;9iQ`8`n7o+4vlV-KV4AdGq`0H!@^WaqLwoahDoR6FhYck&sUQtm+Gw(7F<hO
zsM38Ac#W5XTCXoLlFM8YY2R=$`mt5ex$nOU#X9c!S-?0F(duArr24YDop1x^^dn0D
zjOc!QAplgp#5Sq4Ll`vf9%n2KcvEodeJpTWV|*9wX30r4*+lHzKkpB+_n#|IE8SGg
z=nLn3sEf3pb;0%Uudze#M>30gQMg>37I>Y>|2ud7H)#$*tgB7)J4Z^tk0@I>yMQsz
z$<>Zo-Ey0!|3M|k+qRgULLZHcM2?4>o1dy+?C8g;QGTzP>+2BcM$7-<0*rW-#E_uX
zi%O%A5{-B}7N9%Xri_=ua^bZn)bnjo%^n<}1R3zjLeXwkQoI*$tB#uXhzpIG<aG#j
z-PZ7;LV2k7HPll@N-Ig(mN%Fe!^xB$;|oUcVSw<SD>2DP+~LmUV<GQ{Fql=MfOLA?
zf_VU91`B1G`17BG`RhBFQK@W|97k!n)`QxUzeB3}MaoL7cr>|prQ|FvGqhf}IK%`%
zQtaj~Fi}vjOWSB|rw^D$NM~{9sxX*SY?drG`zlO~l21KzQ<j(L)FXdDk2O!7Q~mte
zJdK3B*X}eQh0)!KiZrW~H!&@=tArzd%GxW)!`1Cidx$qKJNJy=Ke9}+<;AsV*>D73
z6XBQL-BGU(l<4I{e{uT$0<Mnrd_UsGxT4Q*@BQ@&^0oGtd2~u|J&}lzzW3biqW8A!
zAndg9xMDaVb_cLFK8LV3E>`$P>djTt?s>pXNk+zTHm0Sy?R*aQUtG=2`xK7Y3~-Ru
z2)r?vG%nJc2yr$@MaJI;eTp&HPa<3G_olxlqltWxMih*nK_Rf$UdD`_p@~+!YR!ZS
zq7stD!A>wQO#IoP1mA;a@;Sru9qkiQjVK&+UeV0LyQN-uxlGS0%)(K%XCdRBeDu(N
zRrUPqyMM8v)a}wg`z5l{)-}c?dMK}lKY%;VuzPXaM7jvYH6B?zeEmw=J@HD(eg=ZS
z)WyLqZ7;UpB3Dlc(X_h=uwblYYRz{&pveq7W;SYETsqp{1v2H!PVYb$(--C6atXJq
zdJe0U$TQ0u0e+Hti?@L;dHbC`eA_Tg)W?}Sk0_)Pjv83LXrO)A?#ZL!%oADdjrTw^
zu_EesYUxjR`somLZb(RT+At#z&zEe@SX&XJqi&s$_0DYWT%uvr1yPdWn<^da8QwqK
zCJrpej?-_CEiN&-ia^M1iR1<T-R$bDM&O!w8=jJ(c;nUDS(DTKfs6SZ{ISt@+>Cb=
zJSZak^NcGPO9Ga*z2Ano76gy4sjg4b9b0YY<XriBaO?$gXZZWcGLw8U$H%5-1FX1O
zNF?hKPuSu%Wgg*>n$vZaSL}5pZdnV>T|8ssI1-t<ZJcS-srPc`L_Wn0inntKE}c|1
zr6N=@L*vl&UyGpcdH4J%vov?RT{--(QIY%u8Ru%RL+{R@pT&4K2xbxmV_W&&YE6S<
z+MiFy0hBd5<?G$D0ma18xwR*f81;$z65li~_qg?EFi_4;hxfYmxP<ZJ(RcER>QhZ{
zu-D}@6b7ZF^SF~(MO__+gl%7um(<%m_MqG5tmMGRFUp}X2-7VqYQg}2jQ)Oum>ku>
z?_Zin5M;&fkl*JJ6}3B&TVF0wpc@`)R?K*}K&OFsefy)cZP!73lvMQ0-jgCBq|3Tn
zXxln!fcSI^|C+s0|8#|>e5Fq^NIP-9nS*vNVyR3^&AG0oAwPkd;%`mF{tpUlw1bmU
za|JAD)%V4#;*_=5@fEs37vAWXdk7nokUVW;Z={i+_WzMk#h=++PvjjGwKyr7-WjJi
zIk@2!|F(Xs;*GOEDfC&iO4GLP?B$Bhb7jsuPs-}EX34tAt6uAP7P7|I{F;;^llo3s
z<KsRpAvMR99MRwKh>!QvrR(mHN71)uzf!JvzN^d!j-LoFX^eY1oXQx>Sxg-g@>zS)
z<4GR43SCj$N*HD-TYB)TbS~!i*E|^`mC3*s*}o~?*uR`$eC>impy<~A4>nkH8GUc!
zQ#S31tCqU7$k7ArMz0kLtIW^t0i4G;BqS@dn}=DAiQ_{BR-+dJ%s6OmRstpMQFLxZ
zzObeSyYsx?Y!CWYV(7cS5qsIxefn(eNGYH4$t>i-hnTUU_XKm~cwu_Uc1P5PVKYA0
z+tLlOT2$`}%NnyuLDU_|g%_2U=o3i06T}6r5RNY{omlaRNJMt0&m@n#Jqyo<p1G<z
z9$pGf9ZTGqXc0FzDsrO~;kp*nt?{~3Dse_i<9Q+JSS`nEKDFI~7c)Swz$tn3DD*yF
z{?-`gLihMd*gy9-)P5=X8u<oRkmqd#H3Q#2iw)J_UT`;s^Ia6$yUw-HrD9;L4=Kh%
ziV3|Te2aZvw*4z+MhED6dQ#+C0|I%Z4GK~wnlBpWmBSOR?PX4?18w(exiZ4cr7cS#
z5<bbB!|KC(Kf9Yxl~Gz*UGyVh&FB0t?z?>;vJPLbl@eYO{jwdE%b93BAE8Og%Gs!>
z{o|o$?)!YmN%=g-f%-_8|9p4(<sZg0@qC!4ov)U0Ner9s3CYzwJxZ&CZ%e$TjFHJl
zr*3kA{NX!`NyAt8cOt^crsIl&J0DgGPGnb9u`|aHmr$+h_((KGbPeGwm{Cu<kfXTB
zVVE@X!o&|saChI(uDU3>O^SSJz^{kzc86qqF>sJRul{nR+a{iOubMyjvNGIZ?daNm
zU8C03oIA}8dQM^$N2y-+F2$k_!`!M`WoBZf2YUxGm|%ApNUuCY7Lxa^5j$D(j5%6P
zIH!}lk^G>SxS-yvq#++xn!ii)_v{?e%%LJbJssNlQ=O^E-pJ_h0rRm{l?p;z;<0)n
zUm|w^<=~RrEh1v;xmwi+y(t?*EK~zY^s@Drd4AB4;iZ}VE6vtO?rZ+Y6dEa=XFN8D
zzWh-Q1MBqE)*qk!Xsw~Cg-mWCtHGO!PjuqfYW%e$rJz_F*tsc9k7Q6Gmg5*s!MxjT
znCMQelf8FQRVAfR#cjQ|yT#9vXUx+5v~|_Oht}jDzO$4vxB7fkPncR9VNqNv^Ztd{
zA5Aw@NW;PrOGd-|=W>t`pg}#~k<<0_5Q+D^ZA9(Xl?;jb9+qcqbv5v$(P7y4=fa2i
zmA1!O6&Lk38l3fF%hz%Fd-6w%h{W&xIw)ZPguu+(rvCR@X#c&I7vQy&X|q>RGZvy>
zE6=l`LWmNX1h>u8I1R$=r;?C9^dXj6qF+favkG^{tt`HSnN-1Hw0f!iD9Mes8fax;
zdW~T<hVStQ+MYr`sBDEEfr3<!bqLx;BZ$3dwk;<dLJn8Igwq@H%4x!Msmi|95rQN6
zzN|49JC!rS;#)xyCVt5v9jbwQF7z|*MjvG3(POlFl-g2PayoATNk$Qr=Oi`D7Bj^Z
z;ATT>z3hBL>3K+cmnvdN%uQbLUHt21PkJeVOK9x+{D(ik5;Y92n}Gp*9zXe)d<3@Y
zBP8D;PalaN?Tmmf&K4bNiK?B|JyvpX64}z+;a%s?E$s>Cd{?c$P5{)_Oi^l5Zwz+>
z+G0rmmOY~Zr;#;)<FT|jbG+5=h0ri<{vcr{j8-_r_3B{W<H+|YjJ~rzH;jgG=&+0R
zwd9=~lGj#ikx#+3R!o^Gm3t*;#S0UXTGt`#22!r{Y$KDRY#9yPGN|5WXH&PLmhqco
z5FR7(SV`MfBXhs}<OW@i-OR(_^I7p-I`KB%_rI#3)gLN~zGcm@LTiNML$@Ix71F)A
z-nBWHHNK_1n30SM8Dkl*=J$FpXm|~>vg2Q2?)&c-%TM#tGqOyTy5LqXeCY4O5h*1z
zTcAg`If-`fZz_gLz+HI@`7zOx?VBz33XWd2J!!>41Q?&9_G8V9Z}ymyHodi?l&-yt
zB@8rO8P-#xoAKP*%kq5E)j|IC8Zw3_cGUL-r4@12BH1a4nB)99x~n)4N1$a#oZscK
zwfkj&cg|_*9E4eDXN5OrIh7VL_3AE>O8$xL;!Hei<r53*Z;sPjBl=qXJDkiNRsz<3
zSo=MX&xuFFx-UkiU_9aR#ZP=M_e{Rm3Y+V#DpQv&LSRcfnF<Go2K3!$BQcHVb*gN(
z)6sEmcqq=@&8a2*D(q><o;B!#3jgbdl8RPapYh(?Q+ApCJa$6z(=O{9TgEMvw5^$_
zyJ4bhPdp6Dqp{^<8rVO5Y&t9s<=~WSkO(|9L=SM2%pvYNl6b)^iqd!<JDBFze7Sn7
zcDu~LZM-uXwWfiL5Qmit5>@O<M^L_C<MZZ&{&`!O4%0I_)x)gO7>AH?$vN4)FcyDM
zwu)R0rC+Cx&Z(*gR(E++iuk+f$<XRjZ;O9utj|jE#WV|*J!Ul;Y)$*Z?h_!QrvH`l
zj1?!rb`}M7-;Pes35AW;9Z$*d;@&5Y>II9-;-?+k4wax!*FupjaVB)zunyDP)feY;
zcK*@UwwKuy^|gREYec;X0+oX&wq$0~(IxnA9Kygt*xr=nlocj3pJ1qmduD~7{V5dt
zr%Q5uPy3E>jN|3*LKe4<1YVnZDgj9QC@E2Sv1B;ocp{j<QH6uI(wfJIqP>P$Ww9jR
zAAgF#UajJ%$|CfH+`=~e*ZM8<PX`mj2$nn|m$bFK>36f&`RPw|o|S#pnTotqqh2f8
zY~ey=qwA_Q>+1dL#RJ!k<(;6A%2#Dko?*+-T$hzH?dpyE(psD=pDPUPd^=YJzgn$l
z(8q$=@mxFCMR_{8VUwnB4>)A3Ou)N)_flU&!y;i#h!OyE5~+;X_ZG<#uvb0yl^zVJ
z;<&E9oqfhUKmsj!2Q`e#%2KQ4C~XXo9D2S8mB?XJb$bna>~@xDu3oh0M37SKb2qZa
z=XQwp)baBI^cT%%CXHi`97LZj1LrW50d@+Q610i<s_NR+u-m~@D!;c0Q4(BW$A|6@
z{w6iN0i928&{9HRYF?c8Bts>(!n8jL<w3?>I`8M%*HF?>wq1160#7<%RbDrNChfG)
z!~wf~iD~`_-ARRj{O5Z$5O6lIMoK7l=^V{Z<easrCf135ntl00w_~KM8(<EjZNI)I
zM)6x5<>`2ct2gN)Y|=5);Iv3XpuSN<>M-vbO!j66XJZ822_iUZaEv%nQP(Tl|9Hzx
z=38H*H{X~0lD&K4oU`588(S7~0KI(ofP*0Hz_;p1rF=N`+LS4iTzE2)%IK-uG&XH@
zdbPc3R}}^SXK~s0qcaY?YHT4pyW&r?4U*AV`{nlQP+&&ZM!WBA&`=sZcHCkelju54
zE?+txda@-6g)a8t?y!0|JV7_TYc*1TvdmUu(YbK#nJFG8#iwaBAK~`Qx(iNyi6G2n
zvZT*CdkTOQ+;NA0DLuw*L}?n*RxPK>te0^xP6C+gwu_YbH_@G9-fEJO{WMv&C@hpy
zKIhA>$9ksdgK_-rnjPcVZ^VR;CHb*XI;$c_@hiTv>0NPgR9dtSV=}0_anw2_Ey1X>
zx_Dbv>lLA;Lgm35R0B~uAxTN9Il{>}Nv=dcI>XstX!YC!iCE0hOKE5#iAp(yBb|hA
zZxL=jevrXY9L3Wyq`O#kpKwGx8L;;UDhW5}|7eLOQ=<-~1aqmfQF>!nu|oagD7x%A
z-D575<f}WR<&MlMZQw#hS-dIkC)Z-0qBRA(9>ht4joi!Eu@o}>ZKWbn`pm2LC@nSl
zrM~t5>df+tf0_OlWK>2~^~6w%ZPX${6(@*TZD(^zUM#aOf?9BZig`}$9xB9>kYMDa
zI(S&`)X90Jj{WY<jF4`qQf`wAjIL!c;=D4@T}x{3{kzuP77z60&!18J3S`k#TAWZO
z^_xj~l){*`riH+GSIsjohz=j(A-CH&>BxyAKF-FPuzT3I+(6g`W{30W_3xMwbdr%?
zea2Kjy3{doT`AY`29E6fbTEkq;Y7Ic60P1xpL`@Pz8b>mY;t}Xww-D-O7;{Ii<`tf
zlsuGozZK0;T;wqr{vxy4Q}IpoTwDr0dzIRu#<cV0Zyz3HG7b1V6`*L!&UZ}sJqd}_
zwwLRIC*#BU6}t>yOzvhw#G5?xSN|15xCDQ@pwIdut*QG_#BiU=eD@)`nDip;C}(R%
zX<gXIim&3!%wq1Wzz$d$pdlRjKSX_HR8<YrHXx1CA<`uv-Q6kOT>?r;cN|K(JEXh2
zyFt3UyAL4U-}ct${np~gkv}Zw%$}JmW_DXc!1vO_9`vIaIl*~->4V0PHWv21M%Z#`
zxZTqXMCW@vOg69(HeEl<Z9X}T!l6Cy^qw!vZN8Pbb27)3Hiy)0AktE{)SX5;_y~ky
zg;+Cr&jay55j)oS*9EjgUUCHLL|;W<x{{!?e$%`M@d~e$Act1io0k-^(eO%98v|IN
zgrl<gS7+(Xq&`5Rt5Nh1sqI<OsQDfBsb{)Q2QqQFq4x}=j{*Pv(EhqJ!JZ?4SWPUd
zG3B~qBk#}yPDVjC#!v45*SGzQQT{@A(Q2dR{`Z-Lu*RxK>4q<Hopf7K;vf6R{m1Th
z$P*ga|7dg!TsTn8DO#)dX5Zm{P8`1|Fp3%V7}t82Q(E7`SO9yM8V>AJMIsi{v)`)3
zEGLf&MKA$%FXu5`A~TLb@~XWOCGopPa6<Ek0{SYxCW^`&@zr}#Vg!BOADol>5iZEm
z+SKZ%@*gwZ_e;fQEeyRhWaj6`9jSES(tw9(Sw>$_y-U*e*59rprL$#$cTg)*P@W?5
z*hv?1RT?|%lnva`-{YsX)5P8Yk?wK^R?be#SUoby)tFfbO8UClIcbz+CMuixbdpoZ
zf2}No&1RHs{CTXt)P>qSu?<c3cs;bL3-q4v+K`Yh4X?Dh98ay4b^C=5t|MgYLVeot
z(ZyNbdI{?AZ`h(3)gI{oeAF~uvDp=eJO}xFA9Rr6)RH2zA<j|~AEu?!<MzNb5f?`~
zg#~7vxE62hK`t_ul7rRax^`IWR@0nG0CRgiF*q9-fA`R;34ua?;A%3=Sg3#*0&F%P
zJj$VuH=0uvYX%?Dm}AKw@zX<#D7JFwH;2h>cp?1@zn|~>hR&6D@8Zp+)!Z8@7fjln
zmuNg~Jt{gm?bm+CQe`#j(|*CiTfapu=B6Kw4XnvXpd%7$t!3YSxft9o<a{)3wrYWV
zvf=jp%Sly7eS!XujTSD|UHaVsv6cdQGG|2OLnT3=`>pfdA9>++14HV|XL}=nKfjEy
zNAm%{l!#d$$x5}n)Ipp}mbgK?8R#+HU|)DWgnM@UlC*rUcnF5}9CZ*7uB|D8e7!y%
z2&*B$|IoED0Z+f)x`d3GC`jI92hB3<dS(fN%A@tNqU2o*)!<O;Tw%EWu;=skV($$^
zKlQx@sgKu>V^d^t2=VOLMbYMQ&2MN2Loz;_SMRRuD#&ata^W8E=96F8ZRjktGdkds
zzM(T#XnV;k)>jOTC}oM7xtG5ZN14jf6NJB`iWsP@@Y*Ar)Gh60EQUQ3+TEyNQmaQ)
z7HjgV2u_^Iv^^ay)V6&W5W(vcyqV*A<#1E=aM~bb*oS*-&2|12Q#Mz2_+=0nefj=>
zn|Vw2pHt4zrl&qU19KyG(QG-{Sxria+F#UnGL(M2&Fy{8Hembv5!JmJB%UQHzZ)Vl
zWUBI+^p|~?oCA1SyQ&Z-(F%V4>bXK+AVlJ3Cq`{yWPJ0hrJ56;1H(_YT8f|H=vBOa
zQQag8R2oUHu&Ev9F!k1p4rBXtAH1*#Dm<_WKpDc5cU@+SpGx$@9nTt(EUX`>rOfT*
z(F9Ts8?SBwAByoxhv^gXP{8zDh!<?<ZT>dSU+9KJ@K+)4-43wCV+h>1(fNUR9nvE1
zq2|Zez|NR6aSDHxt??G175tt2M`-eaFJA1+5ns3Bf#F-kkq@<Ki0=~x^<OiA-@_V)
z@{6ZvuiV-42v38`maoW0#q6asQ!lb#p(ix7e`N4s%85PgtnuqS{=8H~XZZcd<2XZC
zRU2CaIv?v%(%WeaqDu|M$WJdtZtkex<G!z(jAz&9gj$WTxwU<xGTMBR|E|XQqs{Bb
zecwaz%ws%FX6;3ZOv=UklX;&5+lu<;Wkas{oWwj4T(zq+aVs2KLPGR1;+Ds;Wzsh&
zq;+%iS^2F{3`G1fJFO-WcRK+6^nf50=+30o1cOk*Yogs3UuL@aM50os?+X}00opTF
zLLMnl!?v_>PaBmc{UWLUSzp-Ww{f#o1{i#}%15{Vp9lc2x$&1hgooG&py8;8Sb*`_
zT?-#&FP9R2ZLSdQXt8MEb`+zdSsXp_?;ETUS!m3SJr?>ci45hYa6YG0DX%U#f354q
z6Lp@s;eq}h4Ry+~i~DKGmB`I9Vt%@t27c*-#rXyp$L8q@cY7s3e89$VgSOsM(<ErI
zUeEHu;v^8Pr3J=koN9#w+50=_)6OSKEGsJ`96VIRqLS6ML&ed*6nsd23)VLNh~U}o
zyDm2t?_K_MJa#UX`W>A;A?PwHY+2f0xly|J4V|RzX!GS`3sftd0croCE5ip1^9c=I
z|3qX0AEkZZtxu*~ROWIo5EMBK28F*pIzJ6g#$@KYF=>srzyP3%vGPn^L3!Kt`dX)E
zC!`{?`uZvCF){2!3@`>vIW8k@U;vW3iM1Q_-)VOb;xDlB#VcRYfHFXVu5)XVWUmhT
z2-QUkdh7SD$uL%1-X)8Li_Jd-Fx$<j;VfY>TmKRhbk@TYHfR1a8*7_QhbtUMbZ@CO
zC@whv*f_b>zHkz5r$=*IN03&&?C`{#KQGFHHlwDp0Uqcvv(x9ac|W|AGC8|uSYXu9
zYyXBc%Fp^ucI$UMZx_!-`Xt8*GErMyL7eg7oem-+2CO7kp(`@<g<LXE6wNNa)DiMS
ze*Hl}Ep7cSFuGNH^pL$gy$-i>+rF2oBgoNa3+*6{(O3r>Oz#dSlsA3(bh(KQ(#mTc
z=4(CUzMj(67k(@i203E=JT||W%IcBC6cmL!nb~%vd_fZ1t}txe@*oZ^w0MISH&-Tj
zJQtZ&`;8j*_8C!1c6WZ!-W!Xd=Qqc*b&#>1W|ieD5ny*oDql7MY(>C4^N*nNWBXH#
zqWs6+sas(}2*Bj_SX^06?fGh+ahNeQV7vKP?Tm>7a8*C*fRR~0n6{L!WWup%Vvgj~
zdr5QBq0fu_e4_WhKgY1N=M2p(ly{OCUY7}6ZsHy4K%kUQS<lw$q=rARh?^6tSDnBO
z{)?}RB!Goaz*$Ooa_|1Cx0Rgi39+dpMz6#?;Atcvk8ZRPTpg;2Ij-0^hJ>JkycU`V
z$gTZ7>k#=Q9-+Mxm3!jfo4zt|>py-aMj~-zuXK3S{~F)ic5)(z8A&8Le<}v?>ioYR
zCH(!p&mVgjt<4;r#XXDQ8jezhozyn{-Z-n`fmKTo`FL@&_xqG2QAbzY4<#i4&5*2a
zY-cM5-~142pwc*Zptf=Cd9>_Jh)c+hQ(b5couzX8(5koLO6;axYidvSQ~PboCOcnR
zwQr}dhM=Yyg6HK-4LmbjeCL~%o2_dcOJOn1U_K=TbcKijGChYT9GD8au-!vm^k1D{
z#N+UeccA;-qOU&Ha33ft9-#juW+jPXCHKMOO#U1LYWICiAo3|c(Xh_RK=hon>DZuh
zW`Ng`_u*36aJyK4K-;;|=J0Rvji!485m%ivNJlrNn>xZLw|eE5h~E?D$3dyO*Yjpg
zgmVjKD3AyWqL^m5vatw_0iQPvn8N*qqXY*JkP7)O_#_SA=3wpbS`CL}RXfsXHF)A1
z_Sx=jhycCp8(_dSJUs45SG{t51Wa2}Z}X0wEC9?DJ8c*7AE-x#^8U|8P@UPdITUV<
z@r&b0yX#96ulg4rT6eSVD9`cv<j!ngWC%`v7g)SRC+0G~K{6J)%;PsuP|b7m(@yWg
zKc#si2O;L`JNsMN>-9*CdggkApHU02tDsMoEp-V-@9ulrI9Yf@h<kF3Tnx{KU53AE
zqek|5Z0e;bUtLz}s17G9mqgQA2^q^@1w8tBQ?>`!Q!UO3Wwd+KE5ea&w2OW7J%Mq!
zEIb(fd@6bFhB&rKsP4VsI$LL<Fw9A!73(Yu+ls);xosJa?vkpwXlQ@Mc66emxci=T
zees>@*RL8&OMXBx>*`hcqMU)0ufSdn$41!!M<E6<f+;O@G!exS!xMIEbdoY}jS9U?
z2>C`ChS#s;smip|ZC^vW9u+_j<qoS45Pu8`9X9gfe*?!H`4?-^Dp)nzZQJ=kcRToU
zgorS(2x3e{$<jH9XT9kJM(LrD&<Q1NWx!V0`XwLQp^ZX{7!hw~^c!tvPZ=Z_#R10Z
zf*qH`Qzx|+oQ<#;fwf<!kEhGa;}lnDq1RfUL~&qRI>11<98M+oHnr=8Y@iBsEFMIq
zA;+3URfgP5KSm8n>x}HO|5bcSqO7SMw(EMf@2WD0-p4D8Xi!6N9Mfvc_~S1@K^zGd
znT5&yJ;egL!^F3zAFu=?$!|Zaz4CSo=*mZ;F7(-DkF+sJ4y~hPo;XXr${C+okVa@A
zCn?^PKY%+by*}`F23Iz$CnP3hmXyIT5b*n63=WbX+ksKpf`4aGD%u}OB!$fyw6faU
zas^@0{4rervG9at@c9BJ$=%86LuJ72MxpMBwRn=~bme*{R1T5x$FT0f-TrqT754bM
zFM<?>SFxf(-KiH8*KB!X*}Ac+_G)QWEqN|(k0?SKChYt-6KQ?Fj+VKl8`s;FLtk~;
zGz_9PJ|q9E{XSO2=V&A@6?p1LTD3YyRmDr5&vQd=I*byHL!q%U6=ZTt)a~<v5tMy4
zp-7%-)3rn|;f=u%r;^%wOxhl4mD|h^Vqw_feDv@E`WYEq>a(t>1i4DCB#07p0f4s?
z;&5+zt<JKT4Mk}Bh+HS%K$z@VR(bl&l<Uzx)Q<S-Zl_f`((|-m%TQ@XU%U*i;2$;#
z5Mz4f0N!7%wjujWQlS6iM^e~ychT@1E)n+sdq=?5Nlzg+i1K6TGNa-Y-~jsTF%jBs
zUhh6A!eL^cNR*JbH|eW;jfg28883O58CT%COL17ed2@FPIHmn%sRjR=On&kD{(YW1
z8!v`rvAqL{t1-QuDQCl_e`5r5%SfYK_@~K;It*vuK|x?BD^rCGOz7!r|H)2+Z!lNJ
zWiLp&yvWI6ri?HSfbd4{EQ`W2o!`>)#&P1EwvZyB9C;zLC|v^~w`gUR1zP)S%0TSg
z+qHWSqN5U;Dyz>0ig3D-j1B&*&OMHM=YCh-5IE=)eKm=-$jw!-4~7fwZpLh`&bH4w
z)0^vJYBng8EJECntM_9uQ9(JLqRsAfjb(1~7Ywu=PL1kXLT0czeipB3yR!n$%khaI
zVYA2ZG=I`8gcr|GP9TAEdPS-haqg$K!C~V~*UVP0K0e*F4IK!nkS&eHwFvcxNJC=}
z{2CY<Cf}j1^-S|jIHNq>BwF*qMYYmK#CIjmnVz%AZ;6)uFKPmRADB7)X~6rt`oiq)
zUzdFtgjJT{@cBoV{-Nd_oc~CJUr<K6>cbtv=ieZx9e#I)^Ob$G{nqg0U`Fdwqlw{0
z8pedUy0@@_TdLm*fAKzNV$dPDIX^~s6wR>yf=uhvc&InHEq+28;T{h)Gv{f>-&yxA
z#@O;F9bFy|abY=?gfKO46NfAGHqd>t%Zs6oo3YL8gZ5gc{Fr>c<`w-YzsC(B<5-=S
z=dBC~cq0702zZY%CPj1|-IGryR|Y<_i~7qR-*sCXyJy}sxvF?Ek}sB%`G6pouHUoL
z^~W{KKDs$UI}8^^Tjd&}jFo|!gg4w~nuC7ltoN84jG(<w03*&wU=D;<7T3Icj3gX5
zU(om&y^l>}i>>;`IcIC+88FX;7P)}N>bLS7O?7VRXPnw_O;7{^2BWuKuUJ{s+Mao+
ziUIqQ_Y%gs*!|+bl%qRhC-9UX%R7_&d&;Z-^&9U$Rt{~5r>yy?-}zQMKD7-^JwIY*
zgd-ajOEFQ6mh2!Z$#lgg7Ly)F4TZl~qp<+=$s~F_Ud!nd>(#RN(y=MO_)o__Y=jlL
zwX@jQ$t7O>sd*s@KZ378`*O8ZE5B3>K<bp9_XqTEkt4}<+u)qe!~j#}9D{agT7l8@
zJ0cvfH3b3(Ba6527Ui#`Kj$pdTNqxF2f8b2Z~OOB<$&6WctD;({>V##Gx1}qX)1gC
z6!yJQST%Bx%SNw<p;(KtjIDlekvdo}N6P&`lv?|3!;|Yt;P(^Ob5c1=haMr&`m~c!
zURvbcfJ1{=XnF&i%h!n6u_7w$o?@|6z$-yM7Li+42O0~OeV6%gl}3f<hEKMe5*4Jn
z`@IBECP(qsBag;t81IgrlRglQ<P;1RnJ)U?APJ<*Ce^?3f>$)FsqO%lH*WJ%3I2NK
z{6vNS^UP@yuhfF3)gV1nlj+e_>NnwK(%WMxy0jMuML$UVHpJwHXu*D18gs(zyN?f-
z348*`sOM1{-Zzj0jJ+ot4&OrT7pNoKMkRP-^}_9Q#+n86nIUz}D)_2a!ntoFxGW<&
zu|xYN7N@*h2oJ-xI3wYl&%_+XaM|gP{q*5hlO;6EF|Fo=P)^+gVyw#TY%H%?!A<Z7
zZt5aYk*ISl0q&fGaEI--#`KvcKm!7#!Qjyd)Kk8<IpMat=Q+~^JX%h02=`k!V;2@V
z$I~BcFK3WN%R}$V#jhl9pBb=gDvNX8NXVs2-DfJ01k0xj0*1pJ2V)fRp$6f;A-j52
zo!N+lOHaJ`vV9|i^)^YFu@kO}_Hw+7>Jg%lQh|pGD!erSC!_(apcgmYKL;#H^tlx+
zfRC#o8qFT_VIju5@0T-<KAI0{&!*qSQTr@6irc6tWKN1}Dh>wV5F+F;#!DLf<wop(
zCSy)qt0|wLw|$PZoAV4|;%BU&&pak=CG<aRv*R`)O$cSz3Pqeh&cxfNLG*@+hUQMe
zyZD{uc}2jFU4_h#a_UK_iuHA&(xd8QREu(R#G={CGlqOZ|EkWcAg-e&$(!sJ`s~nj
z=(Q)hkFwiVGBS{9n7$4fWRT>W9jZ=kmziPZP+P8*FHO%C)PBn-tu6s|7PJTPu55?Y
z%RoyyT&ANOT50i)&j^MZ@-)c>Ig>8c1-d?6&Mfibu3e~OTtEtn-n$3Tytt1OaNdwq
z_I4MGS#r9$LA(*^Nh-sX#TPmqJj-z@MInpd7x`=(kpNA>COz4_n*;0^{qO;G_)6uL
zaip`&hE@m;yLQChL$C$UslWERdXrKkKydt7kmQ!V{R^B)(EbAFJuVK*brtAL9Pg~|
z{6r2?QA|4SPwre4F58;Q0lxj12AY@#5F5S8H5#*PAu-w6fGu*5))jR^SBR&~o3IiS
zwfD#A%PvvUe4#3BzQ#%Wl%JtICJOw)5XL6k>pMsS689TLZJEod79`@zOz1|NQ@fSx
zU-WOo^UJZGCZ@-8vRg6n5*e!6oC<1nE`}~9WlbtFevm{Q^S3zeT&rSi^OC|`Ngl39
zgu&rwn`iAe6WJ3{7X7NdakWWuk2c*h6vn6Ke&Qoj_`s(G;mm*obBk`Xc3?KO+OG9%
zpO@ylJ121a@QFbrAaT9>k&q&Q3@rVuF=H?B?W!pSL<&PazFLo?!ypY!!=p7RF#JcN
zBNXsnid`4+cw!8oVW`ef_yvO&H(Me62NLEMzj^a`2BRW%!A+y4@62OJF$<7W+`pXx
z<$zze!Rruw_&jgM_1B*W{~7T=g4dYP{!%psrV|CCiL>m4z?O`oI>p{b+#>5uB{_am
z9jc<#m+yv9x@Dt(NFL4KB$+%F6e?BtU`PDfqYl*f(c4{SSFi&3(`M+FDU8o(B05g{
zK9ks(bDPOHmO&}~e8lNJ;ReoR+%S0*fcyD7n&-{NSncCRkGw!608emAHIaEjR{10#
zY3U?q6c>I}Z9cr1O76L(Q1%zdZG)*?mzv+xB<Evu!#F6x$ACOn#tZCWD6+|c6BfS0
z2g9O;FRtfHXxq{eh&pgD+Ol(MH=KDJyyQ6}5Bp<+id!cf2&0w12@RQ~xTpl<2nfpK
zZcxJ-1h^)TtV~AtCvFQibk>qO9U1D+5-2n#`5(z9Eit9~9~9iToO<)e3>xjEd-Zci
zP^%QyYSApU1pvhW3l`<++tS+XpUs|m;P%|h+zk9rlxHsTYyBh=2p(XEIU}vy>mM0x
z`gc^lOmZC7YKQ(Maq7H@XPdPgN@B|^ta_VWU>7YO6U>axP6ZW;$PKZvvq(Z~Z6U5{
zTTU&70Lk29_-4M)S@)-*{Y=soRP!^7lpxCB?`ChX+1D+JxMR{L63iC+1+&Q2`DT{Q
z8Su~ClQ|&{QAc$fI~e-Rx-4wKR=Yjk7Upo`(T?&MiQi)}rv1Z(b}!e_Y0p9K7fwrT
zf$golNbAU@C%2m=K@7sd%Ucqn*g0YO8wt|m4v3ZE&-A9k)++9zr}iL~4MR!u^=0K&
zcqf+Xm6rOLIRWSX;8?5G=a^ii11X_6`aL*NccTnM52WdvFPAGLcGwTMH7b6DGiaPp
zZB1hd@M`r9qrsAZLP4&;{Tu&CZUs_N`F+_!9005WhU$@kGGV0f$>-00+~VBPamyF1
zcwj&6@LWI3_$1z8^`#VOV3b@ue@*T1pOOA1Z@S&|jcj7*uLfBma+b-SGc1DV7z@m1
z`WSyJXNg7%(!n!#2F3u1fy(N(JYaK|OBNv3Vs5C=ba|Nu?s1FiU{4RW-%PurC3~Vw
zS~gKnyo2OT(*V0rErm4`SLg_h{O;xA*qSEX&REXhm7aLq;>YLq{M4vHqQ|`uNty1B
zTd`bCnAayJ{=s?pcaD0vBa7Tx?AUYN)N~`<?L9fE+nwqLs2|F$-iC~_DN5^3jxO_&
zdUf>#$*N>c`H507Cf9nr^`(h2U8KZ|9+GJVy<^lhN}S7GQ`l@duNvk{C!)-*cs-3*
zhaHxCS#6W);eI^XQ)q+Q9#@l7xV`<{492AVI|Boko6rLY;w0h4b1T3%$B(Xt3n)MP
z|0zFX^Vwf7&kW2@SOX$Y$ILyZ18%cDcbA#L*0RXi_viWr$4=0lEkM>rn(V&)%lnek
z{L9*?lzQu8nDg2o=$APYVpqH^7eN~oc*Equi>}RfMk7%rvG+;_bPkEiB0U;YGeJXB
zG5=LxO<*03gq;O)72g{EK<F`jX!{JQtLQDsLX!Tv>vzb(pl)RNgD&m^@VK$#L_9be
zJKCy2BVCO$!C#uaw0E3vB^Yq$<>tKZm^~c@7uYWL&lZ+_Ldmst_T!yrFuK2XWCXD-
zF-vY+wTGb2w83(~)O}q*@(N&nrs)Kw9vCY<^3Ixk1pd5rR43DGS`!B`=;21?dK_c#
z4WreweMO(0s2zi4^VBCbs>ie`%f|Vdbf;Cz*>Xp9Oq4RA-?wYde2RJmj<(?zZSfEZ
zFr}u}Y07{(DCno){lqq)5Mjvl;W6no17>%%R_MCnHShd)XFYexZ{G9W3yW{7>CeBT
zNw~kQ2O1l+7)BtV4}AxClpb8Xze}BdJJA0!*A^(dbPy;Zl5iVv9~VVGX+`I@g3@BK
z4N;ht*i4ACwMoCpPQZ+8oKwxwn*Whv$6|g=B>Q_4Vo$!aTvDvg0mg*w82AIvB0b&r
zm;P4UE((&7s6MgtLh7iLP^%X9Fjf*eb`7~9G3d1VGrk!DE1@#)0hMK(Xe~HgS9)?z
zqu@R-FP7tmN8~ey+8m$QZb}fLQL2doxAXT#%R!a;Tqrld^FX;61->NpCVy%eieyIt
zqkTdJfrHodp6wf25^PC#r2HT%@(fXC1?I~?wFGi<yX;+$uhQa5t#I$lv9_ALSxV2H
z7ns*`Pi(6fXa>@EKe;MG5&rwSn$rj$8UX|?TR;d43gBR+55sXbtZw8p(f)63vJpGn
zV%-N|1ipN?@tSJ4#PL96ldd<ha(|-w@c7E4+fV@M;UKT?wf8ym-@L#j^xsIEYywz<
zf2*Q3O@ge0XwYuO$*dEbqdzOQT|IVlnUaD>Pb=dpg83nzgX$(MVI{;Tw6uTx3>mR7
zL*K%1BoNcFi56i-o9JQj^IOfdD<>FhMsB8&;v#K;_F(Hh^!6rHg(J|qs%Pk>xns~J
z;oDqPkg6=qBLud;7OuDWjk_0m$-y3`luIc`Rd%*CQI)l<;PWwR7j`Q*H&9+5dX0Q<
zcYt{okFTLIodd-ZQFtX?nTh!RhX8l3K|k^gjE4M1`gF=#l~Z^<B*xq5ATD2hhLK}o
zX~*>17uQZUO0VYEAn6&+ykf6%*)rf-+-VoibCD#LBUa!zwNxoeI6^u~oD)5J0%dka
zf9JVm????E4O3WgmwuMrxn5X&dAEw9(O5k&7no|;V;rfszY}?u|6+I$v?xSd>bBfK
zqNdo-zKr~YwiOFNvPVH6aW6G_Wd25Y@b6aeFW#;E(-b{Q(%0+;gbk!Mar3b&VR5DK
zl@6Sgth^1u(>hxQj-&o^I+Z^d_n?!QomR8=nwTqU(Bz{%B%e}PNb!$y0h^pqjxi>(
z-KsCl!h(^gt$puLYc1}#S;~KaL-yrzTZ!UNC32UIo>;-CJ`}!4a}Jw}>cHW;NsKJ4
zaMCPH&+Fc4PLR`k94igT;p(T$xQ!#X;^x~qT}xZJc^(|T@D}<B7}2Zql1_KTgWOE=
z$JE9QiTz;-(quu)(4$Xx&dit~LfzLD`BA`@XRkYg3{VHX=Q2kbEoeL6p6ySiQxnTq
z>5{;q7wNU><u6Sfkt}1OHh~-&?Jx%>=JTS~Vy}ljT-4cb1iv4>ErtUN-!BF-s?`%J
zUo53s_6>iSsC`*2)O~<W<+?-tC?O9C!Oie0qT;9%Q<auI2{PrpDRWo_!=4WSiif>p
z;$NOH2IfD(Bg(Z~c9~;V=)6|2bfYRYdxGUOzK#%`V#{=Z^n{v9-azXhOim_~icmyb
z7tG-?C`^$O%2pTklN*YUR!^dsNzvD4LRHoVrNGu%ta9Tba{)g>i(}v?X|p!mD$cmB
zCJlFZi=cs~@4Tg6;G+{?pz;rqUvYd4M4de?w_96vB?`c{Q;_b~0?um|CBoh5%_Mf`
z#IGM66^DoikV5=Vno_?9D5x=~a6T^1@uS=TlXP_5__b$||DDZ)Q^6!!X1uGS*qlIv
zqwNKYB&V=5RW)DW!~RV>FzC)-R>P4Eit(U>90Tx19B*W)jdb6ct-20%R`0b3AwygY
zDi`uUE62S%?Un3vmF)clKs1#}-+!C0obCr-Xx)3(g-b`Q8|nz|(6?d>lpGZytWLm(
zd@;os|9Y3#KiB{%w|W^UMqVvg?|D2MDa>K5BC&2DYezd}Lw{!|%Z-*+HvxK(M=_9<
zzzf;F_|vyAS*SCQ%Rb*=%XdbU{~)B!w0QKP2@73>OkbdN)3Ph5urr5u_ig0w_sj!g
zn@fF%mQ>y$CwoP1wu0romCZ@NUJKjd;eaFF-%mD2`O~NX?qV7)y>sg38?BiI^K>I#
za~<^Dus~#K&P2G@L6?iOWg0p000q`WjlVlrFzM<(DF&pj^dVuP7vWKnSFJ7^&&;Ux
zrN9fgePaRJJp)bgCxqo~y4<sU%eNNI*OlS$EWVNLdA{-d7cP&CRj_zMwjdjv{b8%*
z6>u4Ykuwkg3qkUPBBO&u*~ShG0W@QQ)lz_+kE#ePI=r_&CdJEu>xu11*`89q>;)`&
z=F>&}QBZ(f93=Xeh@H*l2_2Zx$J5s=)_!~09x2@#=smbgOeN<(?Na>m4KbVLNwXMP
z*#ma}q66x&Ja0m#62L+VVyh{4u?&+_htplA9|2lDe)&Q9Dc2HL658<=g3Kl>7(9N!
z3byJsQ+36yF9&z0p$PaF6+tt9^)N*5aM_^_3yawHbsYW@jOAkR3$y3h9#K5&_!+8$
zrHxLBd;S}X(y0Zh8#5c71yv>kE%S4G^p1TN!jw}(r8i;SZ7xtA3#{iKX&9be8A0xu
zFHOHKsTJF$#UGp?<9<&!^wiNUQRF?MO5TG<&-C_Rkc*_RqKA)VDZNF@N|~2cW|rVc
z57{mVY{ae-TuFe3eDaRu&mv|>|E*EumT)IG2MTrle>WRUlpJwkY@UI|$}amY)W0bR
z4e__ZkJ(SFrj%p;dX<|W52gPNZVu=>S6PzOIFMUnGjbRlXpJO54Q*8u&uU5KW$_bx
zcMW(Bf$b0Du_yt^RZra7eMCMq$BE~j=$k7GfiiFK(hM}|b5fgg5K|)jRDmr@?V;Jq
zD%s#vqqZJrOJ-F$;xLbv&8<;OG+m3{N}$ATYY?y=EG%ZGDQ>o+>vf%ZDU&ntEP+j$
zJwc`<sw_y!A`QFFDC*AG7yK(CW>A&*VWq^P{K=yK*>FdIG&_=GT_VpKF7@gZVX~Y~
z!eMTz-2HI5uYm-9UckAd!2dXd2kz=&U#jIm?9r`&E?)a}g@8e8=TBy??*s3hkVz9j
z_rJ#q1}pK_6a8I2h6Vtupy=1!Rz;^hML=M;ZMO3Iv#R<7*WUMU2}DQu8#?4akQ5K%
zN_>_tQn<tUgUe?0$+seAJ^#MjlWSBCC#kTYPt!^7m8tVkjWC-Bs(e^9IvRhVU`4%6
z4)88VsCmhvg5;wT6`K`8S>W*dxpI`*0?V7FV^QP9Iq)XC5}MNf0d~4E)YS6xbR&(#
zIX3Ws3cH#i5H4N{yO>Q+c-cWX^EYAu+h5r=c}$r;#};V(krPdD+$JCV(_QJV$Oiy!
zYX0eC$}jupnyAv7rjO~APb#O1P;SKsmz`e(KrQ?o?q!XnwS*vWu64t4I?weu9q?N{
z!tOSm?}|%pPE)f2x60k2*tk~K@k7H=n`x0#`;7DBID29|3?S7w$`$vQV_nwgHT^gC
zY;<U)rZpDX<2Yype=LA#e=UGrl6?ud$$8J6I0h5}%8rXD8)-l@q5Reh`By%dRQfx_
z+sCC;EPbcWBgBYKkQsnC5U2h|;^b#71{dOM?k2q#6GW7Egp9m;fV@`vmChkD`ocC2
z8z(ETJ|8#&z}3YH?U2J)7et8NAWNqnnflhe^+lu1iwbeIOw|gpt^E8{%*(uP9I#@j
zd~nwH!<HupfDhh&3VC=7o<F_Z&T)TvA14>%A7ANPdP6OsGTQF{kl)(r)YPeT;tJVf
z67bVow*O(a(pEY%_CbaRaW#cTlkO__9d379D#W1x9C&~Bel0pEt{0Ni&SB}mo(>A{
zoSE+~dbjK9bP(iNGyI6Q47F?Z*6P8@nP{l?rK!5_(%{+t3{M##xsL7ougB|to-Q@}
zjk5~VNi+_Iik_MFWnmQ9d^2WUv5g>=%yihn{r@Z0DW^j|?h0%+&dpY5$AIL-Z5@mL
zH=4`=|A{5c62L`{2S>D~kH<cc&pfJ$I|HP!E!naWNy151GbaO74zVxOZ#0${BeLIj
z%tbrw5NE>m&Sy5JX$hieOj|<7+aG8vGlug#akr;O<mcJm_8P9fF+rw#0=WT99*cBB
zzpeqLo>R^Q9hy$F8JiyeLZmt}kqABSv@^t?)-vbln4Oo^udiLP*VG~Dmg}`?ktMBC
zfH~qt^1S;);=C;5Y9r(InBL=Y%-!~uOn!5t3PWRN%5Uhmzg7s@=sx+6rTufagJ*IZ
z+KFkF<B$_KhIrctCvBhGTi)GM>2J`Sv=_?&CcSM}PtF?$on0Nv-?v1+IMQAb$oQ-E
z^GF!MO*}a&Z!Np$S>gBVSh2Qx^1^ma?R{*uxr6Vgq!g(c`zk7%?Qus9Jl-VvhN|xw
zbeSwuEFU`{q{H)$e)j<OC<b|V(tjx`cP>W*)J$f$ru*X23b^xdoq-e%6Q9E6k|55V
zb%A$lGftkczL+)V{g|UuK?mMy_AWjw0G;aK0X3}k^N)ysEh91^Ly{Q?Q%vqS@rJFL
z4Tci*!8z&q`M^|{99v#n?dQfR(Nw90(>0)EEusJ(X|az;MN^F;Cl3QoL(ZMm(988!
zotKZuU%Xx~FptwxyRyDK-El;IF*HZiR&(sCrrloop?I)X&2@|)Cd>ij;4I^S$sHvs
zDo>MXGW@hUPFawDUT6IZ;dK@H3fDG%yZI|vnUl)}J1`=x7h}9VX!)$2D6g+?q1NsY
zYNR{{>~TGA)_Bvj-t$ZtEppWqE3NBVG|nQwZWW9@XesLdh+e1u${Txiia2qc@z}&3
zm*Km5&5-@VReN;`U{~93pY>jKaJsJ9R2QF|T5m60-kx69xqxST6!xZJFQF9w*!ST7
zTuF%SD@&r%OpQ%DiWLyvO@;&d6s*lC(5HM-KmJ|J@RPy&D^=ld@0GA~KplwjV+P_6
z#lq%Z+H?qhyOo)=_6^hzW~y@EcH0boH<`-G;@2npu8@`vIBsAp7d7Y@+vH6+JK36^
zbCels_Nlf5dLL&yk0weY&vw4gZe1D}!cCzPj3|X|8tRy}887$Hc1NQ>g}0;#>k$V9
z`_nLJM8Y|p_67T}{DOfo*k9vcX}HAwu37iiaaPqw-=7A#TYkIzEUjxjg(Mp;@A9pv
z!&kHV@N~4Zn#F?s`E-6(=8$pEQ+*qtqL7~gX|a*DIxYm+XtO$GzrPX|GnyExvb}=x
z-Qm=}L*m>git0F<VD5&964bIUWKa=Wz1gmo{gmnQ)ogNq>(hc${afScb^@QPqlgXQ
z<jApb<E6j!@CacWUJK>d{Jh(zb8d_4@%WC8W_t1xFR<Col9Pg>mhaG%($)2Tf~yg|
z0fjhlp^m5+7ToW0fi8pH@Rh9{FyaWR3{~&x10!miy_Vd+Vv_&&{+luK9|ph(A{}~y
zQ&$@*i8_jf0J9!_k)frLOkj;#SRbj~_F-u<t#|KkL$g$WMG-h=kZSM|#-VL?g-8Zt
z3qcm`!K(KO-3?c28@a5%$wH(87nyFgnIs#=k1fg4^Mf-C12aK#zAc;qf??JBHM>Ez
zm7C#5Ca%0-A5A;MjkliX#}W$okw(wI`)&vi(hOl04@lA!^-)<|+o`calG%u#kV4<b
zBVC%v3wXMr5<S;gXWrhohdl^foP;(SZ=2V$&x}@@)C4<pSf3d-czsiR<o&+d_HDIo
z0LW)(DLBzRV?a?rEA%s+kG7*HTZgO4xVa2Bj%n8gBB(zNUV9Uih$SMwo-X@rpIhc-
zrE@eHifhiSPH0+O)P26d8G-yZ0B($|v={Y{AG0s{5kOe5$`=o{Mn@6PL~$s5z`7Z5
zoAb}*ghwKzzcuAoZPtI+>_$lDoa<iryg7jTwrIMTm=RN9vsQKayy@ZihCzb;3xzFB
z^^$#n(><$-NhK~WvnjtBXn30PwFhafx&m>4biiaG*gAJbS;2M3_zps3mMOdM-8w<m
z^0a%Oz)5Svb&cs4T_KF#70F|T56<i5=mNnYhY!vsrRcre*u|fQE;`HG&@2+Tg8jP5
z+|vhMjn3M(k2%NeUrn&%4bBV-h@GUMD2g@JY7B<ez7G>vg<$Z=8B#`Adk)GrMQpFE
z9QPK@b9D4ZNUxkO_=M06n%5f)#(WLV7WL0(=K9}V0F3YGpFb1#!Fm%*`Vw<Hfr(mJ
zF2_zz%s4wCJ8vKFQ8`VVhg#gnkP|LXF2{_<Py73Z6AcD^o96D-0*{@uV(m>4{JUwg
zV_9-T7a302&B7;{ng*`tj85-P$6xS}(++->tWDl1H$LZE^ivgIWO~=KuYF5>hA9Ps
zPkfrjwk_1zN(c__^Q_fLeqNp4aAwmN2?Nu$ZKih73g6-K^qhda=f^|f1q@%Ai?)Nt
z!<BnO)FEiF#|DNexhDjYCe8RLsPMQ#HBAVGWyfm{GCXm+nP1zIM1v?KUJ#+kl7G5O
zDBBNjG9ko$c^~lSCn@y{WZIt(9}&XeT{l49b@W+rWCe0Q+9fiHZk3sgu?;+kmkyF=
zOH(UiLv!6S&YJPqW2dOoin!utV0^^54~k8OxjOjzGl>3lJz`G^FI%g8;(FD_5^~ja
zLyb{^-ZuK+N4{;KYJW<<Zm_``E4bKm=PB+JUO-AeLBBsTWT|cy^eu0F8I|wUA((LG
zb;k++l+*vAu0&B;_iF^3%~**E-4&;f-HRRSq@yC`7gnT$pJ{M<T>~#Sp`5DTmp7s&
zIOS`t$kN!x&Q)?&)u8sPmiX7D{Yk?0hy7xy74iD3)4BPTCW+{q_gGwuvvmw)w_J$w
z>-2G^;CyQwQH6rTW#u`6KvtA{1>5C@mnPRj;!DanNt_HSB1?E;1s-Si8v?HMthyqx
zdmEf@881x5?#@}({c67qe%5&jEvqZ6HZUk-=$n~a-QP03i}}B}8vKhZBoJ35v^*<@
z;^NHx=<C)R;@971{xUi|q?(?PC4=XfIL+o0W~>G{+z<vX<h{TSgc`#K#{jQyQY?s&
zy87Vyq|*}0)R17uiQw2NtO<;6P6+ehT(gzDDNvn)%!4uro(EZ10!2yGfXwG0?o>*r
zp`JQgn$l{X-T~oAnBz17!RICG%gMrP$bKqTe-|00&G`1Rg07~IERLAjDv~ae?z4ls
zm^wKiQV^VDu<<S1efb@BniY2k7Kz+u=(y9pdiNH4MNVQKw{<t5B;@^~3!~P)tL;3$
z^9^w`dmbCG`u|z$2J_ZchuJPvBHIJCz+QbmQfg3cb%iv@=o2HTMZsBE?!oCaVI1fb
zYZCL8>QFpa248gBdm%FFUtGEOc;z$H{2AZcwjRs$e^3q&$wD4Ed?5J*rzd`PRVJu_
zfQD>vQPmOrs^`LmutDIiz5LkEr1D?(0(q<Szc_OOafS@31vjB2C&9?d`4z~<{VX~c
zwURF>@}NLvV*(#I<V#E$uqG3bPbcbSrk?NzVj=B)>90Lf3hb8A5GTphUS<hCQ1Ql6
zAe6F1zYdz0s;!zT(w23Dc7TsWl@p~DGMpxfMGK%3FEU$!3A+T|Y?2$-h;@w?mFGu*
z<A#rv3jvjBwMfd!_rNONy+vou!^#_`4_=ELa6ai@ikHrDtYs<lmlNPo7j4ivxG{-p
z#&+AXtb*McWU6d%PV4e|eVVsbzf^|rS-C8~<6N>uv~ISd*&9jK%RTsr-sG8nG>n@u
zoI1x}@W|3K9&WVkToV(um*#By5eYJ;J*}VYDhUm}!S&^Ed7A);H$mDjI#3HZBV=z8
z5SFap@)6;gO|4Z7NMS)%I=txMn+pW5De`JCYZl@2hBWCq=XjiR=4U)o6vJw<V7<Bk
zWupEfB>aErJW}aB#`v~}5hHcfu`UDhyu8X>-+N?M3G$N>Ohb@!&RTp1&`Gmc%3GwH
zV<CKrMMiMmQ_5v@?Zpo-B##>t%ahPtoQK$W-a}vI!hda<;Dh2We7|EWs)R=HF}$T#
zDwK+?+J?fVS->q``NM6aHs8m-uZ0TOmI%S71nyIgnxYXZ@G~lEn=<3BC$78jA+qYu
zC}7Z*CcYI<@O4STmzyiI9EYrB@_u6q;*b62%4GNLQMP7V5nm&DpJ|@D1Uzud29`tT
z_EM9lZFlqQ#4M~&sH!h@7-$K#NWWWIWVC=CF2@`*O6tao9(9V31)Ii$%Xl{VQ9dg<
z;G*6(F&-}en9Q|~91mvzwP1G)E+i(j6I^lEkJq)lG|f0NS9sB9jYTeIXo#=QuKRaR
zHPu{nPi{vs&!3H`2xpsTV#U7+WWjR7?<6|2q+8?c{u4^zXXN02*~<uIFCOFy*B-(B
zzIt>L%%~FIw6U9KHG*xa8yVUff>xI=6GWz$DSQtZi5h*X{*giwf^<7n^CLTT<|73?
z$0*074NNI3xHhR$I`*5`R^G&6>}ZGNWtNrf<_TrdI>8q%V0t7!z1KY`ZdVzzPh&`L
zobc}r2u;{5&*1y98O>O(yi#?XmqR%*^Mu(vc4M$z{IxJyEpOaeQRl!+*i{X(P2uC(
zf@f_TM#lZ`+w(f2XXqayJz|zEmogk{?#J(x53IG)x5G<*VcVWwO7h^SAzt+^?c*Ba
zd;+-}=xn()!DAVr7MRW_s(2nQU$gDYu3HVHGl5z{J`3PyQrMCC(r~mP4mi8=<epK!
z(-@zXoKaCFL4}f#cl>Jh>}w3)sr~b(Hn%hZ{C|-Hf(MH|feTcDZ@yCt3i^-+INr8{
z+vdSq>5G$3`4_7Q`v=bL?PM08mVeG%kDN;d6T|;L`EoSnS)ZcZ#DYuJ?hU3f9afC+
zE?+~K^3CbdBD8B$B!8@fWt=T%Jx<ep9-vP8g1?&|im!Vhst~Dj!pt6qNFWZeD;((y
z51svXl+-Tk7I^#i?gq)Kv#cXlK!Ah-ZEoDc;}F`);uEVI9BkEL_HJQuVXc5SE2OTq
z4Ea=~)92$}ZbugQletIX-pwhbp*KH7?v7BreC0u#%Pza7%Sl(Z_4~Y5OKu3*V`+RJ
zPb1U2Uw#(MC63+t<Xcg0HJJq`j8Zx8SKe@qunDd1M@Z{7jrTBO*KBj<)cets<>G4R
zs(?(S*R6yxwLo(D)&(edUuD+I162)`BLNDsO8aoxzvxqNhfWN8>h!McI@l9pj*+a=
z82lao@I+Yt72<v9I2&6-*mF<y-voWzvjc;4@aHp&(4vm|qZkB7xch+H9&1s)Ng}<9
zYjb+xqG}NQ8KNn!n1lCp0tRP1Pwbcmuz|03no~P3bX#ZAL<~IZO*a^3EB=cWsoP5g
zpJ=5`nZsMi5~h>T=^dO??7~A78Z31VqJzro@?9SLRflbX4#mic-;@{_AW>;};gNcF
zEWuQRj}jSXu>YdAa#>SA0$urK)=ni3&Zf^wTU6a-zE$eT*!V4WL`;IJAVb_#_*W$<
z-YO#o{(E`-uI=$N`lAmw{N}{~%{t5;W=6CvQ9mB;>HN!elsFydgg-I=9i7~?#rly<
z@LW}mP7>>JkiUIwJ6}1r0C`S>S%Z7P)oCxt3fe>d!HJ^K<nwxY#AxYPE9l2UlrMeX
zry5K;9HyrmD2Y@U_gpSDY124R81T6w&V6Ne!Mj)xXY0#LdMm8h|BGnYhkuC+1thK)
zfj2`!wlxh_^}yEz_IGl;GA{%-sTSaiPV7lbE`1GBogGx9n21s&Ou5~$+}LNSn*{m7
zMe)*`*{X_pmlSs<9G37FC5PO@f#Xl}P>p2JkA9A``QF&oxmKbSBJ6VW4mjL~IL#1#
zf{tP^!nj*aIC^sf)1Y<~4lBLLi0Re$^wokqjI3dn?#LVI0~uZS?VhDt)$r2=s@hP^
zpmzVuA+l`ct`YP}OWX9B^Hv7qPQrDe7gKl2m*49hffXy4jAPd~;nEqD-16H$8dh1m
zrW$d!c*iL`uPMma?-@fc@hb<QKBW(6BWgYBl(g4N>$Z$LUXtf=XFsB_iTjDt&Ub@&
z_575=<)z?Jd|d9~9Nz`s)ipUP%@YPQR9u~2t$en3Pn29wAAZ<p?*{GPHy-8}4@s%0
z#%<fcnb1Vu3j&QQG!NPLe~pTqHj@R2^aylLRhH)mZ$5}m{Vmok!HCREsb79CTWD5e
z-if-J@UtfdUCBevZ^U7mk$V#-N&1SIZK{C7GCV5KBm{BB@HXYIE&YfnI;FM{DNo^*
z)DHPoemRL$`DuUhovxA)-7+Gr=WJtMwCeqh*`-V1Pi(dl?4nnQ1nN23Z9E%1J-~ZE
zGf4pE^pETS!?t=<V}O2$q}y|IKLBN6yHEZ6M+UEtdPJSkX6m8_uXVj+n2Ksc-ld1A
z!{gVX04UrHrk9bX%e$pEfj)hY3m#LxIevQ3C$~p98=!Y-uon?|4_(`5BXVTVoCddj
zOF8D35859B5$dOC^^Sc#wNI-~or#w$1<}vG7hBz*RQ9-NM2%rR#9i5EEO*+>|6TyT
z)R}H*89-Yf#@%nFE*Ma9`w-@{%3Uvtmhn^0`nLnlUij}OhMz1*mL_A_?x}?0$(^h~
zU3k(h`eE=FH@xph`BxXZ7If6zQM{$4W;<kLg1!mmwq5_)aoFM*M;=+~sjbe-JPckI
z3_{pjqM=J2O8cyI;BSRAUtXCWbFh3k?wEySt$kHpf0L|pI{8t^kE%{O=^>_{xKun`
zL++9Cf<os2Rm?F<Jt01)HT$jn8NWeVT|&;lIm4Md4zi<DR@)<fKNK~E9{*B+yI1==
z`6qKC04i3Q50b_uCU(7`p422|1j+Hkw*>5iNVcaJ!ps6A8n%&SQMMRfpWPSQ&o+_@
zEaY=&;cYJGq@|}CWUEs5<#^0b?a`JD%k0U72O!AOTOLoFyRlL+!1k(>K}Xzvz3WmG
zNh!W_OZy62oTyTEe1%L@V?k(A_LxUFKvN?M{V-lQ&FB8$gqA@@1L858ms>9<G*cSC
za_M!jP}X{IYK~6VHhKC;n;`(y2|mSY3kxWl51q?5_4SdX5aa(F4GRAU%us>Rz#8s6
zS*bs>ppE4K7v?jzIdh$08yWQ`r~4o*0?^qIk4+J~i&m1!{Sgl?EH=MW`Z_2rF%M3e
zeX&R-F<Sv?xsk4YH(Q~D)Ig6;yCG^~cAQC2VD+TGx-LoF@+olI@L2Z-dy&7rSSgV>
zKSg=vc7uJWx^=<pj~QcGb$PnyyBiP8=nO3b&NTCe^<C~|7gs|y1sy=mAvpa@S?Y9e
z`n=v75ZuM>dNbbZ`Kfzl#kJ&MUz-s@!FkuRmAK}j@uPdf@qRXgo;!=?Bd;#+ZR2>6
zOZfn1QJ+1{bCaAky#vn-h@J$JdOPn+&^CU0-MA5nPB_I9h(7L8SHe0W@jTx;63;&M
zK+A!F3e+;OFBY!WETBv17B&Q@oSJTJA8@$nIE4pXV8drAP~G0Gk9guv<MzlcYT7+i
zg6sMhR~hdA6^JaLK+t>dE6Ru&)E+b`2)!iJC4W}j*yfsfdiqX!F+JBJnoR@gl%>2h
z?qt;0?V6-GTC{>Il`gElWvL{1i&d)|^mlrIn$*@goVz5&{>5kIoVDXlq18u<Qq@V>
z>zJWYULWp*)TR^n#Z8tiec|5Mac}JUdb_XQ>1p_J&3|dJ=6t6sG3PpVAZjxjt(MSw
z;18+bOyq{obK78OV+vn)xu4zKjA%yM?5WC3>89nri2H%COGKV8a@^z4{ci4g)TQop
zhw6cW9vH?JR2tB6=yY|m;rka{%S)nXPDOd)emNF#ESx^BO&-sd0?OmkzEz2NQ{Wxv
zO5M0>24uEHY8aESFw$98SU;p=X+IXjpen`n1(N=QlN~#TNiz4?>|y+#2FBqs#;rrI
zez`AMn#OMq+>}Gt-=M4ZD*Y;hy|)h6sS@hr_r`rivdTa;ex-Fp{a>#$4uEm^gVd5C
zSlMTgAR-|(6pu78p}@S3$QXyfE3e|2!XT;Ti+W|$C|MhJ@Fa1YCNzaPYSZ{bWoZ)Z
zJ~;<4&OtS|%r;JzIZmYA6b4XigfJEtO182V^%`w{ZkgInhY1$9Xcj&zu%+rba%r5H
zFW2$S;B7%Nad#^d;hl2)02JQ4yV3dWI*a4;%Qp<0yqXLk+Gr&}`=|ahAhbVj7%g0E
z4IdmHOK1`^I?ugL+wJiPTNHI5=kJ~j-sP`upv>#ttd9j=UPf^D02Ji?c3T`mS2sAh
zw6vt;IEil520eGzqMl#TQ2iJ}Ixo1rm%=Oitd2aYfi-2IbeoJo-%^m=>ONEy^C5pE
zT*K4KzVN`8gdCfxh7zNOI4d5I`;G?X{^y@ezogdX2<bBuOV7xpzAN>VSW`Cbj7k;|
zvP;!Be1Fk75paSMAtM_^F8F8(vDVs9_w1_=k^ZmkedOkKANrHw7~cH>50P)~42!lU
ziN7TOOvO2jX_i@*cj~?Dy1!p86dRF=kZybT%}zsHSoJ<v8pKntqt}2wZ>gbu#F&I2
zvg8FfRW5VOU9*lsl&2~|Ual)4sBVcy@|mNI%x=e3;+_er$z3O6W0w#q?3Y!qGlq8^
ze={)?I!-f9t}+fc*11TM!-S7F8gyQ-5zo!$c>B5T-QAP>dhqfwgOJI%tH+kWS?`TV
zh1+mAPCVA`g2N=DPV+Y`df-HTVyUJ-P+Jx<6a?F0rf>r>LMitj`9=a(_2jLI>QA}6
z^-op;3!K}6Zpv9;>UmyN)Z%jP*9Agx*{1ue=7m%DxoWpdEv<t0zkJ(oLYpv4#)Q<J
zSI}qM<xf0s9-kczvKfl5-4Pa-v%xKvaN9E7W*ZT4l%-+P6<;R3Z4%8SE3oyis<ec5
z+U1YzN5Rrw$%w!qmury)A?GdT)FY|NC$Z=34f2D!SI@l31rFO1T@8eAP>HLW0Us%@
zv?M<Gpf|FiVFPM&RCbgOC4n3Me-uS^4;1$w&=Qvfd^fug5pmqeM1-UGa-{OFtS#z-
zi8s>bQJ<(jRf`wPi$;dV!$A6aTf1Tk!?#|tX)E%WI2DO}`3T*IHIakft-P!Y$0sJ*
z@WA+(otVxFRuRN0ZnU$WYBzgsjQAQB(dRrIV%BT@S<k{uzL4GWBDHyf%!hFTS%KO(
z71B5L9Vz0=*nYcj8XOA6n4YRD7x-a8qSDNaE<i%~X|+e7k0X64fl6Hpdo(RvdakrP
zKy|pvp-X3GEF*MD%)ZhTjIR=xxJdf&9^n9hE}T<q!RpK07v{^KTbG>BEATCP(i2gP
zjB{&`lOqE<UKZeN9>eFuj3T#*Gb7_&=yQ(cLT7{pkIIF~(g!xpAXjS<kN8oFGU;;o
zbJ5fD(C4<{0?BPNq-R4#sXlW%MY#p_TI2>Du<o|Xqt06jwM9Ne&oLD}bfc}xw!|zA
zhNH_%FLt+GE22WK(xe|3rj192JVQmEdO|)%;P+temjGWwhw>5ezkwxS@Ljs>H{c&h
z=zjnstbu@cs5F7}$L}P3Tvh1{TVu%uvi-{edA#{2MJ2)YVwC%`+q=78J^mk4UmX=?
z+kHKR0-|&(9U>s0f>J|BO1Cs9Dc#))(x5Z~gLDtwDK$zr2n<LLFwDS6N`5!b>+}4+
zwPr0?ti?a~b<a8b?7h#vCZ*Fv%|({{E~g(6&Si~Sv_8`eRn-L*5Xqd%9A4aV&n6Tj
ztxW6}n+Qz8M>h?xQS4Z??!c%PJ&a0t-F0C3M!ZvDL@(!4$ovfBS9-E9vHc%s@jp1Z
zx^gmKI=m0+(&B4>FVTqzq?2%)F$~OQ3hi3`<5uNA?*G`d2{cH}CyBZcE{2xM=vWGu
za&fEcXoT2I>lBwjrBrkdTWfOZfVwX<yATdpGRfR~Ai3Q2=E4bd`9XRM#n^?3)AIhK
zCu$I1pNE>-p2GsWJR-#9HE9Cj%@dj$UVc%USyReBYiE($(A*M!poVC+nWak2JGR;J
z^l)M_OKm2LD`3c@J88DnSzeQwb)o6c1+(38&BjT22VG0B#T9tpOqCn?iHP)z!-TLS
zk89!!oeL?(+rrcauCo|*C-3e6bkurb^Hb8Xa5=gC4;<Mqz4nrZ?U(L+?I>xsG=oz9
z*ORd!O8=eAwIE1bXGf@pnVj$9fqyIi0BS_WJ`h_(vgnON4+ZG~n^1CV_~7fxu6r3X
z$s%_P*C{k4ITjL27Ly;#F$TKiKV#RM)JDbyLox`Bn|NTkjrUzce@f!|2i@_`CWQAs
za#wEfh9nY-1@hEI@iK>Y6?GiqT)1aQWMS$($}p(-#T>@KZCaWx1j7YqU{yePBUsCT
zYB)1wwDTnEv=IjBodj097gd>X8UA!%cfS{|jiRBqq`T!V4~|zXbLnw((_ZztPzT(u
zO6`t5bc&fN^o5p>PMT@`%sv|qc>6Q&)wYb<oO!YsmAUW#oM`0k1ERtUeD0OZd!j3f
zoq4CN-()rEo$~_vyYCBl^^*U`GxA7N8N;}2@mNN&TJvr(TrFI-;EaqfhLA@dO#e38
zbyfWmoEvPOMwkp#86}W^=adVDoSgoml#RCJfOhMvh0g@fw|QeSAHL&f880NkmRg68
zCly>O3sMbziEQRCOckLh%wP9Y87oUSv4;La+09Zmh+(%lCf0HMureKtBcu;TN$GMX
zM1Dv2(?=rYd`EYrW<9h`71?US+;^mOTXAG~-E(C8rfnZPJD9X%dr36hV}1K<<8*w|
zdW`=`@PpY3ERc3eYTny55u*-Q;f8t!xzR4kTq3ReCXInS9e-9tt2{AMi+?VFn|Wjl
zK?HBc7loVbQ9HSP)&{(xbrOr>E8tphbc5|xhZbg$M|y!{wy@(WFV+NO)R@Q%!IP5w
zc=$H!^h*j?gSQ(ffTzr}t`*Ect!;HzN9`WxczRB{$P|w7W<58=5bZ`&)OcS)xz}na
zaRU5nEw`UfDVusi<j0I#+>D<6>Tv+2zd4X1FqD%1e46GygWSS)WR^}I=t>R1H@Zsn
zxc_ocf4==K?Kf>#5!4ErN)kyiA_;yPW=qPs5L*1w*F-<r!c~h`gR_%rx_d&#os<1N
z(|6Od>~6Yka9F*PoraEv2|(s0XcPydJ18UJ+bk`0L84#49yzTBzHIA4JX*4f^~$(j
z^TEcZdacZ_jFld%x#X0!v$PT#N2oWlGLvjo^ZAlSoQ8v}RLj2o2?^Zw-L67hV2J|j
z3BZ-f)h<8G+8w4ZeBQPFcFo)ojt}6NZ#zoE05JJ(cHqGS%(h@B!SiHFQ1JEq6?dl4
zf>^1iwMykTWaUrI7?Nm7=$f1-W)UHNB0QSco<1YSfp#l3;Pz^0aWo(QS^TTpH4~@$
z+_2XHR<aP*K^m2zwLK3wh3n73aVq#}0_Z9v!K%2fS)*$<vVLM(CG`nQ!#OyFWFp3c
z>&4r+m%XKp>dd{c0{SyweZo&I3gv!}ZQwOOPh5P9>n*$x9xcH{SdX(Ls9~yEFV%uN
zCDMMt#6f!t3-jVeJCgqucH$Asf51<{iV}z_NhG3eKLUOncgX3{Dx>MI+q%m+W7NYU
zl@VR-g9Vb4ONbjGOb^L<3;tauhF@gTqW#c1bE-3sXAkNDRxG}~iPE`uKLwvn;g(JB
zqsY0J_oK~T3-_uj+mw<w7A5tgXtS_wj!Sq+cU&dkg%*0#n|o~HvRTj+c)rGd9nmzb
zE*V9_=z~N);gI%>=saDCuSU!f*ewk0a9zM#9bvP9YnOUpJF89d!59KNDxNOlpuN1)
zF*|5O=#LfWUc*4u;kwL)z?>uekMb9&^*HydjVQ_f&SghG%{lXzRG39a&S4)2vx%UG
zXnSCe6mxD1vW{vhfT6E=fdEI;qcw0}j%jKwn(`ynFixXV+T`leUh&BxO)gd+Scqx(
z4SA8Ju5^a49&A@VSHxqaY?OWNk&3wDbCUw9$Nk=Wb%4g#<bbqH6Rz+*bV!A~1u@#%
zI;KBU!}&Ws4Ta%~{*QIdw6QPlB<Si)5{Z)<BPy;Fc6SQvRSKGJk_?=zW<VxQ%hhP8
zZaBJi1c6xJMgU4n^56P`kJMc?m}-T4n#;d%$+6RIY|v*ZyXm2Pv8{1E3=zt{9@E4&
zswnEZz{M{UU(3@%(fqB1S?^?}WRPFWRFi)SL@enh>%1}WV28}tGm6V~lSoMHlPxuD
zXaWL(!TD>xwD=R#c1lW1%Q=rjp^suEztUF^I?5`$s3qni*lQD!NkL8vZbCj#j_S)x
zU8lYgR+y{pwY?hO<|rgmiPz-$j^0607Y6IQ0$6v}T@##YMLg{yhIU&kZP02oL?1Nq
zaC@|x7tNsE@>G%4EWQspOwPd(mD}pn5%4_?rnMdMS>oG$uoA6d*yX1d+v-Sw21iTZ
zTCe@=E0G}jL;Ug+=@w#Foa^hnJFa(vSx0U;-QebEU$nfM^6}Bwbqg@B;{AVwR`(mc
zf6!wLE5HLxVu6izgyh2be`b#Mwxkz%Jd_F3V&WU3s5f~&buTi)0$_1#YL9g2#C=Mq
z-aa8upsRG@Ig4SQIM?KSWtAOD6%q3rr^}bm95v7u7exX9b`%|T3p@zQ>n{0yOh_@A
z(70Jvflf2j8y2f;u7m2HnsiyU7Zk@_wm#XVodm)MG0XQIr4AT_u=jqpurqf&?K6Mv
z@w{U{<m8vr(iN3*S@C{~@WKKD9*Eq$r}x6zb0i>O8y!BDIFZ7*eKD9?hm<IQV`n0k
z@XXv9JBAf7ivkZ{)jxW%BQ8kG_R4RdotOSZI20w07vs$<<Bs|$#l6riOfTz^jhtlG
zp|PMz+}tg3QHqCs)>9L8`=}H|;+tq(O(WgrGZpOU-XRS{b#QA?Der8TB0&Dosh59W
z+q+sqyOP#7-O<Iu%@_p-y+{>_8~=*vCnqnlx(`+<Bb_NrN?>UZB;b#J^RE}+VXlJy
zninP7WTz`Zl7wPnaB5?EL`$!;jw*Shjo~azA%tjB=K0FS?*c-q8NE+CQXKb4aX5cw
zRarbV@ipFxs8OfM&Uf}=O(e_`FE<x93>yt|oR63%i~#PIVIslSu)4bgPr`l)dTjiJ
zINsh)A@gNlHNW*Zd^tX2wi1KR*3b!?bux%I6m;q;0~YtDp_3&JPyZam4f6F+OPn&;
z>o<ezmG^#;TwSfmx1V2~-fMjGV^`n%@K#VER_fI^W_)JnVRq!5D8ZmRbkxCZeFqwq
zeoz^w-=AXGW;wKJQ8jS|Hd!skOn28BBF{6$^YK6|5h+IaxGY|E0tr<v*=4Py>}}@m
zXg9qa3+HTkhdUunjGa659<u8${4^{*5B)0dbkVUWN9<&>p?m2vJ6SP^2a1t+kmX49
zLBLWcQ(|x+$O$MPHhljFQz%CA1M^dFhSrDVE<4AKDZnx07VL%I<|W_oe?XVTRiAiK
zs63ri@wvgm-~q51zTwg7aE2GYpP1$M(62??s?CMIsLxUKgWZg02#x@C?Q9tDcM0}4
zmWG7zHK|!%wX&d2!mKYMvAom<xmuDuIf{6MAp8&{-$F3Apiw49AmDu4+T|q9{WCr2
z#T0LUqqr+x2PT8DYrbzA>iJL*T45M_E{<6^EjnqVuZJX|l4eF!_l{|Gbo2z=9xl23
zvGfUexE!$WQkNx?SfeX){aaS(dSc#7P;^c5b0$I@W7O%{=f>gD$_|04I&wuRA=Oup
zhHzNl3_b}gmJii<2@IpySfL7V1{&0TkQA*LO<vFKL$S!H2*}H2n$J7psRIGL_9wy`
zbEu&Q2?F->V{18-q1WeTXN(e%rE9Wz)ol7@)#$<Nceai`Isf;5^NY-d{G-pVNt#Os
zPzGm#xN4KL9_x*;k6QRiE&fKkSy?7-)`CObH^^8ax=J#QlpeGLKOhWsTbW2?IBu2y
z)gmB+$B5=Re=%^9HEUdcS=<nH>fuQ(@?E@kAy%5rgeri?-8hq>OrIJK?l)h|o+r33
zYF+TeuGEgYRB|^)H&;*F8WqKUx-#16H<Gi0z%%K-XU8XpDjzaKm;O1}zbb1qgRjbN
z?QVa=@FyDN-}jn%Y!DpeeX_7G@6>cF+G=>HWQ4zxuAkK}(O|x?px%2=M;G{>WTf(b
z%No7rDmn%#J<8a6|D#=lB!!q@P!5Wc7gC1OG`%Q|F$Gi4zjTa792UwXAa$Y<XD`$A
zz>S)XWw5<fq*m#}wG#{tlUa_j9%}IPjM7E<nP<pkxNHAh00UzqZ{f2yWA4;RkBK>V
z++Ge&W^~Bx_#Y`r@PgLF8zsEX$5~JI!X)ir3KwR}SR9K_eP7wxd((C8?KwCwB49-S
zq7cp(e~Cq*s%Gf%GRR1GM<^;bNRc0|n^K<oZTn$@YK4*c?;=;-_f(vZg_BzcBPXq^
zEtc$uO4DBh2++kcshhU_S20tCU@MAn^wmol%eSf15?Sc2dbAH|<QweIWky|qmA#v6
zPNhi|T*oM;o!;Wx%085c=M$k`c~atzl9@dzbdC2K$$pM=qsMf8CVyqlmgMb!t<=<h
zrKwywaFO|%33rCqB*M!H{@zf~q05<Obt5s0hA7dlgrD@lS{Y_~F<)`I;MGRyK}fw`
zUwDDjdSZ5-qf5R}X{Z$r{09j1I9-g;`s{4XbzM)@p~JQOo~0#LgX2(U7L%9e6_H(L
zXK%t4it6(_=&fIA>Oy8E+mTTS&0<1+S#VLk`_8d9H|Z!aU?Od(jN|O7HEsdD6wT!s
z1Y47tvfmXaUOn8(;gw`ady01RU?@H}0-epjhFQdYi81H0Itvc={VqA5mk>b6?(Wkb
z9QqX&t9Krk?|{5e)a(~ovk^McoN3BrnQt{LkGVBoiCzi>?=Pyxc=zWju;ganb~e;<
zQ!<G9kC%B!`uD_WCg;>UX}e~X=;f;;7uCKC?V;i93FmFoV!mE+8r#_l^rMafU;L=e
zf30RL0!nH3#|<TQjsC_cY9d*(u?m#Tmg09tZPjP94&7nUthjteg^c6xT%5e_tnOOX
zqJRnf<uS*=&xLJf+G?Zz=c|vYeO27ol&6(c@g@81AUK<8tjxS;jXp<;i$|yYG_(rT
z&7;J3&0uBnm<FEITrh0+KB4tU7ZSLNmVOp+?AKbYZf)}m!51>L;DjMNQLg^Gn@CLM
zo}VC8uO9m)RuFebD@wR+>a#MiN<GN?ExAm0=R~){B+}0d-QNuORp;RydrUJ>qo@|k
z=z};;g$~$8X+@kmB;K2$li!jK1D<R_q<AwlmR7n=LL$}JLVainhgbqZk_C>s6HQd3
zvb*9%f|S)w6?E(4_2u;*_@U!HB22lS8gK-KLbyCE03D~5uJNpM23^vk21jgCF!P->
zvqR(;0Fm5z`8W$8Th-$2R+r13zj)qgp-TOq9U?!(TJ|4J|1N+o`Ed5Z!9zYC9Ndw@
znuA1^d)Q>P4HKpVlaAt(=eDlm(p+9FNiJL`Yyc~|wTu3CW~rn|e}^BPZ){_uHXy_j
z>)b$&wV<1N$JRHa>|7mIGFeAjnCbkE{;kp042i7q7B&HZe}?P*vJ|(L%qa`Sd>5ta
zX$UQ(dZFHL`|`A!dsH_}_$$bIq?tYG-T@qUPh>6JyCjd?sl`Ie#LUS<R=A;D@1rQR
z{m!gO+x^R)o_8p4*b__R^^%bUfY|?LSJ{hrupBw-WE4N}yZd_KqEf;S+Zd5Z%<jL{
zQl`=991>`%@%rO)Lh4^jS*>o4=aHtUzI&-o0IATtWEPPW#LJo8>OR1YXl9`}^V>yM
z7q9x1Kj!E=XkujFu|<K|J^WsQ;m^j1>&CvzfI>moSl_+r-3J4B*`yqtInW2E;rH|U
zdjnKUOMf4$Th9M(8Lc<Zu9Nm6Z(p>pTK;0%y_EKNQ(F`E5VIc#w}QK!Am!scu%oxG
z=cX2ahy8z&3Ffa$rT-IP{t3GMi@qSv{4psg;UK-COdydBuPmu3|5ar+Cs%u6O(VVh
zZer#Dyr8v_ID|w`Bz{)9v+Dba2ni?9R=ipw9Q|6c*6XQ6GLhhh!Y>T&&vjnvIo!1G
zDJs=Tw%7MF$Og^7sYTk0pjsvCh_R(YT@+7>b0i~PMdXz%t|>l1rmS3<g5x_vUXJ<*
z+$gI>ets?oE%iPH_jO@4{%E>I&mRvLU51nObX)N$EwScXTAvDm6HLt$W43jYz0XsW
zFw{;Rl-YrU4_q$4hzu2%-q*>%>FGIb4QDtKkJ!I%U-3v=dz@Ttdj)RuEhXe@@K~R^
z+W(FpSnbB>*b2n-Xd}pw@2*FLSDT~d!Cpuz6)-i_+tFyV!JBtj7O4bhXe`rg%y`K*
zLcx4QNf(L0Nb@O1yiV<`y(^k4ORIeQj+m-~+pd++{n&G(ANv}j$Mc9Mm!(20zkFUx
zon)y`{y3*NX*T|T633u@h%BKt?G7<__#vrzKP@=@0|a|Nr@aEzMs)ix1EI{U_dj6!
zG#8MwID_$&=wVHtNLmuuJez&B3U_XeB(|)6aX!`~pCNaWYFN+Q68T_xfH2$q$MzQU
zK$dDO(kwB9Fe_@p@gP5+KXAR4szsyCqB{&-7Oi(N!?_Svo5k=z_;oG1nR^a~DZSDm
z#P;Mm@pit08!Y)X_aCio<wpv&7-HONc6_b)5nqoEo2++-a#?v7aQ%SGLP5s<II^<G
z!;ZJRZTtBadhbM}l!JA{63g*t6;aUXSq7%rYbj39xQ28PF~T{&{Qle%-QVM9x_^9L
zvas}Pn9TWTN9PoSZWk_c-P=aOMsO;;4~}$m%ZG*wSu%rcEZj0-*P1gT;S`*!%_U{W
zluF<tTaQw2)futTv=*@?zKArH%H<~`ci*0U+9VZY&ckEN*N1#Vh|g}1<|SI?TOGY`
z87(1;zl(Nzo?-(7>z^-XX1yD7fg@)AFlS^=NxbhjtBhRR`h||G!{gkIy0LaRoSP~n
z?Nh4RLugLyvp`E-NXU)p0Qd||efXc^MT>L)!OpE<4$xGJNQw*dQ$|Sk7hbW-a;yBy
z7oA_f+pWw9KCpO18o}fQ+tilB7Fu+<W0&$+PDd8dlHT@*nGtSbklLiil0SwI1%oqZ
zq>6H1v;1x|+R_f?zzNfdiO}}7e^$MNQuL^qk8LPnodVMPB;RBfx@3qXw^nI2R~qU^
z1HMCPU9Wh*Is!;wGbQkJzZJ6QUGr1mV&D9JWXIQEY3fJ0<RdHgdN>=8lU>!_%bZP_
z^bH472#Gi9i^#<l(y?o~{lK%$4@p&S*oMDBfbnsEMR4&`>||xVdEMG$V<*{rG&$7|
zsREq#k=@RIVgO&R*Auq}ELp!<+DtV1Tdc0V=W)z2@fW`U(QLPO$LD=+wR{H9uimT8
zQ&cu)IJzfyTAUYgIJtk^Ut*yO15|=(KhURVCe&hqP3!`g??S4~!Rpvp?Wtq4FKBH+
zVz(bf8t4_h+}gkOsfqYU!?AGPe)eMJxyxSA*6GgA%+7NoR861TWTATl2-c#yHl7mj
zGd1eFyQuzr#tVX9SvQgZmnF%+tZB?Wu<X#yv6%y~`4SJyzj4YXhQk1nuvBqooU8e}
zpgnA4c%ZH(omH!b(!;-G+l_ylPNkR1P$vD(P_{76UJF`LI|);ps+DbY?f1(hOp)ES
zLCLR`>Qk1lz^$r7g00Bk`8M<#L_qe-vB8!|zuvDIDI?7)YLd8UV-#8B(PZMrw9vZR
z2DFvULC%hsdweOvdcoA6pz~VIRGK&G7PjeyB&$iMO@QhKVUCwG{&`$>R|h%Ddqw8K
zF@sZ2$T88~Sml_cy)wjT5Bp%suLMgam+cz%xw<;4+ESQ!S^q(J{8!B2@;>?;(eL#O
zWym|McfDW2dvP|~@xk1BWOETwByncahD<@aK1%=Lg8rs5%TT&!S(BxWS)BBG+UusE
zW6QI}^*~7f1Z=+JnS5*%xf`L`h*#RFPW(!WrFp42A4Z1#EW$i-lS;aDoCmFT#202s
zc+xsLEtZ5RRM@Gtk6xbP_=@)13P=u+w#*OEf-iCl#}?k%dQEX(NitqywzfT>39*eB
zlMu3KT@A?h=dpaT60rMc891wK&i|8=WA6PAtto#7utD~{uY|ssK|*|m&E>?}raHZy
z+gy3<17kj${_nBLDjv!lddrjGC*7i6l246o=_7Pmm>E>0zs<iH(;f^d&&rE{tV+!~
zI_gU5zR#Fv8+z`9ic7Ye%p~hoFpdzqRl}MBJF0&KwI$UURXtF>b==g(PIbFbC1Jq0
zbd3Te71DV&AGDHF<i$cg@E&x10cl*TI7(gD?x49FA1dU&Lvh^b@g~SG{3;+Hd6;&j
zPlc;j`wr{H3~zsbL4A|^HkrLa3ogH#!GpF_|KI0cD<SZ6vIXj)v^b9ILt+hm$Yn@=
zLoNJtY_>BxRn2pA%GyVtw&N@{yDP=RLtk-|`Rn<N2(j#MCxMzs1X@P|I3?QB4f53p
z;M)T@f<mZTv9emk;`oxtuzbL3m637kjEPfE)BQfleDS1wW)se}zW$^fbqMC<Xb*s_
zHNXLv)xkc&menKGV@utGxCMcaq25GqoGtLZBrd@thnXBOWT<L-8upnvaPn#~9AW>B
zJb%3u{~SpWsH-wrBu?`)G-F}p;V5tC<PXl&wAtaOT<rEGkw!|Ax(`;x2L`bB=If|M
zbfNmOb~DCCfadJNyl^5RD>>`r@Gbulwr?)j#za23$6zbii^u(uR}<NGiI(v^YTM$#
zSAuddOB?OGODZCwq^*l~j}$6swb8mm8!PK#u+2n-JZv^;Lug&c0QAH6Tg<`N9_JaD
z5W9v=?ZEP_2lu6B|CnTMqx#a9I<`zr8ApzYe;EZy06)HpUcmu<BC6(@a%H)Uisdca
zQm&_EEh1-vJb(Q97Mq15C)Qpr{B&GAjlW)1ak&2RF=HPf!3LTupa<=z!%qIhe(~Ag
zOZ)*7sQ9%!W8ZXYx%5nDQnScN$m8w##J!13M8hk4m^v6^bY#)%<|fwN)MYtU#OLAn
zXbs8pxrN?k$1_rrkup+84x!c$qms>;PsMnkBX%Z8r>6~eG#PJ^5S|<^B9A2p6l&DM
zSW%-xSD@Wd`NpSm*eyw95`lpnah{$9VW2YC+lr6AHexlkl{6PrXk-0Le(@jg4?Vf*
zP86R3mBJ7t0FYmil7-snV16~Oc0LrgRl|&LhP+I3<d#d%hNWd2Lrb_}qtScdI>S_v
zyH-QA53t0zwhLVZkBp!8KdZED6w;_&!!WIY8ozk5i?6Yy&N#x-p@w9h4h0p!o=O-&
zd<ylBck&YmWWab@rO=gwr6q#CQtH=@(WtW1(|T3eYE^A{E_k_pyWVH|?QaAlqfLKm
z;FY$SpO1d<&3B;s-DXVNyy&b%@bcC1N%iGenQ(F?fGhxl<-xlq5v7?=U^+yLA{EAH
zu-&KJizrDQ%rWBpD&2JFSiK&L%n5%RAF(;4z*5@NqLFJRq*J1E-#g%f1zIE%Q1gQ!
zwV=ew>z39Je<|qsVpLf9gUXTWtPU|_ur91ne2?RVz6+uopVsjxQCgB1OF-axBiJNr
z<Yp|n`Or!{>}Nf@X(0T!-q{ydVvk{e&7G=FqI+IcdS&?`Nr@`ellFPDp`;#^aLQ3W
z?H*>`nWXAH+V#|e12AsKZ?h{#55-W21)gLP>YFwm%Vs1s%dQrYl~u5GYnjZox+!cB
z$>i3P4%lSN>=%9reXhz`txf|BDt#|A*Xyu&sus*iP<#fLMq4c*^SOPeuSyMC%?Lah
zz@ckd%|)_7I~%X>#>f16?m>;gkuvWE#JBzBy$jNhJ^3V;DT6Q8jCH3Fa4SIiU-JKH
zwJWytv8Sk|CWTl!Qoa$@+udASjmf373eOKp+rC9Bhs|mHo;fC)!o_H`CF+XyvNqH$
zOXPiu7yXzy4<zwbZ3LpULlF+0pGhsjmGVgLFIgxlwr?R?3)~vN(<po{(Cf0zzgb@9
zxNhV3L;zW)WS#c8h40ci4zB+mAjMw=`l_C+r&b9*jJ7#u5dMhbtAB{|%G@kYBij+!
zrcwPrv!T`QUo%`(?`8{NQE_%CSxX}sQ&8Ku8Zdt-U}ux-fq0Ol_U0gJ3$y#Q$hDCG
z@a!ZORXJ{(0fvQC5jv}(M+w1>4%8NnFiwV44X7MDC5O!6W4oM%+_+K>`<Kc>BTn*}
zvn7jKXL-ncEtRN3PeGQJF^6=FywKZ{XVqQQ0B?iBW%2C1^Y+L`AI^2L6^Ww3MAX~Z
zOB`~I+&f$Ya{u&X7;&x+(dW)z+k0B~oR<H*o*IGZsJ8-2g!e%~2F6yG`naf0?K226
zS52)0m|tqpEcoY2j^BG+h)ye?W<kaJJa~VJe1%Da<8S?@>vco5$R%Nz?^Cbh=})yF
z48VBU&r-Ibu|Mvs>ozGaKo{6tTLNEvqT_c7LFT~3{_M=HJyn$Kg_+&i_6}8!%O2=c
z73Xwf6j5~}I&jJUuzM@m9N>`wNCc68`s@j&zbG8*VrgmSI6-guzqi};?>NCS26&S>
zgRdWX(2?J}UMx!YRhyi1wVireh#>!bmVT)6nWwsn5}%ZiIL7RqH}1`<2QYu1VtwFL
z;-${5jHx;yv=${Do7|aS%_RMj2v10ebIj&RZe?;|GulcSyT_B1VPby55pn9Mu%&(K
ziey&3bhO}RPe2AnzJfL?gfKC|=ykKjYHx?&S6zms!t;i|13JyvxEqmRrQzVLGpWyN
zm(r<(M8Ht%-oP|B2Cs2ZsPy=Q<gc0G2hI(Z#60rx2yN>H2oB(b=zX4QAB>;xqn-zX
zHSbk=%^M&z6t)#6D>_aTlU@%~8iM1m0tY{dKjGlP=ntN=_)<z)I;D>P8FNGz-)iR-
zNn#?#55?T76x$i==AY8ThAXbR>sfvsjn#JrlP%la;~Z*!-jkXy{XxQ`^%9eI^;Iq7
zy8khA_c?6aB16O48rWgJLWw>FKTFsJvlk{=<*gPdzym3|9snBtNNTRzzdoUU#=pk!
zB)}|}iZzGz#;U|T{S^%!#UEW~CC+;kQ-xoaRFyUyo$#e^OrOL-QLccz25-M?YVy<o
zTtfY!Qk@u<jfz*hs?_5S)Gh3}3(b)zPhdGoN~ST{Vbox=K`|e`QfFfJh^&yWoo`kf
zEf7e+6wv^)Y0&W(@FXbFYGy4B8JvOkRua*5M}jq*feTs9IjR5&Q@|czF<h^lR^HLl
zF?^Hnyu`^wA(eK?u}>%HV*zsfu#rFtf3ePyClmxI`y(YI&=29xxd#-EZT_`EHVK*Z
zh##&U^&@!`9Y-Uv-m1okQcsiBW?Rt@-VFVAN%F}SY=zt*Mg=cYpYf9K5t@e?SBODz
zcjtyHX2o=$vI1A&`mI01ZfA8h#K9LP8Vo=S7x`+@6|oV|7Z*8bt30DJc-IH7<INPu
zjpe{QX(osh7kW!WL)RTJitharf+hH6S2^=R<y(*wP+5MO{-1VCE8$%jdQ;iuegKt4
z4a?gQs4Sm^4tm9z!IKw{c(M#s^D|PP)t667Cwk(7okCr5`Ck-`9DN1jS6M7&-f-r$
ze**WkaNR3x7fMy30MLKcGFC#P8a0WWo7iJ_z)c|(WBxkH+;zWU@tJtZa@^1S96__B
z<Q8M<cw-ca!5a#E4-qf?US!S#QsX<3&q#mGE6uK~SbOF=y&?JIyroUeAmL0>xll#K
zUsm?Jba2l9Po(K;j@WtIIlAdsQNYAUcKnPCyQ$FeIn<z?Y_x#^p!jxI*F$<>)z{N&
z-f+s)9Ppz_#{(%k1n3#mgEzQMtD%hIAmL6^daql3uheY}T?i?xK$&!Ox&=XYe45{T
zaN43`d;*T^b4|B12P?pNRay`6!)l-2pI^=2N;xpf1{p(+E73Z+lSu#DCf3cQqw)xG
zFVhUK9#+<-AU{IYqr*A*&!|EkpE5n$E5LtSQ1bsN6&-&!$@0DegoSW0BLGHzMDjc*
zxaNJ&zg8++cUQ+XiV2TY?4vA@3eqz2W@R@$jlaEcD(8v0)Ms3GI~>XmH-Ii88@I6{
zoQU+J=a6BD$A^rE@kXGDYB!r7lsWd4W&_CM$UKz)ZC_!=IEx4ms~IW1oJ_ckiVo!q
z<2r2OD_8j?VhWGrOjx`Z>KowuseVVrp~)EvOhl`R%bkQhkoqlzYUQ_7v^QTV_dxX0
zUX+j9xc3I7(By2m7);fIC+JiL4`S<sWjHhacBz~ebjLjt(K6$s%{*T@vo_MQ)NCsl
z?G5!)@q%zyn^gKi9ztL!CDMLJf72aLw;s|kNv+1RPx-<oI=tdW0q+#IUL&Fza`P7~
ze{a4j)#y>dtL#@kc;TbA;g${j%`Lmk*psca^|LcBF={ThVbc1uAUX0i(gYOL)L7p>
z<?<iW8~OWiZvhrJJ`kATjSEmgz8C*7MXf5Q(+snn%_aWHCsq40v4}868L(7OQ=Luq
zf`J>b*45=Xcn#`6lciir^mnw}?_73Fat}~NpiDcC!wwQ7wto;#^D^2AM^fy(cJYfQ
zg+(eD69hz5`qZ1$W(>fEiA=e?c9aV?3IcgN+JW9K)l2j`2c|&~A}Ny#VL}%0Wl7*|
zSZ?@Kh7*AhczBq+tkx<=jFeHE^UI|pKKH8&^m%n>1<*Dtm(CvA8`ql+ok1V-_3%8H
zSsBpbuHwNH^hKmQUTk5k)%7*vlxE9guAt0}D~pKNYKF+g2*g<c(P}dr`nNav;TME&
zE$a1&$c?)kzL>Bm+Dl8H|76vNsh-uax4Ra=D=_MIw2!}sR)|sjEi2{f(P+Pp)dTL~
zD%M@&DqII1+cK<B{IwFa8@D9SFC;JEcpKCMt4&Egk_OM$5QmGZj+?kzuP$1laQ0IQ
zH&d{GkNzcp?(+Zqi&O60$jsp&|MDppWvYZLHnxV-O{dG};0Cu@mt^v*pDO~SVo79{
zFF$$lX=Oc0@~*EXM5ge{$<i*HsPf2he{H=XOL^^b%6JUE&g>+SRnw8uTPeGw+CJg(
zX;VO|kF+4Vch&A7Wn9PvG_8ltQ622niFt)3i}ho??s*R{Yq`snu=pvq<<vVJDNTgj
z>E!1{#SjAgJ#Qm`Fz&v(0Y#%~*Rb<Uti<k76L9dT#95Qqath_(zJyb!gAqfUfv^+r
z{mM2vYv1!KgtwL8*(;jWbg}d5fYF!saPOy9!^JN>SHSZ-2{sjO!4U|9t>Ks8c*EDm
zwwO#KqkiG+4+lo3wJzl>w#>LB5kk3oVCsp8pOI52F5LRaOw#iXW_Qg-KU{mS2#N`J
zR=A5sZ+8=0_4w6p278%}byIFeg@{k{XrjEz@}>V?ARTxKQfUt%Gy1WG>#PK5IEE!S
z{{!Q1X$l4Q?{fSz+uSfXbfC^&ne@#J<t<vBkltRtzFJ}A4=SJYO!u<S-&15|;yFHl
z2$t|n1>8S$C~&NYlHDKX51b0~UgD_xsv361_*oh<)REaO`Hej6(vrurU;p(2lsSA&
z<;fgj*}A_Y^;{a)o~(|fJ70y$v(1*rm3z3=&Hgo)S81RPsp_0d>G5|@$~<1GN@Jc^
zV8FzCT;t*Ge(sowM9DK>tQP2wxuEGB4H`efS{`SDXFm`J9ryv$sp3s1{Y}5uv+AN8
zZK`h)_c0df+&8c>H{(kqhLav!>i{U9d9cQ}o+|fV%v3~lB7V{%K%WK;5N8I?p$9|A
zEcuEI#JXnhfnM4O;1Hr1J$g>r|K8;>Bz&hdy6+&kco6L-de{tVK{p4|^!puu_t8Qr
zKFfR=%id6H6tVS<7VGWe;n@oFwpTWCz>}%Z_}s`~4<fvO$CFVcLCDr4bEM>zd&ah$
znw2rQ{oP$GZ#Uo|2E9GL|E)bky?=>M&R{?!@WRqF-4S|7ZosRi{K@K|u*l(10DXfU
zvys|IQCrpgF<Q+W+w?Rt3qZ_ttNYVRYKe{SCkM);V-@#gx{hCMmBzGhLdl}uhGySo
z@zv05E^B{p@1@o3H~-a4*yD@gWm#I}WF~}9jCcEJOgd|X9vkDk)evE#uOGtw!YC9E
zG9N-Z`em`X3UNxX>wSa|P-tSM1JRwHC)$#VzsP|S&)4v0R_?0nxgn;b3`&D2W&t?R
z@Dn2+;g*pTvpvkv?Rj7!1N^gwxD{B$KyE%yGvSXldJqWn(agW~qv4Yg(x^Tup#7jY
zT&nlLKNC?(Trwj`Esg=Vbg;!r1ilPs<dOPdR9Rvzn%-hO>n31_WFyoxp-<GEqRyX|
z5j=MJB-m$g?mwHuIv4mWx$eX0NN=;l={vw)81Vmje<r&BXD?h=0A6lN&{YXgP7I2-
zk_k-+Q{|gk;<OC7PE?1~3`_GWWx#v9K4OOyz<NnuSrN6JEj8v(x+cY${zO@%$yccQ
zuAQln1h9YZ*lXKpc;K%RSh860^kXQ*8~=OpS_>XfzE>Dp1LZR}yXn7&MjA(N0r5a2
zCZqvC`z;1)cl_QQ0y32;?0R;W0p7?cSZVs<=VT$};)wRff|^9Mlf-4Y*Ye`_a{vwA
z1k(2j$y*k4@xg91OG@t4wKwt{su1K4y{qp(w3_y+9e|}bs+n@51m&j?4I%0VXQ+-o
z%mYF)DxH843nY!Mm(robK{QWn9BrudxiL|V>KsOxYa$^T2~Z!y@W*eUmag5(J~q?2
zB@6IcDCF^&zH2$fN%uSC&V^xiY#p{Xkq`I#-Z5n7=VxnGL8t>9*!+I)(&cMYAO5F~
zv{yML&0%|(e`lV*CHpt94<ruSzZ?9sAkK1PHKSYwUvc}Oxa2&OVEF>^HcP?QNmLH^
zu5_d%ZkuXV_@o%ZCGZUiHIIopAl~ObHNb)gaFewH&_s;tQ*s3410bnv{qPRu$tPG_
zufz38^VB9znapGevt@l6j6YFO^+lJZne5LL=BHg5f;U%*xjL|qEJE_vA8JCcPzV~;
z*UsZt<uQHdaaK>zF~#|U$bRJBa^&YRKJu&Uy&&orJSFsq;*0Vx62yD0w%ma5OUE(d
zxi*(xTVjb99*(I+c$!~->(Q&VrQIBcr0WRby_pf##da#+X@R=wp@g6Z@3anM8+#9m
z;btPEta%>z?9NK+7^D8xW+L*j)#jMIg0he@-5k$gq|3Jvr%D)cKvTk9QzoZ(%Pg)L
z@+Aw?+bmaJkrq3ix<6;F(<2bKnt^`nB(yjlnT?t+(kiEBgK%W<+&aNJ%>o3gTa4KM
z$Rhx6qJ{UrDd!>ai`nTw{4OWJL0F=s37z4aaBsS+vLS(^*eg5{$8^3e$H|UuvbQk!
z1MLP3JRASB5IzD(;t2)^g=S}-@eH)*0?AFeu8Qh1D(~*3<=jrDr*2Uwa@_Xnwc)P&
zYT4&Ru(W??*SC{woF40Qq3^6_7IzaY771CU{~Vzjht)OXQ8pgf^5EQ549(y%a!7n{
zWhn(-Y*+=dqvm_ulvN^iJ@!QWVt6lywQv0Ln;o>*$v6llB%e&n%))$WY}okgW4(va
z^knqRh*rr4v6uTQbklToYuvNkxSp=Ia5gO~&Y5>Ab%HgM@a@2vRs-yOEdWr~@u0JJ
zbXUtM@;o6*t3({}i!!Ug1w!oagxr<Y-wW5h;r-!xJ|ex>Na@1^F_ivlD3{h^@h*?=
z&~T+KoNT>9h-^CZUDik3%MEmdEd)^X<OAzPH{K>BwN}+-)K1*lY6Z0w0I<6=U*kVy
z`1Y@c>zZGk({a0NGUA!vvpmUQn&Js}!Th1>&C)f6gN9G1H2{Oc#~H%(sNKPq#dY<N
zRy$eut0%9hE{8-|AgosGPj0W^5pQb!n44P;vUK9zdZgWhI+KeOqf-J>dYN_4^O)Ub
zbs}d!F}Jsk3Vj}iv~Dv>x(+ne;L^$&m3XB-7C)xk!^!?gBBP*f-!|thnmG4-!or_4
z1ndm+wZzYplbg&oq6kF}`j^3{<QKbrI7<OHE?H{vQwHrMmBni-zI3q%jkBgV?iER|
zAPJM5E#+x`Vg|dOta$OT#G+9%_`pUQY0+=BayKZhA<3oaXQ(l%U{(10vhCUv-C119
z(SjOBLIT>-But(M<U<Vc_|qSA)4bEwpLzstqfTSzo#Oh9$_z3&u!V#trRGW&P#Ov(
z<Q=r(yTn|H=SJO^>J`)D<hH)NXt(;o#Wx<FC%-}v22a4xa^Z-)T=z9ayx@O=3KXfZ
z{(a-g<08)`{BEZF^f&g<vP)f%E->_PN`Lv3QW4R}EFW3aKcuX~kGpxt!PA{({Eag+
zw<4{OYbjxEky_71IzQlQ(4vsz&R=-nd@iZzXqS_L5^f#~)9Rg#&KMA*+IdzH4h`d3
zi2=69Tgn}!gjj?lL-M~0t`rmHQ}x9vLB5;0EMUD69uEVyTq!g5hX7Ip>^CCzyX~}3
zsq&Y*6Q84A>*jm91BQhllIwF=y!T0R>aElMaEXY5S`HYF^o{w%A=SPcP>=e$_DPN#
zy_gOozG^DAjrme|iJt*2=h&>Lv>@%ZjtVb<p^z^0Kzn78bhP4V1S@#PtM@=sG8!?z
zkX7l;Ah%&(VIl`pm9Yr8<SY^z+7nVQ%M6X0rO+I4Z#6MeYAl1=t<vb`c2Lz#H?bV8
z(7ZLBbKsx|IOp*p`t~hoQf4n=YaRg*DyuhyijaUsB*KKz_l1L)&pBd>@4Zm=2ve{i
zu&BICJE;1vNRjUUcP0|Pp|nVY_keoCsbqF6$Sm)pFw*R6k5H%(#k2nw7iA$%D)wxl
zuOurSH+){S`rXLmp&XmwbcKO;x7<%0q~Ie=xzw9dUiBU)D>Qkih0FWZ2FVIhCn=wj
z!6al)F)sa-i$G>mGpTB3_Ywo4wIiL4>f!I-AVH^}p_>TcY635J+9)r2vA6)(!dR8d
zWvHhCbq4jqJjQVOOzm!LjQ7d)Plrm_13@P`M6ujx<`<iHb4?6@&Gr@`maAr>Zmc^p
z&7Yt2LQ{#>&Lw=vfN^`S$(NRkd*CSBsS~+4ms<<<BHFT3w{5Lo_F>S8lQ{rfpIv+q
zLS69e{eWUNNBPt^c_vsJilLbu+S4>#prc5cfAU0i$Fr=1;F-_DONt<}5;RY>DD{c3
z*!{1KL7)?d<;W$hb3e_hA>(<&qGfx)c3729`d?LHZg#c;-#qC;$$#W-D-htp8Pt}J
z)L$a_rOe_RRm-I%|3__?%ZpZli)XPoB7#8?_i?V@XOO{yn%U2b=Cr33EmJE`@>mv5
zM28jASiTzO3c^uNtjwCy>u9OeDjB=Ird6d4-V0#Ar?^OFr`LCDBHvZl(WO-@=e&AG
z2#<14!I<WG_Qx+}<n1k`cV>-ih=`r+fQxT|9f(a;I|S#&>Mw3@_{aJ*4V~wu4G(cp
zaKwH{WguaZA3&j)wiXfv1)Nu^>|lcAJSd^2TH(Z|UObLQUQY{kbyj<SI%YD`)D48?
z^u|$}_QNIo?t`k{9s$7<sW>Ft-OU;y!)}h6WGi%q9ZVjUNpRWzg(*`@)<RYZj1dJB
zM9C1Gs^~0N3}22jsc6H<k#lfP=h?kDb{$+l>7$58i{<l@OFY5xP;M@8Y(#%P{NqBp
z$yDw_b9@{B@c3k{10^~RU&vmmd^td`J0GjJ&70Bb01)Gy?8tv2yMX7OMsV+cYxs#_
z0P1$a-RA(TIf~Noyg$FP@EcC7y)(4%<~P2403JKQ7%JKqen|_}%&os<d(CGOY?GW^
zKoriICe;c5$t!nm@Vhb$dQ7n;C79}5PASamzWUWe)}0%$6Py@!i>T<VfJuJ2l_2vp
zSXx;3?TVV2@DNd3K0@QxqvhXHo|o-^=jWjzklv#mNse<vIPZ<Xi%mQ34sMRn>KKxz
zLqf3pw~))<a<q(>F5PSkR}2|DaQMrL`aj@Gft0L9yJL|vzj`X$fw9T&DMZ*67mh%M
z<K6!FvD#tp<>L8)L-FIvE+9k+SWp-<^ZepWlu(mp1QxIqB_UV~A;Di`A3S1Z35!B-
zjvPpuYAJpoS|e17M6gYUdWOLq*z?_{JJ|Ytbqxd^*cnP)&L^>y0$v@qH2NOn|5E%u
zD@Lem?zM<`4@6t`v*C`MoUC+Md#&1M_OV1&zgcdkKR-Q?1~J~mc!d75V|DYwTXFrx
z<`w{t)q&mR3DPpR^3P3pSZF!Fn%>xu%x%b%#{iY;9#jCv&g>7t?Cy-f^ev6zaB)Gg
z0QnU+s)TmT>sMa9%D(Le1@OQaXSB(5x{Q0p8Yx~Ow^hdGVl^yv0M0<zhRivi(ZO@*
zv9Iqvl9F-16m2CBz_bZBz1x-&kPtj$5Ap*X(g33Z1dWFc>OMZPAWvTel<3n_uZ;bR
z71pIoDbV%VmDk#Yr4mfI2J;d>gf#$x8HPb77NC{O5$GlHLt-K<(An+Vm?<drK2R}w
zhQ8PuwdGQ=Fa?E|I1_c%m=Sg&jRIgg1D-E`=i6Zx6_n7_qddz^y5OQhpO7)Kr0rL%
z1<jc}Hu^^^<v8f2+~O%Do9zTXX$@fFxz8AT-ZnOcf|~3p!BzbP5UO8`IvG#ITFDV-
zXNT#u$of&(C%{HCKehNQt)A`QzDfP~ui}3jK#EtyphiGmCZzVWdOm4n@5(TvHJ_Kf
zaUX~B$JFi02nMyq+6c6@vo~(I8l-!^AeyiED6xnkk8%v&xQ*SyZJi-DadvN=H<ufu
z(1L2kj4gd<cbq2kq<Hr9#T;s<T87x5dwgDurA36iTjyJXT>)ZM#<bmn)Jiq`W6=p+
z*SpVT-oJkhdT*~Q03`Q4uEC-akIU2(v0#8sQG#EmH?|S%HC@!W#JuzWOm?~+1dlzQ
zw8jEWmX+<dk6w|AyD#v})m#DRuKhI+c^7!n<CC-T*?V)**^Ud5K7gY$*E0G?qo(c3
ztp9je;u2VTz*FaSH<0QPLeD*Eg7A54Z%sAI{?2<U)-lv<%iH3DDL6C=PC1%2g?cDs
znAhO2iD_bX$bq-Sem=_qX%355dTz^@5}Y(wop1mVAmf0`yXSI&6=PIT=XK5%F|qit
z9;@jFBi6FD|Hoe0q>0o%xRExsEP!fG4f1Z9axr@JuJenRl+K*xqGDu1TvvhTDV?6M
zymjCmyE1s$mrgtu=3s>h34zcaj@BxxA1qYk96Uce7Hnp^rwC_?N7q?Y0J8Q<q4%)2
zuVkLZBcd?N`^iVo6@6mk0@qaA2a&?QjExV&o~M;OABt^KvAAx!*BPP8N^bB-8@o-d
zX>?ac(5}G=Y8Y~Gc{z7bvuvEjhbOAK%5iSeYscGxe^59}Q829e8wgRr{KN}PXt@Sz
z$n9+VCL21|`#}u;m|Ok_2sPx1pi?`AQ`@F1Zb;W}*#nogjf|U6ie8<JSu;76=c<tH
z{^~eh0f|;ZiJ(9}sv$^-PBgV7t_#jte4E01sMybR&4$76k*aui*&&3q#%^4L@3rr^
zFReDa1j&2YW58sIk={_FHGoj(YHRIolq0#fsDIL?SF-SSPcY7_h@L!lX%Rjff1VAG
zgj|W!>z-|8vlJ9@?&@E~P_T=&sYnD10#4XA_1%yE4yEb7`!Vb{UxfS{H@Pav4)FEe
z!t;nPREGK%X_H%OJv3SKJjhNt8W9kM-^ZvaO5$UEV`)k4`1X<xh@FYHqs}qABmA0=
z?#`u25&jnX_RGfn$gMm*VzI!_l@U<f^3VuX1J&|y=s62A3%0i%Xed*}A*sg~D>y~D
zq2iDBWX&a1lIirFG`LAv(~a};9&x$K1jbS^AQFB2y^mh&ySEzik14M&CSlH1m-$}H
z6&ZrR-1eFR6eZZ63p{%tAF!wDe)6S$GzfV-Yd#z`f0`AOO-`y;^M(Q1YL6rCjErr1
zJNR%2qVeH_eB9ayFg9J8+QYhjk-X;7kFc4ZhSZOQY+?TZ>O9no;rer|%-)tLJ-%eA
z0HI6Ip9q9NkIbREa^{FJJ@@xOopG0l^Io?ANWM#M57f%$*Gvn-8A$w`MmsR|XS8JX
zt|`HxGoFH^ikaK7nFz%Bd2Dgz+T-_4VjZcY_`xTD#(!aN<Y)O8Gg?h_*CyY557urn
zLb!v29(&MHvzbtGb82zCc;(e;Z8bAQ2*cJ~`BpMDvE)8%Ad`x(C!<#2<cuG#RuduK
zOk45EkwHYke)Lgpbg!DRrk?C8!+dwJ)jMlpI#Ofq*XTKO&E||5W!BfvxgWoc-uh~e
zckg{~c4CAhBZq@-w5QZqPdt73=LiP;kOvL+0N^8D^G4WEe8>SPsU|<h5#qZy0>8@q
z#$$&0gZH|U%Qa@S9T&*G49$|AfD0I3_BUxBzoYY-8c_Dt_f`#kebtU*O!VoV6H~CP
zoAt_<VY~efL8JJ_W%uW=`HW+v9XK%U;n}?n0eCJzz8hlXBnMbZ12Uk1U>sMapA376
ziX>E<*i>=ey!o!t8ABvFN#i~2GD3wTZc6zxm!Bi(;QBd>OH(C|sOhtY7#MLuZsP3&
zy%TWd6e^#6+mTci>yrD-r=^Jc#L4O9au;Z~J<$_&KrHyYQ6Sc@^5#k3e3T6yBJBS$
zw#G2uggFLFgI*^IB@t5Xf$OY4xG#UwUtPbbI7~T69cIWOTbSzY5R0!!=E5gP0ybhT
z>xR-zK6n}V0rs6zU}8!X{COq%*&J=cWBaF(kj0|ep$YmUl+d^y*)&$be&1*HH~vo+
z=vI*PZ30p_)kbm?$Ey2?KydyS_C=Hw_bLI02qiq$n^#lTz4s|@^+ZsI6R7i?*z{Y7
zuG-f$Bg4k~*T+|0=4dwM?G9A3^l4X+|H6EO*^<%XWp(_UtC(%}C|my<^47~AC5qpp
z?$l~^VBo(p8YCDf-;t{6FdkKxan^<ZtJi~}cf=(W8$Vyi^yACS8Zl^wL%UmORTkoK
zVDK>nSr1d#GFZI*HFN9Pm7i)Ge7@enXjK7|nIhP_>ndE~$Ez^!7l2tnyRmP6Xt0Fu
z38`TfPd-Aq)RiH?fftLaKzOH=RKgT$r>R}uGK+fDN;<AqT~>MJO8&-P$M@R&--mBR
zvv1FPa|%K?BPvPoGNAlZKO4wQvJrDXPd<P6;oFb37A{;KqtEw#d=G`JWe=1D$}3%u
zkq~*fuddF^7C+|W^AJ)tu{bv=GLD20&Tu)FEu_y##UCr4xBF#1(9uslFmC+=4TnPa
z)_u3S!4_)|9(;FU&)kYM-zPQ@j@;TgO?sjb>Yf}Wo+POwOY1maLlBRei*{?jMAJS>
z%PSiF6$1BjQGwe&&J@mjhl<0yak0+J61seC$9c)LUpV{#^XH_)ZGv9D16X5@HN8Ib
z8W(-?&fz+?ap`?5bw%*i1PuR`XnoVw8jt2={eoRqPj*dK#GHVoU)>=V>8NZmQVzSZ
zIZB%INSe<*z%4`_R?g`CS$k`g7a|>ra2BwwPZXCAmcg2^c0@u9XS@KZ*Pn_?^?B`h
zpj{w=`_bVq*n;7hpitVQB=Pwoe7LZ<L~`+KAZO>g0odtuiu%d)_eFm~eH)xOc=OVS
z0*0(@&<N-ar4x&!%9~)=On$VF;2ik^q-A8tD^RPUv<@Z8pSWxBj7}01Qd7fJ$-paM
zHLKjSPzjHso!*tn2CttjM?R+Nl`*mSJja{x`_nX$LYyPvfHrU`mwO(hAY#k6vub|a
z$(Ym_hStwm6mvXT0j=!nJ`a7M<$t$XWPJJ|yLwdD{KNOJWQcK{^V<m-FBemt&lY_s
z5`oo{i_6xfkBvqR&Bdr^eU<>c+PmBltVVu+YImONQ;W$9x}xA39IE)dA=Idz+jwUF
zDAJh-B|^>R(M%DH&)fqFcJFmdybm|tqsxitb=!E8s<EIAj-Qbgd@8r{@fH4#Hl0_W
z8%@q)hd$G)u#HUX#CAt$n<K7IS&TLO;1m-=r`4GFi2SUjE^YxKF5v;ilL&O=02Tt>
zGXdMY&GtgpTH@01M-2H`C-yIM;FXruS^u|%Hb42hIZJXwG-7q>6vTaqtnPL5l0I$`
zPL8XCg8SS=skj^o?BWTe>PJ-%-GOmqd_IuOBbqw5^nLc*bR&whc26kXiBt`0;rqIb
zSCGN`XF9!MS_X5n6QO8e6zy)3R%!8=q^WqwL<U>!w=}DkbzdQ0-hO0mbN+I%nZadO
zIwi!zAX$i!iHs33RQyfn0bf7sXx*E47Px(8LU%Fy5b7}r0g8&~k+ol;=D=Tre)pX3
zuV1B-onL*$@H8E+>X1~YWjJRdsRf3cNI&3^HaA&5`d&|})bY&MhEJa<2LCa;3@G3-
z{b)qzPciHjeq6`-P6!F@`~3Iu(w@C;>{HU6w~M{eI;H$kh=wO<qI+k0ZpJ4@33%aK
z(n0HFzatUHVxLUGMeUvdll2YZwZRD~!vB9feRn+7@B6=zgiwg=Y_ciy7#Z0kl|3Re
z9OGEWjIy&r5{}H0>~S2k?5yKZ_OUs{ImWT)@8$FE`}^<s>pafoy07awuKT_)E)&w4
zF9)q+#uTV)KG^?ji%~m2{<9-Gf%%ki!Xx97r5DvH+2ML_JNm=q820b6&K%^K<8?gp
zIv?{LVq!#Y75O`!-MmS;lzx!<wbZJU^Q6$OmMG9%@-nGKn!095Zo@as6}}4nAT(Jm
zgj5}=e}60DjjBE|hx7v3+ib@^`$&Qe4$FI7EFzu_(fFBE3M3@_M<j%rPx+${8L*Wj
zoFB3%vy*&qZ@RkdXLaEiNC*8F*Mehz?po$S`Ml|1*h=AS7WBdIdD%kg)bqOZzzqw*
zTO0hTYu^0+>7~st6n%nH<lfLBe6In%tJ^|L&&{pxi&*U$yXMv<zm`X9v^1>BUAjJ1
z1!L`6v9OG2NF@2=e5c8l4U;nE%fac&(>y-0S=Cr70%~^9+dS3iovCT?PfqK((I|+?
z<L&aKb793cOs4a6H^7dWm5w_;j`vD*3Liw5n`RToE=*yQz>0_Ph<-WbD;26q5psLB
ziAg_ud`^d>#g}EMwVpjp8gHF!a}8nR&VwX|vh+b9+_m0}OOBIc@Ix5Ys)96YXUU2S
zR3!B`g#=O$y@U~&w_)2^L9E?cm|$o90x>`<g(y<Y3pe>uC+L|a{o9~vMoJ<F?1&(G
z;rZEy@QCHLo^Ovz@b_Jjv_(b~u~mv~dZ;6_+wUhv#>}^ws#d1<t~I8unX3wD?@5#=
zI?<d1#$=V}#aUwqN4m4GB3xVHS*UEfsm*=V^Sv*^CC!{EYH%t;dv~Ui8SQ*0s_DU(
zU<atDsIvfSfx3rn|7GpVa7+K9<$gl#%`ioz#B#i%N_?g#gt5(Q@cw3l1GAz$8O{0p
zy5!LwZII_y!gQ72<Or-@ZweC$OfoKooiGIK4yP<1Tw*n5W17ItLpCKd$Ip3(^u`cI
zQ;rc%i<XnRZqk-byCj~WY|<&z8|A)!VCfo&<&ZyEqA|<7z_ub?*J#>RyB9KQbGi%4
zfr8;?US;PNFj*<TAW}R`<2?4yPyf}^eSTK->Dl71(W8L^gBLz-EaJFCbE)rvwIyGj
z<8x!#DA5;`1eg8gXjPLy)ZPE~6xric!ml<y5i~$fi^mBAJkVarG{Jn_p40)fr7h}V
z&yQYAW$a<s-BYmUPx7VtQ91}Y#l(<~Of?&|SViKs1516&N>rdfWvrm^*Wa8J=sS2d
zziAq)u{%|byk}Wjg0UhbQ1g7jiUfXIw5yi3kBM5)4q4`xPMvGVQIClyDjo0m%>)wr
zh2eK#R2V9IMkITf{SDU);f|cF3W0z}ak^5}ZJswg&PS7Mj|LFS2W44f3*)o<^beR4
zg7rii69!27x?~Cd++u*;`3shPIF9HGOCAiyOeSOd#>g=8q(o5QmS9IJ#>~XZ5f=2p
zG``a_=l<rgM@2$sGsZC{IBXWO1Bc5EDIPA-a4PmH&IKLuD;^#_{gq+=ZiYG<ycPGW
zZ77#$TLH+(oSZ$_f7`J*YS_qqfMo*^*w65bV}e$)7q;lCWSaN%r7d=mjH`X3!|RgP
zd^6^nJ|qva($>m)xlg>@fPtuZdc%C=P4gV&PN~qZK<zVO_3B$|UG4$I`O|Hq_`D`>
zqkKVBj%X=|upc){@47#Ce~Q&cl^Rn1sY@(wa0z^%2fZCc*x;D%xd*;ffZ|w*+|?Vi
z8A3Wfr3Xy9Pwz}d!+uNzc<`JA)W{~~nEu}^KrGr|t7~?t$7@S(`Z#}p4sT!pip@Qa
zw`zDG@oA<tV1ejt;dCy+x77GY9Nv(r<JUwrbO`H-Jw7hQHZQH1Vf=1Du$_qOZWfNc
zemoUlnic#hUAEwpLQO(GKl<>&N51g*iwpCeva|haQ7`8iaTNqedi4Is2yIQAVW&=9
z6qs5EDxV&9G1f|aG$o1D__YW;(Bf@zRzjl=KcC$tdOePtQg{GbSNOO0ef1jM8gTYk
zLH^*mJwXC%8-JF<hX=={A6&mFrI%Tb`1`s)*CvA(s*zT|lhxicDo-?cF;_)9(HJUB
zFKTM&FH^{aZVojX(+z%NoW5pMZ1RcPDpFXTl|og-Sdg!RD;8|0U9J(UW)fSzOhNdE
zyOHWt+QBU{ik~kr+<2nakH>GOp0$ZRuo*+cN&u4&rMWyR>+!;@x_V;&K3DL_J#wZD
zUhcQ)@(5mh`q5d6qW}B=c_w2Wda9SHOIbaL)=2fD;v0gXfS^^27HNvR{_#^BM}TtE
zCCo6rQEnbbW*D<4VXb&gn5%4I<LG5oyk90}_TjBw2>hGMD%7wh9VCtIJs!1kXxQ7U
zM8EjSzMzm3GVAs#c)z6OuH3d=t3mZ+eq>Nuh~n{Or);b)Y%BNw=O*O(f4TVy$W31Y
zMJph7dU4C2Oyh!6$#wW(YuYc1r-rJ?&CBnhAX=Z95(ENTK@djf+#fX>QB^Mc_l0bl
zzv4VK1<<fxKh?j|YzS)m9DYe&zt2yv>BE<HUY?&f6VENTD>P;l%QmDAmb#<mvqg>4
z_jI#o&v!St8Mq*I52H>^($wT}-_1P7A>ZJGTHAxbJGlWqHwu=P0#+!ehn=?*Wf<SR
zOIUhyd4xP#%V6UdKBV<HVLR&y56TG!BA6p{C^?kwJz^XOarMX7KS)b%HOu3DXOHZk
zq_xyA!x+Y_%1b}F{{Z`ye0@VXX#6crCdMnummmESTJCVnpEEs(gt14?!+2MqZ1LYK
zb|0V5zo=el5lL@T;6d_z(hK%;riLj6vUGiH3a45Q9C(m<ddB&BYql<EZ3oQsUu}Gw
zeCuBz<>4MDf&}nCtfVE0&}9|}&#5v-)RL*FmEfyEcRGV2wBax8<26Ni+FCCgTa&D#
zR$QzjEfSay|I`1$Zm_z@H(Hf^Jzbfa{(0pK(eYXp>Mq1F3uUbJlYFOmvRGIQ;**+z
zeFSl;2r4{^f9YU6o+l&8PxCN%PP*JWHe;^!Diw)LdU`sDXKC5w0&e6^0#mB94dIh(
z3XXHXo(7!ep7XSx4B(4aaMNCVihD!S76Oz<ldIYekk1>SQOk#Ml0zX^8A&KT4!x*;
z+b_r9lymzxFJV)AGS)jJ?VQp*6@ir!f6zQ(W-?c<-4EIFj<Dg5@7R*0TNv>TQeEz!
z?{IX;;5?nFW9-MLREY<lEcAFS|7JW4RDN^-{k$U|kSX?gIycg;oG73J=rA@}wQT=N
zC4~OJD1HFaF^eF$5GSJ<Eh9<~%6@);tld-z4El!MCWJbS(4e;@)7D;$IZ)J&1%w`5
zqaVtRPAD}VW2F)(`h&0xB#CqHJG~okS97<%C|{{%-#V+B{YgQb8hqvLZxc_mGG5|8
z)>~7?e~Z-o;X*46;t5>2mu8tSi{f4yDx;Ed%*JJ%f?Ev&scSD&xljf+jqj3_B;FG9
z87vG9W>tFcENZPgiR}E!<J-oy9Wmd`Rj@I~MGZ1<2esAGQecpR15!wu?z&r>RWisS
zLAX`i%c6(RxGX$Y<=~v-tvejmLwDTh;RA98{rF94>ER}SdMCyOiPD)k*Q1s80sM<0
z$fT15v{4s^Vce6ru6!zb5EJ&Mx8JI%U_Cuvp=tN8)m_G}FKkThC3uGHV1w&ybK*;^
zu5XOt$2e!AyEAn`F$J3ciX$({zkpt)CEaV+jl?%Tnj>~~HbT43j*nt$7RO4j^B3kG
zT3UP`PFs5pUFa0h)qUWFZhYt)twO$j0HP{qzw_PT#$JO4SEBEt<TqqAxW<K+23?;A
zn!Ka!Gj6I!gJ$EIOp>PpT2HlUM`$|HSebcvkc~HmpVArk<MKpxjTRFSWK%}*q|Rd=
z#bDj}o`j;(9nJJ0f&;H53!L(!L4!~x_KN|GnA8)+y^CF*_#F-QBZ2Q0bwv7~h<lMQ
z?<u`u&XYk_D6NcTW=Ki6WRLH6LajAQb(j0TLzYj>Pa!$3F&xv8yHcw4d|!lKe_XN>
zw6FOZ@0|xaOs%(Ygz**gdI%%c6-NEJ7oR`lw-J`??piolq&>V#ncWybmK(Tc(cpO;
z=Pr_l0eX#kM2jBpmiHe5KcLa<NvDnx|HD5+s#o~OUSC3HxQ+OS2XMsKZ(Dz|@8YZP
zd+tk(eqO6^GDE)`UYi?>3!_<mN7F*1fz0kW?l-A)Ukc>cu5-~8C6Q~^>H1{tg-#oc
zwB|+?2<=J4veD__Z1U8oE1)h*LHAI4^2s7LBq1l*p!cZhJ7Ly7lA@AnVOdr+fCyG|
z=@-0%QfL54FtNw8?Y09z^7oQ~-MDI!oxK~&^ms)F5M16m<m8W^PrvLWCSC9-UhdTh
z_e-U<N6+D@nwPuFCU0S55rZvwfnJ$$qbcJ%80VAmY$<P(8_*Qr*;l;>zmMIwXnXlQ
zEBjw(JO@v^O5;Jv11TUAeO=PsnY4sugb*EH)-*CEu5<US7x?~h4YnTO35JeUwK7B4
zmsLgTw?T9s`L;2yDb@@}qzRiL<G4JftwM=^b@EvxQO+%u-t3qEgXcuA>mEj{G<GVI
zC$Wuu^N~fUe9`7*TaEj&<GyyxPcL2g-BmEo5J5URQ0q2WLc!p*xhd;5S4$X@ts44C
zT#HD-a-ju30#k$I^Wxu5sl>v<Jc$Iw*#lj81Nl+seF`aS{3&bSO!J8;{Vk2W=<EwB
ztXr=gq9LTMXJubJcltDamV*Y1P^AGc<_LrLT&eBmVpAs?>|~|NObKW2hwy&VJNxs7
zdI@uJvgNtFiO}|)#dCRdGF!KBG3P6Mnr87FX(l{%EuIN{L$73~<yG$O@;B$jl(zY)
zpunn}KPFTgMr^1zk(4s;hYgxsm2hv;gdK9?Ed|GOzkf+#brRJ_85+ST(uLg{6Ob7g
zBz5i&T+hJ^x8NDqa_3pd$CtN$;YHTY>n5*l*IPA3UsPj+Y5%RlBe-HY$+A5;)6y;U
zKSZx`k(Hc3nV-kNgP57^Yjyi>j-ufZ+ly0Gr5+VMXb2!*te&k11}rQK%v5?QtRk0`
z+`q7w4J{Z~6!EuNR^I)%F2&twF}EJP_Nb_j#wyxt^)%(f+RqD9n{qe5hOLp{SR934
zo6=pYk_h@u1^!%VbgfH#V|by7kkz}bz)9AlzF|q3uyyj{h~lw;)d{c7z_llvp@E{S
zhx-fNlpA76qNw@!pxh3FkWG)B!=#&aEY;}kv8^D=*>mDK%A#GfjyH%wNxpKodT6#6
z7&zZLF_5orFnkov;+VDP6s)wjrcN(x))M1sG|@`LMN<0*7w#JsA#ERYl(q3`u&c_M
zqZj0FqWQCp;BB7tPQdPrwTI`fWvQC0+~0gnSn1d5>7PB+tuYm#b0OYOgY8YOe7ntM
z1NhlXyaUmXB*=u{zlC7WetxOG!jp7wh|ehrGzi?j%hQj%9FTm~Bs8jRVgGFXz5B&e
zzqWNh;<wO-a(A1Hv!XtW$#G{-nZvm6rqy@nF5{Z2UIFhCt8%bCN6tymaxthj73S}g
z3y818b3$yyh@S@G^RoQj2>A&2X_Bm|n{uL1TD*bV5wE|~Yx(RLJqn^>ZJjwh>3>kn
z5Ct~9bpE8|iz5m>@W0?YV3$plGp+F<n?1l*{77osT`_HPa}gH*{cHAR&yLOI%G^$o
zQ?5tpEVIqI#Mw#Hb;*UC%$Ld!fv<~HV3%;2rBkY%I?a5pmqY3J8R7yK@_72FREQM)
z`>9-Rj%7byxL?kLUm4Ri=uwoqd92d^9r8J#6=G6p2y2R1%q1YXG!#p~s7!U`p+kPn
zfZl?n@jXG5>Aeu<dh$#3XYBd6l83F0PNFbH(9N<g3iA5a$*nUFcbtdZ1e;wwpGnWN
zW-MI%?WxRb_DKLeEj<_fZ;h*pCR|J}`l>7}4q>x^skw9Co=3dlYvJxEWMDJ9XMq;?
za&_sgqX`?|$-?F6U)=|uz5Hsay=VL`F=1)4pr_Jd@Rg87Z6$z2)k+}^&-?Os`%5|l
zd33%^8U4(SJsx)8SI6g3#Iji-tusyY;aRb`No?mrB@L@BuiR#+Y^<rf^<F*)T5|9M
zj5*|2d*t1KE~}$%7{=@GnY!*nlkV>A`HMG4HKeWKTu#V^lRDQ*$MsEy^)DjU?P2G8
zZA&H>7r9>Zzt`*k&iW%+kCa0HYM`7S7^b;^-OG67pMt!~>x2cPUquh?!y7!`9RaU?
zy}pfM64?Mfv}_tN&n}hN0Ht97zT{;PJ6eYioGNuvTHl`f%8A5p81_M!-=tt-R-pEW
zU4OS%+GwDm4n8+8PkLX<1T3aaD50#4j7z^-vZyoHHYQ|r8};6O{Szn_iYRNb|0I!H
zBdozpIzZzZ5|bHLqW-~1(Em3vQkQL~W;@^V+irTJvudlhV|`upuWdWt6MM0W3hIg`
zj0nI%%W;M=8h`L`JMDsuNyZB4Z!%y#N6SXI-DdDw@%wWYojrj;HR%u_p0HPf?`pc5
z*O=tM6frd@h}qZY#0;WI^BG}VqGEe9kA4q^NYBN<n>WEXXF>((2XjsQWfUBcDBIx8
zjk!*xkPR|RMrPNhi$n|f(&1c?68(V14M=*L!zZV(`>rMFV^Y&BeUu2;xs+7o1LQ{5
zoV0s6VU1bS!W1OMP0A@=k02qKV?fTN7e9e-=#u?z^*bf|Lq2*;>lcLUth5iJ27$o`
zKyZfQ8?)t97k3sJ!qYH(NShyR3Mbqm35n*i!u?V0jVIgKM=ig_lb<yY!a0U3hyt$k
zkKFI(;s3HUkR-PgSjm_vd6R1I^1*ARZ}L<U2)ZErHleqf1N^R{r9mcsR>x<@p!V!h
zaBjX@g|@0dFoqRAU%pXMCQoOV$sG<ZEt1rWkAhH>1Ri|x_BQaFOi+_%CyIq3q<N%%
zWjIzp82X;wkJ}%p6UG%Huqu81Ak%exi~FK#iYB}$tw{;$kQT)<cK-KB=AvIiDI5us
zdAkmnz7#v%8MBe>fo4j$)&ui_--HU?yu90)e7W7ZO52p6;BCVm>`b+<<i*h&rN|W>
z`bl5oPsA{pj1d;{Suw18EZ*{<ad5#Cdl9_WUO|!KZte$p?+>zXGHGMj1*Jnp62n^}
z>3Z=orm)jXoM#9q$mg!jBpxWFw3G3q;mTXOFu1^w)ywp+{KFcA%}}7{hn0-o|JU>P
zJ}{mfy#|8lk_6y-bpjEBk5(?u+*&;}EryAFYzNmJ<kQ#k@|}1Cw;Glj2LlGJ;CbRt
z6DGgsD~7|s4<D`}deyel)!^=hJaWyu0<q;GJMKJ<QG@q9p5|u-lsXlhW@2}H*FER(
z5qf1im!Z3mBlg_0;D86O98MeSj`A|l3GB_7BA~HD(F@NOyCj`<b~K{4$L9j>@`?CJ
zgD!lT#}~uS{vu!O@2+Us!p_Z}e9Af=L=EUCg3MTML9#PqAO__f!h#R5$GM+2K=iZZ
z`+bl-A-rX`OOw>$UBsoFJZ^5Hi8`sx^X_nC^e$+2o$1;M|7&S103b783IE&UskyZ<
zs&=IWMF3&2A>C#Ms$4PKrL22<a<q<?xb=3WNtzyfMxyb|z%k!|KFheGbHl%xPKRFP
zt2`aii*M?Uzen@Tkr!z+3djbM2-{-yX%ZT%)&i71Z{UI_?s2|OX3l+&9yI;)Cn1{t
z2G#wy+FJ=bC)b#Ioyzp%eG&{5#NN(b)P(&w>bzD=OIhRzNIc@6r@{e$4wyZcPJBms
zB|`uhIX4kTU^8<HYOOt#-IRxZ^DQEu2|TAi!-+PtG8<Qr*LP;FDkEgZ^|00>YsT3f
zGV99Ot~>dUt@~m<RAXh5t~DHl)Ok#v&v|i-wn%Y8XB}3ddr49EPBdXof*Rf3JI6f-
z^V{n+vlK+;t`%A~i6-e7a7pn1{x-o}o9p4QQ)!*{KR%e+@c^o;4E&+X26SUVg6vXx
zDkI`us9!6~H(YxU;>oU=YpnH@wOR6O_rfBz@c}iDjG}n@#eI3}IDilSW+l(G3y1yD
z)bg?6_7z5T*yX9gN$zX=Wd8cLEX*rTjnHxO5JutqU};I*jcp!J<~VVN-A>cGo0FBe
zq)l}6Vc2qo*TQc4c8o6bn5a#Z$6PCA#Z)M9>r%ISgWvvN0ouQq@^|ycw0vSdYd5X}
z25Pvx_qeAgXsXB6#*ZNsk5+ouMS+>dPuCROzqNYY=u<EIy106T1wjg4jo)FxtSrv_
zjvhPMm58vQLW4tD6a1xI-|x-<s(HVk5E3t(0_vf20^(+1)9@Clc)&em!xsJvglu;+
zfb~o4pzEc=Lm4wcmzH((WdB&o?tH2VkYqJia-$N__9&2KuQ=bYwN}!1HOsjOzygl4
zoXcrrac{Hykn8Ri;cBFksOh2#)DM5OFEhC5;1d8`2zd1hH;&AIX=jxRq91GL3&Q!O
z$PldBK3vr9byO0lqEh_HP3}5M^{!|M9(WOdhKBmD>72Ou$sF2_U&I7Vp7@&h1Iq@x
zTsmu+P@1jtH%SZg+gbzHq$<o~u^VHHpV9>@p?|d9tm{TXTOC)lg+AGYNPPr^5QfJZ
zUJHFU5_8&KxAf@GPcHTB3{=qu;Eu=uqUJ(#c&*_w;gV2ke|78566p^z$d7&rQtd+7
zv<!C~nU`>RMzH(zqGeiNp;z&W)d%=bq+AjfvH7ioV>+FmyHQL6gtM3ts%_BQGlgw2
zE5=rALYYkXK3TgxhV?r@uk}eF-xMrX<eG<vlKo)z!?K;&)s6kjM0@Xrr~eD<l~R^K
z5CstF-#Xkq6fhzUS6`GAYlaT@ew{`Zjg=&A3$1k{R<8NvAS<u9KVT5@L5pThxkN3=
zLNH@Z`QsD8soXSOANQgF?R>tj0G0e{XkQC>ie<!#PCw4exz`qrt^&)53-l!=CN5Dc
z?RXqbqp9C&*mtAGonI_8D+*;RvB%>tffkz7MX_2i`MW_(E&^}z*wfaYE~CP_jHjCf
zzq(+ub;;3u@%-=^!>Y253(N)UW(LK0eQ>98ez2SRP1vja&79J5+n2oBsQy~8Ywy9g
zU6yKmC40&W_FS_`nuJ#nf0pM&{bKD01vGQk9!9D$L_NS7@$6A9j^sq0pkfX{Z-Rf!
zIsbVszoHGOfb<)9b)ED?iE4fjNV&i28tmjIwHzp&skLx5>7<^_*x8`^?^X$0O&A{2
z+83edyaC%O1*eYq`%l8&a|c3s8+Xl1vSZn%vEH#b$^wo;xSko@Z@Ny<PmgLH*X3Rq
zd@&iQ$XF9$La)6U;s1Mvf^;=Boo1a{sgAvEAJx_aRFr$E9e;sae)39(Qdd;>m+d5B
zfY~a+eH}=ayU4ZbI~ZPzne2F3bS(b6zdv}@TQ<cPY+pOB@6+Y_WNbfOi2f#*M_6W8
z>omtoU9<3>KFo%dy@P=*?0U35jAo@;rhNeN+4OV2ybZ`F$bFFoXk-Cs03t|U4l?~C
z58v}Ea0EcgB>%GW{2V6#`tl1PVV$dS^3NLOc^_0cB+S_O7S}$%*tU@kDQXXm95llH
z^m)VhCmrGGa1F_-5GCwt@)7``zR{8z>j%Mle@sXin#jwSA{zZl#jSCH*XEt_Eizej
zeAbHx=dhYSJlu`bZsanOIPS)Gd{vi5`9b1QJ$c;BXp12|+tA$V2v7_Pq0%<93OxSb
zZL;-a9iLHoIQ%4e)_Z#2Vmo^4lx!vd&8sZ%piU-w02&GEXSp%tbX@lHn^jJ3{A%_C
zspgW0X+{SmWc;knAiH=KMlV<{sa#UW4G&irY(FPB%U{^}c3$mY{tOHlw>ROUvCImE
zR7PL78G~0_?LUL%w)l|chAxw_DEaF*-&h00Le>bWWvId0MJ_8}$}c==6Lr-8p(~32
zQChQpfYP4RzAn3Jj-=hUJ7H$&LPaL@ijwry6TW5$Be~?YV;Y`7-}1zyrOb{FQ-qKB
zn23$BzYOFfTfC1;+4IVLu2|fd{1f3R(bTmmw8vD+TCr$ZyXJY*Yr5IuY{=R|h_H#X
zwyI-+1);~1z^}*DYK`mE=H%W9LcWtM8MT@=GGT1iqha#ar`7Ua4$Jp}4Y{)xRnnwp
zwJ#JySEF00+v@Scrd2+%@)vg^5tF~oKRJ0DBU0&J-@>e($0c?mf*iVHAy^SfGixC&
zFEB|hOA3*Bc0oC1&5*fg(4s4Wo!Up`Zq<E#Sbwz<ObK%3B2BPava#M-sf8cz-Z!vO
zx<LP6*!-zDd7dUnqxb2$;7p^1<>)Cv@Hmie2DRYWe=#d&Q*_{YdrLx)k!5X*bi1r^
z>E39@5dwT>sAzt>*Xz*#>>fyH{Lx$7LJM@l1EgBN9JgwKW~Pj6eN0@a;5QSXVC}o1
z=Nm1qQF0Qd(Wjeed9!bQ&u_)0)+gwGLxc`SO_XU!A*Rwj7Mx!<ty?fP<z3L*%(>9K
z_V{D``C-R_u2Nxk(o_cN&wA##-FwEPUnWGN{geVvZUPJRTB8g?S8U%|vJ$%_o#GIz
zTc=ghwxge(xAJGOFIR3J+mJgt9|T8AgPH`H2i?JME6(<7+MrMk;iy-Kfau)?nI5EI
zGy6PcWk}X9XyqIHd}IF5^ekDfX46i5*Aj#I?(($r#Y=2BNILf&h&}h?kBr=@_z;bx
zQwOzG*?DPZqzfA|gsmTcWU99?jHM?2pV-{<txoM<Nq<WHU&8gwE4LACUwbWo#fqMG
z)&y*=hpG5)cyb(zfs)srbm?<9ruwDx$W;sZXzv|N0=`k}A+D*?^P;&?HM2lBMU#3g
zV=xxjWGrZS!-rP;PHg$@o31%SVIBe~hyH`dpWQUf%u>l%Zg^BYF`13D7G_qU!KxHa
z+oIE{?7+e!DNaneZ9XLImy6O>u7~4ZCud#1pKwMbxEe3EC|#Tf3@Z5lpj}ZG=?~X#
zpP?(gH#k_zJ@qgJj;_VLW={A_;UyAfNPS3L-5kqR@iKmL)Trs{?~_d;GLO<Gx8uTO
z_~~pBNLrM0`5Yz_MwlCRCScj%-8E;G0%fB@&mutnI*~AW%emFj0;2E>Mgk9jn8z^4
z{KFFF|0$kh;xfaROawMx0m3twLZe_qMG4K@8!JhQ9SQf$rHL&Ein{=?%%%NsCWNot
ztmPZdaP{6k*`7~n>+9Vu3Y9{W^tDHC(T@4@{$<UNRiIXKg+XZvY(3PIAJ(6CSB$Jo
zF|6wg-!Jm=btB4!dfs3^g;y;8K+)b)On6MJbb>xyM0=coh0L1o*=$@6f2=6}CPsQ+
z8!}Fp<~O;TNd}(U`0VP1>$ZbOjpyV*qZ-h3eSd|N-Fbprw*YT9{~{P8<>>ln<x#3{
zGt1e*GV}tzepvM;dV3pkigLT|z{`W5v5|}<I!6*T2aV%6s3af#mm--5hMxh!E%P}*
z_@oJ%Z_Iyce91AIyM`(cnb=S|KImI_h9JNUE40rAHGb*tmE`5oS%;2N1{~{6SIdU}
zqC?@Ta4njm@7Ibl*YZ3LcwPObOyjHdyY4vT_ng|=Bl-g#4#u8qQLcj%nkHX-FPPyG
z&uH}K97R4xCK-tcai!oQXJR$SXZ=#s%j>$wb7$g{&ZkXwwntB&YPjkHfMDKtZZ-+t
zcA@At*L+(!oS$?PF`FnxYOVu3=dbrD3jjr)$F6^hWT+#O6Pch2j7@3F5^+b-EQ^7Z
zQEqT4t8S6Q$EV`GOIeku6p-{G5hYNBIx-GG2@D1~2de!PQPneQBk=<eQP|>OVjO%u
zVgNsPeLEL`Mz6MVmH){LMzq2AH350S_$o_?2^63Bv)Hd13ZZoR2Cv1I6Bf~}?mx-*
zZ(jw*L=^nzA|2xC$5{JV@<IV__lLn~_wS!uc=i5#YxYz@l=}j?YU3A)<sz}@zI?5r
z1U8l=&(J-!+qFC+1q{^QW#B{grAgJE$_)th{HRUX&6i6{B?VHz+Dm7S(Cvp6z`BXU
zmWc*Oht_(vG~&gem`K^z_8$->A3m%CnzwpAg4r8=-&(X)zYCFuY&9@2ofF%bIiSt(
z#Z>rVqg3k!;d-0pR-#SyyPzG9H~9njjxWf?cmu_R{(^#?Ha@^NbhNkwrFtS#w%0YX
zOzuNDkMRdkqGsLHzfedhd{*WI>apuxmbF~cdAiqkfaw!Qsw!oJa`z`}u{}$%-cN;5
zDK7lldqV&SQoQKU0ryZckB<WZ$q!8d905K-T7~KO62=kqb=!BJb$I+0r=7bj%i&C8
zXsiw&Cwg5yQ*Wz!gt=T-WD053_%`fpq~qvP@$#O2wnEb6K;v`4ZLYa<)}x=}!OR~-
z&6YicZm+yfS(!Y^zX^G&K(l)6BrsSbI>nxkMoO6weA=#Qc)rz%kjNj;_^l4f38MX~
zXJLBwf3pBh>Box3%+=^_@J6A1vjA`{{NQKVYw#=3-V7mVr#;^JZ?T|T|Go&`@<D=F
zuRt$|on*TJ7=GC4GX95$-o5#s-2dIy^YbMi!Pz0upd_hTLt^MhR^CLq2%sQ4!{ckj
z8r)m&n#$YgD_YMTsbZCQev1x|mPJkGNKn_G>iSIUPdGHuDD?e3*lz>k;-Mc(zWP|&
z;!d?}S^C#}^zDsjh12hB8M)FD=Il{U2{#tXA9VL*9WBBS=9h9Wud{_5yg*f=B;QY$
z&jG~SWWl#$v*!%Da>y#s7Y?cc+3Y#;XpuplirBbB%D#w%9N)qkZv-yR+>8d---(B;
zoM^{FXe-c3hR<A?!;UR6s~RKCw-#5OJs#ROrDG(hk`9)SyZX6~+G!1zju3cgb7+pW
zBaAdCNo-h)e$9z6`0~o*EHTddzn;wy{0`u^_Qrr3*LLfNIsqQ&I|G)Rs<;66pGM8q
zwY6!CPX$nTO8f~^_IQ&j0B)kj(GUh>Q44c_e#qNz7?-T>FOixV<V~9S8IJi`aYp%v
z+_Va_e6od2?1;4*XH9?is8<YxZ$$||-h6q~(Rlc*Fl&OKik(TBOQ{-cvuwGZr>g{A
z<!pUWOKKCaECAXY2z`*HH^7}{6tJFPu``u{jvb$Ykd~Xl<(}NXwS4jSRW)di``q)R
zgGeOQs~C~Is-i!=byLrx{8=_d_@)T6cyl8<Tdc*d!Ox`Mwf8v%H&kA=o|p_OG8j7i
zmJTEJw)yO0f%fR{Q{=+mqmS$r!qSqGNUNs$JXL~L4?rwZz}8){{Hq9!k}5v>AEW_}
zP?+dz>Ty=m%;P=ld<M7dSFtdU0=2DdXh_J>kUY4Xb=<u~K226xfk>fr(mdZO_pB7|
zsd)%<$p3QK?~nio;vxLKd16r!EuPZR$Pnk_VCANh0`B~ty)n}l!qJc2Ni}LyF3xR}
ziKtM#c%XRM`}F7}6}k9#VlP`XWFg`>V1-qBp*0BHQ)&|^IQHH2gZm8w)HZi*kAX&M
z%fm%ha>OPD-c3(qWTrTzpUOKDtX}8R69c*Jvgki{cF|X=jWhLb@H;(apsElNjRHww
zyFYr`O=I6E*~<?LLKVl{7MTr{qFXc)9Tw#$!UT{`cB=?i6XG9B1lCtV$il&^e|Asr
zUW9?c6~hYH-Ng4-E+x{8DC`)PVYT)~n8MXW-73<kxC2}BDp1M=Kf|v3_34ef{cyGM
zmZu+Bdd-lk(S&iLRtwCcX(`k7sYs&YZrr%8uG-l2&T^&MmOIyBPlTCuckA=c?@FBE
zV^dD?hi~Pn%G3i}pXMuA%=VZ2zcQlQnbj_~VQh&bWecOSIU8dO#_l*>2_s??0x$86
ze;Rx@9yT~^IL`Q;J8m}YUl%eLYjbGX-u`g@peu7l`IY8@ThqbNsb3L72@W+LYqd=2
z;c@WyGwL2eRLdZz$)a78FmnDqU5;PlZC3=TC&4znnk=4zsPhUA9%NFsLVN`lO3xsY
zBm)&`l@>tOB;m%JzJYRi0S?wmFi#2;VYz8*ivKIZ=kuvgflQLTQb2M^wn+gd;mBTN
zl#iL_M>V}XUQ|DtZQ5!t{v)_S<?zAijWYGvA&3^eCrLtsPO@%hd2u)zMtKj$j84aI
zJy$WGcC?7`8CBCR>_4v}{rM|YNzf|(#I9kRCQ~F|l~ylX267w8&e+}B(X%}h-&3{K
zE551Z4NPDJWfZmg?5Mbz*O0^ATCT&v=yw)y>o-{yP1pM~gkDwTMLc~l1EXJ={O}#-
zX9qX@=tOCpx>~Ng`Z>XwUSitO7c-~+phwp2{MBM}mnSwnnHnP}ZQ`(=jIIC1=%?sw
zP$Git>EYX+uQ{zc+(tD|eMf@kNanFu<B;_x|G(Ps1;4tgHjgC%?Vo*e219XGZ6pTp
zmuEGn^GdQFHu>=neYN(2RSWWl$LD`g=8PDUi#EA1Ujdn&=FUP50N{?tx?cOk9SF}{
zt9O*=MElwBj#x>Xe@`OuWveq0O}x#i2z6_`y<RU{;eIIbW<Xn%dC{uB;MtR}S-P9C
zWC;vOx!tW?9TQ>8*UH}|=9Of9bbh7#fKLqd+ga-2r$NU9IN0uZvC9+@Og2_-8dWEl
zVK*4(a2%#n_2Q!aH~f#3{yXM~AYYZVrgK%J4^GiNN(QOzAVJf6gAfkkRVnza{KGZ`
z-%uH^=pBsXp=B2Cuf(aLoMq4j{Fhutb!&!debeAY8<{l-dfg`IMAnjtv4s17In?+K
zv}Kz8C0_Rate^U28^wGG5WGk};eWdIfay_T65vX`a|F6qC_$Jx0Bk;RS}C`JT!GV8
zmPdDT0wk0zcGux<z&fjGn>Q2?HB^c<KNDMN?QN!pd3^m4i<@%R$&YSF80I%|pxxE)
z%udii3W7M%n}`{cFjN1q3>r?W3A||`>FJkt?fdW7$-$Sq&T3tYn|t3y+rD2Csqu%W
zIAJ;%0IqEzqJ7)H=vzv8MLLysq>@Nqk^o2lxoM6V^23aH#H~^F5s(5L0pd7kmoUh7
z^;anDL=4De%spFKm>Og&T9rdm#mGByDj&AS;Iv^$iF)%tTaZhLg(b6`w;*`Y#sJ8G
z0rHGtt$-lZ`^vMgFn;r|V>wd&Z^F(|2+&~h1lh!ug*emRO`gEk?@tZ3XdP&&i*<M!
z<4o$JMNwtJ!2I#?bpZ1LkWXDzV5a3fFnD@UTC6n8=%ZT7ELSXBoGBOEb5HlCL8D&3
zdnk93rwYO&WmJEvW7g#Fil9dqrAkb$ae+h7aX$PU&%2&Ht9ENJ{FG_^<SXXXn){Cx
zH`pwilU1dhbOT$3eM^sBd)u3l&mvZBIpOfJU~wy~seR@Im-fIQxVBA4xDz3q>LEyn
zK_S5nE%xOQ@h=FP=Yyes^7f}cm%eQOkVG!^t$n?N@$-miL_5N`zRLeu1Z|y)RUZ$v
znYGaWUmmcW{H40`FV@q5F`7V%*X)1{Eirz>-SFr8EjyKp6^}GF6{y8jqTo2&@ntr1
zJl8%pdyMHDYJNJMHJ^}00YZOe?VsG~uX6Ls!n3B*@BJOnt)uO=Mci|!ZRj4s-apzM
z<L_^V3FNmdw#&pH00TBw)3N35SuU~VYEq49f9fT<UZ%4n=+LNP{Ld<_xV>OKqr!OV
z`wZ(hHVO~K)7C5X6*)#Z%q4TrWL}ntEW4{|+n@NGmeu;ZO?A)0(%U%A$+tGaZH3K4
z2YPv$9|aBIS&&YK(Mj73UfB<;uR(QPXREVS+eryP%De$y9}w}Inl@Nrc!G0#E+)zt
zvt?j8t`9q1lyhtS24Y9ZC05`j<24T2UhnL92_jpdQx3GT1CUX5z*GP74CDcjmDT<I
z5ae9&fdz6;@y35>@J1%vHlqL_jxqk4R}LfoAwW=iRg6OOdw!djr~l3S?7c`BTutio
zu00y(&f#>;kEu5yRB$k3Lz8fA!&TW!ajV==d!cCDCf=iMpV#r=Fxw9~C}kx4l(FOI
z_5_w1gVUaJ^I@eku+PsLv~nnj&Pq4@KJ=*F(Q*1bk``qg>gtho=N+%u#+*D-6CUQr
zHCku*E>cBd$PjtJE1uNoPjFsPULZ<C(!XHrub4&)vkgC@Ub-PU+H&0Q5LA76uYczE
z`094%(y;lb{<%l%xei%UjvPaSYz_QxqB`b=EkjR3J|g;a_9`UC5wTtJospBcD$tz&
zCO2E~Dikm{RZ+><gWhYCi{_+D*L?Vq9p)&-uB?|+O=TDUW&6l2V6Jt_Sor^fWh+K}
zH7fIN8SunsZ_Hl+*ctMs@aygvFep=FG(ngn^kuQSZ+e7R1pmi@i}Sr_Jy%urm0Xv$
zX63!P2?hD@-Ms>jcXa5-S%-x3O)w7Ma@L3*{bh2=i3Mx_iZ`=Nl~{Qed)a=|124dV
zg6snzic~tApV^9Dl7f?2L10Ah*iUlA{WhOl%TfB}qsDzhuKKif0;9=wWjR%J9gEJ6
zeK$~N%LxU(qQiCtslpx_UH**k*yDPoruwTC6bO0TKs&(x5j2-HFQaK&z8U%~W7V%t
z3X@^D{*&xgC*oXgS#cWrr(?sg+qO^BtK8mMB-Bfvzl}nA@sXxFG<4<f-PUF&(Wrx#
z*Hw-+!hm8iNmVuUXWbI!uNFD|Z7h)G2XZb5iEi7G4?E7>8ItGv4+11-66U_Ua%#N*
z;x0(g0W8B}rO32cTT`tyti0|Z!dbrZW$6xl^8JtmitsbaFuT8rl)uQc$2ZGs%U$~A
z1*o-YN`C6RP29cMns>EH-{GsEfqR!by+b~+=j58iHPI!j7<*{PjWau)6gD!g7&jkN
z+Y<bFY;{GMrnG;G@;7)^3iyCSw7kW3r6b3a?Ke_8dSg!1TI6@U#BahTq@3JE-m}9u
z3D<&dt3&dmGjR*6^EU<i_>qc;Hx&`@_MSyS$66kzIV3Ks=k=65ILz@{lon^e+_Dm=
z@leU$DEx7t-gdbg$$Z}$SK8m||0g^GG2|X5w`KzN6U<fcW|<52V}IP;Qzj#wqT2#8
zVBZLEu*)GUBr@Ni)m~7#z&b^@nwDMvzv>oz^ehd?GhKUvG)&=j%P8vxDUl3I#-pNk
zr}1zhLAM$nu(g>%6Tg58P5v$Ani6qE)aF-{#bNWMUkp@B6>Vp}&7O<T&<n|aDI+z?
zKHaXPDx))xHgC-u(FJ<I`H>%8X`{SXil}w?AK9qzc9wZXJ~nT(lcV=^3;}Z{xDHGW
zXAY-1KHDsBIbB{f!nprB^i3<HJ-|*$ZMZ8WSSB~Vak6_aF5mR6>{&WC3wUK!t(v~a
zX7a#x!|~E}_0ok|)wrDT?92J3Pjg?q=!vLnPkcuxZF!h~>&KUw!dd4jbLsxg$tSaF
z*~t=P_B9M)43p#nK~_P#z5RGyC<c1#jeou?b5)M0RcMP*b{1sdK}wH9WJpXkDL>8N
z!Pzy>i@qBd=N1Nwf<dsIWd!|Y>b`I2txah;mrP84C@M;1m?`N2Q%J?p{7{a~-;j;}
zgP|d|*RN)@7}a4Rp|^hc0!qND)WOe|HeM?cOTe;~J5$L~V3&?iQRnPX7-0}p*U%;m
zNob9@`D8={ZWTmn4ZI6uDidZ6U<w*uaoQGV{k_im0|``(OtY>Jt+@oVRsB-1)8Ca(
zyKZ|C3<SH62P<)2+S1t*$nmC|KCD6oGF(=V>=`j;Jx`1qy&1c08?@;jgnb(Dd1^!V
z0dBDMhCcoLj-O47?*6=?saXzF5y9gLza;XhbWC>Ica(zsJ1&sza+20I@v=5awJ}$Y
z3+(+6(}mcv`GMQDh7??h%*?Uva>LN!qs$QM)o1>gF9)A0Ia$Lk>qF}4F)wLpfzfkL
z80d)e(;#mx<E2$Ee!H@dDgi{D7|H`>`>->`ppz<tIkpkDZrJ8iIw>I)eO~@gcH^kI
zricKJvczZuLmI}OX+Bm6&TCcvB2xPU8TrS(x-&>)hBnGP)~PlFe@o>dR8`Z7dbNj-
zcX)hU`3-%GD=c(}-&)3t>2Nlb7ChNp0*nPQ{;V60+v^v5tkEZnsu^)icF9692kOge
z_*!dlEs&?XJ=dSU_14zj_5%}G@EC7|IlM8NGFkKD$U~SY1+T@2(S$P&?e4R(_WM+!
z9gTD{MMz55pOW_k=jys$ptV_?f^-Xa(mqHJJTtL|PM7;O{G@ErSW|x252mXX{oCaw
zCi<|!SFWn<SVOoY5hF>OT{^ZaLn5x_f=h(ew~5LfCDu*e9xay9m|;lE1>P~A(IvgN
zjJUl&l`V;zm@FYP%JA$$3>~t{heyNENjh8wnKA~yAlUKrMUchsC(>AZSaj7L;eDDi
zU)mp}TP+ye9KxfA>KtXDAmbA9Zx*=MC(_{26^Y~rY`R0D1_Vy#hPd--G!R=6OAd*X
z5j)T=wph2H2bJc;Mz^2;QX`cS4Xl`KcD&PyPqe54cU1#=_fMabFsHb3Sj2%!isEGE
zTJ@*#3^$z^pF0|}-r&8?*2j};*5VwU(?gmW{<5g@p(HaG<Hl3NkC`HZ*P0lRIk@{#
zbB|}ND=%lSd%Rrer+>l=C5+76cyi7!7GN~#rX6EzqNA}<_F&xhc@Ee>6QUdh$#Sae
z^uKSToxC`6abpUO*gSL#D|vTjz{2Lg|Iu+q)XdA+@8`vj*bPYr(WMPw#Be(k|9b4n
z7-Cwft<^;-XyM1@^K=!3nP}roOsq%$bk0>Zyjgs$Y~PGP=_Jn|dp4k;bU=~nv<?L4
z3i8^2`cL-m1{9i0Z-Tk+@>D7+jqleMU&_<8Gz1HpYx#_7)zT0Q8<K~Fq^-562t>+P
zOh=f^HnPUAA}i#x8GH9=*SgA>5zLIcXUMmjhb$#@sPf36Xdfg44ZWFwSHD)Q&*_tx
zJ<!MR<+s*(X(wuVB&QvOT9VhjFC&(g$$U{QHsWPpQU&ibY^D(rv-v%}-?v1xdU!wB
zwj;HcL`j5I3$i7DP=t`;BDvuOZjD?v#Fi*fb|PX&1s&xCjusy5p8cJ;#x@&9fMjFq
zR(r~~0{z1=tp~E^zaxn(CEv5AMwi#kjvD?YRjkBcU<h7c$#ho=j6_D>{}jxZSMm$p
z4>Z7?HE-{9Y^t#0Dx3wnzL@9pRo_?V%Vuaf1V}!6MYDrEt{F^0N9{(ctCV6LY*kOc
zKAXIv6)Q4*J8#dhFl)5(Ss^?%1xB~d86#pZ_qzUVqm@ysVUiBwq54H*vUTozk}hp^
z#L>M-=(FnO=)(68NJkcD4(80Wr)>&@b1plUa|ivDb|1fAwEW<~F+?~Iczyx)bA*7e
zl+=lsM1E7P=R#SDN+S7Q4nZi-I`WV4b35@KK^r7-kbg+(zh9(!^^3?}_xw$KlWgoG
zgzD;9=RoQ4p|ty(TdzBKB$>6@$+qH$EIbGQKKG55==f+&q~MxYr-oD{S!J5i@?p$(
z>eI^&{ZN<9tT0e1lD<X|HycyJJpw#@Dvy6%tWrGPkwUSrk}1+5obp#$XpA<<Vz|<|
zm3Z->-{L;)%K8-c2L5|+sV<~R<Y?9{Ot?^X*t%PmKpcrk4D-hpq0C|IN<oCwil-ob
zSerAo@(RZ^MfH&S#}qngcfE`ONZG#3gNs88kA{o37U+x5WMcU2fBcN#g*BS+>hqoB
z)JEcaz?4)f!$k-7=vPSX<G_M;%z68ZwT9r+yU;ui-!xs%hwc5yK;Kh2MU<LNLHOf0
zG%Y6CfHf3$`J<!30nZ!U<1THxo)1{i4^;UpbA-u!P2vw!Y{8-*lsSoK)9)P4FT<g+
zJZXO)R{|nZbV%HBH&(cv=XA=rtT6S-u|V~<ylzE(hl7SFb)j0LpBIUp`J)?#aOV7E
z8NcI%A@qe2(fE1EzyXNf;A@c0TT`(^oZ<KBfOGUaZbuZ$syj^`&G#ENH*b)Vd3lk9
z2hG(T-Ms-hR7t08*QQu!9*`_AU>80_J1v4-Z2&jAP4;%!pJG;lE%i#3?CA^Q608;1
z>@giZ>MkQ|hbnTb2j9_y-%?<}@bcFnZ7+9!aD2e1FIvXmE7n;>jGeqTI;x^>b;XSL
z>--zi>Ye#dvaWRkNIyNnoV7p8+uBYU922)(e)S(>KN<xSn)di~Z65+!ps}qsueCUC
zrPyvNg%XLj?OdN}2@zx(*vplTaaGseI|>wezh-2A-{ysm0Ka<Udw1x?l+KL|Y@aXv
zOLe{b^=lRHHQ@(hbi?L12eH+|2{%j@XY(UXspqb3tG`sVY+!k8-N_Z{!2i4ET&wx>
zJSmn{CT9w+mfkK{_lM`Z4g>ncFgY3<edlR4%UAA!8abRgi2+gnT)yTfS1-qSH%QrL
z^_{KV9^Fph3hDXMEf!+o)|gK5KaH_`HZl<&tO0~ew6v|DEr6Avd+`Fx9t;Dym!oZG
z2k@LyL4tpWCv#|9iv@r&F35T1ODDpczgbB+(#3~l14Y=B_zmdE*v=SMiYJrugPoEV
z9fVUJlCO8RyFG3DW<(y6a2=zbd(BwbD#B#Wi=y17tsZCScq<1M<6i7dPr1(KCOD*a
zI4#07#Htx%UGXvar+Pi6xwz$R%UHi!<7D#eVSSVzlKe=jt!x4P=JT?`NUKSj;I!e_
zcm@i4({C@-xyLMSf7qy_7N%Je_7nvH41-IF73RLHPHgb0AJQJ@alAD8Qw+P?^!IUg
z23RcR6^o1?dD5oRYkWpUEzgj<%+$G*F>AE~OF8;hAHIF=xZ27U@0Z@=Pr|f?@b5u~
z1<ob1T2rtz{;Q2DEWw>xKzlF;w6r$LA6JB|(7hNK<LUFixHcngl+GPE%n1BsQ2AUX
z)#0ok?SGQJ<ZG9E!*8%yEg!^?eRKV-brRKYf>l~4PNHtys~Yfhy{Dm%8-+(y3Nf!h
z$%S5<4ie~k+QAGexT-t3FMKOhsH`)vVa_*&e%YEVtWLkz+w8OM$LZD1szZsv!D1R0
zoJ!mwNvOOzqCIkPrn@+`Ewj3b3s{Ab0=#$fw_RQQy)rW-Cu?_`1Ulj1u?%f4HX*Wd
zJvUV?VL$&dbegN}{^hFT|L@;T8tr*yU!jj%uIdQayUtkdz_T<Zb6SU!NQVffaF9X3
z+k=SuK0$`-QZ8Z~uZYAYfGSdu;!uz}>%D!X#UkfL4hK)ZHJNE<1^nP|@`WzC&Kadf
zX*gyP=2B+UaYM)J9f+o>`_JqbQ*Y1Z-8fV)Cl}rO1}Px+n{}yy|2jr>purGlf8|Fm
zHP%gke;vfHYL6S2_aBcCiVrloYg{Yx&J?IF!VcqpEpd0Yv8V6^R&mJjjO4dGeHNb~
zIpe>2C>kbt_Gk63pkV)C;B+K#YwSU^lEgyu>g1~xtrKT3o?GQTvlqC{6{R0XkIyFl
z5eva=_u@&#gAXi)hV+)ESeP%5w7l3Jc)SE_!1@JS69*s!>}IX@zfMDO8e#U_Gs<39
zx1g^ACay~jj6g}a1Jf6CMDtx&`5?GUdiL}~EUbKt*NE;oa}Dfz5A|j!O+~R#{t_X}
zxc88$0kT2gd{*pk+Wg`XdO`Q4oWiBKm4Yp=FJkj1T%#i{qjt{Q^f2F_Bmx1<53o{h
zutj3xeVVlF(|hoRS&H*cMH)uT#@ShStQ{NCZOvu#MTC<&+@^0FNO%gB&H{9^$+8>t
z!HG8vZckeA5Q(#Sh{%vWg>-xw%G&0+w$uL1tQb0`c43jil#lM@Tx~g=iU=zCnYvYS
zo}tn@uc1#Y6SBj}7J|D+m8+N<?>6o%x+-T-cKC8l4c6lt$T3_u=0woEp}IA7Oifb9
zKl~3eaT7{jebjZjumD=o$irjRi*gB6zsWH(2a8cpQl}Mf<K38Xxm#cUED2c%^7wp6
zm>qZijQXs$^$;kdZ1SEr3|QqNGQdq#^5AARiq)Om195df#GTmMv1-3~36#56SW`-l
z7jL86+zo@LeJk<IlqC=2qJ1*P3*TcM!eW-)kQPDJ6^87@){g@#r~XJaZRyO6eD{(6
z-E{Ci_k6&Iwj#O8c&PuTV-<i3`t>^oUjA@!>YrHR*gbdDNqi=tZl@53+$tA?J#$3B
zSz4TLpS@6v{^jt=!Ub>~%2p_DJO=kK;To&vOyn15u%;thszTNc!Hh{b`50n8ebo&|
z^K5DKLsOY?#L>)<B?fF00)>6p<k3;Mg@MZ3fFGR9o`j#ydGXifEdF2Hj$0Vj1(Im=
zJz!Jp6C?sg7l#5@*!J9gT7}~WP51gm5KkJD?ZdDy)ZV17DKGaeWS**pQ5Fr4_i&*3
zQq}R8B^cIXXT;q?JgG<Sksct<XA&L9NyOsdb2~F@#bI|mDks;9t(zFv7p<SBrQmuT
z?Mvg@e~qth_-xzhmk#W0LO$kzrxS{EGz(v3uqq*D_dobQ-{GCU|EF19zDRZ8)aGNG
zK71m%PYk)F<&a4nBRQyd#yL9EdDkh+iNgEF#p3ZGK5|=-BF>tLvFqh2^&(<{)|tr*
zCY{Yxj_%~0hD2*kI|v{Zs%E1=1{ns}NH?WfWJFwX!RJ=+{i0CUj!zFS9Wd0*F3q3m
z|MzOcRS`;4{@*P-bKsU8U>VN>SCZfEr4|0xSJF0UjQHJg!C8=e>wb=cz#&iLGm@d)
zx8C=0x_~~ol#ELqd>=`%vzt}FFjQtSJYS_Rrp}2jr?T<XvJ~6~wiw2tZT=b-YS6SP
zq<~Mpa*w?6YtDx{Em;0PqP{zj>i_%y77`T|QQ6revgb8Y_R8KPJ1bo4ib#mE_qx_a
zcCxP(vI>`L?-17|u5s<~dtJRh-`_v!ulszS{W#-!UYJ0A-$1py@<ILqt25L0)`M=N
zhIcrgtP!Ollj`eLZv<y2uFgMwv`7EpYikRQgk?b^DY8<)kyqLuB~|GP_tRHf@u25F
zkQzF7rTp6;6>SFa!s5GNcsPG9`%8EFn`68e(Sg*ez*}xsq|V-akpOar3QafbT{9kj
zrFkE3N?m!cDAE7<VAMltJ$&-J3E)+WTfZQ4?zaUv)smi7>Q-{;u}H-JcxIsDcQ;rb
zp?QltnWwvc?hS$KoQL{cu9{$BoGf`=iYl%l=4<0{uq-?rNX8Zd!~8f<I(Na*3PLOU
z2AN5&)@58H>irTs;*-J2Pv`zP3~7!#?|i%#*!N}mRjG--n_md;t8dgRQ$2>Oi3%0}
zn+34@>8W9tYX8{wr?E}AzZq5Ykd|J$eE`*;c#Z|G<u}eRX*Fqm?*LXDS+(lB|H-qF
zZ`B&#v4RLVH(f6%Q<{8X_%~ti^u)XMkj_m;Pe1B^8OKxO&Y~26_Ch+Ky#VxJsDaVi
zSY>N2R%mRO!4fMM<8!DS8&nME@kpwGGW<dIqj4USNP~F~<~lcH3m=Y=MDGji5X%Q#
zMYxw{(IcnNrdrhR#|xC|0}?|WI!j}dU_K?Ga#+K{3|=qBffh-Fy0XaD3`Xm@aSlI{
zj?ziN9~K=P{T#$xeI9Q9uL$F|#nAkes(a442qDp=#ca`tCF^Bt-;<#y2ecBO;&!U0
zzc)IH3Y+>H7P&aWcvmSRJ<BVfE(aWLHJp-f%~a)o5$O{Dud=2aemVS5gC7Nb5Of1b
zrFwOTRr07^G1_@P8a%^#=ORJ6f>RcKjMeHYxs|zM@KegFz!i_?KfrXk`$!m&ZriC5
z1jDAIy;%{aDY0uFUd2i&n~?*-y$4AFA3s4VvENh-;xR_;T7?;Qq@jp<x3AhfW7Typ
z@6g+poo3`4YCr2}3Ce36z2WpzG_{|r{4SAkuSc5$<|B!jeR@XTf#f*bH!-rR_1!fN
zm;~fLl2$sbDq{DOCxyLA=1kXjDKy(nqh^i`shRN#shEix@I>Ry(b}C@ZQluEpZN>l
zkH(jcA$&AMUEBNDBOy780I-9N$_{KY9Fxb2M1;OplIae&knOaMFKl^gawS8i9J)Jw
zZ}&&pO~nV}50@#@0ad=kK4|u>O?p=hj~4yw+`7t5D&#Ce@<EB|vn+7|u2s&z%^AJ9
zZQvV>ZA}~rV<dkJ;oNboCLAc{sXylNJ0c$|3R3j@4CCc`Iw-l~_lzOGSvkVfFy7gw
zL5utp<&oBz$Tqrbjxh-uqsrG0WIrjU{qdHsm2@c;d_vDPd+}0t`$s5GC9@IlJY1zE
z&2nbDZDCtCSRie+5c5v7#)f)PYW*ccN0(;`@8V8KxcjfkJ{&DN!f#Nut8t36h7YN;
zBvm?b{(7_J4jM}Nu&vd7ZhB$vn858JU#Y_X;f2l4q9nYg-vTr}0K|LMP}hg&y&CKE
z`C_@;ky6_>iEkW-QaS&le2NHItcHSt-!a;JhBYm^S712l>cgmO7giFXJVp(-&t@t*
z%_iL1-}${Ms@uCT84cUH8fp8=z%&2!jM5fv(l}?OfZ%*cwh432<KdnYVY%_49~WQw
zNZ1~6OL*;x6PGVP)0-E$9FkJKhCXLStykKj#1dKrNw4)N@>qwY2rfO!8{V}B{64Ww
z+}{dV8?7G4JN4l;R-(jK8asU;O(lzAkop7+N6Bv39X>!8HXFhajf2a=bEJ^+9a;HB
zGlogOi;>5#K$p`{c&8q#@yk;MAMC<_U?&PXLgTR#nMCp$2^0NkM9qt}^9Y1<`@~vc
zyj7-I#(L(|nhx@v-`?wq@yBazixL3Qz~jEcD>^{By&hk-${Xf|Oonoz&aOUx1a?*+
z_96wgUO8wM+UM3$tylEDvo_VM2(Jp)rTyB%8p>y)`#B{tH;IRQIy%gbn!lFvTcPU-
zCC~cZaE;9G6nwPZJD%t>=~uVWyU#zE_j~a^Rd(hu#7YRCnO)iDo^Y8xB6bT{reTYW
z)Jgqs9z*Hy$s8caUdYnn23b%n;tQ{mzte3l_j?s2`p;%QN`$CB8I$0(kfQX+W4cq6
zMhzB+OD484S>{c>4|^&v{H=JnD6ACNZ(*|_cau)+y-B@u2Y9Bkr=&o2o$Mp1&#B8a
zg$T-fA(`@HerW4Qg=noL-Sk{tPFH~HC^a)QAL8pXRaCF>@pY1g#&Os0fZ-UX$D>L0
z4BNDPzrje_(?@q)O5v`$V2_kyyF{w`IjSl@b<7)`ZDXD7dl@Gxr=Ek<%Iiy>3S|>Y
zTOW<aoHc$OFH!&tV68ISJXnzjVH6AC`z2r#wU3^S1GU3ZQrWaM-P9)!qkP&f&V8h1
zi01xRQOpdFVZ+0|8$d-7dv)6vh*jF6<L;kdKUel^yq&t;q4?Lz+di0~I6CeghG~vq
zKrbEGClwHIOUPlkh_-;z6<7f-S!WS*`Bq0GYBV##HAB^2)knIl$rM{*l+*MHQvJJy
z5UyRIMop3iBL%OQ7=HF2qp0%V3zC;BAXBC+GGHEl@#CiE%WKd)7p%F-sDAFAPlxG&
zk%W+c$>R1YheVbOe^lu*h3{&Ym6X@fb>5h0XlISR`w2>_RHjkBc1Bu)z5;B>B@yj1
z%T_Z^eWm$g+-2gTFN646y6sr1-~X_FOUMKKnwi2I3>A`~r-cB{EUM4z@Z5QJ;%BAq
zNRh~GSXI<9m^2Wlrw^I58H`L@0}VO9awtfPlJ0USuW~yQJGjNrlU!R`WqrC2ET3_i
zv%2%G$?o^{J6#iH{;J(blN9OzHvyDOsTIomi)msSz1dPRT|6H}=oChdpsJz&nRA0%
zu5Nwy-8ssF7e$G$HijjC3}eC)tjQB?anyFnAHC|@o}GO*^W)Lx<JY~7PEo9QiTtRz
z-M?sMO2<GQTJuu`nZgt($|ksMTDLG~if(yMa4|mN@OShS`xf1<ycPLhIY|k`pa>L0
zinIPdE*%L?Jms9!ZmzSXLJYYgeD&;=TF}UkThnB$rjMT4JQ%)JASMcpDl@91^l_bg
zH&fAa?Z)ar?V(!}7z<5|Gq-ZZjf2A;U|ytqpWDX>qHOm_(zX<b9tqBg(DEo=Yk?<x
z5$98Ir!|3pPHDavX}U-;V}YAAyWh4;oYB^E`@?BPU*R^af8f>hR8b?lYa~3}eeFA^
zkUFD>t0zUyW=Z{0GtaWr3_YxEDW!S^@WKO96UNyg-F$OR%Udz?_120%-J;U|4`KPQ
zPE$O=d!q!4OJP#PWqe^{1WUW3Y+0&@)RP<f$fzCBc}7txfp7@94I8jFi7s|(ty~c3
z78VQR-Yev{JL4pPMCmTRJ=uERzt`Zmr!ZT)Z(L^4*u3>+m6sLBXtQkK+*qu+9o+vg
zhfH8(MZ`_CBQm#2w>|uB?v}y+f>h)IxXi>CyFMIMk`r+6A#Uv~IMVIuJ-U=p)74^V
z=z#6QeD4^)lt1qN0Z_y}=4SR|Vj8#+=Eye_Zf={IAss0&sN*%`8(MBHw2cf1h`QK6
z!@fZ;!bH^m%TM8tkFLkxeyUUsv_bg@pJ)S6TFnIRz;zcqtbH7oOfdYgo~~(M#Qi~e
zu`^`C?om@+PG_q^$kf_M&@FBQ;Mr>ZuT>`zD|3r{!1=~%AY15d^JZ3|DRIC<i#9v-
z1B?<?W=%iDDCY^`*h_zVwXu)jF*F-F_qCtTJ5k{aE}=YoWepbFYiXX7{=WB#H8VS&
zRU4%{!fKgUMcnQfOD>tZrUW#)EPlR;k#KK{*etfz+dtI~8b1*dn)k#;H(el9#>Kz&
z|F4dlrk09N4dAZV@J`oJ9p+qe@7<`j3{nX9Vyik#`-h29x*4xc@{b$d2@$a3N{9%;
zb0u#?-!os3Ccyah-&wymTUC4bDa57m#}mIQ%1ypNr%;H_^bAN^+}3YMi~!2kbRH@r
z2!3eDY+)fRXy$t8U3}A8JU?<SVn4deyOJ}q&7tH|-kDRJ6-;l;d_Qi7U&`mV7+yS$
zKMgY1ME25WtY!u*R?=2qWSd2LR`NlZkre#i$7fEzu)svb+27Oo<7n%-|9gV~H`uOX
z2EyYs0QL<)8dnW<@QA?wlVK$NsDbaK+h2&)I}7F2?9UU8%pYhH)7C1U?W;isqomI!
zo9%?RrV&J<=G9lCj4r%8ZEW-E9on2-ad`qy61a3Xs+T`O+S0_j;~P<(d3AG<X&77E
zc*<MK<}BmO(WSLB++2qSu&%kj*hjfS<l^23QZR9;PXs-hFJHdwKnf90Q=xO8kWctX
z^!Vu)`aD2K+%~!AlX@sz6L{qtU*MXVq|9($7_lJoe?61kf89<Azk3`=lHxFB0lnws
zn^~A>(?(M!X==Md6+x!o{*J5A(qAFhI@NHprS<*5MlNUE>U#wXd0V3cxPEk|bO>`1
z(y~wI#_O5d40j;*8@Bqsn6nyi{j*K^?wwOnt>mTvvzf@Uo?xDk@OS?lo2FhhpXaIq
zqn-CnUf3wzpn<_pwHCF`UAz}ww&^UWmGt2q|JEA6l&9}~dp`3>w2&t5-mQ`Or<v5Y
ziA96UeM#sRMJI4x;)zTOk1=l1;%JAVNviLE@$EVWB<;xZ{<by^0NBWZw`BNSjAA&~
z>*{T;Et@4jWh%tTw3R*UW^L5Zm%;=RKb>(MYB;f9&Yrxksep`tX_e{PQumEy^~qL8
z0$>xy7#)gbXj9yPUr)G^)2qBB*>*N*B2o(;&VT#><Lxwj8(VBhkY-N#+{g}UL|vgm
zRBRr~OXP(--TW$Zc(2w~i8*8D&BE~Vq|YD1?hN%ReyZgcg?@6)&zGbqXXflOo4g@3
zD5+j~tkCkT7ul^hd78x*ffr|3DXl6h!NLDT1;2Kb7zcQT$ADLGBlyw=v;otK@qNH+
zoLyOOcFlhkSQ9Z&lBQ$-6bIe|9{vRLO_35Ja)-4%EswU-dYW6M@$2d8o#)?gh?ZqN
zUw9F9mCgYS_m^A!dUrEfF?Mizzg~|L<DPJQplb&$u>?9JB7c|k+LEHfgR+_6turNG
zXYt1Phe0|5(6^=CvC_QQY{#vL4X(6RImx-mJ&tR1f%RQRXuaQ!*K1XVpP8KrQ3fvJ
z6J>0<>gna1419{!JKD)K3lKHh<u*zOViKgk$Mao(j_Tw1HEt6!EDw>MdHo*yNxRk%
zFe(Mt6;*V7#60)+-u);$iXoN!+=n|uD7Z*B`&XvyY)R-%pmWy~1&qx;&JcaMmp<kd
zKF(TR;3i&P(M+`&zT23mm6BH_#XQH5-x2d&lb<~4jnMZdvU9R<Uvg`W{xn`Ucdi#*
zlwTj$#jZaW@GFei&#NvnGjbL4T)cZgCmC_pqxq{N>COwW)*YX8NBRo#a0k9=`uZ7(
z<>t?U1;V!BUph|tj5lr!9Szi$>Ytx$wyuPC8;@@1hynH3O8|Y6x`n(7`1Ss$0M<$&
z5ChiSz3+$o5d3Ma{6g$6f|pC@rQEajE!g(y-8l+>^HX3fcum(1&RsCnV>MSK{FCZ&
z$3TYYQZlf>3g5}?#9YaOxw(A0l4WY9)dsk7_nSLFAw<>8zHnyq`58RpLs$UcdQnZ6
zM@K-0bIJ7`0m$&XtGuQU+FKVX@ai{cj-a(oZF)sw1>>Rio;NQPC;buX-rzANIC#VQ
z)3lmCx6?PpMI?Y4$y=~l*!!+81W5j`#xqKMSuPxH*Sr*5l;!)EpstQ~m$4U9Hl2RK
zkBC#8>$DK{s`@j%WW~ekA_$WNY-o1jmR0rrq<5D&V<$q>nm78>ui*gVowe2w!)j+v
z*ZF1=Kr267&N~^0*CaPPM((<PoF-qt*SE?mfcnV1b2zN@JCA98MTsIPA%4!j@bv6`
z6;x1$^46*O*OnimljTD&o|k@)r9Z|!tN3I-ATSU^*BRkSosd*Yy652aQEl%@rgxWL
z+7rGK3tM%4(MH5BdDb<0eU&zJh@_9SR(Tlt|0VyU<k>9v5hQIuT<9wegg~*k>b5}X
zP$QvAdV*M`6qoUu0$>MO6)VEyXB2N`TIP74SD1dNAx&E=RLIZG+qZ#!b=+5({pv?i
z=VlrMylNk((;!wmm|c5(f)QW_J2js9p{ffWwbPM~kqM5t5ZIn-KUM{gsR@MbvdwU!
z?iBR2y)0YZ{`4tk@mo~_USwg&OzO17#Y4fyj%K~ahU^+K<g{~^%T|~1S2m}74+1%G
zz}Ml4qol_h6Bo$()}31vD+M1fo2UOYaFGJPy+G#&&<LUd{q@8<L+(D?x{K|F6jU*n
zEw_r(d&eCNd|SkQ3i$jn?v1L4(jkYc@Lb6qv`VoW+~*#1n#y>kVYCa)gw;%#*W?$E
z=W~mY-kW#UiEN!7EP?-g8DmO3)qYXve?}#A?{LJ<dQNNHK$&6Dz!w<7F&FcD$OjV(
zU93hAJBu_?uX=a=wo7mF*t|7tKKjbTW#R!EQJi?v+uYi^;ER=<4=gl(OdR^ZT8x^E
z*n3GJ&=#*=W^6_u-G9KIrC3)O+;;|ZXiKQQY2dG%DFs%*L~QLYtXv-yVKyg2n_npx
zW@8h2*r>!ll1+i;`}O_!#?dM;Zw(oKYT6b^2c$1#6BTA5egRR4&Wr$-3QkYqt9lh~
z3%)(_%>efEUE2i0Ze7r^B;_}~>P_{`udeQ*<s3=aO>J*~Za=HyV&P~QI9#4xbGa*_
z==B!r-iz{d4!+r0+rmbtLLME{A3FzvgGHkXPH$cakNQhD?49=%eKo;L1Md_PZe%~i
ztC+xL_VtbU(|gLhg%F>K_=!xjxGjE8+IU#OQ{$Js+a`XM<B9gb%N&ZdqQ?Tmw*qL#
z1G)t&D}$XTD%$IA8F`=d-(L^l(oW#Ui55J-U<{3I3!4haLZM1=Q@m+9Efj?(G$N*r
z(0kz;S?wQzHF(>_)eRET<1ae1NIm77(pD<~7_pj=;0`<M#>j)_-(tZ&ScF?obadeA
z|IeUCsO>Ia)2T?C`hec6xj}h6^tO$9Ugdx3>4;m<G5Rd=N@?H59JlKXLH~IE#l;S;
zDI}bTa`>zu1rbUc|D-A8{tIX^0Sg5{Uw|qZJ_w0A8^-K&r%ce!@#H;KfYw#m$_KH}
z{}ddtO8J{RFMs@iWd9Mv{CcaF(HH8tUK=b)*JGH}TPB+Hv)_)H&9C_>ekO&}kpo@D
zwUUlz8h2O{AAL#7=a%A{p@%18LV^BWsDihDt7UdO^K~YL|Euc7a=wot!6&^W04UhF
zLR$$;hpgVMVkDt{bc_CUmy`rOuN@m<F4F(n%jT2q)Y@}TMrvZlYNUAC=^rMV^?=9t
zSMZOW^fj0N03Y*JsLyEnsf2`X|2&WuoO2WJSF7JQiK2r6&q?*Izt-<`Xc#zzmQpN>
zy;)b27CLnVq)-dpcX;mh-f#BL?;Cqd=QI6ce3fh=@5WDPgUI=ezx+B3+;MShnaoqT
zYnS<7y`r~2_+R!Kd71F6KGawJZPz>o+EP|e{K8t$+4^%gSPJ__$;Y6Yho&V%4Z@fq
z+5j};?1@qo6spiecm9Y&2ti*w`j*rRHT`p?2ec%pdWj~I>ki{I1V+rF#02T)y$LtN
zpSCC^*Y)ehaHY0wc*63nt;M_#XaTp=Gc1UHebVt<=th`sj05La^{QQuIlI)R^B-M)
z;|9l1HY>{4otmCI1sHMezeQ$?VlSY03%1k7uX4UrcY)1c337Oy9|XM5QxG#yOubH$
zrLrit$*Rq^U&Xj->blhzyA}8r*rPksG@*zF5-?fdNyD#(t?GCT_h=CpbIa4Wwo47;
z{W#n~9(|<1m<xAS>y#i#eHie%@4mDreW(54;#yj@m_J5^1!hvDL)_K5A`<F1YM$|6
zwZgm<Tb;EyrTQCc<hw~L5ydaG-4hVi?bdb~+wu!TAN()76!83qgo`b|;8y{Nce|Co
z$yMUWH-2ZQyoJ!5x4#i%7Wdi}SN1$DYHR%Wie#UX+bf}5PLw?pn%ANo$RqM@?hiQW
zFHhHwD1V+%YMSV$v@Ptcc#PB{pP;&RHvdDBn)HDF^RQ<MpY>6{IIw;)d=X&pqRJ`u
zq5c31c`?Ey3*hYukc8Nt)%bsyks>5=S!1I-f7$--_~JNa;k@o_t{!-?dC6KEwhs1S
z;D2mM?ZJUWzgU8VfkDOV$^#)Lh+5x<gZH16?BVSC#cB|UG`wlS;gvZg$Hz0Dh69Br
z<4)n}7IxCN>iluf5Ez~rFE@+^JR#?&90Rmb%t(m|$^Juuk>&D5_?>d4kNX;&P0uqC
zuSt4#|Lo=iTeN;SY>4;I+*^JjRhSjI;xEqPKmL}_#xE|DuUt2vDCzOJ&#hk*GQf0F
z5!X1*vipCIyr2Fu3AFionP{YmJQI*|?BV{M%wDD@;RLpz5rUV%8|qmyxy7@h=3Uqj
zxl^M<ehN^PF9}m2eOhl%y7ECmVcLc*&Ya_wrsny&*|}=Qb_gcQolUYc`oUt@R%MCh
z#6t&>3^C80yBg*VA9SdBmwq3A#J5GeyV<#Fhshp?oAQ0Cp3D7JYM*NFelH0tJ<<%k
z#kIJHs|;{J4~9FDh5l38r@cbKn&$wc)wlp(5d&%fwn1EHBH6|5;+og`@-Xkcs&ZG}
z)XK3T$|kaOVrc3XpI3Q_ibCt86G|vCo+-dRYn?eo%1op8xdp0PUAqMOH#Rcf&qD)X
zwQ1=yUk&B_i9Bk{G*Z)CGfJo;CbW;o^<TC;1a@kQd7ZyYS}7W|_&%kYGJNxyd+mc6
zf6bx?f97mbQ}$<+f%sAl@jQKierTbma<NYAv-MZID_!~jJL_ulf6iJ6h%NQOyP2^V
zRo**^iEAo@A7Q$KFV6Dxl=EY`ECsuo<W{ZH8;8x<B!-%Rrqdr^b%$F8LJvz`NH`0o
zWeL@GV}P}dfayy`@#vUwhK{MGSO&lfT3=1wEi*<Ca#Qgw{iI^LCpdCzQ}cMpyb!^y
zHyYB>6?Z37D%(EE0$@K7c9(h`6o+w<uHnA*n`$q^8aJ$=Il`?(YZnk8(7ZiqrIRdF
zHT=&}JT1I)*_2>QAje}%_@mIUS>!FgM8o#5rB5DJ`p2avEFlIgP8LQHu-f~P5SavN
zrd>52D=J4uIl;L3_u5=YB`lY(K<BXWGOkM%U*v&_zZtE-IthJw+4r){9PwSnYj0tR
z=tfBmEsu|XUg-V|9Z2dkgNnW<*o)sD8aK2lCEqgLieFiLVUHcmXA$2JT#$L8XQtOu
zTv|$f?<L{q0y%}ply@0BuPa=A`KHqTeoVk8HYvNbpGzAnvyw2Y)!9W4WLBu8r}NFa
zss|xaPd;6tfyeWFyMK*<=q{u6wJ)5?AD*A0v};Gr%;wBa<J~WMfBfkEAX?Yo`^NJ)
zaM009kH_sV7kBAsoaXub;h){e!N+_Xv%4jOyuhCyB~(-?wRKf-eo3xLbg?Pai3XJu
z9rIr$2AtOE&<hFge9X?9(enp;Fau7pA7m1PS3n?8&c&S^0?;(@!k=Hc?Nt*QNd3v+
z*nGqA{pblY9U;-5*H3Q>HdA9oqAV(Pobpx2o)k~VX~af1ly3@GA$fR}*=Y`=HXlxr
zjU2vuiKVBzN%W^vo}i%{+Kqgv9}Ychuu(1Dkf?7NJZszx`uk`1>mXmHgNx^gSYV|R
z=?|ZSBK1-Rl=Exz^4umu)Tej9=J?uH*ZD@=$$+bYdP6{TpdnrvmnKk7^;3*H`E+q}
z9WS&KCi|e}cT@=Bj(Q}$Q}dCx>-hA`wYcEU+KeKv1(M8n4opmqlBiBO=<dUH*@5Zq
zLJi)`k-kvRs(|JECgA0antxBv`rDWo5$72}5w0FbVF$juGDVw}wI_B`*lLMU&$296
z(#R0Tq4kq6{c+Kn=GKa&+FOq+%bomO)X@g|HD8+Z_I{R5&rYjkc9==J)hkbC>_v$T
zT-!Ff;``@l(t6BT)|{a}fNpi)>9<5#ar7SJb*|{;SvDf9UysTB?%X?Op`2w}Jc-xH
zuSkG$%;qmiJYnIug<NgggMs!CYm1!}G=mf`iS5~2`D?N#p8oAs!<IwxMJu9spEnI}
znA9OT3z*GjoZym#7>6JDn@)&APX4}J;*VZ-KpKJ#7br+)d}6jx6>)c>qHj7ue4pjd
zFvQ#>_t`FW7|<`stBo>dY^_+S^(rqjxcKv?nJ%%?)!C-C&(_}mx2TFo&OC=3u}^iI
zj7N-xmcFHVTOigeHJnK9%evU0Vpw?C{3&+fZy~YE1Oc9oHTC9rVh~3bwh<YJ`@AUu
z5<-fB{X5xrM0RkV@!qUnIj$Ei0cjprGq&|;LLi)oYyKVSgUW8#d$0G>DGzFSL49&`
z;$bQB(fMY~oe$|A6chhpW}e9=7j^d3HH-h|PAe|=rA10^A6+EUx;!eqFpqX-c(F-1
zu27H{H4rJnZ8AMMi&`B|7OAVNsnr|q)<4^uK94GotgEXx_!R7VfP68WU6beL(MQuz
zubLL@+qq*)KUP7ump)X_c>SGV^zz^K?V+L5i%QWmH%(FTJeGgv0fOMIW7%Sg7bNTS
z)&2$FlLG(W+rN#bnN8&9wn+p_sCBUlKHiAokwP!>BEiSra8**SU@lUjXR%~Ix#V(c
zqtwe?oT((M-scGJf4TdXCz7}1#f|j6YnVoYKk<dSd?gOAdA)q>{o)y~)2HB?mh<x&
z0%vFzVx{yh`3fT1{y_)I(QQR<#n*5Zj}aMNfqd*uT#pj3x1w7rtJ029RsNy6sZdD{
z8;zQ8AbaDWs2#xM_q2hjXL#uL1+5~w#)UIjgm^<ToSL`oXkvy>CQe<0(c;fq9yRBV
z-(AA?iVd$9|C<E>$IpANeG4`TJno)w6%yphTE)vYhy~At9|tOTU<7Af5r64srY3b@
z)+D&UJ<ltrzS#M}G>(PFsyDK-qvqB&4Qaq-cL__Ji9CSe`7E4v7}3zX?bG*AJ(;2o
zxg5!Y|4iKUB9D51FNG9;z?Tnzoom(k%m7R#{vN-PDXtJewVx=TnKi$CEzT9!&AVe4
z+7_ErMFSQp@ON?B5BU>~Tf_A^X0^%PcHm}IQaruqXHFF_q&80OFn-?K;3o;&u+ZoJ
z$&1@1f9cfrAS3mx<<n0#>6mwn*ME!EOOghj(zylvtWT$dMSJ3JAZt#z1`0wQ!6aER
zuV%bJn_3X?T;OP|vUqOUcapbv?;|4$sNxRxy2tveNk6}(-%@acVb)h`hf5V}i<n#J
z;ZBlD3^;pQONzFAmmBYX)hvr$1oXPQLQhTR{|0SB@n?WS@a{~j(4xu=aBAN<n2L1}
z;pCCw7{9#LZTBp!Lgg)bjDmr7>{hBIDu2bb9<oZ(6(T!LS|WT?JUWvp9L+HOXgbb(
z<X{k&b=7z_`*oI`<mY7zZ#PjM(K%(9nB_+_`i(JBa4Q=TL$f7ze&!<P?amFS=X~--
z;`sA(^zcM#14Qy*E~?CkK{Ky*>KiG*JCwz_6fJd~^V4gQkbDEh=xZ3c8r9nG(U4+<
z2Euz>nU8;xFo+k>m3PZx3|{bzb8LO<F>&1nK7N31id=<&WQ{5kgkCjW2W3%YpaR$%
zqx+Hck=6PBsP5=%i&>ir<OVOAUP&ochOgBw+ma1u7}B&X;uweYwdfoiJ|pxchIn1D
zY6}mZl*VQ*Q=SEDnmRT85^E_jv#_VojA0xSy+_C}+vNXu+~V!ohJIwG>VE{8T_3sv
zvh_>Zyb3bBn}q_8pJ&Zd%zqKKGQ&*|+98HJ?+F#T2jE_Pm~W7VHccqRl;~d7duAXJ
zG*3y`?$_fk&5J4YY2F|3nW-Sg(-OpC?m_^n=|7y6kJp&0AP6!Gu9N&qfz}iy{!vvP
z*7=b6h|xzBp|YXiMk_TP#haEaBU%>aS|SKfdommMdnk$QV_927zR5}K&%pa9e>O<3
z1}MtC9yyv^8*uYqrlA79)AHZVN7iJCL5Yj%bvHnk+0|zZ%RF0E%sRWV4u&Jnq9@+#
z<{7A#TCd^G5aO!+VFIFCK<LfdP$Fj`x@Crmc1EXx7?tI2^N2_9k#II(@Ve~tpCgu~
zZ?3rpa)`h-%Eu3?PFpuof##S+LYj^faC>*jkaJP=^OP#cnc+BkvI!R-xB+rRBb98@
zu0<Z)mvbQO^K0e~;R%d#R!BtRB;xI9w`iuSWHQ-58>!DF0K#!e%7<-Q+3y<C)mh%e
zwWB5)95n)mq3jhOTLV<KTybkbxnw&YsC1}9#ryqXr-=lKi8x+81}vjxIRwxS!uF8p
z<u}@>0j%#v2DaLa9M5*pz$1VgHS1XbH-@@0dl&e3wwn)p^hKd!)G<DO#C;PnHWTGN
zlVhao0ozd<`Rvy)i+)=a5~vWy-6Nqp?}+7c$}O7&Iv|F(1L)Z?M|<%MA<0B?+wf(v
zdZqROJfy(l{Y_Wv6eRW1twL|%!>(g1nm!gcQnvvbqRBKCJsAx1Xd0%o7KQ$p-P8#9
z<na`@{yc9Z-~JkgZcV9@BpfqVi!$P)ljWDY-7gvKX>yxT)Z)!zsKwh(nSg=h&GbuJ
zI4JNxeXq>{04=O?jHu4R*WTy(i4~fjqR{yr8s;M<c7)@%A>8iD`?cW>J0G|xFS*;A
zQjADp%21rSPVwL#uf0EQ2V`=*Hfvq$HlZrOFNy2#GT0BWr>M%~b7*<>Umxk6=QAsp
z=BLGlH$R;>NH3PN!cB>w<l7yPxb4G7^r1ATBg{q5_Kr=R@=MQ!lv1C!C@a%p_FMO$
zBYw9L$s-Nb%{DSGayEYnT>tH?iIx72y!K@K9iw5&@*54g*L$#?9pu@@M4RiBxB4Yv
zkgJuSu7J{){I~St?OZ0V<b;Pxe4`0j8X8><!%e2L(}=7}2wE8*e%}ycy&f<+8P)1J
z73QRH9${|Tejp&}Nis6*wr1*<IJDEo>ZpKXXAO7-wL5TD{CE}r^Eo$e0x=deRDB)-
zSTnBSJLg<hZ#Qjj3dJ$S1;pRPMioe{BsL2^TZ~M>rduAuB_)#xYi);0vx{@zO>1yY
z$iGNtjO9v_%`my=qIXsAUC!LVHi(DhootfIbD9j3!S2=Z?(XsN>DBS^^X#`PH~c0p
z`Dgj-wct$<2Vn9o@l<%KVr;zg*|U@F6$hmcM%^Xm;^;HR!Oep9FE-a2YzH7YGP>_%
z$Hr*5;=uc?9PeZ^;-y!V>Xi`Ou^NHvgZ_Sew=Suv+=-_K<vdyNyeNRjOji)dz9qRU
zL*nL~IS%&v>LdSwUZ&!xW^3iKDvTa3s<C0t&0=bBV7ix;`V}EDAUR@9Fjw&~nV6LF
zd!ZZoQ^A+d7KWIG|00YMgdSt`dxjTg1AAJKHMI_xg5mk42Lw*0R<uMsEFO}(X$-;@
ze{CA3@V+*4;Z?`3uSwe;i%OXZoSLD-4DUEO6?x`gnWQER=8|)10oFk_QXHGbADt?;
z=ap;}Tr|Sn-U4)>RXJ!bf4tP!>;_2d1GX_m^&}U-b+|S|SNa<x182Ye5W@o*yIo6i
zT6WY>)V{n9$3z`YN%3T`_PZ`twuoqYO91&Go!jHtZsi^Jz*x)@ic^^(4$=f~lJP>f
zaEG>D{yqo+;<LR1BHaNWGRMz50|^L0-gp%KdGk)ls7|%_Z`e2(;dcu6D1yXTd|rvh
z9mPh4dkbjUm-ys7?g(yl6p1RsOch*p8;T&$UZGch%Y(TQolor6wme_{)c(@eEw5CX
zUjcdSfqhKxW<3K*{Adt?4!Yw05`>EusBOT$N<+6cR`s<Np(-!xI{rX?B!VThbZ<NO
z)9wA{^;B+@7@&!9koxIs3CUTK=EGP=L(rQ(^O6%NrOW%*kW}hl{`#SUay=mEZ@&b>
zFb@KLJumXAWN=d37(gqIEArKIw{%70rmw6r(U3E15hDgQ!W&-&H`<uL&pSVDfAg$e
zbe`pwwq#9T_Snfp4y!UlO1>k&$xWYG|JLFwmx{{qpi<-CK}^aillX&3YqGFnW4!&o
z?1(%XYczVw&^G|5rLN(i)41ye@2T9hq0^H2s@man)$8V0sHORtzrWL8G5I1t=lD+|
z-svf~b0$<tXqDUZOEeD8je3Ry>KELx3Odx6bmcs6en<rB?K+%AD?=x}>163^P4Arz
z%mVRa=zGmpSjc)y=Hd>@zu!p?ddviE$y-<Kqr>dv)9qb}B7Oio=gxX{M>1GKW?_xJ
zoN#rOxha1{>ZeAmIr)%}G=zmH_<TA}nnzJEp1$cU+J9z``yT$(pbvLuh(I7{Hy;26
zdq2K*dHn~HuNwAU0#<9I@GH!>kjkh)BaU8tLAhD>!TKC}KWUmK1otgAiFmP6>UBR|
zkr`JkJco)`f1`p311Zi=87;J`<TaxYTvqkA-1>dJe>uN4Kz;A7@Hq-Xi<aPQ(C`3&
zz$&tB_lF5<z*CecUT;R~N(k|n!O56AUIp3gf_;=wk?<EYwV)v76P~RpCpdb_0X9DO
z#MPN>WxejeR<|%3w{BlpfeTzy5_MeDHt-q$(5~&@so2~EtWWaQ_-!wS=`AGKqiy>j
zv0qJrm91=5&KVCjzc_nX$*%SKN1XH{@p@In>4D^y5k_hFk`ck*N>xBXYOQEQe5*ZR
z6umD80r>3WG=gAP+zz-6_i0ZYv@Is`9D6cn1@@{jd(2`GT|BwrAF0_#&mg=gKKHb!
zu?5uPPI_1antL+c67QJ+Z}Wf?U;K^subX}$h(E;g$u{X-5Mu(iks%(Z3PeFv)voxX
zTWeLOl3=h3R!0>3L~-YV71Y6}X+o(oFu7F&`alPKsQsixkWM65BAwD%vxPo8%uHp2
zr_%B9lbD$Jz4u4glVPWFw>fzoZ$ZRoM#j;lf*zx2mH^%8)~#M~zZnDUR(izxr9#ie
z7<>eQir*mV;%ck_5;;mn9p?n|QfB3#9a|cZg766qHwh(d2*^x;(3g~Gy`<1bjUc9*
zb21;9@hEF0s;9oZQ>v+^n+d@rORl~!uM$Kr*+KI5HjnbjXSfL+rl~$)AGY^6@e*R(
z2Q@z;1SzffZ~bHq==26~OycGr)<zPrxDp>KV!nY}!tR_AY<<L*G#W=Q-75w8yG?&9
zr}K)%zUu3zBkcyF2df5QpSz1E3XCmbhwN4Ejqgv!j})U$8at&Ts`gA(t`Ft6$&YNR
z9c-o6aqXIs(kEof#N&*VWe}UCK6?s4iUnjDAzO(2Yaj?65Eh=Ikbn_`(#O_oww`;7
zkXc}})i!;xhOzTvuf&dSC}R3<p~GrX#Ei0<%Qwdu<cp|EC@OrirV}@!nEcMOpLi-B
z9|Zk4H&VB_m3tx4pTMFC^ckCwAIsmi2Iwwv#$_uP?Q{ajnI%9ex^-PibN1w3p+6qv
z2FXpB`HX^sDu6)ls{9iWd(c-F%?+3co#*eN{`LXzLfVUr0>+lW;dO5v1L*RD=;NT8
zMW=8dqnwE{)5TH>(lNb@X{U?Lgz%1%^%&RR>`v@FF%{}Cp)f}mkL9Gh(oTu=$wj6G
z5oCK=I!%B366gGQmF3RB5=2c%pJ)N~^s2ok(aqFt#r8sY2J2Zd{K9X;U`slo6we}%
ztOaIE(ghTx*NQ&3R?e;m(v-x<N`K*XOkiFl1w4Z-6x+%OmiQ{Jl%ieei`2NeVGr>e
zN-@~lTA{V5pcoxDt*mTm-SgROJKOoPa`#48!qweT{(f@9Y2A$-Wc-Q~8S<zwX~?Qo
zP&Y+J?yCf{Gb6Ghz+6()Prl>NmFS($6MM-Oq9T?6Efnz2#dzgxOL{5C<;^rV{&%x^
zR*VFYCE6WZm=foGE%Net^p-s)u6CFb9$o>f?oD(`?v`rt*EWE@(h_5IDq!an03SuK
z$=_y?VH*zr={UK{LZ2cU!M8i-kok>C>u-M6&Dk%N=QaZ1mtEQSFfsnaSd}UgDpHLu
znEl-l`m;u*H|OjSSoj{!Zd_VZx`w`|M^mZkDfn5;nc=nex%hKglm(Cq9O3$TMq2PO
zPnKbQK+*#wJ97;44~AFcW$Z1ux*Fx5C%J^Sb5$d|{?Qv=FH_D*1s8=ev3eI4QO=jj
zS;ZG#g>Wv+8L51My?(ltoAFRO+%DX?#}iz>GxKKi-59!2cAn%W6o-B!EUURDwQ$^E
zd3ZcH6w%m3!N4i5={6ZJwBoORn{Xq3??umWw#vyCuK$mAaQvmYo0W-Td#`|8(EeL(
zu{dRbeX>R0J@#lf@_PmcW>ae<{ily=7{SZ^Y|puQ9u_K^fcG@_TRl}`u6^(mrmIm6
zl^Ca}fH_T$-a)L*=t$j<i5i*?O;3a5^kgrjAs0r`4mEpHw6F|~LBF&z%#2QvD>>0&
z*w!9T@H++xk9l^?TP3J7)UHnZ_4P|>rmSsBdIKyvf}JueBk_6$(Y^iCcZrx1qo6r=
zXThw78GQX|^&@tD{jjyq`=#9nHtIXDSp@ya#ue-2<g1WAk7<`opB!srvX1KC>c0yL
z->yN=j?Fk^k#m0ZVEzn>zShn*66=wA#q=4vPQ}{o=C06}BCKa=@EGNj1AsHftKpZ>
z7h>$TQ1!0{%N!4@18y>T+d)#&^RAs|CBwa$xU~G0-mbAH9#47b#l>jh=#qTLt|ruS
zt=LWoijRUJw<n}Wzm~RHwa@3>+^GIM8LM|}4?sBDwv-NCE8o%H=*{NrCLpDWI5_C8
z!ORR42`>c07Uh&L)KL~H(9|smo*!$jX93~lAcsh7V;dWW08klF#zQ+b(TbR@&n<G$
z2KJHHSq@9Clk@ZYC>ritDR-h#2`NvD1Y3*>2-mb5eL}Lx=08F{*mG_y{sE3&-{a+%
zB7f+eLJy-c>52+i=_+({t2&dCe~x+_fBp<rUubWKtlLz<A01SPJEW5a<#4v52bB>+
zc<221Q={K9Y%My>lcGo;Id(HcP$`DUaAz(nZ60i@MxoOjPX5EQc-t|6-ZHtM2Gok&
z{#(p7>&W|HUUs<kSF^W*^Y}sUoj#|0A3!N$dRSXDQTD9hCt$&*vE#e=GeK6(PeCAu
zU;bO3EMR=udrhHg_6>UyuZ$9(*t=sJ`SE$c%|LgyDX}|Aa~QSyaM0W*w5Fb?QwG-A
zL5!t&hNPvcTgos{at>X)_)z4&!r;vzd6UieYgXCGxSsfPD3IHHn$yM~W%*=>^a>~^
z7~6PJ3BP!WKg?Lp*?Z|dBX|eGEeG|@!VP{eQr2niX+p6|j9fAKVK^i8#=+Wwo<67c
zS99*hteBVoa)Tp~_^R#BM__<CbWY46Yk&eOrpVq-^zpw6EJ3cn>y0a*@nhJAl5t{9
zkN0EH(7@F(d8$3!*5(b=1{z-3=_<wlwcInH7r-hf2g#Bn`6174=MePa&qFlz|B~{y
zE8CNTW{xy)YaTZ0R5mp2?xiAC5y~i0KwO$Lyw~vLoaj+6P+tW}3>?l<D<P10adAI<
zhx<+|2`+T?j=~*@b26tDLKe=&{CAH9x(s|O&FTvVaofRtDXP!DMavBh)(+5wf2eSW
z3HiE5^Gj)(4$n3;Rh>%RO_|AVZTX-RKhKBpR+dSHrOkaYy^P+tD0+k_A*dz;P)<I~
z1dyhIS{&G0c_o#Qaj)5lF~<@kog+>52FA(0sq+}1Jf?Gfh#zE(5sIO|n_bv)@?xsp
zPu?6RrrYuUPuv@+V+eb|TWo3^PBDHf6P6ax?ahxTZ0P67FZw$mt!oRO;jHB<537L8
z2Uildx<v(0NB7`ksv^6J=plqg;{zO>wW&f*t$kXS1{?-nC8*}3VTiD#1G7|jHWx-{
zc#beFy6$zy#PgyuvxJeI1;T_!8W5c_LeChercbuLQ7kSz-Zcq#hDn?9`niukTvij4
ze<}}><$i+<h=9Az0NCIp)XxR7e5Vh++Ny-|dtkP<nDA(%X$GSbV^MqzoXgx#%$BVs
zlK=wFH3))DI<{8lE`EUzHGA7MJ>3f%78sX`sc3-J#QIH7qa#jFdnR;mjbZ_|W>uTr
z#GeUil5SHZ1pNk3QMNKP3&`$r7HR}){j24mon936c4}DH7VZ{(rK9RK-Jd&KxLKVR
z_N?1&&TQ|zA=)}lY1qunIY)Xh4_F9^u=IRs<-2a1*=-iKETFH9tp_~s$9QQD43+Ys
z8nVB__+Nz$F$k2Su7cu$A|#jN0A6>HyFTy?YwTa@-f1&e14Q|g7DN|G7j#vk<Jfok
ze0)M<K|BdWM>nb)<Z3tqm<5kP$|D)G%}tS*u|#gM$}Ju$SkKJJ@y=L1%NY#*U|i!8
z<Z!v(y8_w;AL_-o;tlRTA%+ffeA)~|z+jzMp0&j^;Kg)KrviJPpYv=}SwP<MHGSZx
zi6l5Oi0*k!O>(1+MyIDwI`F`_m6g@Pg~&Ga*CJi<6cpw-Q_x*JLs1mQprok^&4$mg
z%*lWSO{)IssbRazBamz>I`9Qb6DS{ou0`-GEhvXYs;9ybqPbNP60i36R+~_gG&zdG
z)Sp!$pYu->8<YKTL$2#WF;T831&MDUcD}CjHX4)1B*G<1CxXfh$-tMF)23|y(~_Ro
z+1Eh?gFv;Sq$2b>=nErY0_N3Hg04=lpodq@Ff-wyMZTJ_*w(pzotBAL%KjNa;%dkS
z+dLgQ@s%x}O3s?(<H6|3;$e9g?{u0<Elb3~cllIA3&ptx3afI00>YB=OxLACO1l62
zcT{!)juQyi-*SF3z}d62Hy%Zjk7*kqtdAzOwCpETW6Z_>8u<?VW?cMShM6z;Zo(-s
z7MG(HWS-M0wXyAB>6$+>>zf2$pu0sZG=BeMdqUvNgl?<#gRlLi5@V<3@qt2sTefYa
z#~;dZul^(G$*(uaGf8CwybXK-I*Pg5+{yL#KIT$PC?gG-TXsmrn@|*mzM^JD866N#
zs7_*~JXreWpe(qlZ1(!>CfDo>^91yaK5#tnt*z=A+Ei-JLa*a-F{G5>gjmF)pG~WG
zAXH^v8DA_g84;{jt^0^aC_(z}NPu9V5~QqLgm*Cxx;IcO_miK+&~et*Xh5T{d5*x>
z8Vh|jua9gJt-V;q%<n-yPuPfNrYsb<3KCvH=&2K}`Nd<`qdSVyBnFmq{m@tU4Bz_W
z4&_wPegOwJ*c+E-N9q(0Zs*j`%#~>DpLYS0Epn#5EK>~pg53dKOT{+2CFAY@><0CJ
zqQg}E7MI2#95efGux7j7FR~<rB`y+0JxHIk1Uqfwj@-Kg=j{mg;aAjDph4Gvm8Ng8
zRC4Y<sS|%v8ED5YBx?3}=%5VKI3X5Ov|go?zA05X_D(~hXk8auuXM5q$hvUlvNgd-
z?aFY)GUym~3b;0)hyjY_eH#no3v?CH5_KCC@A5}6nms6-U<qH>KC<Id5<^trEL+|a
zhk;s33P50fay~we7>0~-E115n{U1oigiRQF=a*C+>%{V1aFaWq=3&L_40r}hfG5<>
zd-$KTjeT#T1iG))iZ*A#yazlFsEcTk{I1{zRS3=@-OM5L(-SZ!9k%L8ODp?yvAL91
zj0G#Y+!z+U|NA3jS)#`7WN>i`$HP<unQDe~_Oij-SP{)z$bojhB_dB34H6_p(Wh|M
z!(u?es9C_`V8NemY<T@L3z<>8JhfGQjJg~I0&`LE&@6}Jj;B1?sl=~(>Cn^LsPktt
ztMQpSDW;XaGF5HanH+z&pT#W5%`NuJl6zLU)l;@&F_Lg)F>b)B5ktC}k}B7;>Wmb8
zI{0h$i=g-ob}6jYM|=oNh;K#eV)3UsFH_wGT}uRdqe>F^3YV-?q$U<N|I>^^OLH<&
zs>|Qd&kAw2h5NFUwLWEE$7IL{%?*re@|1E1DNn_C_+_o^R7>=IK|Nij+-z(baB2c}
zfw?Y)e#Dk+MN$6zNDszT$DeDV%m7_R|I;SR?bm!HAcEe*Sx)6kPoxDKWei}Sjbs~r
z>|J1=c^gQ3Qa{bjekoy8B0EF~Ue(yrt#o8FTo4ys$-(W-KvX9y7+Y6BQtp<^<ApRM
zG=rO4gS#w^@_YT5sb!h(1BB?+xwuC+=hoN!4ofAR#?dU`_J71m1fME{?gLJ+^*Jj1
z(u}hIVCMD?U!zsH1pwnAAE}l<`>q2mkp%NJ>9iCkS(<Sr+osG9&kOH*MfVK8;^(Mz
z-E1A){oIkY+W6D;4diadXvUUU4DIuvd2F)YrrO1OxIchLM0qZOPmZR$%s)~Yl%cJ7
zP1@A6Ge9{0>CYmOU%{#&?=u?r9@N3NaPzU|#f{eBvst^=1AUs_nSI}S4}uxzJw)S%
zxKPE{ryhG8bxG9eqEjyP(%_3#UpbP#H;3RQhY-Hc2=9{#0Ba$qFCmcZ#V;5j&`;P#
zVwT7FEPhD5SPuH9H~lwbOK~*rofXu}Bv^UM)4Pb<PbcN4h5MWGeH{M}Uml4T2=swq
zV-aypuG6OTfN)yi9+6k7^$EOSXtsHxfmvVnsaf$u0!YzoAE}f6v-m(&6dIuPKcVK-
zyE_4tb|22ZWy1*K5&C4pWYD~g0o1N+@?|Q_FRwUtEjM~Gb=2uF{Y{c$QFsc<m2@xK
zQE@RxxI@>cHMV(j%thr#B7qC>V67&KOeC7BmtV@bI7X#xtmRvyqhgx9TaTr`G0II9
zp^joM%fL@z<Zx{9U$OiKq)GRbE58EC$+wD^W|-srm4i@>Bm3|BEag^pd=jJ8LKpYa
zo*q7#5lvFIFgkxS`^KA3#ed<$4w~1;!F77|d$bZA+r{d4r{|&*h(UrPgEs56AY0|P
zjF{#4Ks+%2F9Lvr{MA7B8C%iOs>b*pWzMOMPeFK0qNCzcLmG9|y;$@sb+vuif!E5-
zQU4}YaLoDn`pG7h*oGtRhCmF==8f1x#d4o?>gxl7hynHebf*u5YhjwfSGn+6M>xyb
zCgAlDa~^oJgm7<(0$vZGj8xeIp8)1a3NIwVXt@>T>%RMn^u&rk>=}vFkP%W0hhjDN
zqRs6|`)OcxMrNxK!QST@dk2K8g-&-f^Eaj0F#+*g>991jub03oXsbPd9dz^df~O1{
zCJHYoT$tgqUxXF3Vh~3g;We#`UERVZUP-8+Q702De8X;|*px_}+M}qxA%yIoH6a~P
z4|!PVY_NYzx;Zjf<hTxgsC2RmT>Qbm(ER12i6-d&?N&6Is&R^t4bb9~#a{O*u-Dv~
z4;#e6b1A$Pdyo~S?`6%jZ>PFdTt~$jOhf)?t60)Yi|>=kERcjg-Ai<`LvM)RJ<@tT
zD1lzfA!cncLD{=J`0Dt-SpY!Yv;QM!aQU19bnQL1(Le>!17NnGdE3k-GZm7NPE;rG
z4M+s$JMFR0$(YBrb;l5N>IryL=%&c>&9z~)HY!8h!-DC!&sg8Vl?&X&#_mqhE{^!d
zsochl(N`u{NA~Y><NFNvL9^jkzXffB56$A|fn^~e*|$%^FcE#P&!2!XpMF2Odp;;8
zbyh<3(q%+<s*ta~j$4a|M|kY{mw5)Yg&uesX=V*tQ&lG=qp4p|lfPvze@IV_K;fEZ
zsw<3|Yp6h<wZ#I}!xHcoh(A9)z<A+LzdzLmj>R`ks8}}vsL$vqDYul(BrEeI>>D5{
z&lm1GbJLuTe$aVy&7G3duhxhCH%9CFzL>?Gg^gUFXfi<^vh(|k^lRUqnb5T~Z~5x@
z*i*+$JnTohQOh@35_?yycP7;WGYDe-9M!`*$AW1B+_O{iWz$^i(U#^FOAw%Wrphsw
z4rJle3(r^Qrf;6^b+~&EZsBlM)rA3kT8gm6yAtCGVVv^|F?lF@w5gomQ4k#KXZOw-
z8qZ=7J2dNZe$}IJ;&}J$-P|e*dX3y77U%y@7i<3M;`r+fQV_v6z-cgJTJXAfGa5*0
z0nD2wsZ*J-v37N&#hxKPF^IZ^Be1H>>XDC|<04c$NmzM?SRK~GzQ;dE`h)ek{PN$i
z0`Q%s;KpKw<yfM12Tmc)Mv;w-{Fnd(ls`*=ACT_WY`(;Ema?aX3v?5-;F+C><G}-&
zYYF_Zyp)C1Z5ley3o=bvbSt+sNl`bhZPdot9!W`<DtvQ&$c1=}w4Nwm^oJqh*(f!A
zuO|@fmbLE|45sO^srS&gWWMxgmcRE$1Zm)*;^5j~u7hO)K^OAlfl3@7;32dBBlb;$
z4^fabP-3!DzAUeTI12>LRFpoCO#4+=CS5pmu8<P03(&t>H%RWcr~Ld?slio(O(K)Y
zA;z3n0`6#GIK||zU*xOXo#IT^ouDxYRjcM5XWVGa%xo5&`);0-_op*qJ?W*4=%N`U
zgCJgr597l+_XyJt;5b)*27F~9$Yr+es%-Wi_>h`4paU=#(6a}E>;0pWwO-%}FOTPA
z%IvkYC8diWaIX8aW8LAES+7oJbq$B#OF;W_h87>s9LMjPKiS|{^3RrcF<JaAaqMq|
z<q;)^H3hd=+WRf;(D2@EvFzrZ9talNh?i!>w5cL|fU?%he*l_kcJSZnZmee3fE|HQ
ze{5U|w{YKaO^sW)!mIl=S3F?aP5MWBaOS0U1g4CwWB<|f6&F#rgQGm-;vyx(`L8uO
zQh`+tsaffg^|w>mf6s~!ei(IzrhL$8U;%jn{Z0-H+nqu@W;F};Hvz3#1G7m9ka?g*
zbc?TypqE)ttunw_T6L=L%W;1pf!7El5t*jbO*cT$7O={yKM|wMown-1^SlFtGxNC6
zuM9I%a(*tVI<_Kd8q|{IzD37_;cCNViJ?yb-htMx&MsV)WdPXuHV$WiSKpj_i$T1t
z^5R8MgX#7Ndy%;;S1zU=%R(J^&B&6wv-P+620lNyNa&^+=Y~@h*6n6*=V?Ea-_if0
z>P^6*`u@l9TauFHQ_^NFB-x8(8I;1<BYT#TlwAgyF_!j4mXSUC*h6-PK}kee#=a}t
z4A}?Sf9H;RfB*mUJRTnRo^xO4wQuL%jDgdh`d;2_aT9fP?zO$9aT8A`lq+^O65*P6
z2*Lu-zxo~Z6wI=E5fg;=T85~{<C{rtnif+?x_63PK7DN-3yFwILCo0LQgXMLX5nah
z!g1F6+Is%s3$YXO=Z?OM)oG0Om5~jr`1$MLaRDg?0`qO)kU*_h237%CKq)B_?*Xsh
z3O*1ne!nN_T?nCAd9WkZQlk|8XHi@0AP>SK)TuY+seqSp>=UoB0%zI6JUf=p+LLzO
zchSEYWu6Lxw@Ue_zmAJ<vvrp12uYQZ#3=Z$oYsP)-o8MLHAFT5nR7he1&%-cb&$Vx
zSm(YobqKiMjoDcjeKzH-`QXk7{w%g#`}Q<(bS8$eYR$Z-D6jBUFNuReha+Po5!sTY
zpJpr5=|H|P8NN5s?te5|JJmQzLR2A8xzHo!!65=<uAh#Hj3MjEa7Sf7?^2ayI<b9A
zU*x2V=dqRdk%tPs4WbQog|vr}(WoZ6`WKE)8Y`|>l5XhB{fv&`A`3sI0DzT|WlH<~
z6~{2MA$VydUx~vW`}_Cltj%*-JcLf8bR4$C;*BD?Kd3RV_=yQbn&`I<g)RCBrv%%E
z?eJ+bHoSQ;{`1#oz85R$s4r?2-`D&uww4}f2eF+0G1ojM2n*cbCV?$Dp$MT0KL-%<
zH3!T1Zkun%m_=n0d!8lt+mlwJgD5B{VYScHh4Vo0jbDRqpG7F5fky@-Bn2vtR`5DR
z)6u=5apJj`7(0lp0+6eQoGSv}0z~9Lm7#gCy-H0<{AgCwN8%$;lrozC>^;ldZ>ra|
ztQl{H(AJzz6AXGc$|#$5H`1hu)BiAyA42F#+o9GMJ}n5o2Q(c)C43k25W>Fw-4pP7
zR;zdDTHMLhqMQ_>F8>c-?ybr-4hnuw`Reo|)hpvD0^JF{UF_|h&DoRK@+Te>if5yV
z22ZMIrY42rAR_alUDMJz!Mjg??m<6B64kP?{I2M`cR==wQo*O=Z7qB)(p?e^dZ1+n
zP=WU;#t9-{1Uq|;SAsn}=t(j~58?48ruo_QgU%>t&am7VyEUo;&e`aVWhqvMc)d#I
zq#^$4_>llv|DZE4@72_d4sk&1z$Io?Cv?CVXDV>b5R*RnA>A`4J?;b-|MZD3(i=T;
z3o4{4+o$6Y!CX{pCj^h7(M#f784rWMBB)4RK`y~Nf$lwfyxbQ=F6lX#mi<)s67&BI
zjfNkUo?l;%=B{|!Z`Zz>tgL4#9~kQnSvXseHg3*n`B?)kIJ~U}hw{HixVfNp(6pc=
zPHBN-5a>1XP?t(9htfBDTr+#Y3s#-}1mkpP$v0h*%gd=9an#GlOq&%t4CCFTAu|0T
zoUaN=5Keja(ER;#9IG=>tC~*>QIq6B18@BPfm?h((M}bTw^(_s`z)zZw-`|CD;MVM
z$p<Tz6wbDd7F=DN;X=KmJHZ>Qx!!_PM1UC7@jif!d}yGZPB{U5GOHAC3+n>^=5K5t
zUj$!_=LGNc^*hpTVOw!_Mf8F&k@EgyVBYZMi}G<}P{;%ZHzY*S{J(TXOx>0uL_Ij{
zo)?Kqhr=FaFNsS!YDa$7{O=S8%SG0hGz+g7?Mt8Rnmu`tU)W+mxAz(rNpjI3H~=qb
zkQRk2AFezGL0HiI&5B$XpaC-!-ec-Sc5X@ez|lNVj=gH^9l+kQ2O8fnKvoM<FyQ&-
zyXlgGdBPrux@Xv(3z>~mb?OGC4Bl|1H}W!hQ0o#Xb5wzVAI^>S=h7>IZTm;epV~*e
zUmS-5JnxT8RA$*316LqDFP%=Ip&b-(Ar9_3xVI}~m?13iS-P|3L}`g3h&c8Xzav61
z005+m!ViN$=2}?^c#Jy8Za7l}hX1hvVTuxR{TFbRlWER~L=@-{Osrpvuh1lcZ@2pM
zU-@5y+aEz#S^95A7+vD_wfFT{|B~4$?&N6XD?<6Q`T16zrv<o7_Jd(SfK1zHR+T0X
zZTYH;GSyl2I$}=m&4+xnNVQ2y!5xb6R#EZ~@~?p#sG+p(1+$flppT8z8bFJl*bTx)
zV`4am4G*FyY`WqW=wBVLBaBK<1x3G)GP`k3FW6^ue)ID{bh8m?9P+oU%kG6*M?nr)
zi&RJBG+^)yE(x<E7CQ<iCX9;-RpHpjC?m?A4gFXR&?=!Ed|H{opL+r`>x-OpggG6o
zBAPvIjvo1T9Z~o(Ehi_j_qLAEZS*5#aI^ULobVgM;1&XpK^dL03nm}*TEXMv10R%$
zvErORKZV-sflw&TDAeR&d~Hj4QMz->q35`kjus+y%ztZP?OFLPr+F}g><gMnTl+2T
zDrgHpgt{cU6giZ&ez-DvlVXclpcWV{f`ZxCP*mGWLL|qEiw;;L=_%!>07AN2q8sI)
z04B=45gOQ&s79+<go6fBz>Q!KI{VPqSrxr4b;UnCC|na7GCzNXl%iqjxApFAGPrK7
z>dyip8dnG2@W*|G^%WSzU*Fd}5Y(~cW3NFNr1Qp}sk4?xNugT8tJ%yJT&H^pKgny*
z`Y*ibZ=beO&<o>XjQj}Shsa>1!sKx2>88lJFx2=;Le#fcnHS*)hJp=;H@`awK@ulG
z%ceg!$dw!O6B}U-2L`oZ`R!|NpNBUDTR!x~{303(hF5N{+bkV&=UCAIJV{2tSbE~q
zGAQt1@ZX%Ui*KgU<Zl9^BDr4eN9S@fG6<XI`Zd0Hd~fI8$pMn=FLn*yATVFT{Mg}t
z(^8a4Y%L<w3+a)?mG;=ztDb!!)F@oHmC}PeDFBMR3Fyv5w>voQ_U|ZHKjgRYxf?8|
zSfDl?YmT1(CV)Uxr@hUoa_9n1GigRiGK|eY`1ObK+^@^slk)lkfSDND0Mo+HRpUo=
z|9vhKu26FtJ^uyQOl<+c%4MT7EH~r_K2_b#xd1>t3yzN{2QMJJs`2iB8P+-^?$N#L
z!3ZKgbvqv5B>f%0NeaM;0}Uq<HjG{XG2K04(77}Jo9lr^x79Bmd$$z+xpb+7I%3cy
z=Y7wRBNi)DhskDf*(vY(C?54b3a#;N&&DWNs8Sv<I*K#Tj`rwPR)MW7SObEgoZ=2c
z`%U0Sg5B%YBaRyAt6+`+n4{1LL<t3xLj`V@6xBRc3hF!XkT|r<0tjMqr$<ai|6OfT
ziak>|Pl%K-<;rK+TN432mSoUir-MZQqdafIc&GN@&X;7J1asqOB~%^Rbo-EPuYSL6
zBNF226i|k&e<y7}#>diZ5O~yU%x1JL!t<f2umdX9d>)SnrSOwTt7xkz^HR8kK-T{Y
z;8p=YTv>xhqIZ)+EPCYC^*FiGT#aXG_YXB|u0O`>Y7(%%x1BrTa5nJ`tPF#JO}R#T
z{tpx0I`7TeQUoK5Dm9D=0<?|>hKb`7@w8CsV=(ANM}v@FJOq{SZ^oKYw=iMn)e?H*
z_bCgCr=vQ-kTmy0{5!TEwiY$<r{U(ThnTm2m4-4VFqnn%te%D3+0EIxpefcmv~ajz
zfH}qjX9>#fK;E%V5ARHw_0t1t$<w6gCuUX!CkE$r;6V-q(le{%W~rNC+J4M}5_e2}
zy$tUqQ7jK!kY_M}{&VFU{Bdw@1|A<r$D$1pn;p1g#+RHTFWip+EwA`t7<t8Ttb1Q6
z&6UA_$hG({eEx{z+??G_xtH<NgSF_DpM$4PrpaWftZ1y~fs~W1<gz_%ZTwd_N`S)W
z?O(7l*s&z((tKO+upVgzDLfyW4SJ}<a%NaQdAw6J$K|GDr1XKa{6x3aKUMjIqZ?Hv
z1%!qtAYGC0%jq@LI!@y(4O-VV3~(#<QptHV`3o*S#;R@Nm_w>pjf}w7FQD&JN<gg^
z8mEbZuiEuTu&scgBfn2^lg3+m^NcOAH@k0n>K*?*czyCFW{VCv9Q!_s(B^p>5Zg!V
zCktdT`zJrs?+hj3ukC|S)re8rF44^$+)mC&O@~;<`x-7U+>qO|3)ouW>^D|4ES-Z-
z9HGib>(hpWDf+O@2g83za_q94kF{2$)=X#o!fnx9XM3A4ej>AT529+$w4#0$>uc)~
z%5VbmSFF)e1YO$y+O`ro1OBAb$kS6;Nyy{@)J$*5X%DxoQi`Om1MMl@{|v0(^>IIV
zYN-vdjEyS0yS+4XlBcaRlB**-w_Gn$!6DD{?fjzaD@$R@63|Q=PN2pNnblT@K#3LJ
zU>a>~**1iV5$`8By9SeEnpo_2W&y)3zcJQaUmW|=VM%+`1gw#~FmM|&Jd}5URk|ro
z{1uX0J@ryd;d1Wj7rnJ+)G(YgFu|uvEI>QReU_b5d;P_LZvTka{)duJi#^|L5$n`~
zuC7wYNK%vH<!Xu5?2<QN&AJ7#%RpA^gS9P0C{94_H6DHGH3tX^DVNHBbcu||{N(0R
zl*md2Jd<PW7}@d0vH;^VyxutVOU4o2*K62ni+ODJbO14K1EF*D0pMf-+Ij`PWtmQ{
ztyq4aiRkOYMHqpj4<*@CLU}`g4gukvbr{<GMH^<Iku0B1f;m7k386`+Ew<lpp*yA3
zJT`HMitGZbKD_5d^27tCA;C<;t90rU=&`05+DNH8e+{jF22f&Ke_k!gVV&c0sg7Qn
z1W%w-25B=mT-d>>4-|m$Fw*6p2>O4^4Lz-`J=?XEwt@uUmEOz@!3&n@k^X?aMbcm^
zkbEW&q0+ORjzdM7yq0?KzWjY9$J8S&i*#km)KEWc+4@Rjzfq5DRsb_Q?Q|U6QLvDA
z5+ds;Ie@Nt3r?dD+N3HJxh9H*>qPsy>UAZb-|ypPE51@^JydXtmt-Y9I)NC;(j@pU
zO(4iXAe6$S;Orqh{F9%*;Ig<Zn>(pJV~~2}zME|rFVX%gDHI?P<ncj^Cw~e(6GQ+Z
z%Z9*$&RyE1RvB1ns_2S7aKbiu3YE~~a$~KcHaK9$f-b`9W!C-KU&ewOslNfCz>i1O
zLp|06#D_w=$>Q=ySIr&loFcm(1mRhM+hieMEg>^M2dYnr957?9t_i_f6dpyj+esG*
zQzIvxxDm+)2Gyx``N!{%4y2gH?u2%=Y^pmfDRrzzZ?HS&^okY7<%UunaN9LB(geZ2
zOcO{S`r|eKnU+@P@Fd9}JX^ya+cir15>jS^CvFz`uH4R1Sk@Lr_@)~rti>O_`TLkz
zRUu9+0d`s|{s%M^eDsO{A|)G~(SIvFI25LoUiiYt>8+NO<FJ`|>mr*~_ad9u{k3l{
zD+XTc^^?aZwo_-$0CwktjocYf#XC*e_-p>5kG9^!#d6r6;ty=7zj~?~*Ja}>b`0cJ
zM;|ze{V>hQMag^zHsy!sVSp3o9?w0HKLKbXAomIXbZ<?B#kB5JO>}j~(2`a6dXIZ?
z`E-Uo(Ykp)>T9rN4xQ4%n^SRRTIRwn;5*Ifc2}xBfj(x<`5?A3$hi!>GWbjc`3w+G
zqA|(+uU8C#cYk)7&M0lzaz*U~Uh?81eeH4Qx62^3yGhBpX>Evan9h`w$NMgCxaRGr
zs0qZGn_6t9&0GbWWQU#QNMKz}NZ^RYF7XKZBjoR)-IU*BEm;>T#Y->?ZQ}OZE`HU=
z(><-;QQ3gUAxIMk*zV=J0V%4(4c+_4o4I4^6_ImoUnu6%1-@6OE5w}+kkkalI_X=g
zZ#2(mbm{n6Wl^;fK4;*oOA82(Vqq{KSZ}`tnA$c*?hO2O4xmA2$C<<Mjy%P&=F>Kj
z_Z_-VBZJ;29iFM0zuxEfO{uGoGPg=9nyvQ=p4*rP%>M!gt0s{T)<7^^emK;Bs}b+q
zT`CeY`6E1|w4_udxx(obXvzPrt(ELMQ%$wwr#HibICO7Q_{1U!SU+boQ;UHDSb;tX
zgxLsK>ma<Y`l*7yj+JuWNk*gMxdARYiJjwpC*nvG<l(UQw`bxBMx)28)P;4inx7^L
zW-b(R;))0bgg+jzm`OBn!UDoS>>jL+?gN3M^c7y&%|alrAW{r!Y>m>f`r}}xFmF%a
z{IaC0d5V%(Z6WMFTw-AsVT&{doCVss0AufG=K`)CeGpG9x*RV980+KndD@9vy)%M6
zq@lX%wlA6HN15i@z78F~KPQma_O)EC$gLzh^5n1p1qaX+3mc%CL~t_6U(6MtsXCPU
z&ssuMHno5i5v(zT?(muVlU=!!JFhQww}6T~wnS5Ni48WFcD5c1zO?<kyuS);3+OaE
ziKJy|;Ej;I>{z$ob9<w;TL!iSOEi&7A$Zua&4%3q>sB~+i~vEa6-oY|P)Z#5YV4Ph
z`I7-PlAJB&H-!X;T)-=2Ip5thHMOX$h1CL649!79{imSz|2U1nPv^-cX9sb${<&|w
z5<|oShwMWCb%5skATqA00wo?89$-Tf<<PFT@*e%XP5iUQQ0(RN#Z&gS4Q@LY7V{HQ
z7HcJP&<TDZQd{|Wm4A|c;%-I#bB~2Kgq(t8ntKz6*>FaW7!oJe4~$hjz#&f$(6jzm
zegan?+8_P@Q!@UlP1&)8xi)t*lYx&GjiWeAiE4?`yEM}60rKW=5!nZ3(S{r5s~Q#8
zB)I(gICoppAyp^O6kvCidMZE&N%Iqb6NZ2qp$+v*igI{|?d>ZTex0|uqE8gE<9GUj
znK|B54x*&pyV1mdDm=ugJNI^Zqz;*f@WSIy&HZ|DamrR))j4qIOKE_gBXBF2(?7KY
z)d3F>HCJmV?dMAji^L8B3nVD-eFbce8E~6*OChj%wBbJyID3lpCf-jE#wgc7X|_S+
zRvZB1keml_rS~5OvfQ(D;h!Z)lpal~g@aMT?4Q$IJ^d@ZTc)_7-dW&lNHoB7is$%m
z<%hq4+f=M1nHkBI(6No+o2l%mjsa#qD-Jx{IwT+XStcWxT)qbu`sQ<KyWm*Ymyc@?
zt~Qv8<~o+x{HfsIss)}|B6u-3SRX!#D9`e0p0nYZ@m|{fMDk+<AG(+Q1!`s-utFs@
zGQd)dqHW6xPV2(ZM8LM4%9z$f!#TBpZbNmMHHe4wCc#e+^YwWX=X&W`!8Dc#Szh3H
zfYr?{!SVLpfocX}H(|E1mM~H9qz_@H5#oD|<nm4uNNfhsNRYg9(O-sy<mOrfZV)%0
zy%@JdE8FBSP^uMx)pt7S0Sw0Zd)MjxS-_E=|BH7Z>*0aTEZ@y9-hfCkT)*UTmU1A^
zKn2fD3}ONHpc44pyFe&=Ma6J-FB@~UElgS_hW<<gHNG>HNKLUrkbl5+5PHXX4gBLL
zvRI2;rFmZEdPcl_v9Znq=avlETToGw2p}U1tdfU>|D(+;bv1#gD{~8b?FDNfyX;IN
ze%Rgs2_*9<Y>+BpB2o*K17_et5%4;*VYdz2`_$5NGh`(wcnmS44LslO;zC$lt{5E3
zf}ogD%<M}%^IxA7_=gIGAG0>N5qWQaXmlkN;w(XiqqH-i0H_pAa7tU*j;r_|{?JXK
zuiOSlxZCpWW;*rO_fm54JB2FXtW|3yoD?ez0%vS?2a(cqeS@m8`Z9=H%YtWX2ZS1E
zqjdYdpdAp7EA5D+|FB`9QX7;jcPVK)R{_6;37k%`;-!?z--5G<@abl`X;r|}Tl@!r
zZlbMiT^FB!m`J66ff^TJkWx4r+qLBZ_Lx_218^%*%p?COr0o4Kme_@c8rf)+Sixi2
znprsg^M_K%7)V<!ppQZjJ**bv+&lgQMhOO{>UUyp`R_#4=U(d*mb?_FV@&{VLD<!r
zymk8@+fnmW7*suKJJmdXep={D+qn!lDgQ?dz?w81aLdZT8j3cyeuPp#+c3bKFD-YW
z2oyJ+y7xiK;wRxCk?A!szo6#!5u_4**)!J9>?)m*uWB!r2QrC$JxsYhOkb;tfi3fg
zkAsrwE1Q`hE};AWFRp;B=SA|Ioo_xKX>8e9#wwM-#&VG6(One#kNNkv$1j9hY<SMC
zhk}l<RYc@h;CJZLr~&WFT5sQ9W=_O_q_hmS1z`=VP69j3kzbj?#r^ayDYUqZw^LI9
zF@q7yGX|zb8Rl-clz;lq-zfz*3v#Gf&`SWf_xd|u4Lb%E^{!|)-2G?_vR=Fp^4gV~
z|9L&o6VNDd2jq{NVS|IBlLL&j74)B?R(H+Br-SA_df4!_GQ(`PmHY7@Lx%jkH|*}R
zjPUvnPws(pTr*z(!ZgUA)A=10BqV^^2e#gvHrEn_1G|Gay%xs}09A!owtiv*{!g}p
z8zA~<r5O08)~BmTbU*dGV;v1PM%eyas{NBqNQ%-eFbE<%ZW?StFxf4Q|0DbTPfh%Y
zS<I{eY=9Hl;HMLv0p$J}HGkQS8iPc#f)2St+8u+mJ81CT2>OdnvSGpsVii#}`Ouvi
zBAajOvOs-bRtIh)WB=JpNMnT=sU!`$U1&Z^qbh?ORMbMt8q>DvG|z}+1@)W;cn9y^
z0)gtAWc+6&Ag4t~WH30<5e<8Tv}49aEzAFO8q{|`7{7sS!G^<E|LpWu%>B7MCBHK|
z*K3iJCHjr|_<%&o>AlASPg~b0A3Jcc?%iEB(t*sUx5UaTLOhYakxi*GNA$&)KMO=&
zK4^X9!2h)JnZL64kDQSy_sTAHx>&8mZ<;+7UQ{tW*xMbZb_XLZzZBuvM5>xx+Dc=j
zmxJ&vakN4qypfahj^|GN384Uv#6PwLoLhF|+=+RO*U`;;tPgOi75pIqpAm#;hyRq|
zbww=+ZIWETPxyIfFBe3zsRWh5=Pws&&YFMdIv)Q*{)HxZ84U6$84BUfyT}Dk1w&%w
z64K%7C*^z!FOW<I7=-$(aP^NiRK##M*%<eKjb;H}oZbzf4$uP+03@_w-FgzY^5SuT
zyA}hGiE}-_*&zK7?!oC%6i!IB@vzl-+A1MOWJD|p3p{Bm5ER06wsjBh^4C}vh?iYN
zHjR(A&IpSxSS2`yWe=o$;T(KJvosf^Y%k%*0$*2d+>|)V<RgBRX@2Gs#G4I6F(pc?
zCc>8+t|o*O@gHUSLxX}B-X8kOzYX|{c)Y=TBv~hRpa2%vRe<Wt^a=;4p$+9@70RS4
zJqgz|c=J?Ma8>9i<NntI`TN*M?giP%?V`b1LX|Y6CsE`167v6W6<)&QIaq@9y+BKl
zwoZ+x0?v|&o{mQXCV&_Wf?1(9O>Kbd55Kple5zr+`U&#Np@RZbfGgY)<MI!QAx{*~
zQh1WAYh2_GK)luP=IkvT<iM##8(kD_b$$MG56sV<$dCeyhg8G(DbBqF@ROELpivhR
zk}@C#=t)S_gFPzyCWG~l9;BzM!<pP+Y%utq1ZRe!kP8C1EC7af+7k#`WQEDxyboY0
zs+MyX5~0;nJ&E~~?LcJKo&gThpLB#T*Yp3qyj%<}SLjKMNW)<8z+iYx06NxG1|d=Q
ze<3Av;fy?-lMX=2W;80@vH=@$y#4A3jobX+5ll$&0MIr7sDH)(=Z??0WZG8oJ^PT-
zfLg8a4H)<a#;1=1&LFR+(cYZ^?h!NQrwGHWH1Gxn(&q7hw2c1)HUKCI=<EgKpd$(v
z8QKU@+rAI}u8D)8mKFoZ+Z_#jhpv9Ak)|#80$y(P)PIbluoMY4dy#7|G(scjsqPpW
zH-edC(ULgD+j9G$8VeC{KX3Q5#{pN7GXTa0?Vvx8X@>&*51*=dMEPn4<8!uVpBxl8
z@Ce*HCZ;)czm3LLHLhEY0B!yly+pd2hBzmHDbD%>yCC!BpF7HQ>puJlE&#LjnAim_
z$p6jdz!VxWC76PrKi(t93e~(^2tEjw?gTo+^>9=2H5$)ZlhZWOkpL0?18RU<`Mih#
zNw>b<(e|Qk`}xmEfZ{JGKqY6G84n+zr+bF`lf27JkVK0hWe*H?Ie2j~q<Zf?m^{#O
zSd*~JM|jrfj{{6$ls!BSxG0dxDv(ZHUQ>iZ!%ofrHf4dF{*Z#KO<=(9!hkEsyG5ze
zARCbqdq=%TTl^Jm@g%VLVqhIJl?ECAPga^B?1Ok$X;>Ms{zpQ8#YTSY5DfF|?WYH!
z=b1|^T_1s-*&X|(+!jc0)wEv#;;;Y}WBmtcEYMlgb8?sQe76$7gZu|z;jQ(G0DreW
zvjrv)403mIlJ&?kZ9}m3V;X)2kg2>ArAC98_mdS6Tr3bxq0J|Iz~o|hveLvZ4b>&C
zlPqXc>1b0u{?py+jd@o;DTl&D_ze@G_J54~8Tk#PK>e6Dc!hkCRu=$wg>1oidPIYl
zcEws<k)3gWvjlu?kaq3ff1GFC;0q)Q;)P|WW_};7T?L*baaRT~gk?V+#Pky2_4%az
zKR$+-n!pD9Z2>Fs%F|}u`cL)v-;Nfbc*4}^eI@?^vVI954#2+zSPc;i;xzS%rkNMl
zQcvXgn@Hy|4@F3sRSP`0^(|1(5b4#faS35~&5!*GQ)VRza8pw3Z2;k291JHsC=01T
z;%V1CY1idj0M|F*XT4EbG_B!3y*U8>P~N>-(F6XLc#=9u!&9!i+PM>t;%HdB0<fs!
z6%Ek8JM<@XldSzKzV3l=FqSTh{bv!B8!L54v08u`?lR0~?DaoQWAHw0@Ez9=<Ck%D
zkx@0uoVN3^65EP!q^8n#?!oV0sT?-2YWxmc&*y2MVHoW#Y~yS$?GMShU}k3!53|3D
zq!~#NUN{P-smjGR__l*oPuJ74hfYTEy$FWSSq+Ss1Nj;N81Xj+ra(gKBFz*~y8PI`
zV^7l+-c6kw9Yt*^Bf-u7fq!5TfC}L)+|QyBG*i;`q^4oK;fGuvk_jo{`RHZDHq490
z7~^v%fKmfWffHuu5F1$k0)O^N4Chw<dary{b-m8X3|*diA!0)7bd4oF(S7Q)9W7s@
zo~ne5v4f{FRc-92VMI+pTOy7Q8fXZ$ajiO<`|I+N>wM22GzcvJ?+|sieN~}GZh0j>
zSU%1rUnG60%(7)#VQ4Dw7izn5<3gO0yIf?=oZLq*pZZWvHP7zTaY~V+4Q`GLi-2qm
zDxc~!WfUD?mRtJ6ast8uo2r2O1@xn`BKf>O#M}Oms62-j$yc6R2yC``MDRov$^|3K
z7QTc<eVVFF6EF=DXu@$e;lk&m3DY}Vy#;r_<?}Zo&r#VLH-c>E<$ZsjUv}ybz1!r;
zUteM?AM|UX>{rQ;4g}zwOe4}$@bpDAFEn;C0%V%U!eQxIJCiS#q{T3@-}!fds8CX3
z>0Q(K*#ZkAuhYXGmGv4v_tb8<ARm4R;@Bsm8E+6f<P|ToaLb~p-#kv{P)`s5#ipOD
zeJKvpQO{-WInbpu%wb#CKmJOlk;5gT-Z@0Pi&wYOl3V`$EGr;t1J(wd7boe$4#{2c
z<u-`l<pWHw;9EVirw@uySebM$u=OLhotZr=JE!Zbj!(P!gWp#!QWd|Py4;?*n(5Ft
z6gF=&DYcpD;6>EdFPc9k?VZkwOSWMg!imbdnd)do+$s3&xz_KM`C)-RT)OI<hsZtf
z<i&PYVB=kmix2kPf!zsrz*fB81~C8eTPHXerzogZxj&!xO6)F~AWNOC8keF+tL>R<
z;4@W}J^%Yrk9n@ir;{<5HtF?7jPRJ(sp1NBp;6u=9pQNFtx$>fX`o&Y2jk~5ZGb@!
z5qxCGNTV${rEwfK(ChX3bG<EYoGTYqyEMDG$yi<aKip*EA?o&uvhKjNg4@oL!6b+E
zj(hf!5>mhWi|3>^G9ujdt-+IF3(fph-+^|%u+Hf}+mWtwiY24o7Ga}<m=6gtQcCRk
z(@cYt`R{YXm=pqrtm87n>k_*4Oe3iA(~YR%A1UJtR4m5b;K|BtUv9BDBF}c`Pj*b~
zsTV$=86?C#P27^;mH_LJ@76%LamQgrA@Nah@F?4q>5E0qTwGG<T<)*RxzSCmT-?J+
zf014;wh81Z!{2R@Lk3CN&BCYVqY7?}XA$O)7+O4fHCr|3TU=an-|7cTj-U54%STf;
zIy>Xluls<9S!|!9JcKoB^e3+YC<L!3@zIPVK=WRBu{g0bUE{>``+E_9^AXtiKb2n&
zqOvy<KMA(7r4!j6rrGW#x)X@g-{OZh(pla24r)9~APhzP*%lFA$C)AQ&Yhgp5pC@r
zR#FYCM~BJz^8Q@8#5G`?^47t4>X{%<=TDUlHIyQNLOR!^5;dv`8zxdPyk#JO$#=$K
zWnrw*OPWd7>Dk!a;%VLZ834X@ZFrd;jiX=Brk^8ydMxZA=VfV{<wtZc+N|oR);jX`
zsmEBWFOlFIZu!Xm)ynU__(ca;Z(TnBU=b)yr}isA$6p895DB!bFY<Ofcu5-Ni`di=
z9{RC7AE8#vZ@(ekfLSC{pJAF8dvEQzR#8o2<7^c@!PaB8I{sR~(DKUNL)1~D@Gf>g
zEjpnU^YsA>c7mJlf`2{UOyO92J|9D|cdeNyW+E@k*Gc7TE+DGvZ!EA#o5e6uslSRP
zA@!^0PMi>@z>x<;cdIN?PC&NRxRH^%M@J>VIZfHiF)#l7#_i91gZFf(6plHblxVge
zVi#=tOLVy9lb!O2$;T76DlAQjpYMY{DT$0Id>dHb@gnT%DvDfZg1$x59LSJ88pV#H
zNnzi@-<I#eo6NOXsBFC%-k=1956B*2ocV%b!j&uC2A{v;_x@Nvn$ha4*JIE&y1+4c
zeA?a1Fr&w1`(kqaXxpDxVbZ?8?pk;ZYCq&O_Yl;*KiOqmyttN5U0h5pm?@(~fo$6o
zU6LR__6O|KuSf0Z9EKh$pF2@zNIC*zSXRWG!wbS)kPR4e!1?%d^2IC9Ew3nUBzPe%
zweCazx?7q$OPT*tx-1hAFEKuAA}1X%Bz;n`XCHd?Ddq?pnV3Gr5T#r?)<$^DN;dga
zX;AM+jc6lmtX~*stas}$vC6jSG%vER(<lD<&GuULOq$IeC}d6}>M8@Yx(F-O^2DhR
zufXe8no*!^&yu3RP|z20h`L8ts&#Ec$vSbb1>Mmv#Ng?z&Dp&QYk-q`vOZ5)Bqqq|
zss+rVj#0Vl)-(Ie3f|8a5SN^A9fsIdZ1s^tsO58YnB(LK+c*LPrHCH=dBe%$(z;ty
zx=q!g@g=i$QibqxM7Bn_rbv_i4YyZk<76!&MaopYDwm$1+h@FlB>Vz2ni@g5(~=Ps
z<S*oTyZ^YcVzCE`{AH^^W05~$_)?k+=1*1c-nXudNm$)BoSSC#+Ka{0qZ1BNbC)i^
zq9>%BK2GL)udGW@)&)qC+bevw+Va#A7P~}egQ5&vEx%#z@Mfj+ck6m&B&A$1G9zgg
zPf-Wqd7Nlwpb!dj6=X!w9(S4l0gmRQs<X-*C8tNY=$6g<(-Xp7wT{rEy~+odA1O7J
z3RdxaJ4%k=w|hyyp841(WG``PkaE6NG&r@?cimWS?zhJH8&^y$%j{qdGZ6GO!ALUs
z=T;iu9%w{0!4$~34D68Lxq+Q|uL|-5>aSyAC)1ybBq;M_TvqZ(9-8FZgczyckCNv$
zI*g^TE7R}tl0!eT@C>APcjb}XbrEUUiqhC15W8|nJY#{x#^LP1L*-XAU#mtL$N7BD
z$8m&%UcZ=mGlco!&rgdhifJv{|I=B`bI7u4n%+ySvC4RG(axdodoOw^Zcbn1SZ97M
zL$U3s8F4<i+J0l=Z5lYP9P&m1w~Zu~!gdjVjExMro=UQ|Cg2gf`f*vm1htXLwxYN*
z!a$8z_Ci-9UL8aU{>=Y!kjmXcj+vN^IXGvxcd+0{ZrHbjC|%={DmHS2h-rj0c^^6$
zppA~SV9=83pc^e|&a=Mi!npOOepJqT^JNKf{k5gf%3R;aiR<m5z&^8=;7PzqD2WAG
z4RD^Sb<YU3Sqf|!lxV((xa=dNEk7^L^y0meec8-jm9nZ6*H^h&W_wT9yFK4>dnljR
zoqdok{r=}KLS~P)egFwB77TKz@6t9~``m6u+%)aIRAC14!>qyh;8!p^uvfY7^KS?0
z5u85?-{l8HsaE3Z5F4WRAoa^$MC{qtoMx4Zv#p)e3S1jy<^^NafgOdPHX)Y-#E=P_
zUE<PNcLF6)L8BR&NtPHdV~4G#rsB=$>degiPbiQ<FQ7LdLn9Yp-<)Ex8#1+~R*&~@
zaJsL97Z$$%K47Et4s%RjR?>H@hMSRkyFf%UMfkkOc4ZUr=bBKf*j3?yp|o0tm8oK5
zBZsw%!456C_U)2;Ac<55ajFXqPs}i$q(Ho^fs6zhD8OMIn!Wqhq4blp`_SEE-m7j0
z4SMK+wjW+YTai1!|B5_6?;{8<$Ub<ltRzi||FVyeKK+*1eDVE3D!q&diDP)(@-zbY
zZuY@Eok2OVu<|o2d~7?s2l9Rf<LxkwGP_Q$|E9E_w<2x{Kl<lxbI+5oUd(#7%!edp
zT|PjK1vWv4%`e}~TxZ@s<W&2i&D>XtdC`?;mNee7sm<&ms9g_SQ40l};(3ZZ?BuHk
z9YjGVuAMt^F65{r@PUEFx^2IgxLQl6oyc0U>V4<^U6>*}`~uPezV;foGGmnIh}~e5
zkLDckfCF*Vx`b_0?mXkmi2l%c)8Vx41cQu4{T50>$Wzxc3pJM6_6Y6iqF>R1MehCC
zLbBozWcnE1(Lp#ibsgW068SE4m`@rgJ{rRGu3r%g`HX1UXxH<)8a~>rJ}vz)Zbp5_
zWH`-Au@@i1CyAYj*RYVuyDTs%CL%(j7Eat>H+83`_0Qs*`m+#jH|0yKvO2{T(+$Np
zRq`K+2y}yV9R&DKeLWtew){hH1216zVaEMg{KR{5a4<pQ6F=Lk%N#5y8xZg6qj9!X
zG<zwMC^)zgt*q;#M3M;Dj$j?mTbdC6-}=<~X1|5ivoo@N7I%hA60hy}8ednva5*R?
zVnTH$uQ!v~!Ls9!?v9~{V6fd-A5cXvMKkY$aQrsx8r0T<+y|3$+O8@IVX}FR`Iv5^
z;}se&`G7E#E1IX5xOzvP)IKeDwwdkCl2~?$?d-B&Q^CzkS+^!FUGtlXBX<UuxBZNy
zj&y~pFcf*T%jG;;IcQj2a@xil$m@QPuKjXU4jPjJI`_mt`7UbJ-_CG!#{`8)>lnZH
zlD);zy*(<a&E+y7fZywvl-3-TntAaa<+-^^fs^^NV6a2?$`3Q*FWDTQpF-F94)gVb
zb!$q2BOM%lmBD`ic5a@~;!+TKpR7IA$Bm-;lp&AkAX;&&&x@qGgpa*#FdmWNs>=vB
zuSJi9?w?V7Kj1r>on8BtkvgQn9sD&=NyX-CLXu|gqbG{%6!GlTawNmbZ_@K(@ds;4
z-0ce~YFdCr$4YaFt+X7Xgu-w5p+IFY@N56&&`>HjIbHZMChp!yJ9wQT>^R1^oN{EP
zKCLub4M60Ln@kludFx{m%_Hv04l41G!0mU^JXujl!kng3>(g%r;lZ9fL6iVBj-rQ6
zt^0rFG9RVH@|*}uyP0|Xtt#sG{1vCcB1>__9ejzSiH+P5h<E1;f4C$t2<1ZZ&OH15
zMSvSAasv*8Yv|F(7ixc^j&*&zCA^Sv+wohx(T11tq(y*bx8rnm!hKS$cu7Oai|x(g
ze!c>yZ=<qX`MrsWHF-kq_v{;sq6xDT^5d6FrW|zbS64*MHb{riz>szh4cW_`g=z+U
zaI@i5EX+PCk+#EM_bRUdOr+vsKm-pG1yceD?;+bSY~(K9YK@(J>zP6`hqV#~kCC5f
zCj!-pVhJ<XS>5-jL@O}?v#^&qGqe%Tn(U_L_o(W6H9E`mhg0qSX12|Vu+f{+g9y#x
z(h{j@wqft<n37zh2V44UDKE6t_CjT>K&6JHM1hP(04?1Ccp`LrmhHqZA|26XKUr+F
zg4?yDm$a%N*0iEDS1{eVoW^(e3yIkY?TSociGP_s=969W%)&4+@?8WaN2aBFGN?s=
zu&m;)tmIm<nqddQH1%zhA*rAlbq(aSY#6zqhezQYQs8($(5+D9t82B4rKOo4GkQ?(
zih8_6((*Q~h+T7mcxq*KHXnMJ!vL)@np>5qKAy@gUDWeXBq4cQ==FMfM&_^m$e_x6
zG<(V1O=SD|@JkBfd9?*|kpJloPf$(}g7;+(ryH#Qrl_Ca4N0Y_5m?tV<9=YoKMhT*
z2{K%IBkwkrnD+g0KPvFu>wc1oX6*7(wT#da(C4<3Hh8%BIw$*v`-seCq;EoMte9xq
zT*9==q?o3gRjOH&*bRqX0Xa!Z!dQO)&HoMM{pw;qpKW#C@2=n1i*(S#AYE{R7;ztt
zPrc*YdG<oy(|c*@suAZ1TV|}1XJF3|m${ajdgc_}jlr#)(e*Z)w-1C`QiHZSWblu&
z5F7&~iTo5BC*6GT#o?Pum+*9jzG*S;-0j<@)gAfYR<muXh7ZTIZS;X>y5S78ycC>E
zQ-F1^b)F2(&a12D8qY_xd$BH~`qui;qGj7%-z_Ax&)iT`+QEczoArGti`$;g$zqva
z>@J^P-ic<zGQJ=0{yL~qEt_c5yNZ0hE|^)qY4+gt*sIbE-U6$-oY<RP^Oc)F5t*#a
zP=mB0lII;&1!m!IaMmlp!k(57E4Y;_)9r1qyX^3gQ!qV!$EugT&2Ov9awDkjg6EIU
z&e?&g<q~><+Via&HW*EIF-5hXzu+zMH@#}&$PTZ@rfb9+W#ipsF`0DAzU!8NpmV^J
zA-KpMhg?qs6-WjNvvVP1GBm5!@HBKbINpJ?{)V|`p+=)>bkK#nIk(kV#U6B685K1k
zTkL1(`n=C&^_?}hQ7v~+tC<!%-{rMU%9tqW2wsqnFwTFx@R~i)csipg^&3xQy>poO
zLzC+{v4&k`x2`+orEU^HMy*}?*)|`%(e%mOxknJMhbk>A1@U5oxceOBK8NJ=4CJ;N
z2T@v@E?UKF;zrBd8Ho)pl&@=bCoAG-gpBZH5$T}v>o4y47*w=iZ(;0qbY7%yM^4ob
zq($YOu`vaOuw~`RRu+i2NfKzqEsos;rhi9)NM^RzkU7!x;^ccfDcyooW{%j67H0HA
zr&!84vtrTrZ3VIh$1E(9mBd{nQ64aJ_BEdGG`gf)Z0DmM!FJ=ySO#N%Nmdc%dbm_h
zxCot>Hpr%Z6QqbCtKlk##AO(v!`Eoc8KU%F!Tc(Mqr(wn*gdd#sa;aX!9e?3!j@rN
zP-nfiTIg8wK@?KX&OV?y+APs&BPA_G9ptd`)PLT*&X}G>lS+k!vum{*HwOxCq%yaB
z<3Zd7+RmEn3)HG_DJT~F{__I7$w!>_(3`Y}`rkF_ns4-Ka+6an*uca#9l~k`v2@*x
z4U#-pAG*ETdvA-JuUcnNExr1YD;qd%ZBh5$|E!99=WMQ*oVNp<!@xZz1;mt2%ZKrO
zn#~4-f4mwW-dR-D&B(x3ypFXrdeE-9c=>Sql|9fC;V@JoUI6xv_D@vJc|yF>%^-CT
z>)Z97g|g31Ip;;hB)L+9pC2>dS<oXIIXcU5rCI?Smn+ih^4=<$f&0Nt48Kf-hL=df
zo$XilE4nwA$j{`&zS)#!@%kuV&&kUw`bp3J%qu47AVi+72IkcU#Ms~8`niH8|MIyC
zE=c|DU-J#VCCuL4-W<ewDSvkM(~_dSE@vk`^P+Y=`8JI54Uf2>F59`rT%cgt%}ng&
zR2##OnG$A`?`%04W>e19-ot1d6^l=CUEq`sBpN()^d9wCES<aIHoZSwS|m)|a{#3U
zHF&Y{TZmG;Ye6(kmk303J8qY+1_WEyDIdJ<T4{G3CHE5UV*I*h4hTDIS_V`2Grcz0
z1!OG}S8sbCU43h4-fL1EZt<b-;M|<aI>PhnGbedNQl(C+w(wZKxt1Wkzt7Seko=AX
zu3v-BQSxR-9*ER-djX)<YEU+X@vCFku#wO{vii|w<Cq1ijzg=y0URR3I6Uww@^-m)
z{5v%^2=@^Da+tW5U?22FOAX0UzbIrRaU=inEBlk!)S&6ng5Mt*flcW#%E3(-o_}B_
zpxIl&2y9r52=ch5nFG+Yi8QVfILh>>Zc+_A^n|r3(`j2$t`morTEi=W{*6L=^PX^e
z0zdeS_O)S5SsN-a@S(!9*GF{>@UAg2=W`?Zy?-BLzs8dNaalV2QWgGJNjFpaKB#-m
z1-S&rpVaZsbtRDXm)E<S+JEQ4$W{x3Z}Yrri)j5I-?S*RN5Sa5*ADfeuySQZxSpA8
zbVr(5a9!d$?c_`-y5^fuvGZH7cIDmqTd0y#K=x}dR%H%OD&`X1w-Z&`t1}4;b4GYq
z0_7zXGA+hPPd5qIi^*>eYC>d(cQp4Bx{#8Yq%&^w)s`9)nvt@zsz;3XP8Ch*)=o8c
zIAhN&e_jY>)ppBrs!clJ41y@;<>yDL)gO>ITfi-K01=t`Iw&ApQn?_v*6#p>^olLB
zc*Aj}2Xg12F&q!_LUjTYl*j<ANMc_8uA50@_O4z!Y$4(vd10m}Y3n4>5?h#q;ZcZg
zA1~*xb9ykyvZ|8=T;?yRrvui1ImQPZ4A?UhyA)#I?5(w7x23O^?qj6Q-Yx9BkiXCW
z$}JAY{U#(jsDKH?$F1Feb<gngiZQw8v&!1V_Y%BrsOA>WnP~CsAahvWzqB1gQ%cb0
zCdP4-&0HTRTEsfuxmj{4gkqYeV<$`$uWyANUDnlaB4^`~J7=0$vU$-rpE>p4BvA`A
zVvL(`PIBj=yKh`H(b;e=%^8G{%2w^WG+bB7iAQ5fi7}zml?B4dm@4<r(qLaX4;K{4
z5dwpr-kFpWxj!E<vJ1UWOMA_MLQNevbf2{<wwp~rxlXJadJNX1X4j6#1|5LT5&`RJ
z!6mKMw;=Q)Ps4Rnkf@AZ&n<|LX_QZCDxHkpswhq0I;ETI)E?<)oTvUBxlw!}b3$FK
zetPtj)lX?I0a54j57(5il{eh>r?%JNW`sH`y(cM$RxL%F(AAv%M(*w@L7W5WGv=4<
zXBut$3U0rpBtjuVJ3<soI3){LQWNw3N?pk5pd458Y{ob3g}O_5@%AKL9v9qb?(F8f
z&i+~gMc-@I4dGd&W*ldXpOh(%4f>@q+C+pCP`ZPU?s_Ynk|tbDQ8m85QhuDACO<3+
za%O!4_>>nb4)rC*#oOcKeMPgjy_Ynn>0IMjL34vH$Uy^j3~JNB$D>Z}`a95FotXu`
z7%9=>LpSPv1y!xT*uS+r-t{hCrvF3V#L!*~+%eH}AjG8$7TB5`WX}@e@bN-|&`8d{
zs5!<wwQ$0S^7hS;7<l$jSC-8S*89fG_i`}a<(EE~<(dp2`uU&+-4Z81Ba)rgB<T7D
zr1fjwt$m*e`YA$fo|-59#7YZ^w#N25Vy7ZK%tn79K39D3T-zuc891YzF+XL3U~9>w
zR&l63*#7<bHln*gggx?|{rZRU7)6KNq4^1Ue&mc(j+`&`qo>PoG6)1o>*3-V#KA$C
zkC1Cz@Q~XN?*z=BweB8;eGn5|Yu*RyyMhnq%|`(FLkgc)MwV$t4yx*IcsjOK3O^B&
z?G7cBDQ<^_^<gh7rQO!O)Ys>6In6X|VC_g)J>MYO`;{+<MB8uN8ci<TS|53vqVGGD
z{OgEzoTR3K-FH%_%)l8W<BNWeUp=>Hdh@koyQ)8Q3db8dT&#|S3UsB8Mb2Ed#VHC<
zrqh<d3+6@@-63^QmsLgDOYLR>LKpWEyD97OL#M`!2fg1nmzqShd%y3TbF&DRqf;1~
z+?w7@O`qnzku86B)%{3r_p(a2WKidpVjMa)T}?H++nvBoCJ1*fQWXNyyAO)$e)jkf
zKS?z~%sI`-MG9yZh?qVkxIaP@t>O+I;VJzP6kMEcJV9F2*qWB{O$zM;UOvXpRllBN
z(ZOuZYVKUOMR!C@Q0S!>4x@w_rJ%-%=P`$~&n=Nx6S(sh*ez{Nf-Ig6w^ACSqJ+}9
zoLz)oE3|jakd9zb_I*?5R5!y-H(7#zrWxVn+os14KFb04{{^r|*GYTe95QGFI!Ycq
zE!4`UWEr8jnxfP&&9!}WdB{d`aAPY>t}V(6NV~-iLp;MQmyMjN+1669uKl=?m$-3)
zbA$kPwblk@YZyv7hrO0^xHCZ^iC9tUu=HHotoZlII0d&3keCuXR_IhWN|)PFrKWHF
zt>6dK8i+z>Z&@9Jp1Z(p1z=prD^Ic<w|TxgQxl&ei5+8DGmY0It#jSJJ{rVWIUCnr
z=5$4fe*FM(w6EZUNQ*!w2qOQcdt$0bP7Pv*w_exZ$;y*Y+LD%s>jXKb`8Qv%&d6}F
zD+d)indg^b2^c9mb+jI7@Z`&V5E-uVQ>Ea-Ef~>Wzgw$rvy-LO?yNUF5kwWZ)d*ea
zc6f6copUzpP4fycy_XKPh<8NY;O@LMJ~y|dUg?Yu*rs%K%wghnEE9BX>UBGM7T7#~
zrW#Mh@vJ`u*{oC34j$HX&Q8MwWL{;ZmV8N-z1(?!PHTA`HMd!QB2NS6nCJ(z4?xG8
z_Gs{>4kg&%dyw@P9dpV*Jbx&<428rSxbwr@@L1oFl;w2W_&8ZHj}~cxP)u9xn{4X!
zh^qA=$;EQ(XL~^ktTBJoP}Z}uIbjt&xYo?t=*9_3ROCNxDt#3W6_;FYrFek4SlZY9
z?QVPS?ord1I>w{n7EiW&bId5`R)OQiCM!t!xi_d2`a9}-bbSfI3-89-XeMt~YJ2?0
z)inksUbno(cvJL@pl=MKl>zOOhycYMH^p~|*3MyW^1+P|!F#jC4CrC4E~r|kEJ(UW
zcB8V|0+T2>K_-HK*US6bFT49{=0DO}$~|!2w1U-3E8Za9>t$W)^+Ot3_3GJ3n@Y3F
z4|S-(_e%+LxgF062Qco>Y)#M4Zy4T?HEOr}(I#*xw=>73LT!0;C~Y#Bq0`JWGx?ca
zV}Z?LT~KV$A>Jp+3uSlc=G@~0&mfP-U&MY^>BI!HW(P1pOsudyZI|6O+zpi~((+@M
zb@XLS_2O5Hy{)ckJC&%iV}NrN`+&_S#;e3?+DlbS?c2#xs~gGF6YQ};p>Fk4qw6yy
z&pO7h!28m1O5M{LjE&`2<F3%IB1`VN49Ggs?6EhUu|Z6{&+fRHyUE*H@!b-p4D(}!
z4F&f>@8Kjp6&0{cYbICDXZ_}eH*d+2!He7Lsi8dY^(-!qd!Ol#=$d&+jyd!ifRo*y
zcP>>~m-GRtxYZvwo@R4mVFagIthUZ^toSZ)bA{d~ssCh>j<o7u$Y2W-97=pVe}%oo
zFdOgv_O-c;<}tc-WwBTNE9!#H42$E}4`p*(6gVygq26;st#JDeRjPeg5-8&hxYVk;
zn}Z7}F;X)h_9T=p>D}b<p2trKwQLjv=Wv;Ron!Cyb)#2mZ*w+Jp3n*%CUp<Vs6L}F
zubx}eBN7CY)4Ph9DY8N11_LriZo?+Uk(P<i-CPXoi_jH5ZKLN8bZ3-}8-hUVow#LW
z{0Q{?M~PFNqj_!rgo4mBoNvMX+nvimRZTRXf*K%LCO}xksAUI>sdaPc7G}Rls~2bB
zR27eYJnKCVj~>+1qNU>|=yrj+_0dDWpD9Ld44dUfvn|cps?~>9Elqws8h$^*Q8)k0
zvvz=`w1_ri&9H6c!(VcRm8J<*<)-zkE^W`H#qFEEdKAn&Ixog(ec*!LdqGAG^b7p3
z?U+3jGPyV>Yzmz)*>?KAA3!m7xIR>>LHRdObf`9V7xL1dpM7Q9YxTwNCe!nQL#8(M
zE5?KZ{FEFJeq9Yvd<mERx|#rMOZ<8zozqt-^Fwpf+>-0QNcU<2PkI7&^UmNAf;kSh
z-eL8@_Mo2Z)LR6;V&Y>dsLQGCa*S8kw(PPlbr6s(-UJA#<_$<W25yQg-5huis-WPL
zVw92DDaByv;@<T?x;j(W_}b&XnOJanf)`1xjO{hlUQMq)_v4B|{RXwS)Ho{W_BDr|
zwqS0D#-3$Q?$=XnN;#duI}bj*-i&ztT2solPfI)cl0l>u_Q}vre#?38;Oz2z%X$``
zj-f&Mn?&y?mvXU4kWIfB!R8uP<|OQ#c6si?6;ihVw#Q^I)W8OMU0R*~s`c-(zOD(J
z^`W*NfthNfL9;vFaUgbK5^UniE-9~8j+9Gl1*PHh^JeQ)i1715->b1L0u&it8OkG-
zdoD%Z#b=Xsw~~#9*XB>KKicpeAX?@%3fE^<KKyX6dUmgc*HRo#F3rw7hQnjA=kUyM
zp=N)nGbznO*ki1wDsY0~;r042<$U$l?(rikK*Mdd;A~?-v(-LmAQ0ri3EI0(kUugg
z`RB*Y>(?K0Qj~T|EvG%p{H*3~ni+6KjH*X8$#-ywiFK`VJL@@I7H)j^VZNm_xJ%aH
z5KPY2Z)Lu#@1t$EjGdXM-&E&x8xNTa>Eit6K(bf$ZEkBu8+(k~iY#G@5X+AYvdPXV
zHUu>yN^8}rnGe3&dBg&<iY%G*1q4(O=_DVgS!_2rxt<_uW+LqZ%)$+jOsUC%jdi~i
z%}s`)I!*kpj-HLrOxVo10UYFuT!NDw(*1pI5?Qi#gbH<0p(0dmT^*X5YSezC;B)8k
zqm&ur$e5tp-&c8@^!V*_tugnov8wE#w0<D6rBozXL!;@YzFFGE^n_H+JVp&1$Pn=l
z<gWLH$rV+rR(LtLM=(1S*^bKfUg|fm!4{NVo_iP%zi&Mk6ca{_XoN1=Rbt=eyr~}}
z=1!$pDGfTxX*7d~&J!CT<{>hw6Cf6MgVK3?I67eim~;ZyZA3-VAc_gGcqhA26R}Pf
zO)>Cw2JWoM%?}sPCS<}tZ!G=7XMH9a1dwg&Cd|vla%i$YXgNp|<>;O+Ue4|qY93}D
z<L-Am`o_)!n6D+6xM+Yf50JO;=b(v(JFVFYvhJEHmZ#Qg8-Q^70mu_9=UPWoPCPJ{
z9?a`CU@RK7-p);&URJmAc1cx@e59o&`Pmacx0wp!UIX7HR3QKm-OX`fbu|xEHr?3H
zJ{Wk4g!?}RQIiz{$b6HVKi<BT^BnVEnHfrg+Xu9#EsazLzXjUT;lgd|ydyP`3E@;B
zn2>L8Rq?Sy{GfZ8Gvte~Es$EVd(0j-6Ya#HzG)Oz*JXJldr0=Lt9dJL(u3P2POfUF
zexuSauA17=zBR4bf-JM_X0@olY_z(8nsSQgKAB_LLO~~H>l7*=bVn#2SDV6Ixw0o^
z5k@Wgxzo2IM81KJDN6HC%CfJ=S@Kqyh^A4udrnnvkePci36mh<^Nc<serw{|8g|yN
z_rXHJG3>N1GcYag!=fo3EzGmkrgwOQD|@o?wv&cXf!qoa)IrwZHg?17X(?1;pcabD
zk%B>7UE7F?BAe;6PPYp6)mZ0bxR|}qF+|ua#eKxf0!2P#2l5VO%&^&gOY0PDU=Iq5
z$oFsj!~HFGeQ6@hwWICp;9-jk>8&8cje+&}cFJ4T)#^**xbkP96=74f1q3ErV=lcH
zu|sv9c=7EL%W9%uWm;fUmF_*uJmZu`VX3Ujs~7DOvY&Mii)3OFmcKri>jVz53d73%
zmS+2z9s;tW)Fphh=XqGIwqyUSNVB%!$^5HGD;z2qX5~w>)$E`@jn<oa9S)KpWwd0#
z5Z8rC!B&i|Zs$G%KVo7d$nhSF>KL&*l9E!I<|{toNUa<0qRct;0p7}xOi@_hvO9bK
zH+l0G!2-wq2!Ep*Q_>4EZ$IMo6RmdoFS8#j8yz3MFO}RCaS!;(xhXGL?hnVu^_9;U
z8oCT+bWNOXUkKrY-GzP+8Jo+vy|BaH31UT8wknQ&{w%4xKFeBT{(D6k=BS$^Qo@dg
zQ9+^YMusnzZ?vDjFt$RU>TL+>KGf9Jn-d=1Rlpee`6K~H>dMUJ6P<8=*{Z67gnIYx
z+`0Me$~%FL!e8%$AdW!I8p$l}Ey-CaF_P}+ocfYqyWYtcYe@9SW;DOl1oD#-(goM0
zxFek=x69Tb5u{ZlDhx*3Sy%%k!CjkR^d@!4>I5iW?c7MQcPy4BeAyD1zHYZ6?etg|
zWVL}0^|B&QxZQTL%+GuKlh52w)w*B3R$me2CEAle=BJ&ED=_zJMi(;hMOp%>wlSy)
zDeUbP0m7(K@YJIUzHg!9*Fc-yx8sPU#|>B3YB4uE2-?q_%x#67<rGO@JUQ!r$r7vA
z^eVmEK4&>Zi1cq(!T=tF0lW<#fdHeR_S{B@J)%$>Xo3>HoL+A5cCkC{|BtHg4r?-d
z!bM$l#losI3!nnhK}1@p7DRgQO+k872)$a+1(DvnlprObl!T6`fPfGn^bmp|B?Jg1
zArc7O6WQN=?#;72yZhJoeRJl_yz|a`=IGy=1w=cwy>J4_?N?@f6I~VT)gM>9bE4W?
z(@a<z$RQGH0jD`UC3y<^Q=|<qa8c4RS&cgYEf9K;@IXBkP`mYB6|=3MnAlOP&no7>
zJ(+-Sb}Y}o<<h^iYXf-BvX5lr9Xqn)^pTi{UHc0<tt^XCt)BqOaRBSv-{gOVVdy!?
zMi8yTY^37%VOVKZit`JjiAQhVQ5sBBlQakR!Z)MMr|-lzmV_xrJ%oK##^Wr=Vxr>E
zBS>fbx7k>wt#S(*v82mw%DD<JdvR;KT$8*WZL+GY^t<Pu*!iS6PWZq6wEzMYRcnsW
z<X65|W9Hw<bYCt9Ea=_V?~iwQcIUk?qT%%qQmv4Aemc<@#O#iFCV!*R(3!;CKPfZf
z&r2S*O;r3iO0Y1V`Y+4NAMt<xv50A&ZBg;%sU~(R`?UW1sFWSU&)bW-y_QBkyp+^s
z<q2nkWLpJV_aLw$#HJUT9kU)NO6%n;Bv&bybGDm{$mQB~D0D=#YU!Ez>~hVHZ^}Ln
zoE6>tMvza9iUXz$Xk+@?Wc<%GPh5_2-YH2zHl%}mplv2)yMvC396{UcK`i|RKPvIi
z*IIo@pj;=BM^HH$29*oAUip%LHuIL4vc?!FF{~`}->{`FX986=#{<wZqwZYLhS{IS
zfFKkK+!A{*>J7YNp=>J}y3-J8(IEAX5iy_O!P>jcqRBYNA_!^9dwIqB7QSA|d&94;
zuCBDW&RDxo+tu0K$T}3RGdjBbyL+w-4lh2<72$!Y&WR1}o0pv}yqyomAEb~ffM3QF
z=vn>i|B4VUMxCqzlPElgoR_b!88WUnE^dy15*#j)u;HwH2Wn3PAC$;ImlujiM@J=b
zGNqrSkZA;)<_c9~G%aYWc;{2y3tnK&c?(*dee~r$xO|~VS)8aWZ1#ozC1YvV0ej9a
zeGxXp+n0=k>#gA)a92+keM7^f<z<4AscFe;*aInPsSmC1?+iNMzDHDbBnkA)|GRtg
z_554<0g7{U!saY{I$bu%a5b1ku8w6%@T04x8PYa^n_Df8?++id9k8Y&NHH;R#=8;A
zlW}Rda)}iMmJ!hZ1tIFZE$v=Qf9?u8Tk;e=5`Z>Z<9zjbMXEu00%5lWp%mD`#mdg>
zZ~qRIc>)4@ckVpb(9pOI^ZwzIHzynGjxiD8G8JJn1|PtCUSIaSNpNtJ1!i)1bh2z=
zl&!87A#~}C@cCGQEANCZy%V?s{=>zT_mXkFV#QNlg&6e!O)lH_1w!$K*C$M#{}MEq
zvV@tn^MV3S*yN@O=myPBdrwU3myJ`->{uetZa^M>83Bkw6cof;w?OW`ng$TX_h3L-
zB|=~S(d{r)t7Z7y*M^`$jf!*(HbbEG#TH*$iVF{-4yJkKktb4gcYa`mZu=^TbB9rW
zJ{a4}eO(C9uPU62IvfDDae8dhIqv#r$+>1&*h7)6xgW$Ve?3VdbW`0+2lLIK7VwV{
zY1c4lt@66!Cq2Lr=`Q`OSL@x588npda<QciAOoDa{NHr0>}t5aC_suoY^0xw`0lW?
zVSJw9w3xDI6TMQ2uVr#-!~b15Fz#9&)Yg>B!S&-6Qx#h_A-3g<S6FD&G*o?Ggsd3P
zE?wuQ?R$wbAUy*RZR@(SZ(xnW_Qez%?Bhp#F>a2dLbB!3b7R_kz12_5Qx&*Sr3ajz
zVnbdwa)#VC2E}<*iaut5BdSZWEv*l?i@s2Z_67E{_5{lBU$;OB7q4*$#^N8z7Wd!G
zl{5>yZ6fvc@8|m!-sU?25TxjLkSm<Bf1*q7(kol`ck)0z@c=C`G+QkCSaCB^KDAi4
zQ_<^6@%8Y9)GxAyA_dI-%ITj7#aVL?%bAl2y{MdGU4^jN+;JrxxIXc_j%(n^?S0YG
zlmG6Aw9}>e4j>O)HU7_on~attfKfgLS%$GLndX`nJu6f*6S??Hd}*B0Ec?>I9zkte
zw1Cds{{fAu-Pz}P2eHbUnx1O#{2>rG?dR*bz%QcCogJ<c=CxL}i{seFCx~8v;%reP
zNRuA}u)@OEzHt~83t^l9MjjIBbpM469nj<G%VSJ`4ei782@%J+PjW8_ehm=Bsn0@`
zdQ;VQYDfVPk10-l*-U;nRn5(yqAc-VY%w_28aoIHz9pZN<6cYd<<Fv1B%>b-52&Fn
zc#ex(K>KWDk-UHT9-CIV=_5POgNcc->if*C3fdI0z?`r)mqeXfn4cF}EVe{XbdIff
zekz`Rf(BUS@OA!6JKKWLOIm7ABOm@46m9}K&nLqkX=yz@?MK#TB0CzlH2ma}intHz
z^x=;wxZj@|Ar)#i?oymQJODM5`el-f$(M@v>(?^UvNVxubE&!I7YlWj71a**<0dQ+
zB?kKPw7l<`UDHBc8oGCwMJ;MS3O%BG$91}QIR3XVyUCNFf%^2FaUddQ7j!TB@(i6p
zdeh<}j4a~XTNe{+eZ!5yty8#*t9cdIAHIwop6@bPBi19d3N?o)iNEE=WGglcrYyD(
z%--5Ed!$z|D{n(+0V77Mm3=Ermk?D}aQo@>LAQmAFdzZo05Mnvg82`;lw^kv7y>#0
zxI`ipGtUR(;q6<jBaH+L8Jqmjj7%iuD9fC7Qj5w?(ba5716{^lDoN`->f%@d0i~3Y
z>QnM{JBg1<t<Ip1<N62fF`eatE0U?jfqOa2<BD7^>!~13m4OCXgw<Em4u-3J^pi6H
zW!iSH80YGwOgfRMp4D@YjOw%zU`>6s>2i*SjUkMh*Tv#8yvTbIb=@jAbSHMFZa!l8
zlg76~@%gUdQ0K>`ov}KrIPI#gL2#e-_b8?SQ;(=t>KAkBp0cAG_WfWr=T@oxez&V|
zTMzWK%&tGEBd?DA>NMS8h_?Yf9`FiFg$BF8=x4eTMm<qgg3vb9kan8m0Sgttd>0%$
z#Pn5RY}m)5LFj3FfNAfjZ9NjCTyHD(Fa8ZQbw06f7OKG-s0>#r-wtZ$W(IWyT|@5q
zso#T8Wy|bp8-e~M6TDjxX?*&hBcJ~Porj3qBZmgZR?n-_Zk6AeNV-9p$0*T_{$fRJ
zperqy%uOtdcL-yU5>_B-`Pi_0Kjz}%Pf9uHjVqq=YAd+yV96FE{!Re8KbV{?%(*?v
zj<*zcTte&i4Nkr+tl74$d)RFi*?SabU!TH<mjv2(6)~W^h#v!|pZJu(5E9Vzj2P=~
zE6zsqaZ~Q($qkmAa&%lATH*pzuRwD}V9wG`9b&>gcA$WEhrE6!jC@TV?_IO)X{r4_
zWLbG-=Zsit5wlf@UgY!&reIdZKB0AY7K%L>wt_3^<<@lsUWW~!mvcb;)21Km@@BNX
zcI>;q(qRE#q*I2}ro6o?Y8*S<0h)Ip!o)PuqF1u-h9A5ugl??dMN3q7zSO)l!qpua
zEkSFgJS~hJX$n7o;4zlmL%ck(d8#UJGCwe>#%<yN@xipsLRmF$Z}$p($~Iv$oE=>n
zI?NZ%)_0ThE1ZcJOF!rHiwW$oomf+FDjpo`{qVh1lC#}-^BEJZ@oluRMY6S95lS9Y
z#XKe31C6QpRC=R;e+-ckn;?~mS!p)w2?cO+I>cq;W1g+mKV!QKoLY|y5-eMh2HfFx
zmHVxs*|R!+q0{QI9V|gXp-%wx{(12JM1%r3UUwC@p-M+$Ge`R$K3F-9=jh3{|Eerb
z{oWNi@OCfNGdoYwaEaA{i#8T4Jpa@9jyh+#NeB>afWVWJhImCr8UvHltlMt|zMhb5
zqwVpOiNwOB2X1n@iwvjb<`i>RWWyQ}N72t76v1aLI!<+F#Qrp~=WD^x<1AxH>FKMu
z6#CIWI%0X}9h)9IBjo0P|A`aMq}|0IxElTV0X5Fw*g2$O44PcA@q5|C1DnRl=Zx4{
zv%O@DTUl%Si01!YyZ)l!nsQaOY}w_0rHt42?_G!rCN;fFB6agGF4x(w1w{3J3UTE+
zU_(nxty}<$K6vWLXP5P;^D3>E!AVZ~&rnCX&gT8Gi{BHJGcoQS)9ezQJacqy$Y=8~
zw8S;0f1ANO{+SCv>UZmfs*Viw-bI2YHT9?cL|wSAw2NyE`R$*m-$b#JA<gc<<oJJW
zrDLr^`r5riXQLW|poG6VR;;WlLm!FSdnT@y-v-OypF(;7nw?iMbm-zAB1JdFBb5{#
zzf~{7@tu0+M&3~Ogo#~bIc%3aXgNVq7_7>39qNAIuWJ@Z7X`T<Y@`F8#CQL6n^<Pb
z-Wf3v-96JoufK~rK6Z(`+$63uCX<F5*kId|StxorCunpb_<aewjULG-01#JcwKwFW
zfBmt|V4mvx?Wr1np2^t1Nf>H~d{Aj^vNC8&EKNocDg{RpWC23QDUaDf9*n;2;8d*t
zMl+-mxxTPaFQb%7?ea3h+5NIb2Kn={3sZK5W2}^ugq&<jX3zVJXy!#$+SYzt4xxW)
z)}K$E`wwbhLv)%zmfv*MHiAE{(d5qZCTbTxxw!Q4fL7_P&DGnw7{wJ(dndsxY+vq5
z*`hSU?W>r-SIbk-$^zOM`PFA(Rq(6@E|f|^D;E}W$JQ(e;a1Xr0V})vs&xYv+PJ@5
zuC4Y=lAcNa0cm{`%S+$l2YD^KXXDD1&`M!>f|uSs7!g`ybw3TWhe%7OUpk-ks<?>X
zeL3+-QeW%yc*L$F+AqmHvG2yjN|vn3-Jte=G$I&a7f(xLJL@0!CK^Am&J3GYesYn$
z+ax0cCx}D&?j-W{W&5C<Zx_m;0&~F_-F~)DO<HQ}$y%eM)UmyZ$gnR{=dHulH#$GO
zd6}xzT5TY#6UF9{=lRjo$ADR}D@wwC1FIa^bP8Ktgv?`?pPd&=XE${ys^?j4O1ehF
z+}k3(U4#h{KGpRzo1E)j0+%`Aspw0rXD1<)A2qCRId>LcJPTaxDSmq+3#cx1RF7~*
z;6S*cuXIFB%ET&+C!pUVukxjsI(KvPT_-V-Jpqc|z|dG#)nIVv&CE$=Z#g`sjp8R!
z|Bua7?hp-iHa%8fFD>t!F|UI6a|p*ra%yD9s#5r4-3BEe)KL#-vFRuoShj4j8m^IK
zESkIDNpvdWEtp>%jI_DRm#E|jLYyosBa|UbruQ(h^qW+&q0cES3jTSEBbrnsWn`&-
z;^&K19+p~C9rLg={$w#D=8Yw7V?)WqQ!6X>rv|RA&=N>}x~5H28KE04Ji2bO{w5{M
z_8k`;@@hn}`+G*A^X~(fIRvJBA}_o;ikSA<^b8G~Fd4beOv74vkID(XO}+SV;S{%Z
z1N0n^2E!u`mVqO`u~!a*zN}>m2upvVCWeyrE&WG9A}zB!Li>He*TOqw|I}1_1Zjja
z<~$L_f?^((j7P_<ElY5It@A@Vk+a_HYIO;GK<3GWydSMD5{?t??>1VcJr2b`FC@K5
zyPRCpqFCL65P^qVelqv6881ulbm2WexXGvaHnUf4nXd&6qT$o)OiK)Vp8xT**>DSR
z1|whyofVDl#v2v$rS8wYOoGz*SeZ_28S-Y0{4<19wkn_J*H_@~*IirFck=3oo;KaZ
zx3ny;QPx81o&BO>GoCqjQC!fCQZ+*Q>$J9UgUaw$|L4+(z;G;)v5rQic2v1e7x9Rn
z`S@$a$C#~Hzfnc0&KrN-E3fnj!<-6m8ZYb6pX#Ya@rTtEcq!0wTQ90p;+j+9{U=_@
zTQxE))TgCi$#aiTpqs-ooHlI?$4yV=``q}*DUNC7FT^Pgc|l$id?|}0ba1dXuu^&I
z6|-gpZ%f_Z*hOZ~oTBhx=iH#gX=S52sLq?#ke_a4Vtp~oo5cwRqVjQKq@!{=L$^TK
z`0OH(e{5Zn*ai;LFfb_On+dN?@~jB{^O1F6>FlOGDR=Vzk<jlysPV0oK@05mM36O7
z0jADcDE~yJP^{>3Rp}6S>v+C!zldQ3Pbd$ypSv-6W1WiaAc4gj9$&!nafq2;F|HuJ
zdp%{pyjz=J`LvMWp^j9PF;)(8h24_#k~wObI2~w^q!czvU^>ycy<1OO*<ukbKGmW!
z4dy>E$e!uoVF)v^JIp5je`7*5ER13H0UB<mCYVggO!>&KhWBDK&W%b)mXW%J%WE4X
z;Bf7W9v(X7aN&}t51AN6Q_?ITo_<j}>6cBc9R{FJOau1ji@3rwE=X_k<<yaF%bUn`
zl(F<!gMS9kYo_Jt!*EKs%x>E%$=G}hEv`NiN{KQLa!sSy+G^aB3*B7dv;f!fhKz}e
zj_fRo4JtBEr7b>*hmL@#;Q4!tM?5gN`7ef;BSbxh-xo{Zbij4iu{X8&I&^LV0ewYF
zp5$a1IQ3{1#>+^0{MWIeFBy+TvoErFS@YjWsw1!B{6Qv{qbSSg`-{ZkU&&3cXb0>D
zO3=0wlp>EI`ZLYbyL7u$%y4FsYL>GOj1#R%!(9f{l|+wBYsF8#zfj5)1x3<0j|MMO
z8&?bJ8*hvDkSM(?V0d%<WJF%dp(gb+r=1_j4!I;2LVn@ru-%7kezhO}x_2#vs5?jC
z^?O+edkx*x=Yu#{AbY;-aGSQZNS0;oLvZXJTan~Y;NMyNRtjlF&Mroac{RMur8iG^
z)*t&EM)#x|jl*4U?>>5z>#aspH}o&vAV(jAiEKQ}dRhN;c9^$+9G)Y$?y;r@%0oLN
zR{y4HwmFQiMt-vu>*Q~`{FcHE-`;;Zja<FmyVyxCp0_l**o{*cS<Gv?Uz{-1?7_S%
zV%q>66rnq>;GakScgny1UU3}=G`h>WlR=NO{7*f-Nl^1Ae{hPByv>A1oM>r!vdPH*
z3OXq}M&RnkR*m8>yDd0hom>67nabBfNybvgGvryBeo<bvR685>_7|RN0bDPUj$*UF
zV5){0o(9w%QqZtK#5rsa@l5$hWwR%<SAgpU`>BNRtjlQX+*~Md&1oJKe{Ic37SASp
z-z0L&Y>$T3Od{7fl?Xdo24Y|rRKJ>IYoX<pvaq^GyJlh2J3``44xL8>h`@!KX$*`J
z`UMeZKchg7p(mEloIMp>>Nbj)&lPnQFJq7X-X=Ds6z(+7cq2%?ZGl_&BU?xJw7D8q
z8%n9<Q-%r$Lbn<eimPl$nK~I3<HZ-QC;ThcGE?wk?Q03!LqOSpka(0H65XQ@dEw29
zh)~08S$DmzHP`YKx4s(d)ewNa$<=hmI)>T4bs#6vmRHE56HF6OgJU_XffJ(#N|M&$
zVa3<PG2YdxXIiL}s#UHJ90~+><#$Pv#xhYq6B*ZSfERo|`Db<ThemrEcb*kd*k4sG
z=hDUH6&vwjqxcr0b*oDZEfK<(fgm?YO)uXiy19+sFNqyTkY3hF`Vto!_g;B_WL2vp
zoa#lCT~8F9RC?K-KMmb*P{riMSv7g%3k>LPaQn~q(C1lz-&EoC0T;*%C#m75|1#}t
z^tO>*{DU{512{-oYSd(nV5h`y_q&iz9-6qo5Cqqxw4iQOc6TDF)zFXdwS;JJGmg*^
zH`>jg{UHPG#1h)ZWh#pA17%c%3z!o=<Mf|yZidUYS*X0q*0!)$C$6kI=AO__Z9~FY
zsFszbzlm~Fn)<mLP|^Z)%<ve@{+H?viTo$1-@54<iz1;ueODAefph+)+59XY$#IJ-
z16i>yQmO6LA}u>Zz3*0WU#ICaBhovY6dA&#yAHGZ+Thqk!71I?Wm}wK;clz6sxtLH
zywZ{jT|1eNcdn#NuGQlIUXS3O8Z6u|@^8$?F0eCi_iTU0Di2IZuMuuY9tkD?3=Hz~
zci_4pr+Yhlq^}pToNd0qUn3&x+RD~%`v~%S%nAYQd7N%fUSQ7<{PHQ?YTlH?Q5~NZ
zXGOhYNN0{0p%>Ihc%(5NWt&@p@hTfrtNbwVtmbRA$jfWiWrF?RJ+yxG$`3UXN&&hL
z@lexz5Z9V~lhgjodF$1=MjMD5zC7;7$lKtat?cjSWtx)Iu~R^w^V$Zjzil2k!OHZP
zfbTDTy&+Y)#nqe37}m?<|14{SePI5}r`K1`twn4vB#eDi46-mAvo(017Y?)WrxBiD
z1GH26mBb33#=BCT|B|~Kd6GIxY*HAct@t68X0i*G1KyQH<o20U7YcpI-fxj_7Y&6I
zsmrQaQYD?{bJP-@jIu41xgFgM^pk_>-!K;#!c-}AeOQD9-qqvM$oz8o%ODVnLy3iT
zjR%(v&16DZ?q)kjoUEs098qi&b$}e_g@=n4r}@=WoD$ZE#?p$2Jvqz}k~<H6Mw^vU
zWB#<-*fs%Y(hQ@fONO_mRn|WoF{Y=o?nvP@vDuD`5ndbpXCiF>Olkm$FULc!BB$o_
zYO&g6h;){*SlVT@bno@iBLvt%yf6BVG22fL#ZLZ&YI2LRZ&vJc+SK-=JpA8t(l<NT
zd@P5;73B<dS2z8BZV$U)shf<JM(4WIV{a8aRKM@lWLJ#mu(@S9q(EP7mIoZi*2~lX
z+dcd_S_0=mquKZ65tog<f7yuE^0Ydvi{jqhyUfaY1D!c8wsCn%jt|D6f7K6*QYdA`
zl5UXW+gmfQkF0uDLFc3H+H>Oem32`AnVeFL8gr-VQT(T*pWsq$((>zPU!HXl>g{7k
zdb4aKI6H*J;%hrVM7sGL%v20BJ{+kPF_`htt2$?~jHD92KT6@WkfEi9J7P(yHRcYd
z?8l}OMnox1;e8%e-Sb7ZiYs68-g*cRvT~C<!naqT*tTLs#Pc7)m}kMHPm=zP1p#8}
zsSfy6uLgskH~AgryCXq3iV&m&)D)yHGo2>Z`zI7@%{Wn+H>RCu!*1kJO!4C1B<_Z<
zncP~9{gR8DYVuT>_yiAlY*kjJ)}R$+l-5Gq5v2B(`!ec0iFHsP%NzYb&~caMbok-w
zb^|{<KODOC>qUwt`^M2TpVK&gp8Z_a92$KSJZZ)U;nAC^M{GRKu8KT6^}tju3x>*3
z{<O-~KG29~&%I(S%@4;V4u3^4#|C*t2YVTjvrw0C4?})qUW*E1DL*3c92|F=`Ah09
zCqWkL|HTUwN>6UAGP}dk+_t$^Gq)FB9YZKR+di8kRdbU+hV?6>W~vMJwNqV5aR-zI
zS)Nw=aOf0311g`MZU4j2=K5ddvI|A9Qy%SsS2!ST3t>0JlYDoz$<*(xtPnqw-!qe~
z!jUgir-O8UKu_0e^{2LygDGs3z1g)Az?^X;-Pi3pCw>85I#ym9xVb#_vihk>o-JZz
zq{By@>G;c_F`RXYO2nob*FZn>=d=LEBQvIkhr;USZ_}1K92Pf5rY)!Xw$A@zoLbt)
zaPL@hifTt<Ddz$_up~`3HL21UUky33<j1z%=K2TUO}>_6R?O22A5tt{fZC!Sx7nUA
z*P}`ByLE32Ugs04%yhOmpnMsFTD?3qR>j@<11|~1N3sJ<#YkWB^K?`;@}HcfUboo+
ziT``|O0y?*Oi8a$lfB6aOIqHHP<rM7_Q%tV{USJss2-5x53Ye-w!U=|E%AUatxqV2
zqrqOu?7aThPj6ZOehpnKFkqYt>>v6UW_p7>^411j;p)HF{J^bahuyjV#{^*FusdLb
z+X+5mXq}7oH)4nnKOBX_(Cqx-Ld!qevyq+(+|Sx}>xz&>3Cwe)#Oi;GSxfGd!*P~}
z!F~?}duulIu=*YJ-~&=dd6|)6|9iohK3(Ffelx!lc)@N_`zbVy$3M^VdHxOV;LN)T
z2I>adfhzp{!h$BXFD&)ON~$WxD;lel@dAPDfB!|QEUz+Fmvx6kXBj`Va0g{1%VnYg
zu#LhYe5=<js8U0eYU~R%JjRlQQG#f`l0cu+x0swvEg!Und_+M{$FxsstJnF<AG~@q
z{FrHp+?8FFxLJ0r74hr$&|Nj5=%kYErMJDvvSwa4h(`PH$SA%?rlkXV8Yw>klA3_@
z11}KV|LXy^KEilwjrbL8Pp7)yfa{GbV&ACgo+4Vxx710Nzp;I|l)!$$0x4JwMf~PJ
zX4NQLmQ@KCqlWzq!_n-K30)$c;%P~1!Hz0pqH!6q-ex@Ta3z<uPeNI@cjBw^!nBG8
z5}4L1GOVe;CgfR|0uKC_SJ0^8w^hv*X)-N#kZ8+3dS5sC9SB0LKIBM#^Tg(7W%Laj
zQJ{Ic-kx{kDTw`zu2BuX=qlM7t%J?AODH&Z%oogL^58u&bKT1)8iRAT@+997RI1V;
znkndo)4@CTj<1Z*`4Zog9en1f!*crq;Lw+YdE>T6c**7_Xt7R3AB8aB-XG(P;Fj}0
zrvje#*};9H`q!%KQakcv8`5$<WsR86Wg!#VA*k=*Gei|tSKJGs2Vp%!g|@j6;esRd
zq$lR+F5ii-EXlTg)v<09s0d#TzLhCC(eS1KO=~$3!UZ;FQA5|efSm}w97x-J=BD+c
z*j~0;Jgr1JXfI_~FNKvg=)jja%Dj(@OX-yhH$U>`JwTuSQ^A>67-I5*9YyIS%+u`L
zSU>c+&9xa{ba<eB*r+!12~q23jv1b9rMa_mop5Cr0&|?cihoUTF4s-Y$M^lj%H1J#
z#H~cL$mKXW^U-s;du-xQaU2vRCsK`j{qaV~cYU8lm-%_1$NTwU%S6oj{=M@Iw$IjF
z!Wr~rW4um)hi>+z?s?yDt!Wv7zIu_RtXQ#wW(LV1@)d&E{h>v^#K`g2r?&Qp+cio>
zbZkUS?KHAfKRAA4fjN#`>K_rSFVhrk-KMk$i$0kXZzwQf<c&Lc$#+ibN|V|1nFQvn
zytV41)FvI*p&olnAZPQ$Pb}ieIr8KmJ_NvRC7oAC^RCjT4Ms<Tl~T5ArxUsy4w#o6
zT|B<X_6*46c6zLy(LDmpwvP9Pde3|jb|c1brQ3NoH^#5d!Pt~_V5<9ZU(WfVAJqK2
zcepU$^G=L4d1*<Xt!+{)Uqlu|hZGjiFix4OAVs9E_(b1L7$jT&$U0Box16B(Z}^%>
zqP+FT&la}GC^{&J^bQR=g{h#Lw?#|6n((ro2J{JIEEnkP&o^!`b%$Y{ms{%jWmYej
zTb%75RDed3eJG|ezTf%@<V>?zPF<Y~xVZK7uXaVk@hj#ks1?zC-OL)jgq}=&TU2!s
zn(aRHpr)Twm%G+I6kK;~0V(+kWl;-&w`d{V(_y9-_Dp?y)yp!td=<nPR0R1ionG$v
zc3PAn%;-O=m$K|U?EyJDbGd3wgWIp0p}s2=by^_DcN%poOGCg!UKMPNn4QMAi}J)*
z5!Zf3z;*MQUd}cYjkcZ#HTDE`%65^EGTIJ#3VV_Xam4cKC|;4e5p;B&l@9MejQ)Yb
zpR3&Esse7Aa6Suv_w<BT!S0lN<F3!-x&<Kc@BMZ6+DO0hW2-UWWyn&(BOMtrEKJf7
znh|SfWGnQ+Qbr5SPqg@;=5NHk$^Nil7V4{Wke=W!b{`B*wSD|bo<X_nP~Q>pb^=j7
z5%c2C*>Z-+)Sh&mh>##xLxU3Txrzdxz^~AE$WwtP_a2gs@6`D@Y+ZIe+VjO63*DC%
ztsqEpcBDVKk>BQ7IzqI~te7@h|CqK~Ze9AQ(VA7XO~?Q;CPbeq5*<YcJhwXzzlqj4
zslK+~zeOufQb(U-2wxvHd_#m|m%c6bN4;BD>bqk<CCqa%bmxU=t7xu2|2=x0M@o>7
zMWe=a<?S{?aAa7sElrA@RW^s<OCL+q@vU@-Vb7U9o)i40;B8fE#SU7Mj1iy4YlY#J
zt=VOE(|7{pv1inpxeUPmH&oHo*-g<*8~nE<7N+vzs{7?Kql9*NQgTo1;wOhvpUx7N
z@6fW^MSSz(*1ysqN93nBZ>2FY#7t`)CJfX^{?P`R_ttUm-EQLCswjTGzkGukUYlC?
z|I`%ko&bbfv+<1eZFzUdiyLVrq!iYwoyvgL7M?Pq5*Sm`=JS4S!b+xpcIPUFNl<C`
zltv0?QrD~8yMQaJ0)v`A$H5M}8K1F1kU20fwRPszEbpe<Dy+yP`x5BGdM)TO3$xTF
zcW0V=J$m49*Vd}lSZc5~ftIyCo9j*6NjdJ}T=|{gx2jS)xfr5Kwp4=ac{|x4SC7zP
z0TX=>4IfSniP)%tOH`P-xfS$c&X&J93(XgB9DQSC&Zg%d-VbH@6(u=#hr2B?zIX?H
zH^{+h<J7p1+i_B)gQfAgZkAA7ha+Za(%P7c7Ctk1UR-!Q%=^7i9T%Cq3_~@Kyns1{
z;Fjrr;uADm9IK&DgVg{icJtWD2=0-?*@pDb!)U89gv@<w06o~NahbE`tL|izc1rz3
zM|ezs`Ne^>RIiPY4TYQ<=s~JQ=%)B7GQ4Ynr8Yo`m%U6M(;RLJ2{LM@%pb?nE~*D1
z0l}!JMgK(o(*OBF$;+b<JrQE_O-IPl%^z;oOC2_@GauAxbO(q|dGfXqXQwg$B4~*$
zNFC?w!guMS^bB>2KJ20*%Z8<iSsJSBEWT|z!`QThB2D@%K|4BGVOrU`UUc-d7yV*|
z85!)e)T4~i4xoJKw=$cWy~xz-#z?aB%jdSnREdk>mM3NdKk^o2%AN8h$+0hmj^z~C
zPAgd3hB(!w=IRNRe^(=Ww=>nDc3&Gfbg}w(ovlGegslMyzCPNVA>WM7DqPN`&^?>~
zqdWTKjaT4<thk#BhM<3eNltx&^9r>Uw5jfEs+vr;SZh7-Oc6|3^+!tdVnXz#5ph{{
zNj7oA5mE!wU-uG=sLT1&Ato8E<oD`S^5P{DOtObXWOlH{>Lv^kXlq!#S2Vjie8(FB
z&uu@qc20fqQtUAX)qB@YM&SNBY_-gU9Sa3wFoss|sg;kZdEcVlZ3gAz(VFrGp!C<i
zdQ~*rcwA!b)H0P67{`i&tLU*NIk`@DFS;&AISHC5Yo|(iciXKc$G7gSxzd(>&OrPe
zH#!$E&p%8qh8crR&F+z>GdP)H&_C@zG#7aTxQv9p%83~nu&Mx{B(S^}obvOZ+d1Mb
zM`V#;kompDnj$26H%&bHtDF54d!Nu02PHE2?V^4h3+n4&`i(wC6G>FPN}U>aRpR*g
z4Xqy;SB7*CN_B|l`Zl$n))1^FT|dGN#)g?SHc?vxYlv_Ad6hR)jsbK8l3<(QG`^H>
zcm>fUovc`f-#t@;*Fq2M>!MSrB?0peZZd%t5lZqEL+3S(KSf+Bdzop@J+y~^%&A;*
zzl6)WpeF8}z<I7+d&)Rf3ES*mUT`f9)r=HL8POU2rRwBNE!8xZ^XPAtSe-k^WI_Gi
zqY+A`Ning&dmfiQ8BGbI$WNCfCeFfxy)^u7AG93HptV7lfnONIHi1>%9k4PnOhtj$
z1bF2yguA)Ya^<BeBRdtoa}P9*b<i12>d!6$^egk^2$s0{q5#$MQM4F<{OW&YY`j1m
z8HqM5eADs+u@KV=)qG<!A=h}}W31cK$YQFe;kS;Ctw;6u=aZbu?0Q5ZnbtEKW|KeM
zGRJEop#r9_1ZB8o;rb<gvO0#Y2X~Yk=AD*TmPPh-&bYW=mi?`HM7>KRsQR}HLw-HD
zAYn%4++olRxL44Ig8ub6EjEXBG)~#PT%GmGBviOJ@yj($ardo$$Woz%f6vU)20^@3
z)^3cn0ob;woi)*1H6b^nwwWh=vY`#Gj^Y9j0h%g)TS%Sq9bv@m$9JHcd>3NG)Q3o=
zXp-*1`bo~FM~~YnZg<smEj+Bh?uUs9__6(0bKg5c?_R0ckSOGIu%4rX=r2^9?g-wp
zjW}vA&KDcP7^5NJTw43hz-8Q^=)TYyOCiyd0_R6(#xzA#zl^>=V2)cSx8Q>9vtDv*
zc1rY23E#b=$=y(JcTpsI3E0Nf)N&!d_lk0ZDLolK9I)>25#}%oq}?{w%77=Dsp?Z&
zHdk&bHb|82<|!7rLBy}W&#qL4Z$wlXCz~$aBhn(cLN}k$cGl!my01`cpoO5-SKbt)
zMwJFJyOrKc!QHeyclZgufIDaSJqel>`&&Foq~*$56Iz`qa|O3R&)<u7H6nuNl|GoY
z*gg&_`a<4MQ=SRh4fkm4RsE9s;x?JRFUm&~3d-J~rJYywQbM;m(ddR7;hUf$VAofL
zp6PEWTzOY&x9pxGqm?(%xNyODZp1jq&&OaRcMs=3b_EBDt9$a*qP;_jHK>unt=J*a
zw*BJF%&g5;qFpfjlW8gGU&=N5OV8j8X$-%IM%Z(qWkr9^q%uTYOqJ?HwyOz!yHeY5
zPsWRLp+;tNJh;u?e0#dr{Hu-UQu+4ZwrRctQk1as92V_;K|J8P*WG>Yapij78N{*O
z)|({q=dir9^GfTGU4(pX_ve9a3MP-Q8&T`;v%9+Z+2eS{v2wY4nCd61EiGOZWBZ+y
z*V}C4M8b9};j||u{|98fl>?7(ZVR<q-=-{+9MVokNUpf|EsdTCqI30q8x_Y5BH^$T
z$Go5p+(Yj|i;hzMPUBqL<h$mUKE@uP?H{hA>*YMOvhtRRG22!FSrO6Wdf7-KFjb@6
zO}lGivDN7~bgL}3+0#d-FQPSU!;umGRk@@{@**~nXiHkRcia5#KhXI<EkNUe-6S@3
zAQk(@x?rIpz-g<yqvsd{j1C37dJgG>nKLapJBljIkL*BxCN;R>%uX~kDVHd6noIdV
zA%7EA_rN8|)jm=*`o&fGucFqGkOLHc^np@j(kf&!NFVX_?INE8t5BZ8y-!pZrq`NU
zU2@;R{-?Gtd#-w-794`X+0KBCN**>8pWqcHJlrejt&ZGJURoGAueRoysm(1GO?$Vy
zmRV;lK__IV<NHwt*#8rjqsFUzu<t}Bb|L%xWlc4T;+P|P94QV*j8hqJhX<Ky#yY9W
z$d0L~m0L(F3Cl13m<_zjVNelP*29l7Dr)Y5W`AWe8<JY=0=g^cqC;@n6)ddKZMO@W
zBUj@{Ky&ZD8dch=U2CR@FR#km=}&@@d&efH70NK?(xpKfx2Gqp(mNK8e7;6cm08~Z
z3pW1EeNZsmu9w_pIo$ZH#T^sau{G4A{t~<3Yxsom1#B*6vZuzLI+&w)!KU;5jm%Mb
z9e1uVU*OW_Z&3s4U3vMzT))dl6*khn&nn!x?u40~9<J&{d^4+LOSunrV#yx^upaXL
zHjfAcQrH~P1DD`gcpwhUGg79`1%v0lER0@kPyDy%GOWD$@#`;x>3G?>^TKsd(7IQw
z6O?<u+I%pKjegB9&7@>;X~YsoV$1Pgm<W2>_cdsF!nen9OVTE+Ac!g%<m*&LO|tJd
zydh{4@sMHWPt*Af*kIrnIEd-Hw3MEnEvkr=Dqc2I@hN$les(=+e_PQN40l2(eiFks
ze*}5w_J@$o)2eRE4h;dNsn_^_WSAYH0lpLx?C3PTIXpH($VA!{_nKH0sO1J2#VPI7
zpO2F84PDgkN7NMts=V_!c4_gec;+H_yzHI>@XhQNy$j&^dJHei!{kYi>Mh5NkS9zH
zQS;tRe;tLPKdXAnxzJLJ)@<_zaJiTDg8g-V<`*+tSyWQ2jVkp9BHNf5I*Zy`%tf=L
zotsB`Lr$vM(_M6)jAj*y;^<5C>O!4~+ie83O?bG4Jr}z9eRaWIQ>%~+G04GDa80fS
zJk&1-1RbX8s+SHmh|JlOtDc$y8My<)$3PLK5J%79rT?A#@_!=f!l+;ZRoS2S9%}4U
zSNs^JLg&_+7e9Ydg}4#A{K-r0XHJIx%o&0BE&M*E%#aPQf}6vuGKF(3+w<+}42_fm
zVH(12F;4_u+dHMk>^2f*OV!DrjJVKOgw97fPXub#tuz-;q9+T^h$~c`5m&N}w+p(J
zVrY+v$edGm@Cgi@N}0FkVVHSBhp6;hk3bPC&M#_}8#jkUc<gN#C7z5F%(v&5$R-WL
zinyk3n%yR@D0(At3!Syopivk^iJYenfNgwIex998MTt}=RZ1RNjA21(mft9C4r}aL
zh6(&b3Nz2IfQF#*O0)^1^QR^^vlrHHjL9q|o-(2TeJF+-SGiAq$a&XP>q8L(a_ZQ?
zAK|hr27#(|qivgwkYMyO=l5T`*A`<`!A*G)%?BDM8BT1jmDbT+Em}-&pvsJK5pSml
z(nYDZAhr#d5s)<g2jgnL7QBa02b1NXowl?^{4m<B_O9*i`3N6U-I@tuVezeng1BJ0
zUPV}@9U09Moy_LZrgJlQ<fdzZ3+-!${1&(4=}XJYBYLK7#H}Z{N;_fLN$gb7^XEs-
z@E*S%|IqoWM81&_+{`>fNLa{7-{yVvruT@^*b<%{v4lHV+?HUU?#ge`yL_CXBp+aO
zFV{oB8skmKoI5*$8!J@LbcGy0t>NGf$EFV-BU}jj75OUY_>J1i6(xC#Thsx649Q>9
zj`{{^R3`F;C^}=(0&f~IDFW!d$Y`Ey$XcFP2~v1FWzncz!i26U`)yuTemzl8uV5qU
z{`E{5r^<!C4EeI&gXP#=GVx%m_h<>dSlIo8;K6M#z<j^7ZT-{mf8V^Cf}qE2y7Am>
zv_6RIrx&DqXto6w>4N`VS|F79F5FE$#V`d!7VCRt+3JOjie0n;G1GkYNy?b6sSBC+
zqAl**k)e!FSe!8U{#V^Cj2eblkhBe((8U8<<3LmQH~Flcxf2nKf1(swt@Us4_?b|I
z!?OTIW@@9nwwg);FB-uW9{ACD9}H9>^S_mO-5{7daz@#CEDI%sE}1qdjdsp=-aURZ
ztVOhG7_p<uS`grAo?0M9jvmo9oG3bO{`}E2<)@=%)&rcnQX9f{EO*@M^X*9FGBSLS
z629MLw<2T{lLLB*fBc<i>d*qZ>|F^h?pGZMpVH0;Jqo=W*OEM-QWl`P^|K<Z+E%wY
zd)Nu+EUGWi>T)G!q+5dhN>}UHLA(5+YF!VZq_o1b?8VQ-W-pwujfYm;viBe$;1z=3
zyhxo`q(uG3*}_Mey>{(C`E~vF`wuZaeMNsT#|g{Silec4zJ#F_Mb0Z~+nE3hONrkg
zeWo5!-1j!<uC0j{^1zzYwsdDLp1B$wgczsXFdle!R#v<9?cz^oEs!{cs`6lZF6Pq+
zf<u;?xyr%7>;r8vT~=A`pL<K};X}HfZH4Jg?m`Rwpv^>YD$aqXqW90Avf%LyI-{H=
z5o>(qYlIQqHN1Y$WAMRK2P+Y|)5*h5m1RQ!(Zc2!#><h#65@Zr_ov3vXelkzqGloH
z?mdUq&R^%mecGGr`?Ik6uWm<f*eV~igl%J*qFXSFZ(HsGfD59X^3Pg2HTLMmN=wU9
zASTzNp?qs9b-Qf`yCH3_A8(7VfMd8;d{s9>9-7*M%K!u4(7~UKjbZU?*HM+@TFY)8
z2AG8nc6#CFP<IA=Z{^T3#Jn=-IW+c+rNQK&_iw3zI5-h~f}JR2P_Va)%G-Z{-2cgS
zp=tV&T?vDpJAJ87s{Og7>z8pjGFX1>X?~ZDR#~~Y6Qr}gB2ePJlda}*lBo&4$ERn?
z*MMo}9BsAF6}y*xdvsn$M02prqGK7XvS0MkJ7;aRhx785lvgPHfJ8wpdKe1K<X(Vn
zQ{Z`1mA3mkRWLtYkch?gR8GwBHy@*~ay&c2p*JzPzlikt^$}5Ji82PsDk~52<X3j9
z>`L*+gz~oKVL;RU2~Q-*^wDD-L)>2a1lXBGMd}N8^$LUeGia9bEZ8IUq6qw6ag9vL
z?ih2-Z<?99iHs<=Eczkh-_p&m2#?UMuC@WMwU7a$SII?b+N)Op$3?gQ$wL)G%o`6(
z%roDQS^Kt4H^yH1_U%Z(6-u;N^@Z@B7l_?>;QF9k?f_}Xdbf@(loZWm-Be+9Bo`9#
z;?k0{F`<)Ot){QQtXe?dX@OsFM;6YjK3r7B?bxTCFZ~(LcBgk#Ij6}QEgaXZ)QBEO
zz^nFW*l0g<-)MIR$W2dVOJ4+``VWr_*ll1IQ+ekd53SEL8f!Zjv95w83$YcgyCt49
zlx+~80D7UT)#;8hPsck%*UZPND&$L$%)+1t1ke~^-{}JNi+s71KU17){y)bdn33uY
z^NH>6x>uj;nSE*$1TSdn;-GyFy@N8$N~HE0g075hxJ98(`jq9j`#TA}^Q0==ZiWf&
zARRA209ZD{?q`(~L)aGuFv6B0rcbYKGDq`C!Na3H0!Yd~y(&GU#8DES61R<CvFB;@
z3~cDP_-=Ww#FF;wJ0rVH@Z(?&;$BdBWm|<6vFXFzJFj^d0+W`a%jZ*^o-Cdf%{_7V
zaf)_kg&EB##bo4`D(r7+5~6jxyz*RIc!vbMacOD$`i-8rCql)S+xB@BH<Ni%xend}
zu1HVh&~f45rDiN*o^eO&*Dhfgo#&Xx1-pe5pD4$*We?AZ^Go?_JRB1h9-DW%&w6r8
z5}K*qG!*24^yeRf)gZ#4PH|jjc?0l+lHBW%_!Hf^XX~1)b^O-e`PLq5kMD8i7dDYG
zE*|l1c4XHVvL{F?N4c3=I*t?bq~VrCxj_E}Lv1U6ue|*Y+qRNLn`zLm;^jM3cC(zK
zlXeC{zutluWcWP(D%oK9CJr~6J!l#}QhLx>Xz3-7)Cx!5hP_^XG`RV5eJ!LK2YppA
zK9z2w=4IlWqOcti^>EwI1*J(y?sWu>JeHi{d^4<(YB}KvqwKxnaiG;)$n#yoYk#eB
zYt66JJqYMO+prq)IyF`a`*drpZl3%At^Zo#AENsj{eGN7?}|Dk^0bmoOS&<mGiAT#
z8Y?@)u^}rwPx#eFMy9cO=(4u$Wl&Z5ws-5(#dH@Il7Gnwc3#h^^QAz%V!gO^g8gHU
zLT(-@o%XD2-K+rF<)!LYW>ECP@iRs4G@LDT`TgRBuVDx2jej^4je9&*`o#P1uzb`3
zCr^W|Tt!&n3i0e8j+UNilWzUN|Bq5Vm{apEmPdy$xwtcqyX#O1HOJ_GkT9L7N=r6$
zWXb)DaF5US;x|S{7AwE>+^_ZDT|^w+aS~3`cB8szIxxzf>!>yLgOPWPIfGgpet%j$
zMWB)z94uLV%{TT&wr_=QjKRSj37A9^x;nOlUJ~SiNCcMWDFbG7ytDDFPvknssiocE
zXTcgWRT^O2z%aZ#?Hg&-r`L$JFwsV&e2i)zvKt?uyZxR0=*^>=#m058d%taNc@VbS
z$oQ^sy#5XOJ*(VEu~mg|KmX!Z+PM4b#HJcr|LnF=b4^1xkP-;opmz(34o~F<V5W~#
zXv^jIPWW|=Zg>(~Y~FVz@+jZk{-zdz^m8P?9Klj?!9mcSi(n}#tU#484vU{vlvCUu
zTDK2xDWi7;#YU!c&|chlG?8mne&ts@P{1|rgiu&f+|xFN+?6?{TGHjMoRo}MpO2OR
zU`5!?<!~@4mmc=kpJqw;J2$=Zz!WxF7uFxU-eb$|1HL9Mj{N8EN8~wcqzKF>R+#(?
z^|>~9lq^iBr1re3^G82F`}@vyhw?(1lK$3gNU-<vGD<Kl>BSvEj`+JrG}~t`bH6+y
z$nlYdNuxc#cwidE+^WUvUaD|O4@?G9r>R@YZ$GJp%N2SA4^39f7xLSx3n||1+KIO(
z>;le}4MiLu&&Nn>rHGccZRk5(;Dqt4iVOa^1t));?ll*H6~S*)%#O_Zq{&U@MxCF%
zLCvMRjoW+am9phpgXe|tJKl?vQMzZJW(CAGMQbn|N6jr?{9fwgb*H(IU&ibTH?>(t
z{&yg1U{Q|G;Enig-TPOs8mBNCS##<6x)Zxv4ypv1%Y@kU)XjiKGxFt2?t6CxuT--z
znK8XN-Zq-`y|hlUB(=X{8|pYRDHkB`SNmjmC<7}q;#50jrhw$bHa^ZY@v6X4>Zakb
zmaZYb%{6lLBX=y9{{#jHIt|F6=Zxrt+zf+?V8njBRx|i;`IgT1<KxR|A8s;|u2mtQ
zkos_b_&5IB&hv5(jX^G2hWw1D8g;9JeN8QZo)2cvVl59)n(6n6p$p>tq&Hnu^6%d6
zb7NHLYiUW4pcALaI?tx2X9K^fc5J!#4}~jB8OFI+1<tue)l>c966vmH<#e**!k>Nk
zpG+}8_kN4&gf2=&2dOwvZo3aR?bQ((@$K#L1q7w)1ahpxCadk!uIHD({Xg%}vCvo;
zwm1iV5sdqKtbeb{)1tA@xMQo;NRO^x%XL$FYUW5pG&x{mgK|An!Fm3F7#<y^Ti`C}
zY5}6Qedy6kzt-_Lt5ssR*u@&TL=BFFJ{03utiSgDgbZ)(Q%5s;^j0lN5xN2$qd97T
zA|}^&|1wTY;tS`~>gUODuY*?2@Sv$Y{@*cOfi?0ZW~VhHftl>HG#-}~u@RZkANq#6
zzv78xS+9^?kBxpuHDl6|Ly|rzlgF0c5V+ZeIB_aJbw2l4yMWCJ>Qm`8ErKS}Zz(wZ
z>{1z@L<_As-L>af=VpC-p*Y_NK7a6Q$1pa}P{_WV_ggnxL=uV5J#_QUYLKT}50qsr
zV7EZAap9F?N%p>s5aE(AxrN`+?W)fb0eY)dy)?G(xB=&=5D0mH0OwxOVcYO(o;xOW
zzS`46T<A=?a6YpOu^&&bZ=ERH%ZVLe^NYZC&|hKpazi;voH!-k=_GV=W<H*SVH=cw
z_}ARu$U|qN7Yomw9;dG3n`%Qmr=ZFDHGH(6#ohE~+=J|^!%gH^y9bxv`EK+tq|rw~
z8p`rr{9pWw_dh4>0{Nm;8Ur8E-6n9_dW`_>h6HEVGkUP0+I@kZE}X^gue6@XUM94y
z6$B`0IQ*<o^52&>Wkn@rM1Vkdg|>XN!$&?%pD5iWD%IKpc#fNYnuwrB25ihBYUw><
zHB9?uf03*YKjmdPH2rLMblOd}o0+&WSSWsj+>JC@E(+v>&B=agAskO82h!?W_=ThJ
ze??rF0?MMbP{+?e>Ha}j6A#-$x|pN{>%4GX6&?f&JQCYK^wp-a?b*BP?*8k=mr{y~
zF!VddlK!}L(0}w&QgMa*2`<M#07$|Qa-^+8ER6EP)#?iP`h_;xF|K)WUTMd>XvYLv
zfe6?S;YbQ{djK{d8T?DPc_r8Gqx#m3GfSO(7^4f?S+TcVbyv&&?5EID9`TI98VBEV
z=ihZN2RPLPPwpMbXUL}XpJiZr14=>w?ql5DSaQbCO1zi)DXP9LAdh-8;q|#+z)6mB
zvln1nXD7D@2RjKC+GXpD(P5xD?dDS$94#JsYyA1y`~i!mYU+Mo6FErJMBY+zd2R7m
z%7(0m1yaek|E%iWwfci0b4_L3O>K&2<>it2nyC8Ym$*frmPuIBBTV|jl)oQCyqc+P
zK%#u?Z#v+9S{yNycviV!q}J3%mk@d|SjIi2SDr!Mm*>4t*|`cCcs}b4yl<`KB1*|7
zwJ4<vvDA1Wi}m9J3&kn(OHDvSKj#xGTOAtSf>}%TkYD}=b5xJDjOS#C?#nB=a%`O^
zmk6H1aN7RW%T0R)6YgYrNLJRYISqaAE#+ZDAxDCEMg=^0RR4Qo(YB`=t1APl=UHV>
zeM)2vb&(H4?oZ0J0wQ4yLY=x2daBb1u$Q^;*vq&u%jTL4b|!{awL2#xY_9~iU!y;T
zqa;7)Hs|AEgp?EM9S(HT^^Jg@)5uADL<BfrzFD=LKTBASqYgQuHL$xJ651$lQ*!*)
zAIUtGSSOkCBL+T|7~^G7X7BSn@g3&RzC5`nQ*|oB7L?(je^s(#T^&5!S%W}UjU#w9
z5u)#$E|Nc<4~#Q<=wG=ymT`)w5ekOrB^T5uZLIEo3kELN5kGJ0@go)WjzDCWDdSy=
zmG?5V)WU^(r*4x{V+hn1OX7E*f|Hi)ME5W{A~=*gUw8kL5EzI|-Jx^s;UT7RVoIWA
z5nZVArKLVleoRST%O3z@J(d$^mI~R=PEvQ#e)t!G&(Qi09Ijp%5YNpj+m#-B=i8AM
zx?=U91#<;C{QJ-6{L!Gl-N<1A_gOQ@W`mIjokO=2$DLO%*|&yv-24&B;rIARD3DFj
z<&&F9od}z9%x#22a<@VErJ=l9srYJE(P!gC))|SIr`$QO%{21lyqXq9>*su-*7n8w
zl#Gk6#5}Vqo$$F!4oNwI8Y%4R>c~IGkJ>K*r1Jt4S-_4j1V3TruJ4WR25YMc)Xyy@
zJ9m`sa~LaIJR7}pf=R5aYT{guQi~?8`IoUN3##e-wb0#96V%Skh6`f3ng*!Uk-&#3
zrsZ=veQO-RiB(lV@@V__@L=*I($s)}mnA|3lPF?&uA$~1+L!HQNRUsNAjL1PqXcJB
z+GVTpL0Mhx18*JWiByZ2Gvs)Pn3HBOq<Rt@RpAu9xH`VOp-HS5{dI|=tYm&H^htuA
z4pH6#X>w)66Vh{TB5@z#o9H=lQ#-VDPeJT(ivfl5rZfGD(ivWQA;S2F9K7lI0lG-~
za<jAYn|Byx>LF0ue1J`1yfT13i#jvUN?qe_0@9sVevkqE`-;aJLOV8S%4_buLMck5
zqSS}um#Y$ik*8lwhK0_qaAsP8(H`^v+Kd}kVsf)!@Qpnk2|U&h=`No&=Aolk!`mhL
z{Vc-`I$y-D0IuTzs<rg|^Dv$mOl)e5j#3YX5nL+ZY2E-T3tP*~Td+covFX(hU(P68
z%}VmCJHys#>m~QmjEi^?bMi8)!*u$;?SE5_F^XE6a<-{?$ycf#>7C$bcPGXyvtNd}
z-t$qtgTU2{Je$LKz4e#g`oh4l`#%4#&*D?cyYwIzVIS$f=s)!CNf%c*OY+Mj_!?7F
z!aW=qg4I#KEx~sC`L&JQscSjE0CDH)-uuhpNuc>RgMrIrpTUUz*QKoL;Dg6}Nkw4*
zE0@<*-ERwe96jn@rT;!Gr2F@cVu&=mGhq%v&nizZ(E;=q9<Mg~Qzc}F?#?1a%}-c=
zKJzy2vR!Yg)R&wKh$+nTRxCgGe#rdN`4)W4Ei5^?=B;cbxP$mCKcMo02<<#$H9;+W
zg}Kka<c9oAS@TiXI4hYu9VeE7gZbx86+Iki;9vW8;)_MgCmRr24I!rE$}fVD)A|Fe
zabFuj$A^AzR|J~QWc**_$0q{gTl&0di!RNpuQrHlju!~HHqhM(F}OT!k1^16GLg5~
zj<v#B3gCd_fliP;7M;Q+lux1lmV0n%1#&PmYYlnqU4<9m32G@f0vZ>$zSv6+r>tbt
zc>ll53J#5FfUR|I4VYlPf=4=&8|Gtisq`Feee4-yZ|cg?sn?I!KAvyzf3;g{5#C~*
zX>@Ktt?I*oOgP2?5-qWc-4|QgQ4b&bKU}>DJXBr$KR%@=PbtzuVJHe^OWDWvlv3Hs
zzAGxqGGxZSwa5q~WM77a?E5+xl_kWGeH&TF&e-?)pNqcV@9%$K&-CiK-Fxome9rr`
zp3gal-C=aIIn4j4dh_(hEKJ!p+FY)JrWx<)cZn@$rE_F;qG3e;EWN~%tdpHu=^Sv$
zS5&<9M%*s%1XzAjabQB@6hD4K;eku{M*$K7Zvyt;Js75a>_>dxnMi%o#`s}wR>`z%
zq~622KT-@{gOLo8ygYHGG^POI@i=IECG6YWVyB>^O2oqNf7eLwsH&QhfB~{4PT|Sg
z63A;x*H~LZ5b3C{WEbmM3`>1W{<FfM9rjvaXzih+8*Mpv^^g8x1|J84=>DTHc<Yhy
z+?%((yFUcy<mFtVsPqi~@Iz3Xq#3jcnf-ON{!Qt&|JTX|EI2pkI=zv5Db3w1<lvT_
zj-~cwhB*7rbB`F#wYayxHr9%2-BRtzTzc*pfqjM1=`-EzD`JsZbtydhdz_x(`5C*D
zBC;>7s9fvNQI~%-cU^ssRAoC=f;IbIW_m2rKW*^tPs;+mX=osMeAKqx1<nYnBVKK7
z$ZuRusoPRfycz|St&+1c$E8_mmCUVYUpCPr94gX@Tkxig*K=SQyC2r33rumTXH-kJ
z(Muiu?&9Pc02YMY4;Wx<v%7qM-~N(igWE6f?VMbd%FBCbfo?Bv?ZtUP-=)9kC>6(`
zs86nlr*G>)8oW)BIWpFK>;C<pzcY?f+1bm61VT6a?2nn8<<6FoOI9OPd>AghU4S-U
z<NIh%i*GOhl1k(y@A!;ht~Hb|!Df}5@HFlY=vy38?kP;|QF6zwnj5$Xuy@$2oa=2d
zOz7%u{FEQNqC3?yRYI99u0ce@wOVOmJd}CFWthhZF$}Umuscr+e#r?!Yf4)XCvj%l
z=jbNh7i&%p+RTf<lj2FPk4kNvlt6uRWyrmr-X51fB`XPxGsZ$$*zlCQC9bHG%lCLw
zEY&PJpV9T6{ne%SYNUn4(P`fVD9}tGuW5c28tW%TK6MLGhexZ_Np$boz<S6Nq$BU1
zgSKNVi4g#aWp@sSjol+*&pBR1bNfd;MW*kx$oydn%1L4{GJXPWEI<@&gR3o1d(X}p
z)$Q8KqMW^Doi50cZ{=F2mYS^xO$)^8^|aU5RU2^igCmLLET4yy93LdUZ2Wy^&=D*n
z8S8vyZIRXj5!R!nzkFh(13yOJ#z?=4D$n0|2CZw@Cu-kYIvauia0OHcr&fNj4*(Mt
zGoo59L_)EP4QjPcM|(<!uR*15;T`F9f2G~@ZKKiK93d|pcjge0;eaJCPA-F(-(~H-
zivGhcoliT@td(3{lnT<*HSuLiD-V>Eg^FuGHI&UCp+kgg&#&VDhbxnNc-bT1&x<o~
zcG*hR`M0ZOYZ|Weo>qMqXqv41!a`HLaSV=fdJXjs^$Y0@d0r%?Cukg~9Y%M6Re$3_
z!)JYtH|2dH8fqn_hu11A+J#!F_723guD+G3cbuu`C5^<IehqQ9e23ps%ZM<JY)7cQ
z{5{!*Kc2UPYF5{9RKS<f(v9KEj#3BP&phHLzaw1a&hqR6u7r0fwf5?M$Y1q;DE;Vp
zyRNpv&Y$_r(;mq#X(m}GJ?{n?&94nUfyR##K<>As@*zvk7f^uR8A|>Xi5&)Y`g%L#
zL$cN{Sonj*i_Amo%Lo&b&y6n(#pNe?Fl4-DrypPb(|KQiP&46vYXMmEljfVO^(a{D
z`eQzep5rq+=TBG+MoqX+#&4>>rMj$9Bk0q_zre5l^S2h@f;uSPlySe(+h*`NW;U3)
z*>0+*tQYm}?EoW4y+OOF$6()_h7ta3K#AR5+l4nHKMIr8o<3T9vi1aCY3tT9##4~B
zaXznawYpPH&Z_yz+*_}_2COTxW@#;4d!qLlikl-tnx%y&JL7k_4H{{5=@h8O%3?8c
zaA^l6uwZ@+D!iUHR+)-yx;kqCmeIU>>-6lMYdKGP3~h5wH;J)hl|D|bmM<D(8BY;z
z6Q<ucq%@Eb`RjKg^Vy7Li}@!xfWPF(Z;sl!Cn(32CMVOHvXY&otau?GtP|HE>15KW
zC3mB9K$Qy|1d1tZt1s1j@;%jd_)iyU8Vq5dUB`YYY}*+iN0gAPJ%d1aAenOicLiiB
zS@%pO$%z(P)8gM|I{=*apxqft23~eIw0EE-<ori_ydKS=$)zr>=_YgG&aHd0uINJ2
z#tPFjBTeeHV|tsLE23agcIqTAcIh|vlZ|mlLamtMx!mjidM6W(om8|74pU`Eesn34
zu-Omw*<)bWkCSvYkHWD2AX5h1Uo3Ectr>nfd0#eXZb6nu4R2V$MMb|%hn1!%5ello
z;%aH%;f?FN+X@8PW!&spqLHa~g`-P_KHllqhS816N2$$S%73+rz@Ao_FQ<bxYB`a+
zG(c-3xiosn;KwM-oPy8W%F*h>E-!qOh{i@qe8dDNSte-F{YpnO$5U;l+~tbE&MA;z
zYkR~-25Wgbbv$}fHESb@HznFLj*_X(0os<~es^`_FS^8bx$pju(%Ac^-|2&x)}YEk
z`_K-k#oQbVSSfpX|JO~kAipGj)5$hurU-l_=i28(J6$IWrN%5sbL=yYmYb-?or+|$
z$NtYnol@3bGtTXTtyQK5Jc=j5WE&JOmK=jpGefbCPe7Nvp8RmI2prpd&vGj;V(Sm*
zQjQAQNBi?^MeOo_Nwtyuga^0wHZhRf(2RZVVsZIZZl;9jRCn`Sny$PYSQDZeahtOJ
z7!)eC6R25@U`56cD_~qN49y{T@SVKTsP?6Y>c3|pY((#2BLf^81M_m%b!GEDrP+%*
zA`rpYDL_pz2Bm*lFeCDrRnOh52Sf4sb3gB&11t1H&{EHjBJCN(KIW}t7o)G$EnDd<
zs?$pSgYul-vp|kuMil|2I>ezB1489Xf+s+)e)7o0+_P;_DOmM*@-=$<5B{;TW4%ZC
z$@Bd2w1<DMglkTaaj9*OG@Q3Wgg`<Oa@*5BNRFJ+zm0w<x1s1!%T>CvYg~xdC_yEr
z=~f97%r{zk>-E??LRG3oTh_t090#mC>1hp&&Ui0yO{(G(uBGQo=>^FZJ>#>8z8X)o
z`FGNUq>*_i-?>lY-+4lbA@p-UW`OUz3EbnfT$#k$)eNx7Ku332>ztEzD(Z>a-AHZL
zb_O})loy5H-ptiy_Tuf!Rt|N_IPwXhaXjipE=PIex3uPq2tSM9Xil||FRoA$q?pod
z!VT62|0;r96J$4wYbvSeisd^#_?)Y=a2(v9ue}@jPQak^zb@7}%iy!u7Foct5k~eN
z%Hrio>Ot3e%+Km)v_nObO*oH<KBc~}-ZG!#Q$62qxo(kexf*C&8|jU4KQzICO3Fal
zN9pfhejsy|f^`k2uW~52FYtEC`RFWL+4Zll_6^52N%J0h><=olkHOg3GtYz3I8R9E
z9p$yWd7G<>M;|3y^3bxcDC3QGo-pHo2)zP#m4nR%z^cv<MQZ-P^1f`Q#ZRTbk$OQ&
z7*u;^C0dvN_RdPtug3`$GWpqmJW6ajoHcH5&a+Nw8cfDgI=vVEY`&ZPHv%Svju$V|
zNMBBW>XxV;n;nU@%h7^X+Oay5h0eevr1!1hgCFNwpPlTY8h(uBXeqGnaqviK2~5-z
z;TTw0CH09q-TMCU)N}yS|EBW2nyc~I(s*T@hihm9XN>X?)0Im~04}b6?|kBxTW)^r
z>npAFd?J$=Bj7$(A(|$b;^ZL#T!xC0#F8@?KbqvTl;1QOS_$(9wFO_goCnBib%<ya
zF<>nEF_5u{r-8C&Sx@@jdOvD3Wy_5|qSY<hV#!BSwo&#{K(ewRe(OJqmI95w#Lal`
zn|kh6(qgj@=A*X{IYw#C$Np$XtUi=q<NE&@{LBN+D_#O^|G9d*;<s7qg@6KwHO6f7
zfO!`)l3GHSJ~44<uF>`oqD4qbG!1N^p#JPa?9ZxiEPdxAXP<|SWirkoCgj(Wc8#DA
zAQGEPILNjYFYW^k6%T+`CH(#aNig-C*{3(!yL1zvvTScHkd$cDnl+7aYxmu6zni#q
zXwMyUC7%ldYN&lLu$;#@iaADrxfvU1=Moc8O$X>CvKThH@>@DKKI(AoE2<rEmhGmE
zqxLlYaF}N3;*=|}DZAo5vz_(L4Xkr>--T<Xr7t)4R>@zw{QDQu@g^i1ZADRt2+SYx
z9tA_10I&e-VCbWr$=P7&%Q3)#2Uod3{PtOu2F@_qm7;4#&Z>IGMYK*v8K06)_FH{B
zF~2Mgstr%X>HK3dIk3vyQ<SJ0V-bwXhGL)Rd$ErrDF8@1EYY@_d+CROgw5C6?);XS
zecC~s^!6qv`c`a|!d{&r4WufDPc+VFwYJ|!#nL2dG1;};JL%tZRnghJL#9)1EhSFi
zAlcRP=$t#uHkwK##roWLAgv@&wS?O8v-R&rUkMQJ;reL%uV1(qBmMJw@ALd@Z_ZSC
z-L|=Rk>NGnD7S6MskevnkNg|n-;xWr>gCV#4-jZ``Vst$OUYY=#XA39)CIKV^OrA^
z*OI3C<y<1?rsg8&CevKfr`=?UH`N?<Vx`Ckf%A@CYuhB9*Yu;_;4B!JKFRQEbm8yK
zsf=Ei<I5@o-s?J43-j_>)?y>dtJRM>TLZRvPtF}@G;y|MJvZ_8_;Pt9uMA_zn7Ml0
z*N$i@Sk>JWdD_MA;Fw96b?T|yEO=G^_lBE;jdL`lIl;A)71g7=p@KuZQ_=VlW)L0Q
zly>%s*k0*<@kSD9Q(DC5fJEZ1tm9l;Tacs^#iZqp@CReB>oj~|-4ol-kM5JmVxDE&
zq}TP!)G}6neu}@E!E<_b{k8Zkrg?QTFn-detc)+Kx95VnAg_>k6oS5>tBE1ZmKdHP
zb?!$U^#<Bs-!noACXZN{zVMM5oF4?Uu+%GxlU!!%s3xe-79)qcdT#ue$7|^3w)&@8
zR5_loT$VMllbSvZAN(xs<Knb4I~P5OnX^jlpvmJOF1gZg|7^LM{P~8REZX0jn{${Z
z^){@4hVc22bFL&f_ZSurcGJvArp)syZ093M?DIR5=_8@yWklwwu`N=Gd(yx;izklk
z7C2T8)fliqG`BEQ;d`wZs$eV(NwrOtey9pR91jl5d0oEHd=>_)UTkYmcb*#-&Oh0)
zjd3WND75FGo9>N}84}rH$*x#%?PLs(lP;&EWvzR94yUbC=KC*1mx;JPR4bmF|Ik&@
zTd~AiuZ2L2yib?XsQVhtgTp<5zvfQ!4>z3|C4)QAAj;#xCUMR~#TJ12gyZ2QhlX59
zIRd*A=Giv*9gl?2@})jU1)Y>=4Y3ahlTKq0V`|5f8y0c{?}TM~OowqxoMT)|qCeCk
zcy>bG7#!LNi=WNZ9TZ%vmhveVQjH<XTo;ctwl_?~XB<^c7m5)yX+n7@KAHSo(KR#Y
z4_0lj)e!qD_=>F5Xa3_FaL{nv?slBH2Y;(omfvK<s~%5oYzYc8sNC5}T9j83-Gs45
z9)|y<I|F74`GcP6J+-|0m@eN_+kLlV1#j8>pVGB<<<IVYT~@vfyZs#$ba5e(ozOBx
z^5|M!kJ8zsmInN34lmMqZF6jGJAxOEtzW#EYSuob0*A%NLTtCl9&7+=R9%~QL?`C6
z@f~MErw3tGf4Wrev5GkJ({#M?6OT6@=NuK<<M<4A3*o{V@$)?-#`)c$3W^_c@C>5J
zY5Je2)Q6b8v5*<icC&b9;Ch_0INfKSTcu&nXZHj(dF^sR3R8?M)ihPwRs#L6m&0(e
z#6=;nqZO>ci@&qNK}z6?-}mjN!|+GG$nAzE$~PRIyOKih_xQhS#RKhd>LhO7_YHl;
zGxxE~=+B7(q)3nN%g#1WJ5tX}?o!%?U#=w6!&+>5C+g06DJ{+en^T$-=K@^O*{HhX
zmTXsWa@)u6wsb9i*pTV5%+}D|UjJRczTrh@oWESIB&2H}_tTWziE*U<Bz5C|WOID%
zWu5P4qi!M`ld<29&spS;^)blFMM@o3x#2RL|0q%dCsljv3?t=r`z2U!z~J5#?$l$A
zlrh(YP&cYk-w57>Ab>s*_JnFLmd0dQx$^^zq$JdBu*ofOUmP?Mz7?H^7J9>(r|`?$
zA3_Gg-I`c3N>EF`&ZJ+!n4pv$Hh$@8y{69`PZ=!ZtK997Nj1xn*D=3jLny5{zWn3(
zvf)<<(d|2bhZ26Z<#mzcnvrAo3h)jsN*<u4&`09$Dk@gvJuHyr+wbSvA4Q<+UaRCf
zYiyNkE!|2zJ@!QW;n=r5RBNf%=}u@W^oL6wkw>WSS-zv_(o0ig#UdsP6F1Ddl|Ws5
zR~Fce3|*?zj{T9n%eLeilZ_sB^R_WBomUidwJrQC@1tE%m~x6h5n8S7z)NW;UgE5r
zY;H>BYVY_#?50W!>Dz9su7x+y2y{%)6wrb5Kwz+TB__)$A05~AV0G7%|J*oP@P}}l
z$@{CaD+8;3hbSH~(luBrUR2OJx^!2QSD~DO72|6ORQ`gMKcoDKzV7Kp<lnK+0;0&i
zK6@VKbrP9$x`JKHMf=`5*AmOBHd4RAyJr1a-8Qr8vcY#|{T^#^be-qMH<{KUqc=}&
z2+uV7GLI~@v~jmA#s8B+B<NmaV1sm$5#XrwLb@;v#;P86j<a!F0{`f#$BI|j+WS87
zI>OGJQL5RfHeO)RWBk^YI63PrtV6g~is|Tj-Cr$(&;VNIj}fRh>eV;$_+!18x1b~_
zF8+uRb{^eOp0jQ|_i3q(s@?2Uv`{gaBS2a`*{5FjGYLP}A1rmt$h~LTS<pXj-Aa?Y
zIR%^BqM+b*5rR-M1fh#-dHj~C?lp8lcm6ZL+db85L(0QC$vgyCo${g8)u{J2Xh?3l
zX05Zw`Z#1i%M;)JKR5)9ELQCqvFua1Gb*sgj<Uk7R3VqS(=xVVau}npl1?^qt2G?t
zB5}g#wPpLdj3=p^z5Y67sLkKeXPM^Ajq}OdZ>}yYc~Z|#<}jkpa_%-V%=z}&OsT@J
zh?ATYw+3<mPtT-swLA``sQbs3$pOPukxBzAK>PzLl)!e8u&MM@9t}^gj!9ba8i<`6
zmZ6#=4e==z$)626#0z^CXUXr=?X0SH$+I@=-F2Le*HX>+QP()<l)%^w?2Qc)lJnf;
zV-x(^I-8wr>OWudG?TG>{8E(;>Uh%5BFp<u^K62|+V{HfSkr8Hfyp|H(#&mxl9%S@
z<>XjbGs{5yXO_v%9V5HOLNJ)^9b92ZqBq2+znXXUUh0w2*Mn~k!S1~*G<aIvYdiyU
zURY!;8!?*iW{o9XwT{5|T5U>m4mXA&k*;TwehBM%a3Az^^fd?FYiVF<U?2JTv=_pA
z2g`GQ1vVAB1~6x3^qaIjbek2;8Vz3BN+WtyTy`8fU7A-DC=_waq=aGfL%0LY5vzM9
z)U>#DN8~`L)ZM<#WJI4Wb;(>gz8L?1RVnlZXK<t>EWYNc-Lt0a0%k=IP4YhB55vVW
z<~??b)_3tmDcDvAo02q8(tq1=>O2}<X6T!urkaHPkLKC`qe4G2A4gqe*fyYr$%B=f
z<AMg;ozkAE+0&uqU~;C+s(KA-Hg3kgu30TmD3%R}D9X9@-pYGtNNB6Vc1zI80@9d8
zV+E)OgDAx<fkALujldvj?yj1f*tIjj_Uc-2a>{-LD#n;M)Ju8+8ork6bjW)-?+{j2
z-nXi$OT^XcZ_(mO*xz8kjrZ?}GGcL3hfj9CX)N|E(PZaMp+EGI`2n=yqs8s?EIVfQ
z?t;bQajEcbgNoHi7oHdnRbt-HFjfv?-kq&@6EXi?HnH-!xm(+th_za@D?&rDXCZ5#
zt;a!}OIg*NlEkADU!33IbhTD>04H@flhl3)wx|I7#Q#Jgw?^zef8*56|H^9xnj!U+
z)S-e9Hwx?6cKj*0ThHlt>l@2l3;pWc1ZHqM*FD$FuUM^X1aFKN?VZKd_{7Ee=iaAo
z^)<f_bmz~@2nOaNg>$$Pn2W_~H7|Mgf_62qA7>7GW9US<8!KUTL#v!juoA)vcnBKY
z2s6rO*yv{;Ngo{F9yT6tEPq}<_$pJJ;jDIX_2#cZ%Sf~1g>?d+akqSm_2Z5D%LsfP
z8*tap>G@48f4C=s!zkx5ThuN*HMiu$57_@6+aE1;D|0Qhfrd1A#DbI1ame{G*u>te
zmbW_Cw2(0`<CI=<)eBL&HCdcH%;KgeHB^R@kL(MTs(rs)ix8`;jGbLuT^i(V>FcfT
zsWZ!SyZjg6DqA~8XmUOwM1Yg&s+W=3Xkxf6XzfA9Wy7}xf2o9Z0bhtC=lisFdHb8m
z)kf;cFg9VFSv_Wbu`8NdW^4CAHY{3|$aJEsOLfPD(*&QXb)uR|K^u(FQo(*Y!eTMS
zyKh&cW#wcg;5<a9=+xMg@SS^8{}!_IhtkH~gCD+#EK{e2Ssb>%2!mPOTdJ|SS=(P)
z!0*R<mg(G*_lD~~;~$);vDzcv>Q~r3ZEn!ZiJwbKnA$#htWS)2_?);yoi+Hqo-X5$
zR#Do>o$tQDL)0Fw^r=->>^WuZ;O^+wp#;GA$T6ANXP_PXVaSX_4W6itoB}IfzCa4}
zG?=&=y?g07cd8{%LU{B;BBz1o=5z1wzn*T~&}c8L%hDEe9pg9HdFQ76wY2lb5P56n
z`;10Db3~&gRVD)GMsRBGohSY(eQq4t6z4QP?hUY#v)-5c*l)QPsg;m#AL{vIyY#w#
zfE;z(VtaDXznU(oQ4ML+XNW=WY#EFQWcRTM5fbpnjt%`j?v0_Y@8HcA46l4p<k6^m
z;XJtXJ~Nd|q?*hTeGmTnD2ogw@~f)xJ-Ar{1+)Hm>eN9eAS)p7#O8PBwL#YQ?^Lfw
ze#XIy)Rc`#eciA-Zo>(=CG!cn>%$>ugoO(?O`7i3=C6kk1FCUuHkT_m$7Cos2l0GR
zn4|lpFg5)YVUx>sgw}IbIY#1UtdweF6#h{1z=;5@ks+?*%MN0wFaO8wzZeLeI}ZXW
z-p0I+!TV7)QL7tqu7Y?8QpFzy(XI4sunn!wuh8E>0`4bA?R4tA*cDOAdZa5nUGr=y
ze~iG~*ngz8Fm)%4uTtI9-a>kJQV55oZh6M~0nJgFyjb2jC@aHAT{cP?@!TGJsI1e^
zp`wp3cC1G3c9XhGJNnZ2Hn7<PEC#N<^QyUEc|f9Rz>gxW3kX)T6!v?6M|zA$CVqBh
zg}LI#VVJyMgK4RhL}T7YUc`8W-XV{%`Hc@(Hs4@>9&xGup~yYrGicB4u}BCXo($1I
zBj!g@Oay9f!n!y?=L1j(g#Yw~N|X6KRuot7I+|~VR<A6`AiKk)Zr$!*YtfzhSEOan
z8#D6o3*weK$B0t~5YL8Uj1ooQ*led+d**xNI+dM;iYwi;m+Z7J8A#h18(22WRQB6$
zY!_?>GYi<?{&rkX2>YFAL~ux4?)^blB<qy_mvE|apgiY0+R|#O0r`5j-8U7G<S6E`
zEZ!`F@|+Nom1LCLMVOm8{mORwvZ5u_ca}P|<p`|CtKD5b*WOonZ~Gq|>%$tr$eG_(
zG_V1F98f2aA2;d?ViUh1pgUn+0cOvSZF_sWHL1_(IZ%i*mtDHXw*`iFw<jmpH%RuB
z9l|TAInQ#*F?Gts)9umu@Xu+td2+=)SHhgg#j}9nN#%tqDa0)f_9dh$YqZ3clX6(#
z7wn^SaWu?J8gizDgCVE!i*0I6R(?(5M7W2?x2~Q=t}#0Lm_Al_Z=Z12jj8wLT*Jd@
zlS?#Xq71*tF^Kq_GWV8n{PS7Ot)y4zaf@SXZDc;Mia{4!yh~;t0pc#W;r`;CB38MU
zx?TOyUg&t^`Vew}ad1`CK)uf57!<Q1*FQ9+nu%1qn-saZA}qg6F3~EDz2;H(f&I*1
zHBh5{?0lQi&IpJU%<6=FjpdWlv0q)N&pm<Z(oHWJaFGF(PMTrQrioGFJu_>$IRzl{
zd6`0FF6ZUU>#41LsL_v{dPzODOqbZPZh~XO%I*HTr>vYb;J3{nD|^<&)j-XyCUchR
zo>I88HQxuPNqXS65m{?(lEYX&wqlT&c(SfgHJp#~GsulvY;CTGz6Pw0^j{rq#JYQr
zCWjx29<7}8isD7GW9f-uGpCHVhHHo>uS9lEs|k`EwoO~5sZnFA*RvxRvLvZ)dAG!<
zj)phJWIYFf;DyInp4*BSl34q-aa^eq*EsK8`Tf2*8eNPGLWo7yKx}g(3zeUr-$@@D
z9dlMtC}g4Zaa4YkI;!Akeu=aLRKmFBA|k!LLl5J*-Mb1rtPloq&(M=m=F8RQpQU=#
zsRlRL895-l&qH|E?PCD;DRO`YZ<k`CyB;NiOfIcxA@A}#J#Q78&|_+?08%d)m-e)E
zttV(b%jCTO;Fe#)d3MW86)z6i8y5oQ5TQ~>tD7_7lxVpkp;ap)xi51NMIP_QC(2Og
z)?`E=$3o=))kgEZODQZ~Nq04%5N(Cm(52Fi^h<hWhMayr(x9Bd1pw#`Ief-k7XQn=
zsdA){9J?hUzFbj4HF+{mvHCV5dWO72HdtiV8``|->07fEPy9!JIXHCfmdUz%hCnOx
z)YM#-O5qc&d`zIb9e*WRuHyXsZp#Mm$wF<r$`%gymlEhB7z~CrYs%kbtF<CG6=5PS
zg+9yaF=62F1>1TGtXUmy$p<2+6PlYZ>@fBEAolT+X?eZ9fCaPCIWG%c6NLKBJ)YBU
zCMk6~t}Kfnp5Jy`ZKbRa1R7$vgp^aTdDn28cuGXp)7Fm2Y;YK?vg$Ltr;nwuF;O3~
zns3eYwKBRopsGpm*j!gvMbtV|R-aCP*;Nn9mSY`pC9bh4ZxHFy6y`LEp4|{z;vq<f
zL5y^pF$;PY+Ahp=ptZoc!yh?3M!+!uI>&`IW(D~@xR}(wnz&gdpN^xJJ&cIt7vi^W
zdl_i7xjnOy|Gnmvcd75fKV7<W%S&4^%whQDH}@AK2^wNsx(U}^OG{s@+<G!uz5Ds<
z@;`$iJy*9Pv+4YHJ<^3*%~6ilGsl*Jzl9mx`1w%U#mY>@Kvne_Wx0ORsY6L@b&c?-
za(Pstf6KeoX=+rHjUxs-b=>dR%s?w6a(60|GHa55#n>)!e$2&f$+D>0H$QYe*45yp
z$=Lge2@KFm#pGpYg=$be{Ljh0o|aZ9E8~8Um2pl2E`aIfJzp`dGzky(&McjlME;6%
z+zsjp^o|-~v3D07TfDMabDNp!IN4hu%+rE%^0?-)#>G7R`p21cw>wPU8K;A^K7UkE
zyp)^>{(O3qgS`986CR4Ox^~>YPRP+p6Z~USW*-M*qqTu8rPNQY$!)Q&LWYtSUB)C6
z)-?E0m|8!aw8P9MLWryCf4@qHO&zGc*qHYZ)$yUdl>?<aH0zxAEtG@9U2`2B6x!jA
zxsD^s0e#2Z9Q+?TbKP0d+#LKx(VYBi#3-NG<Y~OL@<TC=LXeYT50o<r$Y?po2oE|Z
zWfpnz6es6r5zPR(&34=E)|B@n&$=Az*2<q)mXD$P!U&PxjhnB<tph{MlSksV`tV*m
z*z6t_aif7aq_CWe)eWr8$507fyl;LWh}!Q>oiB6&V)pp1>n;j7kdQapuWvI|zUs@L
z$NMy&YsC8;cMTb9a=pojmp`I5PR?oE%W5|=>Xu8rFSBwHb6%v~B7Zd8l;D)$7oHvY
zCL3;!tN6LS!mK(Z6m=`G$5J5XR$z%CIKTOZU&<D~ENjL(jK9(J<*OUq+_k2!OgWRe
zc@otlv6HE(8-Z>1CTePR%gZ%^ZK5VZn<WeALUME*HX*29LiRd)5?#onpUETduhgts
zQDh8kh;A}EPQ_tAZ~+oAQVM=$N#oOzrz>ve-Re@#HICSkmf|{Y1TkzzSEqb_H*0+<
zbHHvI9i3>dVGbBCBruD>f5y9NSoM}miXlm-W%516kUcCiqJb-5SF(xetgN{rg5(5s
zlQdvAWp$-;ee@+#wMVxMK}Y#9*jw2~_9Tsq%Z(b*sp8~7rb0Rhl;YonRAvlF=)t_$
z3_PmJjeRs2_&!Yp-O)7X!RBX3QJo8;?ubTjglL(wdlsxeJQ3p|%w1P!W@<W499{2z
zLuB?~i>9h|>h=Gv1#o-y%9QfdHN^V9!!vc>r=by%>x6Cf9St)^HPMOUNh}r{nde?)
zXrfywbZvw=Y(caxTeH^@jeP0*sxqHzID9adheV0HX)Rg5Z3KMOuGv{-c;cnIwKunL
z#kqTlYT3AhkgMb#2)SxfAqV0jnDRw$MG;lPnFX7jgnGE#ZSwHfmvSE>C~#4rPNO&k
zajYV^*cmJ@KfAF>M5fr{8~2uc%-3InrLj!{M5Ct9EcROj9rMaKp{o3^cbW8>%<R3_
zKfjS~{9N|?c`M)flI*eMp7>{4=^f`;;l8=8n?mPxcv02k0);hO<5!Zl!!r9!`>;m2
z?&Rj~N;4g+!OELO^Zn=g9Dcb~p!<q=&q{TMKHCbzt_OJL3VAGasn+$-S#F6Zg|48O
zhkYuaxlWxwxfE`~5<sa(iHo)BCi2Lh>8PgznG2D9^XBEZH&&{9W2IZt?o9Knr~lQc
zXpKV?*l^`>ay%B(bA^;HddIQ)*Am^@$2h(pWOkEf^KZhi#`?U?PfOmn6s-nxxr*ky
z0abHRS9{DGS7s5+Zk0Lj26Op}Yz7%)W0`sKv-|ok5Ox!{hGPlnWa|e#Ads@Q>u6q$
zkqyKY4dP|z-(w5<Pa-)4Lung8KHoM7^5SlS^bAa%i$9Vc2k$Y?y$j;#wy{Q=kFo}u
zM9-Mm6F8w#^Kda7U#Z!XT)3YS(ktLvW128($nAuY1c%)#>+FFt>#gm}TZXN>$<}=%
zyCDO@1EpMPaKz`{Qm$*Uedcn_Zn5XeSeL?66EkJJ*U5wZ0MI@-+y@>tWsr<`t6AGz
z+nq{#Fx3L{16iJOTV@`xjL<6UUsag_BTVVxt>2R4A7&!KLU<b-U$xn{k=#EeSCS;b
zBdDhmcNO1{ELRP~#~h5t(RzwR<w%lUu4cA_P2hvBxQMx4*3c~Xe2%rdNtS9)y~ha^
zTkgnyc6@O*^2L_61CcyU$b@B@{oibpY$TAcJvuB>0|G#r{8iqwhPe$QGslIa6^D9n
zCrB|Gb@=KI+;Z{$ikkiKpo{d+*k&B~Yx;(p<G_d2SOdf`&ZDiUEGGS2fXZ_Ug#cHA
zzdgz#)%&Wkn2@c>ZjpMIW6xTOWgmuJ^u4pxFM4O~_b|d>m+zz`OzCN>q!G4x@|D$x
z#Bd3lC#{vpM?<ny=e5eOs5xwg?WB9tAjtD~S0=fq5al+;a?i&u5K3oX4$q7T>&XTm
zh?wpJNW`2#*b1|9TU|c-ctp>jRaOS^O*Y?ZyC&GZFDrf6pmMnAt7egcIXTI1HDD@^
z7)`J+7m#q@eVi)2pa48u{ylRi1(`dTS0_5xB2f4FgEfU}wQ`xy4<|52uB)|i?mBg%
zTS$y$HbFS6Vy?Diyo`0EcN*!Ro>gjdn`s7kW#<CfK~(ehXnmT7u-nWCNV;wQ0HUvJ
zd<nSt&r7$m5Xs*IZbRQV+1A?1sAJ;lZfHMn(r$J|yrwX}X49~~65Y4j&KSP3R6z!z
z`iv(j>u%gu`uXh{;unx4byAoS3Z-pMp+8)u{^9aPwYUIGcruuY1(~L-w2qf2Ds4HB
znn*APdTe~V0v2bLS~}>vzbLI-OSAl(n7HAZ!4Q+KK>g9M1R~W@Qaj_zfkbIq3nP#e
zQ^URkRto5-$OJmF*~Iq^iN(=`D?~IJUDvUdjT7i%R?9KTr@o))DNni-DZ4%y^i`Af
z)k}T(XERp*aV{4R-0_?nz%$|@g4qgiRV^l`qzrqXA=c9Ign81Lcg49cotd`3vbD=<
zgN?Rveqq&9Hv1t<@<v>Z%vxXukC=eXM7JVWURc@f;in32H_-pWw4p@qXep#ULDkC*
zGBGw_iQHVP;qyT$4nGyOLkTu8VHY0&Cq@Mpm-A<N)(f-_R7?hw%gMVz=PwXh&P6g^
zcUu-xSNytCsqP$~#NrNPf&#6@TM$}6ets~LnRfV>9}Q)UR!*F%tEi}G=s42k_h2R3
z#$C_Qbs(S>3{&XTuf^GdY~Oqz)Bnv5*}j0-b`<ia!8DsB;C_tToG$cp8@kD?^NZBp
zc1E1E{d=O{+0tLe)5vPFRFd1(#uvyChW87d^1w+ra1{P6tb7Q}93+O}dwo^jC+v%;
zq%fl*&PAG&J<y$w9TM^SID_ZZeraIsmKs)dcrr6?T=-EZ7xdT8NJE?_gM1N0jwo95
zz1h-)S+4VP?wvq2N0W0QGU9dZpI_}<2|6cOL6CY80A=2Jg!Vz@b{+6qPz{LDeWjgh
zsQgBLdOAw#jFE;p=X;JQPkugB&FFY|?Rr?Bsc9phnQ5c7aEH6K?%_)G33!D#`knsT
zrv@4_nCJbo2n;}+{{aAMb$%u%n$OfvT)>yaqLb`(l&wmw|4ZHd@YTUeCE^C*nwh!T
zay!kzB#&1IID5t!9F_?6;F1&{*=%~@Z7zEKTaV&#;hv@7f08z>g?sEZ6i{FMBk69}
z$+84#fvoGqU#!%*+>p=eckhCSE*OAl0R}s!i75Idv>_{=YCPE=Dy7{gNnv)}_s{4+
z;Wqnv56D>R!p}^|lcd=gJ%s=hz_pl?D8*!Om)%!@EAW?`SVx5%_j8{1y5fGOkZ1-4
z?S;;r&?pJluN@6b|27uWSn=-aoc|du<h>_8UQDerqNfHlXmWSHr*Ls{@}cUg$HSY>
zP8pcM%?t=P(qa+6-}lSE$ATo|JAD&gkmmzIp;rflNeyL40AVm~^`FV6OWi}=(hd?1
zp}W$Y$Axpp#)OMz(@m}VbZXYabna+RsKWEFJPWNqFT3k|5GGaiLbILD`x*?UTfy&A
z8}}hDH^p=<QVyGu$WvQHVmIqEK4aEbc@5wYi@7!RQQ!%PPZOn_FM+A=TCU-@z*Odl
z0azpB)b?q~(gYU3z=z{Q<`0HD3JOV<#BJ2(L=htKccGBochq|<3Cg{?f=T|R|9Mw6
zWl#EHE59Y(1&eUh>28nRY%WgIJo30-V+FE8CJk<In#T&;(A{%hW<~z5uRIHYLpqVP
z|879ui{YMb5sKB!wShBw34Gi|{bGpN-KdD}#YN1-J$UY=_gHrk&h%uU6G6W9DNx`U
zu>p^~`XLp|&1tGJ#RjpmMY*HdTDWMXIr5hKmQEdNO*ECOqsf<0g5YjcgysZ|k`}9g
zwmMYR8wnK61d?mG5cC6F@;A|%cTM|R$Y$UNhzF=QeOfmS{mfprp?%woN`X4i&y)_#
zaYIzShm6OBA2=Zmyn2!Rm-F*}p63B(su!?bbw8WC>e`c8H53g(61X_-!xK800oQmS
zk!b(}C+)(&XL?{3SE6eJYe|&E+_hy_Gr+U+JsX?ndnlU`Go_N~0;Ps)A;NCkXa0%|
zA5^X}F}bfG<F%}#oW#UpJ;YXHb_az!?Ax}VZayUnFh05mM+UW?!39i>dV?sIB@n{^
zbvhJ+9qPvZhr9nR<B1EDIm3aGF_%515uFtn)N{k#bV(`kT*Gog;#xBH;dGq3^B*_B
zYePw(Y!uD+m5o<Gvg@MejBFn>p14|rS}PRJTUrq=A6WsgJs0#@Iom%rpjCrGWTz~=
z6%;4HroklfqJ_l4SAUizA2sXhkqa;~r-~%wv#~?5NdJU^!P9^OOa1o=W*h-O(^T-J
zYcc*9HHhfVFD54cTzrk6FEiuiEJ|tKGYzv(t@>i^o~#wuPGGbBGFk>&EMwPy8kj9^
zx4t(v3)r;;R^A>$s4O=S5|`_oa}Pib7r1)s!-5n|8-H>=n(V*u179gAIOA-uY+aT+
z*A@A{LSFC>=&ugLzKp|IKIgx>1SFFm`qdVb*qI#&l6M^{W%Ir#m&JHa{H#Drs=;L-
zy&ekm`ZP2|Q+p{y01gJRKv||}MGn8IKc0aJMvgTtbK-SRiA_3gm3s<(KHcnl*#ro7
zyf&eUuN8}Zd+?D59y-*mwP`zZ&0V6lxcu6C@Xhy*m6!6cO_ox`316ZDdhym<b>pC1
z%=!pWYhM{4l8Fbh=v?SLV{65ZVB0$CDfiy7LKu3TTa19x%7#lV1|3Z?$p0(E4>^DW
z$bQfHnS~La`WE7myfIo+(TrRgSlevR5kSc-R&*X*tDRWwQc!r(Gs0(PZo2GE8^yY~
z2*ted9#Y`XdqXX`-z1zKQ=>VDucYQft-u(KG=yqb>2Q!Pxm#$jsJzmDw(!oTcZ%#;
zGa<K2Dpg~#7>uWkm~2cE{b70ci1H(gGiM-|9bA4Z{v5uRYP($}lRpD%v5Pz)Z$Ok2
z2d4crw?XF?kffIYmhFL8`d>?1rW$BLpz!i5<58>W5ZZn|Be}CHL6{e?OLkFGj+2X$
z(%zd5`zi!jWDY>J_X$J&uH~L?@pal<zG>{-bWzPxN}cJ;vMcW^IUqF+@Zz-zN(Y?9
zK=l!H<wzNMr%KrFtd=-aizMt^_~TgFe0@{D+;KrR_|deS_XaYlUIx@r^PTFscIX5M
zm{(!ybG>p~2Wc#We|5J)QcpOCA7&a-o=uh4VF4XMpmfKSLup_2>f*7tF4>g4R4QNn
zqeb};?V#YOqrn&G`iTsiy$>w)fXTtw8kXL=G<>DYDxiy0DP;Vrsgqa4e0G48Z1|5?
zG9=(@w)+sO+C)1#RP)*NGMZ4Q(ub!8WCF_DeKG6lca33QC`kLl548SQTxK+41RFkw
z?J74_o9XWDz$ldiXa1|$a5d};1m~=neI`8gbak})knP@4>9o>>NKC<Jq3<DO)Q-wq
zzGzmx2oso@!_PU1aN4NF?v0~`{{vCK5gIPa%pVKQ^d1-06?q_-y)I*i<5xhP5oY}W
z?eZfihqJ>;UC6*L_I~EAH5+4Ms>}4*V_r-^(PB#E_H{=*MGQIR--jGH=U8dA7Ro;@
z%f#r}@1+YXIQ5T|e09RUQuG=xeW|17w(~80xXj%$>MkKglU-u)t1_(MDD>1`WDbUA
zd<x7gelzG42_W_Txd+O2AP+I~51?NH&Zv{LuVzFBQCIwUa2y|)o3WXwpT3xqQiv<U
zOt52s{0PeK!6!wYC$~Bpzhv2QZ?N}r19JT9e|n~G@0vJ2h<}P)CLOVZ-IIS!e?9R4
zQ6G)>Dqzq$<%`Mi)<?Vw3ex*Jgc;TZOiP3vHz)r$XeB&ML7`d&3^-w}K_=JIU=5ej
zd{}-71=R>0r-!rpzolLE)KcgVlY&<K!CF`#HchWtS1zs6Y*AN%WR9dR!CIV-qrCKJ
z8D{1`V2Z!&_pbnZD<MaKljN~bwMzl540=v<Kc2b=6Zv?h|BxW4ae&%`#a}@yR0}Cq
z;|74Qg;)1E6mJJAotR~C`<Q6?UCGB;DGQt_7DdpzbWoxIXAJ!Ng#u<^HTGWctN7bq
z($$tjy%C4uk8=r7<^Wt4dToq$+y_nMbZZ=_0RhXLY=W)|5XD;HD)P5<nXvg{m^H|I
z@96)Q2SX+j2HHub#vafTJmX2<G7iX7au@kaJ@mC0=qb~E!H`!1a$NvST9vvvm#Ngg
z7Z^VVPPT;}i@$5)DeQ-FRX_Mj^Z$Isnd9C8wUVF?aj!{d+=293NCNJP0a4KfuTxM8
zpZ*fr@c1v0&j^q;1Xs(A2ktvHzCdYP@B<<mWIz4A&p$~2kp?srDiinj7U+s3sD{w}
z&&1R22B&Pa6y$QiT23F_FA>>-%A0_;1+N(b<Qev+0DTNy`rr2`k2?(ib9!^r?=7R<
zCG?)^yC?}}PoPFi%Bct6`PknIplktRimI`d1E1{j8WduSK<_WIA9VBHloOx>RJ_4h
zK=fdH0qO^4{nozsC4a*Q8f!^FTKdx9zOw)e1_L(=V$H|s%>%mr_s&r+Q;~h{U-Yf}
zpI5;s|Kc28J78dxpdSXBnA&f4?c0IGB_n#fObVo~$g6^3)1D9ddpq9^A&-S_r2-gU
zVDt<=;FsneY0iK&%cZ!#4+9vCVgPB@m48P-6L66YP@Dm=`x@si?>@)kuU=!MKu)Jf
zAb5P%gYN)ZSK}t9g|MKGLw*T-vvcmR3Q7h}qI@%S>+7C0fC|?AVY3Yc%$2tXh|Kym
z|7G70iNqX3dBuQ_8b&H|evSej1h`rrG5~eI|D?Q$XYOf6&yNRfT<75$j)cG?2u3S(
ztKy(H?>967a6vVZ*Er~xVX5N(Li^G#6eUDKBjyc|(1BSWI51G}*EOLr#(`eB&%E8E
zXO^rB5bOkXcJDTOAf_IC4P0JjH{9tzY5*3YBaCWyiVq}Y3Z!H9?yhX%4&)XM)b`J-
zfV@o^M#jW_4;zN2)Ku;cLv7u={hB^U6<~*-)8hb>@q(mq0QpJ4v#Ak=1Eh3XOL59Z
z0EX<{j?X4IadXZcm=@h|LX3MhgI5gbY&#M7^bm!x48O6yL$6d{(?68M{V&~ouVgtv
z_UH)g1z`Nt7obvnF(wc8O;iad$JD_X>VuwbZtfiLlW$QDK=PstFdA?$T~5n69CW}m
z(bD2<!d}GzWE;N{a0g0ExA3LHwjp5Lo~7AwmwN6o0j;Wn=?}VYZTk5@C>Dh}m;pd>
zj*$?xKcKdHp!AXh1P1YF@Q*Abgai3A?3`a-VFn83uvaHA2Nqs{drOQI&3$33`XC6D
zGN{^>w*=4;X;wRUD`Ub4Fg73XyhR_NJz&ZApg+%Km>3CRfC-r?H$igB0S#3B*q_%s
zI*Qd@Uz+!v<6r4_tL35w-ZR3OgkRIQ=n@XJL(b3awH0Q<C+KD1inPdsFC;SB@gJxY
zPR=-A3>6xuOeOHIPI3pYonmC1p8&iCUcCG?7$y-?9oKh;F^D4{JLdsU<)Wc?RKPor
zL5mL*w)^%ue6cRh4}-f8bsR9*0=srFx{|BSfCmpD4p%mVZY}-+wrvvFEo1<uD`~$E
zl1m1lEh^Me*0(^g#+@Dawf@JOCLb`Kpdu8;>I3d`OQNi7mqGtcE-+?4hy}|AVX#;6
zY>Y^NhBy`Y5wCzBN2KKKcTfj!pONeCG6A!L;B`M>Bz%D!DRK@E?Gqf|v;(RAIDqYL
zC&2ZlHKBb7dx@>qVAdgN?T*;H|5)J!U<dRu>#uB#j)1K^8nlNVn?dZ++cP{IO8da<
zZIPRw76J+%d@=km{9-_$!aMw9=+$@+k4zv7NWcdxD}dP}fR?r=9NbW=U&DnIs(~~d
zs;UL7yGLf&SHoUnwt}3M0JajLQvbqOP0T^BoB;y<w11=7TDw!-mAubA*6snoy**gD
zUI${`>3M(O<cZ}#v{E^Ny6*J>)Fgm`c&y+ivJZi7uem@BP7Ms$DoE$tn>RTaFjnQO
zoTTT2_OK~1$R8oSQi@s6-{;w58fRB<V*~KULJstzb75p(dsH2zWP#S}AaRia0;>=7
zA4OB4TyFnc7Iwgi_QV0U%tC0B+O^&vp_cFTiq&#JA8V`A9*TEI0}`tIZ`U1FWMJ?1
zG*c+&Ml(SSvJg(flmH(E7_E!20&!poGr?krJ?-qpbQ8`v*w$s@#*ID&>%{?-Fueji
z>V|l9_kVaKFl+*07m|hzP<R%<vhA}kV)1vjZ2+ljfbffQV6+92!6?acdPwdQes3n5
zYZx+R7frxFW=_f-`18l$zL?_G73LH`_eB#>Le%mGICU}7PLDkms>Qjnd!pIoaEWsc
zKvNb6#&5$6d=|a)KtU5|4RCpJr`@gY11RtTSh|P<N7NU51wBszJ(pu*L>{0!YBU8r
zG7ssK?Hk}Ly&ee8<i8C}1Yp*_06DD$c@c{z`5F^rnDx$fJ*f5gN8H?eL@?RvW?<sk
zdi@yeKJ<(`frByRAa}y$ucDc^__JMZW?D!U(j{OxnYy}6KnU*{wy)&c`!thS0^tbH
zdGpHc(Ol5-MR4AE&ZFf!?@TzMuUN2l@cRwlB#&(WY)3+}Y!8^k3Wgr|Vt?J$l~)t%
z-n<NIvaF0as8i!WUy5M>R=5}`tp}*8h?A6Ldz(bTVAjGKX!NF}Vb_6Inv=T?IYZ#e
zVJDu%)>2*vVKDrhE^Wz&ylS8T_VEhfIhzdNIjHg$-iL~=pKt0*X_o>v9@W4mndMTD
z43W8d^N_p%01Ycq=uWi-kU*$O{gh^G4UJE8bq`$#9mkx?Sz4GjD5&dx4EP<wNO4cK
zhaRgMQ&!d*2{Lb>tW)TOjr0mSHts37@jl{*=|0i{#2E&;at)_qobCW%f-5Hm1RZr6
zM1~s8q_X}tPyK5QC&UqFV1`(L%ag#bh`3WNr@F5zUaF{SB|3d!^TFawQuk6+Facnd
zbN&NB<p{*c-QRy~{KTi)k=J#^+R4T0BzgopBhKc*MVKxZFx0iHi3id*iW1$Ovyfy*
zILIa^>%>UmmPqQ(7xDf7!9L!C)P`XxfL0v@Eq2DinEjArL&V8O`UCOP$oGlmm-Ix=
zVYu1I4>AiI9V`n2s12C!;u^lS&#ckLc9bZ)jEgMv;}()b%aZLuQm*yx_+hUV;J;eg
z0tE!PV6boIM(g~>e4YMK@`asj+%kn`t>xKZU!${tz<u=#RIDDnQ>~Ls4@rppR#cki
zNIm(zX?(%>ur#OXWlmX5u*3F49mrSze{dwfCFT0$My2h<OlTOHk#Uc+T{q9b+6|!o
zwbvz>y(QDLcN1hdjidMbH=C&6G+a;i8A&Dkd{%Gjv`@pav2w^7r|803PC@NA67MKn
z-FIbse|QI_u74lOw;Nuba8W}`bIMlC$-`P61ECQ64TRzY2Dz`|y#fRpIk7P;SRom`
z53Q63GO8PZ)sKxvreQ57!fa_RZu($P#sNJ*<>MUYQ#Xfn|KpJh7jRg`xT|%4O8H3B
z<=RY)^XCC6I@xCq%O`@M)Iv>;jS;<d64Gd1Zce*3txgNJR|Wl5JC+J?e4(`1&ZT#-
z7G8*$b`VbaVdnQS<Q4G5H1D*D$EKn5#`Z(abhOEfieeJa5wE*ffuAZr0_E8~&oMgg
zN5=BgEW81AXNX3a$p^QKcsYDApv1h&mP?f$w$d329J!M#ofux=oj@Zq9T}BXdxm(j
z!#;ayY&&(4%`2e#^c>6@xIs>WoE{hV)uVnRkRFP69Z{@oAHl5tK+Ek^h;!}=?sN8c
zx@Nx9a48*Sp^a>6n$|nf2oJ=liEnbk9;!k80U8Gc4t@K9!^O-cE)B|`5%ZDi$=pj{
zAE<#`9PGZrf11yY7Aru>%WW}jTCcm4AP4VNi$GZ|d<RONhjTbuV~@@8rPn(6<79=|
z)TA9RB_~IBnwv9Hu(^~W`=+vsuy)9?*miPMkcP|<xSH%Yw-uyqC#<BY!xm4QV*jBU
zf`vf^sX9lzqyVNz74|%M<N>E^qhr!)6BUVyl*m{9YTD`w6DoF(V7fv|B{ZWy0r()j
zO%UR&6x&xrEF+_nxxDOG>slsIY5(39&Uf2-ng(qc2K4+WQSFWbScwA>F=hGGO=@?w
z-rjD#6zG>1b1t)@yNapO*JEw~sZE9Q8zO@Pjstdz3epE*(X>uep2Y6=du$x%173!R
zOPSQ76v{I+*`36I0W3KUF!(b8NINYcXz&8#;KzMw(3wLyb3!`8m|sm{amwv3&^ZfK
zXs~tCpvWkA!yB_chjBs=?<M6kS{J%e(r8oO2h935(G(M?u%q(_0Dz<eSl?rKhVkvb
ze$0{5XzP%8^-@AL?t<TPdZ7?y5@_52U}LIWP!I;CfM#Ik8n)hl-1dbY6O>nS+s(ac
zH;ht(L>aiKAO;8r3nPa?BBumE=h40z;YXKAGpgave`xi6FvT1G3JEBV-D|lAoTP`r
z%m-kYxlCR6HSaHrA@^p>0L5xGU=d*}kB>RRJ_FB*iE%Xr(li!_MnXa*wr9MZ78ZH}
z9>ysuY(D^_%@0Q5s}JOsTAYOBRtm^%C&tNW3apm_&X$O*9$2GrqHf6CXZZVs=9EPG
zij~542$fLb%8<7#J%OOM8RhxQ6j+NC`Q~0)6dgB;&Jkl3<VGI;bjd&>hi7`=WW=@8
z!B(roA5Xp$#j{?!^zPN8nPhc3CEG)(4_+GNxqbWIRg@c)OKAu%5*S2X&?}a-pKME+
zCoh-Iav+ts0`C6yPj-#7SM`+DG8$07AC;{ssui`dvLubDXnHbv3f9e#WlQ^~)#FNi
zba21!9<cx9Ow3|m&8%x<vzKqgDL)_^el2z=n~nX=2+J`M<b%ViP%k<<mO`X8%b+C0
zV^Y()ZQNzg?#ZG-b*aO!)eye^Lr(q(Y;3n%ha<a8*!bnWw8qxVOnR^RD=D?g;87k&
zm*|`JUDB`^2A-Bf5-Hk7?$_%BKg~f*i(sx8c!Vu1ezm>)D^9|*+aY*<7S(5R6{PaF
znpnZX1VQ3gBtu6pB;AIde%|ANj6lZq$N3CxKcW6~qOU4{br|l&)1H>z#j~L~2}Our
zdMKAn+?JY6N`56Gy{iD%$bl-G#qq%p!Dwrs783xmPJgrpotGo;@A~}~fEvz!ED|;P
ztqoB+(yc!yR~Qnz`xW)uW79U6`aGprQirMzTd;swm%6PU%yDnA?Dr+;t+tnVxrQB{
zVtcn|JU?35V#Vb~H13nyCyN}Fd|*}oz4AuD)Kax{x_F#<>+>HJL$4@@gsu$qd%i;O
zS?)NOCGS`@-Y2z87U4nv{={DZ+!4wwb8!yN4%_1nueC_r==uYpHC%tQHd0rL96t~_
zx`h~6tp^0yUOf+<M`o67_FVRSxHmfS?=nf(8RAIww^PWgQLFjjX(Z_U)&oFJlBqoH
zpEm_lQw+h|R{NY%dLk0_rJ}d-c8X(OktlDh{Z)6)rf72PUgJi3QZTQ`rKS6oLiI|Z
zKj32f)DbWsjdJ1P!SDFj`V1FrB<}cJmK!|iaMCy^%xBKf(xJPL<tZ&g(ScX0JSG9W
z+>*k5v>o!=I6|ARj(N_b`Uu(pI}e1x-arL_qLuryT6^^WG4<yOiP4`We+!Mxu$g)O
zYJxsm&XlWO2y}v~3Gn)$>@!$~l|P9!<6(CKcpFe%6j$0~tl`&{+5fQc!DgK~BO*n0
z{yI)VEjW;8qgA!o-2gzJ7ebSve=(2q?O<`HJ?=U^csnFfhp1qas|X2*eKHyIqD5(u
z@4g4V&6<OhzXn_2g@*hyATa83U9dD^ze7FT_q97Woh_d6q~P%vIEE3u#8<AtxJiIo
z0f5@JYOv$Q9m|dmx)AC8LHYBfZ|4!aR7J=LA7YZBHpxEuKB7MR%0`81@$7k7SWFFg
zq0*wGgEgdIe~$|i<#$K!t7fb&woJyN#A(3`P5Qxu%JxQE4q)HW2<@XN*s4l;7AbC&
zS;-L^7oWPP!Kluy7mhBHrJY2J(GRQn%fZ`ymkF(tMTjIb*yG;4!7N=Q2A2!guZ8c~
z?D4+d@r$#nLOj~8J@B&6J8W|*i>~)c;FUga1K8u|65vFg%9kA-qW3G~MiKkyU3z9|
z9x>vYxS{H)DP_)bGNfF*ex7^7Hl@#jjRPk55$qk{-j$Y)R9Tb{HveP;xdzV-kdB`m
zQo_N1O?y0E>ACE8fA{ALdsvAC=n1_-dR8T0y-^YZJnYqT^E}qxv=HZD&SM$<R^qO^
zD(?O(``~B*`P|>au<Jr6CSYt4+D1FJ!GZfCl00Z3U7u<r2YSLcy`!8lZXSJk!|$?q
z(uJmZzJ3~*eLZ0BYtWBDwWT>IJghQP=B}Syc`hP1Fl#PS6oq>hJW6cyAD^E=^)Z~C
zJLFYrE>HWXs&HzmIJmqJ1vy#Q;o9PkZN`&hPm6KiYz?K%d;LTD!=8%}lG?20G)rh<
z^r3u8v@l!VZPVaz?hVSGc96fo+V`UXQ4ym%n^cUr7JJkB?tR&yag`+lsR0MPEdz{A
zUp1b__CA1D!)2V>qRu{x!)sMN5BQZy%0V?3T)48K8`ZjP6l=5fbch{x5%5g#|7-8c
zznaRj^|gIUx2V)B?V?Z=tGo~ufs{cZGQ<(RfQc5Z6f#;WhyybMGFm*PN*Uw^851bm
zfvS?BfD#Nti1Gxk7-&HSgb>gWWG;h32SW1p3Egk4_tyId-dgRi-gC}Adw=`;_TD!n
zw~l#w7RdVWHZvZQE5jS(eRNv&JkMj??_~60ux~kcD>y(Z8Ls5$Pb|V(QSOuAgeh*X
ze%tr3MAX~WYao}MwSZ;k$F2S2GIx_{ccMB}cKm=E7r0X7r|2NTG0!>^YRFLwGmdn2
zdIQaMjwyKEa#5Nm_Zy}ugTS;pSmF*#tU0jc8X%cdsN9buzioWALx=f%eDK9tmQ9Vr
z6reJOF8(-%D1P)xG<?VBqlA^a;JfB$y}7EEb~J_%2@a8ARu}WQa*5Y$V({=C{|c^b
z-rr$rCcJt)<*^+m+Q03`#ZbJKs5enkGYNv2r3v>=MOhyAejRUQy28d1LTW=5!y0#h
z%`xzqkC7Jtdne6^{4811GISf!t?l{F<>h@mEe`10U=c%nCeDSNiKreQM+Yqm25EV7
zJUo0qnP#GVq!o&wZ;~6iMMdNCeN|Z<=jM|gxa~xTuN^hlo-8+d7uHjU78?8P((%~>
zas34^a8%gcb%*18yiy#1*+z%J<)))G1}Q0WKQ|{upXF_365yd8@DTI^@PGE2;_B+1
zR0x@sh0-S>>Z{LFXB?*DcETD?GORhI$hQp4jepp2Ve&JG>@x5M{U{jeN!pOLceE7s
z>=#ghLV$zUsNaQipTKXM6yZ@3xzA&M?zo`0YzDr7_%Y<f3y^gNxA&&(s`h4dT@&u9
z@KCG5nt3qOuaLEcZ<)dd5Cu9a%HRvBw?ZyCf3bKc<^qa#fb8X;x}`nL`SznAUdO2T
zjIg|~El8HFWbzIwO5j>eHj>IoD2(zmfE9jz`OEzwV*!m~XxUn1*)_7lh<SSA>@+RR
zmNJ7_u|~ss-XiZU2UVcIJRbh>J0M*T&uTQbGvDr7QBbABt!0Sw<OP<wi!n|X+7-Aa
z>rT|FdBs9-{^lW$>zm*(vZXwk3qPPIeiPRJSLD<`fvBD)ZL}~J?S`{Mp+s<zNQy3u
zSLe?EAjxCgR{AB&L9G~YI0FuUjTbC{OMmn^oDH7rc{#?B=UXN!4?!kQ0~v{8(8Dh9
za3W#vrDbmO7e1D)PhSVH1-bJvy*aS!kW&-za}pSv)A7rFD-*#2quAb*pPiQ9iRy$+
z2hTAXx$$LT%dsG9WGn&s@EkYVq{VjHj?Ys%+@#{CvjG5sVPx*+-t;;vF+e*D?F}_R
zwi~QCM+BIn6{3OdM7eN#^V8!jz?qwLz4dAJ3t@)r9)!ddEwIf+#=L@x30Hb(>wuMM
z>WNLJX**Bbf1ct*6MttRdv->h0yo4sNX(vrn6;2GOzNf<$=R&8@A3P2iA6;-73GzA
zh@{$!{(ipIqb<%A<SAk51fbs>(Eo%G=E`0_-VE`3cDa~8(6@Oi?wFO1L7Jo`F5jLD
z&Owxp=|6=tdVw{jxG`q`D3j>!OK%77jP5KiEt<Sn59DcSYC_oaVM#2|24;Q@t{`X!
zNa0Ec@`^V2&ZPwTv3NH~vm3Yzh-y{Rv$js0Dkua}<3q?U1GuocMsye;zoNrqNUd5}
ziLPHb!_F=(ne?Tv$ztakzs0K%@<G$}{tQWG{Rt48{OkKAB^<?F++wo?NOzaP|KSGU
z>V3JR-Dn}A5KN~P9S6MofUwV#E%@)D<&KD}(SbQL71hk<$T6>JT}x+0A!I-VFdX+Z
z%#qB^Ak9LHkGi@R3cj6))@IDFn#$;gupLX?BwgZ>#(;}SC8y)pTqQDrcP1yodJ1(R
ztyiA}&rg7GJ;jX(#a?Z+9$G_vy>qR2t(>1C`Jl6Os?h(2yz{A*aTKSpX9DC7%U%YT
zTX_W(C0%Am#MNrEdZ?83xnKBggBDk-ixp6|v2#z)<3?;oZhck9g$Q(*^Exmx$>Dy9
zIY(hbsJ(`fwzgiN8~TNx{Jq&n_;PI~J2$)zH*#j=YJv-Uyexn~=r56e?*zC$!2>N2
zTz73-bEv#pFxUKGEYGIF+3|o_$j2u+Q}>i}J0;T&K;8*C0I2@M;6x6te5)0SByprI
z5mCWB(bwH2ZiG-@SH^X*L(YK~y<%6@9R)4&F+s)jZ;+fo!cHOK$h?H8?K!xlSRSSv
zY20wmJu%r#K6jd-<?czSNqZ2qeDeWXd%^c@P7rD<Z4HyH!^KD46N@JJbnhO+Q<gij
zCvSg*bUH-XL+KukmdOz!_m)DfZ>&5;b}lU24+X%1rBf5~fU6r5mG<uclkP>mK;64Y
z<o8owQBrdRD*AZk#j9?T^Gl~*rtDtY0P+|0TdvFwz>x+OumnLW={xvV_i0G4a$K{8
zVp(XHnE`jlM&E#ws@EolRV|n6oH3?qI%@re(2VFH16QJO@$MdVWpQPC+Nv>wzJ^m?
z*}Ytjayc-nL6yLFTp(_6{I8%#qFcVZbP_@#GiQtiX4Ie-Pb=Fef_M}1oK^C*Hi^z-
zgF55;NOvTD;K19+zA>P0(JEMUos8N1k8~c(;;Y|1^AR$ekF{MMa*{<tpzh)EuZAln
ziFz3Q3V`Bw970uuSJ4Dz2!NuFG65q-wsU%-F<^Fa&A9OgA2Q;efmqXfW+g_SM+;Vi
z=p7|zXg_Q7!#0P)-K1+yg-?blp{`9#7f*j$V*!F5N^-)hFX+Enj6M4VxgZG~o+)$X
zsunswy|pPO!vTCjYV3t`H{N%7xr^%jmrmtzV;a#xHE>YSBCu>RVV^5|is(W#P+?<O
zSo2k+%yC-G-)(a5_16=veP{ZHD+4XoEyhG@I^2H=Dz!+}elkmo1bGiT{zG&4m_#f&
z51-`cuB@?vg3}7}y)7$s5$2--toHkNMeEPAaHS3MbApndgXh^K)|J&7JeylQnZ>zW
zItZ-%1Tm)JR=9}Ae?S$yhm>wcS@bMl^2i#HEm1rW@7__VV-QszbG$bl_;MYT|JcJY
zbdPkn#|U1)RwQfh5w?b7(%rS*ep_bgg%#~R;p^rylwXs1?X~{um*|uXNV|mCzd<!m
zDBk0xTGGqt>{(~$yH(n?-q$v`I%Zky7k&;?ff;azA8o;=F)lbaU#4+XNVV0AIsZNG
z*7I6C+xLyIa{KQWm0@$|Ta)Dx+Dli1a`_YhTOA?-w3jeUR?7^A1IA80sL6j&yn9E)
z(%^?NBe5nR`BqSqokTau_5!l9#z4-4NsR>+s#^%Gqkkes8Qv{;v&5}u{pq{0fjjvw
z2Fv;81&g?NL2J%)l@Q_b*&o3`!y8~=o-CFa(Yip{T_@i^>^)b0er0Lf)1Q+<X8SmP
z4?}+m`)tUMlyMO!!ze@tl}z+R<iZ5NoEzy)C@i#~OWQ7dGy9<=I%>AF?#sG!-kA@?
z{32<Dd*y`YjDwBo-6?ApQW6lLOm@}$VIVWimj~%<ei_Q@EfkI1ir|sZFkC+7HAmJx
zQk@?5oVm8V<Wk(l*HwO_>NMX`VVduY(Tr4?D!E-XJ2LQGwGZtg{~qm<4wvD}^vGI4
z&@#AS-N4N@Y9icfVujp-qj|lSAyic_uS)eRjE%lT3uv28tUCQ-GLt>1TFzDZgGxzX
zLU)iU2K;#;{Cx^C&%vWOWDB~R$o6y3D182$cdq(@)xCI03b-kYQ62IHg*S-bb~BZN
z5A5E2{`9y(z&Z<li*l`rn<J<Lw9W<QK=h(7paxF(!}0J3H)I<LFBeqB`BIxYPt7UT
zmWL`=bPL~{x#U{AA+e=^9~{5Ep?JEl>AievnsRPTY^OZ3cawUB(7$v5L)-@@GCmEv
z?a?|vK3Asg_(hg$Qca+|Id$^fjgR9eURCLI52rc$m1$-nY<XlY=v0lX5&Y;5#O?4m
z_e;DoWvd8bF(Q|YZEIMznO1w1v&R^j9LJ>K!<PvAY+p;wTM!Q~5D$z**j%XK>kDL)
znJ7w$JJxf`%Od_-YtWL^J)y@a%WSJbQWa`9_fM(9A`Jm#&JdURgQPpx!wp?~x*>8K
zC7=F1-L$K-YH9a~L5p7cxMh8#fJqhe1ETK((_*%p(Yl;to_02r4p}QiR(gC-;oZGV
zMn-9%Ud02(v##TDUFS`ryn#FCVIArqF`gA#hq}Q`S-i8N2T@1AhY3-+-k>F~4Fom0
zsZp`_tev*8(E|zbLg<M+4nCnj0Xpy`?DJ(;&?@WR%1h$yV{6^THG?2q$;pFBlH=qI
zP%aB3WDZG)wv_gH3K@G1*KDOqQHuMh51CLflY{Zej>^1qT~@$7smX&lag19_6Q5D1
zgGW(oh)v%F#QLIM-;OFKgf-}fQztC*PlZOqV);I0<1{_buJhL^Yg3|+4_)$I=s7k4
zk}w@8*)Ybb$qOH<@Tda=@P%u>&hhkCko~nb4ZfCufI`-_pLw*PEmRE>BIqL;P{Ich
zD2PkJTzBXjC_SyY)z0M+OXjA70=EV_Oi3O+3|rGNxlgM`|1Dra6l8<XRalqeAD1|)
zWs22heA)He?`5fT?DNvdUwY;)7x%p@hln!co4CCsK&JwRIW`~<)-RB6--2(Gag9Bd
zhjJ<C$Jc}~=v9;Fb*Gjz-ltyHAs>?3RrLej=3h4#MbgD7$E;||JI`T~-ipM72jV$O
zs)&Wc)+2);17$^JF~R<VSo`>?$LY7B#?U9!1Zlc*3z-udpZiE9#|uWndP<<wP6$O?
z7(#`6lu#ccs}OYiYoYJ{iW&;_-KuGS)2?{+M4hOgYB-;dPaafA^yk{X^_Aqw@1T0-
zq$T`LRUy)SCd^b}ma%I=!utQcP|<ZurAthBcpP89{)OJdAlbX4MBHYohx7<N%v$L(
zm~UD5ED)@yLhPR42DNAc6S}^Z4&J`_XehrD_P%Siy|_seLr%YG4@qAo(mjwW{F0ia
zDTSZ1>~$tud4M(Vo$zTI-yFb-+~a-;H0x=k>Kn9}`GSCY%)4*y?_ZM^=H_OBtBZFg
zUD<fRf}=>|sxFbEx<f(lg_)pu`l!hf)gm{1@f^Aw6M-=mfp|81w+%7ToRh8^XnVrG
z$?`<!Tchz+`s2+W4{btVo^u<TFznezq!eF9cUIRkDH~`(t)ZM;lS0O9Oj}3Q^JHD%
z!k<oc#koTq&4@Tts_HZL02RBL0wIG^9HxMP+9{~~v82P$G8_sGA96=9Sp7k4dlA=!
zkfmnkW;551dF}xV`fkXi#>$`D&1@U>!2*o~v{0C}GZLHc0fI{i^-0ob3lw=l3GAWw
zlNr*ohriW&{dV@+Rzv1&Rmbw-15Q<j-xeGK77{~~Q-YK`=o>(A0+fg!A(a-|d;JqO
zV7!q!CgfG$W{VR8&CfUbmxO5q?Pf{MesC`97;-%L42z!bI}q<gN}WQYy4PR{wC&D{
zkGAT+DC+>cZ^;u=KCrevM;5__VMB{yF0Kp%MV~=kl6K03t-q}uct?{kl3s#spvutV
zPW`ORi0jA10*F{CM^Q?u^xlha>Yw{xB8zcgFoE%0fUPs2CLTo-v82b8t$O5R>DGmq
z%RWmrjEyCw90gQk3}2qC61OrI{BsVsFoNnQz;j9M%ZH`Mz=UkwyeQQV3JVK!vx2S1
zpR76#VH?2%ofIuZ$rc_%jHYq`n;#Hoh&n*Fu>AJExp%B|nI6}0GY{&<t6V~ODK$+8
zE<rPHh`fYM2qz<O<^8+v_nPTc!979#yeG^XtiFRSl3^-<4P6L4s2R5GjI^%^f;w{D
zgqV3%@#O9xo7%Lp5mML{S1R%P%!cT_&*{|HKtK`*UKk>0A0rezUFgqExwTA6!-W=_
ziHRPq#RZHsqo?&kh`;By<ZWQYd?v23rQAcU)$u`A)B)5ALgOji4eu-EFm%BpUu#R`
z0w+ZvSBv6@k?zcy2ct9KOFhS{U-8jJj*#(ud7kOe_)N|$VV~h^86OCZAsQ_~nG!X3
zWd(M47oeD}&?Vw*sKG0tzz-L<46T1^^t(Ni(*$=ZJ)~gK{EY?of?A)vGgkVLd8F!}
z4Ik$5Efj1%QUK#?T;oDYHvyD!VxlD{SY^tbvR67j-y(knn?SoYL#i5Zsh9Oo%s3tu
z4?c+nnX5oDcNhlCSXTs8eGa6?n9>}vUV^PmJVDlkOw3R#F0U>FGWs(Sw~Yc=Ty>U)
zvfK$Z4s%BIBCA*%*9-)0oqN#MIV&ph`o91!<f4mY>EQdlO3yx;U#=OX6C^WENgWl9
zc$;a4;v?=v*z;t2k=7mt1*1QKq!e9-Dyag}PV*Zm*t3M2yt!D#8~~%qxS{`B*aY6)
zblx?1;mwt?oD}PHJ~T)QWGA5_0XduRUo;OtZ!0o{4hhS02B$hHGV%JGve)I?vBNLu
zlpP^_|5I9$l*T%`ZMpda$dxo)Ie{M~U1@?Zs6FJ+SghB<ke9dBnY(i%TB_j7uh>(e
z?^=0EWtbl{*!BA~PzL^EdtlF!gQ4&P$9&lph*|#zN!EcCm(pfu`v8R}D0;SWbf<_$
zu?u^qL*a7PbO_UrFj$8|qSQngK?th=x3-?NsjgtvKw1sTU&pI}2}~c!u``Sd>a3|!
zT2v?qvUOGpZw^=TfgvR133x`NMptx!Zc~@&%avV#0>e7&BFq|_^1qCa+{ywDv)$YU
zgoAnf0l{Mn<ZCXjxj<?d6hn6iqq7=`3GrJF8NZR5hh1-n_`|ci{L!<&z_SV*{$mo4
zA_fdG-=_EIa65Qxe&O&B+m0S_W5AyZhN8~`fFTT^q@$$tpyDJLlD$lVd$+;f(g%=9
zN45dsW7&t$&T;^0H=!Q2JUN>VDQ8&3x4pO_{zIo}pD}m{-gE*8(WtF@D|Mf%I!hLq
z^A?LbIyoU*DM^&-!Kfa{Qkrfha#9ki&$D&mS$m3OtQ6x`t6LZKzu)P<R8hn2o%*SC
zlC8Lrj$WN-FGWX}jPV`gp|M~qDj--ZxxwUI=)`4JKEx{E(GGYlVG1VrnEaR)H1J-+
zj`H5ZTTIuxsQ9<VQDig<&%((bmLOh1o8T%nq>77cehSkSW!U6|>d7K#{y>48Wm*Fb
zH=)OVg2!@kR<6vO7Ik{SFyT`NLWmwk1QEFUJjfWf38r)KrlPp|_(8>6B5pgC0tQZZ
z_^xNAvQ)uRkiuVm*1~h57ckAhaHu;%xvDHeU4=`JSnKr17`CmdKM?oy=qNmc=_64L
z%7pj7?xfXSW{&#tV<yZi4~A?VTHieB=5f5wT#E{N7Ni=+`6~>XxvDU-%2;qKXeB-V
znBqSt(^<a)c(!OC3wj3?9@dKFBKyuwnJZ}vprx;67aBBA+BG#<fmf`ao<i{mG6ydw
z6y7@OYT>Am;~?S(2MmAYbueeF;{tOp$5b5rGqR6!9m3ZCC3vMAhm$|z8f$8_<+DX|
zV}Hr_F-*IR0_HP;4xK&%ksuT!csz|_9aKCk-!F2p&S^@0Gb1mfHCHX1dKisr`Y{0P
zRh-3>8No}0$IPJ5`OT~9cgGcIcS|^c)WYLS?a==|sdDvS8Xj2K@TA8%ghQ4ZGc%j?
zWIcBuBjd8|&>f%&`dEtx9t1ibDc??K2ye(TVaBF7y;%F_NOSPE3!^X5@;+$HD50*w
zr7o3!yw^x0RZTcFPbGk<Bi-6hZOBob<+BXzdx}f*Wgm&SEfmK@P=02$VXYUbv7!L0
z`LbKEAh;X7&cRl$0@R3>Lw$Oh$mia1RIDQUJ`MbdF*m_cB>9(|tUnp-AN2q+HlzS*
zbbTCP^I6==B+4as_x%3-iTyuIGUYp`Ik+Gi>RDIR8DQA@24pmCx+GTP<j?*|<4i))
zR(oc3lA8r3Ci-s57({AxJu*4LAKuMj*(ak5UwG%qGcNIEgG7n>nkTlidq@_c7$St^
zojOQsmmPmX8=E5=`fmUzt8nFI%fwl4C&e|qZOfV`Mb>=TE8K{qP~uYOc2AGv`Kyaz
z{szB+fby(=;K+P5xAqHahNd(n^4DtWBfm-Es@zCD^lCA}geibC+<ybM1)pR~KUsqH
z^RzCXbPQdhiqDsU<FaLENK@T=W%0sv-whg7UuOg@Y6F$&GKdx#IzTKj^Mf!wby7UW
zOMB-YekJ~!nzVddJ=$N`H1FSMtl2}Bnh31mRq=6BsHF;QeGB+WBz$cnP(Q{k*o>lj
zOL4RMvE|~qJ)|Els6G6~mYE}SA?&k!H`LQ8n9>uMmWH779wK_zzM2~(Qt_xbQr~vu
z?LhiGGrB;3T3zi2Z|e_^-3{JJc@n9{0t+h9pMAZ+v7HD#8^fU3qy%ZkEjHRI+a2xX
z>j?07X58`4lI8ec{dlFWwDeGjxNqp(j5_yR2QRWdVDjy39V<?L+uplCKB63*QUCpU
zqyN>>;<~mp^`+>^(eb)8eqCE#UE6#etCLfncgoJM@%Lh$LBoMLg^?B&=(K<R`<Dm)
i<$?b%9`J3{=$VlFzh3d70;V(=M(k(rE7{}o-G2d9+Q3Hu

literal 0
HcmV?d00001


From e8e6685d4911e97fad7d7696d058575dd7a43277 Mon Sep 17 00:00:00 2001
From: harshitasao <harshitasao@gmail.com>
Date: Sun, 2 Apr 2023 01:18:02 +0530
Subject: [PATCH 078/272] Added v1.27 Release blog article

---
 content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md b/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
index da60ef0330d..f1de059db9b 100644
--- a/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
+++ b/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
@@ -3,8 +3,9 @@ layout: blog
 title: "Kubernetes v1.27: Chill Vibes"
 date: 2023-04-11
 slug: kubernetes-v1-27-release
+---
 
-**Authors**: [Kubernetes 1.26 Release Team](https://github.com/kubernetes/sig-release/blob/master/releases/release-1.27/release-team.md)
+**Authors**: [Kubernetes v1.27 Release Team](https://github.com/kubernetes/sig-release/blob/master/releases/release-1.27/release-team.md)
 
 Announcing the release of Kubernetes v1.27, the first release of 2023!
 

From fc071f236b2f4c29a7bf554d1d34975581c697a6 Mon Sep 17 00:00:00 2001
From: harshitasao <harshitasao@gmail.com>
Date: Sun, 2 Apr 2023 01:21:46 +0530
Subject: [PATCH 079/272] made some corrections

---
 content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md b/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
index f1de059db9b..5a8874f9dea 100644
--- a/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
+++ b/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
@@ -28,7 +28,7 @@ Special thinks to [Britnee Laverack](https://www.instagram.com/artsyfie/) for cr
 
 # What's New (Major Themes)
 
-### Freeze `k8s.gcr.io` image registry
+## Freeze `k8s.gcr.io` image registry
 
 Replacing the old image registry, [k8s.gcr.io](https://cloud.google.com/container-registry/) with [registry.k8s.io](https://github.com/kubernetes/registry.k8s.io) which has been generally available for several months. The Kubernetes project created and runs the `registry.k8s.io` image registry, which is fully controlled by the community.
 This mean that all subsequent image releases would not be available on the old registry. Freezing  the `k8s.gcr.io` image registry by not pushing any new digests or tags after this release.
@@ -155,13 +155,10 @@ This release saw several removals:
 * [Removal of `IdentifyPodOS` feature gate](https://github.com/kubernetes/kubernetes/pull/111229)
 * [Removal of `DaemonSetUpdateSurge` feature gate](https://github.com/kubernetes/kubernetes/pull/111194)
 
-
-
 ## Release notes
 
 The complete details of the Kubernetes v1.27 release are available in our [release notes](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.27.md).
 
-
 ## Availability
 
 Kubernetes v1.27 is available for download on [GitHub](https://github.com/kubernetes/kubernetes/releases/tag/v1.27.0). To get started with Kubernetes, you can run local Kubernetes clusters using [minikube](https://minikube.sigs.k8s.io/docs/), [kind](https://kind.sigs.k8s.io/), etc. You can also easily install v1.27 using [kubeadm](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/).

From 1378908574282f8d5ba8812165864ef725c6cd54 Mon Sep 17 00:00:00 2001
From: Alex Wang <wangqingcan1990@gmail.com>
Date: Wed, 15 Mar 2023 10:51:59 +0800
Subject: [PATCH 080/272] =?UTF-8?q?doc:=20forbid=20to=20set=20matchLabelKe?=
 =?UTF-8?q?ys=20when=20labelSelector=20isn=E2=80=99t=20set=20in=20topology?=
 =?UTF-8?q?SpreadConstraints?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Signed-off-by: Alex Wang <wangqingcan1990@gmail.com>
---
 .../topology-spread-constraints.md            | 19 ++++++++++++++++---
 1 file changed, 16 insertions(+), 3 deletions(-)

diff --git a/content/en/docs/concepts/scheduling-eviction/topology-spread-constraints.md b/content/en/docs/concepts/scheduling-eviction/topology-spread-constraints.md
index 6e47447100c..a7691706462 100644
--- a/content/en/docs/concepts/scheduling-eviction/topology-spread-constraints.md
+++ b/content/en/docs/concepts/scheduling-eviction/topology-spread-constraints.md
@@ -129,17 +129,30 @@ your cluster. Those fields are:
   for more details.
 
 - **matchLabelKeys** is a list of pod label keys to select the pods over which
-  spreading will be calculated. The keys are used to lookup values from the pod labels, those key-value labels are ANDed with `labelSelector` to select the group of existing pods over which spreading will be calculated for the incoming pod. Keys that don't exist in the pod labels will be ignored. A null or empty list means only match against the `labelSelector`.
+  spreading will be calculated. The keys are used to lookup values from the pod labels,
+  those key-value labels are ANDed with `labelSelector` to select the group of existing
+  pods over which spreading will be calculated for the incoming pod. The same key is
+  forbidden to exist in both `matchLabelKeys` and `labelSelector`. `matchLabelKeys` cannot
+  be set when `labelSelector` isn't set. Keys that don't exist in the pod labels will be
+  ignored. A null or empty list means only match against the `labelSelector`.
 
-  With `matchLabelKeys`, users don't need to update the `pod.spec` between different revisions. The controller/operator just needs to set different values to the same `label` key for different revisions. The scheduler will assume the values automatically based on `matchLabelKeys`. For example, if users use Deployment, they can use the label keyed with `pod-template-hash`, which is added automatically by the Deployment controller, to distinguish between different revisions in a single Deployment.
+  With `matchLabelKeys`, you don't need to update the `pod.spec` between different revisions.
+  The controller/operator just needs to set different values to the same label key for different
+  revisions. The scheduler will assume the values automatically based on `matchLabelKeys`. For
+  example, if you are configuring a Deployment, you can use the label keyed with
+  [pod-template-hash](/docs/concepts/workloads/controllers/deployment/#pod-template-hash-label), which
+  is added automatically by the Deployment controller, to distinguish between different revisions
+  in a single Deployment.
 
   ```yaml
       topologySpreadConstraints:
           - maxSkew: 1
             topologyKey: kubernetes.io/hostname
             whenUnsatisfiable: DoNotSchedule
+            labelSelector:
+              matchLabels:
+                app: foo
             matchLabelKeys:
-              - app
               - pod-template-hash
   ```
 

From 7b39e9a9ec5bbb6aa89fb50c25aec3f394366393 Mon Sep 17 00:00:00 2001
From: Philippe Martin <phmartin@redhat.com>
Date: Mon, 3 Apr 2023 08:22:54 +0200
Subject: [PATCH 081/272] API Ref multi-pages v1.27

---
 api-ref-assets/api/swagger.json               | 7514 ++++++++++++-----
 api-ref-assets/config/fields.yaml             |    5 +
 api-ref-assets/config/toc.yaml                |   19 +-
 .../certificate-signing-request-v1.md         |   10 +
 .../cluster-trust-bundle-v1alpha1.md          |  506 ++
 .../self-subject-review-v1beta1.md            |  142 +
 .../service-account-v1.md                     |   15 +
 .../cluster-role-binding-v1.md                |   10 +
 .../cluster-role-v1.md                        |   10 +
 .../role-binding-v1.md                        |   15 +
 .../authorization-resources/role-v1.md        |   15 +
 .../self-subject-review-v1alpha1.md           |    2 +-
 .../cluster-resources/api-service-v1.md       |   10 +
 .../cluster-cidr-v1alpha1.md                  |   22 +-
 .../cluster-resources/component-status-v1.md  |    5 +
 .../cluster-resources/event-v1.md             |   15 +
 .../cluster-resources/flow-schema-v1beta3.md  |   10 +
 .../cluster-resources/lease-v1.md             |   21 +-
 .../cluster-resources/namespace-v1.md         |    7 +-
 .../cluster-resources/node-v1.md              |   16 +-
 .../priority-level-configuration-v1beta3.md   |   10 +
 .../cluster-resources/runtime-class-v1.md     |   24 +-
 .../node-selector-requirement.md              |    4 +-
 .../common-definitions/object-meta.md         |   14 +-
 .../common-definitions/status.md              |    2 +-
 .../common-parameters/common-parameters.md    |   24 +-
 .../config-map-v1.md                          |   15 +
 .../csi-driver-v1.md                          |   40 +-
 .../csi-node-v1.md                            |   16 +-
 .../csi-storage-capacity-v1.md                |   27 +-
 .../persistent-volume-claim-v1.md             |   25 +-
 .../persistent-volume-v1.md                   |   41 +-
 .../config-and-storage-resources/secret-v1.md |   15 +
 .../storage-class-v1.md                       |   26 +-
 .../volume-attachment-v1.md                   |   40 +-
 .../config-and-storage-resources/volume.md    |   21 +-
 .../custom-resource-definition-v1.md          |   18 +-
 .../mutating-webhook-configuration-v1.md      |   48 +
 .../validating-admission-policy-v1alpha1.md   |  376 +-
 .../validating-webhook-configuration-v1.md    |   48 +
 .../policy-resources/ip-address-v1alpha1.md   |  509 ++
 .../policy-resources/limit-range-v1.md        |   15 +
 .../policy-resources/network-policy-v1.md     |   81 +-
 .../pod-disruption-budget-v1.md               |   17 +-
 .../policy-resources/resource-quota-v1.md     |   19 +-
 .../service-resources/endpoint-slice-v1.md    |   36 +-
 .../service-resources/endpoints-v1.md         |   30 +-
 .../service-resources/ingress-class-v1.md     |   28 +-
 .../service-resources/ingress-v1.md           |   77 +-
 .../service-resources/service-v1.md           |   25 +-
 .../controller-revision-v1.md                 |   15 +
 .../workload-resources/cron-job-v1.md         |   21 +-
 .../workload-resources/daemon-set-v1.md       |   19 +-
 .../workload-resources/deployment-v1.md       |   19 +-
 .../horizontal-pod-autoscaler-v1.md           |   41 +-
 .../horizontal-pod-autoscaler-v2.md           |   55 +-
 .../workload-resources/job-v1.md              |   43 +-
 ....md => pod-scheduling-context-v1alpha2.md} |  159 +-
 .../workload-resources/pod-template-v1.md     |   15 +
 .../workload-resources/pod-v1.md              |  667 +-
 .../workload-resources/priority-class-v1.md   |   14 +-
 .../workload-resources/replica-set-v1.md      |   15 +
 .../replication-controller-v1.md              |   17 +-
 ...md => resource-claim-template-v1alpha2.md} |   79 +-
 ...v1alpha1.md => resource-claim-v1alpha2.md} |  126 +-
 ...v1alpha1.md => resource-class-v1alpha2.md} |   66 +-
 .../workload-resources/stateful-set-v1.md     |   23 +-
 67 files changed, 8340 insertions(+), 3094 deletions(-)
 create mode 100644 content/en/docs/reference/kubernetes-api/authentication-resources/cluster-trust-bundle-v1alpha1.md
 create mode 100644 content/en/docs/reference/kubernetes-api/authentication-resources/self-subject-review-v1beta1.md
 create mode 100644 content/en/docs/reference/kubernetes-api/policy-resources/ip-address-v1alpha1.md
 rename content/en/docs/reference/kubernetes-api/workload-resources/{pod-scheduling-v1alpha1.md => pod-scheduling-context-v1alpha2.md} (69%)
 rename content/en/docs/reference/kubernetes-api/workload-resources/{resource-claim-template-v1alpha1.md => resource-claim-template-v1alpha2.md} (84%)
 rename content/en/docs/reference/kubernetes-api/workload-resources/{resource-claim-v1alpha1.md => resource-claim-v1alpha2.md} (80%)
 rename content/en/docs/reference/kubernetes-api/workload-resources/{resource-class-v1alpha1.md => resource-class-v1alpha2.md} (87%)

diff --git a/api-ref-assets/api/swagger.json b/api-ref-assets/api/swagger.json
index 410add77696..12903fd69f2 100644
--- a/api-ref-assets/api/swagger.json
+++ b/api-ref-assets/api/swagger.json
@@ -1,5 +1,23 @@
 {
   "definitions": {
+    "io.k8s.api.admissionregistration.v1.MatchCondition": {
+      "description": "MatchCondition represents a condition which must by fulfilled for a request to be sent to a webhook.",
+      "properties": {
+        "expression": {
+          "description": "Expression represents the expression which will be evaluated by CEL. Must evaluate to bool. CEL expressions have access to the contents of the AdmissionRequest and Authorizer, organized into CEL variables:\n\n'object' - The object from the incoming request. The value is null for DELETE requests. 'oldObject' - The existing object. The value is null for CREATE requests. 'request' - Attributes of the admission request(/pkg/apis/admission/types.go#AdmissionRequest). 'authorizer' - A CEL Authorizer. May be used to perform authorization checks for the principal (user or service account) of the request.\n  See https://pkg.go.dev/k8s.io/apiserver/pkg/cel/library#Authz\n'authorizer.requestResource' - A CEL ResourceCheck constructed from the 'authorizer' and configured with the\n  request resource.\nDocumentation on CEL: https://kubernetes.io/docs/reference/using-api/cel/\n\nRequired.",
+          "type": "string"
+        },
+        "name": {
+          "description": "Name is an identifier for this match condition, used for strategic merging of MatchConditions, as well as providing an identifier for logging purposes. A good name should be descriptive of the associated expression. Name must be a qualified name consisting of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyName',  or 'my.name',  or '123-abc', regex used for validation is '([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]') with an optional DNS subdomain prefix and '/' (e.g. 'example.com/MyName')\n\nRequired.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "name",
+        "expression"
+      ],
+      "type": "object"
+    },
     "io.k8s.api.admissionregistration.v1.MutatingWebhook": {
       "description": "MutatingWebhook describes an admission webhook and the resources and operations it applies to.",
       "properties": {
@@ -18,6 +36,19 @@
           "description": "FailurePolicy defines how unrecognized errors from the admission endpoint are handled - allowed values are Ignore or Fail. Defaults to Fail.",
           "type": "string"
         },
+        "matchConditions": {
+          "description": "MatchConditions is a list of conditions that must be met for a request to be sent to this webhook. Match conditions filter requests that have already been matched by the rules, namespaceSelector, and objectSelector. An empty list of matchConditions matches all requests. There are a maximum of 64 match conditions allowed.\n\nThe exact matching logic is (in order):\n  1. If ANY matchCondition evaluates to FALSE, the webhook is skipped.\n  2. If ALL matchConditions evaluate to TRUE, the webhook is called.\n  3. If any matchCondition evaluates to an error (but none are FALSE):\n     - If failurePolicy=Fail, reject the request\n     - If failurePolicy=Ignore, the error is ignored and the webhook is skipped\n\nThis is an alpha feature and managed by the AdmissionWebhookMatchConditions feature gate.",
+          "items": {
+            "$ref": "#/definitions/io.k8s.api.admissionregistration.v1.MatchCondition"
+          },
+          "type": "array",
+          "x-kubernetes-list-map-keys": [
+            "name"
+          ],
+          "x-kubernetes-list-type": "map",
+          "x-kubernetes-patch-merge-key": "name",
+          "x-kubernetes-patch-strategy": "merge"
+        },
         "matchPolicy": {
           "description": "matchPolicy defines how the \"rules\" list is used to match incoming requests. Allowed values are \"Exact\" or \"Equivalent\".\n\n- 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 \"rules\" only included `apiGroups:[\"apps\"], apiVersions:[\"v1\"], resources: [\"deployments\"]`, a request to apps/v1beta1 or extensions/v1beta1 would not be sent to the webhook.\n\n- 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 \"rules\" only included `apiGroups:[\"apps\"], apiVersions:[\"v1\"], resources: [\"deployments\"]`, a request to apps/v1beta1 or extensions/v1beta1 would be converted to apps/v1 and sent to the webhook.\n\nDefaults to \"Equivalent\"",
           "type": "string"
@@ -219,6 +250,19 @@
           "description": "FailurePolicy defines how unrecognized errors from the admission endpoint are handled - allowed values are Ignore or Fail. Defaults to Fail.",
           "type": "string"
         },
+        "matchConditions": {
+          "description": "MatchConditions is a list of conditions that must be met for a request to be sent to this webhook. Match conditions filter requests that have already been matched by the rules, namespaceSelector, and objectSelector. An empty list of matchConditions matches all requests. There are a maximum of 64 match conditions allowed.\n\nThe exact matching logic is (in order):\n  1. If ANY matchCondition evaluates to FALSE, the webhook is skipped.\n  2. If ALL matchConditions evaluate to TRUE, the webhook is called.\n  3. If any matchCondition evaluates to an error (but none are FALSE):\n     - If failurePolicy=Fail, reject the request\n     - If failurePolicy=Ignore, the error is ignored and the webhook is skipped\n\nThis is an alpha feature and managed by the AdmissionWebhookMatchConditions feature gate.",
+          "items": {
+            "$ref": "#/definitions/io.k8s.api.admissionregistration.v1.MatchCondition"
+          },
+          "type": "array",
+          "x-kubernetes-list-map-keys": [
+            "name"
+          ],
+          "x-kubernetes-list-type": "map",
+          "x-kubernetes-patch-merge-key": "name",
+          "x-kubernetes-patch-strategy": "merge"
+        },
         "matchPolicy": {
           "description": "matchPolicy defines how the \"rules\" list is used to match incoming requests. Allowed values are \"Exact\" or \"Equivalent\".\n\n- 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 \"rules\" only included `apiGroups:[\"apps\"], apiVersions:[\"v1\"], resources: [\"deployments\"]`, a request to apps/v1beta1 or extensions/v1beta1 would not be sent to the webhook.\n\n- 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 \"rules\" only included `apiGroups:[\"apps\"], apiVersions:[\"v1\"], resources: [\"deployments\"]`, a request to apps/v1beta1 or extensions/v1beta1 would be converted to apps/v1 and sent to the webhook.\n\nDefaults to \"Equivalent\"",
           "type": "string"
@@ -348,6 +392,59 @@
       },
       "type": "object"
     },
+    "io.k8s.api.admissionregistration.v1alpha1.AuditAnnotation": {
+      "description": "AuditAnnotation describes how to produce an audit annotation for an API request.",
+      "properties": {
+        "key": {
+          "description": "key specifies the audit annotation key. The audit annotation keys of a ValidatingAdmissionPolicy must be unique. The key must be a qualified name ([A-Za-z0-9][-A-Za-z0-9_.]*) no more than 63 bytes in length.\n\nThe key is combined with the resource name of the ValidatingAdmissionPolicy to construct an audit annotation key: \"{ValidatingAdmissionPolicy name}/{key}\".\n\nIf an admission webhook uses the same resource name as this ValidatingAdmissionPolicy and the same audit annotation key, the annotation key will be identical. In this case, the first annotation written with the key will be included in the audit event and all subsequent annotations with the same key will be discarded.\n\nRequired.",
+          "type": "string"
+        },
+        "valueExpression": {
+          "description": "valueExpression represents the expression which is evaluated by CEL to produce an audit annotation value. The expression must evaluate to either a string or null value. If the expression evaluates to a string, the audit annotation is included with the string value. If the expression evaluates to null or empty string the audit annotation will be omitted. The valueExpression may be no longer than 5kb in length. If the result of the valueExpression is more than 10kb in length, it will be truncated to 10kb.\n\nIf multiple ValidatingAdmissionPolicyBinding resources match an API request, then the valueExpression will be evaluated for each binding. All unique values produced by the valueExpressions will be joined together in a comma-separated list.\n\nRequired.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "key",
+        "valueExpression"
+      ],
+      "type": "object"
+    },
+    "io.k8s.api.admissionregistration.v1alpha1.ExpressionWarning": {
+      "description": "ExpressionWarning is a warning information that targets a specific expression.",
+      "properties": {
+        "fieldRef": {
+          "description": "The path to the field that refers the expression. For example, the reference to the expression of the first item of validations is \"spec.validations[0].expression\"",
+          "type": "string"
+        },
+        "warning": {
+          "description": "The content of type checking information in a human-readable form. Each line of the warning contains the type that the expression is checked against, followed by the type check error from the compiler.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "fieldRef",
+        "warning"
+      ],
+      "type": "object"
+    },
+    "io.k8s.api.admissionregistration.v1alpha1.MatchCondition": {
+      "properties": {
+        "expression": {
+          "description": "Expression represents the expression which will be evaluated by CEL. Must evaluate to bool. CEL expressions have access to the contents of the AdmissionRequest and Authorizer, organized into CEL variables:\n\n'object' - The object from the incoming request. The value is null for DELETE requests. 'oldObject' - The existing object. The value is null for CREATE requests. 'request' - Attributes of the admission request(/pkg/apis/admission/types.go#AdmissionRequest). 'authorizer' - A CEL Authorizer. May be used to perform authorization checks for the principal (user or service account) of the request.\n  See https://pkg.go.dev/k8s.io/apiserver/pkg/cel/library#Authz\n'authorizer.requestResource' - A CEL ResourceCheck constructed from the 'authorizer' and configured with the\n  request resource.\nDocumentation on CEL: https://kubernetes.io/docs/reference/using-api/cel/\n\nRequired.",
+          "type": "string"
+        },
+        "name": {
+          "description": "Name is an identifier for this match condition, used for strategic merging of MatchConditions, as well as providing an identifier for logging purposes. A good name should be descriptive of the associated expression. Name must be a qualified name consisting of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyName',  or 'my.name',  or '123-abc', regex used for validation is '([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]') with an optional DNS subdomain prefix and '/' (e.g. 'example.com/MyName')\n\nRequired.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "name",
+        "expression"
+      ],
+      "type": "object"
+    },
     "io.k8s.api.admissionregistration.v1alpha1.MatchResources": {
       "description": "MatchResources decides whether to run the admission control policy on an object based on whether it meets the match criteria. The exclude rules take precedence over include rules (if a resource matches both, it is excluded)",
       "properties": {
@@ -464,6 +561,20 @@
       "type": "object",
       "x-kubernetes-map-type": "atomic"
     },
+    "io.k8s.api.admissionregistration.v1alpha1.TypeChecking": {
+      "description": "TypeChecking contains results of type checking the expressions in the ValidatingAdmissionPolicy",
+      "properties": {
+        "expressionWarnings": {
+          "description": "The type checking warnings for each expression.",
+          "items": {
+            "$ref": "#/definitions/io.k8s.api.admissionregistration.v1alpha1.ExpressionWarning"
+          },
+          "type": "array",
+          "x-kubernetes-list-type": "atomic"
+        }
+      },
+      "type": "object"
+    },
     "io.k8s.api.admissionregistration.v1alpha1.ValidatingAdmissionPolicy": {
       "description": "ValidatingAdmissionPolicy describes the definition of an admission validation policy that accepts or rejects an object without changing it.",
       "properties": {
@@ -482,6 +593,10 @@
         "spec": {
           "$ref": "#/definitions/io.k8s.api.admissionregistration.v1alpha1.ValidatingAdmissionPolicySpec",
           "description": "Specification of the desired behavior of the ValidatingAdmissionPolicy."
+        },
+        "status": {
+          "$ref": "#/definitions/io.k8s.api.admissionregistration.v1alpha1.ValidatingAdmissionPolicyStatus",
+          "description": "The status of the ValidatingAdmissionPolicy, including warnings that are useful to determine if the policy behaves in the expected way. Populated by the system. Read-only."
         }
       },
       "type": "object",
@@ -568,6 +683,14 @@
         "policyName": {
           "description": "PolicyName references a ValidatingAdmissionPolicy name which the ValidatingAdmissionPolicyBinding binds to. If the referenced resource does not exist, this binding is considered invalid and will be ignored Required.",
           "type": "string"
+        },
+        "validationActions": {
+          "description": "validationActions declares how Validations of the referenced ValidatingAdmissionPolicy are enforced. If a validation evaluates to false it is always enforced according to these actions.\n\nFailures defined by the ValidatingAdmissionPolicy's FailurePolicy are enforced according to these actions only if the FailurePolicy is set to Fail, otherwise the failures are ignored. This includes compilation errors, runtime errors and misconfigurations of the policy.\n\nvalidationActions is declared as a set of action values. Order does not matter. validationActions may not contain duplicates of the same action.\n\nThe supported actions values are:\n\n\"Deny\" specifies that a validation failure results in a denied request.\n\n\"Warn\" specifies that a validation failure is reported to the request client in HTTP Warning headers, with a warning code of 299. Warnings can be sent both for allowed or denied admission responses.\n\n\"Audit\" specifies that a validation failure is included in the published audit event for the request. The audit event will contain a `validation.policy.admission.k8s.io/validation_failure` audit annotation with a value containing the details of the validation failures, formatted as a JSON list of objects, each with the following fields: - message: The validation failure message string - policy: The resource name of the ValidatingAdmissionPolicy - binding: The resource name of the ValidatingAdmissionPolicyBinding - expressionIndex: The index of the failed validations in the ValidatingAdmissionPolicy - validationActions: The enforcement actions enacted for the validation failure Example audit annotation: `\"validation.policy.admission.k8s.io/validation_failure\": \"[{\"message\": \"Invalid value\", {\"policy\": \"policy.example.com\", {\"binding\": \"policybinding.example.com\", {\"expressionIndex\": \"1\", {\"validationActions\": [\"Audit\"]}]\"`\n\nClients should expect to handle additional values by ignoring any values not recognized.\n\n\"Deny\" and \"Warn\" may not be used together since this combination needlessly duplicates the validation failure both in the API response body and the HTTP warning headers.\n\nRequired.",
+          "items": {
+            "type": "string"
+          },
+          "type": "array",
+          "x-kubernetes-list-type": "set"
         }
       },
       "type": "object"
@@ -607,10 +730,31 @@
     "io.k8s.api.admissionregistration.v1alpha1.ValidatingAdmissionPolicySpec": {
       "description": "ValidatingAdmissionPolicySpec is the specification of the desired behavior of the AdmissionPolicy.",
       "properties": {
+        "auditAnnotations": {
+          "description": "auditAnnotations contains CEL expressions which are used to produce audit annotations for the audit event of the API request. validations and auditAnnotations may not both be empty; a least one of validations or auditAnnotations is required.",
+          "items": {
+            "$ref": "#/definitions/io.k8s.api.admissionregistration.v1alpha1.AuditAnnotation"
+          },
+          "type": "array",
+          "x-kubernetes-list-type": "atomic"
+        },
         "failurePolicy": {
-          "description": "FailurePolicy defines how to handle failures for the admission policy. Failures can occur from invalid or mis-configured policy definitions or bindings. A policy is invalid if spec.paramKind refers to a non-existent Kind. A binding is invalid if spec.paramRef.name refers to a non-existent resource. Allowed values are Ignore or Fail. Defaults to Fail.",
+          "description": "failurePolicy defines how to handle failures for the admission policy. Failures can occur from CEL expression parse errors, type check errors, runtime errors and invalid or mis-configured policy definitions or bindings.\n\nA policy is invalid if spec.paramKind refers to a non-existent Kind. A binding is invalid if spec.paramRef.name refers to a non-existent resource.\n\nfailurePolicy does not define how validations that evaluate to false are handled.\n\nWhen failurePolicy is set to Fail, ValidatingAdmissionPolicyBinding validationActions define how failures are enforced.\n\nAllowed values are Ignore or Fail. Defaults to Fail.",
           "type": "string"
         },
+        "matchConditions": {
+          "description": "MatchConditions is a list of conditions that must be met for a request to be validated. Match conditions filter requests that have already been matched by the rules, namespaceSelector, and objectSelector. An empty list of matchConditions matches all requests. There are a maximum of 64 match conditions allowed.\n\nIf a parameter object is provided, it can be accessed via the `params` handle in the same manner as validation expressions.\n\nThe exact matching logic is (in order):\n  1. If ANY matchCondition evaluates to FALSE, the policy is skipped.\n  2. If ALL matchConditions evaluate to TRUE, the policy is evaluated.\n  3. If any matchCondition evaluates to an error (but none are FALSE):\n     - If failurePolicy=Fail, reject the request\n     - If failurePolicy=Ignore, the policy is skipped",
+          "items": {
+            "$ref": "#/definitions/io.k8s.api.admissionregistration.v1alpha1.MatchCondition"
+          },
+          "type": "array",
+          "x-kubernetes-list-map-keys": [
+            "name"
+          ],
+          "x-kubernetes-list-type": "map",
+          "x-kubernetes-patch-merge-key": "name",
+          "x-kubernetes-patch-strategy": "merge"
+        },
         "matchConstraints": {
           "$ref": "#/definitions/io.k8s.api.admissionregistration.v1alpha1.MatchResources",
           "description": "MatchConstraints specifies what resources this policy is designed to validate. The AdmissionPolicy cares about a request if it matches _all_ Constraints. However, in order to prevent clusters from being put into an unstable state that cannot be recovered from via the API ValidatingAdmissionPolicy cannot match ValidatingAdmissionPolicy and ValidatingAdmissionPolicyBinding. Required."
@@ -620,7 +764,7 @@
           "description": "ParamKind specifies the kind of resources used to parameterize this policy. If absent, there are no parameters for this policy and the param CEL variable will not be provided to validation expressions. If ParamKind refers to a non-existent kind, this policy definition is mis-configured and the FailurePolicy is applied. If paramKind is specified but paramRef is unset in ValidatingAdmissionPolicyBinding, the params variable will be null."
         },
         "validations": {
-          "description": "Validations contain CEL expressions which is used to apply the validation. A minimum of one validation is required for a policy definition. Required.",
+          "description": "Validations contain CEL expressions which is used to apply the validation. Validations and AuditAnnotations may not both be empty; a minimum of one Validations or AuditAnnotations is required.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.admissionregistration.v1alpha1.Validation"
           },
@@ -628,22 +772,49 @@
           "x-kubernetes-list-type": "atomic"
         }
       },
-      "required": [
-        "validations"
-      ],
+      "type": "object"
+    },
+    "io.k8s.api.admissionregistration.v1alpha1.ValidatingAdmissionPolicyStatus": {
+      "description": "ValidatingAdmissionPolicyStatus represents the status of a ValidatingAdmissionPolicy.",
+      "properties": {
+        "conditions": {
+          "description": "The conditions represent the latest available observations of a policy's current state.",
+          "items": {
+            "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Condition"
+          },
+          "type": "array",
+          "x-kubernetes-list-map-keys": [
+            "type"
+          ],
+          "x-kubernetes-list-type": "map"
+        },
+        "observedGeneration": {
+          "description": "The generation observed by the controller.",
+          "format": "int64",
+          "type": "integer"
+        },
+        "typeChecking": {
+          "$ref": "#/definitions/io.k8s.api.admissionregistration.v1alpha1.TypeChecking",
+          "description": "The results of type checking for each expression. Presence of this field indicates the completion of the type checking."
+        }
+      },
       "type": "object"
     },
     "io.k8s.api.admissionregistration.v1alpha1.Validation": {
       "description": "Validation specifies the CEL expression which is used to apply the validation.",
       "properties": {
         "expression": {
-          "description": "Expression represents the expression which will be evaluated by CEL. ref: https://github.com/google/cel-spec CEL expressions have access to the contents of the Admission request/response, organized into CEL variables as well as some other useful variables:\n\n'object' - The object from the incoming request. The value is null for DELETE requests. 'oldObject' - The existing object. The value is null for CREATE requests. 'request' - Attributes of the admission request([ref](/pkg/apis/admission/types.go#AdmissionRequest)). 'params' - Parameter resource referred to by the policy binding being evaluated. Only populated if the policy has a ParamKind.\n\nThe `apiVersion`, `kind`, `metadata.name` and `metadata.generateName` are always accessible from the root of the object. No other metadata properties are accessible.\n\nOnly 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: - '__' escapes to '__underscores__' - '.' escapes to '__dot__' - '-' escapes to '__dash__' - '/' escapes to '__slash__' - Property names that exactly match a CEL RESERVED keyword escape to '__{keyword}__'. The keywords are:\n\t  \"true\", \"false\", \"null\", \"in\", \"as\", \"break\", \"const\", \"continue\", \"else\", \"for\", \"function\", \"if\",\n\t  \"import\", \"let\", \"loop\", \"package\", \"namespace\", \"return\".\nExamples:\n  - Expression accessing a property named \"namespace\": {\"Expression\": \"object.__namespace__ > 0\"}\n  - Expression accessing a property named \"x-prop\": {\"Expression\": \"object.x__dash__prop > 0\"}\n  - Expression accessing a property named \"redact__d\": {\"Expression\": \"object.redact__underscores__d > 0\"}\n\nEquality on arrays with 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:\n  - 'set': `X + Y` performs a union where the array positions of all elements in `X` are preserved and\n    non-intersecting elements in `Y` are appended, retaining their partial order.\n  - 'map': `X + Y` performs a merge where the array positions of all keys in `X` are preserved but the values\n    are overwritten by values in `Y` when the key sets of `X` and `Y` intersect. Elements in `Y` with\n    non-intersecting keys are appended, retaining their partial order.\nRequired.",
+          "description": "Expression represents the expression which will be evaluated by CEL. ref: https://github.com/google/cel-spec CEL expressions have access to the contents of the API request/response, organized into CEL variables as well as some other useful variables:\n\n- 'object' - The object from the incoming request. The value is null for DELETE requests. - 'oldObject' - The existing object. The value is null for CREATE requests. - 'request' - Attributes of the API request([ref](/pkg/apis/admission/types.go#AdmissionRequest)). - 'params' - Parameter resource referred to by the policy binding being evaluated. Only populated if the policy has a ParamKind. - 'authorizer' - A CEL Authorizer. May be used to perform authorization checks for the principal (user or service account) of the request.\n  See https://pkg.go.dev/k8s.io/apiserver/pkg/cel/library#Authz\n- 'authorizer.requestResource' - A CEL ResourceCheck constructed from the 'authorizer' and configured with the\n  request resource.\n\nThe `apiVersion`, `kind`, `metadata.name` and `metadata.generateName` are always accessible from the root of the object. No other metadata properties are accessible.\n\nOnly 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: - '__' escapes to '__underscores__' - '.' escapes to '__dot__' - '-' escapes to '__dash__' - '/' escapes to '__slash__' - Property names that exactly match a CEL RESERVED keyword escape to '__{keyword}__'. The keywords are:\n\t  \"true\", \"false\", \"null\", \"in\", \"as\", \"break\", \"const\", \"continue\", \"else\", \"for\", \"function\", \"if\",\n\t  \"import\", \"let\", \"loop\", \"package\", \"namespace\", \"return\".\nExamples:\n  - Expression accessing a property named \"namespace\": {\"Expression\": \"object.__namespace__ > 0\"}\n  - Expression accessing a property named \"x-prop\": {\"Expression\": \"object.x__dash__prop > 0\"}\n  - Expression accessing a property named \"redact__d\": {\"Expression\": \"object.redact__underscores__d > 0\"}\n\nEquality on arrays with 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:\n  - 'set': `X + Y` performs a union where the array positions of all elements in `X` are preserved and\n    non-intersecting elements in `Y` are appended, retaining their partial order.\n  - 'map': `X + Y` performs a merge where the array positions of all keys in `X` are preserved but the values\n    are overwritten by values in `Y` when the key sets of `X` and `Y` intersect. Elements in `Y` with\n    non-intersecting keys are appended, retaining their partial order.\nRequired.",
           "type": "string"
         },
         "message": {
           "description": "Message represents the message displayed when validation fails. The message is required if the Expression contains line breaks. The message must not contain line breaks. If unset, the message is \"failed rule: {Rule}\". e.g. \"must be a URL with the host matching spec.host\" If the Expression contains line breaks. Message is required. The message must not contain line breaks. If unset, the message is \"failed Expression: {Expression}\".",
           "type": "string"
         },
+        "messageExpression": {
+          "description": "messageExpression declares a CEL expression that evaluates to the validation failure message that is returned when this rule fails. Since messageExpression is used as a failure message, it must evaluate to a string. If both message and messageExpression are present on a validation, then messageExpression will be used if validation fails. If messageExpression results in a runtime error, the runtime error is logged, and the validation failure message is produced as if the messageExpression field were unset. If messageExpression evaluates to an empty string, a string with only spaces, or a string that contains line breaks, then the validation failure message will also be produced as if the messageExpression field were unset, and the fact that messageExpression produced an empty string/string with only spaces/string with line breaks will be logged. messageExpression has access to all the same variables as the `expression` except for 'authorizer' and 'authorizer.requestResource'. Example: \"object.x must be less than max (\"+string(params.max)+\")\"",
+          "type": "string"
+        },
         "reason": {
           "description": "Reason represents a machine-readable description of why this validation failed. If this is the first validation in the list to fail, this reason, as well as the corresponding HTTP response code, are used in the HTTP response to the client. The currently supported reasons are: \"Unauthorized\", \"Forbidden\", \"Invalid\", \"RequestEntityTooLarge\". If not set, StatusReasonInvalid is used in the response to the client.",
           "type": "string"
@@ -1009,7 +1180,7 @@
         },
         "template": {
           "$ref": "#/definitions/io.k8s.api.core.v1.PodTemplateSpec",
-          "description": "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'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"
+          "description": "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's node selector (or on every node if no node selector is specified). The only allowed template.spec.restartPolicy value is \"Always\". More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template"
         },
         "updateStrategy": {
           "$ref": "#/definitions/io.k8s.api.apps.v1.DaemonSetUpdateStrategy",
@@ -1096,7 +1267,7 @@
           "description": "Rolling update config params. Present only if type = \"RollingUpdate\"."
         },
         "type": {
-          "description": "Type of daemon set update. Can be \"RollingUpdate\" or \"OnDelete\". Default is RollingUpdate.\n\n",
+          "description": "Type of daemon set update. Can be \"RollingUpdate\" or \"OnDelete\". Default is RollingUpdate.",
           "type": "string"
         }
       },
@@ -1242,7 +1413,7 @@
         },
         "template": {
           "$ref": "#/definitions/io.k8s.api.core.v1.PodTemplateSpec",
-          "description": "Template describes the pods that will be created."
+          "description": "Template describes the pods that will be created. The only allowed template.spec.restartPolicy value is \"Always\"."
         }
       },
       "required": [
@@ -1309,7 +1480,7 @@
           "description": "Rolling update config params. Present only if DeploymentStrategyType = RollingUpdate."
         },
         "type": {
-          "description": "Type of deployment. Can be \"Recreate\" or \"RollingUpdate\". Default is RollingUpdate.\n\n",
+          "description": "Type of deployment. Can be \"Recreate\" or \"RollingUpdate\". Default is RollingUpdate.",
           "type": "string"
         }
       },
@@ -1659,14 +1830,14 @@
         },
         "ordinals": {
           "$ref": "#/definitions/io.k8s.api.apps.v1.StatefulSetOrdinals",
-          "description": "ordinals controls the numbering of replica indices in a StatefulSet. The default ordinals behavior assigns a \"0\" index to the first replica and increments the index by one for each additional replica requested. Using the ordinals field requires the StatefulSetStartOrdinal feature gate to be enabled, which is alpha."
+          "description": "ordinals controls the numbering of replica indices in a StatefulSet. The default ordinals behavior assigns a \"0\" index to the first replica and increments the index by one for each additional replica requested. Using the ordinals field requires the StatefulSetStartOrdinal feature gate to be enabled, which is beta."
         },
         "persistentVolumeClaimRetentionPolicy": {
           "$ref": "#/definitions/io.k8s.api.apps.v1.StatefulSetPersistentVolumeClaimRetentionPolicy",
           "description": "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"
         },
         "podManagementPolicy": {
-          "description": "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.\n\n",
+          "description": "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.",
           "type": "string"
         },
         "replicas": {
@@ -1689,7 +1860,7 @@
         },
         "template": {
           "$ref": "#/definitions/io.k8s.api.core.v1.PodTemplateSpec",
-          "description": "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. Each pod will be named with the format <statefulsetname>-<podindex>. For example, a pod in a StatefulSet named \"web\" with index number \"3\" would be named \"web-3\"."
+          "description": "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. Each pod will be named with the format <statefulsetname>-<podindex>. For example, a pod in a StatefulSet named \"web\" with index number \"3\" would be named \"web-3\". The only allowed template.spec.restartPolicy value is \"Always\"."
         },
         "updateStrategy": {
           "$ref": "#/definitions/io.k8s.api.apps.v1.StatefulSetUpdateStrategy",
@@ -1779,7 +1950,7 @@
           "description": "RollingUpdate is used to communicate parameters when Type is RollingUpdateStatefulSetStrategyType."
         },
         "type": {
-          "description": "Type indicates the type of the StatefulSetUpdateStrategy. Default is RollingUpdate.\n\n",
+          "description": "Type indicates the type of the StatefulSetUpdateStrategy. Default is RollingUpdate.",
           "type": "string"
         }
       },
@@ -1996,7 +2167,7 @@
       "type": "object"
     },
     "io.k8s.api.authentication.v1alpha1.SelfSubjectReview": {
-      "description": "SelfSubjectReview contains the user information that the kube-apiserver has about the user making this request. When using impersonation, users will receive the user info of the user being impersonated.",
+      "description": "SelfSubjectReview contains the user information that the kube-apiserver has about the user making this request. When using impersonation, users will receive the user info of the user being impersonated.  If impersonation or request header authentication is used, any extra keys will have their case ignored and returned as lowercase.",
       "properties": {
         "apiVersion": {
           "description": "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",
@@ -2034,6 +2205,45 @@
       },
       "type": "object"
     },
+    "io.k8s.api.authentication.v1beta1.SelfSubjectReview": {
+      "description": "SelfSubjectReview contains the user information that the kube-apiserver has about the user making this request. When using impersonation, users will receive the user info of the user being impersonated.  If impersonation or request header authentication is used, any extra keys will have their case ignored and returned as lowercase.",
+      "properties": {
+        "apiVersion": {
+          "description": "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",
+          "type": "string"
+        },
+        "kind": {
+          "description": "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",
+          "type": "string"
+        },
+        "metadata": {
+          "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta",
+          "description": "Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata"
+        },
+        "status": {
+          "$ref": "#/definitions/io.k8s.api.authentication.v1beta1.SelfSubjectReviewStatus",
+          "description": "Status is filled in by the server with the user attributes."
+        }
+      },
+      "type": "object",
+      "x-kubernetes-group-version-kind": [
+        {
+          "group": "authentication.k8s.io",
+          "kind": "SelfSubjectReview",
+          "version": "v1beta1"
+        }
+      ]
+    },
+    "io.k8s.api.authentication.v1beta1.SelfSubjectReviewStatus": {
+      "description": "SelfSubjectReviewStatus is filled by the kube-apiserver and sent back to a user.",
+      "properties": {
+        "userInfo": {
+          "$ref": "#/definitions/io.k8s.api.authentication.v1.UserInfo",
+          "description": "User attributes of the user making this request."
+        }
+      },
+      "type": "object"
+    },
     "io.k8s.api.authorization.v1.LocalSubjectAccessReview": {
       "description": "LocalSubjectAccessReview checks whether or not a user or group can perform an action in a given namespace. Having a namespace scoped resource makes it much easier to grant namespace scoped policy that includes permissions checking.",
       "properties": {
@@ -2411,15 +2621,15 @@
       "description": "CrossVersionObjectReference contains enough information to let you identify the referred resource.",
       "properties": {
         "apiVersion": {
-          "description": "API version of the referent",
+          "description": "apiVersion is the API version of the referent",
           "type": "string"
         },
         "kind": {
-          "description": "Kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds",
+          "description": "kind is the kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds",
           "type": "string"
         },
         "name": {
-          "description": "Name of the referent; More info: http://kubernetes.io/docs/user-guide/identifiers#names",
+          "description": "name is the name of the referent; More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names",
           "type": "string"
         }
       },
@@ -2447,11 +2657,11 @@
         },
         "spec": {
           "$ref": "#/definitions/io.k8s.api.autoscaling.v1.HorizontalPodAutoscalerSpec",
-          "description": "behaviour of autoscaler. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status."
+          "description": "spec defines the behaviour of autoscaler. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status."
         },
         "status": {
           "$ref": "#/definitions/io.k8s.api.autoscaling.v1.HorizontalPodAutoscalerStatus",
-          "description": "current information about the autoscaler."
+          "description": "status is the current information about the autoscaler."
         }
       },
       "type": "object",
@@ -2471,7 +2681,7 @@
           "type": "string"
         },
         "items": {
-          "description": "list of horizontal pod autoscaler objects.",
+          "description": "items is the list of horizontal pod autoscaler objects.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.autoscaling.v1.HorizontalPodAutoscaler"
           },
@@ -2502,7 +2712,7 @@
       "description": "specification of a horizontal pod autoscaler.",
       "properties": {
         "maxReplicas": {
-          "description": "upper limit for the number of pods that can be set by the autoscaler; cannot be smaller than MinReplicas.",
+          "description": "maxReplicas is the upper limit for the number of pods that can be set by the autoscaler; cannot be smaller than MinReplicas.",
           "format": "int32",
           "type": "integer"
         },
@@ -2516,7 +2726,7 @@
           "description": "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."
         },
         "targetCPUUtilizationPercentage": {
-          "description": "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.",
+          "description": "targetCPUUtilizationPercentage is the 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.",
           "format": "int32",
           "type": "integer"
         }
@@ -2531,26 +2741,26 @@
       "description": "current status of a horizontal pod autoscaler",
       "properties": {
         "currentCPUUtilizationPercentage": {
-          "description": "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.",
+          "description": "currentCPUUtilizationPercentage is the 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.",
           "format": "int32",
           "type": "integer"
         },
         "currentReplicas": {
-          "description": "current number of replicas of pods managed by this autoscaler.",
+          "description": "currentReplicas is the current number of replicas of pods managed by this autoscaler.",
           "format": "int32",
           "type": "integer"
         },
         "desiredReplicas": {
-          "description": "desired number of replicas of pods managed by this autoscaler.",
+          "description": "desiredReplicas is the  desired number of replicas of pods managed by this autoscaler.",
           "format": "int32",
           "type": "integer"
         },
         "lastScaleTime": {
           "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time",
-          "description": "last time the HorizontalPodAutoscaler scaled the number of pods; used by the autoscaler to control how often the number of pods is changed."
+          "description": "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."
         },
         "observedGeneration": {
-          "description": "most recent generation observed by this autoscaler.",
+          "description": "observedGeneration is the most recent generation observed by this autoscaler.",
           "format": "int64",
           "type": "integer"
         }
@@ -2578,11 +2788,11 @@
         },
         "spec": {
           "$ref": "#/definitions/io.k8s.api.autoscaling.v1.ScaleSpec",
-          "description": "defines the behavior of the scale. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status."
+          "description": "spec defines the behavior of the scale. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status."
         },
         "status": {
           "$ref": "#/definitions/io.k8s.api.autoscaling.v1.ScaleStatus",
-          "description": "current status of the scale. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status. Read-only."
+          "description": "status is the current status of the scale. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status. Read-only."
         }
       },
       "type": "object",
@@ -2598,7 +2808,7 @@
       "description": "ScaleSpec describes the attributes of a scale subresource.",
       "properties": {
         "replicas": {
-          "description": "desired number of instances for the scaled object.",
+          "description": "replicas is the desired number of instances for the scaled object.",
           "format": "int32",
           "type": "integer"
         }
@@ -2609,12 +2819,12 @@
       "description": "ScaleStatus represents the current status of a scale subresource.",
       "properties": {
         "replicas": {
-          "description": "actual number of observed instances of the scaled object.",
+          "description": "replicas is the actual number of observed instances of the scaled object.",
           "format": "int32",
           "type": "integer"
         },
         "selector": {
-          "description": "label query over pods that should match the replicas count. This is same as the label selector but in the string format to avoid introspection by clients. The string will be in the same format as the query-param syntax. More info about label selectors: http://kubernetes.io/docs/user-guide/labels#label-selectors",
+          "description": "selector is the label query over pods that should match the replicas count. This is same as the label selector but in the string format to avoid introspection by clients. The string will be in the same format as the query-param syntax. More info about label selectors: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/",
           "type": "string"
         }
       },
@@ -2650,7 +2860,7 @@
       "description": "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 \"pods\" source.",
       "properties": {
         "container": {
-          "description": "Container is the name of the container in the pods of the scaling target",
+          "description": "container is the name of the container in the pods of the scaling target",
           "type": "string"
         },
         "current": {
@@ -2658,7 +2868,7 @@
           "description": "current contains the current value for the given metric"
         },
         "name": {
-          "description": "Name is the name of the resource in question.",
+          "description": "name is the name of the resource in question.",
           "type": "string"
         }
       },
@@ -2673,15 +2883,15 @@
       "description": "CrossVersionObjectReference contains enough information to let you identify the referred resource.",
       "properties": {
         "apiVersion": {
-          "description": "API version of the referent",
+          "description": "apiVersion is the API version of the referent",
           "type": "string"
         },
         "kind": {
-          "description": "Kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds",
+          "description": "kind is the kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds",
           "type": "string"
         },
         "name": {
-          "description": "Name of the referent; More info: http://kubernetes.io/docs/user-guide/identifiers#names",
+          "description": "name is the name of the referent; More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names",
           "type": "string"
         }
       },
@@ -2731,16 +2941,16 @@
       "description": "HPAScalingPolicy is a single policy which must hold true for a specified past interval.",
       "properties": {
         "periodSeconds": {
-          "description": "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).",
+          "description": "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).",
           "format": "int32",
           "type": "integer"
         },
         "type": {
-          "description": "Type is used to specify the scaling policy.",
+          "description": "type is used to specify the scaling policy.",
           "type": "string"
         },
         "value": {
-          "description": "Value contains the amount of change which is permitted by the policy. It must be greater than zero",
+          "description": "value contains the amount of change which is permitted by the policy. It must be greater than zero",
           "format": "int32",
           "type": "integer"
         }
@@ -2768,7 +2978,7 @@
           "type": "string"
         },
         "stabilizationWindowSeconds": {
-          "description": "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).",
+          "description": "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).",
           "format": "int32",
           "type": "integer"
         }
@@ -3208,7 +3418,7 @@
           "description": "current contains the current value for the given metric"
         },
         "name": {
-          "description": "Name is the name of the resource in question.",
+          "description": "name is the name of the resource in question.",
           "type": "string"
         }
       },
@@ -3290,7 +3500,7 @@
       "description": "CronJobSpec describes how the job execution will look like and when it will actually run.",
       "properties": {
         "concurrencyPolicy": {
-          "description": "Specifies how to treat concurrent executions of a Job. Valid values are: - \"Allow\" (default): allows CronJobs to run concurrently; - \"Forbid\": forbids concurrent runs, skipping next run if previous run hasn't finished yet; - \"Replace\": cancels currently running job and replaces it with a new one\n\n",
+          "description": "Specifies how to treat concurrent executions of a Job. Valid values are:\n\n- \"Allow\" (default): allows CronJobs to run concurrently; - \"Forbid\": forbids concurrent runs, skipping next run if previous run hasn't finished yet; - \"Replace\": cancels currently running job and replaces it with a new one",
           "type": "string"
         },
         "failedJobsHistoryLimit": {
@@ -3321,7 +3531,7 @@
           "type": "boolean"
         },
         "timeZone": {
-          "description": "The time zone name for the given schedule, see https://en.wikipedia.org/wiki/List_of_tz_database_time_zones. If not specified, this will default to the time zone of the kube-controller-manager process. The set of valid time zone names and the time zone offset is loaded from the system-wide time zone database by the API server during CronJob validation and the controller manager during execution. If no system-wide time zone database can be found a bundled version of the database is used instead. If the time zone name becomes invalid during the lifetime of a CronJob or due to a change in host configuration, the controller will stop creating new new Jobs and will create a system event with the reason UnknownTimeZone. More information can be found in https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#time-zones This is beta field and must be enabled via the `CronJobTimeZone` feature gate.",
+          "description": "The time zone name for the given schedule, see https://en.wikipedia.org/wiki/List_of_tz_database_time_zones. If not specified, this will default to the time zone of the kube-controller-manager process. The set of valid time zone names and the time zone offset is loaded from the system-wide time zone database by the API server during CronJob validation and the controller manager during execution. If no system-wide time zone database can be found a bundled version of the database is used instead. If the time zone name becomes invalid during the lifetime of a CronJob or due to a change in host configuration, the controller will stop creating new new Jobs and will create a system event with the reason UnknownTimeZone. More information can be found in https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#time-zones",
           "type": "string"
         }
       },
@@ -3469,11 +3679,11 @@
           "type": "integer"
         },
         "completionMode": {
-          "description": "CompletionMode specifies how Pod completions are tracked. It can be `NonIndexed` (default) or `Indexed`.\n\n`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.\n\n`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)`.\n\nMore completion modes can be added in the future. If the Job controller observes a mode that it doesn't recognize, which is possible during upgrades due to version skew, the controller skips updates for the Job.",
+          "description": "completionMode specifies how Pod completions are tracked. It can be `NonIndexed` (default) or `Indexed`.\n\n`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.\n\n`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)`.\n\nMore completion modes can be added in the future. If the Job controller observes a mode that it doesn't recognize, which is possible during upgrades due to version skew, the controller skips updates for the Job.",
           "type": "string"
         },
         "completions": {
-          "description": "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/",
+          "description": "Specifies the desired number of successfully finished pods the job should be run with.  Setting to null 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/",
           "format": "int32",
           "type": "integer"
         },
@@ -3495,12 +3705,12 @@
           "description": "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"
         },
         "suspend": {
-          "description": "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.",
+          "description": "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.",
           "type": "boolean"
         },
         "template": {
           "$ref": "#/definitions/io.k8s.api.core.v1.PodTemplateSpec",
-          "description": "Describes the pod that will be created when executing a job. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/"
+          "description": "Describes the pod that will be created when executing a job. The only allowed template.spec.restartPolicy values are \"Never\" or \"OnFailure\". More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/"
         },
         "ttlSecondsAfterFinished": {
           "description": "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't be automatically deleted. If this field is set to zero, the Job becomes eligible to be deleted immediately after it finishes.",
@@ -3522,7 +3732,7 @@
           "type": "integer"
         },
         "completedIndexes": {
-          "description": "CompletedIndexes holds the completed indexes when .spec.completionMode = \"Indexed\" 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 \"1,3-5,7\".",
+          "description": "completedIndexes holds the completed indexes when .spec.completionMode = \"Indexed\" 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 \"1,3-5,7\".",
           "type": "string"
         },
         "completionTime": {
@@ -3560,7 +3770,7 @@
         },
         "uncountedTerminatedPods": {
           "$ref": "#/definitions/io.k8s.api.batch.v1.UncountedTerminatedPods",
-          "description": "UncountedTerminatedPods holds the UIDs of Pods that have terminated but the job controller hasn't yet accounted for in the status counters.\n\nThe 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\n    counter.\n\nOld jobs might not be tracked using this field, in which case the field remains null."
+          "description": "uncountedTerminatedPods holds the UIDs of Pods that have terminated but the job controller hasn't yet accounted for in the status counters.\n\nThe 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:\n\n1. 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\n    counter.\n\nOld jobs might not be tracked using this field, in which case the field remains null."
         }
       },
       "type": "object"
@@ -3604,7 +3814,7 @@
           "type": "string"
         },
         "operator": {
-          "description": "Represents the relationship between the container exit code(s) and the specified values. Containers completed with success (exit code 0) are excluded from the requirement check. Possible values are: - In: the requirement is satisfied if at least one container exit code\n  (might be multiple if there are multiple containers not restricted\n  by the 'containerName' field) is in the set of specified values.\n- NotIn: the requirement is satisfied if at least one container exit code\n  (might be multiple if there are multiple containers not restricted\n  by the 'containerName' field) is not in the set of specified values.\nAdditional values are considered to be added in the future. Clients should react to an unknown operator by assuming the requirement is not satisfied.\n\n",
+          "description": "Represents the relationship between the container exit code(s) and the specified values. Containers completed with success (exit code 0) are excluded from the requirement check. Possible values are:\n\n- In: the requirement is satisfied if at least one container exit code\n  (might be multiple if there are multiple containers not restricted\n  by the 'containerName' field) is in the set of specified values.\n- NotIn: the requirement is satisfied if at least one container exit code\n  (might be multiple if there are multiple containers not restricted\n  by the 'containerName' field) is not in the set of specified values.\nAdditional values are considered to be added in the future. Clients should react to an unknown operator by assuming the requirement is not satisfied.",
           "type": "string"
         },
         "values": {
@@ -3642,10 +3852,10 @@
       "type": "object"
     },
     "io.k8s.api.batch.v1.PodFailurePolicyRule": {
-      "description": "PodFailurePolicyRule describes how a pod failure is handled when the requirements are met. One of OnExitCodes and onPodConditions, but not both, can be used in each rule.",
+      "description": "PodFailurePolicyRule describes how a pod failure is handled when the requirements are met. One of onExitCodes and onPodConditions, but not both, can be used in each rule.",
       "properties": {
         "action": {
-          "description": "Specifies the action taken on a pod failure when the requirements are satisfied. Possible values are: - FailJob: indicates that the pod's job is marked as Failed and all\n  running pods are terminated.\n- Ignore: indicates that the counter towards the .backoffLimit is not\n  incremented and a replacement pod is created.\n- Count: indicates that the pod is handled in the default way - the\n  counter towards the .backoffLimit is incremented.\nAdditional values are considered to be added in the future. Clients should react to an unknown action by skipping the rule.\n\n",
+          "description": "Specifies the action taken on a pod failure when the requirements are satisfied. Possible values are:\n\n- FailJob: indicates that the pod's job is marked as Failed and all\n  running pods are terminated.\n- Ignore: indicates that the counter towards the .backoffLimit is not\n  incremented and a replacement pod is created.\n- Count: indicates that the pod is handled in the default way - the\n  counter towards the .backoffLimit is incremented.\nAdditional values are considered to be added in the future. Clients should react to an unknown action by skipping the rule.",
           "type": "string"
         },
         "onExitCodes": {
@@ -3671,7 +3881,7 @@
       "description": "UncountedTerminatedPods holds UIDs of Pods that have terminated but haven't been accounted in Job status counters.",
       "properties": {
         "failed": {
-          "description": "Failed holds UIDs of failed Pods.",
+          "description": "failed holds UIDs of failed Pods.",
           "items": {
             "type": "string"
           },
@@ -3679,7 +3889,7 @@
           "x-kubernetes-list-type": "set"
         },
         "succeeded": {
-          "description": "Succeeded holds UIDs of succeeded Pods.",
+          "description": "succeeded holds UIDs of succeeded Pods.",
           "items": {
             "type": "string"
           },
@@ -3874,6 +4084,90 @@
       },
       "type": "object"
     },
+    "io.k8s.api.certificates.v1alpha1.ClusterTrustBundle": {
+      "description": "ClusterTrustBundle is a cluster-scoped container for X.509 trust anchors (root certificates).\n\nClusterTrustBundle objects are considered to be readable by any authenticated user in the cluster, because they can be mounted by pods using the `clusterTrustBundle` projection.  All service accounts have read access to ClusterTrustBundles by default.  Users who only have namespace-level access to a cluster can read ClusterTrustBundles by impersonating a serviceaccount that they have access to.\n\nIt can be optionally associated with a particular assigner, in which case it contains one valid set of trust anchors for that signer. Signers may have multiple associated ClusterTrustBundles; each is an independent set of trust anchors for that signer. Admission control is used to enforce that only users with permissions on the signer can create or modify the corresponding bundle.",
+      "properties": {
+        "apiVersion": {
+          "description": "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",
+          "type": "string"
+        },
+        "kind": {
+          "description": "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",
+          "type": "string"
+        },
+        "metadata": {
+          "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta",
+          "description": "metadata contains the object metadata."
+        },
+        "spec": {
+          "$ref": "#/definitions/io.k8s.api.certificates.v1alpha1.ClusterTrustBundleSpec",
+          "description": "spec contains the signer (if any) and trust anchors."
+        }
+      },
+      "required": [
+        "spec"
+      ],
+      "type": "object",
+      "x-kubernetes-group-version-kind": [
+        {
+          "group": "certificates.k8s.io",
+          "kind": "ClusterTrustBundle",
+          "version": "v1alpha1"
+        }
+      ]
+    },
+    "io.k8s.api.certificates.v1alpha1.ClusterTrustBundleList": {
+      "description": "ClusterTrustBundleList is a collection of ClusterTrustBundle objects",
+      "properties": {
+        "apiVersion": {
+          "description": "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",
+          "type": "string"
+        },
+        "items": {
+          "description": "items is a collection of ClusterTrustBundle objects",
+          "items": {
+            "$ref": "#/definitions/io.k8s.api.certificates.v1alpha1.ClusterTrustBundle"
+          },
+          "type": "array"
+        },
+        "kind": {
+          "description": "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",
+          "type": "string"
+        },
+        "metadata": {
+          "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta",
+          "description": "metadata contains the list metadata."
+        }
+      },
+      "required": [
+        "items"
+      ],
+      "type": "object",
+      "x-kubernetes-group-version-kind": [
+        {
+          "group": "certificates.k8s.io",
+          "kind": "ClusterTrustBundleList",
+          "version": "v1alpha1"
+        }
+      ]
+    },
+    "io.k8s.api.certificates.v1alpha1.ClusterTrustBundleSpec": {
+      "description": "ClusterTrustBundleSpec contains the signer and trust anchors.",
+      "properties": {
+        "signerName": {
+          "description": "signerName indicates the associated signer, if any.\n\nIn order to create or update a ClusterTrustBundle that sets signerName, you must have the following cluster-scoped permission: group=certificates.k8s.io resource=signers resourceName=<the signer name> verb=attest.\n\nIf signerName is not empty, then the ClusterTrustBundle object must be named with the signer name as a prefix (translating slashes to colons). For example, for the signer name `example.com/foo`, valid ClusterTrustBundle object names include `example.com:foo:abc` and `example.com:foo:v1`.\n\nIf signerName is empty, then the ClusterTrustBundle object's name must not have such a prefix.\n\nList/watch requests for ClusterTrustBundles can filter on this field using a `spec.signerName=NAME` field selector.",
+          "type": "string"
+        },
+        "trustBundle": {
+          "description": "trustBundle contains the individual X.509 trust anchors for this bundle, as PEM bundle of PEM-wrapped, DER-formatted X.509 certificates.\n\nThe data must consist only of PEM certificate blocks that parse as valid X.509 certificates.  Each certificate must include a basic constraints extension with the CA bit set.  The API server will reject objects that contain duplicate certificates, or that use PEM block headers.\n\nUsers of ClusterTrustBundles, including Kubelet, are free to reorder and deduplicate certificate blocks in this file according to their own logic, as well as to drop PEM block headers and inter-block data.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "trustBundle"
+      ],
+      "type": "object"
+    },
     "io.k8s.api.coordination.v1.Lease": {
       "description": "Lease defines a lease concept.",
       "properties": {
@@ -3891,7 +4185,7 @@
         },
         "spec": {
           "$ref": "#/definitions/io.k8s.api.coordination.v1.LeaseSpec",
-          "description": "Specification of the Lease. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status"
+          "description": "spec contains the specification of the Lease. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status"
         }
       },
       "type": "object",
@@ -3911,7 +4205,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Items is a list of schema objects.",
+          "description": "items is a list of schema objects.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.coordination.v1.Lease"
           },
@@ -3950,7 +4244,7 @@
           "type": "string"
         },
         "leaseDurationSeconds": {
-          "description": "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.",
+          "description": "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.",
           "format": "int32",
           "type": "integer"
         },
@@ -4147,7 +4441,7 @@
       "properties": {
         "controllerExpandSecretRef": {
           "$ref": "#/definitions/io.k8s.api.core.v1.SecretReference",
-          "description": "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 beta 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."
+          "description": "controllerExpandSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI ControllerExpandVolume call. 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."
         },
         "controllerPublishSecretRef": {
           "$ref": "#/definitions/io.k8s.api.core.v1.SecretReference",
@@ -4163,7 +4457,7 @@
         },
         "nodeExpandSecretRef": {
           "$ref": "#/definitions/io.k8s.api.core.v1.SecretReference",
-          "description": "nodeExpandSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI NodeExpandVolume call. This is an alpha field and requires enabling CSINodeExpandSecret feature gate. This field is optional, may be omitted if no secret is required. If the secret object contains more than one secret, all secrets are passed."
+          "description": "nodeExpandSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI NodeExpandVolume call. This is a beta field which is enabled default by CSINodeExpandSecret feature gate. This field is optional, may be omitted if no secret is required. If the secret object contains more than one secret, all secrets are passed."
         },
         "nodePublishSecretRef": {
           "$ref": "#/definitions/io.k8s.api.core.v1.SecretReference",
@@ -4720,7 +5014,7 @@
           "type": "string"
         },
         "imagePullPolicy": {
-          "description": "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\n\n",
+          "description": "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",
           "type": "string"
         },
         "lifecycle": {
@@ -4753,6 +5047,14 @@
           "$ref": "#/definitions/io.k8s.api.core.v1.Probe",
           "description": "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"
         },
+        "resizePolicy": {
+          "description": "Resources resize policy for the container.",
+          "items": {
+            "$ref": "#/definitions/io.k8s.api.core.v1.ContainerResizePolicy"
+          },
+          "type": "array",
+          "x-kubernetes-list-type": "atomic"
+        },
         "resources": {
           "$ref": "#/definitions/io.k8s.api.core.v1.ResourceRequirements",
           "description": "Compute Resources required by this container. Cannot be updated. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/"
@@ -4778,7 +5080,7 @@
           "type": "string"
         },
         "terminationMessagePolicy": {
-          "description": "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.\n\n",
+          "description": "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.",
           "type": "string"
         },
         "tty": {
@@ -4853,7 +5155,7 @@
           "type": "string"
         },
         "protocol": {
-          "description": "Protocol for port. Must be UDP, TCP, or SCTP. Defaults to \"TCP\".\n\n",
+          "description": "Protocol for port. Must be UDP, TCP, or SCTP. Defaults to \"TCP\".",
           "type": "string"
         }
       },
@@ -4862,6 +5164,24 @@
       ],
       "type": "object"
     },
+    "io.k8s.api.core.v1.ContainerResizePolicy": {
+      "description": "ContainerResizePolicy represents resource resize policy for the container.",
+      "properties": {
+        "resourceName": {
+          "description": "Name of the resource to which this resource resize policy applies. Supported values: cpu, memory.",
+          "type": "string"
+        },
+        "restartPolicy": {
+          "description": "Restart policy to apply when specified resource is resized. If not specified, it defaults to NotRequired.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "resourceName",
+        "restartPolicy"
+      ],
+      "type": "object"
+    },
     "io.k8s.api.core.v1.ContainerState": {
       "description": "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.",
       "properties": {
@@ -4946,42 +5266,53 @@
     "io.k8s.api.core.v1.ContainerStatus": {
       "description": "ContainerStatus contains details for the current status of this container.",
       "properties": {
+        "allocatedResources": {
+          "additionalProperties": {
+            "$ref": "#/definitions/io.k8s.apimachinery.pkg.api.resource.Quantity"
+          },
+          "description": "AllocatedResources represents the compute resources allocated for this container by the node. Kubelet sets this value to Container.Resources.Requests upon successful pod admission and after successfully admitting desired pod resize.",
+          "type": "object"
+        },
         "containerID": {
-          "description": "Container's ID in the format '<type>://<container_id>'.",
+          "description": "ContainerID is the ID of the container in the format '<type>://<container_id>'. Where type is a container runtime identifier, returned from Version call of CRI API (for example \"containerd\").",
           "type": "string"
         },
         "image": {
-          "description": "The image the container is running. More info: https://kubernetes.io/docs/concepts/containers/images.",
+          "description": "Image is the name of container image that the container is running. The container image may not match the image used in the PodSpec, as it may have been resolved by the runtime. More info: https://kubernetes.io/docs/concepts/containers/images.",
           "type": "string"
         },
         "imageID": {
-          "description": "ImageID of the container's image.",
+          "description": "ImageID is the image ID of the container's image. The image ID may not match the image ID of the image used in the PodSpec, as it may have been resolved by the runtime.",
           "type": "string"
         },
         "lastState": {
           "$ref": "#/definitions/io.k8s.api.core.v1.ContainerState",
-          "description": "Details about the container's last termination condition."
+          "description": "LastTerminationState holds the last termination state of the container to help debug container crashes and restarts. This field is not populated if the container is still running and RestartCount is 0."
         },
         "name": {
-          "description": "This must be a DNS_LABEL. Each container in a pod must have a unique name. Cannot be updated.",
+          "description": "Name is a DNS_LABEL representing the unique name of the container. Each container in a pod must have a unique name across all container types. Cannot be updated.",
           "type": "string"
         },
         "ready": {
-          "description": "Specifies whether the container has passed its readiness probe.",
+          "description": "Ready specifies whether the container is currently passing its readiness check. The value will change as readiness probes keep executing. If no readiness probes are specified, this field defaults to true once the container is fully started (see Started field).\n\nThe value is typically used to determine whether a container is ready to accept traffic.",
           "type": "boolean"
         },
+        "resources": {
+          "$ref": "#/definitions/io.k8s.api.core.v1.ResourceRequirements",
+          "description": "Resources represents the compute resource requests and limits that have been successfully enacted on the running container after it has been started or has been successfully resized."
+        },
         "restartCount": {
-          "description": "The number of times the container has been restarted.",
+          "description": "RestartCount holds the number of times the container has been restarted. Kubelet makes an effort to always increment the value, but there are cases when the state may be lost due to node restarts and then the value may be reset to 0. The value is never negative.",
           "format": "int32",
           "type": "integer"
         },
         "started": {
-          "description": "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.",
+          "description": "Started indicates whether the container has finished its postStart lifecycle hook and 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. In both cases, startup probes will run again. Is always true when no startupProbe is defined and container is running and has passed the postStart lifecycle hook. The null value must be treated the same as false.",
           "type": "boolean"
         },
         "state": {
           "$ref": "#/definitions/io.k8s.api.core.v1.ContainerState",
-          "description": "Details about the container's current condition."
+          "description": "State holds details about the container's current condition."
         }
       },
       "required": [
@@ -5073,7 +5404,7 @@
         },
         "sizeLimit": {
           "$ref": "#/definitions/io.k8s.apimachinery.pkg.api.resource.Quantity",
-          "description": "sizeLimit is the 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"
+          "description": "sizeLimit is the 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: https://kubernetes.io/docs/concepts/storage/volumes#emptydir"
         }
       },
       "type": "object"
@@ -5086,7 +5417,7 @@
           "type": "string"
         },
         "ip": {
-          "description": "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.",
+          "description": "The IP of this endpoint. May not be loopback (127.0.0.0/8 or ::1), link-local (169.254.0.0/16 or fe80::/10), or link-local multicast (224.0.0.0/24 or ff02::/16).",
           "type": "string"
         },
         "nodeName": {
@@ -5108,7 +5439,7 @@
       "description": "EndpointPort is a tuple that describes a single port.",
       "properties": {
         "appProtocol": {
-          "description": "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 https://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.",
+          "description": "The application protocol for this port. This is used as a hint for implementations to offer richer behavior for protocols that they understand. This field follows standard Kubernetes label syntax. Valid values are either:\n\n* Un-prefixed protocol names - reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names).\n\n* Kubernetes-defined prefixed names:\n  * 'kubernetes.io/h2c' - HTTP/2 over cleartext as described in https://www.rfc-editor.org/rfc/rfc7540\n\n* Other protocols should use implementation-defined prefixed names such as mycompany.com/my-custom-protocol.",
           "type": "string"
         },
         "name": {
@@ -5121,7 +5452,7 @@
           "type": "integer"
         },
         "protocol": {
-          "description": "The IP protocol for this port. Must be UDP, TCP, or SCTP. Default is TCP.\n\n",
+          "description": "The IP protocol for this port. Must be UDP, TCP, or SCTP. Default is TCP.",
           "type": "string"
         }
       },
@@ -5324,7 +5655,7 @@
           "type": "string"
         },
         "imagePullPolicy": {
-          "description": "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\n\n",
+          "description": "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",
           "type": "string"
         },
         "lifecycle": {
@@ -5357,6 +5688,14 @@
           "$ref": "#/definitions/io.k8s.api.core.v1.Probe",
           "description": "Probes are not allowed for ephemeral containers."
         },
+        "resizePolicy": {
+          "description": "Resources resize policy for the container.",
+          "items": {
+            "$ref": "#/definitions/io.k8s.api.core.v1.ContainerResizePolicy"
+          },
+          "type": "array",
+          "x-kubernetes-list-type": "atomic"
+        },
         "resources": {
           "$ref": "#/definitions/io.k8s.api.core.v1.ResourceRequirements",
           "description": "Resources are not allowed for ephemeral containers. Ephemeral containers use spare resources already allocated to the pod."
@@ -5386,7 +5725,7 @@
           "type": "string"
         },
         "terminationMessagePolicy": {
-          "description": "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.\n\n",
+          "description": "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.",
           "type": "string"
         },
         "tty": {
@@ -5840,7 +6179,7 @@
           "description": "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."
         },
         "scheme": {
-          "description": "Scheme to use for connecting to the host. Defaults to HTTP.\n\n",
+          "description": "Scheme to use for connecting to the host. Defaults to HTTP.",
           "type": "string"
         }
       },
@@ -6408,7 +6747,7 @@
           "x-kubernetes-patch-strategy": "merge"
         },
         "phase": {
-          "description": "Phase is the current lifecycle phase of the namespace. More info: https://kubernetes.io/docs/tasks/administer-cluster/namespaces/\n\n",
+          "description": "Phase is the current lifecycle phase of the namespace. More info: https://kubernetes.io/docs/tasks/administer-cluster/namespaces/",
           "type": "string"
         }
       },
@@ -6618,7 +6957,7 @@
           "type": "string"
         },
         "operator": {
-          "description": "Represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist. Gt, and Lt.\n\n",
+          "description": "Represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist. Gt, and Lt.",
           "type": "string"
         },
         "values": {
@@ -6701,7 +7040,7 @@
       "description": "NodeStatus is information about the current status of a node.",
       "properties": {
         "addresses": {
-          "description": "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 https://pr.k8s.io/79391 for an example.",
+          "description": "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 https://pr.k8s.io/79391 for an example. Consumers should assume that addresses can change during the lifetime of a Node. However, there are some exceptions where this may not be possible, such as Pods that inherit a Node's address in its own status or consumers of the downward API (status.hostIP).",
           "items": {
             "$ref": "#/definitions/io.k8s.api.core.v1.NodeAddress"
           },
@@ -6752,7 +7091,7 @@
           "description": "Set of ids/uuids to uniquely identify the node. More info: https://kubernetes.io/docs/concepts/nodes/node/#info"
         },
         "phase": {
-          "description": "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.\n\n",
+          "description": "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.",
           "type": "string"
         },
         "volumesAttached": {
@@ -6950,7 +7289,7 @@
       ]
     },
     "io.k8s.api.core.v1.PersistentVolumeClaimCondition": {
-      "description": "PersistentVolumeClaimCondition contails details about state of pvc",
+      "description": "PersistentVolumeClaimCondition contains details about state of pvc",
       "properties": {
         "lastProbeTime": {
           "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time",
@@ -7091,7 +7430,7 @@
           "x-kubernetes-patch-strategy": "merge"
         },
         "phase": {
-          "description": "phase represents the current phase of PersistentVolumeClaim.\n\n",
+          "description": "phase represents the current phase of PersistentVolumeClaim.",
           "type": "string"
         },
         "resizeStatus": {
@@ -7264,7 +7603,7 @@
           "description": "nodeAffinity defines constraints that limit what nodes this volume can be accessed from. This field influences the scheduling of pods that use this volume."
         },
         "persistentVolumeReclaimPolicy": {
-          "description": "persistentVolumeReclaimPolicy defines 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\n\n",
+          "description": "persistentVolumeReclaimPolicy defines 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",
           "type": "string"
         },
         "photonPersistentDisk": {
@@ -7314,7 +7653,7 @@
           "type": "string"
         },
         "phase": {
-          "description": "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\n\n",
+          "description": "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",
           "type": "string"
         },
         "reason": {
@@ -7703,7 +8042,7 @@
           "description": "Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy."
         },
         "dnsPolicy": {
-          "description": "Set DNS policy for the pod. Defaults to \"ClusterFirst\". Valid values are 'ClusterFirstWithHostNet', 'ClusterFirst', 'Default' or 'None'. 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 'ClusterFirstWithHostNet'.\n\n",
+          "description": "Set DNS policy for the pod. Defaults to \"ClusterFirst\". Valid values are 'ClusterFirstWithHostNet', 'ClusterFirst', 'Default' or 'None'. 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 'ClusterFirstWithHostNet'.",
           "type": "string"
         },
         "enableServiceLinks": {
@@ -7823,7 +8162,7 @@
           "x-kubernetes-patch-strategy": "merge,retainKeys"
         },
         "restartPolicy": {
-          "description": "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\n\n",
+          "description": "Restart policy for all containers within the pod. One of Always, OnFailure, Never. In some contexts, only a subset of those values may be permitted. Default to Always. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy",
           "type": "string"
         },
         "runtimeClassName": {
@@ -7835,7 +8174,7 @@
           "type": "string"
         },
         "schedulingGates": {
-          "description": "SchedulingGates is an opaque list of values that if specified will block scheduling the pod. More info:  https://git.k8s.io/enhancements/keps/sig-scheduling/3521-pod-scheduling-readiness.\n\nThis is an alpha-level feature enabled by PodSchedulingReadiness feature gate.",
+          "description": "SchedulingGates is an opaque list of values that if specified will block scheduling the pod. If schedulingGates is not empty, the pod will stay in the SchedulingGated state and the scheduler will not attempt to schedule the pod.\n\nSchedulingGates can only be set at pod creation time, and be removed only afterwards.\n\nThis is a beta feature enabled by the PodSchedulingReadiness feature gate.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.core.v1.PodSchedulingGate"
           },
@@ -7958,7 +8297,7 @@
           "type": "string"
         },
         "phase": {
-          "description": "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's status. There are five possible phase values:\n\nPending: 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.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase\n\n",
+          "description": "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's status. There are five possible phase values:\n\nPending: 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.\n\nMore info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase",
           "type": "string"
         },
         "podIP": {
@@ -7975,13 +8314,17 @@
           "x-kubernetes-patch-strategy": "merge"
         },
         "qosClass": {
-          "description": "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\n\n",
+          "description": "The Quality of Service (QOS) classification assigned to the pod based on resource requirements See PodQOSClass type for available QOS classes More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-qos/#quality-of-service-classes",
           "type": "string"
         },
         "reason": {
           "description": "A brief CamelCase message indicating details about why the pod is in this state. e.g. 'Evicted'",
           "type": "string"
         },
+        "resize": {
+          "description": "Status of resources resize desired for pod's containers. It is empty if no resources resize is pending. Any changes to container resources will automatically set this to \"Proposed\"",
+          "type": "string"
+        },
         "startTime": {
           "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time",
           "description": "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."
@@ -8079,7 +8422,7 @@
           "type": "integer"
         },
         "protocol": {
-          "description": "Protocol is the protocol of the service port of which status is recorded here The supported values are: \"TCP\", \"UDP\", \"SCTP\"\n\n",
+          "description": "Protocol is the protocol of the service port of which status is recorded here The supported values are: \"TCP\", \"UDP\", \"SCTP\"",
           "type": "string"
         }
       },
@@ -8143,7 +8486,7 @@
         },
         "grpc": {
           "$ref": "#/definitions/io.k8s.api.core.v1.GRPCAction",
-          "description": "GRPC specifies an action involving a GRPC port. This is a beta field and requires enabling GRPCContainerProbe feature gate."
+          "description": "GRPC specifies an action involving a GRPC port."
         },
         "httpGet": {
           "$ref": "#/definitions/io.k8s.api.core.v1.HTTPGetAction",
@@ -8444,7 +8787,7 @@
         },
         "template": {
           "$ref": "#/definitions/io.k8s.api.core.v1.PodTemplateSpec",
-          "description": "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"
+          "description": "Template is the object that describes the pod that will be created if insufficient replicas are detected. This takes precedence over a TemplateRef. The only allowed template.spec.restartPolicy value is \"Always\". More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template"
         }
       },
       "type": "object"
@@ -8643,12 +8986,15 @@
       "description": "ResourceRequirements describes the compute resource requirements.",
       "properties": {
         "claims": {
-          "description": "Claims lists the names of resources, defined in spec.resourceClaims, that are used by this container.\n\nThis is an alpha field and requires enabling the DynamicResourceAllocation feature gate.\n\nThis field is immutable.",
+          "description": "Claims lists the names of resources, defined in spec.resourceClaims, that are used by this container.\n\nThis is an alpha field and requires enabling the DynamicResourceAllocation feature gate.\n\nThis field is immutable. It can only be set for containers.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.core.v1.ResourceClaim"
           },
           "type": "array",
-          "x-kubernetes-list-type": "set"
+          "x-kubernetes-list-map-keys": [
+            "name"
+          ],
+          "x-kubernetes-list-type": "map"
         },
         "limits": {
           "additionalProperties": {
@@ -8661,7 +9007,7 @@
           "additionalProperties": {
             "$ref": "#/definitions/io.k8s.apimachinery.pkg.api.resource.Quantity"
           },
-          "description": "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/",
+          "description": "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. Requests cannot exceed Limits. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/",
           "type": "object"
         }
       },
@@ -8809,11 +9155,11 @@
       "description": "A scoped-resource selector requirement is a selector that contains values, a scope name, and an operator that relates the scope name and values.",
       "properties": {
         "operator": {
-          "description": "Represents a scope's relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist.\n\n",
+          "description": "Represents a scope's relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist.",
           "type": "string"
         },
         "scopeName": {
-          "description": "The name of the scope that the selector applies to.\n\n",
+          "description": "The name of the scope that the selector applies to.",
           "type": "string"
         },
         "values": {
@@ -8838,7 +9184,7 @@
           "type": "string"
         },
         "type": {
-          "description": "type indicates which kind of seccomp profile will be applied. Valid options are:\n\nLocalhost - 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.\n\n",
+          "description": "type indicates which kind of seccomp profile will be applied. Valid options are:\n\nLocalhost - 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.",
           "type": "string"
         }
       },
@@ -9280,7 +9626,7 @@
           "type": "integer"
         },
         "protocol": {
-          "description": "The IP protocol for this port. Supports \"TCP\", \"UDP\", and \"SCTP\". Default is TCP.\n\n",
+          "description": "The IP protocol for this port. Supports \"TCP\", \"UDP\", and \"SCTP\". Default is TCP.",
           "type": "string"
         },
         "targetPort": {
@@ -9324,7 +9670,7 @@
           "type": "string"
         },
         "externalTrafficPolicy": {
-          "description": "externalTrafficPolicy describes how nodes distribute service traffic they receive on one of the Service's \"externally-facing\" addresses (NodePorts, ExternalIPs, and LoadBalancer IPs). If set to \"Local\", the proxy will configure the service in a way that assumes that external load balancers will take care of balancing the service traffic between nodes, and so each node will deliver traffic only to the node-local endpoints of the service, without masquerading the client source IP. (Traffic mistakenly sent to a node with no endpoints will be dropped.) The default value, \"Cluster\", uses the standard behavior of routing to all endpoints evenly (possibly modified by topology and other features). Note that traffic sent to an External IP or LoadBalancer IP from within the cluster will always get \"Cluster\" semantics, but clients sending to a NodePort from within the cluster may need to take traffic policy into account when picking a node.\n\n",
+          "description": "externalTrafficPolicy describes how nodes distribute service traffic they receive on one of the Service's \"externally-facing\" addresses (NodePorts, ExternalIPs, and LoadBalancer IPs). If set to \"Local\", the proxy will configure the service in a way that assumes that external load balancers will take care of balancing the service traffic between nodes, and so each node will deliver traffic only to the node-local endpoints of the service, without masquerading the client source IP. (Traffic mistakenly sent to a node with no endpoints will be dropped.) The default value, \"Cluster\", uses the standard behavior of routing to all endpoints evenly (possibly modified by topology and other features). Note that traffic sent to an External IP or LoadBalancer IP from within the cluster will always get \"Cluster\" semantics, but clients sending to a NodePort from within the cluster may need to take traffic policy into account when picking a node.",
           "type": "string"
         },
         "healthCheckNodePort": {
@@ -9390,7 +9736,7 @@
           "x-kubernetes-map-type": "atomic"
         },
         "sessionAffinity": {
-          "description": "Supports \"ClientIP\" and \"None\". 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\n\n",
+          "description": "Supports \"ClientIP\" and \"None\". 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",
           "type": "string"
         },
         "sessionAffinityConfig": {
@@ -9398,7 +9744,7 @@
           "description": "sessionAffinityConfig contains the configurations of session affinity."
         },
         "type": {
-          "description": "type determines how the Service is exposed. Defaults to ClusterIP. Valid options are ExternalName, ClusterIP, NodePort, and LoadBalancer. \"ClusterIP\" 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 \"None\", no virtual IP is allocated and the endpoints are published as a set of endpoints rather than a virtual IP. \"NodePort\" builds on ClusterIP and allocates a port on every node which routes to the same endpoints as the clusterIP. \"LoadBalancer\" builds on NodePort and creates an external load-balancer (if supported in the current cloud) which routes to the same endpoints as the clusterIP. \"ExternalName\" 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\n\n",
+          "description": "type determines how the Service is exposed. Defaults to ClusterIP. Valid options are ExternalName, ClusterIP, NodePort, and LoadBalancer. \"ClusterIP\" 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 \"None\", no virtual IP is allocated and the endpoints are published as a set of endpoints rather than a virtual IP. \"NodePort\" builds on ClusterIP and allocates a port on every node which routes to the same endpoints as the clusterIP. \"LoadBalancer\" builds on NodePort and creates an external load-balancer (if supported in the current cloud) which routes to the same endpoints as the clusterIP. \"ExternalName\" 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",
           "type": "string"
         }
       },
@@ -9528,7 +9874,7 @@
       "description": "The node this Taint is attached to has the \"effect\" on any pod that does not tolerate the Taint.",
       "properties": {
         "effect": {
-          "description": "Required. The effect of the taint on pods that do not tolerate the taint. Valid effects are NoSchedule, PreferNoSchedule and NoExecute.\n\n",
+          "description": "Required. The effect of the taint on pods that do not tolerate the taint. Valid effects are NoSchedule, PreferNoSchedule and NoExecute.",
           "type": "string"
         },
         "key": {
@@ -9554,7 +9900,7 @@
       "description": "The pod this Toleration is attached to tolerates any taint that matches the triple <key,value,effect> using the matching operator <operator>.",
       "properties": {
         "effect": {
-          "description": "Effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.\n\n",
+          "description": "Effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.",
           "type": "string"
         },
         "key": {
@@ -9562,7 +9908,7 @@
           "type": "string"
         },
         "operator": {
-          "description": "Operator represents a key'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.\n\n",
+          "description": "Operator represents a key'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.",
           "type": "string"
         },
         "tolerationSeconds": {
@@ -9620,7 +9966,7 @@
           "description": "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."
         },
         "matchLabelKeys": {
-          "description": "MatchLabelKeys is a set of pod label keys to select the pods over which spreading will be calculated. The keys are used to lookup values from the incoming pod labels, those key-value labels are ANDed with labelSelector to select the group of existing pods over which spreading will be calculated for the incoming pod. Keys that don't exist in the incoming pod labels will be ignored. A null or empty list means only match against labelSelector.",
+          "description": "MatchLabelKeys is a set of pod label keys to select the pods over which spreading will be calculated. The keys are used to lookup values from the incoming pod labels, those key-value labels are ANDed with labelSelector to select the group of existing pods over which spreading will be calculated for the incoming pod. The same key is forbidden to exist in both MatchLabelKeys and LabelSelector. MatchLabelKeys cannot be set when LabelSelector isn't set. Keys that don't exist in the incoming pod labels will be ignored. A null or empty list means only match against labelSelector.\n\nThis is a beta field and requires the MatchLabelKeysInPodTopologySpread feature gate to be enabled (enabled by default).",
           "items": {
             "type": "string"
           },
@@ -9650,7 +9996,7 @@
           "type": "string"
         },
         "whenUnsatisfiable": {
-          "description": "WhenUnsatisfiable indicates how to deal with a pod if it doesn'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,\n  but giving higher precedence to topologies that would help reduce the\n  skew.\nA constraint is considered \"Unsatisfiable\" for an incoming pod if and only if every possible node assignment for that pod would violate \"MaxSkew\" 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't make it *more* imbalanced. It's a required field.\n\n",
+          "description": "WhenUnsatisfiable indicates how to deal with a pod if it doesn'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,\n  but giving higher precedence to topologies that would help reduce the\n  skew.\nA constraint is considered \"Unsatisfiable\" for an incoming pod if and only if every possible node assignment for that pod would violate \"MaxSkew\" 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't make it *more* imbalanced. It's a required field.",
           "type": "string"
         }
       },
@@ -10040,7 +10386,7 @@
       "description": "EndpointConditions represents the current condition of an endpoint.",
       "properties": {
         "ready": {
-          "description": "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 \"true\" for terminating endpoints.",
+          "description": "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 \"true\" for terminating endpoints, except when the normal readiness behavior is being explicitly overridden, for example when the associated Service has set the publishNotReadyAddresses flag.",
           "type": "boolean"
         },
         "serving": {
@@ -10072,20 +10418,20 @@
       "description": "EndpointPort represents a Port used by an EndpointSlice",
       "properties": {
         "appProtocol": {
-          "description": "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 https://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.",
+          "description": "The application protocol for this port. This is used as a hint for implementations to offer richer behavior for protocols that they understand. This field follows standard Kubernetes label syntax. Valid values are either:\n\n* Un-prefixed protocol names - reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names).\n\n* Kubernetes-defined prefixed names:\n  * 'kubernetes.io/h2c' - HTTP/2 over cleartext as described in https://www.rfc-editor.org/rfc/rfc7540\n\n* Other protocols should use implementation-defined prefixed names such as mycompany.com/my-custom-protocol.",
           "type": "string"
         },
         "name": {
-          "description": "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 '-'. * must start and end with an alphanumeric character. Default is empty string.",
+          "description": "name represents 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 '-'. * must start and end with an alphanumeric character. Default is empty string.",
           "type": "string"
         },
         "port": {
-          "description": "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.",
+          "description": "port represents 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.",
           "format": "int32",
           "type": "integer"
         },
         "protocol": {
-          "description": "The IP protocol for this port. Must be UDP, TCP, or SCTP. Default is TCP.",
+          "description": "protocol represents the IP protocol for this port. Must be UDP, TCP, or SCTP. Default is TCP.",
           "type": "string"
         }
       },
@@ -10096,7 +10442,7 @@
       "description": "EndpointSlice represents a subset of the endpoints that implement a service. For a given service there may be multiple EndpointSlice objects, selected by labels, which must be joined to produce the full set of endpoints.",
       "properties": {
         "addressType": {
-          "description": "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.\n\n",
+          "description": "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.",
           "type": "string"
         },
         "apiVersion": {
@@ -10149,7 +10495,7 @@
           "type": "string"
         },
         "items": {
-          "description": "List of endpoint slices",
+          "description": "items is the list of endpoint slices",
           "items": {
             "$ref": "#/definitions/io.k8s.api.discovery.v1.EndpointSlice"
           },
@@ -11455,14 +11801,14 @@
       "properties": {
         "backend": {
           "$ref": "#/definitions/io.k8s.api.networking.v1.IngressBackend",
-          "description": "Backend defines the referenced service endpoint to which the traffic will be forwarded to."
+          "description": "backend defines the referenced service endpoint to which the traffic will be forwarded to."
         },
         "path": {
-          "description": "Path is matched against the path of an incoming request. Currently it can contain characters disallowed from the conventional \"path\" part of a URL as defined by RFC 3986. Paths must begin with a '/' and must be present when using PathType with value \"Exact\" or \"Prefix\".",
+          "description": "path is matched against the path of an incoming request. Currently it can contain characters disallowed from the conventional \"path\" part of a URL as defined by RFC 3986. Paths must begin with a '/' and must be present when using PathType with value \"Exact\" or \"Prefix\".",
           "type": "string"
         },
         "pathType": {
-          "description": "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 '/'. Matching is\n  done on a path element by element basis. A path element refers is the\n  list of labels in the path split by the '/' separator. A request is a\n  match for path p if every p is an element-wise prefix of p of the\n  request path. Note that if the last element of the path is a substring\n  of the last element in request path, it is not a match (e.g. /foo/bar\n  matches /foo/bar/baz, but does not match /foo/barbaz).\n* ImplementationSpecific: Interpretation of the Path matching is up to\n  the IngressClass. Implementations can treat this as a separate PathType\n  or treat it identically to Prefix or Exact path types.\nImplementations are required to support all path types.",
+          "description": "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 '/'. Matching is\n  done on a path element by element basis. A path element refers is the\n  list of labels in the path split by the '/' separator. A request is a\n  match for path p if every p is an element-wise prefix of p of the\n  request path. Note that if the last element of the path is a substring\n  of the last element in request path, it is not a match (e.g. /foo/bar\n  matches /foo/bar/baz, but does not match /foo/barbaz).\n* ImplementationSpecific: Interpretation of the Path matching is up to\n  the IngressClass. Implementations can treat this as a separate PathType\n  or treat it identically to Prefix or Exact path types.\nImplementations are required to support all path types.",
           "type": "string"
         }
       },
@@ -11476,7 +11822,7 @@
       "description": "HTTPIngressRuleValue is a list of http selectors pointing to backends. In the example: http://<host>/<path>?<searchpart> -> backend where where parts of the url correspond to RFC 3986, this resource will be used to match against everything after the last '/' and before the first '?' or '#'.",
       "properties": {
         "paths": {
-          "description": "A collection of paths that map requests to backends.",
+          "description": "paths is a collection of paths that map requests to backends.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.networking.v1.HTTPIngressPath"
           },
@@ -11493,11 +11839,11 @@
       "description": "IPBlock describes a particular CIDR (Ex. \"192.168.1.0/24\",\"2001:db8::/64\") that is allowed to the pods matched by a NetworkPolicySpec's podSelector. The except entry describes CIDRs that should not be included within this rule.",
       "properties": {
         "cidr": {
-          "description": "CIDR is a string representing the IP Block Valid examples are \"192.168.1.0/24\" or \"2001:db8::/64\"",
+          "description": "cidr is a string representing the IPBlock Valid examples are \"192.168.1.0/24\" or \"2001:db8::/64\"",
           "type": "string"
         },
         "except": {
-          "description": "Except is a slice of CIDRs that should not be included within an IP Block Valid examples are \"192.168.1.0/24\" or \"2001:db8::/64\" Except values will be rejected if they are outside the CIDR range",
+          "description": "except is a slice of CIDRs that should not be included within an IPBlock Valid examples are \"192.168.1.0/24\" or \"2001:db8::/64\" Except values will be rejected if they are outside the cidr range",
           "items": {
             "type": "string"
           },
@@ -11526,11 +11872,11 @@
         },
         "spec": {
           "$ref": "#/definitions/io.k8s.api.networking.v1.IngressSpec",
-          "description": "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"
+          "description": "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"
         },
         "status": {
           "$ref": "#/definitions/io.k8s.api.networking.v1.IngressStatus",
-          "description": "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"
+          "description": "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"
         }
       },
       "type": "object",
@@ -11547,11 +11893,11 @@
       "properties": {
         "resource": {
           "$ref": "#/definitions/io.k8s.api.core.v1.TypedLocalObjectReference",
-          "description": "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 \"Service\"."
+          "description": "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 \"Service\"."
         },
         "service": {
           "$ref": "#/definitions/io.k8s.api.networking.v1.IngressServiceBackend",
-          "description": "Service references a Service as a Backend. This is a mutually exclusive setting with \"Resource\"."
+          "description": "service references a service as a backend. This is a mutually exclusive setting with \"Resource\"."
         }
       },
       "type": "object"
@@ -11573,7 +11919,7 @@
         },
         "spec": {
           "$ref": "#/definitions/io.k8s.api.networking.v1.IngressClassSpec",
-          "description": "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"
+          "description": "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"
         }
       },
       "type": "object",
@@ -11593,7 +11939,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Items is the list of IngressClasses.",
+          "description": "items is the list of IngressClasses.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.networking.v1.IngressClass"
           },
@@ -11624,23 +11970,23 @@
       "description": "IngressClassParametersReference identifies an API object. This can be used to specify a cluster or namespace-scoped resource.",
       "properties": {
         "apiGroup": {
-          "description": "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.",
+          "description": "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.",
           "type": "string"
         },
         "kind": {
-          "description": "Kind is the type of resource being referenced.",
+          "description": "kind is the type of resource being referenced.",
           "type": "string"
         },
         "name": {
-          "description": "Name is the name of resource being referenced.",
+          "description": "name is the name of resource being referenced.",
           "type": "string"
         },
         "namespace": {
-          "description": "Namespace is the namespace of the resource being referenced. This field is required when scope is set to \"Namespace\" and must be unset when scope is set to \"Cluster\".",
+          "description": "namespace is the namespace of the resource being referenced. This field is required when scope is set to \"Namespace\" and must be unset when scope is set to \"Cluster\".",
           "type": "string"
         },
         "scope": {
-          "description": "Scope represents if this refers to a cluster or namespace scoped resource. This may be set to \"Cluster\" (default) or \"Namespace\".",
+          "description": "scope represents if this refers to a cluster or namespace scoped resource. This may be set to \"Cluster\" (default) or \"Namespace\".",
           "type": "string"
         }
       },
@@ -11654,12 +12000,12 @@
       "description": "IngressClassSpec provides information about the class of an Ingress.",
       "properties": {
         "controller": {
-          "description": "Controller refers to the name of the controller that should handle this class. This allows for different \"flavors\" 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. \"acme.io/ingress-controller\". This field is immutable.",
+          "description": "controller refers to the name of the controller that should handle this class. This allows for different \"flavors\" 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. \"acme.io/ingress-controller\". This field is immutable.",
           "type": "string"
         },
         "parameters": {
           "$ref": "#/definitions/io.k8s.api.networking.v1.IngressClassParametersReference",
-          "description": "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."
+          "description": "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."
         }
       },
       "type": "object"
@@ -11672,7 +12018,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Items is the list of Ingress.",
+          "description": "items is the list of Ingress.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.networking.v1.Ingress"
           },
@@ -11703,15 +12049,15 @@
       "description": "IngressLoadBalancerIngress represents the status of a load-balancer ingress point.",
       "properties": {
         "hostname": {
-          "description": "Hostname is set for load-balancer ingress points that are DNS based.",
+          "description": "hostname is set for load-balancer ingress points that are DNS based.",
           "type": "string"
         },
         "ip": {
-          "description": "IP is set for load-balancer ingress points that are IP based.",
+          "description": "ip is set for load-balancer ingress points that are IP based.",
           "type": "string"
         },
         "ports": {
-          "description": "Ports provides information about the ports exposed by this LoadBalancer.",
+          "description": "ports provides information about the ports exposed by this LoadBalancer.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.networking.v1.IngressPortStatus"
           },
@@ -11725,7 +12071,7 @@
       "description": "IngressLoadBalancerStatus represents the status of a load-balancer.",
       "properties": {
         "ingress": {
-          "description": "Ingress is a list containing ingress points for the load-balancer.",
+          "description": "ingress is a list containing ingress points for the load-balancer.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.networking.v1.IngressLoadBalancerIngress"
           },
@@ -11738,16 +12084,16 @@
       "description": "IngressPortStatus represents the error condition of a service port",
       "properties": {
         "error": {
-          "description": "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\n  CamelCase names\n- cloud provider specific error values must have names that comply with the\n  format foo.example.com/CamelCase.",
+          "description": "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\n  CamelCase names\n- cloud provider specific error values must have names that comply with the\n  format foo.example.com/CamelCase.",
           "type": "string"
         },
         "port": {
-          "description": "Port is the port number of the ingress port.",
+          "description": "port is the port number of the ingress port.",
           "format": "int32",
           "type": "integer"
         },
         "protocol": {
-          "description": "Protocol is the protocol of the ingress port. The supported values are: \"TCP\", \"UDP\", \"SCTP\"\n\n",
+          "description": "protocol is the protocol of the ingress port. The supported values are: \"TCP\", \"UDP\", \"SCTP\"",
           "type": "string"
         }
       },
@@ -11761,7 +12107,7 @@
       "description": "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.",
       "properties": {
         "host": {
-          "description": "Host is the fully qualified domain name of a network host, as defined by RFC 3986. Note the following deviations from the \"host\" part of the URI as defined in RFC 3986: 1. IPs are not allowed. Currently an IngressRuleValue can only apply to\n   the IP in the Spec of the parent Ingress.\n2. The `:` delimiter is not respected because ports are not allowed.\n\t  Currently the port of an Ingress is implicitly :80 for http and\n\t  :443 for https.\nBoth 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.\n\nHost can be \"precise\" which is a domain name without the terminating dot of a network host (e.g. \"foo.bar.com\") or \"wildcard\", which is a domain name prefixed with a single wildcard label (e.g. \"*.foo.com\"). The wildcard character '*' 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 == \"*\"). 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.",
+          "description": "host is the fully qualified domain name of a network host, as defined by RFC 3986. Note the following deviations from the \"host\" part of the URI as defined in RFC 3986: 1. IPs are not allowed. Currently an IngressRuleValue can only apply to\n   the IP in the Spec of the parent Ingress.\n2. The `:` delimiter is not respected because ports are not allowed.\n\t  Currently the port of an Ingress is implicitly :80 for http and\n\t  :443 for https.\nBoth 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.\n\nhost can be \"precise\" which is a domain name without the terminating dot of a network host (e.g. \"foo.bar.com\") or \"wildcard\", which is a domain name prefixed with a single wildcard label (e.g. \"*.foo.com\"). The wildcard character '*' 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 == \"*\"). 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.",
           "type": "string"
         },
         "http": {
@@ -11774,12 +12120,12 @@
       "description": "IngressServiceBackend references a Kubernetes Service as a Backend.",
       "properties": {
         "name": {
-          "description": "Name is the referenced service. The service must exist in the same namespace as the Ingress object.",
+          "description": "name is the referenced service. The service must exist in the same namespace as the Ingress object.",
           "type": "string"
         },
         "port": {
           "$ref": "#/definitions/io.k8s.api.networking.v1.ServiceBackendPort",
-          "description": "Port of the referenced service. A port name or port number is required for a IngressServiceBackend."
+          "description": "port of the referenced service. A port name or port number is required for a IngressServiceBackend."
         }
       },
       "required": [
@@ -11792,14 +12138,14 @@
       "properties": {
         "defaultBackend": {
           "$ref": "#/definitions/io.k8s.api.networking.v1.IngressBackend",
-          "description": "DefaultBackend is the backend that should handle requests that don'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."
+          "description": "defaultBackend is the backend that should handle requests that don'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."
         },
         "ingressClassName": {
-          "description": "IngressClassName is the name of an IngressClass cluster resource. Ingress controller implementations use this field to know whether they should be serving this Ingress resource, by a transitive connection (controller -> IngressClass -> Ingress resource). Although the `kubernetes.io/ingress.class` annotation (simple constant name) was never formally defined, it was widely supported by Ingress controllers to create a direct binding between Ingress controller and Ingress resources. Newly created Ingress resources should prefer using the field. However, even though the annotation is officially deprecated, for backwards compatibility reasons, ingress controllers should still honor that annotation if present.",
+          "description": "ingressClassName is the name of an IngressClass cluster resource. Ingress controller implementations use this field to know whether they should be serving this Ingress resource, by a transitive connection (controller -> IngressClass -> Ingress resource). Although the `kubernetes.io/ingress.class` annotation (simple constant name) was never formally defined, it was widely supported by Ingress controllers to create a direct binding between Ingress controller and Ingress resources. Newly created Ingress resources should prefer using the field. However, even though the annotation is officially deprecated, for backwards compatibility reasons, ingress controllers should still honor that annotation if present.",
           "type": "string"
         },
         "rules": {
-          "description": "A list of host rules used to configure the Ingress. If unspecified, or no rule matches, all traffic is sent to the default backend.",
+          "description": "rules is a list of host rules used to configure the Ingress. If unspecified, or no rule matches, all traffic is sent to the default backend.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.networking.v1.IngressRule"
           },
@@ -11807,7 +12153,7 @@
           "x-kubernetes-list-type": "atomic"
         },
         "tls": {
-          "description": "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.",
+          "description": "tls represents the 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.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.networking.v1.IngressTLS"
           },
@@ -11822,16 +12168,16 @@
       "properties": {
         "loadBalancer": {
           "$ref": "#/definitions/io.k8s.api.networking.v1.IngressLoadBalancerStatus",
-          "description": "LoadBalancer contains the current status of the load-balancer."
+          "description": "loadBalancer contains the current status of the load-balancer."
         }
       },
       "type": "object"
     },
     "io.k8s.api.networking.v1.IngressTLS": {
-      "description": "IngressTLS describes the transport layer security associated with an Ingress.",
+      "description": "IngressTLS describes the transport layer security associated with an ingress.",
       "properties": {
         "hosts": {
-          "description": "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.",
+          "description": "hosts is 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.",
           "items": {
             "type": "string"
           },
@@ -11839,7 +12185,7 @@
           "x-kubernetes-list-type": "atomic"
         },
         "secretName": {
-          "description": "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 \"Host\" header field used by an IngressRule, the SNI host is used for termination and value of the Host header is used for routing.",
+          "description": "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 \"Host\" header field used by an IngressRule, the SNI host is used for termination and value of the \"Host\" header is used for routing.",
           "type": "string"
         }
       },
@@ -11862,11 +12208,11 @@
         },
         "spec": {
           "$ref": "#/definitions/io.k8s.api.networking.v1.NetworkPolicySpec",
-          "description": "Specification of the desired behavior for this NetworkPolicy."
+          "description": "spec represents the specification of the desired behavior for this NetworkPolicy."
         },
         "status": {
           "$ref": "#/definitions/io.k8s.api.networking.v1.NetworkPolicyStatus",
-          "description": "Status is the current state of the NetworkPolicy. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status"
+          "description": "status represents the current state of the NetworkPolicy. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status"
         }
       },
       "type": "object",
@@ -11882,14 +12228,14 @@
       "description": "NetworkPolicyEgressRule describes a particular set of traffic that is allowed out of pods matched by a NetworkPolicySpec's podSelector. The traffic must match both ports and to. This type is beta-level in 1.8",
       "properties": {
         "ports": {
-          "description": "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.",
+          "description": "ports is a 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.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.networking.v1.NetworkPolicyPort"
           },
           "type": "array"
         },
         "to": {
-          "description": "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.",
+          "description": "to is a 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.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.networking.v1.NetworkPolicyPeer"
           },
@@ -11902,14 +12248,14 @@
       "description": "NetworkPolicyIngressRule describes a particular set of traffic that is allowed to the pods matched by a NetworkPolicySpec's podSelector. The traffic must match both ports and from.",
       "properties": {
         "from": {
-          "description": "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.",
+          "description": "from is a 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.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.networking.v1.NetworkPolicyPeer"
           },
           "type": "array"
         },
         "ports": {
-          "description": "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.",
+          "description": "ports is a 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.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.networking.v1.NetworkPolicyPort"
           },
@@ -11926,7 +12272,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Items is a list of schema objects.",
+          "description": "items is a list of schema objects.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.networking.v1.NetworkPolicy"
           },
@@ -11958,15 +12304,15 @@
       "properties": {
         "ipBlock": {
           "$ref": "#/definitions/io.k8s.api.networking.v1.IPBlock",
-          "description": "IPBlock defines policy on a particular IPBlock. If this field is set then neither of the other fields can be."
+          "description": "ipBlock defines policy on a particular IPBlock. If this field is set then neither of the other fields can be."
         },
         "namespaceSelector": {
           "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelector",
-          "description": "Selects Namespaces using cluster-scoped labels. This field follows standard label selector semantics; if present but empty, it selects all namespaces.\n\nIf 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."
+          "description": "namespaceSelector selects namespaces using cluster-scoped labels. This field follows standard label selector semantics; if present but empty, it selects all namespaces.\n\nIf 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."
         },
         "podSelector": {
           "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelector",
-          "description": "This is a label selector which selects Pods. This field follows standard label selector semantics; if present but empty, it selects all pods.\n\nIf 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's own Namespace."
+          "description": "podSelector is a label selector which selects pods. This field follows standard label selector semantics; if present but empty, it selects all pods.\n\nIf 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's own namespace."
         }
       },
       "type": "object"
@@ -11975,16 +12321,16 @@
       "description": "NetworkPolicyPort describes a port to allow traffic on",
       "properties": {
         "endPort": {
-          "description": "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.",
+          "description": "endPort indicates that the range of ports from port to endPort if set, 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.",
           "format": "int32",
           "type": "integer"
         },
         "port": {
           "$ref": "#/definitions/io.k8s.apimachinery.pkg.util.intstr.IntOrString",
-          "description": "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."
+          "description": "port represents 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."
         },
         "protocol": {
-          "description": "The protocol (TCP, UDP, or SCTP) which traffic must match. If not specified, this field defaults to TCP.",
+          "description": "protocol represents the protocol (TCP, UDP, or SCTP) which traffic must match. If not specified, this field defaults to TCP.",
           "type": "string"
         }
       },
@@ -11994,14 +12340,14 @@
       "description": "NetworkPolicySpec provides the specification of a NetworkPolicy",
       "properties": {
         "egress": {
-          "description": "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",
+          "description": "egress is a 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",
           "items": {
             "$ref": "#/definitions/io.k8s.api.networking.v1.NetworkPolicyEgressRule"
           },
           "type": "array"
         },
         "ingress": {
-          "description": "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'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)",
+          "description": "ingress is a 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'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)",
           "items": {
             "$ref": "#/definitions/io.k8s.api.networking.v1.NetworkPolicyIngressRule"
           },
@@ -12009,10 +12355,10 @@
         },
         "podSelector": {
           "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelector",
-          "description": "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."
+          "description": "podSelector 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."
         },
         "policyTypes": {
-          "description": "List of rule types that the NetworkPolicy relates to. Valid options are [\"Ingress\"], [\"Egress\"], or [\"Ingress\", \"Egress\"]. 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 [ \"Egress\" ]. Likewise, if you want to write a policy that specifies that no egress is allowed, you must specify a policyTypes value that include \"Egress\" (since such a policy would not include an Egress section and would otherwise default to just [ \"Ingress\" ]). This field is beta-level in 1.8",
+          "description": "policyTypes is a list of rule types that the NetworkPolicy relates to. Valid options are [\"Ingress\"], [\"Egress\"], or [\"Ingress\", \"Egress\"]. 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 [ \"Egress\" ]. Likewise, if you want to write a policy that specifies that no egress is allowed, you must specify a policyTypes value that include \"Egress\" (since such a policy would not include an egress section and would otherwise default to just [ \"Ingress\" ]). This field is beta-level in 1.8",
           "items": {
             "type": "string"
           },
@@ -12025,10 +12371,10 @@
       "type": "object"
     },
     "io.k8s.api.networking.v1.NetworkPolicyStatus": {
-      "description": "NetworkPolicyStatus describe the current state of the NetworkPolicy.",
+      "description": "NetworkPolicyStatus describes the current state of the NetworkPolicy.",
       "properties": {
         "conditions": {
-          "description": "Conditions holds an array of metav1.Condition that describe the state of the NetworkPolicy. Current service state",
+          "description": "conditions holds an array of metav1.Condition that describe the state of the NetworkPolicy. Current service state",
           "items": {
             "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Condition"
           },
@@ -12047,11 +12393,11 @@
       "description": "ServiceBackendPort is the service port being referenced.",
       "properties": {
         "name": {
-          "description": "Name is the name of the port on the Service. This is a mutually exclusive setting with \"Number\".",
+          "description": "name is the name of the port on the Service. This is a mutually exclusive setting with \"Number\".",
           "type": "string"
         },
         "number": {
-          "description": "Number is the numerical port number (e.g. 80) on the Service. This is a mutually exclusive setting with \"Name\".",
+          "description": "number is the numerical port number (e.g. 80) on the Service. This is a mutually exclusive setting with \"Name\".",
           "format": "int32",
           "type": "integer"
         }
@@ -12075,7 +12421,7 @@
         },
         "spec": {
           "$ref": "#/definitions/io.k8s.api.networking.v1alpha1.ClusterCIDRSpec",
-          "description": "Spec is the desired state of the ClusterCIDR. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status"
+          "description": "spec is the desired state of the ClusterCIDR. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status"
         }
       },
       "type": "object",
@@ -12095,7 +12441,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Items is the list of ClusterCIDRs.",
+          "description": "items is the list of ClusterCIDRs.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.networking.v1alpha1.ClusterCIDR"
           },
@@ -12126,19 +12472,19 @@
       "description": "ClusterCIDRSpec defines the desired state of ClusterCIDR.",
       "properties": {
         "ipv4": {
-          "description": "IPv4 defines an IPv4 IP block in CIDR notation(e.g. \"10.0.0.0/8\"). At least one of IPv4 and IPv6 must be specified. This field is immutable.",
+          "description": "ipv4 defines an IPv4 IP block in CIDR notation(e.g. \"10.0.0.0/8\"). At least one of ipv4 and ipv6 must be specified. This field is immutable.",
           "type": "string"
         },
         "ipv6": {
-          "description": "IPv6 defines an IPv6 IP block in CIDR notation(e.g. \"2001:db8::/64\"). At least one of IPv4 and IPv6 must be specified. This field is immutable.",
+          "description": "ipv6 defines an IPv6 IP block in CIDR notation(e.g. \"2001:db8::/64\"). At least one of ipv4 and ipv6 must be specified. This field is immutable.",
           "type": "string"
         },
         "nodeSelector": {
           "$ref": "#/definitions/io.k8s.api.core.v1.NodeSelector",
-          "description": "NodeSelector defines which nodes the config is applicable to. An empty or nil NodeSelector selects all nodes. This field is immutable."
+          "description": "nodeSelector defines which nodes the config is applicable to. An empty or nil nodeSelector selects all nodes. This field is immutable."
         },
         "perNodeHostBits": {
-          "description": "PerNodeHostBits defines the number of host bits to be configured per node. A subnet mask determines how much of the address is used for network bits and host bits. For example an IPv4 address of 192.168.0.0/24, splits the address into 24 bits for the network portion and 8 bits for the host portion. To allocate 256 IPs, set this field to 8 (a /24 mask for IPv4 or a /120 for IPv6). Minimum value is 4 (16 IPs). This field is immutable.",
+          "description": "perNodeHostBits defines the number of host bits to be configured per node. A subnet mask determines how much of the address is used for network bits and host bits. For example an IPv4 address of 192.168.0.0/24, splits the address into 24 bits for the network portion and 8 bits for the host portion. To allocate 256 IPs, set this field to 8 (a /24 mask for IPv4 or a /120 for IPv6). Minimum value is 4 (16 IPs). This field is immutable.",
           "format": "int32",
           "type": "integer"
         }
@@ -12148,6 +12494,106 @@
       ],
       "type": "object"
     },
+    "io.k8s.api.networking.v1alpha1.IPAddress": {
+      "description": "IPAddress represents a single IP of a single IP Family. The object is designed to be used by APIs that operate on IP addresses. The object is used by the Service core API for allocation of IP addresses. An IP address can be represented in different formats, to guarantee the uniqueness of the IP, the name of the object is the IP address in canonical format, four decimal digits separated by dots suppressing leading zeros for IPv4 and the representation defined by RFC 5952 for IPv6. Valid: 192.168.1.5 or 2001:db8::1 or 2001:db8:aaaa:bbbb:cccc:dddd:eeee:1 Invalid: 10.01.2.3 or 2001:db8:0:0:0::1",
+      "properties": {
+        "apiVersion": {
+          "description": "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",
+          "type": "string"
+        },
+        "kind": {
+          "description": "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",
+          "type": "string"
+        },
+        "metadata": {
+          "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta",
+          "description": "Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata"
+        },
+        "spec": {
+          "$ref": "#/definitions/io.k8s.api.networking.v1alpha1.IPAddressSpec",
+          "description": "spec is the desired state of the IPAddress. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status"
+        }
+      },
+      "type": "object",
+      "x-kubernetes-group-version-kind": [
+        {
+          "group": "networking.k8s.io",
+          "kind": "IPAddress",
+          "version": "v1alpha1"
+        }
+      ]
+    },
+    "io.k8s.api.networking.v1alpha1.IPAddressList": {
+      "description": "IPAddressList contains a list of IPAddress.",
+      "properties": {
+        "apiVersion": {
+          "description": "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",
+          "type": "string"
+        },
+        "items": {
+          "description": "items is the list of IPAddresses.",
+          "items": {
+            "$ref": "#/definitions/io.k8s.api.networking.v1alpha1.IPAddress"
+          },
+          "type": "array"
+        },
+        "kind": {
+          "description": "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",
+          "type": "string"
+        },
+        "metadata": {
+          "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta",
+          "description": "Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata"
+        }
+      },
+      "required": [
+        "items"
+      ],
+      "type": "object",
+      "x-kubernetes-group-version-kind": [
+        {
+          "group": "networking.k8s.io",
+          "kind": "IPAddressList",
+          "version": "v1alpha1"
+        }
+      ]
+    },
+    "io.k8s.api.networking.v1alpha1.IPAddressSpec": {
+      "description": "IPAddressSpec describe the attributes in an IP Address.",
+      "properties": {
+        "parentRef": {
+          "$ref": "#/definitions/io.k8s.api.networking.v1alpha1.ParentReference",
+          "description": "ParentRef references the resource that an IPAddress is attached to. An IPAddress must reference a parent object."
+        }
+      },
+      "type": "object"
+    },
+    "io.k8s.api.networking.v1alpha1.ParentReference": {
+      "description": "ParentReference describes a reference to a parent object.",
+      "properties": {
+        "group": {
+          "description": "Group is the group of the object being referenced.",
+          "type": "string"
+        },
+        "name": {
+          "description": "Name is the name of the object being referenced.",
+          "type": "string"
+        },
+        "namespace": {
+          "description": "Namespace is the namespace of the object being referenced.",
+          "type": "string"
+        },
+        "resource": {
+          "description": "Resource is the resource of the object being referenced.",
+          "type": "string"
+        },
+        "uid": {
+          "description": "UID is the uid of the object being referenced.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
     "io.k8s.api.node.v1.Overhead": {
       "description": "Overhead structure represents the resource overhead associated with running a pod.",
       "properties": {
@@ -12155,7 +12601,7 @@
           "additionalProperties": {
             "$ref": "#/definitions/io.k8s.apimachinery.pkg.api.resource.Quantity"
           },
-          "description": "PodFixed represents the fixed resource overhead associated with running a pod.",
+          "description": "podFixed represents the fixed resource overhead associated with running a pod.",
           "type": "object"
         }
       },
@@ -12169,7 +12615,7 @@
           "type": "string"
         },
         "handler": {
-          "description": "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 & 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 \"runc\" 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.",
+          "description": "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 & 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 \"runc\" 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.",
           "type": "string"
         },
         "kind": {
@@ -12182,11 +12628,11 @@
         },
         "overhead": {
           "$ref": "#/definitions/io.k8s.api.node.v1.Overhead",
-          "description": "Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, see\n https://kubernetes.io/docs/concepts/scheduling-eviction/pod-overhead/"
+          "description": "overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, see\n https://kubernetes.io/docs/concepts/scheduling-eviction/pod-overhead/"
         },
         "scheduling": {
           "$ref": "#/definitions/io.k8s.api.node.v1.Scheduling",
-          "description": "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."
+          "description": "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."
         }
       },
       "required": [
@@ -12209,7 +12655,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Items is a list of schema objects.",
+          "description": "items is a list of schema objects.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.node.v1.RuntimeClass"
           },
@@ -12372,7 +12818,7 @@
           "x-kubernetes-patch-strategy": "replace"
         },
         "unhealthyPodEvictionPolicy": {
-          "description": "UnhealthyPodEvictionPolicy defines the criteria for when unhealthy pods should be considered for eviction. Current implementation considers healthy pods, as pods that have status.conditions item with type=\"Ready\",status=\"True\".\n\nValid policies are IfHealthyBudget and AlwaysAllow. If no policy is specified, the default behavior will be used, which corresponds to the IfHealthyBudget policy.\n\nIfHealthyBudget policy means that running pods (status.phase=\"Running\"), but not yet healthy can be evicted only if the guarded application is not disrupted (status.currentHealthy is at least equal to status.desiredHealthy). Healthy pods will be subject to the PDB for eviction.\n\nAlwaysAllow policy means that all running pods (status.phase=\"Running\"), but not yet healthy are considered disrupted and can be evicted regardless of whether the criteria in a PDB is met. This means perspective running pods of a disrupted application might not get a chance to become healthy. Healthy pods will be subject to the PDB for eviction.\n\nAdditional policies may be added in the future. Clients making eviction decisions should disallow eviction of unhealthy pods if they encounter an unrecognized policy in this field.\n\nThis field is alpha-level. The eviction API uses this field when the feature gate PDBUnhealthyPodEvictionPolicy is enabled (disabled by default).",
+          "description": "UnhealthyPodEvictionPolicy defines the criteria for when unhealthy pods should be considered for eviction. Current implementation considers healthy pods, as pods that have status.conditions item with type=\"Ready\",status=\"True\".\n\nValid policies are IfHealthyBudget and AlwaysAllow. If no policy is specified, the default behavior will be used, which corresponds to the IfHealthyBudget policy.\n\nIfHealthyBudget policy means that running pods (status.phase=\"Running\"), but not yet healthy can be evicted only if the guarded application is not disrupted (status.currentHealthy is at least equal to status.desiredHealthy). Healthy pods will be subject to the PDB for eviction.\n\nAlwaysAllow policy means that all running pods (status.phase=\"Running\"), but not yet healthy are considered disrupted and can be evicted regardless of whether the criteria in a PDB is met. This means perspective running pods of a disrupted application might not get a chance to become healthy. Healthy pods will be subject to the PDB for eviction.\n\nAdditional policies may be added in the future. Clients making eviction decisions should disallow eviction of unhealthy pods if they encounter an unrecognized policy in this field.\n\nThis field is beta-level. The eviction API uses this field when the feature gate PDBUnhealthyPodEvictionPolicy is enabled (enabled by default).",
           "type": "string"
         }
       },
@@ -12829,16 +13275,20 @@
       "type": "object",
       "x-kubernetes-map-type": "atomic"
     },
-    "io.k8s.api.resource.v1alpha1.AllocationResult": {
-      "description": "AllocationResult contains attributed of an allocated resource.",
+    "io.k8s.api.resource.v1alpha2.AllocationResult": {
+      "description": "AllocationResult contains attributes of an allocated resource.",
       "properties": {
         "availableOnNodes": {
           "$ref": "#/definitions/io.k8s.api.core.v1.NodeSelector",
-          "description": "This field will get set by the resource driver after it has allocated the resource driver to inform the scheduler where it can schedule Pods using the ResourceClaim.\n\nSetting this field is optional. If null, the resource is available everywhere."
+          "description": "This field will get set by the resource driver after it has allocated the resource to inform the scheduler where it can schedule Pods using the ResourceClaim.\n\nSetting this field is optional. If null, the resource is available everywhere."
         },
-        "resourceHandle": {
-          "description": "ResourceHandle contains arbitrary data returned by the driver after a successful allocation. This is opaque for Kubernetes. Driver documentation may explain to users how to interpret this data if needed.\n\nThe maximum size of this field is 16KiB. This may get increased in the future, but not reduced.",
-          "type": "string"
+        "resourceHandles": {
+          "description": "ResourceHandles contain the state associated with an allocation that should be maintained throughout the lifetime of a claim. Each ResourceHandle contains data that should be passed to a specific kubelet plugin once it lands on a node. This data is returned by the driver after a successful allocation and is opaque to Kubernetes. Driver documentation may explain to users how to interpret this data if needed.\n\nSetting this field is optional. It has a maximum size of 32 entries. If null (or empty), it is assumed this allocation will be processed by a single kubelet plugin with no ResourceHandle data attached. The name of the kubelet plugin invoked will match the DriverName set in the ResourceClaimStatus this AllocationResult is embedded in.",
+          "items": {
+            "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceHandle"
+          },
+          "type": "array",
+          "x-kubernetes-list-type": "atomic"
         },
         "shareable": {
           "description": "Shareable determines whether the resource supports more than one consumer at a time.",
@@ -12847,8 +13297,8 @@
       },
       "type": "object"
     },
-    "io.k8s.api.resource.v1alpha1.PodScheduling": {
-      "description": "PodScheduling objects hold information that is needed to schedule a Pod with ResourceClaims that use \"WaitForFirstConsumer\" allocation mode.\n\nThis is an alpha type and requires enabling the DynamicResourceAllocation feature gate.",
+    "io.k8s.api.resource.v1alpha2.PodSchedulingContext": {
+      "description": "PodSchedulingContext objects hold information that is needed to schedule a Pod with ResourceClaims that use \"WaitForFirstConsumer\" allocation mode.\n\nThis is an alpha type and requires enabling the DynamicResourceAllocation feature gate.",
       "properties": {
         "apiVersion": {
           "description": "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",
@@ -12863,11 +13313,11 @@
           "description": "Standard object metadata"
         },
         "spec": {
-          "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodSchedulingSpec",
+          "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContextSpec",
           "description": "Spec describes where resources for the Pod are needed."
         },
         "status": {
-          "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodSchedulingStatus",
+          "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContextStatus",
           "description": "Status describes where resources for the Pod can be allocated."
         }
       },
@@ -12878,22 +13328,22 @@
       "x-kubernetes-group-version-kind": [
         {
           "group": "resource.k8s.io",
-          "kind": "PodScheduling",
-          "version": "v1alpha1"
+          "kind": "PodSchedulingContext",
+          "version": "v1alpha2"
         }
       ]
     },
-    "io.k8s.api.resource.v1alpha1.PodSchedulingList": {
-      "description": "PodSchedulingList is a collection of Pod scheduling objects.",
+    "io.k8s.api.resource.v1alpha2.PodSchedulingContextList": {
+      "description": "PodSchedulingContextList is a collection of Pod scheduling objects.",
       "properties": {
         "apiVersion": {
           "description": "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",
           "type": "string"
         },
         "items": {
-          "description": "Items is the list of PodScheduling objects.",
+          "description": "Items is the list of PodSchedulingContext objects.",
           "items": {
-            "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodScheduling"
+            "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContext"
           },
           "type": "array"
         },
@@ -12913,13 +13363,13 @@
       "x-kubernetes-group-version-kind": [
         {
           "group": "resource.k8s.io",
-          "kind": "PodSchedulingList",
-          "version": "v1alpha1"
+          "kind": "PodSchedulingContextList",
+          "version": "v1alpha2"
         }
       ]
     },
-    "io.k8s.api.resource.v1alpha1.PodSchedulingSpec": {
-      "description": "PodSchedulingSpec describes where resources for the Pod are needed.",
+    "io.k8s.api.resource.v1alpha2.PodSchedulingContextSpec": {
+      "description": "PodSchedulingContextSpec describes where resources for the Pod are needed.",
       "properties": {
         "potentialNodes": {
           "description": "PotentialNodes lists nodes where the Pod might be able to run.\n\nThe size of this field is limited to 128. This is large enough for many clusters. Larger clusters may need more attempts to find a node that suits all pending resources. This may get increased in the future, but not reduced.",
@@ -12936,13 +13386,13 @@
       },
       "type": "object"
     },
-    "io.k8s.api.resource.v1alpha1.PodSchedulingStatus": {
-      "description": "PodSchedulingStatus describes where resources for the Pod can be allocated.",
+    "io.k8s.api.resource.v1alpha2.PodSchedulingContextStatus": {
+      "description": "PodSchedulingContextStatus describes where resources for the Pod can be allocated.",
       "properties": {
         "resourceClaims": {
           "description": "ResourceClaims describes resource availability for each pod.spec.resourceClaim entry where the corresponding ResourceClaim uses \"WaitForFirstConsumer\" allocation mode.",
           "items": {
-            "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimSchedulingStatus"
+            "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimSchedulingStatus"
           },
           "type": "array",
           "x-kubernetes-list-map-keys": [
@@ -12953,7 +13403,7 @@
       },
       "type": "object"
     },
-    "io.k8s.api.resource.v1alpha1.ResourceClaim": {
+    "io.k8s.api.resource.v1alpha2.ResourceClaim": {
       "description": "ResourceClaim describes which resources are needed by a resource consumer. Its status tracks whether the resource has been allocated and what the resulting attributes are.\n\nThis is an alpha type and requires enabling the DynamicResourceAllocation feature gate.",
       "properties": {
         "apiVersion": {
@@ -12969,11 +13419,11 @@
           "description": "Standard object metadata"
         },
         "spec": {
-          "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimSpec",
+          "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimSpec",
           "description": "Spec describes the desired attributes of a resource that then needs to be allocated. It can only be set once when creating the ResourceClaim."
         },
         "status": {
-          "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimStatus",
+          "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimStatus",
           "description": "Status describes whether the resource is available and with which attributes."
         }
       },
@@ -12985,11 +13435,11 @@
         {
           "group": "resource.k8s.io",
           "kind": "ResourceClaim",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       ]
     },
-    "io.k8s.api.resource.v1alpha1.ResourceClaimConsumerReference": {
+    "io.k8s.api.resource.v1alpha2.ResourceClaimConsumerReference": {
       "description": "ResourceClaimConsumerReference contains enough information to let you locate the consumer of a ResourceClaim. The user must be a resource in the same namespace as the ResourceClaim.",
       "properties": {
         "apiGroup": {
@@ -13016,7 +13466,7 @@
       ],
       "type": "object"
     },
-    "io.k8s.api.resource.v1alpha1.ResourceClaimList": {
+    "io.k8s.api.resource.v1alpha2.ResourceClaimList": {
       "description": "ResourceClaimList is a collection of claims.",
       "properties": {
         "apiVersion": {
@@ -13026,7 +13476,7 @@
         "items": {
           "description": "Items is the list of resource claims.",
           "items": {
-            "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaim"
+            "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaim"
           },
           "type": "array"
         },
@@ -13047,11 +13497,11 @@
         {
           "group": "resource.k8s.io",
           "kind": "ResourceClaimList",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       ]
     },
-    "io.k8s.api.resource.v1alpha1.ResourceClaimParametersReference": {
+    "io.k8s.api.resource.v1alpha2.ResourceClaimParametersReference": {
       "description": "ResourceClaimParametersReference contains enough information to let you locate the parameters for a ResourceClaim. The object must be in the same namespace as the ResourceClaim.",
       "properties": {
         "apiGroup": {
@@ -13073,7 +13523,7 @@
       ],
       "type": "object"
     },
-    "io.k8s.api.resource.v1alpha1.ResourceClaimSchedulingStatus": {
+    "io.k8s.api.resource.v1alpha2.ResourceClaimSchedulingStatus": {
       "description": "ResourceClaimSchedulingStatus contains information about one particular ResourceClaim with \"WaitForFirstConsumer\" allocation mode.",
       "properties": {
         "name": {
@@ -13091,7 +13541,7 @@
       },
       "type": "object"
     },
-    "io.k8s.api.resource.v1alpha1.ResourceClaimSpec": {
+    "io.k8s.api.resource.v1alpha2.ResourceClaimSpec": {
       "description": "ResourceClaimSpec defines how a resource is to be allocated.",
       "properties": {
         "allocationMode": {
@@ -13099,7 +13549,7 @@
           "type": "string"
         },
         "parametersRef": {
-          "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimParametersReference",
+          "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimParametersReference",
           "description": "ParametersRef references a separate object with arbitrary parameters that will be used by the driver when allocating a resource for the claim.\n\nThe object must be in the same namespace as the ResourceClaim."
         },
         "resourceClassName": {
@@ -13112,12 +13562,12 @@
       ],
       "type": "object"
     },
-    "io.k8s.api.resource.v1alpha1.ResourceClaimStatus": {
+    "io.k8s.api.resource.v1alpha2.ResourceClaimStatus": {
       "description": "ResourceClaimStatus tracks whether the resource has been allocated and what the resulting attributes are.",
       "properties": {
         "allocation": {
-          "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.AllocationResult",
-          "description": "Allocation is set by the resource driver once a resource has been allocated successfully. If this is not specified, the resource is not yet allocated."
+          "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.AllocationResult",
+          "description": "Allocation is set by the resource driver once a resource or set of resources has been allocated successfully. If this is not specified, the resources have not been allocated yet."
         },
         "deallocationRequested": {
           "description": "DeallocationRequested indicates that a ResourceClaim is to be deallocated.\n\nThe driver then must deallocate this claim and reset the field together with clearing the Allocation field.\n\nWhile DeallocationRequested is set, no new consumers may be added to ReservedFor.",
@@ -13130,15 +13580,18 @@
         "reservedFor": {
           "description": "ReservedFor indicates which entities are currently allowed to use the claim. A Pod which references a ResourceClaim which is not reserved for that Pod will not be started.\n\nThere can be at most 32 such reservations. This may get increased in the future, but not reduced.",
           "items": {
-            "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimConsumerReference"
+            "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimConsumerReference"
           },
           "type": "array",
-          "x-kubernetes-list-type": "set"
+          "x-kubernetes-list-map-keys": [
+            "uid"
+          ],
+          "x-kubernetes-list-type": "map"
         }
       },
       "type": "object"
     },
-    "io.k8s.api.resource.v1alpha1.ResourceClaimTemplate": {
+    "io.k8s.api.resource.v1alpha2.ResourceClaimTemplate": {
       "description": "ResourceClaimTemplate is used to produce ResourceClaim objects.",
       "properties": {
         "apiVersion": {
@@ -13154,7 +13607,7 @@
           "description": "Standard object metadata"
         },
         "spec": {
-          "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimTemplateSpec",
+          "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimTemplateSpec",
           "description": "Describes the ResourceClaim that is to be generated.\n\nThis field is immutable. A ResourceClaim will get created by the control plane for a Pod when needed and then not get updated anymore."
         }
       },
@@ -13166,11 +13619,11 @@
         {
           "group": "resource.k8s.io",
           "kind": "ResourceClaimTemplate",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       ]
     },
-    "io.k8s.api.resource.v1alpha1.ResourceClaimTemplateList": {
+    "io.k8s.api.resource.v1alpha2.ResourceClaimTemplateList": {
       "description": "ResourceClaimTemplateList is a collection of claim templates.",
       "properties": {
         "apiVersion": {
@@ -13180,7 +13633,7 @@
         "items": {
           "description": "Items is the list of resource claim templates.",
           "items": {
-            "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimTemplate"
+            "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimTemplate"
           },
           "type": "array"
         },
@@ -13201,11 +13654,11 @@
         {
           "group": "resource.k8s.io",
           "kind": "ResourceClaimTemplateList",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       ]
     },
-    "io.k8s.api.resource.v1alpha1.ResourceClaimTemplateSpec": {
+    "io.k8s.api.resource.v1alpha2.ResourceClaimTemplateSpec": {
       "description": "ResourceClaimTemplateSpec contains the metadata and fields for a ResourceClaim.",
       "properties": {
         "metadata": {
@@ -13213,7 +13666,7 @@
           "description": "ObjectMeta 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."
         },
         "spec": {
-          "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimSpec",
+          "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimSpec",
           "description": "Spec for the ResourceClaim. The entire content is copied unchanged into the ResourceClaim that gets created from this template. The same fields as in a ResourceClaim are also valid here."
         }
       },
@@ -13222,7 +13675,7 @@
       ],
       "type": "object"
     },
-    "io.k8s.api.resource.v1alpha1.ResourceClass": {
+    "io.k8s.api.resource.v1alpha2.ResourceClass": {
       "description": "ResourceClass is used by administrators to influence how resources are allocated.\n\nThis is an alpha type and requires enabling the DynamicResourceAllocation feature gate.",
       "properties": {
         "apiVersion": {
@@ -13242,7 +13695,7 @@
           "description": "Standard object metadata"
         },
         "parametersRef": {
-          "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClassParametersReference",
+          "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClassParametersReference",
           "description": "ParametersRef references an arbitrary separate object that may hold parameters that will be used by the driver when allocating a resource that uses this class. A dynamic resource driver can distinguish between parameters stored here and and those stored in ResourceClaimSpec."
         },
         "suitableNodes": {
@@ -13258,11 +13711,11 @@
         {
           "group": "resource.k8s.io",
           "kind": "ResourceClass",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       ]
     },
-    "io.k8s.api.resource.v1alpha1.ResourceClassList": {
+    "io.k8s.api.resource.v1alpha2.ResourceClassList": {
       "description": "ResourceClassList is a collection of classes.",
       "properties": {
         "apiVersion": {
@@ -13272,7 +13725,7 @@
         "items": {
           "description": "Items is the list of resource classes.",
           "items": {
-            "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClass"
+            "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClass"
           },
           "type": "array"
         },
@@ -13293,11 +13746,11 @@
         {
           "group": "resource.k8s.io",
           "kind": "ResourceClassList",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       ]
     },
-    "io.k8s.api.resource.v1alpha1.ResourceClassParametersReference": {
+    "io.k8s.api.resource.v1alpha2.ResourceClassParametersReference": {
       "description": "ResourceClassParametersReference contains enough information to let you locate the parameters for a ResourceClass.",
       "properties": {
         "apiGroup": {
@@ -13323,6 +13776,20 @@
       ],
       "type": "object"
     },
+    "io.k8s.api.resource.v1alpha2.ResourceHandle": {
+      "description": "ResourceHandle holds opaque resource data for processing by a specific kubelet plugin.",
+      "properties": {
+        "data": {
+          "description": "Data contains the opaque data associated with this ResourceHandle. It is set by the controller component of the resource driver whose name matches the DriverName set in the ResourceClaimStatus this ResourceHandle is embedded in. It is set at allocation time and is intended for processing by the kubelet plugin whose name matches the DriverName set in this ResourceHandle.\n\nThe maximum size of this field is 16KiB. This may get increased in the future, but not reduced.",
+          "type": "string"
+        },
+        "driverName": {
+          "description": "DriverName specifies the name of the resource driver whose kubelet plugin should be invoked to process this ResourceHandle's data once it lands on a node. This may differ from the DriverName set in ResourceClaimStatus this ResourceHandle is embedded in.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
     "io.k8s.api.scheduling.v1.PriorityClass": {
       "description": "PriorityClass defines mapping from a priority class name to the priority integer value. The value can be any valid integer.",
       "properties": {
@@ -13347,11 +13814,11 @@
           "description": "Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata"
         },
         "preemptionPolicy": {
-          "description": "PreemptionPolicy is the Policy for preempting pods with lower priority. One of Never, PreemptLowerPriority. Defaults to PreemptLowerPriority if unset.",
+          "description": "preemptionPolicy is the Policy for preempting pods with lower priority. One of Never, PreemptLowerPriority. Defaults to PreemptLowerPriority if unset.",
           "type": "string"
         },
         "value": {
-          "description": "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.",
+          "description": "value represents the integer 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.",
           "format": "int32",
           "type": "integer"
         }
@@ -13420,7 +13887,7 @@
         },
         "spec": {
           "$ref": "#/definitions/io.k8s.api.storage.v1.CSIDriverSpec",
-          "description": "Specification of the CSI Driver."
+          "description": "spec represents the specification of the CSI Driver."
         }
       },
       "required": [
@@ -13478,27 +13945,27 @@
           "type": "boolean"
         },
         "fsGroupPolicy": {
-          "description": "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.\n\nThis field is immutable.\n\nDefaults 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's access mode contains ReadWriteOnce.",
+          "description": "fsGroupPolicy 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.\n\nThis field is immutable.\n\nDefaults 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's access mode contains ReadWriteOnce.",
           "type": "string"
         },
         "podInfoOnMount": {
-          "description": "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. \"csi.storage.k8s.io/pod.name\": pod.Name \"csi.storage.k8s.io/pod.namespace\": pod.Namespace \"csi.storage.k8s.io/pod.uid\": string(pod.UID) \"csi.storage.k8s.io/ephemeral\": \"true\" if the volume is an ephemeral inline volume\n                                defined by a CSIVolumeSource, otherwise \"false\"\n\n\"csi.storage.k8s.io/ephemeral\" is a new feature in Kubernetes 1.16. It is only required for drivers which support both the \"Persistent\" and \"Ephemeral\" VolumeLifecycleMode. Other drivers can leave pod info disabled and/or ignore this field. As Kubernetes 1.15 doesn'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.\n\nThis field is immutable.",
+          "description": "podInfoOnMount indicates this CSI volume driver requires additional pod information (like podName, podUID, etc.) during mount operations, if set to true. If set to false, pod information will not be passed on mount. Default is false.\n\nThe 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.\n\nThe following VolumeConext will be passed if podInfoOnMount is set to true. This list might grow, but the prefix will be used. \"csi.storage.k8s.io/pod.name\": pod.Name \"csi.storage.k8s.io/pod.namespace\": pod.Namespace \"csi.storage.k8s.io/pod.uid\": string(pod.UID) \"csi.storage.k8s.io/ephemeral\": \"true\" if the volume is an ephemeral inline volume\n                                defined by a CSIVolumeSource, otherwise \"false\"\n\n\"csi.storage.k8s.io/ephemeral\" is a new feature in Kubernetes 1.16. It is only required for drivers which support both the \"Persistent\" and \"Ephemeral\" VolumeLifecycleMode. Other drivers can leave pod info disabled and/or ignore this field. As Kubernetes 1.15 doesn'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.\n\nThis field is immutable.",
           "type": "boolean"
         },
         "requiresRepublish": {
-          "description": "RequiresRepublish indicates the CSI driver wants `NodePublishVolume` being periodically called to reflect any possible change in the mounted volume. This field defaults to false.\n\nNote: 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.",
+          "description": "requiresRepublish indicates the CSI driver wants `NodePublishVolume` being periodically called to reflect any possible change in the mounted volume. This field defaults to false.\n\nNote: 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.",
           "type": "boolean"
         },
         "seLinuxMount": {
-          "description": "SELinuxMount specifies if the CSI driver supports \"-o context\" mount option.\n\nWhen \"true\", the CSI driver must ensure that all volumes provided by this CSI driver can be mounted separately with different `-o context` options. This is typical for storage backends that provide volumes as filesystems on block devices or as independent shared volumes. Kubernetes will call NodeStage / NodePublish with \"-o context=xyz\" mount option when mounting a ReadWriteOncePod volume used in Pod that has explicitly set SELinux context. In the future, it may be expanded to other volume AccessModes. In any case, Kubernetes will ensure that the volume is mounted only with a single SELinux context.\n\nWhen \"false\", Kubernetes won't pass any special SELinux mount options to the driver. This is typical for volumes that represent subdirectories of a bigger shared filesystem.\n\nDefault is \"false\".",
+          "description": "seLinuxMount specifies if the CSI driver supports \"-o context\" mount option.\n\nWhen \"true\", the CSI driver must ensure that all volumes provided by this CSI driver can be mounted separately with different `-o context` options. This is typical for storage backends that provide volumes as filesystems on block devices or as independent shared volumes. Kubernetes will call NodeStage / NodePublish with \"-o context=xyz\" mount option when mounting a ReadWriteOncePod volume used in Pod that has explicitly set SELinux context. In the future, it may be expanded to other volume AccessModes. In any case, Kubernetes will ensure that the volume is mounted only with a single SELinux context.\n\nWhen \"false\", Kubernetes won't pass any special SELinux mount options to the driver. This is typical for volumes that represent subdirectories of a bigger shared filesystem.\n\nDefault is \"false\".",
           "type": "boolean"
         },
         "storageCapacity": {
-          "description": "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.\n\nThe 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.\n\nAlternatively, the driver can be deployed with the field unset or false and it can be flipped later when storage capacity information has been published.\n\nThis field was immutable in Kubernetes <= 1.22 and now is mutable.",
+          "description": "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, if set to true.\n\nThe 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.\n\nAlternatively, the driver can be deployed with the field unset or false and it can be flipped later when storage capacity information has been published.\n\nThis field was immutable in Kubernetes <= 1.22 and now is mutable.",
           "type": "boolean"
         },
         "tokenRequests": {
-          "description": "TokenRequests indicates the CSI driver needs pods' 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: \"csi.storage.k8s.io/serviceAccount.tokens\": {\n  \"<audience>\": {\n    \"token\": <token>,\n    \"expirationTimestamp\": <expiration timestamp in RFC3339>,\n  },\n  ...\n}\n\nNote: 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.",
+          "description": "tokenRequests indicates the CSI driver needs pods' 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: \"csi.storage.k8s.io/serviceAccount.tokens\": {\n  \"<audience>\": {\n    \"token\": <token>,\n    \"expirationTimestamp\": <expiration timestamp in RFC3339>,\n  },\n  ...\n}\n\nNote: 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.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.storage.v1.TokenRequest"
           },
@@ -13506,7 +13973,7 @@
           "x-kubernetes-list-type": "atomic"
         },
         "volumeLifecycleModes": {
-          "description": "volumeLifecycleModes defines what kind of volumes this CSI volume driver supports. The default if the list is empty is \"Persistent\", which is the usage defined by the CSI specification and implemented in Kubernetes via the usual PV/PVC mechanism. The other mode is \"Ephemeral\". 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.\n\nThis field is immutable.",
+          "description": "volumeLifecycleModes defines what kind of volumes this CSI volume driver supports. The default if the list is empty is \"Persistent\", which is the usage defined by the CSI specification and implemented in Kubernetes via the usual PV/PVC mechanism.\n\nThe other mode is \"Ephemeral\". 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.\n\nFor 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.\n\nThis field is beta. This field is immutable.",
           "items": {
             "type": "string"
           },
@@ -13529,7 +13996,7 @@
         },
         "metadata": {
           "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta",
-          "description": "metadata.name must be the Kubernetes node name."
+          "description": "Standard object's metadata. metadata.name must be the Kubernetes node name."
         },
         "spec": {
           "$ref": "#/definitions/io.k8s.api.storage.v1.CSINodeSpec",
@@ -13556,7 +14023,7 @@
           "description": "allocatable represents the volume resources of a node that are available for scheduling. This field is beta."
         },
         "name": {
-          "description": "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.",
+          "description": "name represents 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.",
           "type": "string"
         },
         "nodeID": {
@@ -13639,7 +14106,7 @@
         },
         "capacity": {
           "$ref": "#/definitions/io.k8s.apimachinery.pkg.api.resource.Quantity",
-          "description": "Capacity is the value reported by the CSI driver in its GetCapacityResponse for a GetCapacityRequest with topology and parameters that match the previous fields.\n\nThe 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."
+          "description": "capacity is the value reported by the CSI driver in its GetCapacityResponse for a GetCapacityRequest with topology and parameters that match the previous fields.\n\nThe 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."
         },
         "kind": {
           "description": "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",
@@ -13647,18 +14114,18 @@
         },
         "maximumVolumeSize": {
           "$ref": "#/definitions/io.k8s.apimachinery.pkg.api.resource.Quantity",
-          "description": "MaximumVolumeSize is the value reported by the CSI driver in its GetCapacityResponse for a GetCapacityRequest with topology and parameters that match the previous fields.\n\nThis 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."
+          "description": "maximumVolumeSize is the value reported by the CSI driver in its GetCapacityResponse for a GetCapacityRequest with topology and parameters that match the previous fields.\n\nThis 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."
         },
         "metadata": {
           "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta",
-          "description": "Standard object'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-<uuid>, a generated name, or a reverse-domain name which ends with the unique CSI driver name.\n\nObjects are namespaced.\n\nMore info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata"
+          "description": "Standard object's metadata. The name has no particular meaning. It must 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-<uuid>, a generated name, or a reverse-domain name which ends with the unique CSI driver name.\n\nObjects are namespaced.\n\nMore info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata"
         },
         "nodeTopology": {
           "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelector",
-          "description": "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."
+          "description": "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."
         },
         "storageClassName": {
-          "description": "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.",
+          "description": "storageClassName represents 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.",
           "type": "string"
         }
       },
@@ -13682,7 +14149,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Items is the list of CSIStorageCapacity objects.",
+          "description": "items is the list of CSIStorageCapacity objects.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.storage.v1.CSIStorageCapacity"
           },
@@ -13717,11 +14184,11 @@
       "description": "StorageClass describes the parameters for a class of storage for which PersistentVolumes can be dynamically provisioned.\n\nStorageClasses are non-namespaced; the name of the storage class according to etcd is in ObjectMeta.Name.",
       "properties": {
         "allowVolumeExpansion": {
-          "description": "AllowVolumeExpansion shows whether the storage class allow volume expand",
+          "description": "allowVolumeExpansion shows whether the storage class allow volume expand.",
           "type": "boolean"
         },
         "allowedTopologies": {
-          "description": "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.",
+          "description": "allowedTopologies 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.",
           "items": {
             "$ref": "#/definitions/io.k8s.api.core.v1.TopologySelectorTerm"
           },
@@ -13741,7 +14208,7 @@
           "description": "Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata"
         },
         "mountOptions": {
-          "description": "Dynamically provisioned PersistentVolumes of this storage class are created with these mountOptions, e.g. [\"ro\", \"soft\"]. Not validated - mount of the PVs will simply fail if one is invalid.",
+          "description": "mountOptions controls the mountOptions for dynamically provisioned PersistentVolumes of this storage class. e.g. [\"ro\", \"soft\"]. Not validated - mount of the PVs will simply fail if one is invalid.",
           "items": {
             "type": "string"
           },
@@ -13751,19 +14218,19 @@
           "additionalProperties": {
             "type": "string"
           },
-          "description": "Parameters holds the parameters for the provisioner that should create volumes of this storage class.",
+          "description": "parameters holds the parameters for the provisioner that should create volumes of this storage class.",
           "type": "object"
         },
         "provisioner": {
-          "description": "Provisioner indicates the type of the provisioner.",
+          "description": "provisioner indicates the type of the provisioner.",
           "type": "string"
         },
         "reclaimPolicy": {
-          "description": "Dynamically provisioned PersistentVolumes of this storage class are created with this reclaimPolicy. Defaults to Delete.",
+          "description": "reclaimPolicy controls the reclaimPolicy for dynamically provisioned PersistentVolumes of this storage class. Defaults to Delete.",
           "type": "string"
         },
         "volumeBindingMode": {
-          "description": "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.",
+          "description": "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.",
           "type": "string"
         }
       },
@@ -13787,7 +14254,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Items is the list of StorageClasses",
+          "description": "items is the list of StorageClasses",
           "items": {
             "$ref": "#/definitions/io.k8s.api.storage.v1.StorageClass"
           },
@@ -13818,11 +14285,11 @@
       "description": "TokenRequest contains parameters of a service account token.",
       "properties": {
         "audience": {
-          "description": "Audience is the intended audience of the token in \"TokenRequestSpec\". It will default to the audiences of kube apiserver.",
+          "description": "audience is the intended audience of the token in \"TokenRequestSpec\". It will default to the audiences of kube apiserver.",
           "type": "string"
         },
         "expirationSeconds": {
-          "description": "ExpirationSeconds is the duration of validity of the token in \"TokenRequestSpec\". It has the same default value of \"ExpirationSeconds\" in \"TokenRequestSpec\".",
+          "description": "expirationSeconds is the duration of validity of the token in \"TokenRequestSpec\". It has the same default value of \"ExpirationSeconds\" in \"TokenRequestSpec\".",
           "format": "int64",
           "type": "integer"
         }
@@ -13849,11 +14316,11 @@
         },
         "spec": {
           "$ref": "#/definitions/io.k8s.api.storage.v1.VolumeAttachmentSpec",
-          "description": "Specification of the desired attach/detach volume behavior. Populated by the Kubernetes system."
+          "description": "spec represents specification of the desired attach/detach volume behavior. Populated by the Kubernetes system."
         },
         "status": {
           "$ref": "#/definitions/io.k8s.api.storage.v1.VolumeAttachmentStatus",
-          "description": "Status of the VolumeAttachment request. Populated by the entity completing the attach or detach operation, i.e. the external-attacher."
+          "description": "status represents status of the VolumeAttachment request. Populated by the entity completing the attach or detach operation, i.e. the external-attacher."
         }
       },
       "required": [
@@ -13876,7 +14343,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Items is the list of VolumeAttachments",
+          "description": "items is the list of VolumeAttachments",
           "items": {
             "$ref": "#/definitions/io.k8s.api.storage.v1.VolumeAttachment"
           },
@@ -13911,7 +14378,7 @@
           "description": "inlineVolumeSpec contains all the information necessary to attach a persistent volume defined by a pod's inline VolumeSource. This field is populated only for the CSIMigration feature. It contains translated fields from a pod's inline VolumeSource to a PersistentVolumeSpec. This field is beta-level and is only honored by servers that enabled the CSIMigration feature."
         },
         "persistentVolumeName": {
-          "description": "Name of the persistent volume to attach.",
+          "description": "persistentVolumeName represents the name of the persistent volume to attach.",
           "type": "string"
         }
       },
@@ -13921,16 +14388,16 @@
       "description": "VolumeAttachmentSpec is the specification of a VolumeAttachment request.",
       "properties": {
         "attacher": {
-          "description": "Attacher indicates the name of the volume driver that MUST handle this request. This is the name returned by GetPluginName().",
+          "description": "attacher indicates the name of the volume driver that MUST handle this request. This is the name returned by GetPluginName().",
           "type": "string"
         },
         "nodeName": {
-          "description": "The node that the volume should be attached to.",
+          "description": "nodeName represents the node that the volume should be attached to.",
           "type": "string"
         },
         "source": {
           "$ref": "#/definitions/io.k8s.api.storage.v1.VolumeAttachmentSource",
-          "description": "Source represents the volume that should be attached."
+          "description": "source represents the volume that should be attached."
         }
       },
       "required": [
@@ -13945,22 +14412,22 @@
       "properties": {
         "attachError": {
           "$ref": "#/definitions/io.k8s.api.storage.v1.VolumeError",
-          "description": "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."
+          "description": "attachError represents 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."
         },
         "attached": {
-          "description": "Indicates the volume is successfully attached. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.",
+          "description": "attached indicates the volume is successfully attached. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.",
           "type": "boolean"
         },
         "attachmentMetadata": {
           "additionalProperties": {
             "type": "string"
           },
-          "description": "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.",
+          "description": "attachmentMetadata is populated with any information returned by the attach operation, upon successful attach, 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.",
           "type": "object"
         },
         "detachError": {
           "$ref": "#/definitions/io.k8s.api.storage.v1.VolumeError",
-          "description": "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."
+          "description": "detachError represents 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."
         }
       },
       "required": [
@@ -13972,12 +14439,12 @@
       "description": "VolumeError captures an error encountered during a volume operation.",
       "properties": {
         "message": {
-          "description": "String detailing the error encountered during Attach or Detach operation. This string may be logged, so it should not contain sensitive information.",
+          "description": "message represents the error encountered during Attach or Detach operation. This string may be logged, so it should not contain sensitive information.",
           "type": "string"
         },
         "time": {
           "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time",
-          "description": "Time the error was encountered."
+          "description": "time represents the time the error was encountered."
         }
       },
       "type": "object"
@@ -13986,96 +14453,13 @@
       "description": "VolumeNodeResources is a set of resource limits for scheduling of volumes.",
       "properties": {
         "count": {
-          "description": "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.",
+          "description": "count indicates the 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.",
           "format": "int32",
           "type": "integer"
         }
       },
       "type": "object"
     },
-    "io.k8s.api.storage.v1beta1.CSIStorageCapacity": {
-      "description": "CSIStorageCapacity stores the result of one CSI GetCapacity call. For a given StorageClass, this describes the available capacity in a particular topology segment.  This can be used when considering where to instantiate new PersistentVolumes.\n\nFor example this can express things like: - StorageClass \"standard\" has \"1234 GiB\" available in \"topology.kubernetes.io/zone=us-east1\" - StorageClass \"localssd\" has \"10 GiB\" available in \"kubernetes.io/hostname=knode-abc123\"\n\nThe following three cases all imply that no capacity is available for a certain combination: - no object exists with suitable topology and storage class name - such an object exists, but the capacity is unset - such an object exists, but the capacity is zero\n\nThe producer of these objects can decide which approach is more suitable.\n\nThey are consumed by the kube-scheduler when a CSI driver opts into capacity-aware scheduling with CSIDriverSpec.StorageCapacity. The scheduler compares the MaximumVolumeSize against the requested size of pending volumes to filter out unsuitable nodes. If MaximumVolumeSize is unset, it falls back to a comparison against the less precise Capacity. If that is also unset, the scheduler assumes that capacity is insufficient and tries some other node.",
-      "properties": {
-        "apiVersion": {
-          "description": "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",
-          "type": "string"
-        },
-        "capacity": {
-          "$ref": "#/definitions/io.k8s.apimachinery.pkg.api.resource.Quantity",
-          "description": "Capacity is the value reported by the CSI driver in its GetCapacityResponse for a GetCapacityRequest with topology and parameters that match the previous fields.\n\nThe 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."
-        },
-        "kind": {
-          "description": "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",
-          "type": "string"
-        },
-        "maximumVolumeSize": {
-          "$ref": "#/definitions/io.k8s.apimachinery.pkg.api.resource.Quantity",
-          "description": "MaximumVolumeSize is the value reported by the CSI driver in its GetCapacityResponse for a GetCapacityRequest with topology and parameters that match the previous fields.\n\nThis 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."
-        },
-        "metadata": {
-          "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta",
-          "description": "Standard object'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-<uuid>, a generated name, or a reverse-domain name which ends with the unique CSI driver name.\n\nObjects are namespaced.\n\nMore info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata"
-        },
-        "nodeTopology": {
-          "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelector",
-          "description": "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."
-        },
-        "storageClassName": {
-          "description": "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.",
-          "type": "string"
-        }
-      },
-      "required": [
-        "storageClassName"
-      ],
-      "type": "object",
-      "x-kubernetes-group-version-kind": [
-        {
-          "group": "storage.k8s.io",
-          "kind": "CSIStorageCapacity",
-          "version": "v1beta1"
-        }
-      ]
-    },
-    "io.k8s.api.storage.v1beta1.CSIStorageCapacityList": {
-      "description": "CSIStorageCapacityList is a collection of CSIStorageCapacity objects.",
-      "properties": {
-        "apiVersion": {
-          "description": "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",
-          "type": "string"
-        },
-        "items": {
-          "description": "Items is the list of CSIStorageCapacity objects.",
-          "items": {
-            "$ref": "#/definitions/io.k8s.api.storage.v1beta1.CSIStorageCapacity"
-          },
-          "type": "array",
-          "x-kubernetes-list-map-keys": [
-            "name"
-          ],
-          "x-kubernetes-list-type": "map"
-        },
-        "kind": {
-          "description": "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",
-          "type": "string"
-        },
-        "metadata": {
-          "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta",
-          "description": "Standard list metadata More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata"
-        }
-      },
-      "required": [
-        "items"
-      ],
-      "type": "object",
-      "x-kubernetes-group-version-kind": [
-        {
-          "group": "storage.k8s.io",
-          "kind": "CSIStorageCapacityList",
-          "version": "v1beta1"
-        }
-      ]
-    },
     "io.k8s.apiextensions-apiserver.pkg.apis.apiextensions.v1.CustomResourceColumnDefinition": {
       "description": "CustomResourceColumnDefinition specifies a column for server side printing.",
       "properties": {
@@ -14116,12 +14500,12 @@
       "description": "CustomResourceConversion describes how to convert different versions of a CR.",
       "properties": {
         "strategy": {
-          "description": "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\n  is needed for this option. This requires spec.preserveUnknownFields to be false, and spec.conversion.webhook to be set.",
+          "description": "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\n  is needed for this option. This requires spec.preserveUnknownFields to be false, and spec.conversion.webhook to be set.",
           "type": "string"
         },
         "webhook": {
           "$ref": "#/definitions/io.k8s.apiextensions-apiserver.pkg.apis.apiextensions.v1.WebhookConversion",
-          "description": "webhook describes how to call the conversion webhook. Required when `strategy` is set to `Webhook`."
+          "description": "webhook describes how to call the conversion webhook. Required when `strategy` is set to `\"Webhook\"`."
         }
       },
       "required": [
@@ -14686,6 +15070,10 @@
           "description": "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 \"failed rule: {Rule}\". e.g. \"must be a URL with the host matching spec.host\"",
           "type": "string"
         },
+        "messageExpression": {
+          "description": "MessageExpression declares a CEL expression that evaluates to the validation failure message that is returned when this rule fails. Since messageExpression is used as a failure message, it must evaluate to a string. If both message and messageExpression are present on a rule, then messageExpression will be used if validation fails. If messageExpression results in a runtime error, the runtime error is logged, and the validation failure message is produced as if the messageExpression field were unset. If messageExpression evaluates to an empty string, a string with only spaces, or a string that contains line breaks, then the validation failure message will also be produced as if the messageExpression field were unset, and the fact that messageExpression produced an empty string/string with only spaces/string with line breaks will be logged. messageExpression has access to all the same variables as the rule; the only difference is the return type. Example: \"x must be less than max (\"+string(self.max)+\")\"",
+          "type": "string"
+        },
         "rule": {
           "description": "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: {\"rule\": \"self.status.actual <= self.spec.maxDesired\"}\n\nIf 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: {\"rule\": \"self.components['Widget'].priority < 10\"} - Rule scoped to a list of integers: {\"rule\": \"self.values.all(value, value >= 0 && value < 100)\"} - Rule scoped to a string value: {\"rule\": \"self.startsWith('kube')\"}\n\nThe `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.\n\nUnknown 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:\n  - A schema with no type and x-kubernetes-preserve-unknown-fields set to true\n  - An array where the items schema is of an \"unknown type\"\n  - An object where the additionalProperties schema is of an \"unknown type\"\n\nOnly 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: - '__' escapes to '__underscores__' - '.' escapes to '__dot__' - '-' escapes to '__dash__' - '/' escapes to '__slash__' - Property names that exactly match a CEL RESERVED keyword escape to '__{keyword}__'. The keywords are:\n\t  \"true\", \"false\", \"null\", \"in\", \"as\", \"break\", \"const\", \"continue\", \"else\", \"for\", \"function\", \"if\",\n\t  \"import\", \"let\", \"loop\", \"package\", \"namespace\", \"return\".\nExamples:\n  - Rule accessing a property named \"namespace\": {\"rule\": \"self.__namespace__ > 0\"}\n  - Rule accessing a property named \"x-prop\": {\"rule\": \"self.x__dash__prop > 0\"}\n  - Rule accessing a property named \"redact__d\": {\"rule\": \"self.redact__underscores__d > 0\"}\n\nEquality 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:\n  - 'set': `X + Y` performs a union where the array positions of all elements in `X` are preserved and\n    non-intersecting elements in `Y` are appended, retaining their partial order.\n  - 'map': `X + Y` performs a merge where the array positions of all keys in `X` are preserved but the values\n    are overwritten by values in `Y` when the key sets of `X` and `Y` intersect. Elements in `Y` with\n    non-intersecting keys are appended, retaining their partial order.",
           "type": "string"
@@ -15155,6 +15543,11 @@
           "kind": "DeleteOptions",
           "version": "v1"
         },
+        {
+          "group": "certificates.k8s.io",
+          "kind": "DeleteOptions",
+          "version": "v1alpha1"
+        },
         {
           "group": "certificates.k8s.io",
           "kind": "DeleteOptions",
@@ -15283,7 +15676,7 @@
         {
           "group": "resource.k8s.io",
           "kind": "DeleteOptions",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         },
         {
           "group": "scheduling.k8s.io",
@@ -15456,7 +15849,7 @@
           "additionalProperties": {
             "type": "string"
           },
-          "description": "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",
+          "description": "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: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations",
           "type": "object"
         },
         "creationTimestamp": {
@@ -15493,7 +15886,7 @@
           "additionalProperties": {
             "type": "string"
           },
-          "description": "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",
+          "description": "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: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels",
           "type": "object"
         },
         "managedFields": {
@@ -15504,11 +15897,11 @@
           "type": "array"
         },
         "name": {
-          "description": "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",
+          "description": "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: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#names",
           "type": "string"
         },
         "namespace": {
-          "description": "Namespace defines the space within which each name must be unique. An empty namespace is equivalent to the \"default\" namespace, but \"default\" 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.\n\nMust be a DNS_LABEL. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/namespaces",
+          "description": "Namespace defines the space within which each name must be unique. An empty namespace is equivalent to the \"default\" namespace, but \"default\" 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.\n\nMust be a DNS_LABEL. Cannot be updated. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces",
           "type": "string"
         },
         "ownerReferences": {
@@ -15529,7 +15922,7 @@
           "type": "string"
         },
         "uid": {
-          "description": "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.\n\nPopulated by the system. Read-only. More info: http://kubernetes.io/docs/user-guide/identifiers#uids",
+          "description": "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.\n\nPopulated by the system. Read-only. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#uids",
           "type": "string"
         }
       },
@@ -15555,11 +15948,11 @@
           "type": "string"
         },
         "name": {
-          "description": "Name of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#names",
+          "description": "Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#names",
           "type": "string"
         },
         "uid": {
-          "description": "UID of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#uids",
+          "description": "UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#uids",
           "type": "string"
         }
       },
@@ -15655,7 +16048,7 @@
         {
           "group": "resource.k8s.io",
           "kind": "Status",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       ]
     },
@@ -15705,7 +16098,7 @@
           "type": "integer"
         },
         "uid": {
-          "description": "UID of the resource. (when there is a single resource which can be described). More info: http://kubernetes.io/docs/user-guide/identifiers#uids",
+          "description": "UID of the resource. (when there is a single resource which can be described). More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#uids",
           "type": "string"
         }
       },
@@ -15858,6 +16251,11 @@
           "kind": "WatchEvent",
           "version": "v1"
         },
+        {
+          "group": "certificates.k8s.io",
+          "kind": "WatchEvent",
+          "version": "v1alpha1"
+        },
         {
           "group": "certificates.k8s.io",
           "kind": "WatchEvent",
@@ -15986,7 +16384,7 @@
         {
           "group": "resource.k8s.io",
           "kind": "WatchEvent",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         },
         {
           "group": "scheduling.k8s.io",
@@ -16444,6 +16842,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -16609,6 +17014,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -16720,6 +17132,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -16831,6 +17250,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -16942,6 +17368,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -17015,6 +17448,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -17100,7 +17540,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -17166,7 +17606,7 @@
           "uniqueItems": true
         },
         {
-          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
           "in": "query",
           "name": "fieldValidation",
           "type": "string",
@@ -17331,6 +17771,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -17424,6 +17871,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -17517,7 +17971,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -17738,7 +18192,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -17817,7 +18271,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -17945,6 +18399,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -18038,6 +18499,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -18131,7 +18599,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -18352,7 +18820,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -18431,7 +18899,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -18559,6 +19027,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -18652,6 +19127,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -18745,7 +19227,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -18966,7 +19448,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -19045,7 +19527,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -19173,6 +19655,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -19266,6 +19755,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -19359,7 +19855,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -19580,7 +20076,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -19659,7 +20155,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -19787,6 +20283,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -19880,6 +20383,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -19973,7 +20483,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -20194,7 +20704,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -20273,7 +20783,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -20410,7 +20920,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -20489,7 +20999,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -20617,6 +21127,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -20710,6 +21227,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -20803,7 +21327,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -21024,7 +21548,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -21103,7 +21627,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -21284,7 +21808,7 @@
           "uniqueItems": true
         },
         {
-          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
           "in": "query",
           "name": "fieldValidation",
           "type": "string",
@@ -21466,7 +21990,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -21545,7 +22069,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -21605,7 +22129,7 @@
           "uniqueItems": true
         },
         {
-          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
           "in": "query",
           "name": "fieldValidation",
           "type": "string",
@@ -22651,7 +23175,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -22730,7 +23254,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -22858,6 +23382,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -22951,6 +23482,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -23044,7 +23582,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -23265,7 +23803,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -23344,7 +23882,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -23472,6 +24010,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -23565,6 +24110,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -23658,7 +24210,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -23879,7 +24431,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -23958,7 +24510,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -24095,7 +24647,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -24174,7 +24726,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -24311,7 +24863,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -24390,7 +24942,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -24518,6 +25070,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -24611,6 +25170,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -24704,7 +25270,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -24925,7 +25491,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -25004,7 +25570,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -25141,7 +25707,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -25220,7 +25786,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -25348,6 +25914,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -25441,6 +26014,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -25534,7 +26114,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -25755,7 +26335,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -25834,7 +26414,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -25962,6 +26542,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -26055,6 +26642,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -26148,7 +26742,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -26369,7 +26963,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -26448,7 +27042,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -26508,7 +27102,7 @@
           "uniqueItems": true
         },
         {
-          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
           "in": "query",
           "name": "fieldValidation",
           "type": "string",
@@ -26681,6 +27275,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -26774,6 +27375,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -26867,7 +27475,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -27088,7 +27696,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -27167,7 +27775,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -27828,7 +28436,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -27907,7 +28515,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -28114,7 +28722,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -28193,7 +28801,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -28253,7 +28861,7 @@
           "uniqueItems": true
         },
         {
-          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
           "in": "query",
           "name": "fieldValidation",
           "type": "string",
@@ -28413,7 +29021,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -28492,7 +29100,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -28620,6 +29228,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -28713,6 +29328,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -28798,7 +29420,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -29011,7 +29633,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -29090,7 +29712,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -29727,7 +30349,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -29806,7 +30428,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -29944,6 +30566,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -30045,6 +30674,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -30138,6 +30774,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -30223,7 +30866,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -30436,7 +31079,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -30515,7 +31158,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -30644,7 +31287,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -30723,7 +31366,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -30861,6 +31504,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -30972,6 +31622,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -31083,6 +31740,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -31194,6 +31858,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -31305,6 +31976,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -31416,6 +32094,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -31527,6 +32212,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -31638,6 +32330,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -31749,6 +32448,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -31860,6 +32566,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -31971,6 +32684,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -32082,6 +32802,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -32201,6 +32928,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -32328,6 +33062,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -32447,6 +33188,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -32574,6 +33322,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -32693,6 +33448,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -32820,6 +33582,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -32939,6 +33708,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -33066,6 +33842,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -33185,6 +33968,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -33312,6 +34102,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -33431,6 +34228,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -33558,6 +34362,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -33677,6 +34488,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -33804,6 +34622,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -33923,6 +34748,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -34050,6 +34882,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -34169,6 +35008,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -34296,6 +35142,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -34415,6 +35268,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -34542,6 +35402,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -34661,6 +35528,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -34788,6 +35662,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -34907,6 +35788,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -35034,6 +35922,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -35153,6 +36048,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -35264,6 +36166,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -35383,6 +36292,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -35494,6 +36410,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -35605,6 +36528,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -35724,6 +36654,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -35835,6 +36772,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -35946,6 +36890,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -36057,6 +37008,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -36168,6 +37126,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -36279,6 +37244,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -36390,6 +37362,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -36501,6 +37480,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -36701,6 +37687,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -36794,6 +37787,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -36879,7 +37879,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -37092,7 +38092,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -37171,7 +38171,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -37299,6 +38299,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -37392,6 +38399,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -37477,7 +38491,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -37690,7 +38704,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -37769,7 +38783,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -37907,6 +38921,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -38026,6 +39047,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -38137,6 +39165,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -38256,6 +39291,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -38390,6 +39432,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -38483,6 +39532,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -38568,7 +39624,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -38781,7 +39837,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -38860,7 +39916,215 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "in": "query",
+            "name": "fieldValidation",
+            "type": "string",
+            "uniqueItems": true
+          }
+        ],
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.admissionregistration.v1alpha1.ValidatingAdmissionPolicy"
+            }
+          },
+          "201": {
+            "description": "Created",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.admissionregistration.v1alpha1.ValidatingAdmissionPolicy"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "admissionregistration_v1alpha1"
+        ],
+        "x-kubernetes-action": "put",
+        "x-kubernetes-group-version-kind": {
+          "group": "admissionregistration.k8s.io",
+          "kind": "ValidatingAdmissionPolicy",
+          "version": "v1alpha1"
+        }
+      }
+    },
+    "/apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{name}/status": {
+      "get": {
+        "consumes": [
+          "*/*"
+        ],
+        "description": "read status of the specified ValidatingAdmissionPolicy",
+        "operationId": "readAdmissionregistrationV1alpha1ValidatingAdmissionPolicyStatus",
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.admissionregistration.v1alpha1.ValidatingAdmissionPolicy"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "admissionregistration_v1alpha1"
+        ],
+        "x-kubernetes-action": "get",
+        "x-kubernetes-group-version-kind": {
+          "group": "admissionregistration.k8s.io",
+          "kind": "ValidatingAdmissionPolicy",
+          "version": "v1alpha1"
+        }
+      },
+      "parameters": [
+        {
+          "description": "name of the ValidatingAdmissionPolicy",
+          "in": "path",
+          "name": "name",
+          "required": true,
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "If 'true', then the output is pretty printed.",
+          "in": "query",
+          "name": "pretty",
+          "type": "string",
+          "uniqueItems": true
+        }
+      ],
+      "patch": {
+        "consumes": [
+          "application/json-patch+json",
+          "application/merge-patch+json",
+          "application/strategic-merge-patch+json",
+          "application/apply-patch+yaml"
+        ],
+        "description": "partially update status of the specified ValidatingAdmissionPolicy",
+        "operationId": "patchAdmissionregistrationV1alpha1ValidatingAdmissionPolicyStatus",
+        "parameters": [
+          {
+            "in": "body",
+            "name": "body",
+            "required": true,
+            "schema": {
+              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
+            }
+          },
+          {
+            "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
+            "in": "query",
+            "name": "dryRun",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "fieldManager is a name associated with the actor or entity that is making these changes. 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).",
+            "in": "query",
+            "name": "fieldManager",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "in": "query",
+            "name": "fieldValidation",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "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.",
+            "in": "query",
+            "name": "force",
+            "type": "boolean",
+            "uniqueItems": true
+          }
+        ],
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.admissionregistration.v1alpha1.ValidatingAdmissionPolicy"
+            }
+          },
+          "201": {
+            "description": "Created",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.admissionregistration.v1alpha1.ValidatingAdmissionPolicy"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "admissionregistration_v1alpha1"
+        ],
+        "x-kubernetes-action": "patch",
+        "x-kubernetes-group-version-kind": {
+          "group": "admissionregistration.k8s.io",
+          "kind": "ValidatingAdmissionPolicy",
+          "version": "v1alpha1"
+        }
+      },
+      "put": {
+        "consumes": [
+          "*/*"
+        ],
+        "description": "replace status of the specified ValidatingAdmissionPolicy",
+        "operationId": "replaceAdmissionregistrationV1alpha1ValidatingAdmissionPolicyStatus",
+        "parameters": [
+          {
+            "in": "body",
+            "name": "body",
+            "required": true,
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.admissionregistration.v1alpha1.ValidatingAdmissionPolicy"
+            }
+          },
+          {
+            "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
+            "in": "query",
+            "name": "dryRun",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.",
+            "in": "query",
+            "name": "fieldManager",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -38988,6 +40252,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -39081,6 +40352,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -39166,7 +40444,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -39379,7 +40657,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -39458,7 +40736,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -39596,6 +40874,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -39715,6 +41000,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -39826,6 +41118,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -39945,6 +41244,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -40112,6 +41418,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -40205,6 +41518,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -40290,7 +41610,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -40503,7 +41823,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -40582,7 +41902,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -40711,7 +42031,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -40790,7 +42110,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -40928,6 +42248,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -41047,6 +42374,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -41214,6 +42548,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -41307,6 +42648,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -41392,7 +42740,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -41605,7 +42953,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -41684,7 +43032,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -41813,7 +43161,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -41892,7 +43240,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -42030,6 +43378,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -42149,6 +43504,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -42326,6 +43688,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -42437,6 +43806,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -42548,6 +43924,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -42649,6 +44032,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -42742,6 +44132,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -42835,7 +44232,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -43056,7 +44453,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -43135,7 +44532,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -43263,6 +44660,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -43356,6 +44760,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -43449,7 +44860,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -43670,7 +45081,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -43749,7 +45160,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -43886,7 +45297,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -43965,7 +45376,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -44093,6 +45504,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -44186,6 +45604,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -44279,7 +45704,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -44500,7 +45925,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -44579,7 +46004,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -44716,7 +46141,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -44795,7 +46220,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -44932,7 +46357,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -45011,7 +46436,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -45139,6 +46564,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -45232,6 +46664,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -45325,7 +46764,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -45546,7 +46985,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -45625,7 +47064,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -45762,7 +47201,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -45841,7 +47280,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -45978,7 +47417,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -46057,7 +47496,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -46185,6 +47624,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -46278,6 +47724,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -46371,7 +47824,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -46592,7 +48045,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -46671,7 +48124,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -46808,7 +48261,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -46887,7 +48340,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -47024,7 +48477,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -47103,7 +48556,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -47241,6 +48694,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -47352,6 +48812,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -47463,6 +48930,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -47574,6 +49048,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -47685,6 +49166,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -47804,6 +49292,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -47931,6 +49426,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -48050,6 +49552,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -48177,6 +49686,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -48296,6 +49812,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -48423,6 +49946,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -48542,6 +50072,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -48669,6 +50206,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -48788,6 +50332,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -48915,6 +50466,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -49026,6 +50584,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -49137,6 +50702,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -49236,7 +50808,7 @@
           "uniqueItems": true
         },
         {
-          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
           "in": "query",
           "name": "fieldValidation",
           "type": "string",
@@ -49358,7 +50930,7 @@
           "uniqueItems": true
         },
         {
-          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
           "in": "query",
           "name": "fieldValidation",
           "type": "string",
@@ -49430,6 +51002,128 @@
         }
       }
     },
+    "/apis/authentication.k8s.io/v1beta1/": {
+      "get": {
+        "consumes": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf"
+        ],
+        "description": "get available resources",
+        "operationId": "getAuthenticationV1beta1APIResources",
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.APIResourceList"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "authentication_v1beta1"
+        ]
+      }
+    },
+    "/apis/authentication.k8s.io/v1beta1/selfsubjectreviews": {
+      "parameters": [
+        {
+          "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
+          "in": "query",
+          "name": "dryRun",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.",
+          "in": "query",
+          "name": "fieldManager",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+          "in": "query",
+          "name": "fieldValidation",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "If 'true', then the output is pretty printed.",
+          "in": "query",
+          "name": "pretty",
+          "type": "string",
+          "uniqueItems": true
+        }
+      ],
+      "post": {
+        "consumes": [
+          "*/*"
+        ],
+        "description": "create a SelfSubjectReview",
+        "operationId": "createAuthenticationV1beta1SelfSubjectReview",
+        "parameters": [
+          {
+            "in": "body",
+            "name": "body",
+            "required": true,
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.authentication.v1beta1.SelfSubjectReview"
+            }
+          }
+        ],
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.authentication.v1beta1.SelfSubjectReview"
+            }
+          },
+          "201": {
+            "description": "Created",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.authentication.v1beta1.SelfSubjectReview"
+            }
+          },
+          "202": {
+            "description": "Accepted",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.authentication.v1beta1.SelfSubjectReview"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "authentication_v1beta1"
+        ],
+        "x-kubernetes-action": "post",
+        "x-kubernetes-group-version-kind": {
+          "group": "authentication.k8s.io",
+          "kind": "SelfSubjectReview",
+          "version": "v1beta1"
+        }
+      }
+    },
     "/apis/authorization.k8s.io/": {
       "get": {
         "consumes": [
@@ -49513,7 +51207,7 @@
           "uniqueItems": true
         },
         {
-          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
           "in": "query",
           "name": "fieldValidation",
           "type": "string",
@@ -49610,7 +51304,7 @@
           "uniqueItems": true
         },
         {
-          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
           "in": "query",
           "name": "fieldValidation",
           "type": "string",
@@ -49699,7 +51393,7 @@
           "uniqueItems": true
         },
         {
-          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
           "in": "query",
           "name": "fieldValidation",
           "type": "string",
@@ -49788,7 +51482,7 @@
           "uniqueItems": true
         },
         {
-          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+          "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
           "in": "query",
           "name": "fieldValidation",
           "type": "string",
@@ -50021,6 +51715,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -50122,6 +51823,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -50215,6 +51923,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -50308,7 +52023,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -50529,7 +52244,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -50608,7 +52323,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -50745,7 +52460,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -50824,7 +52539,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -50962,6 +52677,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -51081,6 +52803,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -51208,6 +52937,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -51352,6 +53088,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -51453,6 +53196,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -51546,6 +53296,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -51639,7 +53396,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -51860,7 +53617,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -51939,7 +53696,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -52076,7 +53833,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -52155,7 +53912,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -52293,6 +54050,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -52412,6 +54176,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -52539,6 +54310,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -52716,6 +54494,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -52827,6 +54612,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -52928,6 +54720,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -53021,6 +54820,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -53114,7 +54920,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -53335,7 +55141,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -53414,7 +55220,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -53551,7 +55357,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -53630,7 +55436,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -53758,6 +55564,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -53851,6 +55664,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -53944,7 +55764,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -54165,7 +55985,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -54244,7 +56064,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -54381,7 +56201,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -54460,7 +56280,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -54598,6 +56418,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -54709,6 +56536,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -54828,6 +56662,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -54955,6 +56796,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -55074,6 +56922,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -55201,6 +57056,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -55368,6 +57230,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -55461,6 +57330,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -55546,7 +57422,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -55759,7 +57635,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -55838,7 +57714,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -55967,7 +57843,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -56046,7 +57922,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -56175,7 +58051,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -56254,7 +58130,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -56392,6 +58268,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -56511,6 +58394,902 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
+        {
+          "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
+          "in": "query",
+          "name": "timeoutSeconds",
+          "type": "integer",
+          "uniqueItems": true
+        },
+        {
+          "description": "Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.",
+          "in": "query",
+          "name": "watch",
+          "type": "boolean",
+          "uniqueItems": true
+        }
+      ]
+    },
+    "/apis/certificates.k8s.io/v1alpha1/": {
+      "get": {
+        "consumes": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf"
+        ],
+        "description": "get available resources",
+        "operationId": "getCertificatesV1alpha1APIResources",
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.APIResourceList"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "certificates_v1alpha1"
+        ]
+      }
+    },
+    "/apis/certificates.k8s.io/v1alpha1/clustertrustbundles": {
+      "delete": {
+        "consumes": [
+          "*/*"
+        ],
+        "description": "delete collection of ClusterTrustBundle",
+        "operationId": "deleteCertificatesV1alpha1CollectionClusterTrustBundle",
+        "parameters": [
+          {
+            "in": "body",
+            "name": "body",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
+            }
+          },
+          {
+            "description": "The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
+            "in": "query",
+            "name": "continue",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
+            "in": "query",
+            "name": "dryRun",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
+            "in": "query",
+            "name": "fieldSelector",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "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.",
+            "in": "query",
+            "name": "gracePeriodSeconds",
+            "type": "integer",
+            "uniqueItems": true
+          },
+          {
+            "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
+            "in": "query",
+            "name": "labelSelector",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
+            "in": "query",
+            "name": "limit",
+            "type": "integer",
+            "uniqueItems": true
+          },
+          {
+            "description": "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.",
+            "in": "query",
+            "name": "orphanDependents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
+          {
+            "description": "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.",
+            "in": "query",
+            "name": "propagationPolicy",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
+            "in": "query",
+            "name": "resourceVersion",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
+            "in": "query",
+            "name": "resourceVersionMatch",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
+          {
+            "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
+            "in": "query",
+            "name": "timeoutSeconds",
+            "type": "integer",
+            "uniqueItems": true
+          }
+        ],
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "certificates_v1alpha1"
+        ],
+        "x-kubernetes-action": "deletecollection",
+        "x-kubernetes-group-version-kind": {
+          "group": "certificates.k8s.io",
+          "kind": "ClusterTrustBundle",
+          "version": "v1alpha1"
+        }
+      },
+      "get": {
+        "consumes": [
+          "*/*"
+        ],
+        "description": "list or watch objects of kind ClusterTrustBundle",
+        "operationId": "listCertificatesV1alpha1ClusterTrustBundle",
+        "parameters": [
+          {
+            "description": "allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.",
+            "in": "query",
+            "name": "allowWatchBookmarks",
+            "type": "boolean",
+            "uniqueItems": true
+          },
+          {
+            "description": "The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
+            "in": "query",
+            "name": "continue",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
+            "in": "query",
+            "name": "fieldSelector",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
+            "in": "query",
+            "name": "labelSelector",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
+            "in": "query",
+            "name": "limit",
+            "type": "integer",
+            "uniqueItems": true
+          },
+          {
+            "description": "resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
+            "in": "query",
+            "name": "resourceVersion",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
+            "in": "query",
+            "name": "resourceVersionMatch",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
+          {
+            "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
+            "in": "query",
+            "name": "timeoutSeconds",
+            "type": "integer",
+            "uniqueItems": true
+          },
+          {
+            "description": "Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.",
+            "in": "query",
+            "name": "watch",
+            "type": "boolean",
+            "uniqueItems": true
+          }
+        ],
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf",
+          "application/json;stream=watch",
+          "application/vnd.kubernetes.protobuf;stream=watch"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.certificates.v1alpha1.ClusterTrustBundleList"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "certificates_v1alpha1"
+        ],
+        "x-kubernetes-action": "list",
+        "x-kubernetes-group-version-kind": {
+          "group": "certificates.k8s.io",
+          "kind": "ClusterTrustBundle",
+          "version": "v1alpha1"
+        }
+      },
+      "parameters": [
+        {
+          "description": "If 'true', then the output is pretty printed.",
+          "in": "query",
+          "name": "pretty",
+          "type": "string",
+          "uniqueItems": true
+        }
+      ],
+      "post": {
+        "consumes": [
+          "*/*"
+        ],
+        "description": "create a ClusterTrustBundle",
+        "operationId": "createCertificatesV1alpha1ClusterTrustBundle",
+        "parameters": [
+          {
+            "in": "body",
+            "name": "body",
+            "required": true,
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.certificates.v1alpha1.ClusterTrustBundle"
+            }
+          },
+          {
+            "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
+            "in": "query",
+            "name": "dryRun",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.",
+            "in": "query",
+            "name": "fieldManager",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "in": "query",
+            "name": "fieldValidation",
+            "type": "string",
+            "uniqueItems": true
+          }
+        ],
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.certificates.v1alpha1.ClusterTrustBundle"
+            }
+          },
+          "201": {
+            "description": "Created",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.certificates.v1alpha1.ClusterTrustBundle"
+            }
+          },
+          "202": {
+            "description": "Accepted",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.certificates.v1alpha1.ClusterTrustBundle"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "certificates_v1alpha1"
+        ],
+        "x-kubernetes-action": "post",
+        "x-kubernetes-group-version-kind": {
+          "group": "certificates.k8s.io",
+          "kind": "ClusterTrustBundle",
+          "version": "v1alpha1"
+        }
+      }
+    },
+    "/apis/certificates.k8s.io/v1alpha1/clustertrustbundles/{name}": {
+      "delete": {
+        "consumes": [
+          "*/*"
+        ],
+        "description": "delete a ClusterTrustBundle",
+        "operationId": "deleteCertificatesV1alpha1ClusterTrustBundle",
+        "parameters": [
+          {
+            "in": "body",
+            "name": "body",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
+            }
+          },
+          {
+            "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
+            "in": "query",
+            "name": "dryRun",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "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.",
+            "in": "query",
+            "name": "gracePeriodSeconds",
+            "type": "integer",
+            "uniqueItems": true
+          },
+          {
+            "description": "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.",
+            "in": "query",
+            "name": "orphanDependents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
+          {
+            "description": "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.",
+            "in": "query",
+            "name": "propagationPolicy",
+            "type": "string",
+            "uniqueItems": true
+          }
+        ],
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"
+            }
+          },
+          "202": {
+            "description": "Accepted",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "certificates_v1alpha1"
+        ],
+        "x-kubernetes-action": "delete",
+        "x-kubernetes-group-version-kind": {
+          "group": "certificates.k8s.io",
+          "kind": "ClusterTrustBundle",
+          "version": "v1alpha1"
+        }
+      },
+      "get": {
+        "consumes": [
+          "*/*"
+        ],
+        "description": "read the specified ClusterTrustBundle",
+        "operationId": "readCertificatesV1alpha1ClusterTrustBundle",
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.certificates.v1alpha1.ClusterTrustBundle"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "certificates_v1alpha1"
+        ],
+        "x-kubernetes-action": "get",
+        "x-kubernetes-group-version-kind": {
+          "group": "certificates.k8s.io",
+          "kind": "ClusterTrustBundle",
+          "version": "v1alpha1"
+        }
+      },
+      "parameters": [
+        {
+          "description": "name of the ClusterTrustBundle",
+          "in": "path",
+          "name": "name",
+          "required": true,
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "If 'true', then the output is pretty printed.",
+          "in": "query",
+          "name": "pretty",
+          "type": "string",
+          "uniqueItems": true
+        }
+      ],
+      "patch": {
+        "consumes": [
+          "application/json-patch+json",
+          "application/merge-patch+json",
+          "application/strategic-merge-patch+json",
+          "application/apply-patch+yaml"
+        ],
+        "description": "partially update the specified ClusterTrustBundle",
+        "operationId": "patchCertificatesV1alpha1ClusterTrustBundle",
+        "parameters": [
+          {
+            "in": "body",
+            "name": "body",
+            "required": true,
+            "schema": {
+              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
+            }
+          },
+          {
+            "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
+            "in": "query",
+            "name": "dryRun",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "fieldManager is a name associated with the actor or entity that is making these changes. 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).",
+            "in": "query",
+            "name": "fieldManager",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "in": "query",
+            "name": "fieldValidation",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "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.",
+            "in": "query",
+            "name": "force",
+            "type": "boolean",
+            "uniqueItems": true
+          }
+        ],
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.certificates.v1alpha1.ClusterTrustBundle"
+            }
+          },
+          "201": {
+            "description": "Created",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.certificates.v1alpha1.ClusterTrustBundle"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "certificates_v1alpha1"
+        ],
+        "x-kubernetes-action": "patch",
+        "x-kubernetes-group-version-kind": {
+          "group": "certificates.k8s.io",
+          "kind": "ClusterTrustBundle",
+          "version": "v1alpha1"
+        }
+      },
+      "put": {
+        "consumes": [
+          "*/*"
+        ],
+        "description": "replace the specified ClusterTrustBundle",
+        "operationId": "replaceCertificatesV1alpha1ClusterTrustBundle",
+        "parameters": [
+          {
+            "in": "body",
+            "name": "body",
+            "required": true,
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.certificates.v1alpha1.ClusterTrustBundle"
+            }
+          },
+          {
+            "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
+            "in": "query",
+            "name": "dryRun",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.",
+            "in": "query",
+            "name": "fieldManager",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "in": "query",
+            "name": "fieldValidation",
+            "type": "string",
+            "uniqueItems": true
+          }
+        ],
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.certificates.v1alpha1.ClusterTrustBundle"
+            }
+          },
+          "201": {
+            "description": "Created",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.certificates.v1alpha1.ClusterTrustBundle"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "certificates_v1alpha1"
+        ],
+        "x-kubernetes-action": "put",
+        "x-kubernetes-group-version-kind": {
+          "group": "certificates.k8s.io",
+          "kind": "ClusterTrustBundle",
+          "version": "v1alpha1"
+        }
+      }
+    },
+    "/apis/certificates.k8s.io/v1alpha1/watch/clustertrustbundles": {
+      "get": {
+        "consumes": [
+          "*/*"
+        ],
+        "description": "watch individual changes to a list of ClusterTrustBundle. deprecated: use the 'watch' parameter with a list operation instead.",
+        "operationId": "watchCertificatesV1alpha1ClusterTrustBundleList",
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf",
+          "application/json;stream=watch",
+          "application/vnd.kubernetes.protobuf;stream=watch"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "certificates_v1alpha1"
+        ],
+        "x-kubernetes-action": "watchlist",
+        "x-kubernetes-group-version-kind": {
+          "group": "certificates.k8s.io",
+          "kind": "ClusterTrustBundle",
+          "version": "v1alpha1"
+        }
+      },
+      "parameters": [
+        {
+          "description": "allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.",
+          "in": "query",
+          "name": "allowWatchBookmarks",
+          "type": "boolean",
+          "uniqueItems": true
+        },
+        {
+          "description": "The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
+          "in": "query",
+          "name": "continue",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
+          "in": "query",
+          "name": "fieldSelector",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
+          "in": "query",
+          "name": "labelSelector",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
+          "in": "query",
+          "name": "limit",
+          "type": "integer",
+          "uniqueItems": true
+        },
+        {
+          "description": "If 'true', then the output is pretty printed.",
+          "in": "query",
+          "name": "pretty",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
+          "in": "query",
+          "name": "resourceVersion",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
+          "in": "query",
+          "name": "resourceVersionMatch",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
+        {
+          "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
+          "in": "query",
+          "name": "timeoutSeconds",
+          "type": "integer",
+          "uniqueItems": true
+        },
+        {
+          "description": "Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.",
+          "in": "query",
+          "name": "watch",
+          "type": "boolean",
+          "uniqueItems": true
+        }
+      ]
+    },
+    "/apis/certificates.k8s.io/v1alpha1/watch/clustertrustbundles/{name}": {
+      "get": {
+        "consumes": [
+          "*/*"
+        ],
+        "description": "watch changes to an object of kind ClusterTrustBundle. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.",
+        "operationId": "watchCertificatesV1alpha1ClusterTrustBundle",
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf",
+          "application/json;stream=watch",
+          "application/vnd.kubernetes.protobuf;stream=watch"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "certificates_v1alpha1"
+        ],
+        "x-kubernetes-action": "watch",
+        "x-kubernetes-group-version-kind": {
+          "group": "certificates.k8s.io",
+          "kind": "ClusterTrustBundle",
+          "version": "v1alpha1"
+        }
+      },
+      "parameters": [
+        {
+          "description": "allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.",
+          "in": "query",
+          "name": "allowWatchBookmarks",
+          "type": "boolean",
+          "uniqueItems": true
+        },
+        {
+          "description": "The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
+          "in": "query",
+          "name": "continue",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
+          "in": "query",
+          "name": "fieldSelector",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
+          "in": "query",
+          "name": "labelSelector",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
+          "in": "query",
+          "name": "limit",
+          "type": "integer",
+          "uniqueItems": true
+        },
+        {
+          "description": "name of the ClusterTrustBundle",
+          "in": "path",
+          "name": "name",
+          "required": true,
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "If 'true', then the output is pretty printed.",
+          "in": "query",
+          "name": "pretty",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
+          "in": "query",
+          "name": "resourceVersion",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
+          "in": "query",
+          "name": "resourceVersionMatch",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -56688,6 +59467,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -56789,6 +59575,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -56882,6 +59675,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -56975,7 +59775,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -57196,7 +59996,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -57275,7 +60075,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -57413,6 +60213,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -57532,6 +60339,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -57659,6 +60473,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -57836,6 +60657,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -57937,6 +60765,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -58030,6 +60865,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -58123,7 +60965,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -58344,7 +61186,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -58423,7 +61265,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -58561,6 +61403,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -58680,6 +61529,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -58807,6 +61663,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -58984,6 +61847,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -59085,6 +61955,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -59178,6 +62055,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -59271,7 +62155,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -59492,7 +62376,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -59571,7 +62455,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -59709,6 +62593,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -59828,6 +62719,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -59955,6 +62853,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -60122,6 +63027,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -60215,6 +63127,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -60300,7 +63219,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -60513,7 +63432,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -60592,7 +63511,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -60721,7 +63640,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -60800,7 +63719,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -60928,6 +63847,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -61021,6 +63947,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -61106,7 +64039,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -61319,7 +64252,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -61398,7 +64331,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -61527,7 +64460,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -61606,7 +64539,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -61744,6 +64677,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -61863,6 +64803,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -61974,6 +64921,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -62093,6 +65047,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -62227,6 +65188,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -62320,6 +65288,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -62405,7 +65380,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -62618,7 +65593,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -62697,7 +65672,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -62826,7 +65801,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -62905,7 +65880,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -63033,6 +66008,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -63126,6 +66108,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -63211,7 +66200,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -63424,7 +66413,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -63503,7 +66492,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -63632,7 +66621,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -63711,7 +66700,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -63849,6 +66838,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -63968,6 +66964,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -64079,6 +67082,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -64198,6 +67208,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -64365,6 +67382,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -64458,6 +67482,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -64543,7 +67574,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -64756,7 +67787,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -64835,7 +67866,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -64964,7 +67995,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -65043,7 +68074,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -65181,6 +68212,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -65300,6 +68338,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -65467,6 +68512,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -65560,6 +68612,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -65645,7 +68704,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -65858,7 +68917,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -65937,7 +68996,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -66075,6 +69134,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -66176,6 +69242,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -66269,6 +69342,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -66362,7 +69442,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -66583,7 +69663,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -66662,7 +69742,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -66799,7 +69879,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -66878,7 +69958,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -67006,6 +70086,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -67099,6 +70186,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -67192,7 +70286,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -67413,7 +70507,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -67492,7 +70586,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -67629,7 +70723,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -67708,7 +70802,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -67846,6 +70940,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -67957,6 +71058,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -68076,6 +71184,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -68187,6 +71302,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -68306,6 +71428,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -68433,6 +71562,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -68552,6 +71688,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -68679,6 +71822,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -68790,6 +71940,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -68924,6 +72081,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -69017,6 +72181,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -69102,7 +72273,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -69315,7 +72486,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -69394,7 +72565,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -69437,6 +72608,618 @@
         }
       }
     },
+    "/apis/networking.k8s.io/v1alpha1/ipaddresses": {
+      "delete": {
+        "consumes": [
+          "*/*"
+        ],
+        "description": "delete collection of IPAddress",
+        "operationId": "deleteNetworkingV1alpha1CollectionIPAddress",
+        "parameters": [
+          {
+            "in": "body",
+            "name": "body",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
+            }
+          },
+          {
+            "description": "The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
+            "in": "query",
+            "name": "continue",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
+            "in": "query",
+            "name": "dryRun",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
+            "in": "query",
+            "name": "fieldSelector",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "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.",
+            "in": "query",
+            "name": "gracePeriodSeconds",
+            "type": "integer",
+            "uniqueItems": true
+          },
+          {
+            "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
+            "in": "query",
+            "name": "labelSelector",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
+            "in": "query",
+            "name": "limit",
+            "type": "integer",
+            "uniqueItems": true
+          },
+          {
+            "description": "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.",
+            "in": "query",
+            "name": "orphanDependents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
+          {
+            "description": "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.",
+            "in": "query",
+            "name": "propagationPolicy",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
+            "in": "query",
+            "name": "resourceVersion",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
+            "in": "query",
+            "name": "resourceVersionMatch",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
+          {
+            "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
+            "in": "query",
+            "name": "timeoutSeconds",
+            "type": "integer",
+            "uniqueItems": true
+          }
+        ],
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "networking_v1alpha1"
+        ],
+        "x-kubernetes-action": "deletecollection",
+        "x-kubernetes-group-version-kind": {
+          "group": "networking.k8s.io",
+          "kind": "IPAddress",
+          "version": "v1alpha1"
+        }
+      },
+      "get": {
+        "consumes": [
+          "*/*"
+        ],
+        "description": "list or watch objects of kind IPAddress",
+        "operationId": "listNetworkingV1alpha1IPAddress",
+        "parameters": [
+          {
+            "description": "allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.",
+            "in": "query",
+            "name": "allowWatchBookmarks",
+            "type": "boolean",
+            "uniqueItems": true
+          },
+          {
+            "description": "The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
+            "in": "query",
+            "name": "continue",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
+            "in": "query",
+            "name": "fieldSelector",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
+            "in": "query",
+            "name": "labelSelector",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
+            "in": "query",
+            "name": "limit",
+            "type": "integer",
+            "uniqueItems": true
+          },
+          {
+            "description": "resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
+            "in": "query",
+            "name": "resourceVersion",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
+            "in": "query",
+            "name": "resourceVersionMatch",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
+          {
+            "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
+            "in": "query",
+            "name": "timeoutSeconds",
+            "type": "integer",
+            "uniqueItems": true
+          },
+          {
+            "description": "Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.",
+            "in": "query",
+            "name": "watch",
+            "type": "boolean",
+            "uniqueItems": true
+          }
+        ],
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf",
+          "application/json;stream=watch",
+          "application/vnd.kubernetes.protobuf;stream=watch"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.networking.v1alpha1.IPAddressList"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "networking_v1alpha1"
+        ],
+        "x-kubernetes-action": "list",
+        "x-kubernetes-group-version-kind": {
+          "group": "networking.k8s.io",
+          "kind": "IPAddress",
+          "version": "v1alpha1"
+        }
+      },
+      "parameters": [
+        {
+          "description": "If 'true', then the output is pretty printed.",
+          "in": "query",
+          "name": "pretty",
+          "type": "string",
+          "uniqueItems": true
+        }
+      ],
+      "post": {
+        "consumes": [
+          "*/*"
+        ],
+        "description": "create an IPAddress",
+        "operationId": "createNetworkingV1alpha1IPAddress",
+        "parameters": [
+          {
+            "in": "body",
+            "name": "body",
+            "required": true,
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.networking.v1alpha1.IPAddress"
+            }
+          },
+          {
+            "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
+            "in": "query",
+            "name": "dryRun",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.",
+            "in": "query",
+            "name": "fieldManager",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "in": "query",
+            "name": "fieldValidation",
+            "type": "string",
+            "uniqueItems": true
+          }
+        ],
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.networking.v1alpha1.IPAddress"
+            }
+          },
+          "201": {
+            "description": "Created",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.networking.v1alpha1.IPAddress"
+            }
+          },
+          "202": {
+            "description": "Accepted",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.networking.v1alpha1.IPAddress"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "networking_v1alpha1"
+        ],
+        "x-kubernetes-action": "post",
+        "x-kubernetes-group-version-kind": {
+          "group": "networking.k8s.io",
+          "kind": "IPAddress",
+          "version": "v1alpha1"
+        }
+      }
+    },
+    "/apis/networking.k8s.io/v1alpha1/ipaddresses/{name}": {
+      "delete": {
+        "consumes": [
+          "*/*"
+        ],
+        "description": "delete an IPAddress",
+        "operationId": "deleteNetworkingV1alpha1IPAddress",
+        "parameters": [
+          {
+            "in": "body",
+            "name": "body",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
+            }
+          },
+          {
+            "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
+            "in": "query",
+            "name": "dryRun",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "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.",
+            "in": "query",
+            "name": "gracePeriodSeconds",
+            "type": "integer",
+            "uniqueItems": true
+          },
+          {
+            "description": "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.",
+            "in": "query",
+            "name": "orphanDependents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
+          {
+            "description": "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.",
+            "in": "query",
+            "name": "propagationPolicy",
+            "type": "string",
+            "uniqueItems": true
+          }
+        ],
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"
+            }
+          },
+          "202": {
+            "description": "Accepted",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "networking_v1alpha1"
+        ],
+        "x-kubernetes-action": "delete",
+        "x-kubernetes-group-version-kind": {
+          "group": "networking.k8s.io",
+          "kind": "IPAddress",
+          "version": "v1alpha1"
+        }
+      },
+      "get": {
+        "consumes": [
+          "*/*"
+        ],
+        "description": "read the specified IPAddress",
+        "operationId": "readNetworkingV1alpha1IPAddress",
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.networking.v1alpha1.IPAddress"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "networking_v1alpha1"
+        ],
+        "x-kubernetes-action": "get",
+        "x-kubernetes-group-version-kind": {
+          "group": "networking.k8s.io",
+          "kind": "IPAddress",
+          "version": "v1alpha1"
+        }
+      },
+      "parameters": [
+        {
+          "description": "name of the IPAddress",
+          "in": "path",
+          "name": "name",
+          "required": true,
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "If 'true', then the output is pretty printed.",
+          "in": "query",
+          "name": "pretty",
+          "type": "string",
+          "uniqueItems": true
+        }
+      ],
+      "patch": {
+        "consumes": [
+          "application/json-patch+json",
+          "application/merge-patch+json",
+          "application/strategic-merge-patch+json",
+          "application/apply-patch+yaml"
+        ],
+        "description": "partially update the specified IPAddress",
+        "operationId": "patchNetworkingV1alpha1IPAddress",
+        "parameters": [
+          {
+            "in": "body",
+            "name": "body",
+            "required": true,
+            "schema": {
+              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
+            }
+          },
+          {
+            "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
+            "in": "query",
+            "name": "dryRun",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "fieldManager is a name associated with the actor or entity that is making these changes. 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).",
+            "in": "query",
+            "name": "fieldManager",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "in": "query",
+            "name": "fieldValidation",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "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.",
+            "in": "query",
+            "name": "force",
+            "type": "boolean",
+            "uniqueItems": true
+          }
+        ],
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.networking.v1alpha1.IPAddress"
+            }
+          },
+          "201": {
+            "description": "Created",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.networking.v1alpha1.IPAddress"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "networking_v1alpha1"
+        ],
+        "x-kubernetes-action": "patch",
+        "x-kubernetes-group-version-kind": {
+          "group": "networking.k8s.io",
+          "kind": "IPAddress",
+          "version": "v1alpha1"
+        }
+      },
+      "put": {
+        "consumes": [
+          "*/*"
+        ],
+        "description": "replace the specified IPAddress",
+        "operationId": "replaceNetworkingV1alpha1IPAddress",
+        "parameters": [
+          {
+            "in": "body",
+            "name": "body",
+            "required": true,
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.networking.v1alpha1.IPAddress"
+            }
+          },
+          {
+            "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
+            "in": "query",
+            "name": "dryRun",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.",
+            "in": "query",
+            "name": "fieldManager",
+            "type": "string",
+            "uniqueItems": true
+          },
+          {
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "in": "query",
+            "name": "fieldValidation",
+            "type": "string",
+            "uniqueItems": true
+          }
+        ],
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.networking.v1alpha1.IPAddress"
+            }
+          },
+          "201": {
+            "description": "Created",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.api.networking.v1alpha1.IPAddress"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "networking_v1alpha1"
+        ],
+        "x-kubernetes-action": "put",
+        "x-kubernetes-group-version-kind": {
+          "group": "networking.k8s.io",
+          "kind": "IPAddress",
+          "version": "v1alpha1"
+        }
+      }
+    },
     "/apis/networking.k8s.io/v1alpha1/watch/clustercidrs": {
       "get": {
         "consumes": [
@@ -69532,6 +73315,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -69651,6 +73441,257 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
+        {
+          "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
+          "in": "query",
+          "name": "timeoutSeconds",
+          "type": "integer",
+          "uniqueItems": true
+        },
+        {
+          "description": "Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.",
+          "in": "query",
+          "name": "watch",
+          "type": "boolean",
+          "uniqueItems": true
+        }
+      ]
+    },
+    "/apis/networking.k8s.io/v1alpha1/watch/ipaddresses": {
+      "get": {
+        "consumes": [
+          "*/*"
+        ],
+        "description": "watch individual changes to a list of IPAddress. deprecated: use the 'watch' parameter with a list operation instead.",
+        "operationId": "watchNetworkingV1alpha1IPAddressList",
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf",
+          "application/json;stream=watch",
+          "application/vnd.kubernetes.protobuf;stream=watch"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "networking_v1alpha1"
+        ],
+        "x-kubernetes-action": "watchlist",
+        "x-kubernetes-group-version-kind": {
+          "group": "networking.k8s.io",
+          "kind": "IPAddress",
+          "version": "v1alpha1"
+        }
+      },
+      "parameters": [
+        {
+          "description": "allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.",
+          "in": "query",
+          "name": "allowWatchBookmarks",
+          "type": "boolean",
+          "uniqueItems": true
+        },
+        {
+          "description": "The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
+          "in": "query",
+          "name": "continue",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
+          "in": "query",
+          "name": "fieldSelector",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
+          "in": "query",
+          "name": "labelSelector",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
+          "in": "query",
+          "name": "limit",
+          "type": "integer",
+          "uniqueItems": true
+        },
+        {
+          "description": "If 'true', then the output is pretty printed.",
+          "in": "query",
+          "name": "pretty",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
+          "in": "query",
+          "name": "resourceVersion",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
+          "in": "query",
+          "name": "resourceVersionMatch",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
+        {
+          "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
+          "in": "query",
+          "name": "timeoutSeconds",
+          "type": "integer",
+          "uniqueItems": true
+        },
+        {
+          "description": "Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.",
+          "in": "query",
+          "name": "watch",
+          "type": "boolean",
+          "uniqueItems": true
+        }
+      ]
+    },
+    "/apis/networking.k8s.io/v1alpha1/watch/ipaddresses/{name}": {
+      "get": {
+        "consumes": [
+          "*/*"
+        ],
+        "description": "watch changes to an object of kind IPAddress. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.",
+        "operationId": "watchNetworkingV1alpha1IPAddress",
+        "produces": [
+          "application/json",
+          "application/yaml",
+          "application/vnd.kubernetes.protobuf",
+          "application/json;stream=watch",
+          "application/vnd.kubernetes.protobuf;stream=watch"
+        ],
+        "responses": {
+          "200": {
+            "description": "OK",
+            "schema": {
+              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"
+            }
+          },
+          "401": {
+            "description": "Unauthorized"
+          }
+        },
+        "schemes": [
+          "https"
+        ],
+        "tags": [
+          "networking_v1alpha1"
+        ],
+        "x-kubernetes-action": "watch",
+        "x-kubernetes-group-version-kind": {
+          "group": "networking.k8s.io",
+          "kind": "IPAddress",
+          "version": "v1alpha1"
+        }
+      },
+      "parameters": [
+        {
+          "description": "allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.",
+          "in": "query",
+          "name": "allowWatchBookmarks",
+          "type": "boolean",
+          "uniqueItems": true
+        },
+        {
+          "description": "The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
+          "in": "query",
+          "name": "continue",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
+          "in": "query",
+          "name": "fieldSelector",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
+          "in": "query",
+          "name": "labelSelector",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
+          "in": "query",
+          "name": "limit",
+          "type": "integer",
+          "uniqueItems": true
+        },
+        {
+          "description": "name of the IPAddress",
+          "in": "path",
+          "name": "name",
+          "required": true,
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "If 'true', then the output is pretty printed.",
+          "in": "query",
+          "name": "pretty",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
+          "in": "query",
+          "name": "resourceVersion",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
+          "in": "query",
+          "name": "resourceVersionMatch",
+          "type": "string",
+          "uniqueItems": true
+        },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -69818,6 +73859,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -69911,6 +73959,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -69996,7 +74051,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -70209,7 +74264,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -70288,7 +74343,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -70426,6 +74481,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -70545,6 +74607,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -70712,6 +74781,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -70805,6 +74881,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -70898,7 +74981,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -71119,7 +75202,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -71198,7 +75281,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -71335,7 +75418,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -71414,7 +75497,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -71552,6 +75635,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -71671,6 +75761,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -71798,6 +75895,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -71909,6 +76013,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -72076,6 +76187,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -72169,6 +76287,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -72254,7 +76379,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -72467,7 +76592,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -72546,7 +76671,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -72674,6 +76799,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -72767,6 +76899,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -72852,7 +76991,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -73065,7 +77204,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -73144,7 +77283,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -73272,6 +77411,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -73365,6 +77511,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -73458,7 +77611,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -73679,7 +77832,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -73758,7 +77911,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -73886,6 +78039,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -73979,6 +78139,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -74072,7 +78239,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -74293,7 +78460,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -74372,7 +78539,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -74510,6 +78677,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -74621,6 +78795,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -74732,6 +78913,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -74851,6 +79039,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -74962,6 +79157,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -75081,6 +79283,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -75200,6 +79409,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -75327,6 +79543,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -75446,6 +79669,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -75573,6 +79803,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -75684,6 +79921,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -75795,6 +80039,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -75844,7 +80095,7 @@
         ]
       }
     },
-    "/apis/resource.k8s.io/v1alpha1/": {
+    "/apis/resource.k8s.io/v1alpha2/": {
       "get": {
         "consumes": [
           "application/json",
@@ -75852,7 +80103,7 @@
           "application/vnd.kubernetes.protobuf"
         ],
         "description": "get available resources",
-        "operationId": "getResourceV1alpha1APIResources",
+        "operationId": "getResourceV1alpha2APIResources",
         "produces": [
           "application/json",
           "application/yaml",
@@ -75873,17 +80124,17 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ]
       }
     },
-    "/apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings": {
+    "/apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts": {
       "delete": {
         "consumes": [
           "*/*"
         ],
-        "description": "delete collection of PodScheduling",
-        "operationId": "deleteResourceV1alpha1CollectionNamespacedPodScheduling",
+        "description": "delete collection of PodSchedulingContext",
+        "operationId": "deleteResourceV1alpha2CollectionNamespacedPodSchedulingContext",
         "parameters": [
           {
             "in": "body",
@@ -75962,6 +80213,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -75990,21 +80248,21 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "deletecollection",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
-          "kind": "PodScheduling",
-          "version": "v1alpha1"
+          "kind": "PodSchedulingContext",
+          "version": "v1alpha2"
         }
       },
       "get": {
         "consumes": [
           "*/*"
         ],
-        "description": "list or watch objects of kind PodScheduling",
-        "operationId": "listResourceV1alpha1NamespacedPodScheduling",
+        "description": "list or watch objects of kind PodSchedulingContext",
+        "operationId": "listResourceV1alpha2NamespacedPodSchedulingContext",
         "parameters": [
           {
             "description": "allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.",
@@ -76055,6 +80313,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -76081,7 +80346,7 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodSchedulingList"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContextList"
             }
           },
           "401": {
@@ -76092,13 +80357,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "list",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
-          "kind": "PodScheduling",
-          "version": "v1alpha1"
+          "kind": "PodSchedulingContext",
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -76122,15 +80387,15 @@
         "consumes": [
           "*/*"
         ],
-        "description": "create a PodScheduling",
-        "operationId": "createResourceV1alpha1NamespacedPodScheduling",
+        "description": "create a PodSchedulingContext",
+        "operationId": "createResourceV1alpha2NamespacedPodSchedulingContext",
         "parameters": [
           {
             "in": "body",
             "name": "body",
             "required": true,
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodScheduling"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContext"
             }
           },
           {
@@ -76148,7 +80413,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -76164,19 +80429,19 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodScheduling"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContext"
             }
           },
           "201": {
             "description": "Created",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodScheduling"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContext"
             }
           },
           "202": {
             "description": "Accepted",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodScheduling"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContext"
             }
           },
           "401": {
@@ -76187,23 +80452,23 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "post",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
-          "kind": "PodScheduling",
-          "version": "v1alpha1"
+          "kind": "PodSchedulingContext",
+          "version": "v1alpha2"
         }
       }
     },
-    "/apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings/{name}": {
+    "/apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts/{name}": {
       "delete": {
         "consumes": [
           "*/*"
         ],
-        "description": "delete a PodScheduling",
-        "operationId": "deleteResourceV1alpha1NamespacedPodScheduling",
+        "description": "delete a PodSchedulingContext",
+        "operationId": "deleteResourceV1alpha2NamespacedPodSchedulingContext",
         "parameters": [
           {
             "in": "body",
@@ -76250,13 +80515,13 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodScheduling"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContext"
             }
           },
           "202": {
             "description": "Accepted",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodScheduling"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContext"
             }
           },
           "401": {
@@ -76267,21 +80532,21 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "delete",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
-          "kind": "PodScheduling",
-          "version": "v1alpha1"
+          "kind": "PodSchedulingContext",
+          "version": "v1alpha2"
         }
       },
       "get": {
         "consumes": [
           "*/*"
         ],
-        "description": "read the specified PodScheduling",
-        "operationId": "readResourceV1alpha1NamespacedPodScheduling",
+        "description": "read the specified PodSchedulingContext",
+        "operationId": "readResourceV1alpha2NamespacedPodSchedulingContext",
         "produces": [
           "application/json",
           "application/yaml",
@@ -76291,7 +80556,7 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodScheduling"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContext"
             }
           },
           "401": {
@@ -76302,18 +80567,18 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "get",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
-          "kind": "PodScheduling",
-          "version": "v1alpha1"
+          "kind": "PodSchedulingContext",
+          "version": "v1alpha2"
         }
       },
       "parameters": [
         {
-          "description": "name of the PodScheduling",
+          "description": "name of the PodSchedulingContext",
           "in": "path",
           "name": "name",
           "required": true,
@@ -76343,8 +80608,8 @@
           "application/strategic-merge-patch+json",
           "application/apply-patch+yaml"
         ],
-        "description": "partially update the specified PodScheduling",
-        "operationId": "patchResourceV1alpha1NamespacedPodScheduling",
+        "description": "partially update the specified PodSchedulingContext",
+        "operationId": "patchResourceV1alpha2NamespacedPodSchedulingContext",
         "parameters": [
           {
             "in": "body",
@@ -76369,7 +80634,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -76392,13 +80657,13 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodScheduling"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContext"
             }
           },
           "201": {
             "description": "Created",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodScheduling"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContext"
             }
           },
           "401": {
@@ -76409,28 +80674,28 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "patch",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
-          "kind": "PodScheduling",
-          "version": "v1alpha1"
+          "kind": "PodSchedulingContext",
+          "version": "v1alpha2"
         }
       },
       "put": {
         "consumes": [
           "*/*"
         ],
-        "description": "replace the specified PodScheduling",
-        "operationId": "replaceResourceV1alpha1NamespacedPodScheduling",
+        "description": "replace the specified PodSchedulingContext",
+        "operationId": "replaceResourceV1alpha2NamespacedPodSchedulingContext",
         "parameters": [
           {
             "in": "body",
             "name": "body",
             "required": true,
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodScheduling"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContext"
             }
           },
           {
@@ -76448,7 +80713,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -76464,13 +80729,13 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodScheduling"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContext"
             }
           },
           "201": {
             "description": "Created",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodScheduling"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContext"
             }
           },
           "401": {
@@ -76481,23 +80746,23 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "put",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
-          "kind": "PodScheduling",
-          "version": "v1alpha1"
+          "kind": "PodSchedulingContext",
+          "version": "v1alpha2"
         }
       }
     },
-    "/apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings/{name}/status": {
+    "/apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts/{name}/status": {
       "get": {
         "consumes": [
           "*/*"
         ],
-        "description": "read status of the specified PodScheduling",
-        "operationId": "readResourceV1alpha1NamespacedPodSchedulingStatus",
+        "description": "read status of the specified PodSchedulingContext",
+        "operationId": "readResourceV1alpha2NamespacedPodSchedulingContextStatus",
         "produces": [
           "application/json",
           "application/yaml",
@@ -76507,7 +80772,7 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodScheduling"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContext"
             }
           },
           "401": {
@@ -76518,18 +80783,18 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "get",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
-          "kind": "PodScheduling",
-          "version": "v1alpha1"
+          "kind": "PodSchedulingContext",
+          "version": "v1alpha2"
         }
       },
       "parameters": [
         {
-          "description": "name of the PodScheduling",
+          "description": "name of the PodSchedulingContext",
           "in": "path",
           "name": "name",
           "required": true,
@@ -76559,8 +80824,8 @@
           "application/strategic-merge-patch+json",
           "application/apply-patch+yaml"
         ],
-        "description": "partially update status of the specified PodScheduling",
-        "operationId": "patchResourceV1alpha1NamespacedPodSchedulingStatus",
+        "description": "partially update status of the specified PodSchedulingContext",
+        "operationId": "patchResourceV1alpha2NamespacedPodSchedulingContextStatus",
         "parameters": [
           {
             "in": "body",
@@ -76585,7 +80850,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -76608,13 +80873,13 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodScheduling"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContext"
             }
           },
           "201": {
             "description": "Created",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodScheduling"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContext"
             }
           },
           "401": {
@@ -76625,28 +80890,28 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "patch",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
-          "kind": "PodScheduling",
-          "version": "v1alpha1"
+          "kind": "PodSchedulingContext",
+          "version": "v1alpha2"
         }
       },
       "put": {
         "consumes": [
           "*/*"
         ],
-        "description": "replace status of the specified PodScheduling",
-        "operationId": "replaceResourceV1alpha1NamespacedPodSchedulingStatus",
+        "description": "replace status of the specified PodSchedulingContext",
+        "operationId": "replaceResourceV1alpha2NamespacedPodSchedulingContextStatus",
         "parameters": [
           {
             "in": "body",
             "name": "body",
             "required": true,
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodScheduling"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContext"
             }
           },
           {
@@ -76664,7 +80929,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -76680,13 +80945,13 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodScheduling"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContext"
             }
           },
           "201": {
             "description": "Created",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodScheduling"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContext"
             }
           },
           "401": {
@@ -76697,23 +80962,23 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "put",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
-          "kind": "PodScheduling",
-          "version": "v1alpha1"
+          "kind": "PodSchedulingContext",
+          "version": "v1alpha2"
         }
       }
     },
-    "/apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims": {
+    "/apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims": {
       "delete": {
         "consumes": [
           "*/*"
         ],
         "description": "delete collection of ResourceClaim",
-        "operationId": "deleteResourceV1alpha1CollectionNamespacedResourceClaim",
+        "operationId": "deleteResourceV1alpha2CollectionNamespacedResourceClaim",
         "parameters": [
           {
             "in": "body",
@@ -76792,6 +81057,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -76820,13 +81092,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "deletecollection",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaim",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "get": {
@@ -76834,7 +81106,7 @@
           "*/*"
         ],
         "description": "list or watch objects of kind ResourceClaim",
-        "operationId": "listResourceV1alpha1NamespacedResourceClaim",
+        "operationId": "listResourceV1alpha2NamespacedResourceClaim",
         "parameters": [
           {
             "description": "allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.",
@@ -76885,6 +81157,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -76911,7 +81190,7 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimList"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimList"
             }
           },
           "401": {
@@ -76922,13 +81201,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "list",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaim",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -76953,14 +81232,14 @@
           "*/*"
         ],
         "description": "create a ResourceClaim",
-        "operationId": "createResourceV1alpha1NamespacedResourceClaim",
+        "operationId": "createResourceV1alpha2NamespacedResourceClaim",
         "parameters": [
           {
             "in": "body",
             "name": "body",
             "required": true,
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaim"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaim"
             }
           },
           {
@@ -76978,7 +81257,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -76994,19 +81273,19 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaim"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaim"
             }
           },
           "201": {
             "description": "Created",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaim"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaim"
             }
           },
           "202": {
             "description": "Accepted",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaim"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaim"
             }
           },
           "401": {
@@ -77017,23 +81296,23 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "post",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaim",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       }
     },
-    "/apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name}": {
+    "/apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{name}": {
       "delete": {
         "consumes": [
           "*/*"
         ],
         "description": "delete a ResourceClaim",
-        "operationId": "deleteResourceV1alpha1NamespacedResourceClaim",
+        "operationId": "deleteResourceV1alpha2NamespacedResourceClaim",
         "parameters": [
           {
             "in": "body",
@@ -77080,13 +81359,13 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaim"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaim"
             }
           },
           "202": {
             "description": "Accepted",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaim"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaim"
             }
           },
           "401": {
@@ -77097,13 +81376,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "delete",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaim",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "get": {
@@ -77111,7 +81390,7 @@
           "*/*"
         ],
         "description": "read the specified ResourceClaim",
-        "operationId": "readResourceV1alpha1NamespacedResourceClaim",
+        "operationId": "readResourceV1alpha2NamespacedResourceClaim",
         "produces": [
           "application/json",
           "application/yaml",
@@ -77121,7 +81400,7 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaim"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaim"
             }
           },
           "401": {
@@ -77132,13 +81411,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "get",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaim",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -77174,7 +81453,7 @@
           "application/apply-patch+yaml"
         ],
         "description": "partially update the specified ResourceClaim",
-        "operationId": "patchResourceV1alpha1NamespacedResourceClaim",
+        "operationId": "patchResourceV1alpha2NamespacedResourceClaim",
         "parameters": [
           {
             "in": "body",
@@ -77199,7 +81478,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -77222,13 +81501,13 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaim"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaim"
             }
           },
           "201": {
             "description": "Created",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaim"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaim"
             }
           },
           "401": {
@@ -77239,13 +81518,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "patch",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaim",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "put": {
@@ -77253,14 +81532,14 @@
           "*/*"
         ],
         "description": "replace the specified ResourceClaim",
-        "operationId": "replaceResourceV1alpha1NamespacedResourceClaim",
+        "operationId": "replaceResourceV1alpha2NamespacedResourceClaim",
         "parameters": [
           {
             "in": "body",
             "name": "body",
             "required": true,
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaim"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaim"
             }
           },
           {
@@ -77278,7 +81557,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -77294,13 +81573,13 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaim"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaim"
             }
           },
           "201": {
             "description": "Created",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaim"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaim"
             }
           },
           "401": {
@@ -77311,23 +81590,23 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "put",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaim",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       }
     },
-    "/apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name}/status": {
+    "/apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{name}/status": {
       "get": {
         "consumes": [
           "*/*"
         ],
         "description": "read status of the specified ResourceClaim",
-        "operationId": "readResourceV1alpha1NamespacedResourceClaimStatus",
+        "operationId": "readResourceV1alpha2NamespacedResourceClaimStatus",
         "produces": [
           "application/json",
           "application/yaml",
@@ -77337,7 +81616,7 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaim"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaim"
             }
           },
           "401": {
@@ -77348,13 +81627,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "get",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaim",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -77390,7 +81669,7 @@
           "application/apply-patch+yaml"
         ],
         "description": "partially update status of the specified ResourceClaim",
-        "operationId": "patchResourceV1alpha1NamespacedResourceClaimStatus",
+        "operationId": "patchResourceV1alpha2NamespacedResourceClaimStatus",
         "parameters": [
           {
             "in": "body",
@@ -77415,7 +81694,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -77438,13 +81717,13 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaim"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaim"
             }
           },
           "201": {
             "description": "Created",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaim"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaim"
             }
           },
           "401": {
@@ -77455,13 +81734,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "patch",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaim",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "put": {
@@ -77469,14 +81748,14 @@
           "*/*"
         ],
         "description": "replace status of the specified ResourceClaim",
-        "operationId": "replaceResourceV1alpha1NamespacedResourceClaimStatus",
+        "operationId": "replaceResourceV1alpha2NamespacedResourceClaimStatus",
         "parameters": [
           {
             "in": "body",
             "name": "body",
             "required": true,
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaim"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaim"
             }
           },
           {
@@ -77494,7 +81773,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -77510,13 +81789,13 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaim"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaim"
             }
           },
           "201": {
             "description": "Created",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaim"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaim"
             }
           },
           "401": {
@@ -77527,23 +81806,23 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "put",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaim",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       }
     },
-    "/apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplates": {
+    "/apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaimtemplates": {
       "delete": {
         "consumes": [
           "*/*"
         ],
         "description": "delete collection of ResourceClaimTemplate",
-        "operationId": "deleteResourceV1alpha1CollectionNamespacedResourceClaimTemplate",
+        "operationId": "deleteResourceV1alpha2CollectionNamespacedResourceClaimTemplate",
         "parameters": [
           {
             "in": "body",
@@ -77622,6 +81901,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -77650,13 +81936,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "deletecollection",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaimTemplate",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "get": {
@@ -77664,7 +81950,7 @@
           "*/*"
         ],
         "description": "list or watch objects of kind ResourceClaimTemplate",
-        "operationId": "listResourceV1alpha1NamespacedResourceClaimTemplate",
+        "operationId": "listResourceV1alpha2NamespacedResourceClaimTemplate",
         "parameters": [
           {
             "description": "allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.",
@@ -77715,6 +82001,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -77741,7 +82034,7 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimTemplateList"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimTemplateList"
             }
           },
           "401": {
@@ -77752,13 +82045,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "list",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaimTemplate",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -77783,14 +82076,14 @@
           "*/*"
         ],
         "description": "create a ResourceClaimTemplate",
-        "operationId": "createResourceV1alpha1NamespacedResourceClaimTemplate",
+        "operationId": "createResourceV1alpha2NamespacedResourceClaimTemplate",
         "parameters": [
           {
             "in": "body",
             "name": "body",
             "required": true,
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimTemplate"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimTemplate"
             }
           },
           {
@@ -77808,7 +82101,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -77824,19 +82117,19 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimTemplate"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimTemplate"
             }
           },
           "201": {
             "description": "Created",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimTemplate"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimTemplate"
             }
           },
           "202": {
             "description": "Accepted",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimTemplate"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimTemplate"
             }
           },
           "401": {
@@ -77847,23 +82140,23 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "post",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaimTemplate",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       }
     },
-    "/apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplates/{name}": {
+    "/apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaimtemplates/{name}": {
       "delete": {
         "consumes": [
           "*/*"
         ],
         "description": "delete a ResourceClaimTemplate",
-        "operationId": "deleteResourceV1alpha1NamespacedResourceClaimTemplate",
+        "operationId": "deleteResourceV1alpha2NamespacedResourceClaimTemplate",
         "parameters": [
           {
             "in": "body",
@@ -77910,13 +82203,13 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimTemplate"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimTemplate"
             }
           },
           "202": {
             "description": "Accepted",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimTemplate"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimTemplate"
             }
           },
           "401": {
@@ -77927,13 +82220,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "delete",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaimTemplate",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "get": {
@@ -77941,7 +82234,7 @@
           "*/*"
         ],
         "description": "read the specified ResourceClaimTemplate",
-        "operationId": "readResourceV1alpha1NamespacedResourceClaimTemplate",
+        "operationId": "readResourceV1alpha2NamespacedResourceClaimTemplate",
         "produces": [
           "application/json",
           "application/yaml",
@@ -77951,7 +82244,7 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimTemplate"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimTemplate"
             }
           },
           "401": {
@@ -77962,13 +82255,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "get",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaimTemplate",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -78004,7 +82297,7 @@
           "application/apply-patch+yaml"
         ],
         "description": "partially update the specified ResourceClaimTemplate",
-        "operationId": "patchResourceV1alpha1NamespacedResourceClaimTemplate",
+        "operationId": "patchResourceV1alpha2NamespacedResourceClaimTemplate",
         "parameters": [
           {
             "in": "body",
@@ -78029,7 +82322,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -78052,13 +82345,13 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimTemplate"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimTemplate"
             }
           },
           "201": {
             "description": "Created",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimTemplate"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimTemplate"
             }
           },
           "401": {
@@ -78069,13 +82362,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "patch",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaimTemplate",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "put": {
@@ -78083,14 +82376,14 @@
           "*/*"
         ],
         "description": "replace the specified ResourceClaimTemplate",
-        "operationId": "replaceResourceV1alpha1NamespacedResourceClaimTemplate",
+        "operationId": "replaceResourceV1alpha2NamespacedResourceClaimTemplate",
         "parameters": [
           {
             "in": "body",
             "name": "body",
             "required": true,
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimTemplate"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimTemplate"
             }
           },
           {
@@ -78108,7 +82401,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -78124,13 +82417,13 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimTemplate"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimTemplate"
             }
           },
           "201": {
             "description": "Created",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimTemplate"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimTemplate"
             }
           },
           "401": {
@@ -78141,23 +82434,23 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "put",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaimTemplate",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       }
     },
-    "/apis/resource.k8s.io/v1alpha1/podschedulings": {
+    "/apis/resource.k8s.io/v1alpha2/podschedulingcontexts": {
       "get": {
         "consumes": [
           "*/*"
         ],
-        "description": "list or watch objects of kind PodScheduling",
-        "operationId": "listResourceV1alpha1PodSchedulingForAllNamespaces",
+        "description": "list or watch objects of kind PodSchedulingContext",
+        "operationId": "listResourceV1alpha2PodSchedulingContextForAllNamespaces",
         "produces": [
           "application/json",
           "application/yaml",
@@ -78169,7 +82462,7 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.PodSchedulingList"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.PodSchedulingContextList"
             }
           },
           "401": {
@@ -78180,13 +82473,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "list",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
-          "kind": "PodScheduling",
-          "version": "v1alpha1"
+          "kind": "PodSchedulingContext",
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -78246,6 +82539,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -78262,13 +82562,13 @@
         }
       ]
     },
-    "/apis/resource.k8s.io/v1alpha1/resourceclaims": {
+    "/apis/resource.k8s.io/v1alpha2/resourceclaims": {
       "get": {
         "consumes": [
           "*/*"
         ],
         "description": "list or watch objects of kind ResourceClaim",
-        "operationId": "listResourceV1alpha1ResourceClaimForAllNamespaces",
+        "operationId": "listResourceV1alpha2ResourceClaimForAllNamespaces",
         "produces": [
           "application/json",
           "application/yaml",
@@ -78280,7 +82580,7 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimList"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimList"
             }
           },
           "401": {
@@ -78291,13 +82591,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "list",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaim",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -78357,6 +82657,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -78373,13 +82680,13 @@
         }
       ]
     },
-    "/apis/resource.k8s.io/v1alpha1/resourceclaimtemplates": {
+    "/apis/resource.k8s.io/v1alpha2/resourceclaimtemplates": {
       "get": {
         "consumes": [
           "*/*"
         ],
         "description": "list or watch objects of kind ResourceClaimTemplate",
-        "operationId": "listResourceV1alpha1ResourceClaimTemplateForAllNamespaces",
+        "operationId": "listResourceV1alpha2ResourceClaimTemplateForAllNamespaces",
         "produces": [
           "application/json",
           "application/yaml",
@@ -78391,7 +82698,7 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClaimTemplateList"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClaimTemplateList"
             }
           },
           "401": {
@@ -78402,13 +82709,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "list",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaimTemplate",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -78468,6 +82775,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -78484,13 +82798,13 @@
         }
       ]
     },
-    "/apis/resource.k8s.io/v1alpha1/resourceclasses": {
+    "/apis/resource.k8s.io/v1alpha2/resourceclasses": {
       "delete": {
         "consumes": [
           "*/*"
         ],
         "description": "delete collection of ResourceClass",
-        "operationId": "deleteResourceV1alpha1CollectionResourceClass",
+        "operationId": "deleteResourceV1alpha2CollectionResourceClass",
         "parameters": [
           {
             "in": "body",
@@ -78569,6 +82883,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -78597,13 +82918,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "deletecollection",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClass",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "get": {
@@ -78611,7 +82932,7 @@
           "*/*"
         ],
         "description": "list or watch objects of kind ResourceClass",
-        "operationId": "listResourceV1alpha1ResourceClass",
+        "operationId": "listResourceV1alpha2ResourceClass",
         "parameters": [
           {
             "description": "allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.",
@@ -78662,6 +82983,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -78688,7 +83016,7 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClassList"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClassList"
             }
           },
           "401": {
@@ -78699,13 +83027,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "list",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClass",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -78722,14 +83050,14 @@
           "*/*"
         ],
         "description": "create a ResourceClass",
-        "operationId": "createResourceV1alpha1ResourceClass",
+        "operationId": "createResourceV1alpha2ResourceClass",
         "parameters": [
           {
             "in": "body",
             "name": "body",
             "required": true,
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClass"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClass"
             }
           },
           {
@@ -78747,7 +83075,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -78763,19 +83091,19 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClass"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClass"
             }
           },
           "201": {
             "description": "Created",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClass"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClass"
             }
           },
           "202": {
             "description": "Accepted",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClass"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClass"
             }
           },
           "401": {
@@ -78786,23 +83114,23 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "post",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClass",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       }
     },
-    "/apis/resource.k8s.io/v1alpha1/resourceclasses/{name}": {
+    "/apis/resource.k8s.io/v1alpha2/resourceclasses/{name}": {
       "delete": {
         "consumes": [
           "*/*"
         ],
         "description": "delete a ResourceClass",
-        "operationId": "deleteResourceV1alpha1ResourceClass",
+        "operationId": "deleteResourceV1alpha2ResourceClass",
         "parameters": [
           {
             "in": "body",
@@ -78849,13 +83177,13 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClass"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClass"
             }
           },
           "202": {
             "description": "Accepted",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClass"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClass"
             }
           },
           "401": {
@@ -78866,13 +83194,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "delete",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClass",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "get": {
@@ -78880,7 +83208,7 @@
           "*/*"
         ],
         "description": "read the specified ResourceClass",
-        "operationId": "readResourceV1alpha1ResourceClass",
+        "operationId": "readResourceV1alpha2ResourceClass",
         "produces": [
           "application/json",
           "application/yaml",
@@ -78890,7 +83218,7 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClass"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClass"
             }
           },
           "401": {
@@ -78901,13 +83229,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "get",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClass",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -78935,7 +83263,7 @@
           "application/apply-patch+yaml"
         ],
         "description": "partially update the specified ResourceClass",
-        "operationId": "patchResourceV1alpha1ResourceClass",
+        "operationId": "patchResourceV1alpha2ResourceClass",
         "parameters": [
           {
             "in": "body",
@@ -78960,7 +83288,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -78983,13 +83311,13 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClass"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClass"
             }
           },
           "201": {
             "description": "Created",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClass"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClass"
             }
           },
           "401": {
@@ -79000,13 +83328,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "patch",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClass",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "put": {
@@ -79014,14 +83342,14 @@
           "*/*"
         ],
         "description": "replace the specified ResourceClass",
-        "operationId": "replaceResourceV1alpha1ResourceClass",
+        "operationId": "replaceResourceV1alpha2ResourceClass",
         "parameters": [
           {
             "in": "body",
             "name": "body",
             "required": true,
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClass"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClass"
             }
           },
           {
@@ -79039,7 +83367,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -79055,13 +83383,13 @@
           "200": {
             "description": "OK",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClass"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClass"
             }
           },
           "201": {
             "description": "Created",
             "schema": {
-              "$ref": "#/definitions/io.k8s.api.resource.v1alpha1.ResourceClass"
+              "$ref": "#/definitions/io.k8s.api.resource.v1alpha2.ResourceClass"
             }
           },
           "401": {
@@ -79072,23 +83400,23 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "put",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClass",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       }
     },
-    "/apis/resource.k8s.io/v1alpha1/watch/namespaces/{namespace}/podschedulings": {
+    "/apis/resource.k8s.io/v1alpha2/watch/namespaces/{namespace}/podschedulingcontexts": {
       "get": {
         "consumes": [
           "*/*"
         ],
-        "description": "watch individual changes to a list of PodScheduling. deprecated: use the 'watch' parameter with a list operation instead.",
-        "operationId": "watchResourceV1alpha1NamespacedPodSchedulingList",
+        "description": "watch individual changes to a list of PodSchedulingContext. deprecated: use the 'watch' parameter with a list operation instead.",
+        "operationId": "watchResourceV1alpha2NamespacedPodSchedulingContextList",
         "produces": [
           "application/json",
           "application/yaml",
@@ -79111,13 +83439,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "watchlist",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
-          "kind": "PodScheduling",
-          "version": "v1alpha1"
+          "kind": "PodSchedulingContext",
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -79185,6 +83513,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -79201,13 +83536,13 @@
         }
       ]
     },
-    "/apis/resource.k8s.io/v1alpha1/watch/namespaces/{namespace}/podschedulings/{name}": {
+    "/apis/resource.k8s.io/v1alpha2/watch/namespaces/{namespace}/podschedulingcontexts/{name}": {
       "get": {
         "consumes": [
           "*/*"
         ],
-        "description": "watch changes to an object of kind PodScheduling. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.",
-        "operationId": "watchResourceV1alpha1NamespacedPodScheduling",
+        "description": "watch changes to an object of kind PodSchedulingContext. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.",
+        "operationId": "watchResourceV1alpha2NamespacedPodSchedulingContext",
         "produces": [
           "application/json",
           "application/yaml",
@@ -79230,13 +83565,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "watch",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
-          "kind": "PodScheduling",
-          "version": "v1alpha1"
+          "kind": "PodSchedulingContext",
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -79276,7 +83611,7 @@
           "uniqueItems": true
         },
         {
-          "description": "name of the PodScheduling",
+          "description": "name of the PodSchedulingContext",
           "in": "path",
           "name": "name",
           "required": true,
@@ -79312,6 +83647,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -79328,13 +83670,13 @@
         }
       ]
     },
-    "/apis/resource.k8s.io/v1alpha1/watch/namespaces/{namespace}/resourceclaims": {
+    "/apis/resource.k8s.io/v1alpha2/watch/namespaces/{namespace}/resourceclaims": {
       "get": {
         "consumes": [
           "*/*"
         ],
         "description": "watch individual changes to a list of ResourceClaim. deprecated: use the 'watch' parameter with a list operation instead.",
-        "operationId": "watchResourceV1alpha1NamespacedResourceClaimList",
+        "operationId": "watchResourceV1alpha2NamespacedResourceClaimList",
         "produces": [
           "application/json",
           "application/yaml",
@@ -79357,13 +83699,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "watchlist",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaim",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -79431,6 +83773,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -79447,13 +83796,13 @@
         }
       ]
     },
-    "/apis/resource.k8s.io/v1alpha1/watch/namespaces/{namespace}/resourceclaims/{name}": {
+    "/apis/resource.k8s.io/v1alpha2/watch/namespaces/{namespace}/resourceclaims/{name}": {
       "get": {
         "consumes": [
           "*/*"
         ],
         "description": "watch changes to an object of kind ResourceClaim. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.",
-        "operationId": "watchResourceV1alpha1NamespacedResourceClaim",
+        "operationId": "watchResourceV1alpha2NamespacedResourceClaim",
         "produces": [
           "application/json",
           "application/yaml",
@@ -79476,13 +83825,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "watch",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaim",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -79558,6 +83907,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -79574,13 +83930,13 @@
         }
       ]
     },
-    "/apis/resource.k8s.io/v1alpha1/watch/namespaces/{namespace}/resourceclaimtemplates": {
+    "/apis/resource.k8s.io/v1alpha2/watch/namespaces/{namespace}/resourceclaimtemplates": {
       "get": {
         "consumes": [
           "*/*"
         ],
         "description": "watch individual changes to a list of ResourceClaimTemplate. deprecated: use the 'watch' parameter with a list operation instead.",
-        "operationId": "watchResourceV1alpha1NamespacedResourceClaimTemplateList",
+        "operationId": "watchResourceV1alpha2NamespacedResourceClaimTemplateList",
         "produces": [
           "application/json",
           "application/yaml",
@@ -79603,13 +83959,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "watchlist",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaimTemplate",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -79677,6 +84033,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -79693,13 +84056,13 @@
         }
       ]
     },
-    "/apis/resource.k8s.io/v1alpha1/watch/namespaces/{namespace}/resourceclaimtemplates/{name}": {
+    "/apis/resource.k8s.io/v1alpha2/watch/namespaces/{namespace}/resourceclaimtemplates/{name}": {
       "get": {
         "consumes": [
           "*/*"
         ],
         "description": "watch changes to an object of kind ResourceClaimTemplate. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.",
-        "operationId": "watchResourceV1alpha1NamespacedResourceClaimTemplate",
+        "operationId": "watchResourceV1alpha2NamespacedResourceClaimTemplate",
         "produces": [
           "application/json",
           "application/yaml",
@@ -79722,13 +84085,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "watch",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaimTemplate",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -79804,6 +84167,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -79820,13 +84190,13 @@
         }
       ]
     },
-    "/apis/resource.k8s.io/v1alpha1/watch/podschedulings": {
+    "/apis/resource.k8s.io/v1alpha2/watch/podschedulingcontexts": {
       "get": {
         "consumes": [
           "*/*"
         ],
-        "description": "watch individual changes to a list of PodScheduling. deprecated: use the 'watch' parameter with a list operation instead.",
-        "operationId": "watchResourceV1alpha1PodSchedulingListForAllNamespaces",
+        "description": "watch individual changes to a list of PodSchedulingContext. deprecated: use the 'watch' parameter with a list operation instead.",
+        "operationId": "watchResourceV1alpha2PodSchedulingContextListForAllNamespaces",
         "produces": [
           "application/json",
           "application/yaml",
@@ -79849,13 +84219,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "watchlist",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
-          "kind": "PodScheduling",
-          "version": "v1alpha1"
+          "kind": "PodSchedulingContext",
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -79915,6 +84285,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -79931,13 +84308,13 @@
         }
       ]
     },
-    "/apis/resource.k8s.io/v1alpha1/watch/resourceclaims": {
+    "/apis/resource.k8s.io/v1alpha2/watch/resourceclaims": {
       "get": {
         "consumes": [
           "*/*"
         ],
         "description": "watch individual changes to a list of ResourceClaim. deprecated: use the 'watch' parameter with a list operation instead.",
-        "operationId": "watchResourceV1alpha1ResourceClaimListForAllNamespaces",
+        "operationId": "watchResourceV1alpha2ResourceClaimListForAllNamespaces",
         "produces": [
           "application/json",
           "application/yaml",
@@ -79960,13 +84337,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "watchlist",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaim",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -80026,6 +84403,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -80042,13 +84426,13 @@
         }
       ]
     },
-    "/apis/resource.k8s.io/v1alpha1/watch/resourceclaimtemplates": {
+    "/apis/resource.k8s.io/v1alpha2/watch/resourceclaimtemplates": {
       "get": {
         "consumes": [
           "*/*"
         ],
         "description": "watch individual changes to a list of ResourceClaimTemplate. deprecated: use the 'watch' parameter with a list operation instead.",
-        "operationId": "watchResourceV1alpha1ResourceClaimTemplateListForAllNamespaces",
+        "operationId": "watchResourceV1alpha2ResourceClaimTemplateListForAllNamespaces",
         "produces": [
           "application/json",
           "application/yaml",
@@ -80071,13 +84455,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "watchlist",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClaimTemplate",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -80137,6 +84521,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -80153,13 +84544,13 @@
         }
       ]
     },
-    "/apis/resource.k8s.io/v1alpha1/watch/resourceclasses": {
+    "/apis/resource.k8s.io/v1alpha2/watch/resourceclasses": {
       "get": {
         "consumes": [
           "*/*"
         ],
         "description": "watch individual changes to a list of ResourceClass. deprecated: use the 'watch' parameter with a list operation instead.",
-        "operationId": "watchResourceV1alpha1ResourceClassList",
+        "operationId": "watchResourceV1alpha2ResourceClassList",
         "produces": [
           "application/json",
           "application/yaml",
@@ -80182,13 +84573,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "watchlist",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClass",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -80248,6 +84639,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -80264,13 +84662,13 @@
         }
       ]
     },
-    "/apis/resource.k8s.io/v1alpha1/watch/resourceclasses/{name}": {
+    "/apis/resource.k8s.io/v1alpha2/watch/resourceclasses/{name}": {
       "get": {
         "consumes": [
           "*/*"
         ],
         "description": "watch changes to an object of kind ResourceClass. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.",
-        "operationId": "watchResourceV1alpha1ResourceClass",
+        "operationId": "watchResourceV1alpha2ResourceClass",
         "produces": [
           "application/json",
           "application/yaml",
@@ -80293,13 +84691,13 @@
           "https"
         ],
         "tags": [
-          "resource_v1alpha1"
+          "resource_v1alpha2"
         ],
         "x-kubernetes-action": "watch",
         "x-kubernetes-group-version-kind": {
           "group": "resource.k8s.io",
           "kind": "ResourceClass",
-          "version": "v1alpha1"
+          "version": "v1alpha2"
         }
       },
       "parameters": [
@@ -80367,6 +84765,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -80534,6 +84939,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -80627,6 +85039,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -80712,7 +85131,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -80925,7 +85344,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -81004,7 +85423,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -81142,6 +85561,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -81261,6 +85687,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -81428,6 +85861,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -81521,6 +85961,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -81606,7 +86053,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -81819,7 +86266,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -81898,7 +86345,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -82026,6 +86473,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -82119,6 +86573,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -82204,7 +86665,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -82417,7 +86878,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -82496,7 +86957,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -82634,6 +87095,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -82735,6 +87203,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -82828,6 +87303,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -82921,7 +87403,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -83142,7 +87624,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -83221,7 +87703,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -83349,6 +87831,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -83442,6 +87931,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -83527,7 +88023,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -83740,7 +88236,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -83819,7 +88315,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -83947,6 +88443,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -84040,6 +88543,13 @@
             "type": "string",
             "uniqueItems": true
           },
+          {
+            "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+            "in": "query",
+            "name": "sendInitialEvents",
+            "type": "boolean",
+            "uniqueItems": true
+          },
           {
             "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
             "in": "query",
@@ -84125,7 +88635,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -84338,7 +88848,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -84417,7 +88927,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -84546,7 +89056,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -84625,7 +89135,7 @@
             "uniqueItems": true
           },
           {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
+            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
             "in": "query",
             "name": "fieldValidation",
             "type": "string",
@@ -84763,6 +89273,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -84882,6 +89399,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -84993,6 +89517,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -85112,6 +89643,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -85223,6 +89761,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -85342,6 +89887,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -85469,6 +90021,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -85580,6 +90139,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -85699,6 +90265,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -85810,6 +90383,13 @@
           "type": "string",
           "uniqueItems": true
         },
+        {
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+          "in": "query",
+          "name": "sendInitialEvents",
+          "type": "boolean",
+          "uniqueItems": true
+        },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
           "in": "query",
@@ -85930,1119 +90510,11 @@
           "uniqueItems": true
         },
         {
-          "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
+          "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
           "in": "query",
-          "name": "timeoutSeconds",
-          "type": "integer",
-          "uniqueItems": true
-        },
-        {
-          "description": "Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.",
-          "in": "query",
-          "name": "watch",
+          "name": "sendInitialEvents",
           "type": "boolean",
           "uniqueItems": true
-        }
-      ]
-    },
-    "/apis/storage.k8s.io/v1beta1/": {
-      "get": {
-        "consumes": [
-          "application/json",
-          "application/yaml",
-          "application/vnd.kubernetes.protobuf"
-        ],
-        "description": "get available resources",
-        "operationId": "getStorageV1beta1APIResources",
-        "produces": [
-          "application/json",
-          "application/yaml",
-          "application/vnd.kubernetes.protobuf"
-        ],
-        "responses": {
-          "200": {
-            "description": "OK",
-            "schema": {
-              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.APIResourceList"
-            }
-          },
-          "401": {
-            "description": "Unauthorized"
-          }
-        },
-        "schemes": [
-          "https"
-        ],
-        "tags": [
-          "storage_v1beta1"
-        ]
-      }
-    },
-    "/apis/storage.k8s.io/v1beta1/csistoragecapacities": {
-      "get": {
-        "consumes": [
-          "*/*"
-        ],
-        "description": "list or watch objects of kind CSIStorageCapacity",
-        "operationId": "listStorageV1beta1CSIStorageCapacityForAllNamespaces",
-        "produces": [
-          "application/json",
-          "application/yaml",
-          "application/vnd.kubernetes.protobuf",
-          "application/json;stream=watch",
-          "application/vnd.kubernetes.protobuf;stream=watch"
-        ],
-        "responses": {
-          "200": {
-            "description": "OK",
-            "schema": {
-              "$ref": "#/definitions/io.k8s.api.storage.v1beta1.CSIStorageCapacityList"
-            }
-          },
-          "401": {
-            "description": "Unauthorized"
-          }
-        },
-        "schemes": [
-          "https"
-        ],
-        "tags": [
-          "storage_v1beta1"
-        ],
-        "x-kubernetes-action": "list",
-        "x-kubernetes-group-version-kind": {
-          "group": "storage.k8s.io",
-          "kind": "CSIStorageCapacity",
-          "version": "v1beta1"
-        }
-      },
-      "parameters": [
-        {
-          "description": "allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.",
-          "in": "query",
-          "name": "allowWatchBookmarks",
-          "type": "boolean",
-          "uniqueItems": true
-        },
-        {
-          "description": "The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
-          "in": "query",
-          "name": "continue",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
-          "in": "query",
-          "name": "fieldSelector",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
-          "in": "query",
-          "name": "labelSelector",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
-          "in": "query",
-          "name": "limit",
-          "type": "integer",
-          "uniqueItems": true
-        },
-        {
-          "description": "If 'true', then the output is pretty printed.",
-          "in": "query",
-          "name": "pretty",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
-          "in": "query",
-          "name": "resourceVersion",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
-          "in": "query",
-          "name": "resourceVersionMatch",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
-          "in": "query",
-          "name": "timeoutSeconds",
-          "type": "integer",
-          "uniqueItems": true
-        },
-        {
-          "description": "Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.",
-          "in": "query",
-          "name": "watch",
-          "type": "boolean",
-          "uniqueItems": true
-        }
-      ]
-    },
-    "/apis/storage.k8s.io/v1beta1/namespaces/{namespace}/csistoragecapacities": {
-      "delete": {
-        "consumes": [
-          "*/*"
-        ],
-        "description": "delete collection of CSIStorageCapacity",
-        "operationId": "deleteStorageV1beta1CollectionNamespacedCSIStorageCapacity",
-        "parameters": [
-          {
-            "in": "body",
-            "name": "body",
-            "schema": {
-              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
-            }
-          },
-          {
-            "description": "The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
-            "in": "query",
-            "name": "continue",
-            "type": "string",
-            "uniqueItems": true
-          },
-          {
-            "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
-            "in": "query",
-            "name": "dryRun",
-            "type": "string",
-            "uniqueItems": true
-          },
-          {
-            "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
-            "in": "query",
-            "name": "fieldSelector",
-            "type": "string",
-            "uniqueItems": true
-          },
-          {
-            "description": "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.",
-            "in": "query",
-            "name": "gracePeriodSeconds",
-            "type": "integer",
-            "uniqueItems": true
-          },
-          {
-            "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
-            "in": "query",
-            "name": "labelSelector",
-            "type": "string",
-            "uniqueItems": true
-          },
-          {
-            "description": "limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
-            "in": "query",
-            "name": "limit",
-            "type": "integer",
-            "uniqueItems": true
-          },
-          {
-            "description": "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.",
-            "in": "query",
-            "name": "orphanDependents",
-            "type": "boolean",
-            "uniqueItems": true
-          },
-          {
-            "description": "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.",
-            "in": "query",
-            "name": "propagationPolicy",
-            "type": "string",
-            "uniqueItems": true
-          },
-          {
-            "description": "resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
-            "in": "query",
-            "name": "resourceVersion",
-            "type": "string",
-            "uniqueItems": true
-          },
-          {
-            "description": "resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
-            "in": "query",
-            "name": "resourceVersionMatch",
-            "type": "string",
-            "uniqueItems": true
-          },
-          {
-            "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
-            "in": "query",
-            "name": "timeoutSeconds",
-            "type": "integer",
-            "uniqueItems": true
-          }
-        ],
-        "produces": [
-          "application/json",
-          "application/yaml",
-          "application/vnd.kubernetes.protobuf"
-        ],
-        "responses": {
-          "200": {
-            "description": "OK",
-            "schema": {
-              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"
-            }
-          },
-          "401": {
-            "description": "Unauthorized"
-          }
-        },
-        "schemes": [
-          "https"
-        ],
-        "tags": [
-          "storage_v1beta1"
-        ],
-        "x-kubernetes-action": "deletecollection",
-        "x-kubernetes-group-version-kind": {
-          "group": "storage.k8s.io",
-          "kind": "CSIStorageCapacity",
-          "version": "v1beta1"
-        }
-      },
-      "get": {
-        "consumes": [
-          "*/*"
-        ],
-        "description": "list or watch objects of kind CSIStorageCapacity",
-        "operationId": "listStorageV1beta1NamespacedCSIStorageCapacity",
-        "parameters": [
-          {
-            "description": "allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.",
-            "in": "query",
-            "name": "allowWatchBookmarks",
-            "type": "boolean",
-            "uniqueItems": true
-          },
-          {
-            "description": "The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
-            "in": "query",
-            "name": "continue",
-            "type": "string",
-            "uniqueItems": true
-          },
-          {
-            "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
-            "in": "query",
-            "name": "fieldSelector",
-            "type": "string",
-            "uniqueItems": true
-          },
-          {
-            "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
-            "in": "query",
-            "name": "labelSelector",
-            "type": "string",
-            "uniqueItems": true
-          },
-          {
-            "description": "limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
-            "in": "query",
-            "name": "limit",
-            "type": "integer",
-            "uniqueItems": true
-          },
-          {
-            "description": "resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
-            "in": "query",
-            "name": "resourceVersion",
-            "type": "string",
-            "uniqueItems": true
-          },
-          {
-            "description": "resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
-            "in": "query",
-            "name": "resourceVersionMatch",
-            "type": "string",
-            "uniqueItems": true
-          },
-          {
-            "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
-            "in": "query",
-            "name": "timeoutSeconds",
-            "type": "integer",
-            "uniqueItems": true
-          },
-          {
-            "description": "Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.",
-            "in": "query",
-            "name": "watch",
-            "type": "boolean",
-            "uniqueItems": true
-          }
-        ],
-        "produces": [
-          "application/json",
-          "application/yaml",
-          "application/vnd.kubernetes.protobuf",
-          "application/json;stream=watch",
-          "application/vnd.kubernetes.protobuf;stream=watch"
-        ],
-        "responses": {
-          "200": {
-            "description": "OK",
-            "schema": {
-              "$ref": "#/definitions/io.k8s.api.storage.v1beta1.CSIStorageCapacityList"
-            }
-          },
-          "401": {
-            "description": "Unauthorized"
-          }
-        },
-        "schemes": [
-          "https"
-        ],
-        "tags": [
-          "storage_v1beta1"
-        ],
-        "x-kubernetes-action": "list",
-        "x-kubernetes-group-version-kind": {
-          "group": "storage.k8s.io",
-          "kind": "CSIStorageCapacity",
-          "version": "v1beta1"
-        }
-      },
-      "parameters": [
-        {
-          "description": "object name and auth scope, such as for teams and projects",
-          "in": "path",
-          "name": "namespace",
-          "required": true,
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "If 'true', then the output is pretty printed.",
-          "in": "query",
-          "name": "pretty",
-          "type": "string",
-          "uniqueItems": true
-        }
-      ],
-      "post": {
-        "consumes": [
-          "*/*"
-        ],
-        "description": "create a CSIStorageCapacity",
-        "operationId": "createStorageV1beta1NamespacedCSIStorageCapacity",
-        "parameters": [
-          {
-            "in": "body",
-            "name": "body",
-            "required": true,
-            "schema": {
-              "$ref": "#/definitions/io.k8s.api.storage.v1beta1.CSIStorageCapacity"
-            }
-          },
-          {
-            "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
-            "in": "query",
-            "name": "dryRun",
-            "type": "string",
-            "uniqueItems": true
-          },
-          {
-            "description": "fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.",
-            "in": "query",
-            "name": "fieldManager",
-            "type": "string",
-            "uniqueItems": true
-          },
-          {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
-            "in": "query",
-            "name": "fieldValidation",
-            "type": "string",
-            "uniqueItems": true
-          }
-        ],
-        "produces": [
-          "application/json",
-          "application/yaml",
-          "application/vnd.kubernetes.protobuf"
-        ],
-        "responses": {
-          "200": {
-            "description": "OK",
-            "schema": {
-              "$ref": "#/definitions/io.k8s.api.storage.v1beta1.CSIStorageCapacity"
-            }
-          },
-          "201": {
-            "description": "Created",
-            "schema": {
-              "$ref": "#/definitions/io.k8s.api.storage.v1beta1.CSIStorageCapacity"
-            }
-          },
-          "202": {
-            "description": "Accepted",
-            "schema": {
-              "$ref": "#/definitions/io.k8s.api.storage.v1beta1.CSIStorageCapacity"
-            }
-          },
-          "401": {
-            "description": "Unauthorized"
-          }
-        },
-        "schemes": [
-          "https"
-        ],
-        "tags": [
-          "storage_v1beta1"
-        ],
-        "x-kubernetes-action": "post",
-        "x-kubernetes-group-version-kind": {
-          "group": "storage.k8s.io",
-          "kind": "CSIStorageCapacity",
-          "version": "v1beta1"
-        }
-      }
-    },
-    "/apis/storage.k8s.io/v1beta1/namespaces/{namespace}/csistoragecapacities/{name}": {
-      "delete": {
-        "consumes": [
-          "*/*"
-        ],
-        "description": "delete a CSIStorageCapacity",
-        "operationId": "deleteStorageV1beta1NamespacedCSIStorageCapacity",
-        "parameters": [
-          {
-            "in": "body",
-            "name": "body",
-            "schema": {
-              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
-            }
-          },
-          {
-            "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
-            "in": "query",
-            "name": "dryRun",
-            "type": "string",
-            "uniqueItems": true
-          },
-          {
-            "description": "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.",
-            "in": "query",
-            "name": "gracePeriodSeconds",
-            "type": "integer",
-            "uniqueItems": true
-          },
-          {
-            "description": "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.",
-            "in": "query",
-            "name": "orphanDependents",
-            "type": "boolean",
-            "uniqueItems": true
-          },
-          {
-            "description": "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.",
-            "in": "query",
-            "name": "propagationPolicy",
-            "type": "string",
-            "uniqueItems": true
-          }
-        ],
-        "produces": [
-          "application/json",
-          "application/yaml",
-          "application/vnd.kubernetes.protobuf"
-        ],
-        "responses": {
-          "200": {
-            "description": "OK",
-            "schema": {
-              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"
-            }
-          },
-          "202": {
-            "description": "Accepted",
-            "schema": {
-              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status"
-            }
-          },
-          "401": {
-            "description": "Unauthorized"
-          }
-        },
-        "schemes": [
-          "https"
-        ],
-        "tags": [
-          "storage_v1beta1"
-        ],
-        "x-kubernetes-action": "delete",
-        "x-kubernetes-group-version-kind": {
-          "group": "storage.k8s.io",
-          "kind": "CSIStorageCapacity",
-          "version": "v1beta1"
-        }
-      },
-      "get": {
-        "consumes": [
-          "*/*"
-        ],
-        "description": "read the specified CSIStorageCapacity",
-        "operationId": "readStorageV1beta1NamespacedCSIStorageCapacity",
-        "produces": [
-          "application/json",
-          "application/yaml",
-          "application/vnd.kubernetes.protobuf"
-        ],
-        "responses": {
-          "200": {
-            "description": "OK",
-            "schema": {
-              "$ref": "#/definitions/io.k8s.api.storage.v1beta1.CSIStorageCapacity"
-            }
-          },
-          "401": {
-            "description": "Unauthorized"
-          }
-        },
-        "schemes": [
-          "https"
-        ],
-        "tags": [
-          "storage_v1beta1"
-        ],
-        "x-kubernetes-action": "get",
-        "x-kubernetes-group-version-kind": {
-          "group": "storage.k8s.io",
-          "kind": "CSIStorageCapacity",
-          "version": "v1beta1"
-        }
-      },
-      "parameters": [
-        {
-          "description": "name of the CSIStorageCapacity",
-          "in": "path",
-          "name": "name",
-          "required": true,
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "object name and auth scope, such as for teams and projects",
-          "in": "path",
-          "name": "namespace",
-          "required": true,
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "If 'true', then the output is pretty printed.",
-          "in": "query",
-          "name": "pretty",
-          "type": "string",
-          "uniqueItems": true
-        }
-      ],
-      "patch": {
-        "consumes": [
-          "application/json-patch+json",
-          "application/merge-patch+json",
-          "application/strategic-merge-patch+json",
-          "application/apply-patch+yaml"
-        ],
-        "description": "partially update the specified CSIStorageCapacity",
-        "operationId": "patchStorageV1beta1NamespacedCSIStorageCapacity",
-        "parameters": [
-          {
-            "in": "body",
-            "name": "body",
-            "required": true,
-            "schema": {
-              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
-            }
-          },
-          {
-            "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
-            "in": "query",
-            "name": "dryRun",
-            "type": "string",
-            "uniqueItems": true
-          },
-          {
-            "description": "fieldManager is a name associated with the actor or entity that is making these changes. 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).",
-            "in": "query",
-            "name": "fieldManager",
-            "type": "string",
-            "uniqueItems": true
-          },
-          {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
-            "in": "query",
-            "name": "fieldValidation",
-            "type": "string",
-            "uniqueItems": true
-          },
-          {
-            "description": "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.",
-            "in": "query",
-            "name": "force",
-            "type": "boolean",
-            "uniqueItems": true
-          }
-        ],
-        "produces": [
-          "application/json",
-          "application/yaml",
-          "application/vnd.kubernetes.protobuf"
-        ],
-        "responses": {
-          "200": {
-            "description": "OK",
-            "schema": {
-              "$ref": "#/definitions/io.k8s.api.storage.v1beta1.CSIStorageCapacity"
-            }
-          },
-          "201": {
-            "description": "Created",
-            "schema": {
-              "$ref": "#/definitions/io.k8s.api.storage.v1beta1.CSIStorageCapacity"
-            }
-          },
-          "401": {
-            "description": "Unauthorized"
-          }
-        },
-        "schemes": [
-          "https"
-        ],
-        "tags": [
-          "storage_v1beta1"
-        ],
-        "x-kubernetes-action": "patch",
-        "x-kubernetes-group-version-kind": {
-          "group": "storage.k8s.io",
-          "kind": "CSIStorageCapacity",
-          "version": "v1beta1"
-        }
-      },
-      "put": {
-        "consumes": [
-          "*/*"
-        ],
-        "description": "replace the specified CSIStorageCapacity",
-        "operationId": "replaceStorageV1beta1NamespacedCSIStorageCapacity",
-        "parameters": [
-          {
-            "in": "body",
-            "name": "body",
-            "required": true,
-            "schema": {
-              "$ref": "#/definitions/io.k8s.api.storage.v1beta1.CSIStorageCapacity"
-            }
-          },
-          {
-            "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
-            "in": "query",
-            "name": "dryRun",
-            "type": "string",
-            "uniqueItems": true
-          },
-          {
-            "description": "fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.",
-            "in": "query",
-            "name": "fieldManager",
-            "type": "string",
-            "uniqueItems": true
-          },
-          {
-            "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
-            "in": "query",
-            "name": "fieldValidation",
-            "type": "string",
-            "uniqueItems": true
-          }
-        ],
-        "produces": [
-          "application/json",
-          "application/yaml",
-          "application/vnd.kubernetes.protobuf"
-        ],
-        "responses": {
-          "200": {
-            "description": "OK",
-            "schema": {
-              "$ref": "#/definitions/io.k8s.api.storage.v1beta1.CSIStorageCapacity"
-            }
-          },
-          "201": {
-            "description": "Created",
-            "schema": {
-              "$ref": "#/definitions/io.k8s.api.storage.v1beta1.CSIStorageCapacity"
-            }
-          },
-          "401": {
-            "description": "Unauthorized"
-          }
-        },
-        "schemes": [
-          "https"
-        ],
-        "tags": [
-          "storage_v1beta1"
-        ],
-        "x-kubernetes-action": "put",
-        "x-kubernetes-group-version-kind": {
-          "group": "storage.k8s.io",
-          "kind": "CSIStorageCapacity",
-          "version": "v1beta1"
-        }
-      }
-    },
-    "/apis/storage.k8s.io/v1beta1/watch/csistoragecapacities": {
-      "get": {
-        "consumes": [
-          "*/*"
-        ],
-        "description": "watch individual changes to a list of CSIStorageCapacity. deprecated: use the 'watch' parameter with a list operation instead.",
-        "operationId": "watchStorageV1beta1CSIStorageCapacityListForAllNamespaces",
-        "produces": [
-          "application/json",
-          "application/yaml",
-          "application/vnd.kubernetes.protobuf",
-          "application/json;stream=watch",
-          "application/vnd.kubernetes.protobuf;stream=watch"
-        ],
-        "responses": {
-          "200": {
-            "description": "OK",
-            "schema": {
-              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"
-            }
-          },
-          "401": {
-            "description": "Unauthorized"
-          }
-        },
-        "schemes": [
-          "https"
-        ],
-        "tags": [
-          "storage_v1beta1"
-        ],
-        "x-kubernetes-action": "watchlist",
-        "x-kubernetes-group-version-kind": {
-          "group": "storage.k8s.io",
-          "kind": "CSIStorageCapacity",
-          "version": "v1beta1"
-        }
-      },
-      "parameters": [
-        {
-          "description": "allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.",
-          "in": "query",
-          "name": "allowWatchBookmarks",
-          "type": "boolean",
-          "uniqueItems": true
-        },
-        {
-          "description": "The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
-          "in": "query",
-          "name": "continue",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
-          "in": "query",
-          "name": "fieldSelector",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
-          "in": "query",
-          "name": "labelSelector",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
-          "in": "query",
-          "name": "limit",
-          "type": "integer",
-          "uniqueItems": true
-        },
-        {
-          "description": "If 'true', then the output is pretty printed.",
-          "in": "query",
-          "name": "pretty",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
-          "in": "query",
-          "name": "resourceVersion",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
-          "in": "query",
-          "name": "resourceVersionMatch",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
-          "in": "query",
-          "name": "timeoutSeconds",
-          "type": "integer",
-          "uniqueItems": true
-        },
-        {
-          "description": "Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.",
-          "in": "query",
-          "name": "watch",
-          "type": "boolean",
-          "uniqueItems": true
-        }
-      ]
-    },
-    "/apis/storage.k8s.io/v1beta1/watch/namespaces/{namespace}/csistoragecapacities": {
-      "get": {
-        "consumes": [
-          "*/*"
-        ],
-        "description": "watch individual changes to a list of CSIStorageCapacity. deprecated: use the 'watch' parameter with a list operation instead.",
-        "operationId": "watchStorageV1beta1NamespacedCSIStorageCapacityList",
-        "produces": [
-          "application/json",
-          "application/yaml",
-          "application/vnd.kubernetes.protobuf",
-          "application/json;stream=watch",
-          "application/vnd.kubernetes.protobuf;stream=watch"
-        ],
-        "responses": {
-          "200": {
-            "description": "OK",
-            "schema": {
-              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"
-            }
-          },
-          "401": {
-            "description": "Unauthorized"
-          }
-        },
-        "schemes": [
-          "https"
-        ],
-        "tags": [
-          "storage_v1beta1"
-        ],
-        "x-kubernetes-action": "watchlist",
-        "x-kubernetes-group-version-kind": {
-          "group": "storage.k8s.io",
-          "kind": "CSIStorageCapacity",
-          "version": "v1beta1"
-        }
-      },
-      "parameters": [
-        {
-          "description": "allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.",
-          "in": "query",
-          "name": "allowWatchBookmarks",
-          "type": "boolean",
-          "uniqueItems": true
-        },
-        {
-          "description": "The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
-          "in": "query",
-          "name": "continue",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
-          "in": "query",
-          "name": "fieldSelector",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
-          "in": "query",
-          "name": "labelSelector",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
-          "in": "query",
-          "name": "limit",
-          "type": "integer",
-          "uniqueItems": true
-        },
-        {
-          "description": "object name and auth scope, such as for teams and projects",
-          "in": "path",
-          "name": "namespace",
-          "required": true,
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "If 'true', then the output is pretty printed.",
-          "in": "query",
-          "name": "pretty",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
-          "in": "query",
-          "name": "resourceVersion",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
-          "in": "query",
-          "name": "resourceVersionMatch",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
-          "in": "query",
-          "name": "timeoutSeconds",
-          "type": "integer",
-          "uniqueItems": true
-        },
-        {
-          "description": "Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.",
-          "in": "query",
-          "name": "watch",
-          "type": "boolean",
-          "uniqueItems": true
-        }
-      ]
-    },
-    "/apis/storage.k8s.io/v1beta1/watch/namespaces/{namespace}/csistoragecapacities/{name}": {
-      "get": {
-        "consumes": [
-          "*/*"
-        ],
-        "description": "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.",
-        "operationId": "watchStorageV1beta1NamespacedCSIStorageCapacity",
-        "produces": [
-          "application/json",
-          "application/yaml",
-          "application/vnd.kubernetes.protobuf",
-          "application/json;stream=watch",
-          "application/vnd.kubernetes.protobuf;stream=watch"
-        ],
-        "responses": {
-          "200": {
-            "description": "OK",
-            "schema": {
-              "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.WatchEvent"
-            }
-          },
-          "401": {
-            "description": "Unauthorized"
-          }
-        },
-        "schemes": [
-          "https"
-        ],
-        "tags": [
-          "storage_v1beta1"
-        ],
-        "x-kubernetes-action": "watch",
-        "x-kubernetes-group-version-kind": {
-          "group": "storage.k8s.io",
-          "kind": "CSIStorageCapacity",
-          "version": "v1beta1"
-        }
-      },
-      "parameters": [
-        {
-          "description": "allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.",
-          "in": "query",
-          "name": "allowWatchBookmarks",
-          "type": "boolean",
-          "uniqueItems": true
-        },
-        {
-          "description": "The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
-          "in": "query",
-          "name": "continue",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
-          "in": "query",
-          "name": "fieldSelector",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
-          "in": "query",
-          "name": "labelSelector",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
-          "in": "query",
-          "name": "limit",
-          "type": "integer",
-          "uniqueItems": true
-        },
-        {
-          "description": "name of the CSIStorageCapacity",
-          "in": "path",
-          "name": "name",
-          "required": true,
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "object name and auth scope, such as for teams and projects",
-          "in": "path",
-          "name": "namespace",
-          "required": true,
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "If 'true', then the output is pretty printed.",
-          "in": "query",
-          "name": "pretty",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
-          "in": "query",
-          "name": "resourceVersion",
-          "type": "string",
-          "uniqueItems": true
-        },
-        {
-          "description": "resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.\n\nDefaults to unset",
-          "in": "query",
-          "name": "resourceVersionMatch",
-          "type": "string",
-          "uniqueItems": true
         },
         {
           "description": "Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
diff --git a/api-ref-assets/config/fields.yaml b/api-ref-assets/config/fields.yaml
index 60e76f6c299..4f78cffcf7a 100644
--- a/api-ref-assets/config/fields.yaml
+++ b/api-ref-assets/config/fields.yaml
@@ -99,6 +99,7 @@
     - initContainerStatuses
     - containerStatuses
     - ephemeralContainerStatuses
+    - resize
 
 - definition: io.k8s.api.core.v1.Container
   field_categories:
@@ -127,6 +128,7 @@
   - name: Resources
     fields:
     - resources
+    - resizePolicy
   - name: Lifecycle
     fields:
     - lifecycle
@@ -219,6 +221,9 @@
     fields:
     - volumeMounts
     - volumeDevices
+  - name: Resources
+    fields:
+    - resizePolicy
   - name: Lifecycle
     fields:
     - terminationMessagePath
diff --git a/api-ref-assets/config/toc.yaml b/api-ref-assets/config/toc.yaml
index 0c720538739..77bd3cbe9df 100644
--- a/api-ref-assets/config/toc.yaml
+++ b/api-ref-assets/config/toc.yaml
@@ -66,18 +66,18 @@ parts:
   - name: PriorityClass
     group: scheduling.k8s.io
     version: v1
-  - name: PodScheduling
+  - name: PodSchedulingContext
     group: resource.k8s.io
-    version: v1alpha1
+    version: v1alpha2
   - name: ResourceClaim
     group: resource.k8s.io
-    version: v1alpha1
+    version: v1alpha2
   - name: ResourceClaimTemplate
     group: resource.k8s.io
-    version: v1alpha1
+    version: v1alpha2
   - name: ResourceClass
     group: resource.k8s.io
-    version: v1alpha1
+    version: v1alpha2
 - name: Service Resources
   chapters:
   - name: Service
@@ -148,6 +148,12 @@ parts:
   - name: CertificateSigningRequest
     group: certificates.k8s.io
     version: v1
+  - name: ClusterTrustBundle
+    group: certificates.k8s.io
+    version: v1alpha1
+  - name: SelfSubjectReview
+    group: authentication.k8s.io
+    version: v1beta1
 - name: Authorization Resources
   chapters:
   - name: LocalSubjectAccessReview
@@ -191,6 +197,9 @@ parts:
   - name: PodDisruptionBudget
     group: policy
     version: v1
+  - name: IPAddress
+    group: networking.k8s.io
+    version: v1alpha1
 - name: Extend Resources
   chapters:
   - name: CustomResourceDefinition
diff --git a/content/en/docs/reference/kubernetes-api/authentication-resources/certificate-signing-request-v1.md b/content/en/docs/reference/kubernetes-api/authentication-resources/certificate-signing-request-v1.md
index 6d262358596..e462d8ad876 100644
--- a/content/en/docs/reference/kubernetes-api/authentication-resources/certificate-signing-request-v1.md
+++ b/content/en/docs/reference/kubernetes-api/authentication-resources/certificate-signing-request-v1.md
@@ -404,6 +404,11 @@ GET /apis/certificates.k8s.io/v1/certificatesigningrequests
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -899,6 +904,11 @@ DELETE /apis/certificates.k8s.io/v1/certificatesigningrequests
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/authentication-resources/cluster-trust-bundle-v1alpha1.md b/content/en/docs/reference/kubernetes-api/authentication-resources/cluster-trust-bundle-v1alpha1.md
new file mode 100644
index 00000000000..97449346323
--- /dev/null
+++ b/content/en/docs/reference/kubernetes-api/authentication-resources/cluster-trust-bundle-v1alpha1.md
@@ -0,0 +1,506 @@
+---
+api_metadata:
+  apiVersion: "certificates.k8s.io/v1alpha1"
+  import: "k8s.io/api/certificates/v1alpha1"
+  kind: "ClusterTrustBundle"
+content_type: "api_reference"
+description: "ClusterTrustBundle is a cluster-scoped container for X."
+title: "ClusterTrustBundle v1alpha1"
+weight: 5
+auto_generated: true
+---
+
+<!--
+The file is auto-generated from the Go source code of the component using a generic
+[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
+to generate the reference documentation, please read
+[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
+To update the reference content, please follow the 
+[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
+guide. You can file document formatting bugs against the
+[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
+-->
+
+`apiVersion: certificates.k8s.io/v1alpha1`
+
+`import "k8s.io/api/certificates/v1alpha1"`
+
+
+## ClusterTrustBundle {#ClusterTrustBundle}
+
+ClusterTrustBundle is a cluster-scoped container for X.509 trust anchors (root certificates).
+
+ClusterTrustBundle objects are considered to be readable by any authenticated user in the cluster, because they can be mounted by pods using the `clusterTrustBundle` projection.  All service accounts have read access to ClusterTrustBundles by default.  Users who only have namespace-level access to a cluster can read ClusterTrustBundles by impersonating a serviceaccount that they have access to.
+
+It can be optionally associated with a particular assigner, in which case it contains one valid set of trust anchors for that signer. Signers may have multiple associated ClusterTrustBundles; each is an independent set of trust anchors for that signer. Admission control is used to enforce that only users with permissions on the signer can create or modify the corresponding bundle.
+
+<hr>
+
+- **apiVersion**: certificates.k8s.io/v1alpha1
+
+
+- **kind**: ClusterTrustBundle
+
+
+- **metadata** (<a href="{{< ref "../common-definitions/object-meta#ObjectMeta" >}}">ObjectMeta</a>)
+
+  metadata contains the object metadata.
+
+- **spec** (<a href="{{< ref "../authentication-resources/cluster-trust-bundle-v1alpha1#ClusterTrustBundleSpec" >}}">ClusterTrustBundleSpec</a>), required
+
+  spec contains the signer (if any) and trust anchors.
+
+
+
+
+
+## ClusterTrustBundleSpec {#ClusterTrustBundleSpec}
+
+ClusterTrustBundleSpec contains the signer and trust anchors.
+
+<hr>
+
+- **trustBundle** (string), required
+
+  trustBundle contains the individual X.509 trust anchors for this bundle, as PEM bundle of PEM-wrapped, DER-formatted X.509 certificates.
+  
+  The data must consist only of PEM certificate blocks that parse as valid X.509 certificates.  Each certificate must include a basic constraints extension with the CA bit set.  The API server will reject objects that contain duplicate certificates, or that use PEM block headers.
+  
+  Users of ClusterTrustBundles, including Kubelet, are free to reorder and deduplicate certificate blocks in this file according to their own logic, as well as to drop PEM block headers and inter-block data.
+
+- **signerName** (string)
+
+  signerName indicates the associated signer, if any.
+  
+  In order to create or update a ClusterTrustBundle that sets signerName, you must have the following cluster-scoped permission: group=certificates.k8s.io resource=signers resourceName=\<the signer name> verb=attest.
+  
+  If signerName is not empty, then the ClusterTrustBundle object must be named with the signer name as a prefix (translating slashes to colons). For example, for the signer name `example.com/foo`, valid ClusterTrustBundle object names include `example.com:foo:abc` and `example.com:foo:v1`.
+  
+  If signerName is empty, then the ClusterTrustBundle object's name must not have such a prefix.
+  
+  List/watch requests for ClusterTrustBundles can filter on this field using a `spec.signerName=NAME` field selector.
+
+
+
+
+
+## ClusterTrustBundleList {#ClusterTrustBundleList}
+
+ClusterTrustBundleList is a collection of ClusterTrustBundle objects
+
+<hr>
+
+- **apiVersion**: certificates.k8s.io/v1alpha1
+
+
+- **kind**: ClusterTrustBundleList
+
+
+- **metadata** (<a href="{{< ref "../common-definitions/list-meta#ListMeta" >}}">ListMeta</a>)
+
+  metadata contains the list metadata.
+
+- **items** ([]<a href="{{< ref "../authentication-resources/cluster-trust-bundle-v1alpha1#ClusterTrustBundle" >}}">ClusterTrustBundle</a>), required
+
+  items is a collection of ClusterTrustBundle objects
+
+
+
+
+
+## Operations {#Operations}
+
+
+
+<hr>
+
+
+
+
+
+
+### `get` read the specified ClusterTrustBundle
+
+#### HTTP Request
+
+GET /apis/certificates.k8s.io/v1alpha1/clustertrustbundles/{name}
+
+#### Parameters
+
+
+- **name** (*in path*): string, required
+
+  name of the ClusterTrustBundle
+
+
+- **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
+
+
+#### Response
+
+
+200 (<a href="{{< ref "../authentication-resources/cluster-trust-bundle-v1alpha1#ClusterTrustBundle" >}}">ClusterTrustBundle</a>): OK
+
+401: Unauthorized
+
+
+### `list` list or watch objects of kind ClusterTrustBundle
+
+#### HTTP Request
+
+GET /apis/certificates.k8s.io/v1alpha1/clustertrustbundles
+
+#### Parameters
+
+
+- **allowWatchBookmarks** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#allowWatchBookmarks" >}}">allowWatchBookmarks</a>
+
+
+- **continue** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#continue" >}}">continue</a>
+
+
+- **fieldSelector** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldSelector" >}}">fieldSelector</a>
+
+
+- **labelSelector** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#labelSelector" >}}">labelSelector</a>
+
+
+- **limit** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#limit" >}}">limit</a>
+
+
+- **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
+
+- **resourceVersion** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#resourceVersion" >}}">resourceVersion</a>
+
+
+- **resourceVersionMatch** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
+
+
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
+- **timeoutSeconds** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
+
+
+- **watch** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#watch" >}}">watch</a>
+
+
+
+#### Response
+
+
+200 (<a href="{{< ref "../authentication-resources/cluster-trust-bundle-v1alpha1#ClusterTrustBundleList" >}}">ClusterTrustBundleList</a>): OK
+
+401: Unauthorized
+
+
+### `create` create a ClusterTrustBundle
+
+#### HTTP Request
+
+POST /apis/certificates.k8s.io/v1alpha1/clustertrustbundles
+
+#### Parameters
+
+
+- **body**: <a href="{{< ref "../authentication-resources/cluster-trust-bundle-v1alpha1#ClusterTrustBundle" >}}">ClusterTrustBundle</a>, required
+
+  
+
+
+- **dryRun** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
+
+
+- **fieldManager** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
+
+
+- **fieldValidation** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
+
+
+- **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
+
+
+#### Response
+
+
+200 (<a href="{{< ref "../authentication-resources/cluster-trust-bundle-v1alpha1#ClusterTrustBundle" >}}">ClusterTrustBundle</a>): OK
+
+201 (<a href="{{< ref "../authentication-resources/cluster-trust-bundle-v1alpha1#ClusterTrustBundle" >}}">ClusterTrustBundle</a>): Created
+
+202 (<a href="{{< ref "../authentication-resources/cluster-trust-bundle-v1alpha1#ClusterTrustBundle" >}}">ClusterTrustBundle</a>): Accepted
+
+401: Unauthorized
+
+
+### `update` replace the specified ClusterTrustBundle
+
+#### HTTP Request
+
+PUT /apis/certificates.k8s.io/v1alpha1/clustertrustbundles/{name}
+
+#### Parameters
+
+
+- **name** (*in path*): string, required
+
+  name of the ClusterTrustBundle
+
+
+- **body**: <a href="{{< ref "../authentication-resources/cluster-trust-bundle-v1alpha1#ClusterTrustBundle" >}}">ClusterTrustBundle</a>, required
+
+  
+
+
+- **dryRun** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
+
+
+- **fieldManager** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
+
+
+- **fieldValidation** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
+
+
+- **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
+
+
+#### Response
+
+
+200 (<a href="{{< ref "../authentication-resources/cluster-trust-bundle-v1alpha1#ClusterTrustBundle" >}}">ClusterTrustBundle</a>): OK
+
+201 (<a href="{{< ref "../authentication-resources/cluster-trust-bundle-v1alpha1#ClusterTrustBundle" >}}">ClusterTrustBundle</a>): Created
+
+401: Unauthorized
+
+
+### `patch` partially update the specified ClusterTrustBundle
+
+#### HTTP Request
+
+PATCH /apis/certificates.k8s.io/v1alpha1/clustertrustbundles/{name}
+
+#### Parameters
+
+
+- **name** (*in path*): string, required
+
+  name of the ClusterTrustBundle
+
+
+- **body**: <a href="{{< ref "../common-definitions/patch#Patch" >}}">Patch</a>, required
+
+  
+
+
+- **dryRun** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
+
+
+- **fieldManager** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
+
+
+- **fieldValidation** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
+
+
+- **force** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#force" >}}">force</a>
+
+
+- **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
+
+
+#### Response
+
+
+200 (<a href="{{< ref "../authentication-resources/cluster-trust-bundle-v1alpha1#ClusterTrustBundle" >}}">ClusterTrustBundle</a>): OK
+
+201 (<a href="{{< ref "../authentication-resources/cluster-trust-bundle-v1alpha1#ClusterTrustBundle" >}}">ClusterTrustBundle</a>): Created
+
+401: Unauthorized
+
+
+### `delete` delete a ClusterTrustBundle
+
+#### HTTP Request
+
+DELETE /apis/certificates.k8s.io/v1alpha1/clustertrustbundles/{name}
+
+#### Parameters
+
+
+- **name** (*in path*): string, required
+
+  name of the ClusterTrustBundle
+
+
+- **body**: <a href="{{< ref "../common-definitions/delete-options#DeleteOptions" >}}">DeleteOptions</a>
+
+  
+
+
+- **dryRun** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
+
+
+- **gracePeriodSeconds** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#gracePeriodSeconds" >}}">gracePeriodSeconds</a>
+
+
+- **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
+
+- **propagationPolicy** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#propagationPolicy" >}}">propagationPolicy</a>
+
+
+
+#### Response
+
+
+200 (<a href="{{< ref "../common-definitions/status#Status" >}}">Status</a>): OK
+
+202 (<a href="{{< ref "../common-definitions/status#Status" >}}">Status</a>): Accepted
+
+401: Unauthorized
+
+
+### `deletecollection` delete collection of ClusterTrustBundle
+
+#### HTTP Request
+
+DELETE /apis/certificates.k8s.io/v1alpha1/clustertrustbundles
+
+#### Parameters
+
+
+- **body**: <a href="{{< ref "../common-definitions/delete-options#DeleteOptions" >}}">DeleteOptions</a>
+
+  
+
+
+- **continue** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#continue" >}}">continue</a>
+
+
+- **dryRun** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
+
+
+- **fieldSelector** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldSelector" >}}">fieldSelector</a>
+
+
+- **gracePeriodSeconds** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#gracePeriodSeconds" >}}">gracePeriodSeconds</a>
+
+
+- **labelSelector** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#labelSelector" >}}">labelSelector</a>
+
+
+- **limit** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#limit" >}}">limit</a>
+
+
+- **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
+
+- **propagationPolicy** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#propagationPolicy" >}}">propagationPolicy</a>
+
+
+- **resourceVersion** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#resourceVersion" >}}">resourceVersion</a>
+
+
+- **resourceVersionMatch** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
+
+
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
+- **timeoutSeconds** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
+
+
+
+#### Response
+
+
+200 (<a href="{{< ref "../common-definitions/status#Status" >}}">Status</a>): OK
+
+401: Unauthorized
+
diff --git a/content/en/docs/reference/kubernetes-api/authentication-resources/self-subject-review-v1beta1.md b/content/en/docs/reference/kubernetes-api/authentication-resources/self-subject-review-v1beta1.md
new file mode 100644
index 00000000000..064d3f8f027
--- /dev/null
+++ b/content/en/docs/reference/kubernetes-api/authentication-resources/self-subject-review-v1beta1.md
@@ -0,0 +1,142 @@
+---
+api_metadata:
+  apiVersion: "authentication.k8s.io/v1beta1"
+  import: "k8s.io/api/authentication/v1beta1"
+  kind: "SelfSubjectReview"
+content_type: "api_reference"
+description: "SelfSubjectReview contains the user information that the kube-apiserver has about the user making this request."
+title: "SelfSubjectReview v1beta1"
+weight: 6
+auto_generated: true
+---
+
+<!--
+The file is auto-generated from the Go source code of the component using a generic
+[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
+to generate the reference documentation, please read
+[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
+To update the reference content, please follow the 
+[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
+guide. You can file document formatting bugs against the
+[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
+-->
+
+`apiVersion: authentication.k8s.io/v1beta1`
+
+`import "k8s.io/api/authentication/v1beta1"`
+
+
+## SelfSubjectReview {#SelfSubjectReview}
+
+SelfSubjectReview contains the user information that the kube-apiserver has about the user making this request. When using impersonation, users will receive the user info of the user being impersonated.  If impersonation or request header authentication is used, any extra keys will have their case ignored and returned as lowercase.
+
+<hr>
+
+- **apiVersion**: authentication.k8s.io/v1beta1
+
+
+- **kind**: SelfSubjectReview
+
+
+- **metadata** (<a href="{{< ref "../common-definitions/object-meta#ObjectMeta" >}}">ObjectMeta</a>)
+
+  Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
+
+- **status** (<a href="{{< ref "../authentication-resources/self-subject-review-v1beta1#SelfSubjectReviewStatus" >}}">SelfSubjectReviewStatus</a>)
+
+  Status is filled in by the server with the user attributes.
+
+
+
+
+
+## SelfSubjectReviewStatus {#SelfSubjectReviewStatus}
+
+SelfSubjectReviewStatus is filled by the kube-apiserver and sent back to a user.
+
+<hr>
+
+- **userInfo** (UserInfo)
+
+  User attributes of the user making this request.
+
+  <a name="UserInfo"></a>
+  *UserInfo holds the information about the user needed to implement the user.Info interface.*
+
+  - **userInfo.extra** (map[string][]string)
+
+    Any additional information provided by the authenticator.
+
+  - **userInfo.groups** ([]string)
+
+    The names of groups this user is a part of.
+
+  - **userInfo.uid** (string)
+
+    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.
+
+  - **userInfo.username** (string)
+
+    The name that uniquely identifies this user among all active users.
+
+
+
+
+
+## Operations {#Operations}
+
+
+
+<hr>
+
+
+
+
+
+
+### `create` create a SelfSubjectReview
+
+#### HTTP Request
+
+POST /apis/authentication.k8s.io/v1beta1/selfsubjectreviews
+
+#### Parameters
+
+
+- **body**: <a href="{{< ref "../authentication-resources/self-subject-review-v1beta1#SelfSubjectReview" >}}">SelfSubjectReview</a>, required
+
+  
+
+
+- **dryRun** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
+
+
+- **fieldManager** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
+
+
+- **fieldValidation** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
+
+
+- **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
+
+
+#### Response
+
+
+200 (<a href="{{< ref "../authentication-resources/self-subject-review-v1beta1#SelfSubjectReview" >}}">SelfSubjectReview</a>): OK
+
+201 (<a href="{{< ref "../authentication-resources/self-subject-review-v1beta1#SelfSubjectReview" >}}">SelfSubjectReview</a>): Created
+
+202 (<a href="{{< ref "../authentication-resources/self-subject-review-v1beta1#SelfSubjectReview" >}}">SelfSubjectReview</a>): Accepted
+
+401: Unauthorized
+
diff --git a/content/en/docs/reference/kubernetes-api/authentication-resources/service-account-v1.md b/content/en/docs/reference/kubernetes-api/authentication-resources/service-account-v1.md
index f68e674c67e..589f0b923c7 100644
--- a/content/en/docs/reference/kubernetes-api/authentication-resources/service-account-v1.md
+++ b/content/en/docs/reference/kubernetes-api/authentication-resources/service-account-v1.md
@@ -182,6 +182,11 @@ GET /api/v1/namespaces/{namespace}/serviceaccounts
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -250,6 +255,11 @@ GET /api/v1/serviceaccounts
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -560,6 +570,11 @@ DELETE /api/v1/namespaces/{namespace}/serviceaccounts
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/authorization-resources/cluster-role-binding-v1.md b/content/en/docs/reference/kubernetes-api/authorization-resources/cluster-role-binding-v1.md
index a99b970be9b..f84ba0fcf6c 100644
--- a/content/en/docs/reference/kubernetes-api/authorization-resources/cluster-role-binding-v1.md
+++ b/content/en/docs/reference/kubernetes-api/authorization-resources/cluster-role-binding-v1.md
@@ -200,6 +200,11 @@ GET /apis/rbac.authorization.k8s.io/v1/clusterrolebindings
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -485,6 +490,11 @@ DELETE /apis/rbac.authorization.k8s.io/v1/clusterrolebindings
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/authorization-resources/cluster-role-v1.md b/content/en/docs/reference/kubernetes-api/authorization-resources/cluster-role-v1.md
index 387737af3b5..b7e87bf0cca 100644
--- a/content/en/docs/reference/kubernetes-api/authorization-resources/cluster-role-v1.md
+++ b/content/en/docs/reference/kubernetes-api/authorization-resources/cluster-role-v1.md
@@ -196,6 +196,11 @@ GET /apis/rbac.authorization.k8s.io/v1/clusterroles
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -481,6 +486,11 @@ DELETE /apis/rbac.authorization.k8s.io/v1/clusterroles
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/authorization-resources/role-binding-v1.md b/content/en/docs/reference/kubernetes-api/authorization-resources/role-binding-v1.md
index 6f2ad19fa6c..75d4d5f0f84 100644
--- a/content/en/docs/reference/kubernetes-api/authorization-resources/role-binding-v1.md
+++ b/content/en/docs/reference/kubernetes-api/authorization-resources/role-binding-v1.md
@@ -210,6 +210,11 @@ GET /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -278,6 +283,11 @@ GET /apis/rbac.authorization.k8s.io/v1/rolebindings
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -588,6 +598,11 @@ DELETE /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/authorization-resources/role-v1.md b/content/en/docs/reference/kubernetes-api/authorization-resources/role-v1.md
index ab854e246a8..6b378be7caf 100644
--- a/content/en/docs/reference/kubernetes-api/authorization-resources/role-v1.md
+++ b/content/en/docs/reference/kubernetes-api/authorization-resources/role-v1.md
@@ -195,6 +195,11 @@ GET /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -263,6 +268,11 @@ GET /apis/rbac.authorization.k8s.io/v1/roles
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -573,6 +583,11 @@ DELETE /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/authorization-resources/self-subject-review-v1alpha1.md b/content/en/docs/reference/kubernetes-api/authorization-resources/self-subject-review-v1alpha1.md
index ace01dcaf55..a8ed8464f21 100644
--- a/content/en/docs/reference/kubernetes-api/authorization-resources/self-subject-review-v1alpha1.md
+++ b/content/en/docs/reference/kubernetes-api/authorization-resources/self-subject-review-v1alpha1.md
@@ -28,7 +28,7 @@ guide. You can file document formatting bugs against the
 
 ## SelfSubjectReview {#SelfSubjectReview}
 
-SelfSubjectReview contains the user information that the kube-apiserver has about the user making this request. When using impersonation, users will receive the user info of the user being impersonated.
+SelfSubjectReview contains the user information that the kube-apiserver has about the user making this request. When using impersonation, users will receive the user info of the user being impersonated.  If impersonation or request header authentication is used, any extra keys will have their case ignored and returned as lowercase.
 
 <hr>
 
diff --git a/content/en/docs/reference/kubernetes-api/cluster-resources/api-service-v1.md b/content/en/docs/reference/kubernetes-api/cluster-resources/api-service-v1.md
index 81a7620d084..59df5a5e0e6 100644
--- a/content/en/docs/reference/kubernetes-api/cluster-resources/api-service-v1.md
+++ b/content/en/docs/reference/kubernetes-api/cluster-resources/api-service-v1.md
@@ -293,6 +293,11 @@ GET /apis/apiregistration.k8s.io/v1/apiservices
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -683,6 +688,11 @@ DELETE /apis/apiregistration.k8s.io/v1/apiservices
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/cluster-resources/cluster-cidr-v1alpha1.md b/content/en/docs/reference/kubernetes-api/cluster-resources/cluster-cidr-v1alpha1.md
index 82f8eb92288..4fdf307e974 100644
--- a/content/en/docs/reference/kubernetes-api/cluster-resources/cluster-cidr-v1alpha1.md
+++ b/content/en/docs/reference/kubernetes-api/cluster-resources/cluster-cidr-v1alpha1.md
@@ -44,7 +44,7 @@ ClusterCIDR represents a single configuration for per-Node Pod CIDR allocations
 
 - **spec** (<a href="{{< ref "../cluster-resources/cluster-cidr-v1alpha1#ClusterCIDRSpec" >}}">ClusterCIDRSpec</a>)
 
-  Spec is the desired state of the ClusterCIDR. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
+  spec is the desired state of the ClusterCIDR. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
 
 
 
@@ -58,19 +58,19 @@ ClusterCIDRSpec defines the desired state of ClusterCIDR.
 
 - **perNodeHostBits** (int32), required
 
-  PerNodeHostBits defines the number of host bits to be configured per node. A subnet mask determines how much of the address is used for network bits and host bits. For example an IPv4 address of 192.168.0.0/24, splits the address into 24 bits for the network portion and 8 bits for the host portion. To allocate 256 IPs, set this field to 8 (a /24 mask for IPv4 or a /120 for IPv6). Minimum value is 4 (16 IPs). This field is immutable.
+  perNodeHostBits defines the number of host bits to be configured per node. A subnet mask determines how much of the address is used for network bits and host bits. For example an IPv4 address of 192.168.0.0/24, splits the address into 24 bits for the network portion and 8 bits for the host portion. To allocate 256 IPs, set this field to 8 (a /24 mask for IPv4 or a /120 for IPv6). Minimum value is 4 (16 IPs). This field is immutable.
 
 - **ipv4** (string)
 
-  IPv4 defines an IPv4 IP block in CIDR notation(e.g. "10.0.0.0/8"). At least one of IPv4 and IPv6 must be specified. This field is immutable.
+  ipv4 defines an IPv4 IP block in CIDR notation(e.g. "10.0.0.0/8"). At least one of ipv4 and ipv6 must be specified. This field is immutable.
 
 - **ipv6** (string)
 
-  IPv6 defines an IPv6 IP block in CIDR notation(e.g. "2001:db8::/64"). At least one of IPv4 and IPv6 must be specified. This field is immutable.
+  ipv6 defines an IPv6 IP block in CIDR notation(e.g. "2001:db8::/64"). At least one of ipv4 and ipv6 must be specified. This field is immutable.
 
 - **nodeSelector** (NodeSelector)
 
-  NodeSelector defines which nodes the config is applicable to. An empty or nil NodeSelector selects all nodes. This field is immutable.
+  nodeSelector defines which nodes the config is applicable to. An empty or nil nodeSelector selects all nodes. This field is immutable.
 
   <a name="NodeSelector"></a>
   *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.*
@@ -112,7 +112,7 @@ ClusterCIDRList contains a list of ClusterCIDR.
 
 - **items** ([]<a href="{{< ref "../cluster-resources/cluster-cidr-v1alpha1#ClusterCIDR" >}}">ClusterCIDR</a>), required
 
-  Items is the list of ClusterCIDRs.
+  items is the list of ClusterCIDRs.
 
 
 
@@ -206,6 +206,11 @@ GET /apis/networking.k8s.io/v1alpha1/clustercidrs
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -491,6 +496,11 @@ DELETE /apis/networking.k8s.io/v1alpha1/clustercidrs
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/cluster-resources/component-status-v1.md b/content/en/docs/reference/kubernetes-api/cluster-resources/component-status-v1.md
index 0542fedfbd7..f1bcf3b0654 100644
--- a/content/en/docs/reference/kubernetes-api/cluster-resources/component-status-v1.md
+++ b/content/en/docs/reference/kubernetes-api/cluster-resources/component-status-v1.md
@@ -183,6 +183,11 @@ GET /api/v1/componentstatuses
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/cluster-resources/event-v1.md b/content/en/docs/reference/kubernetes-api/cluster-resources/event-v1.md
index 20ed36b1abd..fcdec600ee7 100644
--- a/content/en/docs/reference/kubernetes-api/cluster-resources/event-v1.md
+++ b/content/en/docs/reference/kubernetes-api/cluster-resources/event-v1.md
@@ -258,6 +258,11 @@ GET /apis/events.k8s.io/v1/namespaces/{namespace}/events
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -326,6 +331,11 @@ GET /apis/events.k8s.io/v1/events
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -636,6 +646,11 @@ DELETE /apis/events.k8s.io/v1/namespaces/{namespace}/events
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/cluster-resources/flow-schema-v1beta3.md b/content/en/docs/reference/kubernetes-api/cluster-resources/flow-schema-v1beta3.md
index e325b3d7777..94957e33ba2 100644
--- a/content/en/docs/reference/kubernetes-api/cluster-resources/flow-schema-v1beta3.md
+++ b/content/en/docs/reference/kubernetes-api/cluster-resources/flow-schema-v1beta3.md
@@ -397,6 +397,11 @@ GET /apis/flowcontrol.apiserver.k8s.io/v1beta3/flowschemas
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -787,6 +792,11 @@ DELETE /apis/flowcontrol.apiserver.k8s.io/v1beta3/flowschemas
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/cluster-resources/lease-v1.md b/content/en/docs/reference/kubernetes-api/cluster-resources/lease-v1.md
index b33e8ee19a7..c88ee6d7e4d 100644
--- a/content/en/docs/reference/kubernetes-api/cluster-resources/lease-v1.md
+++ b/content/en/docs/reference/kubernetes-api/cluster-resources/lease-v1.md
@@ -44,7 +44,7 @@ Lease defines a lease concept.
 
 - **spec** (<a href="{{< ref "../cluster-resources/lease-v1#LeaseSpec" >}}">LeaseSpec</a>)
 
-  Specification of the Lease. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
+  spec contains the specification of the Lease. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
 
 
 
@@ -69,7 +69,7 @@ LeaseSpec is a specification of a Lease.
 
 - **leaseDurationSeconds** (int32)
 
-  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.
+  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.
 
 - **leaseTransitions** (int32)
 
@@ -104,7 +104,7 @@ LeaseList is a list of Lease objects.
 
 - **items** ([]<a href="{{< ref "../cluster-resources/lease-v1#Lease" >}}">Lease</a>), required
 
-  Items is a list of schema objects.
+  items is a list of schema objects.
 
 
 
@@ -208,6 +208,11 @@ GET /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -276,6 +281,11 @@ GET /apis/coordination.k8s.io/v1/leases
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -586,6 +596,11 @@ DELETE /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/cluster-resources/namespace-v1.md b/content/en/docs/reference/kubernetes-api/cluster-resources/namespace-v1.md
index 0871c397d3a..6388d7126e4 100644
--- a/content/en/docs/reference/kubernetes-api/cluster-resources/namespace-v1.md
+++ b/content/en/docs/reference/kubernetes-api/cluster-resources/namespace-v1.md
@@ -106,8 +106,6 @@ NamespaceStatus is information about the current status of a Namespace.
 - **phase** (string)
 
   Phase is the current lifecycle phase of the namespace. More info: https://kubernetes.io/docs/tasks/administer-cluster/namespaces/
-  
-  
 
 
 
@@ -253,6 +251,11 @@ GET /api/v1/namespaces
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/cluster-resources/node-v1.md b/content/en/docs/reference/kubernetes-api/cluster-resources/node-v1.md
index a6317d1dc98..0a73ea2cb2d 100644
--- a/content/en/docs/reference/kubernetes-api/cluster-resources/node-v1.md
+++ b/content/en/docs/reference/kubernetes-api/cluster-resources/node-v1.md
@@ -120,8 +120,6 @@ NodeSpec describes the attributes that a node is created with.
   - **taints.effect** (string), required
 
     Required. The effect of the taint on pods that do not tolerate the taint. Valid effects are NoSchedule, PreferNoSchedule and NoExecute.
-    
-    
 
   - **taints.key** (string), required
 
@@ -156,7 +154,7 @@ NodeStatus is information about the current status of a node.
 
   *Patch strategy: merge on key `type`*
   
-  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 https://pr.k8s.io/79391 for an example.
+  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 https://pr.k8s.io/79391 for an example. Consumers should assume that addresses can change during the lifetime of a Node. However, there are some exceptions where this may not be possible, such as Pods that inherit a Node's address in its own status or consumers of the downward API (status.hostIP).
 
   <a name="NodeAddress"></a>
   *NodeAddress contains information for the node's address.*
@@ -412,8 +410,6 @@ NodeStatus is information about the current status of a node.
 - **phase** (string)
 
   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.
-  
-  
 
 - **volumesAttached** ([]AttachedVolume)
 
@@ -578,6 +574,11 @@ GET /api/v1/nodes
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -968,6 +969,11 @@ DELETE /api/v1/nodes
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/cluster-resources/priority-level-configuration-v1beta3.md b/content/en/docs/reference/kubernetes-api/cluster-resources/priority-level-configuration-v1beta3.md
index 5a17134f65d..420699dfaf0 100644
--- a/content/en/docs/reference/kubernetes-api/cluster-resources/priority-level-configuration-v1beta3.md
+++ b/content/en/docs/reference/kubernetes-api/cluster-resources/priority-level-configuration-v1beta3.md
@@ -313,6 +313,11 @@ GET /apis/flowcontrol.apiserver.k8s.io/v1beta3/prioritylevelconfigurations
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -703,6 +708,11 @@ DELETE /apis/flowcontrol.apiserver.k8s.io/v1beta3/prioritylevelconfigurations
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/cluster-resources/runtime-class-v1.md b/content/en/docs/reference/kubernetes-api/cluster-resources/runtime-class-v1.md
index 4f8bb7571de..0fade3be57e 100644
--- a/content/en/docs/reference/kubernetes-api/cluster-resources/runtime-class-v1.md
+++ b/content/en/docs/reference/kubernetes-api/cluster-resources/runtime-class-v1.md
@@ -44,11 +44,11 @@ RuntimeClass defines a class of container runtime supported in the cluster. The
 
 - **handler** (string), required
 
-  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 & 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 "runc" 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.
+  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 & 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 "runc" 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.
 
 - **overhead** (Overhead)
 
-  Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, see
+  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/
 
   <a name="Overhead"></a>
@@ -56,11 +56,11 @@ RuntimeClass defines a class of container runtime supported in the cluster. The
 
   - **overhead.podFixed** (map[string]<a href="{{< ref "../common-definitions/quantity#Quantity" >}}">Quantity</a>)
 
-    PodFixed represents the fixed resource overhead associated with running a pod.
+    podFixed represents the fixed resource overhead associated with running a pod.
 
 - **scheduling** (Scheduling)
 
-  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.
+  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.
 
   <a name="Scheduling"></a>
   *Scheduling specifies the scheduling constraints for nodes supporting a RuntimeClass.*
@@ -85,8 +85,6 @@ RuntimeClass defines a class of container runtime supported in the cluster. The
     - **scheduling.tolerations.operator** (string)
 
       Operator represents a key'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.
-      
-      
 
     - **scheduling.tolerations.value** (string)
 
@@ -95,8 +93,6 @@ RuntimeClass defines a class of container runtime supported in the cluster. The
     - **scheduling.tolerations.effect** (string)
 
       Effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.
-      
-      
 
     - **scheduling.tolerations.tolerationSeconds** (int64)
 
@@ -124,7 +120,7 @@ RuntimeClassList is a list of RuntimeClass objects.
 
 - **items** ([]<a href="{{< ref "../cluster-resources/runtime-class-v1#RuntimeClass" >}}">RuntimeClass</a>), required
 
-  Items is a list of schema objects.
+  items is a list of schema objects.
 
 
 
@@ -218,6 +214,11 @@ GET /apis/node.k8s.io/v1/runtimeclasses
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -503,6 +504,11 @@ DELETE /apis/node.k8s.io/v1/runtimeclasses
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/common-definitions/node-selector-requirement.md b/content/en/docs/reference/kubernetes-api/common-definitions/node-selector-requirement.md
index 4cbdb7881d8..33af2e88e30 100644
--- a/content/en/docs/reference/kubernetes-api/common-definitions/node-selector-requirement.md
+++ b/content/en/docs/reference/kubernetes-api/common-definitions/node-selector-requirement.md
@@ -36,9 +36,7 @@ A node selector requirement is a selector that contains values, a key, and an op
 
 - **operator** (string), required
 
-  Represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist, Gt, and Lt.
-  
-  
+  Represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist. Gt, and Lt.
 
 - **values** ([]string)
 
diff --git a/content/en/docs/reference/kubernetes-api/common-definitions/object-meta.md b/content/en/docs/reference/kubernetes-api/common-definitions/object-meta.md
index 199d4ff7d70..9386baeb83e 100644
--- a/content/en/docs/reference/kubernetes-api/common-definitions/object-meta.md
+++ b/content/en/docs/reference/kubernetes-api/common-definitions/object-meta.md
@@ -32,7 +32,7 @@ ObjectMeta is metadata that all persisted resources must have, which includes al
 
 - **name** (string)
 
-  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
+  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: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#names
 
 - **generateName** (string)
 
@@ -46,15 +46,15 @@ ObjectMeta is metadata that all persisted resources must have, which includes al
 
   Namespace defines the space within which each name must be unique. An empty namespace is equivalent to the "default" namespace, but "default" 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
+  Must be a DNS_LABEL. Cannot be updated. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces
 
 - **labels** (map[string]string)
 
-  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
+  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: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels
 
 - **annotations** (map[string]string)
 
-  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
+  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: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations
 
 
 
@@ -129,11 +129,11 @@ ObjectMeta is metadata that all persisted resources must have, which includes al
 
   - **ownerReferences.name** (string), required
 
-    Name of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#names
+    Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#names
 
   - **ownerReferences.uid** (string), required
 
-    UID of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#uids
+    UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#uids
 
   - **ownerReferences.blockOwnerDeletion** (boolean)
 
@@ -186,7 +186,7 @@ ObjectMeta is metadata that all persisted resources must have, which includes al
 
   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
+  Populated by the system. Read-only. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#uids
 
 
 
diff --git a/content/en/docs/reference/kubernetes-api/common-definitions/status.md b/content/en/docs/reference/kubernetes-api/common-definitions/status.md
index d40a22d6dae..9688eebe5ff 100644
--- a/content/en/docs/reference/kubernetes-api/common-definitions/status.md
+++ b/content/en/docs/reference/kubernetes-api/common-definitions/status.md
@@ -86,7 +86,7 @@ Status is a return value for calls that don't return other objects.
 
   - **details.uid** (string)
 
-    UID of the resource. (when there is a single resource which can be described). More info: http://kubernetes.io/docs/user-guide/identifiers#uids
+    UID of the resource. (when there is a single resource which can be described). More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#uids
 
 - **kind** (string)
 
diff --git a/content/en/docs/reference/kubernetes-api/common-parameters/common-parameters.md b/content/en/docs/reference/kubernetes-api/common-parameters/common-parameters.md
index 1b290a716b7..95a8f5dd37c 100644
--- a/content/en/docs/reference/kubernetes-api/common-parameters/common-parameters.md
+++ b/content/en/docs/reference/kubernetes-api/common-parameters/common-parameters.md
@@ -80,7 +80,7 @@ A selector to restrict the list of returned objects by their fields. Defaults to
 
 ## fieldValidation {#fieldValidation}
 
-fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
+fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
 
 <hr>
 
@@ -184,6 +184,28 @@ Defaults to unset
 
 
 
+## sendInitialEvents {#sendInitialEvents}
+
+`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.
+
+When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan
+  is interpreted as "data at least as new as the provided `resourceVersion`"
+  and the bookmark event is send when the state is synced
+  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.
+  If `resourceVersion` is unset, this is interpreted as "consistent read" and the
+  bookmark event is send when the state is synced at least to the moment
+  when request started being processed.
+- `resourceVersionMatch` set to any other value or unset
+  Invalid error is returned.
+
+Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.
+
+<hr>
+
+
+
+
+
 ## timeoutSeconds {#timeoutSeconds}
 
 Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
diff --git a/content/en/docs/reference/kubernetes-api/config-and-storage-resources/config-map-v1.md b/content/en/docs/reference/kubernetes-api/config-and-storage-resources/config-map-v1.md
index c0619358ab2..78318e2a089 100644
--- a/content/en/docs/reference/kubernetes-api/config-and-storage-resources/config-map-v1.md
+++ b/content/en/docs/reference/kubernetes-api/config-and-storage-resources/config-map-v1.md
@@ -180,6 +180,11 @@ GET /api/v1/namespaces/{namespace}/configmaps
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -248,6 +253,11 @@ GET /api/v1/configmaps
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -558,6 +568,11 @@ DELETE /api/v1/namespaces/{namespace}/configmaps
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/config-and-storage-resources/csi-driver-v1.md b/content/en/docs/reference/kubernetes-api/config-and-storage-resources/csi-driver-v1.md
index 911ef8e77e5..8f331c62bd0 100644
--- a/content/en/docs/reference/kubernetes-api/config-and-storage-resources/csi-driver-v1.md
+++ b/content/en/docs/reference/kubernetes-api/config-and-storage-resources/csi-driver-v1.md
@@ -44,7 +44,7 @@ CSIDriver captures information about a Container Storage Interface (CSI) volume
 
 - **spec** (<a href="{{< ref "../config-and-storage-resources/csi-driver-v1#CSIDriverSpec" >}}">CSIDriverSpec</a>), required
 
-  Specification of the CSI Driver.
+  spec represents the specification of the CSI Driver.
 
 
 
@@ -64,7 +64,7 @@ CSIDriverSpec is the specification of a CSIDriver.
 
 - **fsGroupPolicy** (string)
 
-  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.
+  fsGroupPolicy 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.
   
@@ -72,7 +72,11 @@ CSIDriverSpec is the specification of a CSIDriver.
 
 - **podInfoOnMount** (boolean)
 
-  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. "csi.storage.k8s.io/pod.name": pod.Name "csi.storage.k8s.io/pod.namespace": pod.Namespace "csi.storage.k8s.io/pod.uid": string(pod.UID) "csi.storage.k8s.io/ephemeral": "true" if the volume is an ephemeral inline volume
+  podInfoOnMount indicates this CSI volume driver requires additional pod information (like podName, podUID, etc.) during mount operations, if set to true. 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. "csi.storage.k8s.io/pod.name": pod.Name "csi.storage.k8s.io/pod.namespace": pod.Namespace "csi.storage.k8s.io/pod.uid": string(pod.UID) "csi.storage.k8s.io/ephemeral": "true" if the volume is an ephemeral inline volume
                                   defined by a CSIVolumeSource, otherwise "false"
   
   "csi.storage.k8s.io/ephemeral" is a new feature in Kubernetes 1.16. It is only required for drivers which support both the "Persistent" and "Ephemeral" VolumeLifecycleMode. Other drivers can leave pod info disabled and/or ignore this field. As Kubernetes 1.15 doesn'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.
@@ -81,13 +85,13 @@ CSIDriverSpec is the specification of a CSIDriver.
 
 - **requiresRepublish** (boolean)
 
-  RequiresRepublish indicates the CSI driver wants `NodePublishVolume` being periodically called to reflect any possible change in the mounted volume. This field defaults to false.
+  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.
 
 - **seLinuxMount** (boolean)
 
-  SELinuxMount specifies if the CSI driver supports "-o context" mount option.
+  seLinuxMount specifies if the CSI driver supports "-o context" mount option.
   
   When "true", the CSI driver must ensure that all volumes provided by this CSI driver can be mounted separately with different `-o context` options. This is typical for storage backends that provide volumes as filesystems on block devices or as independent shared volumes. Kubernetes will call NodeStage / NodePublish with "-o context=xyz" mount option when mounting a ReadWriteOncePod volume used in Pod that has explicitly set SELinux context. In the future, it may be expanded to other volume AccessModes. In any case, Kubernetes will ensure that the volume is mounted only with a single SELinux context.
   
@@ -97,7 +101,7 @@ CSIDriverSpec is the specification of a CSIDriver.
 
 - **storageCapacity** (boolean)
 
-  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.
+  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, if set to true.
   
   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.
   
@@ -109,7 +113,7 @@ CSIDriverSpec is the specification of a CSIDriver.
 
   *Atomic: will be replaced during a merge*
   
-  TokenRequests indicates the CSI driver needs pods' 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: "csi.storage.k8s.io/serviceAccount.tokens": {
+  tokenRequests indicates the CSI driver needs pods' 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: "csi.storage.k8s.io/serviceAccount.tokens": {
     "\<audience>": {
       "token": \<token>,
       "expirationTimestamp": \<expiration timestamp in RFC3339>,
@@ -124,19 +128,23 @@ CSIDriverSpec is the specification of a CSIDriver.
 
   - **tokenRequests.audience** (string), required
 
-    Audience is the intended audience of the token in "TokenRequestSpec". It will default to the audiences of kube apiserver.
+    audience is the intended audience of the token in "TokenRequestSpec". It will default to the audiences of kube apiserver.
 
   - **tokenRequests.expirationSeconds** (int64)
 
-    ExpirationSeconds is the duration of validity of the token in "TokenRequestSpec". It has the same default value of "ExpirationSeconds" in "TokenRequestSpec".
+    expirationSeconds is the duration of validity of the token in "TokenRequestSpec". It has the same default value of "ExpirationSeconds" in "TokenRequestSpec".
 
 - **volumeLifecycleModes** ([]string)
 
   *Set: unique values will be kept during a merge*
   
-  volumeLifecycleModes defines what kind of volumes this CSI volume driver supports. The default if the list is empty is "Persistent", which is the usage defined by the CSI specification and implemented in Kubernetes via the usual PV/PVC mechanism. The other mode is "Ephemeral". 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.
+  volumeLifecycleModes defines what kind of volumes this CSI volume driver supports. The default if the list is empty is "Persistent", which is the usage defined by the CSI specification and implemented in Kubernetes via the usual PV/PVC mechanism.
   
-  This field is immutable.
+  The other mode is "Ephemeral". 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.
 
 
 
@@ -254,6 +262,11 @@ GET /apis/storage.k8s.io/v1/csidrivers
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -539,6 +552,11 @@ DELETE /apis/storage.k8s.io/v1/csidrivers
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/config-and-storage-resources/csi-node-v1.md b/content/en/docs/reference/kubernetes-api/config-and-storage-resources/csi-node-v1.md
index cfaf156fa51..2315e13a76d 100644
--- a/content/en/docs/reference/kubernetes-api/config-and-storage-resources/csi-node-v1.md
+++ b/content/en/docs/reference/kubernetes-api/config-and-storage-resources/csi-node-v1.md
@@ -40,7 +40,7 @@ CSINode holds information about all CSI drivers installed on a node. CSI drivers
 
 - **metadata** (<a href="{{< ref "../common-definitions/object-meta#ObjectMeta" >}}">ObjectMeta</a>)
 
-  metadata.name must be the Kubernetes node name.
+  Standard object's metadata. metadata.name must be the Kubernetes node name.
 
 - **spec** (<a href="{{< ref "../config-and-storage-resources/csi-node-v1#CSINodeSpec" >}}">CSINodeSpec</a>), required
 
@@ -67,7 +67,7 @@ CSINodeSpec holds information about the specification of all CSI drivers install
 
   - **drivers.name** (string), required
 
-    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.
+    name represents 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.
 
   - **drivers.nodeID** (string), required
 
@@ -82,7 +82,7 @@ CSINodeSpec holds information about the specification of all CSI drivers install
 
     - **drivers.allocatable.count** (int32)
 
-      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.
+      count indicates the 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.
 
   - **drivers.topologyKeys** ([]string)
 
@@ -204,6 +204,11 @@ GET /apis/storage.k8s.io/v1/csinodes
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -489,6 +494,11 @@ DELETE /apis/storage.k8s.io/v1/csinodes
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/config-and-storage-resources/csi-storage-capacity-v1.md b/content/en/docs/reference/kubernetes-api/config-and-storage-resources/csi-storage-capacity-v1.md
index cf4df4befe4..a1414630a81 100644
--- a/content/en/docs/reference/kubernetes-api/config-and-storage-resources/csi-storage-capacity-v1.md
+++ b/content/en/docs/reference/kubernetes-api/config-and-storage-resources/csi-storage-capacity-v1.md
@@ -48,7 +48,7 @@ They are consumed by the kube-scheduler when a CSI driver opts into capacity-awa
 
 - **metadata** (<a href="{{< ref "../common-definitions/object-meta#ObjectMeta" >}}">ObjectMeta</a>)
 
-  Standard object'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-\<uuid>, a generated name, or a reverse-domain name which ends with the unique CSI driver name.
+  Standard object's metadata. The name has no particular meaning. It must 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-\<uuid>, a generated name, or a reverse-domain name which ends with the unique CSI driver name.
   
   Objects are namespaced.
   
@@ -56,23 +56,23 @@ They are consumed by the kube-scheduler when a CSI driver opts into capacity-awa
 
 - **storageClassName** (string), required
 
-  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.
+  storageClassName represents 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.
 
 - **capacity** (<a href="{{< ref "../common-definitions/quantity#Quantity" >}}">Quantity</a>)
 
-  Capacity is the value reported by the CSI driver in its GetCapacityResponse for a GetCapacityRequest with topology and parameters that match the previous fields.
+  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.
 
 - **maximumVolumeSize** (<a href="{{< ref "../common-definitions/quantity#Quantity" >}}">Quantity</a>)
 
-  MaximumVolumeSize is the value reported by the CSI driver in its GetCapacityResponse for a GetCapacityRequest with topology and parameters that match the previous fields.
+  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.
 
 - **nodeTopology** (<a href="{{< ref "../common-definitions/label-selector#LabelSelector" >}}">LabelSelector</a>)
 
-  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.
+  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.
 
 
 
@@ -98,7 +98,7 @@ CSIStorageCapacityList is a collection of CSIStorageCapacity objects.
 
   *Map: unique values on key name will be kept during a merge*
   
-  Items is the list of CSIStorageCapacity objects.
+  items is the list of CSIStorageCapacity objects.
 
 
 
@@ -202,6 +202,11 @@ GET /apis/storage.k8s.io/v1/namespaces/{namespace}/csistoragecapacities
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -270,6 +275,11 @@ GET /apis/storage.k8s.io/v1/csistoragecapacities
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -580,6 +590,11 @@ DELETE /apis/storage.k8s.io/v1/namespaces/{namespace}/csistoragecapacities
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/config-and-storage-resources/persistent-volume-claim-v1.md b/content/en/docs/reference/kubernetes-api/config-and-storage-resources/persistent-volume-claim-v1.md
index 3d6a889221f..4fc8f3aa65b 100644
--- a/content/en/docs/reference/kubernetes-api/config-and-storage-resources/persistent-volume-claim-v1.md
+++ b/content/en/docs/reference/kubernetes-api/config-and-storage-resources/persistent-volume-claim-v1.md
@@ -77,13 +77,13 @@ PersistentVolumeClaimSpec describes the common attributes of storage devices and
 
   - **resources.claims** ([]ResourceClaim)
 
-    *Set: unique values will be kept during a merge*
+    *Map: unique values on key name will be kept during a merge*
     
     Claims lists the names of resources, defined in spec.resourceClaims, that are used by this container.
     
     This is an alpha field and requires enabling the DynamicResourceAllocation feature gate.
     
-    This field is immutable.
+    This field is immutable. It can only be set for containers.
 
     <a name="ResourceClaim"></a>
     *ResourceClaim references one entry in PodSpec.ResourceClaims.*
@@ -98,7 +98,7 @@ PersistentVolumeClaimSpec describes the common attributes of storage devices and
 
   - **resources.requests** (map[string]<a href="{{< ref "../common-definitions/quantity#Quantity" >}}">Quantity</a>)
 
-    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/
+    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. Requests cannot exceed Limits. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
 
 - **volumeName** (string)
 
@@ -178,7 +178,7 @@ PersistentVolumeClaimStatus is the current status of a persistent volume claim.
   conditions is the current Condition of persistent volume claim. If underlying persistent volume is being resized then the Condition will be set to 'ResizeStarted'.
 
   <a name="PersistentVolumeClaimCondition"></a>
-  *PersistentVolumeClaimCondition contails details about state of pvc*
+  *PersistentVolumeClaimCondition contains details about state of pvc*
 
   - **conditions.status** (string), required
 
@@ -211,8 +211,6 @@ PersistentVolumeClaimStatus is the current status of a persistent volume claim.
 - **phase** (string)
 
   phase represents the current phase of PersistentVolumeClaim.
-  
-  
 
 - **resizeStatus** (string)
 
@@ -377,6 +375,11 @@ GET /api/v1/namespaces/{namespace}/persistentvolumeclaims
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -445,6 +448,11 @@ GET /api/v1/persistentvolumeclaims
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -870,6 +878,11 @@ DELETE /api/v1/namespaces/{namespace}/persistentvolumeclaims
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/config-and-storage-resources/persistent-volume-v1.md b/content/en/docs/reference/kubernetes-api/config-and-storage-resources/persistent-volume-v1.md
index 0aa9021a429..3c300883401 100644
--- a/content/en/docs/reference/kubernetes-api/config-and-storage-resources/persistent-volume-v1.md
+++ b/content/en/docs/reference/kubernetes-api/config-and-storage-resources/persistent-volume-v1.md
@@ -108,8 +108,6 @@ PersistentVolumeSpec is the specification of a persistent volume.
 - **persistentVolumeReclaimPolicy** (string)
 
   persistentVolumeReclaimPolicy defines 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
-  
-  
 
 - **storageClassName** (string)
 
@@ -329,7 +327,7 @@ PersistentVolumeSpec is the specification of a persistent volume.
 
   - **csi.controllerExpandSecretRef** (SecretReference)
 
-    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 beta 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.
+    controllerExpandSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI ControllerExpandVolume call. 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.
 
     <a name="SecretReference"></a>
     *SecretReference represents a Secret Reference. It has enough information to retrieve secret in any namespace*
@@ -363,7 +361,7 @@ PersistentVolumeSpec is the specification of a persistent volume.
 
   - **csi.nodeExpandSecretRef** (SecretReference)
 
-    nodeExpandSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI NodeExpandVolume call. This is an alpha field and requires enabling CSINodeExpandSecret feature gate. This field is optional, may be omitted if no secret is required. If the secret object contains more than one secret, all secrets are passed.
+    nodeExpandSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI NodeExpandVolume call. This is a beta field which is enabled default by CSINodeExpandSecret feature gate. This field is optional, may be omitted if no secret is required. If the secret object contains more than one secret, all secrets are passed.
 
     <a name="SecretReference"></a>
     *SecretReference represents a Secret Reference. It has enough information to retrieve secret in any namespace*
@@ -519,6 +517,29 @@ PersistentVolumeSpec is the specification of a persistent volume.
 
     readOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk
 
+- **glusterfs** (GlusterfsPersistentVolumeSource)
+
+  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
+
+  <a name="GlusterfsPersistentVolumeSource"></a>
+  *Represents a Glusterfs mount that lasts the lifetime of a pod. Glusterfs volumes do not support ownership management or SELinux relabeling.*
+
+  - **glusterfs.endpoints** (string), required
+
+    endpoints is the endpoint name that details Glusterfs topology. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod
+
+  - **glusterfs.path** (string), required
+
+    path is the Glusterfs volume path. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod
+
+  - **glusterfs.endpointsNamespace** (string)
+
+    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
+
+  - **glusterfs.readOnly** (boolean)
+
+    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
+
 - **iscsi** (ISCSIPersistentVolumeSource)
 
   iscsi represents an ISCSI Disk resource that is attached to a kubelet's host machine and then exposed to the pod. Provisioned by an admin.
@@ -838,8 +859,6 @@ PersistentVolumeStatus is the current status of a persistent volume.
 - **phase** (string)
 
   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
-  
-  
 
 - **reason** (string)
 
@@ -989,6 +1008,11 @@ GET /api/v1/persistentvolumes
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -1379,6 +1403,11 @@ DELETE /api/v1/persistentvolumes
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/config-and-storage-resources/secret-v1.md b/content/en/docs/reference/kubernetes-api/config-and-storage-resources/secret-v1.md
index 5310484d56c..3bc2a6b6505 100644
--- a/content/en/docs/reference/kubernetes-api/config-and-storage-resources/secret-v1.md
+++ b/content/en/docs/reference/kubernetes-api/config-and-storage-resources/secret-v1.md
@@ -184,6 +184,11 @@ GET /api/v1/namespaces/{namespace}/secrets
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -252,6 +257,11 @@ GET /api/v1/secrets
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -562,6 +572,11 @@ DELETE /api/v1/namespaces/{namespace}/secrets
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/config-and-storage-resources/storage-class-v1.md b/content/en/docs/reference/kubernetes-api/config-and-storage-resources/storage-class-v1.md
index 6c9126f4c6b..9998f631b34 100644
--- a/content/en/docs/reference/kubernetes-api/config-and-storage-resources/storage-class-v1.md
+++ b/content/en/docs/reference/kubernetes-api/config-and-storage-resources/storage-class-v1.md
@@ -46,17 +46,17 @@ StorageClasses are non-namespaced; the name of the storage class according to et
 
 - **provisioner** (string), required
 
-  Provisioner indicates the type of the provisioner.
+  provisioner indicates the type of the provisioner.
 
 - **allowVolumeExpansion** (boolean)
 
-  AllowVolumeExpansion shows whether the storage class allow volume expand
+  allowVolumeExpansion shows whether the storage class allow volume expand.
 
 - **allowedTopologies** ([]TopologySelectorTerm)
 
   *Atomic: will be replaced during a merge*
   
-  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.
+  allowedTopologies 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.
 
   <a name="TopologySelectorTerm"></a>
   *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.*
@@ -78,19 +78,19 @@ StorageClasses are non-namespaced; the name of the storage class according to et
 
 - **mountOptions** ([]string)
 
-  Dynamically provisioned PersistentVolumes of this storage class are created with these mountOptions, e.g. ["ro", "soft"]. Not validated - mount of the PVs will simply fail if one is invalid.
+  mountOptions controls the mountOptions for dynamically provisioned PersistentVolumes of this storage class. e.g. ["ro", "soft"]. Not validated - mount of the PVs will simply fail if one is invalid.
 
 - **parameters** (map[string]string)
 
-  Parameters holds the parameters for the provisioner that should create volumes of this storage class.
+  parameters holds the parameters for the provisioner that should create volumes of this storage class.
 
 - **reclaimPolicy** (string)
 
-  Dynamically provisioned PersistentVolumes of this storage class are created with this reclaimPolicy. Defaults to Delete.
+  reclaimPolicy controls the reclaimPolicy for dynamically provisioned PersistentVolumes of this storage class. Defaults to Delete.
 
 - **volumeBindingMode** (string)
 
-  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.
+  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.
 
 
 
@@ -114,7 +114,7 @@ StorageClassList is a collection of storage classes.
 
 - **items** ([]<a href="{{< ref "../config-and-storage-resources/storage-class-v1#StorageClass" >}}">StorageClass</a>), required
 
-  Items is the list of StorageClasses
+  items is the list of StorageClasses
 
 
 
@@ -208,6 +208,11 @@ GET /apis/storage.k8s.io/v1/storageclasses
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -493,6 +498,11 @@ DELETE /apis/storage.k8s.io/v1/storageclasses
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/config-and-storage-resources/volume-attachment-v1.md b/content/en/docs/reference/kubernetes-api/config-and-storage-resources/volume-attachment-v1.md
index a0ac08f96b4..bc8d3629dcb 100644
--- a/content/en/docs/reference/kubernetes-api/config-and-storage-resources/volume-attachment-v1.md
+++ b/content/en/docs/reference/kubernetes-api/config-and-storage-resources/volume-attachment-v1.md
@@ -46,11 +46,11 @@ VolumeAttachment objects are non-namespaced.
 
 - **spec** (<a href="{{< ref "../config-and-storage-resources/volume-attachment-v1#VolumeAttachmentSpec" >}}">VolumeAttachmentSpec</a>), required
 
-  Specification of the desired attach/detach volume behavior. Populated by the Kubernetes system.
+  spec represents specification of the desired attach/detach volume behavior. Populated by the Kubernetes system.
 
 - **status** (<a href="{{< ref "../config-and-storage-resources/volume-attachment-v1#VolumeAttachmentStatus" >}}">VolumeAttachmentStatus</a>)
 
-  Status of the VolumeAttachment request. Populated by the entity completing the attach or detach operation, i.e. the external-attacher.
+  status represents status of the VolumeAttachment request. Populated by the entity completing the attach or detach operation, i.e. the external-attacher.
 
 
 
@@ -64,15 +64,15 @@ VolumeAttachmentSpec is the specification of a VolumeAttachment request.
 
 - **attacher** (string), required
 
-  Attacher indicates the name of the volume driver that MUST handle this request. This is the name returned by GetPluginName().
+  attacher indicates the name of the volume driver that MUST handle this request. This is the name returned by GetPluginName().
 
 - **nodeName** (string), required
 
-  The node that the volume should be attached to.
+  nodeName represents the node that the volume should be attached to.
 
 - **source** (VolumeAttachmentSource), required
 
-  Source represents the volume that should be attached.
+  source represents the volume that should be attached.
 
   <a name="VolumeAttachmentSource"></a>
   *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.*
@@ -83,7 +83,7 @@ VolumeAttachmentSpec is the specification of a VolumeAttachment request.
 
   - **source.persistentVolumeName** (string)
 
-    Name of the persistent volume to attach.
+    persistentVolumeName represents the name of the persistent volume to attach.
 
 
 
@@ -97,44 +97,44 @@ VolumeAttachmentStatus is the status of a VolumeAttachment request.
 
 - **attached** (boolean), required
 
-  Indicates the volume is successfully attached. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.
+  attached indicates the volume is successfully attached. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.
 
 - **attachError** (VolumeError)
 
-  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.
+  attachError represents 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.
 
   <a name="VolumeError"></a>
   *VolumeError captures an error encountered during a volume operation.*
 
   - **attachError.message** (string)
 
-    String detailing the error encountered during Attach or Detach operation. This string may be logged, so it should not contain sensitive information.
+    message represents the error encountered during Attach or Detach operation. This string may be logged, so it should not contain sensitive information.
 
   - **attachError.time** (Time)
 
-    Time the error was encountered.
+    time represents the time the error was encountered.
 
     <a name="Time"></a>
     *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.*
 
 - **attachmentMetadata** (map[string]string)
 
-  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.
+  attachmentMetadata is populated with any information returned by the attach operation, upon successful attach, 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.
 
 - **detachError** (VolumeError)
 
-  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.
+  detachError represents 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.
 
   <a name="VolumeError"></a>
   *VolumeError captures an error encountered during a volume operation.*
 
   - **detachError.message** (string)
 
-    String detailing the error encountered during Attach or Detach operation. This string may be logged, so it should not contain sensitive information.
+    message represents the error encountered during Attach or Detach operation. This string may be logged, so it should not contain sensitive information.
 
   - **detachError.time** (Time)
 
-    Time the error was encountered.
+    time represents the time the error was encountered.
 
     <a name="Time"></a>
     *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.*
@@ -161,7 +161,7 @@ VolumeAttachmentList is a collection of VolumeAttachment objects.
 
 - **items** ([]<a href="{{< ref "../config-and-storage-resources/volume-attachment-v1#VolumeAttachment" >}}">VolumeAttachment</a>), required
 
-  Items is the list of VolumeAttachments
+  items is the list of VolumeAttachments
 
 
 
@@ -283,6 +283,11 @@ GET /apis/storage.k8s.io/v1/volumeattachments
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -673,6 +678,11 @@ DELETE /apis/storage.k8s.io/v1/volumeattachments
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/config-and-storage-resources/volume.md b/content/en/docs/reference/kubernetes-api/config-and-storage-resources/volume.md
index 1586c8cdd4b..b81f55944d5 100644
--- a/content/en/docs/reference/kubernetes-api/config-and-storage-resources/volume.md
+++ b/content/en/docs/reference/kubernetes-api/config-and-storage-resources/volume.md
@@ -230,7 +230,7 @@ Volume represents a named volume in a pod that may be accessed by any container
 
   - **emptyDir.sizeLimit** (<a href="{{< ref "../common-definitions/quantity#Quantity" >}}">Quantity</a>)
 
-    sizeLimit is the 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
+    sizeLimit is the 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: https://kubernetes.io/docs/concepts/storage/volumes#emptydir
 
 - **hostPath** (HostPathVolumeSource)
 
@@ -541,6 +541,25 @@ Volume represents a named volume in a pod that may be accessed by any container
 
     readOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk
 
+- **glusterfs** (GlusterfsVolumeSource)
+
+  glusterfs represents a Glusterfs mount on the host that shares a pod's lifetime. More info: https://examples.k8s.io/volumes/glusterfs/README.md
+
+  <a name="GlusterfsVolumeSource"></a>
+  *Represents a Glusterfs mount that lasts the lifetime of a pod. Glusterfs volumes do not support ownership management or SELinux relabeling.*
+
+  - **glusterfs.endpoints** (string), required
+
+    endpoints is the endpoint name that details Glusterfs topology. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod
+
+  - **glusterfs.path** (string), required
+
+    path is the Glusterfs volume path. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod
+
+  - **glusterfs.readOnly** (boolean)
+
+    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
+
 - **iscsi** (ISCSIVolumeSource)
 
   iscsi represents an ISCSI Disk resource that is attached to a kubelet's host machine and then exposed to the pod. More info: https://examples.k8s.io/volumes/iscsi/README.md
diff --git a/content/en/docs/reference/kubernetes-api/extend-resources/custom-resource-definition-v1.md b/content/en/docs/reference/kubernetes-api/extend-resources/custom-resource-definition-v1.md
index 945538d7671..a40e0f70f07 100644
--- a/content/en/docs/reference/kubernetes-api/extend-resources/custom-resource-definition-v1.md
+++ b/content/en/docs/reference/kubernetes-api/extend-resources/custom-resource-definition-v1.md
@@ -210,12 +210,12 @@ CustomResourceDefinitionSpec describes how a user wants their resource to appear
 
   - **conversion.strategy** (string), required
 
-    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
+    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.
 
   - **conversion.webhook** (WebhookConversion)
 
-    webhook describes how to call the conversion webhook. Required when `strategy` is set to `Webhook`.
+    webhook describes how to call the conversion webhook. Required when `strategy` is set to `"Webhook"`.
 
     <a name="WebhookConversion"></a>
     *WebhookConversion describes how to call a conversion webhook*
@@ -533,6 +533,10 @@ JSONSchemaProps is a JSON-Schema following Specification Draft 4 (http://json-sc
 
     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 "failed rule: {Rule}". e.g. "must be a URL with the host matching spec.host"
 
+  - **x-kubernetes-validations.messageExpression** (string)
+
+    MessageExpression declares a CEL expression that evaluates to the validation failure message that is returned when this rule fails. Since messageExpression is used as a failure message, it must evaluate to a string. If both message and messageExpression are present on a rule, then messageExpression will be used if validation fails. If messageExpression results in a runtime error, the runtime error is logged, and the validation failure message is produced as if the messageExpression field were unset. If messageExpression evaluates to an empty string, a string with only spaces, or a string that contains line breaks, then the validation failure message will also be produced as if the messageExpression field were unset, and the fact that messageExpression produced an empty string/string with only spaces/string with line breaks will be logged. messageExpression has access to all the same variables as the rule; the only difference is the return type. Example: "x must be less than max ("+string(self.max)+")"
+
 
 
 
@@ -756,6 +760,11 @@ GET /apis/apiextensions.k8s.io/v1/customresourcedefinitions
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -1146,6 +1155,11 @@ DELETE /apis/apiextensions.k8s.io/v1/customresourcedefinitions
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/extend-resources/mutating-webhook-configuration-v1.md b/content/en/docs/reference/kubernetes-api/extend-resources/mutating-webhook-configuration-v1.md
index fba255e7f76..41cc4de3422 100644
--- a/content/en/docs/reference/kubernetes-api/extend-resources/mutating-webhook-configuration-v1.md
+++ b/content/en/docs/reference/kubernetes-api/extend-resources/mutating-webhook-configuration-v1.md
@@ -117,6 +117,44 @@ MutatingWebhookConfiguration describes the configuration of and admission webhoo
 
     FailurePolicy defines how unrecognized errors from the admission endpoint are handled - allowed values are Ignore or Fail. Defaults to Fail.
 
+  - **webhooks.matchConditions** ([]MatchCondition)
+
+    *Patch strategy: merge on key `name`*
+    
+    *Map: unique values on key name will be kept during a merge*
+    
+    MatchConditions is a list of conditions that must be met for a request to be sent to this webhook. Match conditions filter requests that have already been matched by the rules, namespaceSelector, and objectSelector. An empty list of matchConditions matches all requests. There are a maximum of 64 match conditions allowed.
+    
+    The exact matching logic is (in order):
+      1. If ANY matchCondition evaluates to FALSE, the webhook is skipped.
+      2. If ALL matchConditions evaluate to TRUE, the webhook is called.
+      3. If any matchCondition evaluates to an error (but none are FALSE):
+         - If failurePolicy=Fail, reject the request
+         - If failurePolicy=Ignore, the error is ignored and the webhook is skipped
+    
+    This is an alpha feature and managed by the AdmissionWebhookMatchConditions feature gate.
+
+    <a name="MatchCondition"></a>
+    *MatchCondition represents a condition which must by fulfilled for a request to be sent to a webhook.*
+
+    - **webhooks.matchConditions.expression** (string), required
+
+      Expression represents the expression which will be evaluated by CEL. Must evaluate to bool. CEL expressions have access to the contents of the AdmissionRequest and Authorizer, organized into CEL variables:
+      
+      'object' - The object from the incoming request. The value is null for DELETE requests. 'oldObject' - The existing object. The value is null for CREATE requests. 'request' - Attributes of the admission request(/pkg/apis/admission/types.go#AdmissionRequest). 'authorizer' - A CEL Authorizer. May be used to perform authorization checks for the principal (user or service account) of the request.
+        See https://pkg.go.dev/k8s.io/apiserver/pkg/cel/library#Authz
+      'authorizer.requestResource' - A CEL ResourceCheck constructed from the 'authorizer' and configured with the
+        request resource.
+      Documentation on CEL: https://kubernetes.io/docs/reference/using-api/cel/
+      
+      Required.
+
+    - **webhooks.matchConditions.name** (string), required
+
+      Name is an identifier for this match condition, used for strategic merging of MatchConditions, as well as providing an identifier for logging purposes. A good name should be descriptive of the associated expression. Name must be a qualified name consisting of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyName',  or 'my.name',  or '123-abc', regex used for validation is '([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]') with an optional DNS subdomain prefix and '/' (e.g. 'example.com/MyName')
+      
+      Required.
+
   - **webhooks.matchPolicy** (string)
 
     matchPolicy defines how the "rules" list is used to match incoming requests. Allowed values are "Exact" or "Equivalent".
@@ -336,6 +374,11 @@ GET /apis/admissionregistration.k8s.io/v1/mutatingwebhookconfigurations
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -621,6 +664,11 @@ DELETE /apis/admissionregistration.k8s.io/v1/mutatingwebhookconfigurations
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/extend-resources/validating-admission-policy-v1alpha1.md b/content/en/docs/reference/kubernetes-api/extend-resources/validating-admission-policy-v1alpha1.md
index 36e0feb4a6e..a6d3d72d3e4 100644
--- a/content/en/docs/reference/kubernetes-api/extend-resources/validating-admission-policy-v1alpha1.md
+++ b/content/en/docs/reference/kubernetes-api/extend-resources/validating-admission-policy-v1alpha1.md
@@ -49,50 +49,82 @@ ValidatingAdmissionPolicy describes the definition of an admission validation po
   <a name="ValidatingAdmissionPolicySpec"></a>
   *ValidatingAdmissionPolicySpec is the specification of the desired behavior of the AdmissionPolicy.*
 
-  - **spec.validations** ([]Validation), required
+  - **spec.auditAnnotations** ([]AuditAnnotation)
 
     *Atomic: will be replaced during a merge*
     
-    Validations contain CEL expressions which is used to apply the validation. A minimum of one validation is required for a policy definition. Required.
+    auditAnnotations contains CEL expressions which are used to produce audit annotations for the audit event of the API request. validations and auditAnnotations may not both be empty; a least one of validations or auditAnnotations is required.
 
-    <a name="Validation"></a>
-    *Validation specifies the CEL expression which is used to apply the validation.*
+    <a name="AuditAnnotation"></a>
+    *AuditAnnotation describes how to produce an audit annotation for an API request.*
 
-    - **spec.validations.expression** (string), required
+    - **spec.auditAnnotations.key** (string), required
 
-      Expression represents the expression which will be evaluated by CEL. ref: https://github.com/google/cel-spec CEL expressions have access to the contents of the Admission request/response, organized into CEL variables as well as some other useful variables:
+      key specifies the audit annotation key. The audit annotation keys of a ValidatingAdmissionPolicy must be unique. The key must be a qualified name ([A-Za-z0-9][-A-Za-z0-9_.]*) no more than 63 bytes in length.
       
-      'object' - The object from the incoming request. The value is null for DELETE requests. 'oldObject' - The existing object. The value is null for CREATE requests. 'request' - Attributes of the admission request([ref](/pkg/apis/admission/types.go#AdmissionRequest)). 'params' - Parameter resource referred to by the policy binding being evaluated. Only populated if the policy has a ParamKind.
+      The key is combined with the resource name of the ValidatingAdmissionPolicy to construct an audit annotation key: "{ValidatingAdmissionPolicy name}/{key}".
       
-      The `apiVersion`, `kind`, `metadata.name` and `metadata.generateName` are always accessible from the root of the object. No other metadata properties are accessible.
+      If an admission webhook uses the same resource name as this ValidatingAdmissionPolicy and the same audit annotation key, the annotation key will be identical. In this case, the first annotation written with the key will be included in the audit event and all subsequent annotations with the same key will be discarded.
       
-      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: - '__' escapes to '__underscores__' - '.' escapes to '__dot__' - '-' escapes to '__dash__' - '/' escapes to '__slash__' - Property names that exactly match a CEL RESERVED keyword escape to '__{keyword}__'. The keywords are:
-      	  "true", "false", "null", "in", "as", "break", "const", "continue", "else", "for", "function", "if",
-      	  "import", "let", "loop", "package", "namespace", "return".
-      Examples:
-        - Expression accessing a property named "namespace": {"Expression": "object.__namespace__ > 0"}
-        - Expression accessing a property named "x-prop": {"Expression": "object.x__dash__prop > 0"}
-        - Expression accessing a property named "redact__d": {"Expression": "object.redact__underscores__d > 0"}
-      
-      Equality on arrays with 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.
       Required.
 
-    - **spec.validations.message** (string)
+    - **spec.auditAnnotations.valueExpression** (string), required
 
-      Message represents the message displayed when validation fails. The message is required if the Expression contains line breaks. The message must not contain line breaks. If unset, the message is "failed rule: {Rule}". e.g. "must be a URL with the host matching spec.host" If the Expression contains line breaks. Message is required. The message must not contain line breaks. If unset, the message is "failed Expression: {Expression}".
-
-    - **spec.validations.reason** (string)
-
-      Reason represents a machine-readable description of why this validation failed. If this is the first validation in the list to fail, this reason, as well as the corresponding HTTP response code, are used in the HTTP response to the client. The currently supported reasons are: "Unauthorized", "Forbidden", "Invalid", "RequestEntityTooLarge". If not set, StatusReasonInvalid is used in the response to the client.
+      valueExpression represents the expression which is evaluated by CEL to produce an audit annotation value. The expression must evaluate to either a string or null value. If the expression evaluates to a string, the audit annotation is included with the string value. If the expression evaluates to null or empty string the audit annotation will be omitted. The valueExpression may be no longer than 5kb in length. If the result of the valueExpression is more than 10kb in length, it will be truncated to 10kb.
+      
+      If multiple ValidatingAdmissionPolicyBinding resources match an API request, then the valueExpression will be evaluated for each binding. All unique values produced by the valueExpressions will be joined together in a comma-separated list.
+      
+      Required.
 
   - **spec.failurePolicy** (string)
 
-    FailurePolicy defines how to handle failures for the admission policy. Failures can occur from invalid or mis-configured policy definitions or bindings. A policy is invalid if spec.paramKind refers to a non-existent Kind. A binding is invalid if spec.paramRef.name refers to a non-existent resource. Allowed values are Ignore or Fail. Defaults to Fail.
+    failurePolicy defines how to handle failures for the admission policy. Failures can occur from CEL expression parse errors, type check errors, runtime errors and invalid or mis-configured policy definitions or bindings.
+    
+    A policy is invalid if spec.paramKind refers to a non-existent Kind. A binding is invalid if spec.paramRef.name refers to a non-existent resource.
+    
+    failurePolicy does not define how validations that evaluate to false are handled.
+    
+    When failurePolicy is set to Fail, ValidatingAdmissionPolicyBinding validationActions define how failures are enforced.
+    
+    Allowed values are Ignore or Fail. Defaults to Fail.
+
+  - **spec.matchConditions** ([]MatchCondition)
+
+    *Patch strategy: merge on key `name`*
+    
+    *Map: unique values on key name will be kept during a merge*
+    
+    MatchConditions is a list of conditions that must be met for a request to be validated. Match conditions filter requests that have already been matched by the rules, namespaceSelector, and objectSelector. An empty list of matchConditions matches all requests. There are a maximum of 64 match conditions allowed.
+    
+    If a parameter object is provided, it can be accessed via the `params` handle in the same manner as validation expressions.
+    
+    The exact matching logic is (in order):
+      1. If ANY matchCondition evaluates to FALSE, the policy is skipped.
+      2. If ALL matchConditions evaluate to TRUE, the policy is evaluated.
+      3. If any matchCondition evaluates to an error (but none are FALSE):
+         - If failurePolicy=Fail, reject the request
+         - If failurePolicy=Ignore, the policy is skipped
+
+    <a name="MatchCondition"></a>
+    **
+
+    - **spec.matchConditions.expression** (string), required
+
+      Expression represents the expression which will be evaluated by CEL. Must evaluate to bool. CEL expressions have access to the contents of the AdmissionRequest and Authorizer, organized into CEL variables:
+      
+      'object' - The object from the incoming request. The value is null for DELETE requests. 'oldObject' - The existing object. The value is null for CREATE requests. 'request' - Attributes of the admission request(/pkg/apis/admission/types.go#AdmissionRequest). 'authorizer' - A CEL Authorizer. May be used to perform authorization checks for the principal (user or service account) of the request.
+        See https://pkg.go.dev/k8s.io/apiserver/pkg/cel/library#Authz
+      'authorizer.requestResource' - A CEL ResourceCheck constructed from the 'authorizer' and configured with the
+        request resource.
+      Documentation on CEL: https://kubernetes.io/docs/reference/using-api/cel/
+      
+      Required.
+
+    - **spec.matchConditions.name** (string), required
+
+      Name is an identifier for this match condition, used for strategic merging of MatchConditions, as well as providing an identifier for logging purposes. A good name should be descriptive of the associated expression. Name must be a qualified name consisting of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyName',  or 'my.name',  or '123-abc', regex used for validation is '([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]') with an optional DNS subdomain prefix and '/' (e.g. 'example.com/MyName')
+      
+      Required.
 
   - **spec.matchConstraints** (MatchResources)
 
@@ -262,6 +294,125 @@ ValidatingAdmissionPolicy describes the definition of an admission validation po
 
       Kind is the API kind the resources belong to. Required.
 
+  - **spec.validations** ([]Validation)
+
+    *Atomic: will be replaced during a merge*
+    
+    Validations contain CEL expressions which is used to apply the validation. Validations and AuditAnnotations may not both be empty; a minimum of one Validations or AuditAnnotations is required.
+
+    <a name="Validation"></a>
+    *Validation specifies the CEL expression which is used to apply the validation.*
+
+    - **spec.validations.expression** (string), required
+
+      Expression represents the expression which will be evaluated by CEL. ref: https://github.com/google/cel-spec CEL expressions have access to the contents of the API request/response, organized into CEL variables as well as some other useful variables:
+      
+      - 'object' - The object from the incoming request. The value is null for DELETE requests. - 'oldObject' - The existing object. The value is null for CREATE requests. - 'request' - Attributes of the API request([ref](/pkg/apis/admission/types.go#AdmissionRequest)). - 'params' - Parameter resource referred to by the policy binding being evaluated. Only populated if the policy has a ParamKind. - 'authorizer' - A CEL Authorizer. May be used to perform authorization checks for the principal (user or service account) of the request.
+        See https://pkg.go.dev/k8s.io/apiserver/pkg/cel/library#Authz
+      - 'authorizer.requestResource' - A CEL ResourceCheck constructed from the 'authorizer' and configured with the
+        request resource.
+      
+      The `apiVersion`, `kind`, `metadata.name` and `metadata.generateName` are always accessible from the root of the object. No other metadata properties are accessible.
+      
+      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: - '__' escapes to '__underscores__' - '.' escapes to '__dot__' - '-' escapes to '__dash__' - '/' escapes to '__slash__' - Property names that exactly match a CEL RESERVED keyword escape to '__{keyword}__'. The keywords are:
+      	  "true", "false", "null", "in", "as", "break", "const", "continue", "else", "for", "function", "if",
+      	  "import", "let", "loop", "package", "namespace", "return".
+      Examples:
+        - Expression accessing a property named "namespace": {"Expression": "object.__namespace__ > 0"}
+        - Expression accessing a property named "x-prop": {"Expression": "object.x__dash__prop > 0"}
+        - Expression accessing a property named "redact__d": {"Expression": "object.redact__underscores__d > 0"}
+      
+      Equality on arrays with 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.
+      Required.
+
+    - **spec.validations.message** (string)
+
+      Message represents the message displayed when validation fails. The message is required if the Expression contains line breaks. The message must not contain line breaks. If unset, the message is "failed rule: {Rule}". e.g. "must be a URL with the host matching spec.host" If the Expression contains line breaks. Message is required. The message must not contain line breaks. If unset, the message is "failed Expression: {Expression}".
+
+    - **spec.validations.messageExpression** (string)
+
+      messageExpression declares a CEL expression that evaluates to the validation failure message that is returned when this rule fails. Since messageExpression is used as a failure message, it must evaluate to a string. If both message and messageExpression are present on a validation, then messageExpression will be used if validation fails. If messageExpression results in a runtime error, the runtime error is logged, and the validation failure message is produced as if the messageExpression field were unset. If messageExpression evaluates to an empty string, a string with only spaces, or a string that contains line breaks, then the validation failure message will also be produced as if the messageExpression field were unset, and the fact that messageExpression produced an empty string/string with only spaces/string with line breaks will be logged. messageExpression has access to all the same variables as the `expression` except for 'authorizer' and 'authorizer.requestResource'. Example: "object.x must be less than max ("+string(params.max)+")"
+
+    - **spec.validations.reason** (string)
+
+      Reason represents a machine-readable description of why this validation failed. If this is the first validation in the list to fail, this reason, as well as the corresponding HTTP response code, are used in the HTTP response to the client. The currently supported reasons are: "Unauthorized", "Forbidden", "Invalid", "RequestEntityTooLarge". If not set, StatusReasonInvalid is used in the response to the client.
+
+- **status** (ValidatingAdmissionPolicyStatus)
+
+  The status of the ValidatingAdmissionPolicy, including warnings that are useful to determine if the policy behaves in the expected way. Populated by the system. Read-only.
+
+  <a name="ValidatingAdmissionPolicyStatus"></a>
+  *ValidatingAdmissionPolicyStatus represents the status of a ValidatingAdmissionPolicy.*
+
+  - **status.conditions** ([]Condition)
+
+    *Map: unique values on key type will be kept during a merge*
+    
+    The conditions represent the latest available observations of a policy's current state.
+
+    <a name="Condition"></a>
+    *Condition contains details for one aspect of the current state of this API Resource.*
+
+    - **status.conditions.lastTransitionTime** (Time), required
+
+      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.
+
+      <a name="Time"></a>
+      *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.*
+
+    - **status.conditions.message** (string), required
+
+      message is a human readable message indicating details about the transition. This may be an empty string.
+
+    - **status.conditions.reason** (string), required
+
+      reason contains a programmatic identifier indicating the reason for the condition'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.
+
+    - **status.conditions.status** (string), required
+
+      status of the condition, one of True, False, Unknown.
+
+    - **status.conditions.type** (string), required
+
+      type of condition in CamelCase or in foo.example.com/CamelCase.
+
+    - **status.conditions.observedGeneration** (int64)
+
+      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.
+
+  - **status.observedGeneration** (int64)
+
+    The generation observed by the controller.
+
+  - **status.typeChecking** (TypeChecking)
+
+    The results of type checking for each expression. Presence of this field indicates the completion of the type checking.
+
+    <a name="TypeChecking"></a>
+    *TypeChecking contains results of type checking the expressions in the ValidatingAdmissionPolicy*
+
+    - **status.typeChecking.expressionWarnings** ([]ExpressionWarning)
+
+      *Atomic: will be replaced during a merge*
+      
+      The type checking warnings for each expression.
+
+      <a name="ExpressionWarning"></a>
+      *ExpressionWarning is a warning information that targets a specific expression.*
+
+      - **status.typeChecking.expressionWarnings.fieldRef** (string), required
+
+        The path to the field that refers the expression. For example, the reference to the expression of the first item of validations is "spec.validations[0].expression"
+
+      - **status.typeChecking.expressionWarnings.warning** (string), required
+
+        The content of type checking information in a human-readable form. Each line of the warning contains the type that the expression is checked against, followed by the type check error from the compiler.
+
 
 
 
@@ -489,6 +640,30 @@ ValidatingAdmissionPolicyBinding binds the ValidatingAdmissionPolicy with parame
 
     PolicyName references a ValidatingAdmissionPolicy name which the ValidatingAdmissionPolicyBinding binds to. If the referenced resource does not exist, this binding is considered invalid and will be ignored Required.
 
+  - **spec.validationActions** ([]string)
+
+    *Set: unique values will be kept during a merge*
+    
+    validationActions declares how Validations of the referenced ValidatingAdmissionPolicy are enforced. If a validation evaluates to false it is always enforced according to these actions.
+    
+    Failures defined by the ValidatingAdmissionPolicy's FailurePolicy are enforced according to these actions only if the FailurePolicy is set to Fail, otherwise the failures are ignored. This includes compilation errors, runtime errors and misconfigurations of the policy.
+    
+    validationActions is declared as a set of action values. Order does not matter. validationActions may not contain duplicates of the same action.
+    
+    The supported actions values are:
+    
+    "Deny" specifies that a validation failure results in a denied request.
+    
+    "Warn" specifies that a validation failure is reported to the request client in HTTP Warning headers, with a warning code of 299. Warnings can be sent both for allowed or denied admission responses.
+    
+    "Audit" specifies that a validation failure is included in the published audit event for the request. The audit event will contain a `validation.policy.admission.k8s.io/validation_failure` audit annotation with a value containing the details of the validation failures, formatted as a JSON list of objects, each with the following fields: - message: The validation failure message string - policy: The resource name of the ValidatingAdmissionPolicy - binding: The resource name of the ValidatingAdmissionPolicyBinding - expressionIndex: The index of the failed validations in the ValidatingAdmissionPolicy - validationActions: The enforcement actions enacted for the validation failure Example audit annotation: `"validation.policy.admission.k8s.io/validation_failure": "[{"message": "Invalid value", {"policy": "policy.example.com", {"binding": "policybinding.example.com", {"expressionIndex": "1", {"validationActions": ["Audit"]}]"`
+    
+    Clients should expect to handle additional values by ignoring any values not recognized.
+    
+    "Deny" and "Warn" may not be used together since this combination needlessly duplicates the validation failure both in the API response body and the HTTP warning headers.
+    
+    Required.
+
 
 
 
@@ -524,6 +699,34 @@ GET /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{nam
 
 
 
+#### Response
+
+
+200 (<a href="{{< ref "../extend-resources/validating-admission-policy-v1alpha1#ValidatingAdmissionPolicy" >}}">ValidatingAdmissionPolicy</a>): OK
+
+401: Unauthorized
+
+
+### `get` read status of the specified ValidatingAdmissionPolicy
+
+#### HTTP Request
+
+GET /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{name}/status
+
+#### Parameters
+
+
+- **name** (*in path*): string, required
+
+  name of the ValidatingAdmissionPolicy
+
+
+- **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
+
+
 #### Response
 
 
@@ -581,6 +784,11 @@ GET /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -666,6 +874,56 @@ PUT /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{nam
   
 
 
+- **dryRun** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
+
+
+- **fieldManager** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
+
+
+- **fieldValidation** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
+
+
+- **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
+
+
+#### Response
+
+
+200 (<a href="{{< ref "../extend-resources/validating-admission-policy-v1alpha1#ValidatingAdmissionPolicy" >}}">ValidatingAdmissionPolicy</a>): OK
+
+201 (<a href="{{< ref "../extend-resources/validating-admission-policy-v1alpha1#ValidatingAdmissionPolicy" >}}">ValidatingAdmissionPolicy</a>): Created
+
+401: Unauthorized
+
+
+### `update` replace status of the specified ValidatingAdmissionPolicy
+
+#### HTTP Request
+
+PUT /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{name}/status
+
+#### Parameters
+
+
+- **name** (*in path*): string, required
+
+  name of the ValidatingAdmissionPolicy
+
+
+- **body**: <a href="{{< ref "../extend-resources/validating-admission-policy-v1alpha1#ValidatingAdmissionPolicy" >}}">ValidatingAdmissionPolicy</a>, required
+
+  
+
+
 - **dryRun** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
@@ -716,6 +974,61 @@ PATCH /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{n
   
 
 
+- **dryRun** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
+
+
+- **fieldManager** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
+
+
+- **fieldValidation** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
+
+
+- **force** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#force" >}}">force</a>
+
+
+- **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
+
+
+#### Response
+
+
+200 (<a href="{{< ref "../extend-resources/validating-admission-policy-v1alpha1#ValidatingAdmissionPolicy" >}}">ValidatingAdmissionPolicy</a>): OK
+
+201 (<a href="{{< ref "../extend-resources/validating-admission-policy-v1alpha1#ValidatingAdmissionPolicy" >}}">ValidatingAdmissionPolicy</a>): Created
+
+401: Unauthorized
+
+
+### `patch` partially update status of the specified ValidatingAdmissionPolicy
+
+#### HTTP Request
+
+PATCH /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{name}/status
+
+#### Parameters
+
+
+- **name** (*in path*): string, required
+
+  name of the ValidatingAdmissionPolicy
+
+
+- **body**: <a href="{{< ref "../common-definitions/patch#Patch" >}}">Patch</a>, required
+
+  
+
+
 - **dryRun** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
@@ -866,6 +1179,11 @@ DELETE /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/extend-resources/validating-webhook-configuration-v1.md b/content/en/docs/reference/kubernetes-api/extend-resources/validating-webhook-configuration-v1.md
index d41aa10efeb..6821958013b 100644
--- a/content/en/docs/reference/kubernetes-api/extend-resources/validating-webhook-configuration-v1.md
+++ b/content/en/docs/reference/kubernetes-api/extend-resources/validating-webhook-configuration-v1.md
@@ -117,6 +117,44 @@ ValidatingWebhookConfiguration describes the configuration of and admission webh
 
     FailurePolicy defines how unrecognized errors from the admission endpoint are handled - allowed values are Ignore or Fail. Defaults to Fail.
 
+  - **webhooks.matchConditions** ([]MatchCondition)
+
+    *Patch strategy: merge on key `name`*
+    
+    *Map: unique values on key name will be kept during a merge*
+    
+    MatchConditions is a list of conditions that must be met for a request to be sent to this webhook. Match conditions filter requests that have already been matched by the rules, namespaceSelector, and objectSelector. An empty list of matchConditions matches all requests. There are a maximum of 64 match conditions allowed.
+    
+    The exact matching logic is (in order):
+      1. If ANY matchCondition evaluates to FALSE, the webhook is skipped.
+      2. If ALL matchConditions evaluate to TRUE, the webhook is called.
+      3. If any matchCondition evaluates to an error (but none are FALSE):
+         - If failurePolicy=Fail, reject the request
+         - If failurePolicy=Ignore, the error is ignored and the webhook is skipped
+    
+    This is an alpha feature and managed by the AdmissionWebhookMatchConditions feature gate.
+
+    <a name="MatchCondition"></a>
+    *MatchCondition represents a condition which must by fulfilled for a request to be sent to a webhook.*
+
+    - **webhooks.matchConditions.expression** (string), required
+
+      Expression represents the expression which will be evaluated by CEL. Must evaluate to bool. CEL expressions have access to the contents of the AdmissionRequest and Authorizer, organized into CEL variables:
+      
+      'object' - The object from the incoming request. The value is null for DELETE requests. 'oldObject' - The existing object. The value is null for CREATE requests. 'request' - Attributes of the admission request(/pkg/apis/admission/types.go#AdmissionRequest). 'authorizer' - A CEL Authorizer. May be used to perform authorization checks for the principal (user or service account) of the request.
+        See https://pkg.go.dev/k8s.io/apiserver/pkg/cel/library#Authz
+      'authorizer.requestResource' - A CEL ResourceCheck constructed from the 'authorizer' and configured with the
+        request resource.
+      Documentation on CEL: https://kubernetes.io/docs/reference/using-api/cel/
+      
+      Required.
+
+    - **webhooks.matchConditions.name** (string), required
+
+      Name is an identifier for this match condition, used for strategic merging of MatchConditions, as well as providing an identifier for logging purposes. A good name should be descriptive of the associated expression. Name must be a qualified name consisting of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyName',  or 'my.name',  or '123-abc', regex used for validation is '([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]') with an optional DNS subdomain prefix and '/' (e.g. 'example.com/MyName')
+      
+      Required.
+
   - **webhooks.matchPolicy** (string)
 
     matchPolicy defines how the "rules" list is used to match incoming requests. Allowed values are "Exact" or "Equivalent".
@@ -326,6 +364,11 @@ GET /apis/admissionregistration.k8s.io/v1/validatingwebhookconfigurations
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -611,6 +654,11 @@ DELETE /apis/admissionregistration.k8s.io/v1/validatingwebhookconfigurations
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/policy-resources/ip-address-v1alpha1.md b/content/en/docs/reference/kubernetes-api/policy-resources/ip-address-v1alpha1.md
new file mode 100644
index 00000000000..4828acb88c2
--- /dev/null
+++ b/content/en/docs/reference/kubernetes-api/policy-resources/ip-address-v1alpha1.md
@@ -0,0 +1,509 @@
+---
+api_metadata:
+  apiVersion: "networking.k8s.io/v1alpha1"
+  import: "k8s.io/api/networking/v1alpha1"
+  kind: "IPAddress"
+content_type: "api_reference"
+description: "IPAddress represents a single IP of a single IP Family."
+title: "IPAddress v1alpha1"
+weight: 5
+auto_generated: true
+---
+
+<!--
+The file is auto-generated from the Go source code of the component using a generic
+[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
+to generate the reference documentation, please read
+[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
+To update the reference content, please follow the 
+[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
+guide. You can file document formatting bugs against the
+[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
+-->
+
+`apiVersion: networking.k8s.io/v1alpha1`
+
+`import "k8s.io/api/networking/v1alpha1"`
+
+
+## IPAddress {#IPAddress}
+
+IPAddress represents a single IP of a single IP Family. The object is designed to be used by APIs that operate on IP addresses. The object is used by the Service core API for allocation of IP addresses. An IP address can be represented in different formats, to guarantee the uniqueness of the IP, the name of the object is the IP address in canonical format, four decimal digits separated by dots suppressing leading zeros for IPv4 and the representation defined by RFC 5952 for IPv6. Valid: 192.168.1.5 or 2001:db8::1 or 2001:db8:aaaa:bbbb:cccc:dddd:eeee:1 Invalid: 10.01.2.3 or 2001:db8:0:0:0::1
+
+<hr>
+
+- **apiVersion**: networking.k8s.io/v1alpha1
+
+
+- **kind**: IPAddress
+
+
+- **metadata** (<a href="{{< ref "../common-definitions/object-meta#ObjectMeta" >}}">ObjectMeta</a>)
+
+  Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
+
+- **spec** (<a href="{{< ref "../policy-resources/ip-address-v1alpha1#IPAddressSpec" >}}">IPAddressSpec</a>)
+
+  spec is the desired state of the IPAddress. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
+
+
+
+
+
+## IPAddressSpec {#IPAddressSpec}
+
+IPAddressSpec describe the attributes in an IP Address.
+
+<hr>
+
+- **parentRef** (ParentReference)
+
+  ParentRef references the resource that an IPAddress is attached to. An IPAddress must reference a parent object.
+
+  <a name="ParentReference"></a>
+  *ParentReference describes a reference to a parent object.*
+
+  - **parentRef.group** (string)
+
+    Group is the group of the object being referenced.
+
+  - **parentRef.name** (string)
+
+    Name is the name of the object being referenced.
+
+  - **parentRef.namespace** (string)
+
+    Namespace is the namespace of the object being referenced.
+
+  - **parentRef.resource** (string)
+
+    Resource is the resource of the object being referenced.
+
+  - **parentRef.uid** (string)
+
+    UID is the uid of the object being referenced.
+
+
+
+
+
+## IPAddressList {#IPAddressList}
+
+IPAddressList contains a list of IPAddress.
+
+<hr>
+
+- **apiVersion**: networking.k8s.io/v1alpha1
+
+
+- **kind**: IPAddressList
+
+
+- **metadata** (<a href="{{< ref "../common-definitions/list-meta#ListMeta" >}}">ListMeta</a>)
+
+  Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
+
+- **items** ([]<a href="{{< ref "../policy-resources/ip-address-v1alpha1#IPAddress" >}}">IPAddress</a>), required
+
+  items is the list of IPAddresses.
+
+
+
+
+
+## Operations {#Operations}
+
+
+
+<hr>
+
+
+
+
+
+
+### `get` read the specified IPAddress
+
+#### HTTP Request
+
+GET /apis/networking.k8s.io/v1alpha1/ipaddresses/{name}
+
+#### Parameters
+
+
+- **name** (*in path*): string, required
+
+  name of the IPAddress
+
+
+- **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
+
+
+#### Response
+
+
+200 (<a href="{{< ref "../policy-resources/ip-address-v1alpha1#IPAddress" >}}">IPAddress</a>): OK
+
+401: Unauthorized
+
+
+### `list` list or watch objects of kind IPAddress
+
+#### HTTP Request
+
+GET /apis/networking.k8s.io/v1alpha1/ipaddresses
+
+#### Parameters
+
+
+- **allowWatchBookmarks** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#allowWatchBookmarks" >}}">allowWatchBookmarks</a>
+
+
+- **continue** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#continue" >}}">continue</a>
+
+
+- **fieldSelector** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldSelector" >}}">fieldSelector</a>
+
+
+- **labelSelector** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#labelSelector" >}}">labelSelector</a>
+
+
+- **limit** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#limit" >}}">limit</a>
+
+
+- **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
+
+- **resourceVersion** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#resourceVersion" >}}">resourceVersion</a>
+
+
+- **resourceVersionMatch** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
+
+
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
+- **timeoutSeconds** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
+
+
+- **watch** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#watch" >}}">watch</a>
+
+
+
+#### Response
+
+
+200 (<a href="{{< ref "../policy-resources/ip-address-v1alpha1#IPAddressList" >}}">IPAddressList</a>): OK
+
+401: Unauthorized
+
+
+### `create` create an IPAddress
+
+#### HTTP Request
+
+POST /apis/networking.k8s.io/v1alpha1/ipaddresses
+
+#### Parameters
+
+
+- **body**: <a href="{{< ref "../policy-resources/ip-address-v1alpha1#IPAddress" >}}">IPAddress</a>, required
+
+  
+
+
+- **dryRun** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
+
+
+- **fieldManager** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
+
+
+- **fieldValidation** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
+
+
+- **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
+
+
+#### Response
+
+
+200 (<a href="{{< ref "../policy-resources/ip-address-v1alpha1#IPAddress" >}}">IPAddress</a>): OK
+
+201 (<a href="{{< ref "../policy-resources/ip-address-v1alpha1#IPAddress" >}}">IPAddress</a>): Created
+
+202 (<a href="{{< ref "../policy-resources/ip-address-v1alpha1#IPAddress" >}}">IPAddress</a>): Accepted
+
+401: Unauthorized
+
+
+### `update` replace the specified IPAddress
+
+#### HTTP Request
+
+PUT /apis/networking.k8s.io/v1alpha1/ipaddresses/{name}
+
+#### Parameters
+
+
+- **name** (*in path*): string, required
+
+  name of the IPAddress
+
+
+- **body**: <a href="{{< ref "../policy-resources/ip-address-v1alpha1#IPAddress" >}}">IPAddress</a>, required
+
+  
+
+
+- **dryRun** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
+
+
+- **fieldManager** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
+
+
+- **fieldValidation** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
+
+
+- **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
+
+
+#### Response
+
+
+200 (<a href="{{< ref "../policy-resources/ip-address-v1alpha1#IPAddress" >}}">IPAddress</a>): OK
+
+201 (<a href="{{< ref "../policy-resources/ip-address-v1alpha1#IPAddress" >}}">IPAddress</a>): Created
+
+401: Unauthorized
+
+
+### `patch` partially update the specified IPAddress
+
+#### HTTP Request
+
+PATCH /apis/networking.k8s.io/v1alpha1/ipaddresses/{name}
+
+#### Parameters
+
+
+- **name** (*in path*): string, required
+
+  name of the IPAddress
+
+
+- **body**: <a href="{{< ref "../common-definitions/patch#Patch" >}}">Patch</a>, required
+
+  
+
+
+- **dryRun** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
+
+
+- **fieldManager** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
+
+
+- **fieldValidation** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
+
+
+- **force** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#force" >}}">force</a>
+
+
+- **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
+
+
+#### Response
+
+
+200 (<a href="{{< ref "../policy-resources/ip-address-v1alpha1#IPAddress" >}}">IPAddress</a>): OK
+
+201 (<a href="{{< ref "../policy-resources/ip-address-v1alpha1#IPAddress" >}}">IPAddress</a>): Created
+
+401: Unauthorized
+
+
+### `delete` delete an IPAddress
+
+#### HTTP Request
+
+DELETE /apis/networking.k8s.io/v1alpha1/ipaddresses/{name}
+
+#### Parameters
+
+
+- **name** (*in path*): string, required
+
+  name of the IPAddress
+
+
+- **body**: <a href="{{< ref "../common-definitions/delete-options#DeleteOptions" >}}">DeleteOptions</a>
+
+  
+
+
+- **dryRun** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
+
+
+- **gracePeriodSeconds** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#gracePeriodSeconds" >}}">gracePeriodSeconds</a>
+
+
+- **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
+
+- **propagationPolicy** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#propagationPolicy" >}}">propagationPolicy</a>
+
+
+
+#### Response
+
+
+200 (<a href="{{< ref "../common-definitions/status#Status" >}}">Status</a>): OK
+
+202 (<a href="{{< ref "../common-definitions/status#Status" >}}">Status</a>): Accepted
+
+401: Unauthorized
+
+
+### `deletecollection` delete collection of IPAddress
+
+#### HTTP Request
+
+DELETE /apis/networking.k8s.io/v1alpha1/ipaddresses
+
+#### Parameters
+
+
+- **body**: <a href="{{< ref "../common-definitions/delete-options#DeleteOptions" >}}">DeleteOptions</a>
+
+  
+
+
+- **continue** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#continue" >}}">continue</a>
+
+
+- **dryRun** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
+
+
+- **fieldSelector** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldSelector" >}}">fieldSelector</a>
+
+
+- **gracePeriodSeconds** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#gracePeriodSeconds" >}}">gracePeriodSeconds</a>
+
+
+- **labelSelector** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#labelSelector" >}}">labelSelector</a>
+
+
+- **limit** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#limit" >}}">limit</a>
+
+
+- **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
+
+- **propagationPolicy** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#propagationPolicy" >}}">propagationPolicy</a>
+
+
+- **resourceVersion** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#resourceVersion" >}}">resourceVersion</a>
+
+
+- **resourceVersionMatch** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
+
+
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
+- **timeoutSeconds** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
+
+
+
+#### Response
+
+
+200 (<a href="{{< ref "../common-definitions/status#Status" >}}">Status</a>): OK
+
+401: Unauthorized
+
diff --git a/content/en/docs/reference/kubernetes-api/policy-resources/limit-range-v1.md b/content/en/docs/reference/kubernetes-api/policy-resources/limit-range-v1.md
index 3be570cfb0a..ef4355e4f27 100644
--- a/content/en/docs/reference/kubernetes-api/policy-resources/limit-range-v1.md
+++ b/content/en/docs/reference/kubernetes-api/policy-resources/limit-range-v1.md
@@ -213,6 +213,11 @@ GET /api/v1/namespaces/{namespace}/limitranges
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -281,6 +286,11 @@ GET /api/v1/limitranges
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -591,6 +601,11 @@ DELETE /api/v1/namespaces/{namespace}/limitranges
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/policy-resources/network-policy-v1.md b/content/en/docs/reference/kubernetes-api/policy-resources/network-policy-v1.md
index 5a1b4f17ae6..01345b62583 100644
--- a/content/en/docs/reference/kubernetes-api/policy-resources/network-policy-v1.md
+++ b/content/en/docs/reference/kubernetes-api/policy-resources/network-policy-v1.md
@@ -44,11 +44,11 @@ NetworkPolicy describes what network traffic is allowed for a set of Pods
 
 - **spec** (<a href="{{< ref "../policy-resources/network-policy-v1#NetworkPolicySpec" >}}">NetworkPolicySpec</a>)
 
-  Specification of the desired behavior for this NetworkPolicy.
+  spec represents the specification of the desired behavior for this NetworkPolicy.
 
 - **status** (<a href="{{< ref "../policy-resources/network-policy-v1#NetworkPolicyStatus" >}}">NetworkPolicyStatus</a>)
 
-  Status is the current state of the NetworkPolicy. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
+  status represents the current state of the NetworkPolicy. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
 
 
 
@@ -62,137 +62,137 @@ NetworkPolicySpec provides the specification of a NetworkPolicy
 
 - **podSelector** (<a href="{{< ref "../common-definitions/label-selector#LabelSelector" >}}">LabelSelector</a>), required
 
-  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.
+  podSelector 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.
 
 - **policyTypes** ([]string)
 
-  List of rule types that the NetworkPolicy relates to. Valid options are ["Ingress"], ["Egress"], or ["Ingress", "Egress"]. 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 [ "Egress" ]. Likewise, if you want to write a policy that specifies that no egress is allowed, you must specify a policyTypes value that include "Egress" (since such a policy would not include an Egress section and would otherwise default to just [ "Ingress" ]). This field is beta-level in 1.8
+  policyTypes is a list of rule types that the NetworkPolicy relates to. Valid options are ["Ingress"], ["Egress"], or ["Ingress", "Egress"]. 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 [ "Egress" ]. Likewise, if you want to write a policy that specifies that no egress is allowed, you must specify a policyTypes value that include "Egress" (since such a policy would not include an egress section and would otherwise default to just [ "Ingress" ]). This field is beta-level in 1.8
 
 - **ingress** ([]NetworkPolicyIngressRule)
 
-  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'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)
+  ingress is a 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'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)
 
   <a name="NetworkPolicyIngressRule"></a>
   *NetworkPolicyIngressRule describes a particular set of traffic that is allowed to the pods matched by a NetworkPolicySpec's podSelector. The traffic must match both ports and from.*
 
   - **ingress.from** ([]NetworkPolicyPeer)
 
-    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.
+    from is a 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.
 
     <a name="NetworkPolicyPeer"></a>
     *NetworkPolicyPeer describes a peer to allow traffic to/from. Only certain combinations of fields are allowed*
 
     - **ingress.from.ipBlock** (IPBlock)
 
-      IPBlock defines policy on a particular IPBlock. If this field is set then neither of the other fields can be.
+      ipBlock defines policy on a particular IPBlock. If this field is set then neither of the other fields can be.
 
       <a name="IPBlock"></a>
       *IPBlock describes a particular CIDR (Ex. "192.168.1.0/24","2001:db8::/64") that is allowed to the pods matched by a NetworkPolicySpec's podSelector. The except entry describes CIDRs that should not be included within this rule.*
 
       - **ingress.from.ipBlock.cidr** (string), required
 
-        CIDR is a string representing the IP Block Valid examples are "192.168.1.0/24" or "2001:db8::/64"
+        cidr is a string representing the IPBlock Valid examples are "192.168.1.0/24" or "2001:db8::/64"
 
       - **ingress.from.ipBlock.except** ([]string)
 
-        Except is a slice of CIDRs that should not be included within an IP Block Valid examples are "192.168.1.0/24" or "2001:db8::/64" Except values will be rejected if they are outside the CIDR range
+        except is a slice of CIDRs that should not be included within an IPBlock Valid examples are "192.168.1.0/24" or "2001:db8::/64" Except values will be rejected if they are outside the cidr range
 
     - **ingress.from.namespaceSelector** (<a href="{{< ref "../common-definitions/label-selector#LabelSelector" >}}">LabelSelector</a>)
 
-      Selects Namespaces using cluster-scoped labels. This field follows standard label selector semantics; if present but empty, it selects all namespaces.
+      namespaceSelector 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.
+      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.
 
     - **ingress.from.podSelector** (<a href="{{< ref "../common-definitions/label-selector#LabelSelector" >}}">LabelSelector</a>)
 
-      This is a label selector which selects Pods. This field follows standard label selector semantics; if present but empty, it selects all pods.
+      podSelector 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's own Namespace.
+      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's own namespace.
 
   - **ingress.ports** ([]NetworkPolicyPort)
 
-    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.
+    ports is a 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.
 
     <a name="NetworkPolicyPort"></a>
     *NetworkPolicyPort describes a port to allow traffic on*
 
     - **ingress.ports.port** (IntOrString)
 
-      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.
+      port represents 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.
 
       <a name="IntOrString"></a>
       *IntOrString is a type that can hold an int32 or a string.  When used in JSON or YAML marshalling and unmarshalling, it produces or consumes the inner type.  This allows you to have, for example, a JSON field that can accept a name or number.*
 
     - **ingress.ports.endPort** (int32)
 
-      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.
+      endPort indicates that the range of ports from port to endPort if set, 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.
 
     - **ingress.ports.protocol** (string)
 
-      The protocol (TCP, UDP, or SCTP) which traffic must match. If not specified, this field defaults to TCP.
+      protocol represents the protocol (TCP, UDP, or SCTP) which traffic must match. If not specified, this field defaults to TCP.
 
 - **egress** ([]NetworkPolicyEgressRule)
 
-  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
+  egress is a 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
 
   <a name="NetworkPolicyEgressRule"></a>
   *NetworkPolicyEgressRule describes a particular set of traffic that is allowed out of pods matched by a NetworkPolicySpec's podSelector. The traffic must match both ports and to. This type is beta-level in 1.8*
 
   - **egress.to** ([]NetworkPolicyPeer)
 
-    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.
+    to is a 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.
 
     <a name="NetworkPolicyPeer"></a>
     *NetworkPolicyPeer describes a peer to allow traffic to/from. Only certain combinations of fields are allowed*
 
     - **egress.to.ipBlock** (IPBlock)
 
-      IPBlock defines policy on a particular IPBlock. If this field is set then neither of the other fields can be.
+      ipBlock defines policy on a particular IPBlock. If this field is set then neither of the other fields can be.
 
       <a name="IPBlock"></a>
       *IPBlock describes a particular CIDR (Ex. "192.168.1.0/24","2001:db8::/64") that is allowed to the pods matched by a NetworkPolicySpec's podSelector. The except entry describes CIDRs that should not be included within this rule.*
 
       - **egress.to.ipBlock.cidr** (string), required
 
-        CIDR is a string representing the IP Block Valid examples are "192.168.1.0/24" or "2001:db8::/64"
+        cidr is a string representing the IPBlock Valid examples are "192.168.1.0/24" or "2001:db8::/64"
 
       - **egress.to.ipBlock.except** ([]string)
 
-        Except is a slice of CIDRs that should not be included within an IP Block Valid examples are "192.168.1.0/24" or "2001:db8::/64" Except values will be rejected if they are outside the CIDR range
+        except is a slice of CIDRs that should not be included within an IPBlock Valid examples are "192.168.1.0/24" or "2001:db8::/64" Except values will be rejected if they are outside the cidr range
 
     - **egress.to.namespaceSelector** (<a href="{{< ref "../common-definitions/label-selector#LabelSelector" >}}">LabelSelector</a>)
 
-      Selects Namespaces using cluster-scoped labels. This field follows standard label selector semantics; if present but empty, it selects all namespaces.
+      namespaceSelector 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.
+      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.
 
     - **egress.to.podSelector** (<a href="{{< ref "../common-definitions/label-selector#LabelSelector" >}}">LabelSelector</a>)
 
-      This is a label selector which selects Pods. This field follows standard label selector semantics; if present but empty, it selects all pods.
+      podSelector 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's own Namespace.
+      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's own namespace.
 
   - **egress.ports** ([]NetworkPolicyPort)
 
-    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.
+    ports is a 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.
 
     <a name="NetworkPolicyPort"></a>
     *NetworkPolicyPort describes a port to allow traffic on*
 
     - **egress.ports.port** (IntOrString)
 
-      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.
+      port represents 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.
 
       <a name="IntOrString"></a>
       *IntOrString is a type that can hold an int32 or a string.  When used in JSON or YAML marshalling and unmarshalling, it produces or consumes the inner type.  This allows you to have, for example, a JSON field that can accept a name or number.*
 
     - **egress.ports.endPort** (int32)
 
-      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.
+      endPort indicates that the range of ports from port to endPort if set, 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.
 
     - **egress.ports.protocol** (string)
 
-      The protocol (TCP, UDP, or SCTP) which traffic must match. If not specified, this field defaults to TCP.
+      protocol represents the protocol (TCP, UDP, or SCTP) which traffic must match. If not specified, this field defaults to TCP.
 
 
 
@@ -200,7 +200,7 @@ NetworkPolicySpec provides the specification of a NetworkPolicy
 
 ## NetworkPolicyStatus {#NetworkPolicyStatus}
 
-NetworkPolicyStatus describe the current state of the NetworkPolicy.
+NetworkPolicyStatus describes the current state of the NetworkPolicy.
 
 <hr>
 
@@ -210,7 +210,7 @@ NetworkPolicyStatus describe the current state of the NetworkPolicy.
   
   *Map: unique values on key type will be kept during a merge*
   
-  Conditions holds an array of metav1.Condition that describe the state of the NetworkPolicy. Current service state
+  conditions holds an array of metav1.Condition that describe the state of the NetworkPolicy. Current service state
 
   <a name="Condition"></a>
   *Condition contains details for one aspect of the current state of this API Resource.*
@@ -264,7 +264,7 @@ NetworkPolicyList is a list of NetworkPolicy objects.
 
 - **items** ([]<a href="{{< ref "../policy-resources/network-policy-v1#NetworkPolicy" >}}">NetworkPolicy</a>), required
 
-  Items is a list of schema objects.
+  items is a list of schema objects.
 
 
 
@@ -401,6 +401,11 @@ GET /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -469,6 +474,11 @@ GET /apis/networking.k8s.io/v1/networkpolicies
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -894,6 +904,11 @@ DELETE /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/policy-resources/pod-disruption-budget-v1.md b/content/en/docs/reference/kubernetes-api/policy-resources/pod-disruption-budget-v1.md
index 7fd6fc3551a..ece7b336b9f 100644
--- a/content/en/docs/reference/kubernetes-api/policy-resources/pod-disruption-budget-v1.md
+++ b/content/en/docs/reference/kubernetes-api/policy-resources/pod-disruption-budget-v1.md
@@ -90,7 +90,7 @@ PodDisruptionBudgetSpec is a description of a PodDisruptionBudget.
   
   Additional policies may be added in the future. Clients making eviction decisions should disallow eviction of unhealthy pods if they encounter an unrecognized policy in this field.
   
-  This field is alpha-level. The eviction API uses this field when the feature gate PDBUnhealthyPodEvictionPolicy is enabled (disabled by default).
+  This field is beta-level. The eviction API uses this field when the feature gate PDBUnhealthyPodEvictionPolicy is enabled (enabled by default).
 
 
 
@@ -334,6 +334,11 @@ GET /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -402,6 +407,11 @@ GET /apis/policy/v1/poddisruptionbudgets
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -827,6 +837,11 @@ DELETE /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/policy-resources/resource-quota-v1.md b/content/en/docs/reference/kubernetes-api/policy-resources/resource-quota-v1.md
index 4675db74751..887b89886b5 100644
--- a/content/en/docs/reference/kubernetes-api/policy-resources/resource-quota-v1.md
+++ b/content/en/docs/reference/kubernetes-api/policy-resources/resource-quota-v1.md
@@ -81,14 +81,10 @@ ResourceQuotaSpec defines the desired hard limits to enforce for Quota.
     - **scopeSelector.matchExpressions.operator** (string), required
 
       Represents a scope's relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist.
-      
-      
 
     - **scopeSelector.matchExpressions.scopeName** (string), required
 
       The name of the scope that the selector applies to.
-      
-      
 
     - **scopeSelector.matchExpressions.values** ([]string)
 
@@ -275,6 +271,11 @@ GET /api/v1/namespaces/{namespace}/resourcequotas
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -343,6 +344,11 @@ GET /api/v1/resourcequotas
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -768,6 +774,11 @@ DELETE /api/v1/namespaces/{namespace}/resourcequotas
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/service-resources/endpoint-slice-v1.md b/content/en/docs/reference/kubernetes-api/service-resources/endpoint-slice-v1.md
index d2f6164d71d..06b8f032696 100644
--- a/content/en/docs/reference/kubernetes-api/service-resources/endpoint-slice-v1.md
+++ b/content/en/docs/reference/kubernetes-api/service-resources/endpoint-slice-v1.md
@@ -45,8 +45,6 @@ EndpointSlice represents a subset of the endpoints that implement a service. For
 - **addressType** (string), required
 
   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.
-  
-  
 
 - **endpoints** ([]Endpoint), required
 
@@ -72,7 +70,7 @@ EndpointSlice represents a subset of the endpoints that implement a service. For
 
     - **endpoints.conditions.ready** (boolean)
 
-      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 "true" for terminating endpoints.
+      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 "true" for terminating endpoints, except when the normal readiness behavior is being explicitly overridden, for example when the associated Service has set the publishNotReadyAddresses flag.
 
     - **endpoints.conditions.serving** (boolean)
 
@@ -133,19 +131,26 @@ EndpointSlice represents a subset of the endpoints that implement a service. For
 
   - **ports.port** (int32)
 
-    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.
+    port represents 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.
 
   - **ports.protocol** (string)
 
-    The IP protocol for this port. Must be UDP, TCP, or SCTP. Default is TCP.
+    protocol represents the IP protocol for this port. Must be UDP, TCP, or SCTP. Default is TCP.
 
   - **ports.name** (string)
 
-    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 '-'. * must start and end with an alphanumeric character. Default is empty string.
+    name represents 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 '-'. * must start and end with an alphanumeric character. Default is empty string.
 
   - **ports.appProtocol** (string)
 
-    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 https://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.
+    The application protocol for this port. This is used as a hint for implementations to offer richer behavior for protocols that they understand. This field follows standard Kubernetes label syntax. Valid values are either:
+    
+    * Un-prefixed protocol names - reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names).
+    
+    * Kubernetes-defined prefixed names:
+      * 'kubernetes.io/h2c' - HTTP/2 over cleartext as described in https://www.rfc-editor.org/rfc/rfc7540
+    
+    * Other protocols should use implementation-defined prefixed names such as mycompany.com/my-custom-protocol.
 
 
 
@@ -169,7 +174,7 @@ EndpointSliceList represents a list of endpoint slices
 
 - **items** ([]<a href="{{< ref "../service-resources/endpoint-slice-v1#EndpointSlice" >}}">EndpointSlice</a>), required
 
-  List of endpoint slices
+  items is the list of endpoint slices
 
 
 
@@ -273,6 +278,11 @@ GET /apis/discovery.k8s.io/v1/namespaces/{namespace}/endpointslices
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -341,6 +351,11 @@ GET /apis/discovery.k8s.io/v1/endpointslices
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -651,6 +666,11 @@ DELETE /apis/discovery.k8s.io/v1/namespaces/{namespace}/endpointslices
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/service-resources/endpoints-v1.md b/content/en/docs/reference/kubernetes-api/service-resources/endpoints-v1.md
index 8267741ea71..403dc9d535c 100644
--- a/content/en/docs/reference/kubernetes-api/service-resources/endpoints-v1.md
+++ b/content/en/docs/reference/kubernetes-api/service-resources/endpoints-v1.md
@@ -80,7 +80,7 @@ Endpoints is a collection of endpoints that implement the actual service. Exampl
 
     - **subsets.addresses.ip** (string), required
 
-      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.
+      The IP of this endpoint. May not be loopback (127.0.0.0/8 or ::1), link-local (169.254.0.0/16 or fe80::/10), or link-local multicast (224.0.0.0/24 or ff02::/16).
 
     - **subsets.addresses.hostname** (string)
 
@@ -103,7 +103,7 @@ Endpoints is a collection of endpoints that implement the actual service. Exampl
 
     - **subsets.notReadyAddresses.ip** (string), required
 
-      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.
+      The IP of this endpoint. May not be loopback (127.0.0.0/8 or ::1), link-local (169.254.0.0/16 or fe80::/10), or link-local multicast (224.0.0.0/24 or ff02::/16).
 
     - **subsets.notReadyAddresses.hostname** (string)
 
@@ -131,8 +131,6 @@ Endpoints is a collection of endpoints that implement the actual service. Exampl
     - **subsets.ports.protocol** (string)
 
       The IP protocol for this port. Must be UDP, TCP, or SCTP. Default is TCP.
-      
-      
 
     - **subsets.ports.name** (string)
 
@@ -140,7 +138,14 @@ Endpoints is a collection of endpoints that implement the actual service. Exampl
 
     - **subsets.ports.appProtocol** (string)
 
-      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 https://www.iana.org/assignments/service-names). Non-standard protocols should use prefixed names such as mycompany.com/my-custom-protocol.
+      The application protocol for this port. This is used as a hint for implementations to offer richer behavior for protocols that they understand. This field follows standard Kubernetes label syntax. Valid values are either:
+      
+      * Un-prefixed protocol names - reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names).
+      
+      * Kubernetes-defined prefixed names:
+        * 'kubernetes.io/h2c' - HTTP/2 over cleartext as described in https://www.rfc-editor.org/rfc/rfc7540
+      
+      * Other protocols should use implementation-defined prefixed names such as mycompany.com/my-custom-protocol.
 
 
 
@@ -268,6 +273,11 @@ GET /api/v1/namespaces/{namespace}/endpoints
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -336,6 +346,11 @@ GET /api/v1/endpoints
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -646,6 +661,11 @@ DELETE /api/v1/namespaces/{namespace}/endpoints
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/service-resources/ingress-class-v1.md b/content/en/docs/reference/kubernetes-api/service-resources/ingress-class-v1.md
index 009a5b7f9ef..db6654f2f30 100644
--- a/content/en/docs/reference/kubernetes-api/service-resources/ingress-class-v1.md
+++ b/content/en/docs/reference/kubernetes-api/service-resources/ingress-class-v1.md
@@ -44,7 +44,7 @@ IngressClass represents the class of the Ingress, referenced by the Ingress Spec
 
 - **spec** (<a href="{{< ref "../service-resources/ingress-class-v1#IngressClassSpec" >}}">IngressClassSpec</a>)
 
-  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
+  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
 
 
 
@@ -58,34 +58,34 @@ IngressClassSpec provides information about the class of an Ingress.
 
 - **controller** (string)
 
-  Controller refers to the name of the controller that should handle this class. This allows for different "flavors" 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. "acme.io/ingress-controller". This field is immutable.
+  controller refers to the name of the controller that should handle this class. This allows for different "flavors" 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. "acme.io/ingress-controller". This field is immutable.
 
 - **parameters** (IngressClassParametersReference)
 
-  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.
+  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.
 
   <a name="IngressClassParametersReference"></a>
   *IngressClassParametersReference identifies an API object. This can be used to specify a cluster or namespace-scoped resource.*
 
   - **parameters.kind** (string), required
 
-    Kind is the type of resource being referenced.
+    kind is the type of resource being referenced.
 
   - **parameters.name** (string), required
 
-    Name is the name of resource being referenced.
+    name is the name of resource being referenced.
 
   - **parameters.apiGroup** (string)
 
-    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.
+    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.
 
   - **parameters.namespace** (string)
 
-    Namespace is the namespace of the resource being referenced. This field is required when scope is set to "Namespace" and must be unset when scope is set to "Cluster".
+    namespace is the namespace of the resource being referenced. This field is required when scope is set to "Namespace" and must be unset when scope is set to "Cluster".
 
   - **parameters.scope** (string)
 
-    Scope represents if this refers to a cluster or namespace scoped resource. This may be set to "Cluster" (default) or "Namespace".
+    scope represents if this refers to a cluster or namespace scoped resource. This may be set to "Cluster" (default) or "Namespace".
 
 
 
@@ -109,7 +109,7 @@ IngressClassList is a collection of IngressClasses.
 
 - **items** ([]<a href="{{< ref "../service-resources/ingress-class-v1#IngressClass" >}}">IngressClass</a>), required
 
-  Items is the list of IngressClasses.
+  items is the list of IngressClasses.
 
 
 
@@ -203,6 +203,11 @@ GET /apis/networking.k8s.io/v1/ingressclasses
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -488,6 +493,11 @@ DELETE /apis/networking.k8s.io/v1/ingressclasses
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/service-resources/ingress-v1.md b/content/en/docs/reference/kubernetes-api/service-resources/ingress-v1.md
index d6c7290bac4..354cfa6ba60 100644
--- a/content/en/docs/reference/kubernetes-api/service-resources/ingress-v1.md
+++ b/content/en/docs/reference/kubernetes-api/service-resources/ingress-v1.md
@@ -44,11 +44,11 @@ Ingress is a collection of rules that allow inbound connections to reach the end
 
 - **spec** (<a href="{{< ref "../service-resources/ingress-v1#IngressSpec" >}}">IngressSpec</a>)
 
-  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
+  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
 
 - **status** (<a href="{{< ref "../service-resources/ingress-v1#IngressStatus" >}}">IngressStatus</a>)
 
-  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
+  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
 
 
 
@@ -62,31 +62,31 @@ IngressSpec describes the Ingress the user wishes to exist.
 
 - **defaultBackend** (<a href="{{< ref "../service-resources/ingress-v1#IngressBackend" >}}">IngressBackend</a>)
 
-  DefaultBackend is the backend that should handle requests that don'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.
+  defaultBackend is the backend that should handle requests that don'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.
 
 - **ingressClassName** (string)
 
-  IngressClassName is the name of an IngressClass cluster resource. Ingress controller implementations use this field to know whether they should be serving this Ingress resource, by a transitive connection (controller -> IngressClass -> Ingress resource). Although the `kubernetes.io/ingress.class` annotation (simple constant name) was never formally defined, it was widely supported by Ingress controllers to create a direct binding between Ingress controller and Ingress resources. Newly created Ingress resources should prefer using the field. However, even though the annotation is officially deprecated, for backwards compatibility reasons, ingress controllers should still honor that annotation if present.
+  ingressClassName is the name of an IngressClass cluster resource. Ingress controller implementations use this field to know whether they should be serving this Ingress resource, by a transitive connection (controller -> IngressClass -> Ingress resource). Although the `kubernetes.io/ingress.class` annotation (simple constant name) was never formally defined, it was widely supported by Ingress controllers to create a direct binding between Ingress controller and Ingress resources. Newly created Ingress resources should prefer using the field. However, even though the annotation is officially deprecated, for backwards compatibility reasons, ingress controllers should still honor that annotation if present.
 
 - **rules** ([]IngressRule)
 
   *Atomic: will be replaced during a merge*
   
-  A list of host rules used to configure the Ingress. If unspecified, or no rule matches, all traffic is sent to the default backend.
+  rules is a list of host rules used to configure the Ingress. If unspecified, or no rule matches, all traffic is sent to the default backend.
 
   <a name="IngressRule"></a>
   *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.*
 
   - **rules.host** (string)
 
-    Host is the fully qualified domain name of a network host, as defined by RFC 3986. Note the following deviations from the "host" part of the URI as defined in RFC 3986: 1. IPs are not allowed. Currently an IngressRuleValue can only apply to
+    host is the fully qualified domain name of a network host, as defined by RFC 3986. Note the following deviations from the "host" 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 "precise" which is a domain name without the terminating dot of a network host (e.g. "foo.bar.com") or "wildcard", which is a domain name prefixed with a single wildcard label (e.g. "*.foo.com"). The wildcard character '*' 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 == "*"). 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.
+    host can be "precise" which is a domain name without the terminating dot of a network host (e.g. "foo.bar.com") or "wildcard", which is a domain name prefixed with a single wildcard label (e.g. "*.foo.com"). The wildcard character '*' 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 == "*"). 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.
 
   - **rules.http** (HTTPIngressRuleValue)
 
@@ -98,18 +98,18 @@ IngressSpec describes the Ingress the user wishes to exist.
 
       *Atomic: will be replaced during a merge*
       
-      A collection of paths that map requests to backends.
+      paths is a collection of paths that map requests to backends.
 
       <a name="HTTPIngressPath"></a>
       *HTTPIngressPath associates a path with a backend. Incoming urls matching the path are forwarded to the backend.*
 
       - **rules.http.paths.backend** (<a href="{{< ref "../service-resources/ingress-v1#IngressBackend" >}}">IngressBackend</a>), required
 
-        Backend defines the referenced service endpoint to which the traffic will be forwarded to.
+        backend defines the referenced service endpoint to which the traffic will be forwarded to.
 
       - **rules.http.paths.pathType** (string), required
 
-        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 '/'. Matching is
+        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 '/'. 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 '/' separator. A request is a
           match for path p if every p is an element-wise prefix of p of the
@@ -123,26 +123,26 @@ IngressSpec describes the Ingress the user wishes to exist.
 
       - **rules.http.paths.path** (string)
 
-        Path is matched against the path of an incoming request. Currently it can contain characters disallowed from the conventional "path" part of a URL as defined by RFC 3986. Paths must begin with a '/' and must be present when using PathType with value "Exact" or "Prefix".
+        path is matched against the path of an incoming request. Currently it can contain characters disallowed from the conventional "path" part of a URL as defined by RFC 3986. Paths must begin with a '/' and must be present when using PathType with value "Exact" or "Prefix".
 
 - **tls** ([]IngressTLS)
 
   *Atomic: will be replaced during a merge*
   
-  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.
+  tls represents the 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.
 
   <a name="IngressTLS"></a>
-  *IngressTLS describes the transport layer security associated with an Ingress.*
+  *IngressTLS describes the transport layer security associated with an ingress.*
 
   - **tls.hosts** ([]string)
 
     *Atomic: will be replaced during a merge*
     
-    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.
+    hosts is 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.
 
   - **tls.secretName** (string)
 
-    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 "Host" header field used by an IngressRule, the SNI host is used for termination and value of the Host header is used for routing.
+    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 "Host" header field used by an IngressRule, the SNI host is used for termination and value of the "Host" header is used for routing.
 
 
 
@@ -156,33 +156,33 @@ IngressBackend describes all endpoints for a given service and port.
 
 - **resource** (<a href="{{< ref "../common-definitions/typed-local-object-reference#TypedLocalObjectReference" >}}">TypedLocalObjectReference</a>)
 
-  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 "Service".
+  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 "Service".
 
 - **service** (IngressServiceBackend)
 
-  Service references a Service as a Backend. This is a mutually exclusive setting with "Resource".
+  service references a service as a backend. This is a mutually exclusive setting with "Resource".
 
   <a name="IngressServiceBackend"></a>
   *IngressServiceBackend references a Kubernetes Service as a Backend.*
 
   - **service.name** (string), required
 
-    Name is the referenced service. The service must exist in the same namespace as the Ingress object.
+    name is the referenced service. The service must exist in the same namespace as the Ingress object.
 
   - **service.port** (ServiceBackendPort)
 
-    Port of the referenced service. A port name or port number is required for a IngressServiceBackend.
+    port of the referenced service. A port name or port number is required for a IngressServiceBackend.
 
     <a name="ServiceBackendPort"></a>
     *ServiceBackendPort is the service port being referenced.*
 
     - **service.port.name** (string)
 
-      Name is the name of the port on the Service. This is a mutually exclusive setting with "Number".
+      name is the name of the port on the Service. This is a mutually exclusive setting with "Number".
 
     - **service.port.number** (int32)
 
-      Number is the numerical port number (e.g. 80) on the Service. This is a mutually exclusive setting with "Name".
+      number is the numerical port number (e.g. 80) on the Service. This is a mutually exclusive setting with "Name".
 
 
 
@@ -196,48 +196,46 @@ IngressStatus describe the current state of the Ingress.
 
 - **loadBalancer** (IngressLoadBalancerStatus)
 
-  LoadBalancer contains the current status of the load-balancer.
+  loadBalancer contains the current status of the load-balancer.
 
   <a name="IngressLoadBalancerStatus"></a>
   *IngressLoadBalancerStatus represents the status of a load-balancer.*
 
   - **loadBalancer.ingress** ([]IngressLoadBalancerIngress)
 
-    Ingress is a list containing ingress points for the load-balancer.
+    ingress is a list containing ingress points for the load-balancer.
 
     <a name="IngressLoadBalancerIngress"></a>
     *IngressLoadBalancerIngress represents the status of a load-balancer ingress point.*
 
     - **loadBalancer.ingress.hostname** (string)
 
-      Hostname is set for load-balancer ingress points that are DNS based.
+      hostname is set for load-balancer ingress points that are DNS based.
 
     - **loadBalancer.ingress.ip** (string)
 
-      IP is set for load-balancer ingress points that are IP based.
+      ip is set for load-balancer ingress points that are IP based.
 
     - **loadBalancer.ingress.ports** ([]IngressPortStatus)
 
       *Atomic: will be replaced during a merge*
       
-      Ports provides information about the ports exposed by this LoadBalancer.
+      ports provides information about the ports exposed by this LoadBalancer.
 
       <a name="IngressPortStatus"></a>
       *IngressPortStatus represents the error condition of a service port*
 
       - **loadBalancer.ingress.ports.port** (int32), required
 
-        Port is the port number of the ingress port.
+        port is the port number of the ingress port.
 
       - **loadBalancer.ingress.ports.protocol** (string), required
 
-        Protocol is the protocol of the ingress port. The supported values are: "TCP", "UDP", "SCTP"
-        
-        
+        protocol is the protocol of the ingress port. The supported values are: "TCP", "UDP", "SCTP"
 
       - **loadBalancer.ingress.ports.error** (string)
 
-        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
+        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.
@@ -254,7 +252,7 @@ IngressList is a collection of Ingress.
 
 - **items** ([]<a href="{{< ref "../service-resources/ingress-v1#Ingress" >}}">Ingress</a>), required
 
-  Items is the list of Ingress.
+  items is the list of Ingress.
 
 - **apiVersion** (string)
 
@@ -403,6 +401,11 @@ GET /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -471,6 +474,11 @@ GET /apis/networking.k8s.io/v1/ingresses
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -896,6 +904,11 @@ DELETE /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/service-resources/service-v1.md b/content/en/docs/reference/kubernetes-api/service-resources/service-v1.md
index e98d49081c2..8159685fc44 100644
--- a/content/en/docs/reference/kubernetes-api/service-resources/service-v1.md
+++ b/content/en/docs/reference/kubernetes-api/service-resources/service-v1.md
@@ -89,8 +89,6 @@ ServiceSpec describes the attributes that a user creates on a service.
   - **ports.protocol** (string)
 
     The IP protocol for this port. Supports "TCP", "UDP", and "SCTP". Default is TCP.
-    
-    
 
   - **ports.name** (string)
 
@@ -107,8 +105,6 @@ ServiceSpec describes the attributes that a user creates on a service.
 - **type** (string)
 
   type determines how the Service is exposed. Defaults to ClusterIP. Valid options are ExternalName, ClusterIP, NodePort, and LoadBalancer. "ClusterIP" 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 "None", no virtual IP is allocated and the endpoints are published as a set of endpoints rather than a virtual IP. "NodePort" builds on ClusterIP and allocates a port on every node which routes to the same endpoints as the clusterIP. "LoadBalancer" builds on NodePort and creates an external load-balancer (if supported in the current cloud) which routes to the same endpoints as the clusterIP. "ExternalName" 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
-  
-  
 
 - **ipFamilies** ([]string)
 
@@ -141,8 +137,6 @@ ServiceSpec describes the attributes that a user creates on a service.
 - **sessionAffinity** (string)
 
   Supports "ClientIP" and "None". 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
-  
-  
 
 - **loadBalancerIP** (string)
 
@@ -163,8 +157,6 @@ ServiceSpec describes the attributes that a user creates on a service.
 - **externalTrafficPolicy** (string)
 
   externalTrafficPolicy describes how nodes distribute service traffic they receive on one of the Service's "externally-facing" addresses (NodePorts, ExternalIPs, and LoadBalancer IPs). If set to "Local", the proxy will configure the service in a way that assumes that external load balancers will take care of balancing the service traffic between nodes, and so each node will deliver traffic only to the node-local endpoints of the service, without masquerading the client source IP. (Traffic mistakenly sent to a node with no endpoints will be dropped.) The default value, "Cluster", uses the standard behavior of routing to all endpoints evenly (possibly modified by topology and other features). Note that traffic sent to an External IP or LoadBalancer IP from within the cluster will always get "Cluster" semantics, but clients sending to a NodePort from within the cluster may need to take traffic policy into account when picking a node.
-  
-  
 
 - **internalTrafficPolicy** (string)
 
@@ -286,8 +278,6 @@ ServiceStatus represents the current status of a service.
       - **loadBalancer.ingress.ports.protocol** (string), required
 
         Protocol is the protocol of the service port of which status is recorded here The supported values are: "TCP", "UDP", "SCTP"
-        
-        
 
       - **loadBalancer.ingress.ports.error** (string)
 
@@ -455,6 +445,11 @@ GET /api/v1/namespaces/{namespace}/services
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -523,6 +518,11 @@ GET /api/v1/services
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -948,6 +948,11 @@ DELETE /api/v1/namespaces/{namespace}/services
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/workload-resources/controller-revision-v1.md b/content/en/docs/reference/kubernetes-api/workload-resources/controller-revision-v1.md
index 5a23855cf25..39a4c73b635 100644
--- a/content/en/docs/reference/kubernetes-api/workload-resources/controller-revision-v1.md
+++ b/content/en/docs/reference/kubernetes-api/workload-resources/controller-revision-v1.md
@@ -216,6 +216,11 @@ GET /apis/apps/v1/namespaces/{namespace}/controllerrevisions
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -284,6 +289,11 @@ GET /apis/apps/v1/controllerrevisions
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -594,6 +604,11 @@ DELETE /apis/apps/v1/namespaces/{namespace}/controllerrevisions
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/workload-resources/cron-job-v1.md b/content/en/docs/reference/kubernetes-api/workload-resources/cron-job-v1.md
index 9148da431f4..8222897d123 100644
--- a/content/en/docs/reference/kubernetes-api/workload-resources/cron-job-v1.md
+++ b/content/en/docs/reference/kubernetes-api/workload-resources/cron-job-v1.md
@@ -81,13 +81,13 @@ CronJobSpec describes how the job execution will look like and when it will actu
 
 - **timeZone** (string)
 
-  The time zone name for the given schedule, see https://en.wikipedia.org/wiki/List_of_tz_database_time_zones. If not specified, this will default to the time zone of the kube-controller-manager process. The set of valid time zone names and the time zone offset is loaded from the system-wide time zone database by the API server during CronJob validation and the controller manager during execution. If no system-wide time zone database can be found a bundled version of the database is used instead. If the time zone name becomes invalid during the lifetime of a CronJob or due to a change in host configuration, the controller will stop creating new new Jobs and will create a system event with the reason UnknownTimeZone. More information can be found in https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#time-zones This is beta field and must be enabled via the `CronJobTimeZone` feature gate.
+  The time zone name for the given schedule, see https://en.wikipedia.org/wiki/List_of_tz_database_time_zones. If not specified, this will default to the time zone of the kube-controller-manager process. The set of valid time zone names and the time zone offset is loaded from the system-wide time zone database by the API server during CronJob validation and the controller manager during execution. If no system-wide time zone database can be found a bundled version of the database is used instead. If the time zone name becomes invalid during the lifetime of a CronJob or due to a change in host configuration, the controller will stop creating new new Jobs and will create a system event with the reason UnknownTimeZone. More information can be found in https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#time-zones
 
 - **concurrencyPolicy** (string)
 
-  Specifies how to treat concurrent executions of a Job. Valid values are: - "Allow" (default): allows CronJobs to run concurrently; - "Forbid": forbids concurrent runs, skipping next run if previous run hasn't finished yet; - "Replace": cancels currently running job and replaces it with a new one
-  
+  Specifies how to treat concurrent executions of a Job. Valid values are:
   
+  - "Allow" (default): allows CronJobs to run concurrently; - "Forbid": forbids concurrent runs, skipping next run if previous run hasn't finished yet; - "Replace": cancels currently running job and replaces it with a new one
 
 - **startingDeadlineSeconds** (int64)
 
@@ -294,6 +294,11 @@ GET /apis/batch/v1/namespaces/{namespace}/cronjobs
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -362,6 +367,11 @@ GET /apis/batch/v1/cronjobs
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -787,6 +797,11 @@ DELETE /apis/batch/v1/namespaces/{namespace}/cronjobs
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/workload-resources/daemon-set-v1.md b/content/en/docs/reference/kubernetes-api/workload-resources/daemon-set-v1.md
index 6176734a8bb..923e9074f05 100644
--- a/content/en/docs/reference/kubernetes-api/workload-resources/daemon-set-v1.md
+++ b/content/en/docs/reference/kubernetes-api/workload-resources/daemon-set-v1.md
@@ -66,7 +66,7 @@ DaemonSetSpec is the specification of a daemon set.
 
 - **template** (<a href="{{< ref "../workload-resources/pod-template-v1#PodTemplateSpec" >}}">PodTemplateSpec</a>), required
 
-  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'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
+  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's node selector (or on every node if no node selector is specified). The only allowed template.spec.restartPolicy value is "Always". More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template
 
 - **minReadySeconds** (int32)
 
@@ -82,8 +82,6 @@ DaemonSetSpec is the specification of a daemon set.
   - **updateStrategy.type** (string)
 
     Type of daemon set update. Can be "RollingUpdate" or "OnDelete". Default is RollingUpdate.
-    
-    
 
   - **updateStrategy.rollingUpdate** (RollingUpdateDaemonSet)
 
@@ -347,6 +345,11 @@ GET /apis/apps/v1/namespaces/{namespace}/daemonsets
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -415,6 +418,11 @@ GET /apis/apps/v1/daemonsets
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -840,6 +848,11 @@ DELETE /apis/apps/v1/namespaces/{namespace}/daemonsets
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/workload-resources/deployment-v1.md b/content/en/docs/reference/kubernetes-api/workload-resources/deployment-v1.md
index 1a409e11e7d..3ea68446fe0 100644
--- a/content/en/docs/reference/kubernetes-api/workload-resources/deployment-v1.md
+++ b/content/en/docs/reference/kubernetes-api/workload-resources/deployment-v1.md
@@ -66,7 +66,7 @@ DeploymentSpec is the specification of the desired behavior of the Deployment.
 
 - **template** (<a href="{{< ref "../workload-resources/pod-template-v1#PodTemplateSpec" >}}">PodTemplateSpec</a>), required
 
-  Template describes the pods that will be created.
+  Template describes the pods that will be created. The only allowed template.spec.restartPolicy value is "Always".
 
 - **replicas** (int32)
 
@@ -88,8 +88,6 @@ DeploymentSpec is the specification of the desired behavior of the Deployment.
   - **strategy.type** (string)
 
     Type of deployment. Can be "Recreate" or "RollingUpdate". Default is RollingUpdate.
-    
-    
 
   - **strategy.rollingUpdate** (RollingUpdateDeployment)
 
@@ -360,6 +358,11 @@ GET /apis/apps/v1/namespaces/{namespace}/deployments
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -428,6 +431,11 @@ GET /apis/apps/v1/deployments
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -853,6 +861,11 @@ DELETE /apis/apps/v1/namespaces/{namespace}/deployments
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/workload-resources/horizontal-pod-autoscaler-v1.md b/content/en/docs/reference/kubernetes-api/workload-resources/horizontal-pod-autoscaler-v1.md
index b815969cfc1..699719e21f0 100644
--- a/content/en/docs/reference/kubernetes-api/workload-resources/horizontal-pod-autoscaler-v1.md
+++ b/content/en/docs/reference/kubernetes-api/workload-resources/horizontal-pod-autoscaler-v1.md
@@ -44,11 +44,11 @@ configuration of a horizontal pod autoscaler.
 
 - **spec** (<a href="{{< ref "../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscalerSpec" >}}">HorizontalPodAutoscalerSpec</a>)
 
-  behaviour of autoscaler. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status.
+  spec defines the behaviour of autoscaler. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status.
 
 - **status** (<a href="{{< ref "../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscalerStatus" >}}">HorizontalPodAutoscalerStatus</a>)
 
-  current information about the autoscaler.
+  status is the current information about the autoscaler.
 
 
 
@@ -62,7 +62,7 @@ specification of a horizontal pod autoscaler.
 
 - **maxReplicas** (int32), required
 
-  upper limit for the number of pods that can be set by the autoscaler; cannot be smaller than MinReplicas.
+  maxReplicas is the upper limit for the number of pods that can be set by the autoscaler; cannot be smaller than MinReplicas.
 
 - **scaleTargetRef** (CrossVersionObjectReference), required
 
@@ -73,15 +73,15 @@ specification of a horizontal pod autoscaler.
 
   - **scaleTargetRef.kind** (string), required
 
-    Kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
+    kind is the kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
 
   - **scaleTargetRef.name** (string), required
 
-    Name of the referent; More info: http://kubernetes.io/docs/user-guide/identifiers#names
+    name is the name of the referent; More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names
 
   - **scaleTargetRef.apiVersion** (string)
 
-    API version of the referent
+    apiVersion is the API version of the referent
 
 - **minReplicas** (int32)
 
@@ -89,7 +89,7 @@ specification of a horizontal pod autoscaler.
 
 - **targetCPUUtilizationPercentage** (int32)
 
-  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.
+  targetCPUUtilizationPercentage is the 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.
 
 
 
@@ -103,26 +103,26 @@ current status of a horizontal pod autoscaler
 
 - **currentReplicas** (int32), required
 
-  current number of replicas of pods managed by this autoscaler.
+  currentReplicas is the current number of replicas of pods managed by this autoscaler.
 
 - **desiredReplicas** (int32), required
 
-  desired number of replicas of pods managed by this autoscaler.
+  desiredReplicas is the  desired number of replicas of pods managed by this autoscaler.
 
 - **currentCPUUtilizationPercentage** (int32)
 
-  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.
+  currentCPUUtilizationPercentage is the 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.
 
 - **lastScaleTime** (Time)
 
-  last time the HorizontalPodAutoscaler scaled the number of pods; used by the autoscaler to control how often the number of pods is changed.
+  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.
 
   <a name="Time"></a>
   *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.*
 
 - **observedGeneration** (int64)
 
-  most recent generation observed by this autoscaler.
+  observedGeneration is the most recent generation observed by this autoscaler.
 
 
 
@@ -146,7 +146,7 @@ list of horizontal pod autoscaler objects.
 
 - **items** ([]<a href="{{< ref "../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler" >}}">HorizontalPodAutoscaler</a>), required
 
-  list of horizontal pod autoscaler objects.
+  items is the list of horizontal pod autoscaler objects.
 
 
 
@@ -283,6 +283,11 @@ GET /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -351,6 +356,11 @@ GET /apis/autoscaling/v1/horizontalpodautoscalers
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -776,6 +786,11 @@ DELETE /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/workload-resources/horizontal-pod-autoscaler-v2.md b/content/en/docs/reference/kubernetes-api/workload-resources/horizontal-pod-autoscaler-v2.md
index 16f7b34bd1f..9c0a6c50965 100644
--- a/content/en/docs/reference/kubernetes-api/workload-resources/horizontal-pod-autoscaler-v2.md
+++ b/content/en/docs/reference/kubernetes-api/workload-resources/horizontal-pod-autoscaler-v2.md
@@ -73,15 +73,15 @@ HorizontalPodAutoscalerSpec describes the desired functionality of the Horizonta
 
   - **scaleTargetRef.kind** (string), required
 
-    Kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
+    kind is the kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
 
   - **scaleTargetRef.name** (string), required
 
-    Name of the referent; More info: http://kubernetes.io/docs/user-guide/identifiers#names
+    name is the name of the referent; More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names
 
   - **scaleTargetRef.apiVersion** (string)
 
-    API version of the referent
+    apiVersion is the API version of the referent
 
 - **minReplicas** (int32)
 
@@ -112,15 +112,15 @@ HorizontalPodAutoscalerSpec describes the desired functionality of the Horizonta
 
       - **behavior.scaleDown.policies.type** (string), required
 
-        Type is used to specify the scaling policy.
+        type is used to specify the scaling policy.
 
       - **behavior.scaleDown.policies.value** (int32), required
 
-        Value contains the amount of change which is permitted by the policy. It must be greater than zero
+        value contains the amount of change which is permitted by the policy. It must be greater than zero
 
       - **behavior.scaleDown.policies.periodSeconds** (int32), required
 
-        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).
+        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).
 
     - **behavior.scaleDown.selectPolicy** (string)
 
@@ -128,7 +128,7 @@ HorizontalPodAutoscalerSpec describes the desired functionality of the Horizonta
 
     - **behavior.scaleDown.stabilizationWindowSeconds** (int32)
 
-      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).
+      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).
 
   - **behavior.scaleUp** (HPAScalingRules)
 
@@ -151,15 +151,15 @@ HorizontalPodAutoscalerSpec describes the desired functionality of the Horizonta
 
       - **behavior.scaleUp.policies.type** (string), required
 
-        Type is used to specify the scaling policy.
+        type is used to specify the scaling policy.
 
       - **behavior.scaleUp.policies.value** (int32), required
 
-        Value contains the amount of change which is permitted by the policy. It must be greater than zero
+        value contains the amount of change which is permitted by the policy. It must be greater than zero
 
       - **behavior.scaleUp.policies.periodSeconds** (int32), required
 
-        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).
+        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).
 
     - **behavior.scaleUp.selectPolicy** (string)
 
@@ -167,7 +167,7 @@ HorizontalPodAutoscalerSpec describes the desired functionality of the Horizonta
 
     - **behavior.scaleUp.stabilizationWindowSeconds** (int32)
 
-      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).
+      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).
 
 - **metrics** ([]MetricSpec)
 
@@ -281,15 +281,15 @@ HorizontalPodAutoscalerSpec describes the desired functionality of the Horizonta
 
       - **metrics.object.describedObject.kind** (string), required
 
-        Kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
+        kind is the kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
 
       - **metrics.object.describedObject.name** (string), required
 
-        Name of the referent; More info: http://kubernetes.io/docs/user-guide/identifiers#names
+        name is the name of the referent; More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names
 
       - **metrics.object.describedObject.apiVersion** (string)
 
-        API version of the referent
+        apiVersion is the API version of the referent
 
     - **metrics.object.metric** (MetricIdentifier), required
 
@@ -478,7 +478,7 @@ HorizontalPodAutoscalerStatus describes the current status of a horizontal pod a
 
     - **currentMetrics.containerResource.container** (string), required
 
-      Container is the name of the container in the pods of the scaling target
+      container is the name of the container in the pods of the scaling target
 
     - **currentMetrics.containerResource.current** (MetricValueStatus), required
 
@@ -501,7 +501,7 @@ HorizontalPodAutoscalerStatus describes the current status of a horizontal pod a
 
     - **currentMetrics.containerResource.name** (string), required
 
-      Name is the name of the resource in question.
+      name is the name of the resource in question.
 
   - **currentMetrics.external** (ExternalMetricStatus)
 
@@ -579,15 +579,15 @@ HorizontalPodAutoscalerStatus describes the current status of a horizontal pod a
 
       - **currentMetrics.object.describedObject.kind** (string), required
 
-        Kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
+        kind is the kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
 
       - **currentMetrics.object.describedObject.name** (string), required
 
-        Name of the referent; More info: http://kubernetes.io/docs/user-guide/identifiers#names
+        name is the name of the referent; More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names
 
       - **currentMetrics.object.describedObject.apiVersion** (string)
 
-        API version of the referent
+        apiVersion is the API version of the referent
 
     - **currentMetrics.object.metric** (MetricIdentifier), required
 
@@ -673,7 +673,7 @@ HorizontalPodAutoscalerStatus describes the current status of a horizontal pod a
 
     - **currentMetrics.resource.name** (string), required
 
-      Name is the name of the resource in question.
+      name is the name of the resource in question.
 
 - **currentReplicas** (int32)
 
@@ -849,6 +849,11 @@ GET /apis/autoscaling/v2/namespaces/{namespace}/horizontalpodautoscalers
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -917,6 +922,11 @@ GET /apis/autoscaling/v2/horizontalpodautoscalers
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -1342,6 +1352,11 @@ DELETE /apis/autoscaling/v2/namespaces/{namespace}/horizontalpodautoscalers
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/workload-resources/job-v1.md b/content/en/docs/reference/kubernetes-api/workload-resources/job-v1.md
index 42cec53db7c..00790c4af0a 100644
--- a/content/en/docs/reference/kubernetes-api/workload-resources/job-v1.md
+++ b/content/en/docs/reference/kubernetes-api/workload-resources/job-v1.md
@@ -67,7 +67,7 @@ JobSpec describes how the job execution will look like.
 
 - **template** (<a href="{{< ref "../workload-resources/pod-template-v1#PodTemplateSpec" >}}">PodTemplateSpec</a>), required
 
-  Describes the pod that will be created when executing a job. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
+  Describes the pod that will be created when executing a job. The only allowed template.spec.restartPolicy values are "Never" or "OnFailure". More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
 
 - **parallelism** (int32)
 
@@ -78,11 +78,11 @@ JobSpec describes how the job execution will look like.
 
 - **completions** (int32)
 
-  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/
+  Specifies the desired number of successfully finished pods the job should be run with.  Setting to null 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/
 
 - **completionMode** (string)
 
-  CompletionMode specifies how Pod completions are tracked. It can be `NonIndexed` (default) or `Indexed`.
+  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.
   
@@ -104,7 +104,7 @@ JobSpec describes how the job execution will look like.
 
 - **suspend** (boolean)
 
-  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.
+  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.
 
 ### Selector
 
@@ -136,11 +136,12 @@ JobSpec describes how the job execution will look like.
     A list of pod failure policy rules. The rules are evaluated in order. Once a rule matches a Pod failure, the remaining of the rules are ignored. When no rule matches the Pod failure, the default handling applies - the counter of pod failures is incremented and it is checked against the backoffLimit. At most 20 elements are allowed.
 
     <a name="PodFailurePolicyRule"></a>
-    *PodFailurePolicyRule describes how a pod failure is handled when the requirements are met. One of OnExitCodes and onPodConditions, but not both, can be used in each rule.*
+    *PodFailurePolicyRule describes how a pod failure is handled when the requirements are met. One of onExitCodes and onPodConditions, but not both, can be used in each rule.*
 
     - **podFailurePolicy.rules.action** (string), required
 
       Specifies the action taken on a pod failure when the requirements are satisfied. Possible values are:
+      
       - FailJob: indicates that the pod's job is marked as Failed and all
         running pods are terminated.
       - Ignore: indicates that the counter towards the .backoffLimit is not
@@ -148,8 +149,6 @@ JobSpec describes how the job execution will look like.
       - Count: indicates that the pod is handled in the default way - the
         counter towards the .backoffLimit is incremented.
       Additional values are considered to be added in the future. Clients should react to an unknown action by skipping the rule.
-      
-      
 
     - **podFailurePolicy.rules.onPodConditions** ([]PodFailurePolicyOnPodConditionsPattern), required
 
@@ -178,6 +177,7 @@ JobSpec describes how the job execution will look like.
       - **podFailurePolicy.rules.onExitCodes.operator** (string), required
 
         Represents the relationship between the container exit code(s) and the specified values. Containers completed with success (exit code 0) are excluded from the requirement check. Possible values are:
+        
         - In: the requirement is satisfied if at least one container exit code
           (might be multiple if there are multiple containers not restricted
           by the 'containerName' field) is in the set of specified values.
@@ -185,8 +185,6 @@ JobSpec describes how the job execution will look like.
           (might be multiple if there are multiple containers not restricted
           by the 'containerName' field) is not in the set of specified values.
         Additional values are considered to be added in the future. Clients should react to an unknown operator by assuming the requirement is not satisfied.
-        
-        
 
       - **podFailurePolicy.rules.onExitCodes.values** ([]int32), required
 
@@ -234,7 +232,7 @@ JobStatus represents the current state of a Job.
 
 - **completedIndexes** (string)
 
-  CompletedIndexes holds the completed indexes when .spec.completionMode = "Indexed" 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 "1,3-5,7".
+  completedIndexes holds the completed indexes when .spec.completionMode = "Indexed" 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 "1,3-5,7".
 
 - **conditions** ([]JobCondition)
 
@@ -279,9 +277,11 @@ JobStatus represents the current state of a Job.
 
 - **uncountedTerminatedPods** (UncountedTerminatedPods)
 
-  UncountedTerminatedPods holds the UIDs of Pods that have terminated but the job controller hasn't yet accounted for in the status counters.
+  uncountedTerminatedPods holds the UIDs of Pods that have terminated but the job controller hasn'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
+  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.
   
   Old jobs might not be tracked using this field, in which case the field remains null.
@@ -293,13 +293,13 @@ JobStatus represents the current state of a Job.
 
     *Set: unique values will be kept during a merge*
     
-    Failed holds UIDs of failed Pods.
+    failed holds UIDs of failed Pods.
 
   - **uncountedTerminatedPods.succeeded** ([]string)
 
     *Set: unique values will be kept during a merge*
     
-    Succeeded holds UIDs of succeeded Pods.
+    succeeded holds UIDs of succeeded Pods.
 
 
 
@@ -469,6 +469,11 @@ GET /apis/batch/v1/namespaces/{namespace}/jobs
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -537,6 +542,11 @@ GET /apis/batch/v1/jobs
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -962,6 +972,11 @@ DELETE /apis/batch/v1/namespaces/{namespace}/jobs
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/workload-resources/pod-scheduling-v1alpha1.md b/content/en/docs/reference/kubernetes-api/workload-resources/pod-scheduling-context-v1alpha2.md
similarity index 69%
rename from content/en/docs/reference/kubernetes-api/workload-resources/pod-scheduling-v1alpha1.md
rename to content/en/docs/reference/kubernetes-api/workload-resources/pod-scheduling-context-v1alpha2.md
index 72a2196d523..bb6c08f3ceb 100644
--- a/content/en/docs/reference/kubernetes-api/workload-resources/pod-scheduling-v1alpha1.md
+++ b/content/en/docs/reference/kubernetes-api/workload-resources/pod-scheduling-context-v1alpha2.md
@@ -1,11 +1,11 @@
 ---
 api_metadata:
-  apiVersion: "resource.k8s.io/v1alpha1"
-  import: "k8s.io/api/resource/v1alpha1"
-  kind: "PodScheduling"
+  apiVersion: "resource.k8s.io/v1alpha2"
+  import: "k8s.io/api/resource/v1alpha2"
+  kind: "PodSchedulingContext"
 content_type: "api_reference"
-description: "PodScheduling objects hold information that is needed to schedule a Pod with ResourceClaims that use \"WaitForFirstConsumer\" allocation mode."
-title: "PodScheduling v1alpha1"
+description: "PodSchedulingContext objects hold information that is needed to schedule a Pod with ResourceClaims that use \"WaitForFirstConsumer\" allocation mode."
+title: "PodSchedulingContext v1alpha2"
 weight: 14
 auto_generated: true
 ---
@@ -21,34 +21,34 @@ guide. You can file document formatting bugs against the
 [reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
 -->
 
-`apiVersion: resource.k8s.io/v1alpha1`
+`apiVersion: resource.k8s.io/v1alpha2`
 
-`import "k8s.io/api/resource/v1alpha1"`
+`import "k8s.io/api/resource/v1alpha2"`
 
 
-## PodScheduling {#PodScheduling}
+## PodSchedulingContext {#PodSchedulingContext}
 
-PodScheduling objects hold information that is needed to schedule a Pod with ResourceClaims that use "WaitForFirstConsumer" allocation mode.
+PodSchedulingContext objects hold information that is needed to schedule a Pod with ResourceClaims that use "WaitForFirstConsumer" allocation mode.
 
 This is an alpha type and requires enabling the DynamicResourceAllocation feature gate.
 
 <hr>
 
-- **apiVersion**: resource.k8s.io/v1alpha1
+- **apiVersion**: resource.k8s.io/v1alpha2
 
 
-- **kind**: PodScheduling
+- **kind**: PodSchedulingContext
 
 
 - **metadata** (<a href="{{< ref "../common-definitions/object-meta#ObjectMeta" >}}">ObjectMeta</a>)
 
   Standard object metadata
 
-- **spec** (<a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodSchedulingSpec" >}}">PodSchedulingSpec</a>), required
+- **spec** (<a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContextSpec" >}}">PodSchedulingContextSpec</a>), required
 
   Spec describes where resources for the Pod are needed.
 
-- **status** (<a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodSchedulingStatus" >}}">PodSchedulingStatus</a>)
+- **status** (<a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContextStatus" >}}">PodSchedulingContextStatus</a>)
 
   Status describes where resources for the Pod can be allocated.
 
@@ -56,9 +56,9 @@ This is an alpha type and requires enabling the DynamicResourceAllocation featur
 
 
 
-## PodSchedulingSpec {#PodSchedulingSpec}
+## PodSchedulingContextSpec {#PodSchedulingContextSpec}
 
-PodSchedulingSpec describes where resources for the Pod are needed.
+PodSchedulingContextSpec describes where resources for the Pod are needed.
 
 <hr>
 
@@ -78,9 +78,9 @@ PodSchedulingSpec describes where resources for the Pod are needed.
 
 
 
-## PodSchedulingStatus {#PodSchedulingStatus}
+## PodSchedulingContextStatus {#PodSchedulingContextStatus}
 
-PodSchedulingStatus describes where resources for the Pod can be allocated.
+PodSchedulingContextStatus describes where resources for the Pod can be allocated.
 
 <hr>
 
@@ -109,25 +109,25 @@ PodSchedulingStatus describes where resources for the Pod can be allocated.
 
 
 
-## PodSchedulingList {#PodSchedulingList}
+## PodSchedulingContextList {#PodSchedulingContextList}
 
-PodSchedulingList is a collection of Pod scheduling objects.
+PodSchedulingContextList is a collection of Pod scheduling objects.
 
 <hr>
 
-- **apiVersion**: resource.k8s.io/v1alpha1
+- **apiVersion**: resource.k8s.io/v1alpha2
 
 
-- **kind**: PodSchedulingList
+- **kind**: PodSchedulingContextList
 
 
 - **metadata** (<a href="{{< ref "../common-definitions/list-meta#ListMeta" >}}">ListMeta</a>)
 
   Standard list metadata
 
-- **items** ([]<a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodScheduling" >}}">PodScheduling</a>), required
+- **items** ([]<a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContext" >}}">PodSchedulingContext</a>), required
 
-  Items is the list of PodScheduling objects.
+  Items is the list of PodSchedulingContext objects.
 
 
 
@@ -144,18 +144,18 @@ PodSchedulingList is a collection of Pod scheduling objects.
 
 
 
-### `get` read the specified PodScheduling
+### `get` read the specified PodSchedulingContext
 
 #### HTTP Request
 
-GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings/{name}
+GET /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts/{name}
 
 #### Parameters
 
 
 - **name** (*in path*): string, required
 
-  name of the PodScheduling
+  name of the PodSchedulingContext
 
 
 - **namespace** (*in path*): string, required
@@ -172,23 +172,23 @@ GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings/{name}
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodScheduling" >}}">PodScheduling</a>): OK
+200 (<a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContext" >}}">PodSchedulingContext</a>): OK
 
 401: Unauthorized
 
 
-### `get` read status of the specified PodScheduling
+### `get` read status of the specified PodSchedulingContext
 
 #### HTTP Request
 
-GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings/{name}/status
+GET /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts/{name}/status
 
 #### Parameters
 
 
 - **name** (*in path*): string, required
 
-  name of the PodScheduling
+  name of the PodSchedulingContext
 
 
 - **namespace** (*in path*): string, required
@@ -205,16 +205,16 @@ GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings/{name}/
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodScheduling" >}}">PodScheduling</a>): OK
+200 (<a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContext" >}}">PodSchedulingContext</a>): OK
 
 401: Unauthorized
 
 
-### `list` list or watch objects of kind PodScheduling
+### `list` list or watch objects of kind PodSchedulingContext
 
 #### HTTP Request
 
-GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings
+GET /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts
 
 #### Parameters
 
@@ -264,6 +264,11 @@ GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -278,16 +283,16 @@ GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodSchedulingList" >}}">PodSchedulingList</a>): OK
+200 (<a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContextList" >}}">PodSchedulingContextList</a>): OK
 
 401: Unauthorized
 
 
-### `list` list or watch objects of kind PodScheduling
+### `list` list or watch objects of kind PodSchedulingContext
 
 #### HTTP Request
 
-GET /apis/resource.k8s.io/v1alpha1/podschedulings
+GET /apis/resource.k8s.io/v1alpha2/podschedulingcontexts
 
 #### Parameters
 
@@ -332,6 +337,11 @@ GET /apis/resource.k8s.io/v1alpha1/podschedulings
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -346,16 +356,16 @@ GET /apis/resource.k8s.io/v1alpha1/podschedulings
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodSchedulingList" >}}">PodSchedulingList</a>): OK
+200 (<a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContextList" >}}">PodSchedulingContextList</a>): OK
 
 401: Unauthorized
 
 
-### `create` create a PodScheduling
+### `create` create a PodSchedulingContext
 
 #### HTTP Request
 
-POST /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings
+POST /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts
 
 #### Parameters
 
@@ -365,7 +375,7 @@ POST /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings
   <a href="{{< ref "../common-parameters/common-parameters#namespace" >}}">namespace</a>
 
 
-- **body**: <a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodScheduling" >}}">PodScheduling</a>, required
+- **body**: <a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContext" >}}">PodSchedulingContext</a>, required
 
   
 
@@ -394,27 +404,27 @@ POST /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodScheduling" >}}">PodScheduling</a>): OK
+200 (<a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContext" >}}">PodSchedulingContext</a>): OK
 
-201 (<a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodScheduling" >}}">PodScheduling</a>): Created
+201 (<a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContext" >}}">PodSchedulingContext</a>): Created
 
-202 (<a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodScheduling" >}}">PodScheduling</a>): Accepted
+202 (<a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContext" >}}">PodSchedulingContext</a>): Accepted
 
 401: Unauthorized
 
 
-### `update` replace the specified PodScheduling
+### `update` replace the specified PodSchedulingContext
 
 #### HTTP Request
 
-PUT /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings/{name}
+PUT /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts/{name}
 
 #### Parameters
 
 
 - **name** (*in path*): string, required
 
-  name of the PodScheduling
+  name of the PodSchedulingContext
 
 
 - **namespace** (*in path*): string, required
@@ -422,7 +432,7 @@ PUT /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings/{name}
   <a href="{{< ref "../common-parameters/common-parameters#namespace" >}}">namespace</a>
 
 
-- **body**: <a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodScheduling" >}}">PodScheduling</a>, required
+- **body**: <a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContext" >}}">PodSchedulingContext</a>, required
 
   
 
@@ -451,25 +461,25 @@ PUT /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings/{name}
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodScheduling" >}}">PodScheduling</a>): OK
+200 (<a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContext" >}}">PodSchedulingContext</a>): OK
 
-201 (<a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodScheduling" >}}">PodScheduling</a>): Created
+201 (<a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContext" >}}">PodSchedulingContext</a>): Created
 
 401: Unauthorized
 
 
-### `update` replace status of the specified PodScheduling
+### `update` replace status of the specified PodSchedulingContext
 
 #### HTTP Request
 
-PUT /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings/{name}/status
+PUT /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts/{name}/status
 
 #### Parameters
 
 
 - **name** (*in path*): string, required
 
-  name of the PodScheduling
+  name of the PodSchedulingContext
 
 
 - **namespace** (*in path*): string, required
@@ -477,7 +487,7 @@ PUT /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings/{name}/
   <a href="{{< ref "../common-parameters/common-parameters#namespace" >}}">namespace</a>
 
 
-- **body**: <a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodScheduling" >}}">PodScheduling</a>, required
+- **body**: <a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContext" >}}">PodSchedulingContext</a>, required
 
   
 
@@ -506,25 +516,25 @@ PUT /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings/{name}/
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodScheduling" >}}">PodScheduling</a>): OK
+200 (<a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContext" >}}">PodSchedulingContext</a>): OK
 
-201 (<a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodScheduling" >}}">PodScheduling</a>): Created
+201 (<a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContext" >}}">PodSchedulingContext</a>): Created
 
 401: Unauthorized
 
 
-### `patch` partially update the specified PodScheduling
+### `patch` partially update the specified PodSchedulingContext
 
 #### HTTP Request
 
-PATCH /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings/{name}
+PATCH /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts/{name}
 
 #### Parameters
 
 
 - **name** (*in path*): string, required
 
-  name of the PodScheduling
+  name of the PodSchedulingContext
 
 
 - **namespace** (*in path*): string, required
@@ -566,25 +576,25 @@ PATCH /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings/{name
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodScheduling" >}}">PodScheduling</a>): OK
+200 (<a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContext" >}}">PodSchedulingContext</a>): OK
 
-201 (<a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodScheduling" >}}">PodScheduling</a>): Created
+201 (<a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContext" >}}">PodSchedulingContext</a>): Created
 
 401: Unauthorized
 
 
-### `patch` partially update status of the specified PodScheduling
+### `patch` partially update status of the specified PodSchedulingContext
 
 #### HTTP Request
 
-PATCH /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings/{name}/status
+PATCH /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts/{name}/status
 
 #### Parameters
 
 
 - **name** (*in path*): string, required
 
-  name of the PodScheduling
+  name of the PodSchedulingContext
 
 
 - **namespace** (*in path*): string, required
@@ -626,25 +636,25 @@ PATCH /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings/{name
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodScheduling" >}}">PodScheduling</a>): OK
+200 (<a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContext" >}}">PodSchedulingContext</a>): OK
 
-201 (<a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodScheduling" >}}">PodScheduling</a>): Created
+201 (<a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContext" >}}">PodSchedulingContext</a>): Created
 
 401: Unauthorized
 
 
-### `delete` delete a PodScheduling
+### `delete` delete a PodSchedulingContext
 
 #### HTTP Request
 
-DELETE /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings/{name}
+DELETE /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts/{name}
 
 #### Parameters
 
 
 - **name** (*in path*): string, required
 
-  name of the PodScheduling
+  name of the PodSchedulingContext
 
 
 - **namespace** (*in path*): string, required
@@ -681,18 +691,18 @@ DELETE /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings/{nam
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodScheduling" >}}">PodScheduling</a>): OK
+200 (<a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContext" >}}">PodSchedulingContext</a>): OK
 
-202 (<a href="{{< ref "../workload-resources/pod-scheduling-v1alpha1#PodScheduling" >}}">PodScheduling</a>): Accepted
+202 (<a href="{{< ref "../workload-resources/pod-scheduling-context-v1alpha2#PodSchedulingContext" >}}">PodSchedulingContext</a>): Accepted
 
 401: Unauthorized
 
 
-### `deletecollection` delete collection of PodScheduling
+### `deletecollection` delete collection of PodSchedulingContext
 
 #### HTTP Request
 
-DELETE /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings
+DELETE /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts
 
 #### Parameters
 
@@ -757,6 +767,11 @@ DELETE /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/podschedulings
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/workload-resources/pod-template-v1.md b/content/en/docs/reference/kubernetes-api/workload-resources/pod-template-v1.md
index 8d2737ee735..b8a028e890a 100644
--- a/content/en/docs/reference/kubernetes-api/workload-resources/pod-template-v1.md
+++ b/content/en/docs/reference/kubernetes-api/workload-resources/pod-template-v1.md
@@ -190,6 +190,11 @@ GET /api/v1/namespaces/{namespace}/podtemplates
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -258,6 +263,11 @@ GET /api/v1/podtemplates
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -568,6 +578,11 @@ DELETE /api/v1/namespaces/{namespace}/podtemplates
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/workload-resources/pod-v1.md b/content/en/docs/reference/kubernetes-api/workload-resources/pod-v1.md
index 3b4dbd6ef84..16813f69737 100644
--- a/content/en/docs/reference/kubernetes-api/workload-resources/pod-v1.md
+++ b/content/en/docs/reference/kubernetes-api/workload-resources/pod-v1.md
@@ -161,8 +161,6 @@ PodSpec is a description of a pod.
   - **tolerations.operator** (string)
 
     Operator represents a key'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.
-    
-    
 
   - **tolerations.value** (string)
 
@@ -171,8 +169,6 @@ PodSpec is a description of a pod.
   - **tolerations.effect** (string)
 
     Effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.
-    
-    
 
   - **tolerations.tolerationSeconds** (int64)
 
@@ -219,15 +215,10 @@ PodSpec is a description of a pod.
 
   - **topologySpreadConstraints.whenUnsatisfiable** (string), required
 
-    WhenUnsatisfiable indicates how to deal with a pod if it doesn'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,
+    WhenUnsatisfiable indicates how to deal with a pod if it doesn'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 "Unsatisfiable" for an incoming pod if and only if every possible node assignment for that pod would violate "MaxSkew" 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't make it *more* imbalanced. It's a required field.
-    
-    
 
   - **topologySpreadConstraints.labelSelector** (<a href="{{< ref "../common-definitions/label-selector#LabelSelector" >}}">LabelSelector</a>)
 
@@ -237,7 +228,9 @@ PodSpec is a description of a pod.
 
     *Atomic: will be replaced during a merge*
     
-    MatchLabelKeys is a set of pod label keys to select the pods over which spreading will be calculated. The keys are used to lookup values from the incoming pod labels, those key-value labels are ANDed with labelSelector to select the group of existing pods over which spreading will be calculated for the incoming pod. Keys that don't exist in the incoming pod labels will be ignored. A null or empty list means only match against labelSelector.
+    MatchLabelKeys is a set of pod label keys to select the pods over which spreading will be calculated. The keys are used to lookup values from the incoming pod labels, those key-value labels are ANDed with labelSelector to select the group of existing pods over which spreading will be calculated for the incoming pod. The same key is forbidden to exist in both MatchLabelKeys and LabelSelector. MatchLabelKeys cannot be set when LabelSelector isn't set. Keys that don't exist in the incoming pod labels will be ignored. A null or empty list means only match against labelSelector.
+    
+    This is a beta field and requires the MatchLabelKeysInPodTopologySpread feature gate to be enabled (enabled by default).
 
   - **topologySpreadConstraints.minDomains** (int32)
 
@@ -268,9 +261,7 @@ PodSpec is a description of a pod.
 
 - **restartPolicy** (string)
 
-  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
-  
-  
+  Restart policy for all containers within the pod. One of Always, OnFailure, Never. In some contexts, only a subset of those values may be permitted. Default to Always. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy
 
 - **terminationGracePeriodSeconds** (int64)
 
@@ -355,8 +346,6 @@ PodSpec is a description of a pod.
 - **dnsPolicy** (string)
 
   Set DNS policy for the pod. Defaults to "ClusterFirst". Valid values are 'ClusterFirstWithHostNet', 'ClusterFirst', 'Default' or 'None'. 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 'ClusterFirstWithHostNet'.
-  
-  
 
 ### Hosts namespaces
 
@@ -438,8 +427,6 @@ PodSpec is a description of a pod.
       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.
-      
-      
 
     - **securityContext.seccompProfile.localhostProfile** (string)
 
@@ -561,9 +548,11 @@ PodSpec is a description of a pod.
   
   *Map: unique values on key name will be kept during a merge*
   
-  SchedulingGates is an opaque list of values that if specified will block scheduling the pod. More info:  https://git.k8s.io/enhancements/keps/sig-scheduling/3521-pod-scheduling-readiness.
+  SchedulingGates is an opaque list of values that if specified will block scheduling the pod. If schedulingGates is not empty, the pod will stay in the SchedulingGated state and the scheduler will not attempt to schedule the pod.
   
-  This is an alpha-level feature enabled by PodSchedulingReadiness feature gate.
+  SchedulingGates can only be set at pod creation time, and be removed only afterwards.
+  
+  This is a beta feature enabled by the PodSchedulingReadiness feature gate.
 
   <a name="PodSchedulingGate"></a>
   *PodSchedulingGate is associated to a Pod to guard its scheduling.*
@@ -603,8 +592,6 @@ A single application container that you want to run within a pod.
 - **imagePullPolicy** (string)
 
   Image pull policy. One of Always, Never, IfNotPresent. Defaults to Always if :latest tag is specified, or IfNotPresent otherwise. Cannot be updated. More info: https://kubernetes.io/docs/concepts/containers/images#updating-images
-  
-  
 
 ### Entrypoint
 
@@ -654,8 +641,6 @@ A single application container that you want to run within a pod.
   - **ports.protocol** (string)
 
     Protocol for port. Must be UDP, TCP, or SCTP. Defaults to "TCP".
-    
-    
 
 ### Environment variables
 
@@ -840,13 +825,13 @@ A single application container that you want to run within a pod.
 
   - **resources.claims** ([]ResourceClaim)
 
-    *Set: unique values will be kept during a merge*
+    *Map: unique values on key name will be kept during a merge*
     
     Claims lists the names of resources, defined in spec.resourceClaims, that are used by this container.
     
     This is an alpha field and requires enabling the DynamicResourceAllocation feature gate.
     
-    This field is immutable.
+    This field is immutable. It can only be set for containers.
 
     <a name="ResourceClaim"></a>
     *ResourceClaim references one entry in PodSpec.ResourceClaims.*
@@ -861,7 +846,24 @@ A single application container that you want to run within a pod.
 
   - **resources.requests** (map[string]<a href="{{< ref "../common-definitions/quantity#Quantity" >}}">Quantity</a>)
 
-    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/
+    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. Requests cannot exceed Limits. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
+
+- **resizePolicy** ([]ContainerResizePolicy)
+
+  *Atomic: will be replaced during a merge*
+  
+  Resources resize policy for the container.
+
+  <a name="ContainerResizePolicy"></a>
+  *ContainerResizePolicy represents resource resize policy for the container.*
+
+  - **resizePolicy.resourceName** (string), required
+
+    Name of the resource to which this resource resize policy applies. Supported values: cpu, memory.
+
+  - **resizePolicy.restartPolicy** (string), required
+
+    Restart policy to apply when specified resource is resized. If not specified, it defaults to NotRequired.
 
 ### Lifecycle
 
@@ -888,8 +890,6 @@ A single application container that you want to run within a pod.
 - **terminationMessagePolicy** (string)
 
   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.
-  
-  
 
 - **livenessProbe** (<a href="{{< ref "../workload-resources/pod-v1#Probe" >}}">Probe</a>)
 
@@ -968,8 +968,6 @@ A single application container that you want to run within a pod.
       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.
-      
-      
 
     - **securityContext.seccompProfile.localhostProfile** (string)
 
@@ -1068,8 +1066,6 @@ To add an ephemeral container, use the ephemeralcontainers subresource of an exi
 - **imagePullPolicy** (string)
 
   Image pull policy. One of Always, Never, IfNotPresent. Defaults to Always if :latest tag is specified, or IfNotPresent otherwise. Cannot be updated. More info: https://kubernetes.io/docs/concepts/containers/images#updating-images
-  
-  
 
 ### Entrypoint
 
@@ -1257,6 +1253,26 @@ To add an ephemeral container, use the ephemeralcontainers subresource of an exi
 
     name must match the name of a persistentVolumeClaim in the pod
 
+### Resources
+
+
+- **resizePolicy** ([]ContainerResizePolicy)
+
+  *Atomic: will be replaced during a merge*
+  
+  Resources resize policy for the container.
+
+  <a name="ContainerResizePolicy"></a>
+  *ContainerResizePolicy represents resource resize policy for the container.*
+
+  - **resizePolicy.resourceName** (string), required
+
+    Name of the resource to which this resource resize policy applies. Supported values: cpu, memory.
+
+  - **resizePolicy.restartPolicy** (string), required
+
+    Restart policy to apply when specified resource is resized. If not specified, it defaults to NotRequired.
+
 ### Lifecycle
 
 
@@ -1267,8 +1283,6 @@ To add an ephemeral container, use the ephemeralcontainers subresource of an exi
 - **terminationMessagePolicy** (string)
 
   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.
-  
-  
 
 ### Debugging
 
@@ -1350,8 +1364,6 @@ To add an ephemeral container, use the ephemeralcontainers subresource of an exi
       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.
-      
-      
 
     - **securityContext.seccompProfile.localhostProfile** (string)
 
@@ -1436,8 +1448,6 @@ To add an ephemeral container, use the ephemeralcontainers subresource of an exi
   - **ports.protocol** (string)
 
     Protocol for port. Must be UDP, TCP, or SCTP. Defaults to "TCP".
-    
-    
 
 - **resources** (ResourceRequirements)
 
@@ -1448,13 +1458,13 @@ To add an ephemeral container, use the ephemeralcontainers subresource of an exi
 
   - **resources.claims** ([]ResourceClaim)
 
-    *Set: unique values will be kept during a merge*
+    *Map: unique values on key name will be kept during a merge*
     
     Claims lists the names of resources, defined in spec.resourceClaims, that are used by this container.
     
     This is an alpha field and requires enabling the DynamicResourceAllocation feature gate.
     
-    This field is immutable.
+    This field is immutable. It can only be set for containers.
 
     <a name="ResourceClaim"></a>
     *ResourceClaim references one entry in PodSpec.ResourceClaims.*
@@ -1469,7 +1479,7 @@ To add an ephemeral container, use the ephemeralcontainers subresource of an exi
 
   - **resources.requests** (map[string]<a href="{{< ref "../common-definitions/quantity#Quantity" >}}">Quantity</a>)
 
-    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/
+    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. Requests cannot exceed Limits. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
 
 - **lifecycle** (Lifecycle)
 
@@ -1557,8 +1567,6 @@ LifecycleHandler defines a specific action that should be taken in a lifecycle h
   - **httpGet.scheme** (string)
 
     Scheme to use for connecting to the host. Defaults to HTTP.
-    
-    
 
 - **tcpSocket** (TCPSocketAction)
 
@@ -1831,8 +1839,6 @@ Probe describes a health check to be performed against a container to determine
   - **httpGet.scheme** (string)
 
     Scheme to use for connecting to the host. Defaults to HTTP.
-    
-    
 
 - **tcpSocket** (TCPSocketAction)
 
@@ -1878,7 +1884,7 @@ Probe describes a health check to be performed against a container to determine
 
 - **grpc** (GRPCAction)
 
-  GRPC specifies an action involving a GRPC port. This is a beta field and requires enabling GRPCContainerProbe feature gate.
+  GRPC specifies an action involving a GRPC port.
 
   <a name="GRPCAction"></a>
   **
@@ -1925,8 +1931,6 @@ PodStatus represents information about the status of a pod. Status may trail the
   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
-  
-  
 
 - **message** (string)
 
@@ -1996,9 +2000,7 @@ PodStatus represents information about the status of a pod. Status may trail the
 
 - **qosClass** (string)
 
-  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
-  
-  
+  The Quality of Service (QOS) classification assigned to the pod based on resource requirements See PodQOSClass type for available QOS classes More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-qos/#quality-of-service-classes
 
 - **initContainerStatuses** ([]ContainerStatus)
 
@@ -2007,188 +2009,6 @@ PodStatus represents information about the status of a pod. Status may trail the
   <a name="ContainerStatus"></a>
   *ContainerStatus contains details for the current status of this container.*
 
-  - **initContainerStatuses.name** (string), required
-
-    This must be a DNS_LABEL. Each container in a pod must have a unique name. Cannot be updated.
-
-  - **initContainerStatuses.image** (string), required
-
-    The image the container is running. More info: https://kubernetes.io/docs/concepts/containers/images.
-
-  - **initContainerStatuses.imageID** (string), required
-
-    ImageID of the container's image.
-
-  - **initContainerStatuses.containerID** (string)
-
-    Container's ID in the format '\<type>://\<container_id>'.
-
-  - **initContainerStatuses.state** (ContainerState)
-
-    Details about the container's current condition.
-
-    <a name="ContainerState"></a>
-    *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.*
-
-    - **initContainerStatuses.state.running** (ContainerStateRunning)
-
-      Details about a running container
-
-      <a name="ContainerStateRunning"></a>
-      *ContainerStateRunning is a running state of a container.*
-
-      - **initContainerStatuses.state.running.startedAt** (Time)
-
-        Time at which the container was last (re-)started
-
-        <a name="Time"></a>
-        *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.*
-
-    - **initContainerStatuses.state.terminated** (ContainerStateTerminated)
-
-      Details about a terminated container
-
-      <a name="ContainerStateTerminated"></a>
-      *ContainerStateTerminated is a terminated state of a container.*
-
-      - **initContainerStatuses.state.terminated.containerID** (string)
-
-        Container's ID in the format '\<type>://\<container_id>'
-
-      - **initContainerStatuses.state.terminated.exitCode** (int32), required
-
-        Exit status from the last termination of the container
-
-      - **initContainerStatuses.state.terminated.startedAt** (Time)
-
-        Time at which previous execution of the container started
-
-        <a name="Time"></a>
-        *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.*
-
-      - **initContainerStatuses.state.terminated.finishedAt** (Time)
-
-        Time at which the container last terminated
-
-        <a name="Time"></a>
-        *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.*
-
-      - **initContainerStatuses.state.terminated.message** (string)
-
-        Message regarding the last termination of the container
-
-      - **initContainerStatuses.state.terminated.reason** (string)
-
-        (brief) reason from the last termination of the container
-
-      - **initContainerStatuses.state.terminated.signal** (int32)
-
-        Signal from the last termination of the container
-
-    - **initContainerStatuses.state.waiting** (ContainerStateWaiting)
-
-      Details about a waiting container
-
-      <a name="ContainerStateWaiting"></a>
-      *ContainerStateWaiting is a waiting state of a container.*
-
-      - **initContainerStatuses.state.waiting.message** (string)
-
-        Message regarding why the container is not yet running.
-
-      - **initContainerStatuses.state.waiting.reason** (string)
-
-        (brief) reason the container is not yet running.
-
-  - **initContainerStatuses.lastState** (ContainerState)
-
-    Details about the container's last termination condition.
-
-    <a name="ContainerState"></a>
-    *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.*
-
-    - **initContainerStatuses.lastState.running** (ContainerStateRunning)
-
-      Details about a running container
-
-      <a name="ContainerStateRunning"></a>
-      *ContainerStateRunning is a running state of a container.*
-
-      - **initContainerStatuses.lastState.running.startedAt** (Time)
-
-        Time at which the container was last (re-)started
-
-        <a name="Time"></a>
-        *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.*
-
-    - **initContainerStatuses.lastState.terminated** (ContainerStateTerminated)
-
-      Details about a terminated container
-
-      <a name="ContainerStateTerminated"></a>
-      *ContainerStateTerminated is a terminated state of a container.*
-
-      - **initContainerStatuses.lastState.terminated.containerID** (string)
-
-        Container's ID in the format '\<type>://\<container_id>'
-
-      - **initContainerStatuses.lastState.terminated.exitCode** (int32), required
-
-        Exit status from the last termination of the container
-
-      - **initContainerStatuses.lastState.terminated.startedAt** (Time)
-
-        Time at which previous execution of the container started
-
-        <a name="Time"></a>
-        *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.*
-
-      - **initContainerStatuses.lastState.terminated.finishedAt** (Time)
-
-        Time at which the container last terminated
-
-        <a name="Time"></a>
-        *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.*
-
-      - **initContainerStatuses.lastState.terminated.message** (string)
-
-        Message regarding the last termination of the container
-
-      - **initContainerStatuses.lastState.terminated.reason** (string)
-
-        (brief) reason from the last termination of the container
-
-      - **initContainerStatuses.lastState.terminated.signal** (int32)
-
-        Signal from the last termination of the container
-
-    - **initContainerStatuses.lastState.waiting** (ContainerStateWaiting)
-
-      Details about a waiting container
-
-      <a name="ContainerStateWaiting"></a>
-      *ContainerStateWaiting is a waiting state of a container.*
-
-      - **initContainerStatuses.lastState.waiting.message** (string)
-
-        Message regarding why the container is not yet running.
-
-      - **initContainerStatuses.lastState.waiting.reason** (string)
-
-        (brief) reason the container is not yet running.
-
-  - **initContainerStatuses.ready** (boolean), required
-
-    Specifies whether the container has passed its readiness probe.
-
-  - **initContainerStatuses.restartCount** (int32), required
-
-    The number of times the container has been restarted.
-
-  - **initContainerStatuses.started** (boolean)
-
-    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.
-
 - **containerStatuses** ([]ContainerStatus)
 
   The list has one entry per container in the manifest. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-and-container-status
@@ -2196,188 +2016,6 @@ PodStatus represents information about the status of a pod. Status may trail the
   <a name="ContainerStatus"></a>
   *ContainerStatus contains details for the current status of this container.*
 
-  - **containerStatuses.name** (string), required
-
-    This must be a DNS_LABEL. Each container in a pod must have a unique name. Cannot be updated.
-
-  - **containerStatuses.image** (string), required
-
-    The image the container is running. More info: https://kubernetes.io/docs/concepts/containers/images.
-
-  - **containerStatuses.imageID** (string), required
-
-    ImageID of the container's image.
-
-  - **containerStatuses.containerID** (string)
-
-    Container's ID in the format '\<type>://\<container_id>'.
-
-  - **containerStatuses.state** (ContainerState)
-
-    Details about the container's current condition.
-
-    <a name="ContainerState"></a>
-    *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.*
-
-    - **containerStatuses.state.running** (ContainerStateRunning)
-
-      Details about a running container
-
-      <a name="ContainerStateRunning"></a>
-      *ContainerStateRunning is a running state of a container.*
-
-      - **containerStatuses.state.running.startedAt** (Time)
-
-        Time at which the container was last (re-)started
-
-        <a name="Time"></a>
-        *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.*
-
-    - **containerStatuses.state.terminated** (ContainerStateTerminated)
-
-      Details about a terminated container
-
-      <a name="ContainerStateTerminated"></a>
-      *ContainerStateTerminated is a terminated state of a container.*
-
-      - **containerStatuses.state.terminated.containerID** (string)
-
-        Container's ID in the format '\<type>://\<container_id>'
-
-      - **containerStatuses.state.terminated.exitCode** (int32), required
-
-        Exit status from the last termination of the container
-
-      - **containerStatuses.state.terminated.startedAt** (Time)
-
-        Time at which previous execution of the container started
-
-        <a name="Time"></a>
-        *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.*
-
-      - **containerStatuses.state.terminated.finishedAt** (Time)
-
-        Time at which the container last terminated
-
-        <a name="Time"></a>
-        *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.*
-
-      - **containerStatuses.state.terminated.message** (string)
-
-        Message regarding the last termination of the container
-
-      - **containerStatuses.state.terminated.reason** (string)
-
-        (brief) reason from the last termination of the container
-
-      - **containerStatuses.state.terminated.signal** (int32)
-
-        Signal from the last termination of the container
-
-    - **containerStatuses.state.waiting** (ContainerStateWaiting)
-
-      Details about a waiting container
-
-      <a name="ContainerStateWaiting"></a>
-      *ContainerStateWaiting is a waiting state of a container.*
-
-      - **containerStatuses.state.waiting.message** (string)
-
-        Message regarding why the container is not yet running.
-
-      - **containerStatuses.state.waiting.reason** (string)
-
-        (brief) reason the container is not yet running.
-
-  - **containerStatuses.lastState** (ContainerState)
-
-    Details about the container's last termination condition.
-
-    <a name="ContainerState"></a>
-    *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.*
-
-    - **containerStatuses.lastState.running** (ContainerStateRunning)
-
-      Details about a running container
-
-      <a name="ContainerStateRunning"></a>
-      *ContainerStateRunning is a running state of a container.*
-
-      - **containerStatuses.lastState.running.startedAt** (Time)
-
-        Time at which the container was last (re-)started
-
-        <a name="Time"></a>
-        *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.*
-
-    - **containerStatuses.lastState.terminated** (ContainerStateTerminated)
-
-      Details about a terminated container
-
-      <a name="ContainerStateTerminated"></a>
-      *ContainerStateTerminated is a terminated state of a container.*
-
-      - **containerStatuses.lastState.terminated.containerID** (string)
-
-        Container's ID in the format '\<type>://\<container_id>'
-
-      - **containerStatuses.lastState.terminated.exitCode** (int32), required
-
-        Exit status from the last termination of the container
-
-      - **containerStatuses.lastState.terminated.startedAt** (Time)
-
-        Time at which previous execution of the container started
-
-        <a name="Time"></a>
-        *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.*
-
-      - **containerStatuses.lastState.terminated.finishedAt** (Time)
-
-        Time at which the container last terminated
-
-        <a name="Time"></a>
-        *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.*
-
-      - **containerStatuses.lastState.terminated.message** (string)
-
-        Message regarding the last termination of the container
-
-      - **containerStatuses.lastState.terminated.reason** (string)
-
-        (brief) reason from the last termination of the container
-
-      - **containerStatuses.lastState.terminated.signal** (int32)
-
-        Signal from the last termination of the container
-
-    - **containerStatuses.lastState.waiting** (ContainerStateWaiting)
-
-      Details about a waiting container
-
-      <a name="ContainerStateWaiting"></a>
-      *ContainerStateWaiting is a waiting state of a container.*
-
-      - **containerStatuses.lastState.waiting.message** (string)
-
-        Message regarding why the container is not yet running.
-
-      - **containerStatuses.lastState.waiting.reason** (string)
-
-        (brief) reason the container is not yet running.
-
-  - **containerStatuses.ready** (boolean), required
-
-    Specifies whether the container has passed its readiness probe.
-
-  - **containerStatuses.restartCount** (int32), required
-
-    The number of times the container has been restarted.
-
-  - **containerStatuses.started** (boolean)
-
-    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.
-
 - **ephemeralContainerStatuses** ([]ContainerStatus)
 
   Status for any ephemeral containers that have run in this pod.
@@ -2385,187 +2023,9 @@ PodStatus represents information about the status of a pod. Status may trail the
   <a name="ContainerStatus"></a>
   *ContainerStatus contains details for the current status of this container.*
 
-  - **ephemeralContainerStatuses.name** (string), required
+- **resize** (string)
 
-    This must be a DNS_LABEL. Each container in a pod must have a unique name. Cannot be updated.
-
-  - **ephemeralContainerStatuses.image** (string), required
-
-    The image the container is running. More info: https://kubernetes.io/docs/concepts/containers/images.
-
-  - **ephemeralContainerStatuses.imageID** (string), required
-
-    ImageID of the container's image.
-
-  - **ephemeralContainerStatuses.containerID** (string)
-
-    Container's ID in the format '\<type>://\<container_id>'.
-
-  - **ephemeralContainerStatuses.state** (ContainerState)
-
-    Details about the container's current condition.
-
-    <a name="ContainerState"></a>
-    *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.*
-
-    - **ephemeralContainerStatuses.state.running** (ContainerStateRunning)
-
-      Details about a running container
-
-      <a name="ContainerStateRunning"></a>
-      *ContainerStateRunning is a running state of a container.*
-
-      - **ephemeralContainerStatuses.state.running.startedAt** (Time)
-
-        Time at which the container was last (re-)started
-
-        <a name="Time"></a>
-        *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.*
-
-    - **ephemeralContainerStatuses.state.terminated** (ContainerStateTerminated)
-
-      Details about a terminated container
-
-      <a name="ContainerStateTerminated"></a>
-      *ContainerStateTerminated is a terminated state of a container.*
-
-      - **ephemeralContainerStatuses.state.terminated.containerID** (string)
-
-        Container's ID in the format '\<type>://\<container_id>'
-
-      - **ephemeralContainerStatuses.state.terminated.exitCode** (int32), required
-
-        Exit status from the last termination of the container
-
-      - **ephemeralContainerStatuses.state.terminated.startedAt** (Time)
-
-        Time at which previous execution of the container started
-
-        <a name="Time"></a>
-        *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.*
-
-      - **ephemeralContainerStatuses.state.terminated.finishedAt** (Time)
-
-        Time at which the container last terminated
-
-        <a name="Time"></a>
-        *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.*
-
-      - **ephemeralContainerStatuses.state.terminated.message** (string)
-
-        Message regarding the last termination of the container
-
-      - **ephemeralContainerStatuses.state.terminated.reason** (string)
-
-        (brief) reason from the last termination of the container
-
-      - **ephemeralContainerStatuses.state.terminated.signal** (int32)
-
-        Signal from the last termination of the container
-
-    - **ephemeralContainerStatuses.state.waiting** (ContainerStateWaiting)
-
-      Details about a waiting container
-
-      <a name="ContainerStateWaiting"></a>
-      *ContainerStateWaiting is a waiting state of a container.*
-
-      - **ephemeralContainerStatuses.state.waiting.message** (string)
-
-        Message regarding why the container is not yet running.
-
-      - **ephemeralContainerStatuses.state.waiting.reason** (string)
-
-        (brief) reason the container is not yet running.
-
-  - **ephemeralContainerStatuses.lastState** (ContainerState)
-
-    Details about the container's last termination condition.
-
-    <a name="ContainerState"></a>
-    *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.*
-
-    - **ephemeralContainerStatuses.lastState.running** (ContainerStateRunning)
-
-      Details about a running container
-
-      <a name="ContainerStateRunning"></a>
-      *ContainerStateRunning is a running state of a container.*
-
-      - **ephemeralContainerStatuses.lastState.running.startedAt** (Time)
-
-        Time at which the container was last (re-)started
-
-        <a name="Time"></a>
-        *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.*
-
-    - **ephemeralContainerStatuses.lastState.terminated** (ContainerStateTerminated)
-
-      Details about a terminated container
-
-      <a name="ContainerStateTerminated"></a>
-      *ContainerStateTerminated is a terminated state of a container.*
-
-      - **ephemeralContainerStatuses.lastState.terminated.containerID** (string)
-
-        Container's ID in the format '\<type>://\<container_id>'
-
-      - **ephemeralContainerStatuses.lastState.terminated.exitCode** (int32), required
-
-        Exit status from the last termination of the container
-
-      - **ephemeralContainerStatuses.lastState.terminated.startedAt** (Time)
-
-        Time at which previous execution of the container started
-
-        <a name="Time"></a>
-        *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.*
-
-      - **ephemeralContainerStatuses.lastState.terminated.finishedAt** (Time)
-
-        Time at which the container last terminated
-
-        <a name="Time"></a>
-        *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.*
-
-      - **ephemeralContainerStatuses.lastState.terminated.message** (string)
-
-        Message regarding the last termination of the container
-
-      - **ephemeralContainerStatuses.lastState.terminated.reason** (string)
-
-        (brief) reason from the last termination of the container
-
-      - **ephemeralContainerStatuses.lastState.terminated.signal** (int32)
-
-        Signal from the last termination of the container
-
-    - **ephemeralContainerStatuses.lastState.waiting** (ContainerStateWaiting)
-
-      Details about a waiting container
-
-      <a name="ContainerStateWaiting"></a>
-      *ContainerStateWaiting is a waiting state of a container.*
-
-      - **ephemeralContainerStatuses.lastState.waiting.message** (string)
-
-        Message regarding why the container is not yet running.
-
-      - **ephemeralContainerStatuses.lastState.waiting.reason** (string)
-
-        (brief) reason the container is not yet running.
-
-  - **ephemeralContainerStatuses.ready** (boolean), required
-
-    Specifies whether the container has passed its readiness probe.
-
-  - **ephemeralContainerStatuses.restartCount** (int32), required
-
-    The number of times the container has been restarted.
-
-  - **ephemeralContainerStatuses.started** (boolean)
-
-    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.
+  Status of resources resize desired for pod's containers. It is empty if no resources resize is pending. Any changes to container resources will automatically set this to "Proposed"
 
 
 
@@ -2834,6 +2294,11 @@ GET /api/v1/namespaces/{namespace}/pods
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -2902,6 +2367,11 @@ GET /api/v1/pods
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -3442,6 +2912,11 @@ DELETE /api/v1/namespaces/{namespace}/pods
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/workload-resources/priority-class-v1.md b/content/en/docs/reference/kubernetes-api/workload-resources/priority-class-v1.md
index d3faa756960..5afb617faba 100644
--- a/content/en/docs/reference/kubernetes-api/workload-resources/priority-class-v1.md
+++ b/content/en/docs/reference/kubernetes-api/workload-resources/priority-class-v1.md
@@ -44,7 +44,7 @@ PriorityClass defines mapping from a priority class name to the priority integer
 
 - **value** (int32), required
 
-  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.
+  value represents the integer 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.
 
 - **description** (string)
 
@@ -56,7 +56,7 @@ PriorityClass defines mapping from a priority class name to the priority integer
 
 - **preemptionPolicy** (string)
 
-  PreemptionPolicy is the Policy for preempting pods with lower priority. One of Never, PreemptLowerPriority. Defaults to PreemptLowerPriority if unset.
+  preemptionPolicy is the Policy for preempting pods with lower priority. One of Never, PreemptLowerPriority. Defaults to PreemptLowerPriority if unset.
 
 
 
@@ -174,6 +174,11 @@ GET /apis/scheduling.k8s.io/v1/priorityclasses
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -459,6 +464,11 @@ DELETE /apis/scheduling.k8s.io/v1/priorityclasses
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/workload-resources/replica-set-v1.md b/content/en/docs/reference/kubernetes-api/workload-resources/replica-set-v1.md
index 6745c9ef18b..5c6040313cd 100644
--- a/content/en/docs/reference/kubernetes-api/workload-resources/replica-set-v1.md
+++ b/content/en/docs/reference/kubernetes-api/workload-resources/replica-set-v1.md
@@ -297,6 +297,11 @@ GET /apis/apps/v1/namespaces/{namespace}/replicasets
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -365,6 +370,11 @@ GET /apis/apps/v1/replicasets
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -790,6 +800,11 @@ DELETE /apis/apps/v1/namespaces/{namespace}/replicasets
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/workload-resources/replication-controller-v1.md b/content/en/docs/reference/kubernetes-api/workload-resources/replication-controller-v1.md
index c07094341c3..b0bb72eaeda 100644
--- a/content/en/docs/reference/kubernetes-api/workload-resources/replication-controller-v1.md
+++ b/content/en/docs/reference/kubernetes-api/workload-resources/replication-controller-v1.md
@@ -66,7 +66,7 @@ ReplicationControllerSpec is the specification of a replication controller.
 
 - **template** (<a href="{{< ref "../workload-resources/pod-template-v1#PodTemplateSpec" >}}">PodTemplateSpec</a>)
 
-  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
+  Template is the object that describes the pod that will be created if insufficient replicas are detected. This takes precedence over a TemplateRef. The only allowed template.spec.restartPolicy value is "Always". More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template
 
 - **replicas** (int32)
 
@@ -297,6 +297,11 @@ GET /api/v1/namespaces/{namespace}/replicationcontrollers
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -365,6 +370,11 @@ GET /api/v1/replicationcontrollers
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -790,6 +800,11 @@ DELETE /api/v1/namespaces/{namespace}/replicationcontrollers
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/workload-resources/resource-claim-template-v1alpha1.md b/content/en/docs/reference/kubernetes-api/workload-resources/resource-claim-template-v1alpha2.md
similarity index 84%
rename from content/en/docs/reference/kubernetes-api/workload-resources/resource-claim-template-v1alpha1.md
rename to content/en/docs/reference/kubernetes-api/workload-resources/resource-claim-template-v1alpha2.md
index 61dbcbfe4d3..ed1d6b7104f 100644
--- a/content/en/docs/reference/kubernetes-api/workload-resources/resource-claim-template-v1alpha1.md
+++ b/content/en/docs/reference/kubernetes-api/workload-resources/resource-claim-template-v1alpha2.md
@@ -1,11 +1,11 @@
 ---
 api_metadata:
-  apiVersion: "resource.k8s.io/v1alpha1"
-  import: "k8s.io/api/resource/v1alpha1"
+  apiVersion: "resource.k8s.io/v1alpha2"
+  import: "k8s.io/api/resource/v1alpha2"
   kind: "ResourceClaimTemplate"
 content_type: "api_reference"
 description: "ResourceClaimTemplate is used to produce ResourceClaim objects."
-title: "ResourceClaimTemplate v1alpha1"
+title: "ResourceClaimTemplate v1alpha2"
 weight: 16
 auto_generated: true
 ---
@@ -21,9 +21,9 @@ guide. You can file document formatting bugs against the
 [reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
 -->
 
-`apiVersion: resource.k8s.io/v1alpha1`
+`apiVersion: resource.k8s.io/v1alpha2`
 
-`import "k8s.io/api/resource/v1alpha1"`
+`import "k8s.io/api/resource/v1alpha2"`
 
 
 ## ResourceClaimTemplate {#ResourceClaimTemplate}
@@ -32,7 +32,7 @@ ResourceClaimTemplate is used to produce ResourceClaim objects.
 
 <hr>
 
-- **apiVersion**: resource.k8s.io/v1alpha1
+- **apiVersion**: resource.k8s.io/v1alpha2
 
 
 - **kind**: ResourceClaimTemplate
@@ -42,7 +42,7 @@ ResourceClaimTemplate is used to produce ResourceClaim objects.
 
   Standard object metadata
 
-- **spec** (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha1#ResourceClaimTemplateSpec" >}}">ResourceClaimTemplateSpec</a>), required
+- **spec** (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha2#ResourceClaimTemplateSpec" >}}">ResourceClaimTemplateSpec</a>), required
 
   Describes the ResourceClaim that is to be generated.
   
@@ -58,7 +58,7 @@ ResourceClaimTemplateSpec contains the metadata and fields for a ResourceClaim.
 
 <hr>
 
-- **spec** (<a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaimSpec" >}}">ResourceClaimSpec</a>), required
+- **spec** (<a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaimSpec" >}}">ResourceClaimSpec</a>), required
 
   Spec for the ResourceClaim. The entire content is copied unchanged into the ResourceClaim that gets created from this template. The same fields as in a ResourceClaim are also valid here.
 
@@ -76,7 +76,7 @@ ResourceClaimTemplateList is a collection of claim templates.
 
 <hr>
 
-- **apiVersion**: resource.k8s.io/v1alpha1
+- **apiVersion**: resource.k8s.io/v1alpha2
 
 
 - **kind**: ResourceClaimTemplateList
@@ -86,7 +86,7 @@ ResourceClaimTemplateList is a collection of claim templates.
 
   Standard list metadata
 
-- **items** ([]<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha1#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>), required
+- **items** ([]<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha2#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>), required
 
   Items is the list of resource claim templates.
 
@@ -109,7 +109,7 @@ ResourceClaimTemplateList is a collection of claim templates.
 
 #### HTTP Request
 
-GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplates/{name}
+GET /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaimtemplates/{name}
 
 #### Parameters
 
@@ -133,7 +133,7 @@ GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplates
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha1#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha2#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>): OK
 
 401: Unauthorized
 
@@ -142,7 +142,7 @@ GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplates
 
 #### HTTP Request
 
-GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplates
+GET /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaimtemplates
 
 #### Parameters
 
@@ -192,6 +192,11 @@ GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplates
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -206,7 +211,7 @@ GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplates
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha1#ResourceClaimTemplateList" >}}">ResourceClaimTemplateList</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha2#ResourceClaimTemplateList" >}}">ResourceClaimTemplateList</a>): OK
 
 401: Unauthorized
 
@@ -215,7 +220,7 @@ GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplates
 
 #### HTTP Request
 
-GET /apis/resource.k8s.io/v1alpha1/resourceclaimtemplates
+GET /apis/resource.k8s.io/v1alpha2/resourceclaimtemplates
 
 #### Parameters
 
@@ -260,6 +265,11 @@ GET /apis/resource.k8s.io/v1alpha1/resourceclaimtemplates
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -274,7 +284,7 @@ GET /apis/resource.k8s.io/v1alpha1/resourceclaimtemplates
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha1#ResourceClaimTemplateList" >}}">ResourceClaimTemplateList</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha2#ResourceClaimTemplateList" >}}">ResourceClaimTemplateList</a>): OK
 
 401: Unauthorized
 
@@ -283,7 +293,7 @@ GET /apis/resource.k8s.io/v1alpha1/resourceclaimtemplates
 
 #### HTTP Request
 
-POST /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplates
+POST /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaimtemplates
 
 #### Parameters
 
@@ -293,7 +303,7 @@ POST /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplate
   <a href="{{< ref "../common-parameters/common-parameters#namespace" >}}">namespace</a>
 
 
-- **body**: <a href="{{< ref "../workload-resources/resource-claim-template-v1alpha1#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>, required
+- **body**: <a href="{{< ref "../workload-resources/resource-claim-template-v1alpha2#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>, required
 
   
 
@@ -322,11 +332,11 @@ POST /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplate
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha1#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha2#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>): OK
 
-201 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha1#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>): Created
+201 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha2#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>): Created
 
-202 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha1#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>): Accepted
+202 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha2#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>): Accepted
 
 401: Unauthorized
 
@@ -335,7 +345,7 @@ POST /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplate
 
 #### HTTP Request
 
-PUT /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplates/{name}
+PUT /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaimtemplates/{name}
 
 #### Parameters
 
@@ -350,7 +360,7 @@ PUT /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplates
   <a href="{{< ref "../common-parameters/common-parameters#namespace" >}}">namespace</a>
 
 
-- **body**: <a href="{{< ref "../workload-resources/resource-claim-template-v1alpha1#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>, required
+- **body**: <a href="{{< ref "../workload-resources/resource-claim-template-v1alpha2#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>, required
 
   
 
@@ -379,9 +389,9 @@ PUT /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplates
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha1#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha2#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>): OK
 
-201 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha1#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>): Created
+201 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha2#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>): Created
 
 401: Unauthorized
 
@@ -390,7 +400,7 @@ PUT /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplates
 
 #### HTTP Request
 
-PATCH /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplates/{name}
+PATCH /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaimtemplates/{name}
 
 #### Parameters
 
@@ -439,9 +449,9 @@ PATCH /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplat
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha1#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha2#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>): OK
 
-201 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha1#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>): Created
+201 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha2#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>): Created
 
 401: Unauthorized
 
@@ -450,7 +460,7 @@ PATCH /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplat
 
 #### HTTP Request
 
-DELETE /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplates/{name}
+DELETE /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaimtemplates/{name}
 
 #### Parameters
 
@@ -494,9 +504,9 @@ DELETE /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtempla
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha1#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha2#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>): OK
 
-202 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha1#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>): Accepted
+202 (<a href="{{< ref "../workload-resources/resource-claim-template-v1alpha2#ResourceClaimTemplate" >}}">ResourceClaimTemplate</a>): Accepted
 
 401: Unauthorized
 
@@ -505,7 +515,7 @@ DELETE /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtempla
 
 #### HTTP Request
 
-DELETE /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtemplates
+DELETE /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaimtemplates
 
 #### Parameters
 
@@ -570,6 +580,11 @@ DELETE /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaimtempla
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/workload-resources/resource-claim-v1alpha1.md b/content/en/docs/reference/kubernetes-api/workload-resources/resource-claim-v1alpha2.md
similarity index 80%
rename from content/en/docs/reference/kubernetes-api/workload-resources/resource-claim-v1alpha1.md
rename to content/en/docs/reference/kubernetes-api/workload-resources/resource-claim-v1alpha2.md
index 0f435c9721a..24b8419a5ee 100644
--- a/content/en/docs/reference/kubernetes-api/workload-resources/resource-claim-v1alpha1.md
+++ b/content/en/docs/reference/kubernetes-api/workload-resources/resource-claim-v1alpha2.md
@@ -1,11 +1,11 @@
 ---
 api_metadata:
-  apiVersion: "resource.k8s.io/v1alpha1"
-  import: "k8s.io/api/resource/v1alpha1"
+  apiVersion: "resource.k8s.io/v1alpha2"
+  import: "k8s.io/api/resource/v1alpha2"
   kind: "ResourceClaim"
 content_type: "api_reference"
 description: "ResourceClaim describes which resources are needed by a resource consumer."
-title: "ResourceClaim v1alpha1"
+title: "ResourceClaim v1alpha2"
 weight: 15
 auto_generated: true
 ---
@@ -21,9 +21,9 @@ guide. You can file document formatting bugs against the
 [reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
 -->
 
-`apiVersion: resource.k8s.io/v1alpha1`
+`apiVersion: resource.k8s.io/v1alpha2`
 
-`import "k8s.io/api/resource/v1alpha1"`
+`import "k8s.io/api/resource/v1alpha2"`
 
 
 ## ResourceClaim {#ResourceClaim}
@@ -34,7 +34,7 @@ This is an alpha type and requires enabling the DynamicResourceAllocation featur
 
 <hr>
 
-- **apiVersion**: resource.k8s.io/v1alpha1
+- **apiVersion**: resource.k8s.io/v1alpha2
 
 
 - **kind**: ResourceClaim
@@ -44,11 +44,11 @@ This is an alpha type and requires enabling the DynamicResourceAllocation featur
 
   Standard object metadata
 
-- **spec** (<a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaimSpec" >}}">ResourceClaimSpec</a>), required
+- **spec** (<a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaimSpec" >}}">ResourceClaimSpec</a>), required
 
   Spec describes the desired attributes of a resource that then needs to be allocated. It can only be set once when creating the ResourceClaim.
 
-- **status** (<a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaimStatus" >}}">ResourceClaimStatus</a>)
+- **status** (<a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaimStatus" >}}">ResourceClaimStatus</a>)
 
   Status describes whether the resource is available and with which attributes.
 
@@ -103,14 +103,14 @@ ResourceClaimStatus tracks whether the resource has been allocated and what the
 
 - **allocation** (AllocationResult)
 
-  Allocation is set by the resource driver once a resource has been allocated successfully. If this is not specified, the resource is not yet allocated.
+  Allocation is set by the resource driver once a resource or set of resources has been allocated successfully. If this is not specified, the resources have not been allocated yet.
 
   <a name="AllocationResult"></a>
-  *AllocationResult contains attributed of an allocated resource.*
+  *AllocationResult contains attributes of an allocated resource.*
 
   - **allocation.availableOnNodes** (NodeSelector)
 
-    This field will get set by the resource driver after it has allocated the resource driver to inform the scheduler where it can schedule Pods using the ResourceClaim.
+    This field will get set by the resource driver after it has allocated the resource to inform the scheduler where it can schedule Pods using the ResourceClaim.
     
     Setting this field is optional. If null, the resource is available everywhere.
 
@@ -132,11 +132,26 @@ ResourceClaimStatus tracks whether the resource has been allocated and what the
 
         A list of node selector requirements by node's fields.
 
-  - **allocation.resourceHandle** (string)
+  - **allocation.resourceHandles** ([]ResourceHandle)
 
-    ResourceHandle contains arbitrary data returned by the driver after a successful allocation. This is opaque for Kubernetes. Driver documentation may explain to users how to interpret this data if needed.
+    *Atomic: will be replaced during a merge*
     
-    The maximum size of this field is 16KiB. This may get increased in the future, but not reduced.
+    ResourceHandles contain the state associated with an allocation that should be maintained throughout the lifetime of a claim. Each ResourceHandle contains data that should be passed to a specific kubelet plugin once it lands on a node. This data is returned by the driver after a successful allocation and is opaque to Kubernetes. Driver documentation may explain to users how to interpret this data if needed.
+    
+    Setting this field is optional. It has a maximum size of 32 entries. If null (or empty), it is assumed this allocation will be processed by a single kubelet plugin with no ResourceHandle data attached. The name of the kubelet plugin invoked will match the DriverName set in the ResourceClaimStatus this AllocationResult is embedded in.
+
+    <a name="ResourceHandle"></a>
+    *ResourceHandle holds opaque resource data for processing by a specific kubelet plugin.*
+
+    - **allocation.resourceHandles.data** (string)
+
+      Data contains the opaque data associated with this ResourceHandle. It is set by the controller component of the resource driver whose name matches the DriverName set in the ResourceClaimStatus this ResourceHandle is embedded in. It is set at allocation time and is intended for processing by the kubelet plugin whose name matches the DriverName set in this ResourceHandle.
+      
+      The maximum size of this field is 16KiB. This may get increased in the future, but not reduced.
+
+    - **allocation.resourceHandles.driverName** (string)
+
+      DriverName specifies the name of the resource driver whose kubelet plugin should be invoked to process this ResourceHandle's data once it lands on a node. This may differ from the DriverName set in ResourceClaimStatus this ResourceHandle is embedded in.
 
   - **allocation.shareable** (boolean)
 
@@ -156,7 +171,7 @@ ResourceClaimStatus tracks whether the resource has been allocated and what the
 
 - **reservedFor** ([]ResourceClaimConsumerReference)
 
-  *Set: unique values will be kept during a merge*
+  *Map: unique values on key uid will be kept during a merge*
   
   ReservedFor indicates which entities are currently allowed to use the claim. A Pod which references a ResourceClaim which is not reserved for that Pod will not be started.
   
@@ -191,7 +206,7 @@ ResourceClaimList is a collection of claims.
 
 <hr>
 
-- **apiVersion**: resource.k8s.io/v1alpha1
+- **apiVersion**: resource.k8s.io/v1alpha2
 
 
 - **kind**: ResourceClaimList
@@ -201,7 +216,7 @@ ResourceClaimList is a collection of claims.
 
   Standard list metadata
 
-- **items** ([]<a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaim" >}}">ResourceClaim</a>), required
+- **items** ([]<a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaim" >}}">ResourceClaim</a>), required
 
   Items is the list of resource claims.
 
@@ -224,7 +239,7 @@ ResourceClaimList is a collection of claims.
 
 #### HTTP Request
 
-GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name}
+GET /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{name}
 
 #### Parameters
 
@@ -248,7 +263,7 @@ GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name}
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaim" >}}">ResourceClaim</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaim" >}}">ResourceClaim</a>): OK
 
 401: Unauthorized
 
@@ -257,7 +272,7 @@ GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name}
 
 #### HTTP Request
 
-GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name}/status
+GET /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{name}/status
 
 #### Parameters
 
@@ -281,7 +296,7 @@ GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name}/
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaim" >}}">ResourceClaim</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaim" >}}">ResourceClaim</a>): OK
 
 401: Unauthorized
 
@@ -290,7 +305,7 @@ GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name}/
 
 #### HTTP Request
 
-GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims
+GET /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims
 
 #### Parameters
 
@@ -340,6 +355,11 @@ GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -354,7 +374,7 @@ GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaimList" >}}">ResourceClaimList</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaimList" >}}">ResourceClaimList</a>): OK
 
 401: Unauthorized
 
@@ -363,7 +383,7 @@ GET /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims
 
 #### HTTP Request
 
-GET /apis/resource.k8s.io/v1alpha1/resourceclaims
+GET /apis/resource.k8s.io/v1alpha2/resourceclaims
 
 #### Parameters
 
@@ -408,6 +428,11 @@ GET /apis/resource.k8s.io/v1alpha1/resourceclaims
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -422,7 +447,7 @@ GET /apis/resource.k8s.io/v1alpha1/resourceclaims
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaimList" >}}">ResourceClaimList</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaimList" >}}">ResourceClaimList</a>): OK
 
 401: Unauthorized
 
@@ -431,7 +456,7 @@ GET /apis/resource.k8s.io/v1alpha1/resourceclaims
 
 #### HTTP Request
 
-POST /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims
+POST /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims
 
 #### Parameters
 
@@ -441,7 +466,7 @@ POST /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims
   <a href="{{< ref "../common-parameters/common-parameters#namespace" >}}">namespace</a>
 
 
-- **body**: <a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaim" >}}">ResourceClaim</a>, required
+- **body**: <a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaim" >}}">ResourceClaim</a>, required
 
   
 
@@ -470,11 +495,11 @@ POST /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaim" >}}">ResourceClaim</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaim" >}}">ResourceClaim</a>): OK
 
-201 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaim" >}}">ResourceClaim</a>): Created
+201 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaim" >}}">ResourceClaim</a>): Created
 
-202 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaim" >}}">ResourceClaim</a>): Accepted
+202 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaim" >}}">ResourceClaim</a>): Accepted
 
 401: Unauthorized
 
@@ -483,7 +508,7 @@ POST /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims
 
 #### HTTP Request
 
-PUT /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name}
+PUT /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{name}
 
 #### Parameters
 
@@ -498,7 +523,7 @@ PUT /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name}
   <a href="{{< ref "../common-parameters/common-parameters#namespace" >}}">namespace</a>
 
 
-- **body**: <a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaim" >}}">ResourceClaim</a>, required
+- **body**: <a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaim" >}}">ResourceClaim</a>, required
 
   
 
@@ -527,9 +552,9 @@ PUT /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name}
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaim" >}}">ResourceClaim</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaim" >}}">ResourceClaim</a>): OK
 
-201 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaim" >}}">ResourceClaim</a>): Created
+201 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaim" >}}">ResourceClaim</a>): Created
 
 401: Unauthorized
 
@@ -538,7 +563,7 @@ PUT /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name}
 
 #### HTTP Request
 
-PUT /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name}/status
+PUT /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{name}/status
 
 #### Parameters
 
@@ -553,7 +578,7 @@ PUT /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name}/
   <a href="{{< ref "../common-parameters/common-parameters#namespace" >}}">namespace</a>
 
 
-- **body**: <a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaim" >}}">ResourceClaim</a>, required
+- **body**: <a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaim" >}}">ResourceClaim</a>, required
 
   
 
@@ -582,9 +607,9 @@ PUT /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name}/
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaim" >}}">ResourceClaim</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaim" >}}">ResourceClaim</a>): OK
 
-201 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaim" >}}">ResourceClaim</a>): Created
+201 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaim" >}}">ResourceClaim</a>): Created
 
 401: Unauthorized
 
@@ -593,7 +618,7 @@ PUT /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name}/
 
 #### HTTP Request
 
-PATCH /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name}
+PATCH /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{name}
 
 #### Parameters
 
@@ -642,9 +667,9 @@ PATCH /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaim" >}}">ResourceClaim</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaim" >}}">ResourceClaim</a>): OK
 
-201 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaim" >}}">ResourceClaim</a>): Created
+201 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaim" >}}">ResourceClaim</a>): Created
 
 401: Unauthorized
 
@@ -653,7 +678,7 @@ PATCH /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name
 
 #### HTTP Request
 
-PATCH /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name}/status
+PATCH /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{name}/status
 
 #### Parameters
 
@@ -702,9 +727,9 @@ PATCH /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaim" >}}">ResourceClaim</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaim" >}}">ResourceClaim</a>): OK
 
-201 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaim" >}}">ResourceClaim</a>): Created
+201 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaim" >}}">ResourceClaim</a>): Created
 
 401: Unauthorized
 
@@ -713,7 +738,7 @@ PATCH /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name
 
 #### HTTP Request
 
-DELETE /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{name}
+DELETE /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{name}
 
 #### Parameters
 
@@ -757,9 +782,9 @@ DELETE /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{nam
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaim" >}}">ResourceClaim</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaim" >}}">ResourceClaim</a>): OK
 
-202 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha1#ResourceClaim" >}}">ResourceClaim</a>): Accepted
+202 (<a href="{{< ref "../workload-resources/resource-claim-v1alpha2#ResourceClaim" >}}">ResourceClaim</a>): Accepted
 
 401: Unauthorized
 
@@ -768,7 +793,7 @@ DELETE /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims/{nam
 
 #### HTTP Request
 
-DELETE /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims
+DELETE /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims
 
 #### Parameters
 
@@ -833,6 +858,11 @@ DELETE /apis/resource.k8s.io/v1alpha1/namespaces/{namespace}/resourceclaims
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/workload-resources/resource-class-v1alpha1.md b/content/en/docs/reference/kubernetes-api/workload-resources/resource-class-v1alpha2.md
similarity index 87%
rename from content/en/docs/reference/kubernetes-api/workload-resources/resource-class-v1alpha1.md
rename to content/en/docs/reference/kubernetes-api/workload-resources/resource-class-v1alpha2.md
index e06ae249913..8e3c5a50da5 100644
--- a/content/en/docs/reference/kubernetes-api/workload-resources/resource-class-v1alpha1.md
+++ b/content/en/docs/reference/kubernetes-api/workload-resources/resource-class-v1alpha2.md
@@ -1,11 +1,11 @@
 ---
 api_metadata:
-  apiVersion: "resource.k8s.io/v1alpha1"
-  import: "k8s.io/api/resource/v1alpha1"
+  apiVersion: "resource.k8s.io/v1alpha2"
+  import: "k8s.io/api/resource/v1alpha2"
   kind: "ResourceClass"
 content_type: "api_reference"
 description: "ResourceClass is used by administrators to influence how resources are allocated."
-title: "ResourceClass v1alpha1"
+title: "ResourceClass v1alpha2"
 weight: 17
 auto_generated: true
 ---
@@ -21,9 +21,9 @@ guide. You can file document formatting bugs against the
 [reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
 -->
 
-`apiVersion: resource.k8s.io/v1alpha1`
+`apiVersion: resource.k8s.io/v1alpha2`
 
-`import "k8s.io/api/resource/v1alpha1"`
+`import "k8s.io/api/resource/v1alpha2"`
 
 
 ## ResourceClass {#ResourceClass}
@@ -34,7 +34,7 @@ This is an alpha type and requires enabling the DynamicResourceAllocation featur
 
 <hr>
 
-- **apiVersion**: resource.k8s.io/v1alpha1
+- **apiVersion**: resource.k8s.io/v1alpha2
 
 
 - **kind**: ResourceClass
@@ -107,7 +107,7 @@ ResourceClassList is a collection of classes.
 
 <hr>
 
-- **apiVersion**: resource.k8s.io/v1alpha1
+- **apiVersion**: resource.k8s.io/v1alpha2
 
 
 - **kind**: ResourceClassList
@@ -117,7 +117,7 @@ ResourceClassList is a collection of classes.
 
   Standard list metadata
 
-- **items** ([]<a href="{{< ref "../workload-resources/resource-class-v1alpha1#ResourceClass" >}}">ResourceClass</a>), required
+- **items** ([]<a href="{{< ref "../workload-resources/resource-class-v1alpha2#ResourceClass" >}}">ResourceClass</a>), required
 
   Items is the list of resource classes.
 
@@ -140,7 +140,7 @@ ResourceClassList is a collection of classes.
 
 #### HTTP Request
 
-GET /apis/resource.k8s.io/v1alpha1/resourceclasses/{name}
+GET /apis/resource.k8s.io/v1alpha2/resourceclasses/{name}
 
 #### Parameters
 
@@ -159,7 +159,7 @@ GET /apis/resource.k8s.io/v1alpha1/resourceclasses/{name}
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-class-v1alpha1#ResourceClass" >}}">ResourceClass</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-class-v1alpha2#ResourceClass" >}}">ResourceClass</a>): OK
 
 401: Unauthorized
 
@@ -168,7 +168,7 @@ GET /apis/resource.k8s.io/v1alpha1/resourceclasses/{name}
 
 #### HTTP Request
 
-GET /apis/resource.k8s.io/v1alpha1/resourceclasses
+GET /apis/resource.k8s.io/v1alpha2/resourceclasses
 
 #### Parameters
 
@@ -213,6 +213,11 @@ GET /apis/resource.k8s.io/v1alpha1/resourceclasses
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -227,7 +232,7 @@ GET /apis/resource.k8s.io/v1alpha1/resourceclasses
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-class-v1alpha1#ResourceClassList" >}}">ResourceClassList</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-class-v1alpha2#ResourceClassList" >}}">ResourceClassList</a>): OK
 
 401: Unauthorized
 
@@ -236,12 +241,12 @@ GET /apis/resource.k8s.io/v1alpha1/resourceclasses
 
 #### HTTP Request
 
-POST /apis/resource.k8s.io/v1alpha1/resourceclasses
+POST /apis/resource.k8s.io/v1alpha2/resourceclasses
 
 #### Parameters
 
 
-- **body**: <a href="{{< ref "../workload-resources/resource-class-v1alpha1#ResourceClass" >}}">ResourceClass</a>, required
+- **body**: <a href="{{< ref "../workload-resources/resource-class-v1alpha2#ResourceClass" >}}">ResourceClass</a>, required
 
   
 
@@ -270,11 +275,11 @@ POST /apis/resource.k8s.io/v1alpha1/resourceclasses
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-class-v1alpha1#ResourceClass" >}}">ResourceClass</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-class-v1alpha2#ResourceClass" >}}">ResourceClass</a>): OK
 
-201 (<a href="{{< ref "../workload-resources/resource-class-v1alpha1#ResourceClass" >}}">ResourceClass</a>): Created
+201 (<a href="{{< ref "../workload-resources/resource-class-v1alpha2#ResourceClass" >}}">ResourceClass</a>): Created
 
-202 (<a href="{{< ref "../workload-resources/resource-class-v1alpha1#ResourceClass" >}}">ResourceClass</a>): Accepted
+202 (<a href="{{< ref "../workload-resources/resource-class-v1alpha2#ResourceClass" >}}">ResourceClass</a>): Accepted
 
 401: Unauthorized
 
@@ -283,7 +288,7 @@ POST /apis/resource.k8s.io/v1alpha1/resourceclasses
 
 #### HTTP Request
 
-PUT /apis/resource.k8s.io/v1alpha1/resourceclasses/{name}
+PUT /apis/resource.k8s.io/v1alpha2/resourceclasses/{name}
 
 #### Parameters
 
@@ -293,7 +298,7 @@ PUT /apis/resource.k8s.io/v1alpha1/resourceclasses/{name}
   name of the ResourceClass
 
 
-- **body**: <a href="{{< ref "../workload-resources/resource-class-v1alpha1#ResourceClass" >}}">ResourceClass</a>, required
+- **body**: <a href="{{< ref "../workload-resources/resource-class-v1alpha2#ResourceClass" >}}">ResourceClass</a>, required
 
   
 
@@ -322,9 +327,9 @@ PUT /apis/resource.k8s.io/v1alpha1/resourceclasses/{name}
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-class-v1alpha1#ResourceClass" >}}">ResourceClass</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-class-v1alpha2#ResourceClass" >}}">ResourceClass</a>): OK
 
-201 (<a href="{{< ref "../workload-resources/resource-class-v1alpha1#ResourceClass" >}}">ResourceClass</a>): Created
+201 (<a href="{{< ref "../workload-resources/resource-class-v1alpha2#ResourceClass" >}}">ResourceClass</a>): Created
 
 401: Unauthorized
 
@@ -333,7 +338,7 @@ PUT /apis/resource.k8s.io/v1alpha1/resourceclasses/{name}
 
 #### HTTP Request
 
-PATCH /apis/resource.k8s.io/v1alpha1/resourceclasses/{name}
+PATCH /apis/resource.k8s.io/v1alpha2/resourceclasses/{name}
 
 #### Parameters
 
@@ -377,9 +382,9 @@ PATCH /apis/resource.k8s.io/v1alpha1/resourceclasses/{name}
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-class-v1alpha1#ResourceClass" >}}">ResourceClass</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-class-v1alpha2#ResourceClass" >}}">ResourceClass</a>): OK
 
-201 (<a href="{{< ref "../workload-resources/resource-class-v1alpha1#ResourceClass" >}}">ResourceClass</a>): Created
+201 (<a href="{{< ref "../workload-resources/resource-class-v1alpha2#ResourceClass" >}}">ResourceClass</a>): Created
 
 401: Unauthorized
 
@@ -388,7 +393,7 @@ PATCH /apis/resource.k8s.io/v1alpha1/resourceclasses/{name}
 
 #### HTTP Request
 
-DELETE /apis/resource.k8s.io/v1alpha1/resourceclasses/{name}
+DELETE /apis/resource.k8s.io/v1alpha2/resourceclasses/{name}
 
 #### Parameters
 
@@ -427,9 +432,9 @@ DELETE /apis/resource.k8s.io/v1alpha1/resourceclasses/{name}
 #### Response
 
 
-200 (<a href="{{< ref "../workload-resources/resource-class-v1alpha1#ResourceClass" >}}">ResourceClass</a>): OK
+200 (<a href="{{< ref "../workload-resources/resource-class-v1alpha2#ResourceClass" >}}">ResourceClass</a>): OK
 
-202 (<a href="{{< ref "../workload-resources/resource-class-v1alpha1#ResourceClass" >}}">ResourceClass</a>): Accepted
+202 (<a href="{{< ref "../workload-resources/resource-class-v1alpha2#ResourceClass" >}}">ResourceClass</a>): Accepted
 
 401: Unauthorized
 
@@ -438,7 +443,7 @@ DELETE /apis/resource.k8s.io/v1alpha1/resourceclasses/{name}
 
 #### HTTP Request
 
-DELETE /apis/resource.k8s.io/v1alpha1/resourceclasses
+DELETE /apis/resource.k8s.io/v1alpha2/resourceclasses
 
 #### Parameters
 
@@ -498,6 +503,11 @@ DELETE /apis/resource.k8s.io/v1alpha1/resourceclasses
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
diff --git a/content/en/docs/reference/kubernetes-api/workload-resources/stateful-set-v1.md b/content/en/docs/reference/kubernetes-api/workload-resources/stateful-set-v1.md
index 2e588e6f131..a106d18d27e 100644
--- a/content/en/docs/reference/kubernetes-api/workload-resources/stateful-set-v1.md
+++ b/content/en/docs/reference/kubernetes-api/workload-resources/stateful-set-v1.md
@@ -74,7 +74,7 @@ A StatefulSetSpec is the specification of a StatefulSet.
 
 - **template** (<a href="{{< ref "../workload-resources/pod-template-v1#PodTemplateSpec" >}}">PodTemplateSpec</a>), required
 
-  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. Each pod will be named with the format \<statefulsetname>-\<podindex>. For example, a pod in a StatefulSet named "web" with index number "3" would be named "web-3".
+  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. Each pod will be named with the format \<statefulsetname>-\<podindex>. For example, a pod in a StatefulSet named "web" with index number "3" would be named "web-3". The only allowed template.spec.restartPolicy value is "Always".
 
 - **replicas** (int32)
 
@@ -90,8 +90,6 @@ A StatefulSetSpec is the specification of a StatefulSet.
   - **updateStrategy.type** (string)
 
     Type indicates the type of the StatefulSetUpdateStrategy. Default is RollingUpdate.
-    
-    
 
   - **updateStrategy.rollingUpdate** (RollingUpdateStatefulSetStrategy)
 
@@ -114,8 +112,6 @@ A StatefulSetSpec is the specification of a StatefulSet.
 - **podManagementPolicy** (string)
 
   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.
-  
-  
 
 - **revisionHistoryLimit** (int32)
 
@@ -146,7 +142,7 @@ A StatefulSetSpec is the specification of a StatefulSet.
 
 - **ordinals** (StatefulSetOrdinals)
 
-  ordinals controls the numbering of replica indices in a StatefulSet. The default ordinals behavior assigns a "0" index to the first replica and increments the index by one for each additional replica requested. Using the ordinals field requires the StatefulSetStartOrdinal feature gate to be enabled, which is alpha.
+  ordinals controls the numbering of replica indices in a StatefulSet. The default ordinals behavior assigns a "0" index to the first replica and increments the index by one for each additional replica requested. Using the ordinals field requires the StatefulSetStartOrdinal feature gate to be enabled, which is beta.
 
   <a name="StatefulSetOrdinals"></a>
   *StatefulSetOrdinals describes the policy used for replica ordinal assignment in this StatefulSet.*
@@ -395,6 +391,11 @@ GET /apis/apps/v1/namespaces/{namespace}/statefulsets
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -463,6 +464,11 @@ GET /apis/apps/v1/statefulsets
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -888,6 +894,11 @@ DELETE /apis/apps/v1/namespaces/{namespace}/statefulsets
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>

From ba1d6bd99907f4cb0c09c1a44d9e4fb1045126ab Mon Sep 17 00:00:00 2001
From: Kante Yin <kerthcet@gmail.com>
Date: Mon, 3 Apr 2023 00:48:27 +0800
Subject: [PATCH 082/272] Add section about nodeInclusionPolicy

Signed-off-by: Kante Yin <kerthcet@gmail.com>
---
 .../2023-04-11-topology-spread-features.md    | 50 +++++++++++++++++--
 1 file changed, 45 insertions(+), 5 deletions(-)

diff --git a/content/en/blog/_posts/2023-04-11-topology-spread-features.md b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
index 290a5ac2b73..990e3ff784f 100644
--- a/content/en/blog/_posts/2023-04-11-topology-spread-features.md
+++ b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
@@ -8,7 +8,7 @@ evergreen: true
 
 **Authors:** [Alex Wang](https://github.com/denkensk)(Shopee), [Kante Yin](https://github.com/kerthcet)(DaoCloud), [Kensei Nakada](https://github.com/sanposhiho)(Mercari)
 
-In Kubernetes v1.19, [Pod Topology Spread Constraints](https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/) went to GA. 
+In Kubernetes v1.19, [Pod Topology Spread Constraints](https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/) went to GA.
 It is the feature to control how Pods are spread to each failure-domain (regions, zones, nodes etc).
 
 As time passes, we've got further feedbacks from users,
@@ -47,17 +47,57 @@ but other 2 Pods from this replicaset will be unschedulable until more Nodes joi
 The cluster autoscaler provisions new Nodes based on these unschedulable Pods,
 and as a result, the replicas are finally spread over 5 Nodes.
 
-## KEP-3094: Take taints/tolerations into consideration when calculating PodTopologySpread skew
+## Take taints/tolerations into consideration when calculating PodTopologySpread skew
 
-TODO(kerthcet): write it
+Before this, when we deploy a pod with `podTopologySpread` configured, we'll take all
+affinity nodes(satisfied with pod nodeAffinity and nodeSelector) into consideration
+in filtering and scoring, but a node with pod untolerated taint may also be a candidate
+because we didn't take care of node taints, which will lead to the pod pending.
+
+To avoid this and make a more fine-gained decision in scheduling, we introduced two new fields in
+`TopologySpreadConstraint` to define node inclusion policies including nodeAffinity and nodeTaint.
+
+It mostly looks like:
+
+```yaml
+apiVersion: v1
+kind: Pod
+metadata:
+  name: example-pod
+spec:
+  # Configure a topology spread constraint
+  topologySpreadConstraints:
+    - maxSkew: <integer>
+      # ...
+      nodeAffinityPolicy: [Honor|Ignore]
+      nodeTaintsPolicy: [Honor|Ignore]
+  # other Pod fields go here
+```
+
+**nodeAffinityPolicy** indicates how we'll treat Pod's nodeAffinity/nodeSelector in pod topology spreading.
+If `Honor`, we'll filter out nodes not matching nodeAffinity/nodeSelector in calculation.
+If `Ignore`, these nodes will be included instead.
+
+For backwards-compatibility, nodeAffinityPolicy is default to `Honor`.
+
+**nodeTaintsPolicy** indicates how we'll treat node taints in pod topology spreading.
+If `Honor`, only tainted nodes for which the incoming pod has a toleration, will be included in calculation.
+If `Ignore`, we'll not consider the node taints at all in calculation, so a node with pod untolerated taint
+will also be included.
+
+For backwards-compatibility, nodeTaintsPolicy is default to the `Ignore`.
+
+The feature was introduced in v1.25 as alpha level. By default, it was disabled, so if you want to use this feature in v1.25,
+you have to enable the feature gate `NodeInclusionPolicyInPodTopologySpread` actively. In the following v1.26, we graduated
+this feature to beta and it was enabled by default since.
 
 ## KEP-3243: Respect PodTopologySpread after rolling upgrades
 
 TODO(denkensk): write it
 
-## Getting involved 
+## Getting involved
 
-These features are managed by the [SIG/Scheduling](https://github.com/kubernetes/community/tree/master/sig-scheduling). 
+These features are managed by the [SIG/Scheduling](https://github.com/kubernetes/community/tree/master/sig-scheduling).
 
 Please join us and share your feedback. We look forward to hearing from you!
 

From c35cd20175cc3a86d3622794db869a3eaa294d3a Mon Sep 17 00:00:00 2001
From: Alex Wang <wangqingcan1990@gmail.com>
Date: Mon, 3 Apr 2023 15:46:20 +0800
Subject: [PATCH 083/272] blog: add section about matchLabelKeys

Signed-off-by: Alex Wang <wangqingcan1990@gmail.com>
---
 .../2023-04-11-topology-spread-features.md    | 33 ++++++++++++++++++-
 1 file changed, 32 insertions(+), 1 deletion(-)

diff --git a/content/en/blog/_posts/2023-04-11-topology-spread-features.md b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
index 990e3ff784f..9be4953732f 100644
--- a/content/en/blog/_posts/2023-04-11-topology-spread-features.md
+++ b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
@@ -93,7 +93,38 @@ this feature to beta and it was enabled by default since.
 
 ## KEP-3243: Respect PodTopologySpread after rolling upgrades
 
-TODO(denkensk): write it
+Pod Topology Spread uses the fields `topologyKey` or `labelSelector` to identify the group of pods over which
+spreading will be calculated. But it applies to all pods in a Deployment irrespective of their owning
+ReplicaSet. As a result, when a new revision is rolled out, spreading will apply across pods from both the
+old and new ReplicaSets, and so by the time the new ReplicaSet is completely rolled out and the old one is
+rolled back, the actual spreading we are left with may not match expectations because the deleted pods from
+the older ReplicaSet will cause skewed distribution for the remaining pods.
+
+In order to solve this problem and to make more accurate decisions in scheduling, we added a new named
+`matchLabelKeys` to `topologySpreadConstraints`. `matchLabelKeys` is a list of pod label keys to select
+the pods over which spreading will be calculated. The keys are used to lookup values from the pod labels,
+those key-value labels are ANDed with `labelSelector` to select the group of existing pods over
+which spreading will be calculated for the incoming pod.
+
+With `matchLabelKeys`, you don't need to update the `pod.spec` between different revisions.
+The controller/operator just needs to set different values to the same label key for different revisions.
+The scheduler will assume the values automatically based on `matchLabelKeys`.
+For example, if you are configuring a Deployment, you can use the label keyed with
+[pod-template-hash](https://kubernetes.io//docs/concepts/workloads/controllers/deployment/#pod-template-hash-label),
+which is added automatically by the Deployment controller, to distinguish between different
+revisions in a single Deployment.
+
+```yaml
+topologySpreadConstraints:
+    - maxSkew: 1
+      topologyKey: kubernetes.io/hostname
+      whenUnsatisfiable: DoNotSchedule
+      labelSelector:
+        matchLabels:
+          app: foo
+      matchLabelKeys:
+        - pod-template-hash
+```
 
 ## Getting involved
 

From dcfe5ae35f97dc1719e7df3bd83ad9dac46cd8fa Mon Sep 17 00:00:00 2001
From: Kensei Nakada <handbomusic@gmail.com>
Date: Mon, 3 Apr 2023 16:50:49 +0900
Subject: [PATCH 084/272] updat title and slug

---
 content/en/blog/_posts/2023-04-11-topology-spread-features.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/en/blog/_posts/2023-04-11-topology-spread-features.md b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
index 9be4953732f..a159117e310 100644
--- a/content/en/blog/_posts/2023-04-11-topology-spread-features.md
+++ b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
@@ -1,8 +1,8 @@
 ---
 layout: blog
-title: "TBD" // TODO: have a cool title.
+title: "Kubernetes 1.27: More fine-grained pod topology spread policies reached beta"
 date: 2023-04-11
-slug: topology-spread-new-features
+slug: fine-grained-pod-topology-spread-features-beta
 evergreen: true
 ---
 

From bbe2382abfe1f96ef1ddca60ad7fd90bc684d348 Mon Sep 17 00:00:00 2001
From: Kensei Nakada <handbomusic@gmail.com>
Date: Mon, 3 Apr 2023 16:52:53 +0900
Subject: [PATCH 085/272] change the section header

---
 content/en/blog/_posts/2023-04-11-topology-spread-features.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/blog/_posts/2023-04-11-topology-spread-features.md b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
index a159117e310..bd908eece73 100644
--- a/content/en/blog/_posts/2023-04-11-topology-spread-features.md
+++ b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
@@ -47,7 +47,7 @@ but other 2 Pods from this replicaset will be unschedulable until more Nodes joi
 The cluster autoscaler provisions new Nodes based on these unschedulable Pods,
 and as a result, the replicas are finally spread over 5 Nodes.
 
-## Take taints/tolerations into consideration when calculating PodTopologySpread skew
+## KEP-3094: Take taints/tolerations into consideration when calculating PodTopologySpread skew
 
 Before this, when we deploy a pod with `podTopologySpread` configured, we'll take all
 affinity nodes(satisfied with pod nodeAffinity and nodeSelector) into consideration

From 89c7e2ed6e9a4a525e591716153f90edc21a4d8a Mon Sep 17 00:00:00 2001
From: Han Kang <hankang@google.com>
Date: Mon, 3 Apr 2023 01:13:52 -0700
Subject: [PATCH 086/272] Update documentation on SLI metrics (#40064)

* update metrics/slis documentation

* Update content/en/docs/reference/instrumentation/slis.md

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

* Update content/en/docs/reference/instrumentation/slis.md

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

* update feature gate doc

* Update content/en/docs/reference/command-line-tools-reference/feature-gates.md

Co-authored-by: Qiming Teng <tengqm@outlook.com>

---------

Co-authored-by: Tim Bannister <tim@scalefactory.com>
Co-authored-by: Qiming Teng <tengqm@outlook.com>
---
 .../command-line-tools-reference/feature-gates.md         | 3 ++-
 content/en/docs/reference/instrumentation/slis.md         | 8 ++++----
 2 files changed, 6 insertions(+), 5 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 56385ff1481..884018118ca 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,7 +84,8 @@ For a reference to old feature gates that are removed, please refer to
 | `CSINodeExpandSecret` | `true` | Beta | 1.27 | |
 | `CSIVolumeHealth` | `false` | Alpha | 1.21 | |
 | `CloudDualStackNodeIPs` | false | Alpha | 1.27 | |
-| `ComponentSLIs` | `false` | Alpha | 1.26 | |
+| `ComponentSLIs` | `false` | Alpha | 1.26 | 1.26 |
+| `ComponentSLIs` | `true` | Beta | 1.27 | |
 | `ContainerCheckpoint` | `false` | Alpha | 1.25 | |
 | `ContextualLogging` | `false` | Alpha | 1.24 | |
 | `CrossNamespaceVolumeDataSource` | `false` | Alpha| 1.26 | |
diff --git a/content/en/docs/reference/instrumentation/slis.md b/content/en/docs/reference/instrumentation/slis.md
index 744df09336e..3b559a398c9 100644
--- a/content/en/docs/reference/instrumentation/slis.md
+++ b/content/en/docs/reference/instrumentation/slis.md
@@ -9,13 +9,13 @@ weight: 20
 
 <!-- overview -->
 
-{{< feature-state for_k8s_version="v1.26" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
 
-As an alpha feature, Kubernetes lets you configure Service Level Indicator (SLI) metrics 
+By default, Kubernetes {{< skew currentVersion >}} publishes Service Level Indicator (SLI) metrics 
 for each Kubernetes component binary. This metric endpoint is exposed on the serving 
-HTTPS port of each component, at the path `/metrics/slis`. You must enable the 
+HTTPS port of each component, at the path `/metrics/slis`. The 
 `ComponentSLIs` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
-for every component from which you want to scrape SLI metrics.
+defaults to enabled for each Kubernetes component as of v1.27.
 
 <!-- body -->
 

From 24b259fa36f46086827ee19d226fd82a5d0b3d9c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Filip=20K=C5=99epinsk=C3=BD?= <atiratree@gmail.com>
Date: Wed, 15 Mar 2023 13:20:43 +0100
Subject: [PATCH 087/272] Promote PodDisruptionBudget
 UnhealthyPodEvictionPolicy to Beta

---
 content/en/docs/concepts/workloads/pods/disruptions.md       | 5 +++++
 .../reference/command-line-tools-reference/feature-gates.md  | 3 ++-
 .../en/docs/tasks/administer-cluster/safely-drain-node.md    | 5 +++++
 content/en/docs/tasks/run-application/configure-pdb.md       | 4 ++--
 4 files changed, 14 insertions(+), 3 deletions(-)

diff --git a/content/en/docs/concepts/workloads/pods/disruptions.md b/content/en/docs/concepts/workloads/pods/disruptions.md
index 25982067532..1d2b33d55f5 100644
--- a/content/en/docs/concepts/workloads/pods/disruptions.md
+++ b/content/en/docs/concepts/workloads/pods/disruptions.md
@@ -136,6 +136,11 @@ against the disruption budget, but workload resources (such as Deployment and St
 are not limited by PDBs when doing rolling upgrades. Instead, the handling of failures
 during application updates is configured in the spec for the specific workload resource.
 
+It is recommended to set `AlwaysAllow` [Unhealthy Pod Eviction Policy](/docs/tasks/run-application/configure-pdb/#unhealthy-pod-eviction-policy)
+to your PodDisruptionBudgets to support eviction of misbehaving applications during a node drain.
+The default behavior is to wait for the application pods to become [healthy](/docs/tasks/run-application/configure-pdb/#healthiness-of-a-pod)
+before the drain can proceed.
+
 When a pod is evicted using the eviction API, it is gracefully
 [terminated](/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination), honoring the
 `terminationGracePeriodSeconds` setting in its [PodSpec](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podspec-v1-core).
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 884018118ca..361370af51a 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
@@ -158,7 +158,8 @@ For a reference to old feature gates that are removed, please refer to
 | `NodeSwap` | `false` | Alpha | 1.22 | |
 | `OpenAPIEnums` | `false` | Alpha | 1.23 | 1.23 |
 | `OpenAPIEnums` | `true` | Beta | 1.24 | |
-| `PDBUnhealthyPodEvictionPolicy` | `false` | Alpha | 1.26 | |
+| `PDBUnhealthyPodEvictionPolicy` | `false` | Alpha | 1.26 | 1.26 |
+| `PDBUnhealthyPodEvictionPolicy` | `true` | Beta | 1.27 | |
 | `PodAndContainerStatsFromCRI` | `false` | Alpha | 1.23 | |
 | `PodDeletionCost` | `false` | Alpha | 1.21 | 1.21 |
 | `PodDeletionCost` | `true` | Beta | 1.22 | |
diff --git a/content/en/docs/tasks/administer-cluster/safely-drain-node.md b/content/en/docs/tasks/administer-cluster/safely-drain-node.md
index 456fd02c7d4..5afcd3eac1c 100644
--- a/content/en/docs/tasks/administer-cluster/safely-drain-node.md
+++ b/content/en/docs/tasks/administer-cluster/safely-drain-node.md
@@ -35,6 +35,11 @@ If availability is important for any applications that run or could run on the n
 that you are draining, [configure a PodDisruptionBudgets](/docs/tasks/run-application/configure-pdb/)
 first and then continue following this guide.
 
+It is recommended to set `AlwaysAllow` [Unhealthy Pod Eviction Policy](/docs/tasks/run-application/configure-pdb/#unhealthy-pod-eviction-policy)
+to your PodDisruptionBudgets to support eviction of misbehaving applications during a node drain.
+The default behavior is to wait for the application pods to become [healthy](/docs/tasks/run-application/configure-pdb/#healthiness-of-a-pod)
+before the drain can proceed.
+
 ## Use `kubectl drain` to remove a node from service
 
 You can use `kubectl drain` to safely evict all of your pods from a
diff --git a/content/en/docs/tasks/run-application/configure-pdb.md b/content/en/docs/tasks/run-application/configure-pdb.md
index ed3eebe6270..b7e219d4ee9 100644
--- a/content/en/docs/tasks/run-application/configure-pdb.md
+++ b/content/en/docs/tasks/run-application/configure-pdb.md
@@ -241,10 +241,10 @@ These pods are tracked via `.status.currentHealthy` field in the PDB status.
 
 ## Unhealthy Pod Eviction Policy
 
-{{< feature-state for_k8s_version="v1.26" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
 
 {{< note >}}
-In order to use this behavior, you must enable the `PDBUnhealthyPodEvictionPolicy`
+This feature is enabled by default. You can disable it by disabling the `PDBUnhealthyPodEvictionPolicy`
 [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
 on the [API server](/docs/reference/command-line-tools-reference/kube-apiserver/).
 {{< /note >}}

From 85292c0290feb4b23ff613538de98f79f0a4d051 Mon Sep 17 00:00:00 2001
From: harshitasao <harshitasao@gmail.com>
Date: Mon, 3 Apr 2023 17:08:25 +0530
Subject: [PATCH 088/272] made the required changes

---
 .../_posts/2023-04-11-kubernetes-1.27-blog.md | 22 +++++++++----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md b/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
index 5a8874f9dea..ba5b715e07b 100644
--- a/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
+++ b/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
@@ -9,7 +9,7 @@ slug: kubernetes-v1-27-release
 
 Announcing the release of Kubernetes v1.27, the first release of 2023!
 
-This release consist of sixty enhancements. Eighteen of those enhancements are entering Alpha, Tweentynine are graduating to Beta, and Thirteen are graduating to Stable.
+This release consist of 60 enhancements. 18 of those enhancements are entering Alpha, 29 are graduating to Beta, and 13 are graduating to Stable.
 
 ## Release theme and logo
 
@@ -22,16 +22,16 @@ The theme for Kubernetes v1.27 is *Chill Vibes*.
 
 It's a little silly, but there were some important shifts in this release that helped inspire the theme. Throughout a typical Kubernetes release cycle, there are several deadlines that features need to meet to remain included. If a feature misses any of these deadlines, there is an exception process they can go through. Handling these exceptions is a very normal part of the release. But v1.27 is the first release that anyone can remember where we didn't receive a single exception request after the enhancements freeze. Even as the release progressed, things remained much calmer than any of us are used to.
 
-There's a specific reason we were able to enjoy a more calm release this time around, and that's all the work that folks put in beind the scenes to improve how we manage the release. That's what this theme celebrates, people putting in the work to make things better for the community.
+There's a specific reason we were able to enjoy a more calm release this time around, and that's all the work that folks put in behind the scenes to improve how we manage the release. That's what this theme celebrates, people putting in the work to make things better for the community.
 
-Special thinks to [Britnee Laverack](https://www.instagram.com/artsyfie/) for creating the logo. Britnee also design the logo for [Kubernetes 1.24: Stargazer](https://kubernetes.io/blog/2022/05/03/kubernetes-1-24-release-announcement/#release-theme-and-logo).
+Special thanks to [Britnee Laverack](https://www.instagram.com/artsyfie/) for creating the logo. Britnee also designed the logo for [Kubernetes 1.24: Stargazer](https://kubernetes.io/blog/2022/05/03/kubernetes-1-24-release-announcement/#release-theme-and-logo).
 
 # What's New (Major Themes)
 
 ## Freeze `k8s.gcr.io` image registry
 
 Replacing the old image registry, [k8s.gcr.io](https://cloud.google.com/container-registry/) with [registry.k8s.io](https://github.com/kubernetes/registry.k8s.io) which has been generally available for several months. The Kubernetes project created and runs the `registry.k8s.io` image registry, which is fully controlled by the community.
-This mean that all subsequent image releases would not be available on the old registry. Freezing  the `k8s.gcr.io` image registry by not pushing any new digests or tags after this release.
+This means that the old registry `k8s.gcr.io` will be frozen and no further images for Kubernetes and related subprojects will be pushed to the old registry. 
 
 What does this change mean for contributors:
 
@@ -41,7 +41,7 @@ What does this change mean for end users:
 
 * This Kubernetes release will not be published to the old registry.
 
-* Patch releases for v1.24, v1.25, and v1.26 will no longer be published to the old registry from April. 
+* Patch releases for v1.24, v1.25, and v1.26 will no longer be published to the old registry after April. 
 
 * Starting in v1.25, the default image registry has been set to `registry.k8s.io`. This value is overridable in kubeadm and kubelet but setting it to `k8s.gcr.io` will fail for new releases after April as they won’t be present in the old registry.
 
@@ -65,9 +65,10 @@ The `schedulingGates` field contains a list of strings, and each string literal
 
 ## Node Service Log Viewer
 
-This feature helps cluster administrators debug issues with services running on nodes by allowing them to query service logs. To use the feature, ensure that the `NodeLogQuery` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled for that node, and that the kubelet configuration options `enableSystemLogHandler` and `enableSystemLogQuery` are both set to true. On Linux we assume that service logs are available either via journald. On Windows we assume that service logs are available in the application log provider. On both operating systems, logs are also available by reading files within `/var/log/`.
+This feature helps cluster administrators debug issues with services running on nodes by allowing them to query service logs. To use the feature, ensure that the `NodeLogQuery` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled for that node, and that the kubelet configuration options `enableSystemLogHandler` and `enableSystemLogQuery` are both set to true. 
+On Linux, we assume that service logs are available via journald. On Windows, we assume that service logs are available in the application log provider. Logs are also available in the `/var/log/` and `C:\var\log` directories on Linux and Windows, respectively.
 
-A node level administrator can try out this alpha feature on all their nodes, or on just a subset. Provided you're authorized to do so.
+A cluster administrator can try out this alpha feature on all their nodes, or on just a subset.
 
 ## ReadWriteOncePod PersistentVolume Access Mode goes to beta 
 
@@ -102,22 +103,21 @@ In Kubernetes v1.25 and v1.26, this behavior toggle was part of the `SELinuxMoun
 
 ## `JobMutableNodeSchedulingDirectives` graduates to GA
 
-This was introduced in v1.22 and started as a beta level, now it's stable. 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 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 was introduced in v1.22 and started as a beta level, now it's stable. 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` 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 and [scheduling gates](/docs/concepts/scheduling-eviction/pod-scheduling-readiness/). Find more details in KEP: [Allow updating scheduling directives of jobs](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/2926-job-mutable-scheduling-directives)
 
 ## Mutable Pod Scheduling Directives goes to beta
 
-This allows a pod to make pod scheduling directives (nodeSelector, affinity) mutable as long as the pod is gated.  It gives the ability to mutate a pods scheduling directives before it is allowed to be scheduled, and gives an external resource controller the ability to influence pod placement while at the same time offload actual pod-to-node assignment to kube-scheduler.
+This allows mutating a pod that is blocked on a scheduling readiness gate with a more constrained node affinity/selector. It gives the ability to mutate a pods scheduling directives before it is allowed to be scheduled, and gives an external resource controller the ability to influence pod placement while at the same time offload actual pod-to-node assignment to kube-scheduler.
 
 This opens the door for a new pattern of adding scheduling features to Kubernetes.  Specifically, building lightweight schedulers that implement features not supported by kube-scheduler, while relying on the existing kube-scheduler to support all upstream features and handle the pod-to-node binding. This pattern should be the preferred one if the custom feature doesn't require implementing a schedule plugin, which entails re-building and maintaining a custom kube-scheduler binary.
 
 ## DownwardAPIHugePages graduates to stable 
 
-Support for `requests.hugepages-<pagesize>` and `limits.hugepages-<pagesize>` is being added to the downward API to be consistent with other resources like cpu, memory, and ephemeral storage. You can find more details in the KEP: [Downward API HugePages](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2053-downward-api-hugepages).
+In kubernetes v1.20, support for `requests.hugepages-<pagesize>` and `limits.hugepages-<pagesize>` was added to the downward API to be consistent with other resources like cpu, memory, and ephemeral storage. This feature graduates to stable in this release. You can find more details in the KEP: [Downward API HugePages](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2053-downward-api-hugepages).
 
 # Other Updates
-
 ## Graduations to stable
 
 This release includes a total of thirteen enhancements promoted to Stable:

From 6e568b89aace66d641168e6242c8b9387c128b11 Mon Sep 17 00:00:00 2001
From: Jan Safranek <jsafrane@redhat.com>
Date: Wed, 15 Mar 2023 10:34:51 +0100
Subject: [PATCH 089/272] Flip SELinuxMountReadWriteOncePod to Beta

Co-authored-by: Qiming Teng <tengqm@outlook.com>
Co-authored-by: Tim Bannister <tim@scalefactory.com>
---
 .../feature-gates.md                          |  3 ++-
 .../security-context.md                       | 27 ++++++++++---------
 2 files changed, 16 insertions(+), 14 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 884018118ca..a4f2488dc50 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
@@ -183,7 +183,8 @@ For a reference to old feature gates that are removed, please refer to
 | `RetroactiveDefaultStorageClass` | `true` | Beta | 1.26 | |
 | `RotateKubeletServerCertificate` | `false` | Alpha | 1.7 | 1.11 |
 | `RotateKubeletServerCertificate` | `true` | Beta | 1.12 | |
-| `SELinuxMountReadWriteOncePod` | `false` | Alpha | 1.25 | |
+| `SELinuxMountReadWriteOncePod` | `false` | Alpha | 1.25 | 1.26 |
+| `SELinuxMountReadWriteOncePod` | `true` | Beta | 1.27 | |
 | `ServiceNodePortStaticSubrange` | `false` | Alpha | 1.27 | |
 | `SizeMemoryBackedVolumes` | `false` | Alpha | 1.20 | 1.21 |
 | `SizeMemoryBackedVolumes` | `true` | Beta | 1.22 | |
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 0f5549c220b..c23ef53396a 100644
--- a/content/en/docs/tasks/configure-pod-container/security-context.md
+++ b/content/en/docs/tasks/configure-pod-container/security-context.md
@@ -440,7 +440,7 @@ To assign SELinux labels, the SELinux security module must be loaded on the host
 
 ### Efficient SELinux volume relabeling
 
-{{< feature-state for_k8s_version="v1.25" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
 
 By default, the container runtime recursively assigns SELinux label to all
 files on all Pod volumes. To speed up this process, Kubernetes can change the
@@ -449,16 +449,16 @@ SELinux label of a volume instantly by using a mount option
 
 To benefit from this speedup, all these conditions must be met:
 
-* Alpha feature gate `SELinuxMountReadWriteOncePod` must be enabled.
+* The [feature gates](/docs/reference/command-line-tools-reference/feature-gates/) `ReadWriteOncePod`
+  and `SELinuxMountReadWriteOncePod` must be enabled.
 * Pod must use PersistentVolumeClaim with `accessModes: ["ReadWriteOncePod"]`.
 * Pod (or all its Containers that use the PersistentVolumeClaim) must
   have `seLinuxOptions` set.
-* The corresponding PersistentVolume must be either a volume that uses a
-  {{< glossary_tooltip text="CSI" term_id="csi" >}} driver, or a volume that uses the
-  legacy `iscsi` volume type.
-  * If you use a volume backed by a CSI driver, that CSI driver must announce that it
-    supports mounting with `-o context` by setting `spec.seLinuxMount: true` in
-    its CSIDriver instance.
+* The corresponding PersistentVolume must be either:
+  * A volume that uses the legacy in-tree `iscsi`, `rbd` or `fc` volume type.
+  * Or a volume that uses a {{< glossary_tooltip text="CSI" term_id="csi" >}} driver.
+    The CSI driver must announce that it supports mounting with `-o context` by setting
+    `spec.seLinuxMount: true` in its CSIDriver instance.
 
 For any other volume types, SELinux relabelling happens another way: the container
 runtime  recursively changes the SELinux label for all inodes (files and directories)
@@ -466,11 +466,12 @@ in the volume.
 The more files and directories in the volume, the longer that relabelling takes.
 
 {{< note >}}
-In Kubernetes 1.25, the kubelet loses track of volume labels after restart. In
-other words, then kubelet may refuse to start Pods with errors similar to  "conflicting
-SELinux labels of volume", while there are no conflicting labels in Pods. Make sure
-nodes are [fully drained](/docs/tasks/administer-cluster/safely-drain-node/)
-before restarting kubelet.
+<!-- remove after Kubernetes v1.30 is released -->
+If you are running Kubernetes v1.25, refer to the v1.25 version of this task page:
+[Configure a Security Context for a Pod or Container](https://v1-25.docs.kubernetes.io/docs/tasks/configure-pod-container/security-context/) (v1.25).  
+There is an important note in that documentation about a situation where the kubelet
+can lose track of volume labels after restart. This deficiency has been fixed
+in Kubernetes 1.26.
 {{< /note >}}
 
 ## Discussion

From a6d1ec99df27b35d04c84084533d9f9b6fe989be Mon Sep 17 00:00:00 2001
From: Daniel Vega-Myhre <105610547+danielvegamyhre@users.noreply.github.com>
Date: Mon, 3 Apr 2023 07:59:51 -0700
Subject: [PATCH 090/272] Add docs for mutable scheduling directives on gated
 Pods (#40000)

* initial commit

* address comments

* Update content/en/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md

Co-authored-by: Aldo Culquicondor <1299064+alculquicondor@users.noreply.github.com>

* adjust phrasing

* Update content/en/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md

Co-authored-by: Qiming Teng <tengqm@outlook.com>

* Update content/en/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md

Co-authored-by: Qiming Teng <tengqm@outlook.com>

---------

Co-authored-by: Aldo Culquicondor <1299064+alculquicondor@users.noreply.github.com>
Co-authored-by: Qiming Teng <tengqm@outlook.com>
---
 .../pod-scheduling-readiness.md               | 26 +++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/content/en/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md b/content/en/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md
index 07064386701..6146cd23d9f 100644
--- a/content/en/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md
+++ b/content/en/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md
@@ -89,6 +89,32 @@ The metric `scheduler_pending_pods` comes with a new label `"gated"` to distingu
 has been tried scheduling but claimed as unschedulable, or explicitly marked as not ready for
 scheduling. You can use `scheduler_pending_pods{queue="gated"}` to check the metric result.
 
+## Mutable Pod Scheduling Directives
+
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
+
+You can mutate scheduling directives of Pods while they have scheduling gates, with certain constraints.
+At a high level, you can only tighten the scheduling directives of a Pod. In other words, the updated 
+directives would cause the Pods to only be able to be scheduled on a subset of the nodes that it would 
+previously match. More concretely, the rules for updating a Pod's scheduling directives are as follows:
+
+1. For `.spec.nodeSelector`, only additions are allowed. If absent, it will be allowed to be set.
+
+2. For `spec.affinity.nodeAffinity`, if nil, then setting anything is allowed.
+
+3. If `NodeSelectorTerms` was empty, it will be allowed to be set.
+   If not empty, then only additions of `NodeSelectorRequirements` to `matchExpressions`
+   or `fieldExpressions` are allowed, and no changes to existing `matchExpressions`
+   and `fieldExpressions` will be allowed. This is because the terms in
+   `.requiredDuringSchedulingIgnoredDuringExecution.NodeSelectorTerms`, are ORed
+   while the expressions in `nodeSelectorTerms[].matchExpressions` and 
+   `nodeSelectorTerms[].fieldExpressions` are ANDed. 
+
+4. For `.preferredDuringSchedulingIgnoredDuringExecution`, all updates are allowed.
+   This is because preferred terms are not authoritative, and so policy controllers
+   don't validate those terms.
+
+
 ## {{% heading "whatsnext" %}}
 
 * Read the [PodSchedulingReadiness KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/3521-pod-scheduling-readiness) for more details

From 27460b23fa05b73697a1436fe02d65923067a910 Mon Sep 17 00:00:00 2001
From: Tim Allclair <tallclair@google.com>
Date: Mon, 3 Apr 2023 08:23:51 -0700
Subject: [PATCH 091/272] AdmissionWebhookMatchConditions feature documentation
 (#40058)

* AdmissionWebhookMatchConditions feature documentation

* #squash ivelichkovich feedback

* #squash sftim feedback

* Correct statement about request.object

* #squash: sftim feedback

* #squash jpbetz feedback

* #squash: denied function removed

* #squash fix match conditions example

* #squash fix expression quoting

* #squash scope authorizatoin check example

* #squash separate RBAC webhook example

* #squash sftim feedback

* #squash add shared client config for example

* Don't use yaml anchors in example
---
 .../extensible-admission-controllers.md       | 44 ++++++++++++++++-
 .../feature-gates.md                          |  2 +
 .../admission-webhook-match-conditions.yaml   | 47 +++++++++++++++++++
 3 files changed, 92 insertions(+), 1 deletion(-)
 create mode 100644 content/en/examples/access/admission-webhook-match-conditions.yaml

diff --git a/content/en/docs/reference/access-authn-authz/extensible-admission-controllers.md b/content/en/docs/reference/access-authn-authz/extensible-admission-controllers.md
index da59b907c48..aa1a61b2e38 100644
--- a/content/en/docs/reference/access-authn-authz/extensible-admission-controllers.md
+++ b/content/en/docs/reference/access-authn-authz/extensible-admission-controllers.md
@@ -719,6 +719,49 @@ webhooks:
 
 The `matchPolicy` for an admission webhooks defaults to `Equivalent`.
 
+### Matching requests: `matchConditions`
+
+{{< feature-state state="alpha" for_k8s_version="v1.27" >}}
+
+{{< note >}}
+Use of `matchConditions` requires the [featuregate](/docs/reference/command-line-tools-reference/feature-gates/)
+`AdmissionWebhookMatchConditions` to be explicitly enabled on the kube-apiserver before this feature can be used.
+{{< /note >}}
+
+You can define _match conditions_for webhooks if you need fine-grained request filtering. These
+conditions are useful if you find that match rules, `objectSelectors` and `namespaceSelectors` still
+doesn't provide the filtering you want over when to call out over HTTP. Match conditions are
+[CEL expressions](/docs/reference/using-api/cel/). All match conditions must evaluate to true for the
+webhook to be called.
+
+Here is an example illustrating a few different uses for match conditions:
+
+{{< codenew file="access/admission-webhook-match-conditions.yaml" >}}
+
+Match conditions have access to the following CEL variables:
+
+- `object` - The object from the incoming request. The value is null for DELETE requests. The object
+  version may be converted based on the [matchPolicy](#matching-requests-matchpolicy).
+- `oldObject` - The existing object. The value is null for CREATE requests.
+- `request` - The request portion of the [AdmissionReview](#request), excluding `object` and `oldObject`.
+- `authorizer` - A CEL Authorizer. May be used to perform authorization checks for the principal
+  (authenticated user) of the request. See
+  [Authz](https://pkg.go.dev/k8s.io/apiserver/pkg/cel/library#Authz) in the Kubernetes CEL library
+  documentation for more details.
+- `authorizer.requestResource` - A shortcut for an authorization check configured with the request
+  resource (group, resource, (subresource), namespace, name).
+
+For more information on CEL expressions, refer to the
+[Common Expression Language in Kubernetes reference](/docs/reference/using-api/cel/).
+
+In the event of an error evaluating a match condition the webhook is never called. Whether to reject
+the request is determined as follows:
+
+1. If **any** match condition evaluated to `false` (regardless of other errors), the API server skips the webhook.
+2. Otherwise:
+    - for [`failurePolicy: Fail`](#failure-policy), reject the request (without calling the webhook).
+    - for [`failurePolicy: Ignore`](#failure-policy), proceed with the request but skip the webhook.
+
 ### Contacting the webhook
 
 Once the API server has determined a request should be sent to a webhook,
@@ -1175,4 +1218,3 @@ cause the control plane components to stop functioning or introduce unknown beha
 If your admission webhooks don't intend to modify the behavior of the Kubernetes control
 plane, exclude the `kube-system` namespace from being intercepted using a
 [`namespaceSelector`](#matching-requests-namespaceselector).
-
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 10c32102134..7741defbe86 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
@@ -56,6 +56,7 @@ For a reference to old feature gates that are removed, please refer to
 
 | Feature | Default | Stage | Since | Until |
 |---------|---------|-------|-------|-------|
+| `AdmissionWebhookMatchConditions` | Alpha | `false` | 1.27 | |
 | `APIListChunking` | `false` | Alpha | 1.8 | 1.8 |
 | `APIListChunking` | `true` | Beta | 1.9 | |
 | `APIPriorityAndFairness` | `false` | Alpha | 1.18 | 1.19 |
@@ -385,6 +386,7 @@ A *General Availability* (GA) feature is also referred to as a *stable* feature.
 
 Each feature gate is designed for enabling/disabling a specific feature:
 
+- `AdmissionWebhookMatchConditions`: Enable [match conditions](/docs/reference/access-authn-authz/extensible-admission-controllers/#matching-requests-matchconditions) on mutating & validating admission webhooks.
 - `APIListChunking`: Enable the API clients to retrieve (`LIST` or `GET`)
   resources from API server in chunks.
 - `APIPriorityAndFairness`: Enable managing request concurrency with
diff --git a/content/en/examples/access/admission-webhook-match-conditions.yaml b/content/en/examples/access/admission-webhook-match-conditions.yaml
new file mode 100644
index 00000000000..96705289a95
--- /dev/null
+++ b/content/en/examples/access/admission-webhook-match-conditions.yaml
@@ -0,0 +1,47 @@
+apiVersion: admissionregistration.k8s.io/v1
+kind: ValidatingWebhookConfiguration
+webhooks:
+- name: my-webhook.example.com
+  matchPolicy: Equivalent
+  rules:
+  - operations: ['CREATE','UPDATE']
+    apiGroups: ['*']
+    apiVersions: ['*']
+    resources: ['*']
+  failurePolicy: 'Ignore' # Fail-open (optional)
+  sideEffects: None
+  clientConfig:
+    service:
+      namespace: my-namespace
+      name: my-webhook
+    caBundle: '<omitted>'
+  matchConditions:
+  - name: 'exclude-leases' # Each match condition must have a unique name
+    expression: '!(request.resource.group == "coordination.k8s.io" && request.resource.resource == "leases")' # Match non-lease resources.
+  - name: 'exclude-kubelet-requests'
+    expression: '!("system:nodes" in request.userInfo.groups)' # Match requests made by non-node users.
+  - name: 'rbac' # Skip RBAC requests, which are handled by the second webhook.
+    expression: 'request.resource.group != "rbac.authorization.k8s.io"'
+
+# This example illustrates the use of the 'authorizer'. The authorization check is more expensive
+# than a simple expression, so in this example it is scoped to only RBAC requests by using a second
+# webhook. Both webhooks can be served by the same endpoint.
+- name: rbac.my-webhook.example.com
+  matchPolicy: Equivalent
+  rules:
+  - operations: ['CREATE','UPDATE']
+    apiGroups: ['rbac.authorization.k8s.io']
+    apiVersions: ['*']
+    resources: ['*']
+  failurePolicy: 'Fail' # Fail-closed (the default)
+  sideEffects: None
+  clientConfig:
+    service:
+      namespace: my-namespace
+      name: my-webhook
+    caBundle: '<omitted>'
+  matchConditions:
+  - name: 'breakglass'
+    # Skip requests made by users authorized to 'breakglass' on this webhook.
+    # The 'breakglass' API verb does not need to exist outside this check.
+    expression: '!authorizer.group("admissionregistration.k8s.io").resource("validatingwebhookconfigurations").name("my-webhook.example.com").check("breakglass").allowed()'

From cf37b594f24d1e7167687651f1c743816975428f Mon Sep 17 00:00:00 2001
From: Joe Betz <jpbetz@google.com>
Date: Mon, 3 Apr 2023 08:55:52 -0700
Subject: [PATCH 092/272] KEP-3488 ValidatingAdmissionPolicy: Enforcement
 actions, audit annotations, and secondary authz (#40098)

* Document auditAnnotations, validationActions and authorizer

* Apply suggestions from code review

Co-authored-by: Qiming Teng <tengqm@outlook.com>

* Apply suggestions from code review

Co-authored-by: Tim Allclair <timallclair@gmail.com>

* Apply feedback

---------

Co-authored-by: Qiming Teng <tengqm@outlook.com>
Co-authored-by: Tim Allclair <timallclair@gmail.com>
---
 .../validating-admission-policy.md            | 61 +++++++++++++++++++
 .../audit-annotations.md                      | 22 +++++++
 .../audit-event-with-audit-annotation.yaml    | 12 ++++
 ...ing-admission-policy-audit-annotation.yaml | 15 +++++
 4 files changed, 110 insertions(+)
 create mode 100644 content/en/examples/access/audit-event-with-audit-annotation.yaml
 create mode 100644 content/en/examples/access/validating-admission-policy-audit-annotation.yaml

diff --git a/content/en/docs/reference/access-authn-authz/validating-admission-policy.md b/content/en/docs/reference/access-authn-authz/validating-admission-policy.md
index 6342fd3994e..86565e42e98 100644
--- a/content/en/docs/reference/access-authn-authz/validating-admission-policy.md
+++ b/content/en/docs/reference/access-authn-authz/validating-admission-policy.md
@@ -92,6 +92,7 @@ metadata:
   name: "demo-binding-test.example.com"
 spec:
   policyName: "demo-policy.example.com"
+  validationActions: [Deny]
   matchResources:
     namespaceSelector:
       matchLabels:
@@ -107,6 +108,37 @@ ValidatingAdmissionPolicy 'demo-policy.example.com' with binding 'demo-binding-t
 
 The above provides a simple example of using ValidatingAdmissionPolicy without a parameter configured.
 
+#### Validation actions
+
+Each `ValidatingAdmissionPolicyBinding` must specify one or more
+`validationActions` to declare how `validations` of a policy are enforced.
+
+The supported `validationActions` are:
+
+- `Deny`: Validation failure results in a denied request.
+- `Warn`: Validation failure is reported to the request client
+  as a [warning](/blog/2020/09/03/warnings/).
+- `Audit`: Validation failure is included in the audit event for the API request.
+
+For example, to both warn clients about a validation failure and to audit the
+validation failures, use:
+
+```yaml
+validationActions: [Warn, Audit]
+```
+
+`Deny` and `Warn` may not be used together since this combination
+needlessly duplicates the validation failure both in the
+API response body and the HTTP warning headers.
+
+A `validation` that evaluates to false is always enforced according to these
+actions. Failures defined by the `failurePolicy` are enforced
+according to these actions only if the `failurePolicy` is set to `Fail` (or unset),
+otherwise the failures are ignored.
+
+See [Audit Annotations: validation falures](/docs/reference/labels-annotations-taints/audit-annotations/#validation-policy-admission-k8s-io-validation_failure)
+for more details about the validation failure audit annotation.
+
 #### Parameter resources
 
 Parameter resources allow a policy configuration to be separate from its definition. 
@@ -159,6 +191,7 @@ metadata:
   name: "replicalimit-binding-test.example.com"
 spec:
   policyName: "replicalimit-policy.example.com"
+  validationActions: [Deny]
   paramRef:
     name: "replica-limit-test.example.com"
   matchResources:
@@ -188,6 +221,7 @@ metadata:
   name: "replicalimit-binding-nontest"
 spec:
   policyName: "replicalimit-policy.example.com"
+  validationActions: [Deny]
   paramRef:
     name: "replica-limit-clusterwide.example.com"
   matchResources:
@@ -219,6 +253,7 @@ metadata:
   name: "replicalimit-binding-global"
 spec:
   policyName: "replicalimit-policy.example.com"
+  validationActions: [Deny]
   params: "replica-limit-clusterwide.example.com"
   matchResources:
     namespaceSelector:
@@ -299,6 +334,12 @@ variables as well as some other useful variables:
 - 'request' - Attributes of the [admission request](/docs/reference/config-api/apiserver-admission.v1/#admission-k8s-io-v1-AdmissionRequest).
 - 'params' - Parameter resource referred to by the policy binding being evaluated. The value is
   null if `ParamKind` is unset.
+- `authorizer` - A CEL Authorizer. May be used to perform authorization checks for the principal
+  (authenticated user) of the request. See
+  [Authz](https://pkg.go.dev/k8s.io/apiserver/pkg/cel/library#Authz) in the Kubernetes CEL library
+  documentation for more details.
+- `authorizer.requestResource` - A shortcut for an authorization check configured with the request
+  resource (group, resource, (subresource), namespace, name).
 	
 The `apiVersion`, `kind`, `metadata.name` and `metadata.generateName` are always accessible from
 the root of the object. No other metadata properties are accessible.
@@ -386,3 +427,23 @@ the request is determined as follows:
 2. Otherwise:
   - for [`failurePolicy: Fail`](#failure-policy), reject the request (without evaluating the policy).
   - for [`failurePolicy: Ignore`](#failure-policy), proceed with the request but skip the policy.
+
+### Audit annotations
+
+`auditAnnotations` may be used to include audit annotations in the audit event of the API request.
+
+For example, here is an admission policy with an audit annotation:
+
+{{< codenew file="access/validating-admission-policy-audit-annotation.yaml" >}}
+
+When an API request is validated with this admission policy, the resulting audit event will look like:
+
+{{< codenew file="access/audit-event-with-audit-annotation.yaml" >}}
+
+In this example the annotation will only be included if the `spec.replicas` of the Deployment is more than
+50, otherwise the CEL expression evalutes to null and the annotation will not be included.
+
+Note that audit annotation keys are prefixed by the name of the `ValidatingAdmissionWebhook` and a `/`. If
+another admission controller, such as an admission webhook, uses the exact same audit annotation key, the 
+value of the first admission controller to include the audit annotation will be included in the audit
+event and all other values will be ignored.
\ No newline at end of file
diff --git a/content/en/docs/reference/labels-annotations-taints/audit-annotations.md b/content/en/docs/reference/labels-annotations-taints/audit-annotations.md
index f950c6457e2..7c076132058 100644
--- a/content/en/docs/reference/labels-annotations-taints/audit-annotations.md
+++ b/content/en/docs/reference/labels-annotations-taints/audit-annotations.md
@@ -108,3 +108,25 @@ to ensure connections are secured properly and to avoid disruption in future rel
 
 There's more information about this in the Go documentation:
 [Rejecting SHA-1 certificates](https://go.dev/doc/go1.18#sha1).
+
+## validation.policy.admission.k8s.io/validation_failure
+
+Example: `validation.policy.admission.k8s.io/validation_failure: '[{"message": "Invalid value", {"policy": "policy.example.com", {"binding": "policybinding.example.com", {"expressionIndex": "1", {"validationActions": ["Audit"]}]'`
+
+Used by Kubernetes version v1.27 and later.
+
+This annotation indicates that a admission policy validation evaluted to false
+for an API request, or that the validation resulted in an error while the policy
+was configured with `failurePolicy: Fail`.
+
+The value of the annotation is a JSON object. The `message` in the JSON
+provides the message about the validation failure.
+
+The `policy`, `binding` and `expressionIndex` in the JSON identifies the
+name of the `ValidatingAdmissionPolicy`, the name of the
+`ValidatingAdmissionPolicyBinding` and the index in the policy `validations` of
+the CEL expressions that failed, respectively.
+
+The `validationActions` shows what actions were taken for this validation failure.
+See [Validating Admission Policy](/docs/reference/access-authn-authz/validating-admission-policy/)
+for more details about `validationActions`.
diff --git a/content/en/examples/access/audit-event-with-audit-annotation.yaml b/content/en/examples/access/audit-event-with-audit-annotation.yaml
new file mode 100644
index 00000000000..6d947745d4b
--- /dev/null
+++ b/content/en/examples/access/audit-event-with-audit-annotation.yaml
@@ -0,0 +1,12 @@
+# the audit event recorded
+{
+    "kind": "Event",
+    "apiVersion": "audit.k8s.io/v1",
+    "annotations": {
+        "demo-policy.example.com/high-replica-count": "Deployment spec.replicas set to 128"
+        # other annotations
+        ...
+    }
+    # other fields
+    ...
+}
diff --git a/content/en/examples/access/validating-admission-policy-audit-annotation.yaml b/content/en/examples/access/validating-admission-policy-audit-annotation.yaml
new file mode 100644
index 00000000000..378fa97247a
--- /dev/null
+++ b/content/en/examples/access/validating-admission-policy-audit-annotation.yaml
@@ -0,0 +1,15 @@
+apiVersion: admissionregistration.k8s.io/v1alpha1
+kind: ValidatingAdmissionPolicy
+metadata:
+  name: "demo-policy.example.com"
+spec:
+  failurePolicy: Fail
+  matchConstraints:
+    resourceRules:
+    - apiGroups:   ["apps"]
+      apiVersions: ["v1"]
+      operations:  ["CREATE", "UPDATE"]
+      resources:   ["deployments"]
+  validations:
+    - key: "high-replica-count"
+      valueExpression: "object.spec.replicas > 50 ? 'Deployment spec.replicas set to ' + string(object.spec.replicas) : null"

From 0d862b9afe63486f18f804efa6847b19445c6844 Mon Sep 17 00:00:00 2001
From: Jiahui Feng <jhf@google.com>
Date: Wed, 22 Mar 2023 13:42:53 -0700
Subject: [PATCH 093/272] message expression and type checking.

---
 .../validating-admission-policy.md            | 120 +++++++++++++++++-
 .../access/deployment-replicas-policy.yaml    |  20 +++
 2 files changed, 139 insertions(+), 1 deletion(-)
 create mode 100644 content/en/examples/access/deployment-replicas-policy.yaml

diff --git a/content/en/docs/reference/access-authn-authz/validating-admission-policy.md b/content/en/docs/reference/access-authn-authz/validating-admission-policy.md
index 86565e42e98..ffb7f96965c 100644
--- a/content/en/docs/reference/access-authn-authz/validating-admission-policy.md
+++ b/content/en/docs/reference/access-authn-authz/validating-admission-policy.md
@@ -446,4 +446,122 @@ In this example the annotation will only be included if the `spec.replicas` of t
 Note that audit annotation keys are prefixed by the name of the `ValidatingAdmissionWebhook` and a `/`. If
 another admission controller, such as an admission webhook, uses the exact same audit annotation key, the 
 value of the first admission controller to include the audit annotation will be included in the audit
-event and all other values will be ignored.
\ No newline at end of file
+event and all other values will be ignored.
+
+### Message expression
+
+To return a more friendly message when the policy rejects a request, we can use a CEL expression
+to composite a message with `spec.validations[i].messageExpression`. Similar to the validation expression,
+a message expression has access to `object`, `oldObject`, `request`, and `params`. Unlike validations,
+message expression must evaluate to a string.
+
+For example, to better inform the user of the reason of denial when the policy refers to a parameter,
+we can have the following validation:
+
+{{< codenew file="access/deployment-replicas-policy.yaml" >}}
+
+After creating a params object that limits the replicas to 3 and setting up the binding,
+when we try to create a deployment with 5 replicas, we will receive the following message.
+
+```
+$ kubectl create deploy --image=nginx nginx --replicas=5
+error: failed to create deployment: deployments.apps "nginx" is forbidden: ValidatingAdmissionPolicy 'deploy-replica-policy.example.com' with binding 'demo-binding-test.example.com' denied request: object.spec.replicas must be no greater than 3
+```
+
+This is more informative than a static message of "too many replicas".
+
+The message expression takes precedence over the static message defined in `spec.validations[i].message` if both are defined.
+However, if the message expression fails to evaluate, the static message will be used instead.
+Additionally, if the message expression evaluates to a multi-line string,
+the evaluation result will be discarded and the static message will be used if present.
+Note that static message is validated against multi-line strings.
+
+### Type checking
+
+When a policy definition is created or updated, the validation process parses the expressions it contains
+and reports any syntax errors, rejecting the definition if any errors are found. 
+Afterward, the referred variables are checked for type errors, including missing fields and type confusion,
+against the matched types of `spec.matchConstraints`.
+The result of type checking can be retrieved from `status.typeChecking`.
+The presence of `status.typeChecking` indicates the completion of type checking,
+and an empty `status.typeChecking` means that no errors were detected.
+
+For example, given the following policy definition:
+
+```yaml
+apiVersion: admissionregistration.k8s.io/v1alpha1
+kind: ValidatingAdmissionPolicy
+metadata:
+  name: "deploy-replica-policy.example.com"
+spec:
+  matchConstraints:
+    resourceRules:
+    - apiGroups:   ["apps"]
+      apiVersions: ["v1"]
+      operations:  ["CREATE", "UPDATE"]
+      resources:   ["deployments"]
+  validations:
+  - expression: "object.replicas > 1" # should be "object.spec.replicas > 1"
+    message: "must be replicated"
+    reason: Invalid
+```
+
+The status will yield the following information:
+
+```yaml
+status:
+  typeChecking:
+    expressionWarnings:
+    - fieldRef: spec.validations[0].expression
+      warning: |-
+        apps/v1, Kind=Deployment: ERROR: <input>:1:7: undefined field 'replicas'
+         | object.replicas > 1
+         | ......^
+```
+
+If multiple resources are matched in `spec.matchConstraints`, all of matched resources will be checked against.
+For example, the following policy definition 
+
+```yaml
+apiVersion: admissionregistration.k8s.io/v1alpha1
+kind: ValidatingAdmissionPolicy
+metadata:
+  name: "replica-policy.example.com"
+spec:
+  matchConstraints:
+    resourceRules:
+    - apiGroups:   ["apps"]
+      apiVersions: ["v1"]
+      operations:  ["CREATE", "UPDATE"]
+      resources:   ["deployments","replicasets"]
+  validations:
+  - expression: "object.replicas > 1" # should be "object.spec.replicas > 1"
+    message: "must be replicated"
+    reason: Invalid
+```
+
+will have multiple types and type checking result of each type in the warning message.
+
+```yaml
+status:
+  typeChecking:
+    expressionWarnings:
+    - fieldRef: spec.validations[0].expression
+      warning: |-
+        apps/v1, Kind=Deployment: ERROR: <input>:1:7: undefined field 'replicas'
+         | object.replicas > 1
+         | ......^
+        apps/v1, Kind=ReplicaSet: ERROR: <input>:1:7: undefined field 'replicas'
+         | object.replicas > 1
+         | ......^
+```
+
+Type Checking has the following limitation:
+
+- No wildcard matching. If `spec.matchConstraints.resourceRules` contains `"*"` in any of `apiGroups`, `apiVersions` or `resources`,
+  the types that `"*"` matches will not be checked.
+- The number of matched types is limited to 10. This is to prevent a policy that manually specifying too many types.
+  to consume excessive computing resources. In the order of ascending group, version, and then resource, 11th combination and beyond are ignored.
+- Type Checking does not affect the policy behavior in any way. Even if the type checking detects errors, the policy will continue
+  to evaluate. If errors do occur during evaluate, the failure policy will decide its outcome.
+- Type Checking does not apply to CRDs, including matched CRD types and reference of paramKind. The support for CRDs will come in future release.
\ No newline at end of file
diff --git a/content/en/examples/access/deployment-replicas-policy.yaml b/content/en/examples/access/deployment-replicas-policy.yaml
new file mode 100644
index 00000000000..23c04fff621
--- /dev/null
+++ b/content/en/examples/access/deployment-replicas-policy.yaml
@@ -0,0 +1,20 @@
+apiVersion: admissionregistration.k8s.io/v1alpha1
+kind: ValidatingAdmissionPolicy
+metadata:
+  name: "deploy-replica-policy.example.com"
+spec:
+  paramKind:
+    group: rules.example.com
+    kind: ReplicaLimit
+    version: v1
+  matchConstraints:
+    resourceRules:
+    - apiGroups:   ["apps"]
+      apiVersions: ["v1"]
+      operations:  ["CREATE", "UPDATE"]
+      resources:   ["deployments"]
+  validations:
+  - expression: "object.spec.replicas <= params.maxReplicas"
+    messageExpression: "'object.spec.replicas must be no greater than ' + string(params.maxReplicas)"
+    reason: Invalid
+

From 60ea174553f53c0426c3fd5a80fe0a9bbda83748 Mon Sep 17 00:00:00 2001
From: harshitasao <harshitasao@gmail.com>
Date: Tue, 4 Apr 2023 01:08:13 +0530
Subject: [PATCH 094/272] made the required changes

---
 .../_posts/2023-04-11-kubernetes-1.27-blog.md | 76 +++++++++++--------
 1 file changed, 46 insertions(+), 30 deletions(-)

diff --git a/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md b/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
index ba5b715e07b..7d933b4119d 100644
--- a/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
+++ b/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
@@ -55,26 +55,48 @@ If enabled, the kubelet will use the `RuntimeDefault` seccomp profile by default
 
 You can find more detailed information about a possible upgrade and downgrade strategy in the related Kubernetes Enhancement Proposal (KEP): [Enable seccomp by default](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2413-seccomp-by-default).
 
+## Mutable scheduling directives for Jobs graduates to GA
+
+This was introduced in v1.22 and started as a beta level, now it's stable. 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` 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 and [scheduling gates](/docs/concepts/scheduling-eviction/pod-scheduling-readiness/).
+Find more details in the KEP:
+[Allow updating scheduling directives of jobs](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/2926-job-mutable-scheduling-directives).
+
+## DownwardAPIHugePages graduates to stable 
+
+In Kubernetes v1.20, support for `requests.hugepages-<pagesize>` and `limits.hugepages-<pagesize>` was added
+to the [downward API](/docs/concepts/workloads/pods/downward-api/) to be consistent with other resources like cpu, memory, and ephemeral storage.
+This feature graduates to stable in this release. You can find more details in the KEP:
+[Downward API HugePages](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2053-downward-api-hugepages).
+
 ## Pod Scheduling Readiness goes to beta 
 
-Pods were considered ready for scheduling once created. Kubernetes scheduler does its due diligence to find nodes to place all pending Pods. However, in a real-world case, some Pods may stay in a "miss-essential-resources" state for a long period. These Pods actually churn the scheduler (and downstream integrators like Cluster AutoScaler) in an unnecessary manner.
+Pods were considered ready for scheduling once created. Kubernetes scheduler does its due diligence to find nodes to place all pending Pods. However, in a real-world case, some Pods may stay in a _missing-essential-resources_ state for a long period. These Pods actually churn the scheduler (and downstream integrators like Cluster Autoscaler) in an unnecessary manner.
 
 By specifying/removing a Pod's `.spec.schedulingGates`, you can control when a Pod is ready to be considered for scheduling.
 
 The `schedulingGates` field contains a list of strings, and each string literal is perceived as a criteria that Pod should be satisfied before considered schedulable. This field can be initialized only when a Pod is created (either by the client, or mutated during admission). After creation, each schedulingGate can be removed in an arbitrary order, but addition of a new scheduling gate is disallowed.
 
-## Node Service Log Viewer
+## Node log access via Kubernetes API
 
 This feature helps cluster administrators debug issues with services running on nodes by allowing them to query service logs. To use the feature, ensure that the `NodeLogQuery` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled for that node, and that the kubelet configuration options `enableSystemLogHandler` and `enableSystemLogQuery` are both set to true. 
-On Linux, we assume that service logs are available via journald. On Windows, we assume that service logs are available in the application log provider. Logs are also available in the `/var/log/` and `C:\var\log` directories on Linux and Windows, respectively.
+On Linux, we assume that service logs are available via journald. On Windows, we assume that service logs are available in the application log provider. You can also fetch logs from the `/var/log/` and `C:\var\log` directories on Linux and Windows, respectively.
 
 A cluster administrator can try out this alpha feature on all their nodes, or on just a subset.
 
-## ReadWriteOncePod PersistentVolume Access Mode goes to beta 
+## ReadWriteOncePod PersistentVolume access mode goes to beta 
 
 ReadWriteOncePod is a new access mode for [PersistentVolumes](/docs/concepts/storage/persistent-volumes/#persistent-volumes) (PVs) and [PersistentVolumeClaims](/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims) (PVCs) introduced in Kubernetes v1.22. This access mode enables you to restrict volume access to a single pod in the cluster, ensuring that only one pod can write to the volume at a time. This can be particularly useful for stateful workloads that require single-writer access to storage.
 
-The ReadWriteOncePod beta adds support for [scheduler preemption](/docs/concepts/scheduling-eviction/pod-priority-preemption/) of pods using ReadWriteOncePod PVCs. Scheduler preemption allows higher-priority pods to preempt lower-priority pods, so that they can start running on the same node. With this release, pods using ReadWriteOncePod PVCs can also be preempted if a higher-priority pod requires the same PVC. For more context [see here](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/2485-read-write-once-pod-pv-access-mode).
+The ReadWriteOncePod beta adds support for [scheduler preemption](/docs/concepts/scheduling-eviction/pod-priority-preemption/)
+of pods that use ReadWriteOncePod PVCs.
+Scheduler preemption allows higher-priority pods to preempt lower-priority pods, for example when a pod (A) with a ReadWriteOncePod PVC is scheduled, and if another pod (B) is found using the same PVC and pod (A) has higher priority, the scheduler will return an "Unschedulable" status and attempt to preempt pod (B).
+For more context, see the KEP: [ReadWriteOncePod PersistentVolume AccessMode](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/2485-read-write-once-pod-pv-access-mode).
 
 
 ## Respect PodTopologySpread after rolling upgrades
@@ -84,59 +106,53 @@ The ReadWriteOncePod beta adds support for [scheduler preemption](/docs/concepts
 With `matchLabelKeys`, users don't need to update the `pod.spec` between different revisions. The controller/operator just needs to set different values to the same `label` key for different revisions. The scheduler will assume the values automatically based on `matchLabelKeys`. For example, if users use Deployment, they can use the label keyed with `pod-template-hash`, which is added automatically by the Deployment controller, to distinguish between different revisions in a single Deployment.
 
 
-## Speed up SELinux volume relabeling using mounts
+## Faster SELinux volume relabeling using mounts
 
 In this release, how SELinux labels are applied to volumes used by Pods is graduating to beta. This feature speeds up container startup by mounting volumes with the correct SELinux label instead of changing each file on the volumes recursively. Linux kernel with SELinux support allows the first mount of a volume to set SELinux label on the whole volume using `-o context=` mount option. This way, all files will have assigned the given label in a constant time, without recursively walking through the whole volumes.
 
-`context` mount option cannot be applied to bind-mounts or re-mounts of already mounted volumes. Since it's a CSI driver that does the first mount of a volume, it must be the CSI driver who actually applies this mount option. We added a new field `SELinuxMount` to CSI Driver object, so CSI drivers can announce if they support `-o context` mount option.
+The `context` mount option cannot be applied to bind mounts or re-mounts of already mounted volumes.
+For CSI storage, a CSI driver does the first mount of a volume, and so it must be the CSI driver that actually
+applies this mount option. We added a new field `SELinuxMount` to CSIDriver objects, so that drivers can
+announce whether they support the `-o context` mount option.
 
-If Kubernetes knows SELinux label of a Pod **and** CSI driver responsible for a pod's volume announces `SELinuxMount: true` **and** the volume has Access Mode `ReadWriteOncePod`, then it will ask the CSI driver to mount the volume with mount option `context=` **and** it will tell the container runtime not to relabel content of the volume - all files already have the right label. Get more information on the KEP: [Speed up SELinux volume relabeling using mounts](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1710-selinux-relabeling)
+If Kubernetes knows the SELinux label of a Pod **and** the  CSI driver responsible for a pod's volume
+announces `SELinuxMount: true` **and** the volume has Access Mode `ReadWriteOncePod`, then it
+will ask the CSI driver to mount the volume with mount option `context=` **and** it will tell the container
+runtime not to relabel content of the volume (because all files already have the right label).
+Get more information on this from the KEP: [Speed up SELinux volume relabeling using mounts](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1710-selinux-relabeling).
 
 ## Robust VolumeManager reconstruction goes to beta
 
-This is a VolumeManager refactoring that allows kubelet to populate additional information about how existing volumes are mounted during the kubelet startup. In general, this makes volume cleanup more robust. 
-By adding `NewVolumeManagerReconstruction` feature gate and enabling it by default to enable improved discovery of mounted volumes during kubelet startup.
+This is a volume manager refactoring that allows the kubelet to populate additional information about how
+existing volumes are mounted during the kubelet startup. In general, this makes volume cleanup more robust. 
+By adding `NewVolumeManagerReconstruction` feature gate and enabling it by default will enhance the discovery of mounted volumes during kubelet startup.
 
 Before Kubernetes v1.25, the kubelet used different default behavior for discovering mounted volumes during the kubelet startup. If you disable this feature gate (it's enabled by default), you select the legacy discovery behavior.
 
 In Kubernetes v1.25 and v1.26, this behavior toggle was part of the `SELinuxMountReadWriteOncePod` feature gate.
 
-## `JobMutableNodeSchedulingDirectives` graduates to GA
-
-This was introduced in v1.22 and started as a beta level, now it's stable. 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` 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 and [scheduling gates](/docs/concepts/scheduling-eviction/pod-scheduling-readiness/). Find more details in KEP: [Allow updating scheduling directives of jobs](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/2926-job-mutable-scheduling-directives)
-
 ## Mutable Pod Scheduling Directives goes to beta
 
 This allows mutating a pod that is blocked on a scheduling readiness gate with a more constrained node affinity/selector. It gives the ability to mutate a pods scheduling directives before it is allowed to be scheduled, and gives an external resource controller the ability to influence pod placement while at the same time offload actual pod-to-node assignment to kube-scheduler.
 
 This opens the door for a new pattern of adding scheduling features to Kubernetes.  Specifically, building lightweight schedulers that implement features not supported by kube-scheduler, while relying on the existing kube-scheduler to support all upstream features and handle the pod-to-node binding. This pattern should be the preferred one if the custom feature doesn't require implementing a schedule plugin, which entails re-building and maintaining a custom kube-scheduler binary.
 
-## DownwardAPIHugePages graduates to stable 
+## Feature graduations and deprecations in Kubernetes v1.27
+### Graduations to stable
 
-In kubernetes v1.20, support for `requests.hugepages-<pagesize>` and `limits.hugepages-<pagesize>` was added to the downward API to be consistent with other resources like cpu, memory, and ephemeral storage. This feature graduates to stable in this release. You can find more details in the KEP: [Downward API HugePages](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2053-downward-api-hugepages).
+This release includes a total of 9 enhancements promoted to Stable:
 
-# Other Updates
-## Graduations to stable
-
-This release includes a total of thirteen enhancements promoted to Stable:
-
-* [Mutable scheduling directives for suspended Jobs](https://github.com/kubernetes/enhancements/issues/2926)
-* [Add downward API support for hugepages](https://github.com/kubernetes/enhancements/issues/2053)
-* [Kubelet option to enable seccomp by default](https://github.com/kubernetes/enhancements/issues/2413)
 * [Default container annotation that to be used by kubectl](https://github.com/kubernetes/enhancements/issues/2227)
 * [TimeZone support in CronJob](https://github.com/kubernetes/enhancements/issues/3140)
 * [Expose metrics about resource requests and limits that represent the pod model](https://github.com/kubernetes/enhancements/issues/1748)
 * [Server Side Unknown Field Validation](https://github.com/kubernetes/enhancements/issues/2885)
 * [Node Topology Manager](https://github.com/kubernetes/enhancements/issues/693)
-* [Freeze k8s.gcr.io image registry](https://github.com/kubernetes/enhancements/issues/3720)
 * [Add gRPC probe to Pod.Spec.Container.{Liveness,Readiness,Startup} Probe](https://github.com/kubernetes/enhancements/issues/2727)
 * [Add configurable grace period to probes](https://github.com/kubernetes/enhancements/issues/2238)
 * [OpenAPI v3](https://github.com/kubernetes/enhancements/issues/2896)
-* [Stay on supported go versions](https://github.com/kubernetes/enhancements/issues/3744)
+* [Stay on supported Go versions](https://github.com/kubernetes/enhancements/issues/3744)
 
-## Deprecations and removals
+### Deprecations and removals
 
 This release saw several removals:
 
@@ -180,7 +196,7 @@ The [CNCF K8s DevStats](https://k8s.devstats.cncf.io/d/12/dashboards?orgId=1&ref
 
 In the v1.27 release cycle, which [ran for 14 weeks](https://github.com/kubernetes/sig-release/tree/master/releases/release-1.27) (January 9 to April 11), we saw contributions from [1020 companies](https://k8s.devstats.cncf.io/d/9/companies-table?orgId=1&var-period_name=v1.26.0%20-%20now&var-metric=contributions) and [1603 individuals](https://k8s.devstats.cncf.io/d/66/developer-activity-counts-by-companies?orgId=1&var-period_name=v1.26.0%20-%20now&var-metric=contributions&var-repogroup_name=Kubernetes&var-repo_name=kubernetes%2Fkubernetes&var-country_name=All&var-companies=All).
 
-## Upcoming Release Webinar
+## Upcoming release webinar
 
 Join members of the Kubernetes v1.27 release team on <date> to learn about the major features of this release, as well as deprecations and removals to help plan for upgrades. For more information and registration, visit the [event page](#) on the CNCF Online Programs site.
 

From e16de4e8bea60fe7aed1241f0ab2cdf759a8889a Mon Sep 17 00:00:00 2001
From: Aravindh Puthiyaparambil <aravindh@redhat.com>
Date: Tue, 14 Mar 2023 13:59:35 -0700
Subject: [PATCH 095/272] KEP-2258: Node log query documentation

---
 .../cluster-administration/system-logs.md     | 47 +++++++++++++++++++
 .../feature-gates.md                          |  1 +
 2 files changed, 48 insertions(+)

diff --git a/content/en/docs/concepts/cluster-administration/system-logs.md b/content/en/docs/concepts/cluster-administration/system-logs.md
index 6e731ade02b..2c7e29ab548 100644
--- a/content/en/docs/concepts/cluster-administration/system-logs.md
+++ b/content/en/docs/concepts/cluster-administration/system-logs.md
@@ -231,6 +231,53 @@ Similar to the container logs, you should rotate system component logs in the `/
 In Kubernetes clusters created by the `kube-up.sh` script, log rotation is configured by the `logrotate` tool.
 The `logrotate` tool rotates logs daily, or once the log size is greater than 100MB.
 
+## Log query
+
+{{< feature-state for_k8s_version="v1.27" state="alpha" >}}
+
+To help with debugging issues on nodes, Kubernetes v1.27 introduced a feature that allows viewing logs of services
+running on the node. To use the feature, ensure that the `NodeLogQuery`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled for that node, and that the
+kubelet configuration options `enableSystemLogHandler` and `enableSystemLogQuery` are both set to true. On Linux
+we assume that service logs are available via journald. On Windows we assume that service logs are available
+in the application log provider. On both operating systems, logs are also available by reading files within
+`/var/log/`.
+
+Provided you are authorized to interact with node objects, you can try out this alpha feature on all your nodes or
+just a subset. Here is an example to retrieve the kubelet service logs from a node:
+```shell
+# Fetch kubelet logs from a node named node-1.example
+kubectl get --raw "/api/v1/nodes/node-1.example/proxy/logs/?query=kubelet"
+```
+
+You can also fetch files, provided that the files are in a directory that the kubelet allows for log
+fetches. For example, you can fetch a log from `/var/log` on a Linux node:
+```shell
+kubectl get --raw "/api/v1/nodes/<insert-node-name-here>/proxy/logs/?query=/<insert-log-file-name-here>"
+```
+
+The kubelet uses heuristics to retrieve logs. This helps if you are not aware whether a given system service is
+writing logs to the operating system's native logger like journald or to a log file in `/var/log/`. The heuristics
+first checks the native logger and if that is not available attempts to retrieve the first logs from
+`/var/log/<servicename>` or `/var/log/<servicename>.log` or `/var/log/<servicename>/<servicename>.log`.
+
+The complete list of options that can be used are:
+
+Option | Description
+------ | -----------
+`boot` | boot show messages from a specific system boot
+`pattern` | pattern filters log entries by the provided PERL-compatible regular expression
+`query` | query specifies services(s) or files from which to return logs (required)
+`sinceTime` | an [RFC3339](https://www.rfc-editor.org/rfc/rfc3339) timestamp from which to show logs (inclusive)
+`untilTime` | an [RFC3339](https://www.rfc-editor.org/rfc/rfc3339) timestamp until which to show logs (inclusive)
+`tailLines` | specify how many lines from the end of the log to retrieve; the default is to fetch the whole log
+
+Example of a more complex query:
+```shell
+# Fetch kubelet logs from a node named node-1.example that have the word "error"
+kubectl get --raw "/api/v1/nodes/node-1.example/proxy/logs/?query=kubelet&pattern=error"
+```
+
 ## {{% heading "whatsnext" %}}
 
 * Read about the [Kubernetes Logging Architecture](/docs/concepts/cluster-administration/logging/)
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 626cc6931f6..b43a12359bb 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
@@ -151,6 +151,7 @@ For a reference to old feature gates that are removed, please refer to
 | `NetworkPolicyStatus` | `false` | Alpha | 1.24 |  |
 | `NodeInclusionPolicyInPodTopologySpread` | `false` | Alpha | 1.25 | 1.25 |
 | `NodeInclusionPolicyInPodTopologySpread` | `true` | Beta | 1.26 | |
+| `NodeLogQuery` | `false` | Alpha | 1.27 | |
 | `NodeOutOfServiceVolumeDetach` | `false` | Alpha | 1.24 | 1.25 |
 | `NodeOutOfServiceVolumeDetach` | `true` | Beta | 1.26 | |
 | `NodeSwap` | `false` | Alpha | 1.22 | |

From 07bfd16069f16344e5c8d0999b15b82ab35aa55c Mon Sep 17 00:00:00 2001
From: Ryan Phillips <rphillips@redhat.com>
Date: Mon, 3 Apr 2023 16:37:58 -0500
Subject: [PATCH 096/272] terminationGracePeriodSeconds: stable in 1.27

---
 .../configure-liveness-readiness-startup-probes.md              | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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 0f7d9ecc4f9..bafa4e36992 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
@@ -511,7 +511,7 @@ to resolve it.
 
 ### Probe-level `terminationGracePeriodSeconds`
 
-{{< feature-state for_k8s_version="v1.25" state="beta" >}}
+{{< feature-state for_k8s_version="v1.27" state="stable" >}}
 
 Prior to release 1.21, the pod-level `terminationGracePeriodSeconds` was used
 for terminating a container that failed its liveness or startup probe. This

From 618a942f9ee0eccbada6a22e96fd78d71b57e1f0 Mon Sep 17 00:00:00 2001
From: Daniel Vega-Myhre <danielvm@google.com>
Date: Tue, 14 Mar 2023 17:04:09 +0000
Subject: [PATCH 097/272] document elastic indexed jobs

---
 .../en/docs/concepts/workloads/controllers/job.md   | 13 +++++++++++++
 .../command-line-tools-reference/feature-gates.md   |  7 ++++++-
 2 files changed, 19 insertions(+), 1 deletion(-)

diff --git a/content/en/docs/concepts/workloads/controllers/job.md b/content/en/docs/concepts/workloads/controllers/job.md
index 3e0360cc1b4..20b655588d5 100644
--- a/content/en/docs/concepts/workloads/controllers/job.md
+++ b/content/en/docs/concepts/workloads/controllers/job.md
@@ -849,6 +849,19 @@ checking if the Job has the annotation
 this annotation from Jobs. Instead, you can recreate the Jobs to ensure they
 are tracked using Pod finalizers.
 
+### Elastic Indexed Jobs
+
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
+
+You can scale Indexed Jobs up or down by mutating both `.spec.parallelism` 
+and `.spec.completions` together such that `.spec.parallelism == .spec.completions`. 
+When the `ElasticIndexedJob`[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+on the [API server](/docs/reference/command-line-tools-reference/kube-apiserver/)
+is disabled, `.spec.completions` is immutable.
+
+Use cases for elastic Indexed Jobs include batch workloads which require 
+scaling an indexed Job, such as MPI, Horovord, Ray, and PyTorch training jobs.
+
 ## Alternatives
 
 ### Bare Pods
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 a45aa27baa4..7c3bb4a33a7 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
@@ -96,6 +96,7 @@ For a reference to old feature gates that are removed, please refer to
 | `DisableCloudProviders` | `false` | Alpha | 1.22 | |
 | `DisableKubeletCloudCredentialProviders` | `false` | Alpha | 1.23 | |
 | `DynamicResourceAllocation` | `false` | Alpha | 1.26 | |
+| `ElasticIndexedJob` | `true` | Beta` | 1.27 | |
 | `EventedPLEG` | `false` | Alpha | 1.26 | 1.26 |
 | `EventedPLEG` | `false` | Beta | 1.27 | - |
 | `ExpandedDNSConfig` | `false` | Alpha | 1.22 | 1.25 |
@@ -511,8 +512,12 @@ Each feature gate is designed for enabling/disabling a specific feature:
   [downward API](/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information).
 - `DryRun`: Enable server-side [dry run](/docs/reference/using-api/api-concepts/#dry-run) requests
   so that validation, merging, and mutation can be tested without committing.
-- `DynamicResourceAllocation": Enables support for resources with custom parameters and a lifecycle
+- `DynamicResourceAllocation`: Enables support for resources with custom parameters and a lifecycle
   that is independent of a Pod.
+- `ElasticIndexedJob`: Enables Indexed Jobs to be scaled up or down by mutating both
+  `spec.completions` and `spec.parallelism` together such that `spec.completions == spec.parallelism`.
+  See docs on [elastic Indexed Jobs](docs/concepts/workloads/controllers/job#elastic-indexed-jobs)
+  for more details.
 - `EndpointSliceTerminatingCondition`: Enables EndpointSlice `terminating` and `serving`
    condition fields.
 - `EfficientWatchResumption`: Allows for storage-originated bookmark (progress

From f736f8ff055ccc38fd9e87badf8f00aed1c942ae Mon Sep 17 00:00:00 2001
From: kemkemG0 <kenshin.jpsdeveloper@gmail.com>
Date: Mon, 3 Apr 2023 18:13:45 -0700
Subject: [PATCH 098/272] fix japanese wording

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

diff --git a/content/ja/docs/concepts/overview/_index.md b/content/ja/docs/concepts/overview/_index.md
index 89935936589..d4f4a91e473 100644
--- a/content/ja/docs/concepts/overview/_index.md
+++ b/content/ja/docs/concepts/overview/_index.md
@@ -70,7 +70,7 @@ Kubernetesを使うとデプロイしたコンテナのあるべき状態を記
 * **自己修復**
 Kubernetesは、処理が失敗したコンテナを再起動し、コンテナを入れ替え、定義したヘルスチェックに応答しないコンテナを強制終了します。処理の準備ができるまでは、クライアントに通知しません。
 * **機密情報と構成管理**
-Kubernetesは、パスワードやOAuthトークン、SSHキーのよう機密の情報を保持し、管理することができます。機密情報をデプロイし、コンテナイメージを再作成することなくアプリケーションの構成情報を更新することができます。スタック構成の中で機密情報を晒してしまうこともありません。
+Kubernetesは、パスワードやOAuthトークン、SSHキーなどの機密の情報を保持し、管理することができます。機密情報をデプロイし、コンテナイメージを再作成することなくアプリケーションの構成情報を更新することができます。スタック構成の中で機密情報を晒してしまうこともありません。
 
 ## Kubernetesにないもの
 

From eaf9199d071a613632b74e7f3b1c60cd12fdd47d Mon Sep 17 00:00:00 2001
From: Moshe Levi <moshele@nvidia.com>
Date: Tue, 14 Mar 2023 01:58:36 +0200
Subject: [PATCH 099/272] doc: extend PodResources API for Dynamic Resource
 Allocation

Signed-off-by: Moshe Levi <moshele@nvidia.com>
---
 .../compute-storage-net/device-plugins.md     | 62 +++++++++++++++++++
 .../dynamic-resource-allocation.md            |  6 ++
 .../feature-gates.md                          |  7 +++
 3 files changed, 75 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 a241ccee3d4..537bde377ca 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
@@ -213,6 +213,7 @@ for these devices:
 service PodResourcesLister {
     rpc List(ListPodResourcesRequest) returns (ListPodResourcesResponse) {}
     rpc GetAllocatableResources(AllocatableResourcesRequest) returns (AllocatableResourcesResponse) {}
+    rpc Get(GetPodResourcesRequest) returns (GetPodResourcesResponse) {}
 }
 ```
 
@@ -223,6 +224,14 @@ id of exclusively allocated CPUs, device id as it was reported by device plugins
 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.
 
+Starting from Kubernetes v1.27, the `List` enpoint can provide information on resources
+of running pods allocated in `ResourceClaims` by the `DynamicResourceAllocation` API. To enable
+this feature `kubelet` must be started with the following flags:
+
+```
+--feature-gates=DynamicResourceAllocation=true,KubeletPodResourcesDynamiceResources=true
+```
+
 ```gRPC
 // ListPodResourcesResponse is the response returned by List function
 message ListPodResourcesResponse {
@@ -242,6 +251,7 @@ message ContainerResources {
     repeated ContainerDevices devices = 2;
     repeated int64 cpu_ids = 3;
     repeated ContainerMemory memory = 4;
+    repeated DynamicResource dynamic_resources = 5;
 }
 
 // ContainerMemory contains information about memory and hugepages assigned to a container
@@ -267,6 +277,28 @@ message ContainerDevices {
     repeated string device_ids = 2;
     TopologyInfo topology = 3;
 }
+
+// DynamicResource contains information about the devices assigned to a container by Dynamic Resource Allocation
+message DynamicResource {
+    string class_name = 1;
+    string claim_name = 2;
+    string claim_namespace = 3;
+    repeated ClaimResource claim_resources = 4;
+}
+
+// ClaimResource contains per-plugin resource information
+message ClaimResource {
+    repeated CDIDevice cdi_devices = 1 [(gogoproto.customname) = "CDIDevices"];
+}
+
+// CDIDevice specifies a CDI device information
+message CDIDevice {
+    // Fully qualified CDI device name
+    // for example: vendor.com/gpu=gpudevice1
+    // see more details in the CDI specification:
+    // https://github.com/container-orchestrated-devices/container-device-interface/blob/main/SPEC.md
+    string name = 1;
+}
 ```
 {{< note >}}
 cpu_ids in the `ContainerResources` in the `List` endpoint correspond to exclusive CPUs allocated
@@ -333,6 +365,36 @@ Support for the `PodResourcesLister service` requires `KubeletPodResources`
 [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) to be enabled.
 It is enabled by default starting with Kubernetes 1.15 and is v1 since Kubernetes 1.20.
 
+### `Get` gRPC endpoint {#grpc-endpoint-get}
+
+{{< feature-state state="alpha" for_k8s_version="v1.27" >}}
+
+The `Get` endpoint provides information on resources of a running Pod. It exposes information
+similar to those described in the `List` endpoint. The `Get` endpoint requires `PodName`
+and `PodNamespace` of the running Pod.
+
+```gRPC
+// GetPodResourcesRequest contains information about the pod
+message GetPodResourcesRequest {
+    string pod_name = 1;
+    string pod_namespace = 2;
+}
+```
+
+To enable this feature, you must start your kubelet services with the following flag:
+
+```
+--feature-gates=KubeletPodResourcesGet=true
+```
+
+The `Get` endpoint can provide Pod information related to dynamic resources
+allocated by the dynamic resource allocation API. To enable this feature, you must
+ensure your kubelet services are started with the following flags:
+
+```
+--feature-gates=KubeletPodResourcesGet=true,DynamicResourceAllocation=true,KubeletPodResourcesDynamiceResources=true
+```
+
 ## Device plugin integration with the Topology Manager
 
 {{< feature-state for_k8s_version="v1.18" state="beta" >}}
diff --git a/content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md b/content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md
index e1c468f58f0..b2bca19c36b 100644
--- a/content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md
+++ b/content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md
@@ -162,6 +162,12 @@ gets scheduled onto one node and then cannot run there, which is bad because
 such a pending Pod also blocks all other resources like RAM or CPU that were
 set aside for it.
 
+## Monitoring resources
+
+The kubelet provides a gRPC service to enable discovery of dynamic resources of
+running Pods. For more information on the gRPC endpoints, see the
+[resource allocation reporting](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#monitoring-device-plugin-resources).
+
 ## Limitations
 
 The scheduler plugin must be involved in scheduling Pods which use
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 626cc6931f6..cb56ed88416 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
@@ -125,8 +125,10 @@ For a reference to old feature gates that are removed, please refer to
 | `KubeletInUserNamespace` | `false` | Alpha | 1.22 | |
 | `KubeletPodResources` | `false` | Alpha | 1.13 | 1.14 |
 | `KubeletPodResources` | `true` | Beta | 1.15 | |
+| `KubeletPodResourcesGet` | `false` | Alpha | 1.27 | |
 | `KubeletPodResourcesGetAllocatable` | `false` | Alpha | 1.21 | 1.22 |
 | `KubeletPodResourcesGetAllocatable` | `true` | Beta | 1.23 | |
+| `KubeletPodResourcesDynamicResources` | `false` | Alpha | 1.27 | |
 | `KubeletTracing` | `false` | Alpha | 1.25 | |
 | `LegacyServiceAccountTokenTracking` | `false` | Alpha | 1.25 | |
 | `LocalStorageCapacityIsolationFSQuotaMonitoring` | `false` | Alpha | 1.15 | - |
@@ -578,9 +580,14 @@ Each feature gate is designed for enabling/disabling a specific feature:
 - `KubeletPodResources`: Enable the kubelet's pod resources gRPC endpoint. See
   [Support Device Monitoring](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/606-compute-device-assignment/README.md)
   for more details.
+- `KubeletPodResourcesGet`: Enable the `Get` gRPC endpoint on kubelet's for Pod resources.
+  This API augments the [resource allocation reporting](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#monitoring-device-plugin-resources).
 - `KubeletPodResourcesGetAllocatable`: Enable the kubelet's pod resources
   `GetAllocatableResources` functionality. This API augments the
   [resource allocation reporting](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#monitoring-device-plugin-resources)
+- `KubeletPodResourcesDynamiceResources`: Extend the kubelet's pod resources gRPC endpoint to
+  to include resources allocated in `ResourceClaims` via `DynamicResourceAllocation` API.
+  See [resource allocation reporting](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#monitoring-device-plugin-resources) for more details.
   with informations about the allocatable resources, enabling clients to properly
   track the free compute resources on a node.
 - `KubeletTracing`: Add support for distributed tracing in the kubelet.

From a8c4876d4d624edfe75d668ec57253a6a560b1e4 Mon Sep 17 00:00:00 2001
From: niranjandarshann <niranjan.darshan@india.nec.com>
Date: Tue, 4 Apr 2023 13:24:50 +0530
Subject: [PATCH 100/272] Fixed  Incorrect Command At Tutorial #40473

---
 .../docs/tutorials/kubernetes-basics/update/update-intro.html   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/tutorials/kubernetes-basics/update/update-intro.html b/content/en/docs/tutorials/kubernetes-basics/update/update-intro.html
index 62d16e5851d..0c2a3eaca5b 100644
--- a/content/en/docs/tutorials/kubernetes-basics/update/update-intro.html
+++ b/content/en/docs/tutorials/kubernetes-basics/update/update-intro.html
@@ -144,7 +144,7 @@ description: |-
                <p>First, check that the app is running. To find the exposed IP address and port, run the <code>describe service</code> command:</p>
                <p><code><b>kubectl describe services/kubernetes-bootcamp</b></code></p>
                <p>Create an environment variable called <tt>NODE_PORT</tt> that has the value of the Node port assigned:</p>
-               <p><code><b>export NODE_PORT="$(kubectl get services/kubernetes-bootcamp -o go-template='{{(index .spec.ports 0).nodePort}}')</b></code><br />
+               <p><code><b>export NODE_PORT="$(kubectl get services/kubernetes-bootcamp -o go-template='{{(index .spec.ports 0).nodePort}}')"</b></code><br />
                   <code><b>echo "NODE_PORT=$NODE_PORT"</b></code></p>
                <p>Next, do a <code>curl</code> to the the exposed IP and port:</p>
                <p><code><b>curl http://"$(minikube ip):$NODE_PORT"</b></code></p>

From dd444636217a65e4ec8824a4051e66efa607be92 Mon Sep 17 00:00:00 2001
From: Antonio Ojea <antonio.ojea.garcia@gmail.com>
Date: Tue, 4 Apr 2023 13:18:08 +0200
Subject: [PATCH 101/272] Update
 content/en/docs/reference/networking/virtual-ips.md

Co-authored-by: Qiming Teng <tengqm@outlook.com>
---
 content/en/docs/reference/networking/virtual-ips.md | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/content/en/docs/reference/networking/virtual-ips.md b/content/en/docs/reference/networking/virtual-ips.md
index a33b08da067..5d07a7076bc 100644
--- a/content/en/docs/reference/networking/virtual-ips.md
+++ b/content/en/docs/reference/networking/virtual-ips.md
@@ -316,12 +316,17 @@ Users now will be able to inspect the IP addresses assigned to their Services, a
 new network APIs, like Gateway API, can use this new object to extend the Kubernetes
 networking capabilities overcoming the limitations of current Services API.
 
-```bash
-$ kubectl get services
+```shell
+kubectl get services
+```
+```
 NAME         TYPE        CLUSTER-IP        EXTERNAL-IP   PORT(S)   AGE
 kubernetes   ClusterIP   2001:db8:1:2::1   <none>        443/TCP   3d1h
-
-$ kubectl get ipaddresses
+```
+```shell
+kubectl get ipaddresses
+```
+```
 NAME              PARENTREF
 2001:db8:1:2::1   services/default/kubernetes
 2001:db8:1:2::a   services/kube-system/kube-dns

From f674460775e23a2f3c835f0b30f73020b62baf29 Mon Sep 17 00:00:00 2001
From: Antonio Ojea <aojea@google.com>
Date: Tue, 4 Apr 2023 11:33:45 +0000
Subject: [PATCH 102/272] enable v1alpha1 networking api group@

---
 content/en/docs/reference/networking/virtual-ips.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/content/en/docs/reference/networking/virtual-ips.md b/content/en/docs/reference/networking/virtual-ips.md
index 5d07a7076bc..586221ad9f3 100644
--- a/content/en/docs/reference/networking/virtual-ips.md
+++ b/content/en/docs/reference/networking/virtual-ips.md
@@ -300,7 +300,8 @@ IP addresses that are no longer used by any Services.
 
 {{< feature-state for_k8s_version="v1.27" state="alpha" >}}
 If you enable the `MultiCIDRServiceAllocator`
-[feature gate](/docs/reference/command-line-tools-reference/feature-gates/),
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) and the
+[networking.k8s.io/v1alpha1 API group](https://kubernetes.io/docs/tasks/administer-cluster/enable-disable-api/),
 the control plane replaces the existing etcd allocator with a new one, using IPAddress
 objects instead of an internal global allocation map.  The ClusterIP address
 associated to each `Service` will have a referenced IPAddress object.

From 8c906eaab277aa12c6e363a1254081ebafa6f37b Mon Sep 17 00:00:00 2001
From: Katrina Verey <katrina.verey@shopify.com>
Date: Tue, 4 Apr 2023 08:23:53 -0400
Subject: [PATCH 103/272] Add docs for ApplySet-based pruning in kubectl apply
 (#39818)

* Documentation for ApplySet-based pruning (KEP3659)

* Apply suggestions from code review

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

* Add ApplySet labels and annotations to well-known list

* Minor fixups

* Address feedback on label/annotation listing

* Apply suggestions from code review

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

* fix label vs annotation copy-paste errors

* Update prefix to kubernetes.io

---------

Co-authored-by: Tim Bannister <tim@scalefactory.com>
---
 .../labels-annotations-taints/_index.md       | 63 ++++++++++++++
 .../declarative-config.md                     | 84 +++++++++++++------
 2 files changed, 123 insertions(+), 24 deletions(-)

diff --git a/content/en/docs/reference/labels-annotations-taints/_index.md b/content/en/docs/reference/labels-annotations-taints/_index.md
index 35723ced33a..80603b4a2fa 100644
--- a/content/en/docs/reference/labels-annotations-taints/_index.md
+++ b/content/en/docs/reference/labels-annotations-taints/_index.md
@@ -92,6 +92,69 @@ Common forms of values include:
 
 One of the [recommended labels](/docs/concepts/overview/working-with-objects/common-labels/#labels).
 
+### applyset.kubernetes.io/additional-namespaces (alpha) {#applyset-kubernetes-io-additional-namespaces}
+
+Example: `applyset.kubernetes.io/additional-namespaces: "namespace1,namespace2"`
+
+Used on: Objects being used as ApplySet parents.
+
+Use of this annotation is alpha.
+For Kubernetes version {{< skew currentVersion >}}, you can use this annotation on Secrets, ConfigMaps, or custom resources if the {{< glossary_tooltip term_id="CustomResourceDefinition" text="CustomResourceDefinition" >}} defining them has the `applyset.kubernetes.io/is-parent-type` label.
+
+Part of the specification used to implement [ApplySet-based pruning in kubectl](/docs/tasks/manage-kubernetes-objects/declarative-config/#alternative-kubectl-apply-f-directory-prune). This annotation is applied to the parent object used to track an ApplySet to extend the scope of the ApplySet beyond the parent object's own namespace (if any). The value is a comma-separated list of the names of namespaces other than the parent's namespace in which objects are found.
+
+### applyset.kubernetes.io/contains-group-resources (alpha) {#applyset-kubernetes-io-contains-group-resources}
+
+Example: `applyset.kubernetes.io/contains-group-resources: "certificates.cert-manager.io,configmaps,deployments.apps,secrets,services"`
+
+Used on: Objects being used as ApplySet parents.
+
+Use of this annotation is alpha.
+For Kubernetes version {{< skew currentVersion >}}, you can use this annotation on Secrets, ConfigMaps, or custom resources if the {{< glossary_tooltip term_id="CustomResourceDefinition" text="CustomResourceDefinition" >}} defining them has the `applyset.kubernetes.io/is-parent-type` label.
+
+Part of the specification used to implement [ApplySet-based pruning in kubectl](/docs/tasks/manage-kubernetes-objects/declarative-config/#alternative-kubectl-apply-f-directory-prune). This annotation is applied to the parent object used to track an ApplySet to optimize listing of ApplySet member objects. It is optional in the ApplySet specification, as tools can perform discovery or use a different optimization. However, as of Kubernetes version {{< skew currentVersion >}}, it is required by kubectl. When present, the value of this annotation must be a comma separated list of the group-kinds, in the fully-qualified name format, i.e. `<resource>.<group>`.
+
+
+### applyset.kubernetes.io/id (alpha) {#applyset-kubernetes-io-id}
+
+Example: `applyset.kubernetes.io/id: "applyset-0eFHV8ySqp7XoShsGvyWFQD3s96yqwHmzc4e0HR1dsY-v1"`
+
+Used on: Objects being used as ApplySet parents.
+
+Use of this label is alpha.
+For Kubernetes version {{< skew currentVersion >}}, you can use this label on Secrets, ConfigMaps, or custom resources if the {{< glossary_tooltip term_id="CustomResourceDefinition" text="CustomResourceDefinition" >}} defining them has the `applyset.kubernetes.io/is-parent-type` label.
+
+Part of the specification used to implement [ApplySet-based pruning in kubectl](/docs/tasks/manage-kubernetes-objects/declarative-config/#alternative-kubectl-apply-f-directory-prune). This label is what makes an object an ApplySet parent object. Its value is the unique ID of the ApplySet, which is derived from the identity of the parent object itself. This ID **must** be the base64 encoding (using the URL safe encoding of RFC4648) of the hash of the group-kind-name-namespace of the object it is on, in the form: `<base64(sha256(<name>.<namespace>.<kind>.<group>))>`. There is no relation between the value of this label and object UIDs.
+
+### applyset.kubernetes.io/is-parent-type (alpha) {#applyset-kubernetes-io-is-parent-type}
+
+Example: `applyset.kubernetes.io/is-parent-type: "true"`
+
+Used on: Custom Resource Definition (CRD)
+
+Use of this label is alpha.
+Part of the specification used to implement [ApplySet-based pruning in kubectl](/docs/tasks/manage-kubernetes-objects/declarative-config/#alternative-kubectl-apply-f-directory-prune). You can set this label on a {{< glossary_tooltip term_id="CustomResourceDefinition" text="CustomResourceDefinition" >}} (CRD) to identify the custom resource type it defines (not the CRD itself) as an allowed parent for an ApplySet. The only permitted value for this label is `"true"`; if you want to mark a CRD as not being a valid parent for ApplySets, omit this label.
+
+### applyset.kubernetes.io/part-of (alpha) {#applyset-kubernetes-io-part-of}
+
+Example: `applyset.kubernetes.io/part-of: "applyset-0eFHV8ySqp7XoShsGvyWFQD3s96yqwHmzc4e0HR1dsY-v1"`
+
+Used on: All objects.
+
+Use of this label is alpha.
+Part of the specification used to implement [ApplySet-based pruning in kubectl](/docs/tasks/manage-kubernetes-objects/declarative-config/#alternative-kubectl-apply-f-directory-prune). This label is what makes an object a member of an ApplySet. The value of the label **must** match the value of the `applyset.kubernetes.io/id` label on the parent object.
+
+### applyset.kubernetes.io/tooling (alpha) {#applyset-kubernetes-io-tooling}
+
+Example: `applyset.kubernetes.io/tooling: "kubectl/v{{< skew currentVersion >}}"`
+
+Used on: Objects being used as ApplySet parents.
+
+Use of this annotation is alpha.
+For Kubernetes version {{< skew currentVersion >}}, you can use this annotation on Secrets, ConfigMaps, or custom resources if the {{< glossary_tooltip term_id="CustomResourceDefinition" text="CustomResourceDefinition" >}} defining them has the `applyset.kubernetes.io/is-parent-type` label.
+
+Part of the specification used to implement [ApplySet-based pruning in kubectl](/docs/tasks/manage-kubernetes-objects/declarative-config/#alternative-kubectl-apply-f-directory-prune). This annotation is applied to the parent object used to track an ApplySet to indicate which tooling manages that ApplySet. Tooling should refuse to mutate ApplySets belonging to other tools. The value must be in the format `<toolname>/<semver>`.
+
 ### cluster-autoscaler.kubernetes.io/safe-to-evict
 
 Example: `cluster-autoscaler.kubernetes.io/safe-to-evict: "true"`
diff --git a/content/en/docs/tasks/manage-kubernetes-objects/declarative-config.md b/content/en/docs/tasks/manage-kubernetes-objects/declarative-config.md
index 2b54f2f4094..ef51d18fc6d 100644
--- a/content/en/docs/tasks/manage-kubernetes-objects/declarative-config.md
+++ b/content/en/docs/tasks/manage-kubernetes-objects/declarative-config.md
@@ -371,44 +371,82 @@ to result in the user deleting something unintentionally:
 kubectl delete -f <filename>
 ```
 
-### Alternative: `kubectl apply -f <directory/> --prune -l your=label`
+### Alternative: `kubectl apply -f <directory/> --prune`
 
-Only use this if you know what you are doing.
+As an alternative to `kubectl delete`, you can use `kubectl apply` to identify objects to be deleted after
+their manifests have been removed from a directory in the local filesystem.
+
+In Kubernetes {{< skew currentVersion >}}, there are two pruning modes available in kubectl apply:
+- Allowlist-based pruning: This mode has existed since kubectl v1.5 but is still in alpha due to usability, correctness and performance issues with its design. The ApplySet-based mode is designed to replace it.
+- ApplySet-based pruning: An _apply set_ is a server-side object (by default, a Secret) that kubectl can use to accurately and efficiently track set membership across **apply** operations. This mode was introduced in alpha in kubectl v1.27 as a replacement for allowlist-based pruning.
+
+{{< tabs name="kubectl_apply_prune" >}}
+{{% tab name="Allow list" %}}
+
+{{< feature-state for_k8s_version="v1.5" state="alpha" >}}
 
 {{< warning >}}
-`kubectl apply --prune` is in alpha, and backwards incompatible
-changes might be introduced in subsequent releases.
+Take care when using `--prune` with `kubectl apply` in allow list mode. Which objects are pruned depends on the values of the `--prune-allowlist`, `--selector` and `--namespace` flags, and relies on dynamic discovery of the objects in scope. Especially if flag values are changed between invocations, this can lead to objects being unexpectedly deleted or retained.
 {{< /warning >}}
 
-{{< warning >}}
-You must be careful when using this command, so that you
-do not delete objects unintentionally.
-{{< /warning >}}
+To use allowlist-based pruning, add the following flags to your `kubectl apply` invocation:
+- `--prune`: Delete previously applied objects that are not in the set passed to the current invocation.
+- `--prune-allowlist`: A list of group-version-kinds (GVKs) to consider for pruning. This flag is optional but strongly encouraged, as its default value is a partial list of both namespaced and cluster-scoped types, which can lead to surprising results.
+- `--selector/-l`: Use a label selector to constrain the set of objects selected for pruning. This flag is optional but strongly encouraged.
+- `--all`: use instead of `--selector/-l` to explicitly select all previously applied objects of the allowlisted types.
 
-As an alternative to `kubectl delete`, you can use `kubectl apply` to identify objects to be deleted after their
-configuration files have been removed from the directory. Apply with `--prune`
-queries the API server for all objects matching a set of labels, and attempts
-to match the returned live object configurations against the object
-configuration files. If an object matches the query, and it does not have a
-configuration file in the directory, and it has a `last-applied-configuration` annotation,
+Allowlist-based pruning queries the API server for all objects of the allowlisted GVKs that match the given labels (if any), and attempts to match the returned live object configurations against the object
+manifest files. If an object matches the query, and it does not have a
+manifest in the directory, and it has a `kubectl.kubernetes.io/last-applied-configuration` annotation,
 it is deleted.
 
-{{< comment >}}
-TODO(pwittrock): We need to change the behavior to prevent the user from running apply on subdirectories unintentionally.
-{{< /comment >}}
 
 ```shell
-kubectl apply -f <directory/> --prune -l <labels>
+kubectl apply -f <directory/> --prune -l <labels> --prune-allowlist=<gvk-list>
 ```
 
 {{< warning >}}
 Apply with prune should only be run against the root directory
-containing the object configuration files. Running against sub-directories
-can cause objects to be unintentionally deleted if they are returned
-by the label selector query specified with `-l <labels>` and
-do not appear in the subdirectory.
+containing the object manifests. Running against sub-directories
+can cause objects to be unintentionally deleted if they were previously applied, 
+have the labels given (if any), and do not appear in the subdirectory.
 {{< /warning >}}
 
+{{% /tab %}}
+
+{{% tab name="Apply set" %}}
+
+{{< feature-state for_k8s_version="v1.27" state="alpha" >}}
+
+{{< caution >}}
+`kubectl apply --prune --applyset` is in alpha, and backwards incompatible
+changes might be introduced in subsequent releases.
+{{< /caution >}}
+
+To use ApplySet-based pruning, set the `KUBECTL_APPLYSET=true` environment variable, and add the following flags to your `kubectl apply` invocation:
+- `--prune`: Delete previously applied objects that are not in the set passed to the current invocation.
+- `--applyset`: The name of an object that kubectl can use to accurately and efficiently track set membership across `apply` operations.
+
+```shell
+KUBECTL_APPLYSET=true kubectl apply -f <directory/> --prune --applyset=<name>
+```
+
+By default, the type of the ApplySet parent object used is a Secret. However, ConfigMaps can also be used in the format: `--applyset=configmaps/<name>`. When using a Secret or ConfigMap, kubectl will create the object if it does not already exist.
+
+It is also possible to use custom resources as ApplySet parent objects. To enable this, label the Custom Resource Definition (CRD) that defines the resource you want to use with the following: `applyset.kubernetes.io/is-parent-type: true`. Then, create the object you want to use as an ApplySet parent (kubectl does not do this automatically for custom resources). Finally, refer to that object in the applyset flag as follows: `--applyset=<resource>.<group>/<name>` (for example, `widgets.custom.example.com/widget-name`).
+
+With ApplySet-based pruning, kubectl adds the `applyset.kubernetes.io/part-of=<parentID>` label to each object in the set before they are sent to the server. For performance reasons, it also collects the list of resource types and namespaces that the set contains and adds these in annotations on the live parent object. Finally, at the end of the apply operation, it queries the API server for objects of those types in those namespaces (or in the cluster scope, as applicable) that belong to the set, as defined by the `applyset.kubernetes.io/part-of=<parentID>` label.
+
+Caveats and restrictions:
+- Each object may be a member of at most one set.
+- The `--namespace` flag is required when using any namespaced parent, including the default Secret.  This means that ApplySets spanning multiple namespaces must use a cluster-scoped custom resource as the parent object.
+- To safely use ApplySet-based pruning with multiple directories, use a unique ApplySet name for each.
+
+{{% /tab %}}
+
+{{< /tabs >}}
+
+
 ## How to view an object
 
 You can use `kubectl get` with `-o yaml` to view the configuration of a live object:
@@ -1007,5 +1045,3 @@ template:
 * [Imperative Management of Kubernetes Objects Using Configuration Files](/docs/tasks/manage-kubernetes-objects/imperative-config/)
 * [Kubectl Command Reference](/docs/reference/generated/kubectl/kubectl-commands/)
 * [Kubernetes API Reference](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/)
-
-

From 81dfd0cd00c2fdcc99d01f5eb629d1cc24e55c72 Mon Sep 17 00:00:00 2001
From: Sergey Kanzhelev <S.Kanzhelev@live.com>
Date: Tue, 4 Apr 2023 05:57:54 -0700
Subject: [PATCH 104/272] gRPC GA (#39919)

---
 .../_posts/2022-05-13-grpc-probes-in-beta.md  |  1 +
 .../concepts/workloads/pods/pod-lifecycle.md  |  5 +----
 .../feature-gates.md                          |  8 +++++--
 ...igure-liveness-readiness-startup-probes.md | 22 ++++++++++++-------
 4 files changed, 22 insertions(+), 14 deletions(-)

diff --git a/content/en/blog/_posts/2022-05-13-grpc-probes-in-beta.md b/content/en/blog/_posts/2022-05-13-grpc-probes-in-beta.md
index e4a9ab0092c..77cf06d1040 100644
--- a/content/en/blog/_posts/2022-05-13-grpc-probes-in-beta.md
+++ b/content/en/blog/_posts/2022-05-13-grpc-probes-in-beta.md
@@ -7,6 +7,7 @@ slug: grpc-probes-now-in-beta
 
 **Author**: Sergey Kanzhelev (Google)
 
+_Update: Since this article was posted, the feature was graduated to GA in v1.27 and doesn't require any feature gates to be enabled.
 
 With Kubernetes 1.24 the gRPC probes functionality entered beta and is available by default.
 Now you can configure startup, liveness, and readiness probes for your gRPC app
diff --git a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md
index e37e8ac92db..b209a6a65f3 100644
--- a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md
+++ b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md
@@ -302,10 +302,7 @@ Each probe must define exactly one of these four mechanisms:
   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/).
+  of the response is `SERVING`.  
 
 `httpGet`
 : Performs an HTTP `GET` request against the Pod's IP
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 f1dd7e6721a..25c3f1c3f65 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
@@ -101,8 +101,6 @@ For a reference to old feature gates that are removed, please refer to
 | `ExpandedDNSConfig` | `false` | Alpha | 1.22 | 1.25 |
 | `ExpandedDNSConfig` | `true` | Beta | 1.26 | |
 | `ExperimentalHostUserNamespaceDefaulting` | `false` | Beta | 1.5 | |
-| `GRPCContainerProbe` | `false` | Alpha | 1.23 | 1.23 |
-| `GRPCContainerProbe` | `true` | Beta | 1.24 | |
 | `GracefulNodeShutdown` | `false` | Alpha | 1.20 | 1.20 |
 | `GracefulNodeShutdown` | `true` | Beta | 1.21 | |
 | `GracefulNodeShutdownBasedOnPodPriority` | `false` | Alpha | 1.23 | 1.23 |
@@ -293,6 +291,12 @@ For a reference to old feature gates that are removed, please refer to
 | `ExecProbeTimeout` | `true` | GA | 1.20 | - |
 | `JobMutableNodeSchedulingDirectives` | `true` | Beta | 1.23 | 1.26 |
 | `JobMutableNodeSchedulingDirectives` | `true` | GA | 1.27 | |
+| `GRPCContainerProbe` | `false` | Alpha | 1.23 | 1.23 |
+| `GRPCContainerProbe` | `true` | Beta | 1.24 | 1.26 |
+| `GRPCContainerProbe` | `true` | GA | 1.27 | |
+| `IdentifyPodOS` | `false` | Alpha | 1.23 | 1.23 |
+| `IdentifyPodOS` | `true` | Beta | 1.24 | 1.24 |
+| `IdentifyPodOS` | `true` | GA | 1.25 | - |
 | `JobTrackingWithFinalizers` | `false` | Alpha | 1.22 | 1.22 |
 | `JobTrackingWithFinalizers` | `false` | Beta | 1.23 | 1.24 |
 | `JobTrackingWithFinalizers` | `true` | Beta | 1.25 | 1.25 |
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 bafa4e36992..b8d91a824b1 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
@@ -240,21 +240,27 @@ kubectl describe pod goproxy
 
 {{< feature-state for_k8s_version="v1.24" state="beta" >}}
 
-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.
+If your application implements the [gRPC Health Checking Protocol](https://github.com/grpc/grpc/blob/master/doc/health-checking.md),
+this example shows how to configure Kubernetes to use it for application liveness checks.
+Similarly you can configure readiness and startup probes.
 
 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, you must also specify the `service`.
+To use a gRPC probe, `port` must be configured. If you want to distinguish probes of different types
+and probes for different features you can use the `service` field.
+You can set `service` to the value `liveness` and make your gRPC Health Checking endpoint
+respond to this request differently then when you set `service` set to `readiness`.
+This lets you use the same endpoint for different kinds of container health check
+(rather than needing to listen on two different ports).
+If you want to specify your own custom service name and also specify a probe type,
+the Kubernetes project recommends that you use a name that concatenates
+those. For example: `myservice-liveness` (using `-` as a separator).
 
 {{< note >}}
-Unlike HTTP and TCP probes, named ports cannot be used and custom host cannot be configured.
+Unlike HTTP or TCP probes, you cannot specify the healthcheck port by name, and you
+cannot configure a custom hostname.
 {{< /note >}}
 
 Configuration problems (for example: incorrect port and service, unimplemented health checking protocol)

From 427ed08ec7d2f95201f51704be69c6d3f0d44c13 Mon Sep 17 00:00:00 2001
From: Antonio Ojea <antonio.ojea.garcia@gmail.com>
Date: Tue, 4 Apr 2023 15:43:52 +0200
Subject: [PATCH 105/272] Update
 content/en/docs/reference/networking/virtual-ips.md

Co-authored-by: Tim Bannister <tim@scalefactory.com>
---
 content/en/docs/reference/networking/virtual-ips.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/reference/networking/virtual-ips.md b/content/en/docs/reference/networking/virtual-ips.md
index 586221ad9f3..0b4a6e974f4 100644
--- a/content/en/docs/reference/networking/virtual-ips.md
+++ b/content/en/docs/reference/networking/virtual-ips.md
@@ -301,7 +301,7 @@ IP addresses that are no longer used by any Services.
 {{< feature-state for_k8s_version="v1.27" state="alpha" >}}
 If you enable the `MultiCIDRServiceAllocator`
 [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) and the
-[networking.k8s.io/v1alpha1 API group](https://kubernetes.io/docs/tasks/administer-cluster/enable-disable-api/),
+[`networking.k8s.io/v1alpha1` API group](/docs/tasks/administer-cluster/enable-disable-api/),
 the control plane replaces the existing etcd allocator with a new one, using IPAddress
 objects instead of an internal global allocation map.  The ClusterIP address
 associated to each `Service` will have a referenced IPAddress object.

From c4e4aecde8e3f191804a01d25d17c28458757c2b Mon Sep 17 00:00:00 2001
From: Antonio Ojea <antonio.ojea.garcia@gmail.com>
Date: Tue, 4 Apr 2023 15:44:19 +0200
Subject: [PATCH 106/272] Update
 content/en/docs/reference/networking/virtual-ips.md

Co-authored-by: Tim Bannister <tim@scalefactory.com>
---
 content/en/docs/reference/networking/virtual-ips.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/reference/networking/virtual-ips.md b/content/en/docs/reference/networking/virtual-ips.md
index 0b4a6e974f4..6c2cdaacf74 100644
--- a/content/en/docs/reference/networking/virtual-ips.md
+++ b/content/en/docs/reference/networking/virtual-ips.md
@@ -304,7 +304,7 @@ If you enable the `MultiCIDRServiceAllocator`
 [`networking.k8s.io/v1alpha1` API group](/docs/tasks/administer-cluster/enable-disable-api/),
 the control plane replaces the existing etcd allocator with a new one, using IPAddress
 objects instead of an internal global allocation map.  The ClusterIP address
-associated to each `Service` will have a referenced IPAddress object.
+associated to each Service will have a referenced IPAddress object.
 
 The background controller is also replaced by a new one to handle the new IPAddress
 objects and the migration from the old allocator model.

From 460b8993521654b201acc2316e9e64a2a7c9a77f Mon Sep 17 00:00:00 2001
From: MaxymVlasov <MaxymVlasov@users.noreply.github.com>
Date: Tue, 4 Apr 2023 16:44:23 +0300
Subject: [PATCH 107/272] Mention kubernetes/websites everywhere in the same
 way

---
 content/hi/docs/contribute/_index.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/hi/docs/contribute/_index.md b/content/hi/docs/contribute/_index.md
index dc652738acc..c6f748bbda0 100644
--- a/content/hi/docs/contribute/_index.md
+++ b/content/hi/docs/contribute/_index.md
@@ -68,7 +68,7 @@ end
 subgraph second[समीक्षा]
 direction TB
    T[ ] -.-
-   D[K8s/website<br>रिपॉजिटरी<br>को देखें] --- E[Hugo स्टैटिक साइट<br>जनरेटर<br>को देखें]
+   D[kubernetes/website<br>रिपॉजिटरी<br>को देखें] --- E[Hugo स्टैटिक साइट<br>जनरेटर<br>को देखें]
    E --- F[मूलभूत GitHub<br>कमांड समझें]
    F --- G[ओपन PR की समीक्षा करे<br>और समीक्षा प्रक्रिया<br>को बदलें]
 end
@@ -115,7 +115,7 @@ flowchart LR
     direction TB
     S[ ] -.-
     G[दूसरे K8s मेम्बर्स के<br>PRs की समीक्षा करें] -->
-    A[अपने पहले इशू (गुफ फर्स्ट इशू)<br>के लिए K8s/website<br>की इशू सूची पर जाएं] --> B[PR ओपन करें!!]
+    A[अपने पहले इशू (गुफ फर्स्ट इशू)<br>के लिए kubernetes/website<br>की इशू सूची पर जाएं] --> B[PR ओपन करें!!]
     end
     subgraph first[सूचित तैयारी]
     direction TB

From 5056816f28830beee2114ba7f0c347d6349cb8f7 Mon Sep 17 00:00:00 2001
From: Antonio Ojea <antonio.ojea.garcia@gmail.com>
Date: Tue, 4 Apr 2023 15:44:30 +0200
Subject: [PATCH 108/272] Update
 content/en/docs/reference/networking/virtual-ips.md

Co-authored-by: Tim Bannister <tim@scalefactory.com>
---
 content/en/docs/reference/networking/virtual-ips.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/content/en/docs/reference/networking/virtual-ips.md b/content/en/docs/reference/networking/virtual-ips.md
index 6c2cdaacf74..e6a6ef135c0 100644
--- a/content/en/docs/reference/networking/virtual-ips.md
+++ b/content/en/docs/reference/networking/virtual-ips.md
@@ -314,8 +314,9 @@ for the `service-cluster-ip-range`, there is no limitations for IPv4 and for IPv
 users can use masks equal or larger than /64 (previously it was /108).
 
 Users now will be able to inspect the IP addresses assigned to their Services, and
-new network APIs, like Gateway API, can use this new object to extend the Kubernetes
-networking capabilities overcoming the limitations of current Services API.
+Kubernetes extensions such as the [Gateway](https://gateway-api.sigs.k8s.io/) API, can use this new
+IPAddress object kind to enhance the Kubernetes networking capabilities, going beyond the limitations of
+the built-in Service API.
 
 ```shell
 kubectl get services

From 407b5af6c388957e16b2c320e6107f1777c1a9fd Mon Sep 17 00:00:00 2001
From: Matthew Cary <mattcary@google.com>
Date: Tue, 4 Apr 2023 08:05:56 -0700
Subject: [PATCH 109/272] Update docs for StatefulSetAutoDeletePVC beta in 1.27

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

diff --git a/content/en/docs/concepts/workloads/controllers/statefulset.md b/content/en/docs/concepts/workloads/controllers/statefulset.md
index 8023c1020f0..bdb0703f7af 100644
--- a/content/en/docs/concepts/workloads/controllers/statefulset.md
+++ b/content/en/docs/concepts/workloads/controllers/statefulset.md
@@ -360,7 +360,7 @@ StatefulSet will then begin to recreate the Pods using the reverted template.
 
 ## PersistentVolumeClaim retention
 
-{{< feature-state for_k8s_version="v1.23" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
 
 The optional `.spec.persistentVolumeClaimRetentionPolicy` field controls if
 and how PVCs are deleted during the lifecycle of a StatefulSet. You must enable the
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 a45aa27baa4..38b0fccff12 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
@@ -191,7 +191,8 @@ For a reference to old feature gates that are removed, please refer to
 | `ServiceNodePortStaticSubrange` | `false` | Alpha | 1.27 | |
 | `SizeMemoryBackedVolumes` | `false` | Alpha | 1.20 | 1.21 |
 | `SizeMemoryBackedVolumes` | `true` | Beta | 1.22 | |
-| `StatefulSetAutoDeletePVC` | `false` | Alpha | 1.22 | |
+| `StatefulSetAutoDeletePVC` | `false` | Alpha | 1.22 | 1.26 |
+| `StatefulSetAutoDeletePVC` | `false` | Beta | 1.27 | |
 | `StatefulSetStartOrdinal` | `false` | Alpha | 1.26 | 1.26 |
 | `StatefulSetStartOrdinal` | `true` | Beta | 1.27 | |
 | `StorageVersionAPI` | `false` | Alpha | 1.20 | |

From 1b66978934745ced1df9c95d7b10c8c1c21b427b Mon Sep 17 00:00:00 2001
From: Ilya Margolin <ilya@ulani.de>
Date: Tue, 4 Apr 2023 18:56:11 +0200
Subject: [PATCH 110/272] Update docs for kubectl auth whoami

it is not alpha anymore
---
 .../configure-access-multiple-clusters.md                     | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/en/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md b/content/en/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md
index 09322248895..23402785149 100644
--- a/content/en/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md
+++ b/content/en/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md
@@ -403,8 +403,8 @@ $Env:KUBECONFIG=$ENV:KUBECONFIG_SAVED
 It is not always obvious what attributes (username, groups) you will get after authenticating to the cluster. 
 It can be even more challenging if you are managing more than one cluster at the same time.
 
-There is a `kubectl` alpha subcommand command to check subject attributes, such as username,
-for your selected Kubernetes client context: `kubectl auth whoami`.
+There is a `kubectl` subcommand to check subject attributes, such as username, for your selected Kubernetes 
+client context: `kubectl auth whoami`.
 
 Read [API access to authentication information for a client](/docs/reference/access-authn-authz/authentication/#self-subject-review)
 to learn about this in more detail.

From e8e3c2a82279d676669219ce76c06dfaadb32b8c Mon Sep 17 00:00:00 2001
From: Arhell <arhell333@gmail.com>
Date: Wed, 5 Apr 2023 00:39:51 +0300
Subject: [PATCH 111/272] [ja] Updated kubectl describe svc output

---
 .../services-networking/connect-applications-service.md       | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/content/ja/docs/concepts/services-networking/connect-applications-service.md b/content/ja/docs/concepts/services-networking/connect-applications-service.md
index 17aced17830..368972cfe51 100644
--- a/content/ja/docs/concepts/services-networking/connect-applications-service.md
+++ b/content/ja/docs/concepts/services-networking/connect-applications-service.md
@@ -118,8 +118,12 @@ Labels:              run=my-nginx
 Annotations:         <none>
 Selector:            run=my-nginx
 Type:                ClusterIP
+IP Family Policy:    SingleStack
+IP Families:         IPv4
 IP:                  10.0.162.149
+IPs:                 10.0.162.149
 Port:                <unset> 80/TCP
+TargetPort:          80/TCP
 Endpoints:           10.244.2.5:80,10.244.3.4:80
 Session Affinity:    None
 Events:              <none>

From c1512c77ad6d428e6fd7c9df205f9c98310124a4 Mon Sep 17 00:00:00 2001
From: cailynse <cailyn.s.e@gmail.com>
Date: Thu, 23 Feb 2023 19:58:29 -0500
Subject: [PATCH 112/272] Add Blog Post for KEP-3202-beta release

---
 .../index.md                                  | 39 +++++++++++++++++++
 1 file changed, 39 insertions(+)
 create mode 100644 content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md

diff --git a/content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md b/content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
new file mode 100644
index 00000000000..dbc48fab399
--- /dev/null
+++ b/content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
@@ -0,0 +1,39 @@
+---
+layout: blog 
+title: Updates to the Auto-refreshing Official CVE Feed
+date: 2023-04-04
+slug: k8s-cve-feed-beta
+---
+
+**Author**: Cailyn Edwards (Shopify)
+
+Since launching the [Auto-refreshing Official CVE feed](/docs/reference/issues-security/official-cve-feed/) as an `alpha`
+feature in the 1.25 release we have made signficant improvments and updates. We are excited to announce the release of the 
+`beta` version of the feed. This blog post will outline the changes made, and talk about what is planned for the to expect for 
+the `stable` release.
+
+## Updates
+| **\#** | **Title**                                                                                                    | **Issue**                                                       | **Status**                                                                                                                                                                                                                      |
+| ------ | ------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 1 | Support RSS feeds by generating data in Atom format | [kubernetes/sig-security#77](https://github.com/kubernetes/sig-security/issues/77) | open, addressed by [kubernetes/website#39513](https://github.com/kubernetes/website/pull/39513)|
+| 2 | CVE Feed: Sort Markdown Table from most recent to least recently announced CVE | [kubernetes/sig-security#73](https://github.com/kubernetes/sig-security/issues/73) | open, no PR open |
+| 3 | CVE Feed: Add Prow job link as a metadata field | [kubernetes/sig-security#71](https://github.com/kubernetes/sig-security/issues/71) | open, no PR open |
+| 4 | CVE Feed: Add lastUpdatedAt as a metadata field | [kubernetes/sig-security#72](https://github.com/kubernetes/sig-security/issues/72) | open, addressed by [kubernetes/sig-security#76](https://github.com/kubernetes/sig-security/pull/76) |
+| 5 | CVE Feed: JSON feed should pass jsonfeed spec validator | [kubernetes/webite#36808](https://github.com/kubernetes/website/issues/36808) | open, addressed by [kubernetes/sig-security#76](https://github.com/kubernetes/sig-security/pull/76) |
+| 6 | CVE Feed: Include a timestamp field for each CVE indicating when it was last updated | [kubernetes/sig-security#63](https://github.com/kubernetes/sig-security/issues/63) | open, no PR |
+| 7 | CVE Feed: Sort Markdown Table from most recent to least recently announced CVE | [kubernetes/sig-security#73](https://github.com/kubernetes/sig-security/issues/73) | open, no PR |
+
+## Summary of Changes
+TODO - add details of changes
+
+## What's Next?
+
+In preparation to graduate this feature, SIG Security
+is still gathering feedback from end users who are using the updated beta feed.
+
+To help us continue to improve the feed in future Kubernetes Releases please share feedback by adding a comment to
+this [tracking issue](https://github.com/kubernetes/sig-security/issues/1) or
+let us know on
+[#sig-security-tooling](https://kubernetes.slack.com/archives/C01CUSVMHPY)
+Kubernetes Slack channel.
+(Join [Kubernetes Slack here](https://slack.k8s.io))
\ No newline at end of file

From d7f8476c292fa84653ef7c9fd569e196ab6866e9 Mon Sep 17 00:00:00 2001
From: Cailyn <cailyn.s.e@gmail.com>
Date: Tue, 4 Apr 2023 19:45:15 -0400
Subject: [PATCH 113/272] Update
 content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md

Co-authored-by: Nate W. <natew@cncf.io>
---
 .../index.md                                                    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md b/content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
index dbc48fab399..8e0dd06b3c1 100644
--- a/content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
+++ b/content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
@@ -8,7 +8,7 @@ slug: k8s-cve-feed-beta
 **Author**: Cailyn Edwards (Shopify)
 
 Since launching the [Auto-refreshing Official CVE feed](/docs/reference/issues-security/official-cve-feed/) as an `alpha`
-feature in the 1.25 release we have made signficant improvments and updates. We are excited to announce the release of the 
+feature in the 1.25 release, we have made significant improvements and updates. We are excited to announce the release of the
 `beta` version of the feed. This blog post will outline the changes made, and talk about what is planned for the to expect for 
 the `stable` release.
 

From 5843e849046fa57f9f23a2aa0420260afd794a8d Mon Sep 17 00:00:00 2001
From: Cailyn <cailyn.s.e@gmail.com>
Date: Tue, 4 Apr 2023 19:45:23 -0400
Subject: [PATCH 114/272] Update
 content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md

Co-authored-by: Nate W. <natew@cncf.io>
---
 .../index.md                                                    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md b/content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
index 8e0dd06b3c1..9cfa0d4b9ce 100644
--- a/content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
+++ b/content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
@@ -28,7 +28,7 @@ TODO - add details of changes
 
 ## What's Next?
 
-In preparation to graduate this feature, SIG Security
+In preparation for the graduation of this feature, SIG Security
 is still gathering feedback from end users who are using the updated beta feed.
 
 To help us continue to improve the feed in future Kubernetes Releases please share feedback by adding a comment to

From 1fdaa7b46972291b72ececd91229ccd5e77f1d16 Mon Sep 17 00:00:00 2001
From: s-kawamura-w664 <s-kawamura_p@nec.com>
Date: Thu, 30 Mar 2023 14:55:06 +0900
Subject: [PATCH 115/272] [ja] update page weights in /tasks

---
 content/ja/docs/tasks/access-application-cluster/_index.md      | 2 +-
 .../communicate-containers-same-pod-shared-volume.md            | 2 +-
 .../docs/tasks/access-application-cluster/ingress-minikube.md   | 2 +-
 content/ja/docs/tasks/configmap-secret/_index.md                | 2 +-
 content/ja/docs/tasks/configure-pod-container/_index.md         | 2 +-
 .../assign-pods-nodes-using-node-affinity.md                    | 2 +-
 .../ja/docs/tasks/configure-pod-container/assign-pods-nodes.md  | 2 +-
 .../configure-pod-container/attach-handler-lifecycle-event.md   | 2 +-
 .../configure-liveness-readiness-startup-probes.md              | 2 +-
 .../tasks/configure-pod-container/configure-pod-configmap.md    | 2 +-
 .../configure-projected-volume-storage.md                       | 2 +-
 .../tasks/configure-pod-container/configure-volume-storage.md   | 2 +-
 .../ja/docs/tasks/configure-pod-container/extended-resource.md  | 2 +-
 .../docs/tasks/configure-pod-container/quality-service-pod.md   | 2 +-
 .../ja/docs/tasks/configure-pod-container/security-context.md   | 2 +-
 .../tasks/configure-pod-container/share-process-namespace.md    | 2 +-
 content/ja/docs/tasks/configure-pod-container/static-pod.md     | 2 +-
 content/ja/docs/tasks/debug/_index.md                           | 2 +-
 .../debug/debug-application/determine-reason-pod-failure.md     | 1 +
 content/ja/docs/tasks/inject-data-application/_index.md         | 2 +-
 content/ja/docs/tasks/job/_index.md                             | 2 +-
 content/ja/docs/tasks/manage-kubernetes-objects/_index.md       | 2 +-
 content/ja/docs/tasks/network/_index.md                         | 2 +-
 content/ja/docs/tasks/run-application/_index.md                 | 2 +-
 content/ja/docs/tasks/tls/_index.md                             | 2 +-
 25 files changed, 25 insertions(+), 24 deletions(-)

diff --git a/content/ja/docs/tasks/access-application-cluster/_index.md b/content/ja/docs/tasks/access-application-cluster/_index.md
index dc48e622465..cc0f539baa5 100644
--- a/content/ja/docs/tasks/access-application-cluster/_index.md
+++ b/content/ja/docs/tasks/access-application-cluster/_index.md
@@ -1,5 +1,5 @@
 ---
 title: "クラスター内アプリケーションへのアクセス"
 description: クラスター内アプリケーションへアクセスできるようにするために、ロードバランシングやポートフォワーディングの設定、ファイアウォールやDNS設定のセットアップを行います。
-weight: 60
+weight: 100
 ---
diff --git a/content/ja/docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume.md b/content/ja/docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume.md
index 8a0d37d28e3..540cbab72a1 100644
--- a/content/ja/docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume.md
+++ b/content/ja/docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume.md
@@ -1,7 +1,7 @@
 ---
 title: 共有ボリュームを使用して同じPod内のコンテナ間で通信する
 content_type: task
-weight: 110
+weight: 120
 ---
 
 <!-- overview -->
diff --git a/content/ja/docs/tasks/access-application-cluster/ingress-minikube.md b/content/ja/docs/tasks/access-application-cluster/ingress-minikube.md
index be267080996..3c3f7526642 100644
--- a/content/ja/docs/tasks/access-application-cluster/ingress-minikube.md
+++ b/content/ja/docs/tasks/access-application-cluster/ingress-minikube.md
@@ -1,7 +1,7 @@
 ---
 title: Minikube上でNGINX Ingressコントローラーを使用してIngressをセットアップする
 content_type: task
-weight: 100
+weight: 110
 ---
 
 <!-- overview -->
diff --git a/content/ja/docs/tasks/configmap-secret/_index.md b/content/ja/docs/tasks/configmap-secret/_index.md
index 18a8018ce56..39e607f6cf3 100644
--- a/content/ja/docs/tasks/configmap-secret/_index.md
+++ b/content/ja/docs/tasks/configmap-secret/_index.md
@@ -1,6 +1,6 @@
 ---
 title: "Secretの管理"
-weight: 28
+weight: 60
 description: Secretを使用した機密設定データの管理
 ---
 
diff --git a/content/ja/docs/tasks/configure-pod-container/_index.md b/content/ja/docs/tasks/configure-pod-container/_index.md
index 324a19b22b4..c40ed206666 100644
--- a/content/ja/docs/tasks/configure-pod-container/_index.md
+++ b/content/ja/docs/tasks/configure-pod-container/_index.md
@@ -1,6 +1,6 @@
 ---
 title: "Podとコンテナの設定"
 description: Podとコンテナの一般的な設定のタスクを行います。
-weight: 20
+weight: 30
 ---
 
diff --git a/content/ja/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity.md b/content/ja/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity.md
index 77caf9a13c4..d0599138dcd 100644
--- a/content/ja/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity.md
+++ b/content/ja/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity.md
@@ -2,7 +2,7 @@
 title: Node Affinityを利用してPodをノードに割り当てる
 min-kubernetes-server-version: v1.10
 content_type: task
-weight: 120
+weight: 160
 ---
 
 <!-- overview -->
diff --git a/content/ja/docs/tasks/configure-pod-container/assign-pods-nodes.md b/content/ja/docs/tasks/configure-pod-container/assign-pods-nodes.md
index 4e09dbaf932..a1ed76638b8 100644
--- a/content/ja/docs/tasks/configure-pod-container/assign-pods-nodes.md
+++ b/content/ja/docs/tasks/configure-pod-container/assign-pods-nodes.md
@@ -1,7 +1,7 @@
 ---
 title: Podをノードに割り当てる
 content_type: task
-weight: 120
+weight: 150
 ---
 
 <!-- overview -->
diff --git a/content/ja/docs/tasks/configure-pod-container/attach-handler-lifecycle-event.md b/content/ja/docs/tasks/configure-pod-container/attach-handler-lifecycle-event.md
index 1aa194a745a..b7cfb624e7a 100644
--- a/content/ja/docs/tasks/configure-pod-container/attach-handler-lifecycle-event.md
+++ b/content/ja/docs/tasks/configure-pod-container/attach-handler-lifecycle-event.md
@@ -1,7 +1,7 @@
 ---
 title: コンテナライフサイクルイベントへのハンドラー紐付け
 content_type: task
-weight: 140
+weight: 180
 ---
 
 <!-- overview -->
diff --git a/content/ja/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md b/content/ja/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
index 0c14c79bb6b..c5dc0869c7a 100644
--- a/content/ja/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
+++ b/content/ja/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
@@ -1,7 +1,7 @@
 ---
 title: Liveness Probe、Readiness ProbeおよびStartup Probeを使用する
 content_type: task
-weight: 110
+weight: 140
 ---
 
 <!-- overview -->
diff --git a/content/ja/docs/tasks/configure-pod-container/configure-pod-configmap.md b/content/ja/docs/tasks/configure-pod-container/configure-pod-configmap.md
index 7bcacd13a4c..61c8225fe14 100644
--- a/content/ja/docs/tasks/configure-pod-container/configure-pod-configmap.md
+++ b/content/ja/docs/tasks/configure-pod-container/configure-pod-configmap.md
@@ -1,7 +1,7 @@
 ---
 title: Podを構成してConfigMapを使用する
 content_type: task
-weight: 150
+weight: 190
 card:
   name: tasks
   weight: 50
diff --git a/content/ja/docs/tasks/configure-pod-container/configure-projected-volume-storage.md b/content/ja/docs/tasks/configure-pod-container/configure-projected-volume-storage.md
index 4c70662d424..1fd7172bc27 100644
--- a/content/ja/docs/tasks/configure-pod-container/configure-projected-volume-storage.md
+++ b/content/ja/docs/tasks/configure-pod-container/configure-projected-volume-storage.md
@@ -1,7 +1,7 @@
 ---
 title: ストレージにProjectedボリュームを使用するようPodを設定する
 content_type: task
-weight: 70
+weight: 100
 ---
 
 <!-- overview -->
diff --git a/content/ja/docs/tasks/configure-pod-container/configure-volume-storage.md b/content/ja/docs/tasks/configure-pod-container/configure-volume-storage.md
index 5fb2769bdd3..140336d0db7 100644
--- a/content/ja/docs/tasks/configure-pod-container/configure-volume-storage.md
+++ b/content/ja/docs/tasks/configure-pod-container/configure-volume-storage.md
@@ -1,7 +1,7 @@
 ---
 title: ストレージにボリュームを使用するPodを構成する
 content_type: task
-weight: 50
+weight: 80
 ---
 
 <!-- overview -->
diff --git a/content/ja/docs/tasks/configure-pod-container/extended-resource.md b/content/ja/docs/tasks/configure-pod-container/extended-resource.md
index b056fc73898..7a0114582a1 100644
--- a/content/ja/docs/tasks/configure-pod-container/extended-resource.md
+++ b/content/ja/docs/tasks/configure-pod-container/extended-resource.md
@@ -1,7 +1,7 @@
 ---
 title: 拡張リソースをコンテナに割り当てる
 content_type: task
-weight: 40
+weight: 70
 ---
 
 <!-- overview -->
diff --git a/content/ja/docs/tasks/configure-pod-container/quality-service-pod.md b/content/ja/docs/tasks/configure-pod-container/quality-service-pod.md
index 012921d2bfc..ceb917d6227 100644
--- a/content/ja/docs/tasks/configure-pod-container/quality-service-pod.md
+++ b/content/ja/docs/tasks/configure-pod-container/quality-service-pod.md
@@ -1,7 +1,7 @@
 ---
 title: PodにQuality of Serviceを設定する
 content_type: task
-weight: 30
+weight: 60
 ---
 
 
diff --git a/content/ja/docs/tasks/configure-pod-container/security-context.md b/content/ja/docs/tasks/configure-pod-container/security-context.md
index c4e1523af4f..68ce416b5fa 100644
--- a/content/ja/docs/tasks/configure-pod-container/security-context.md
+++ b/content/ja/docs/tasks/configure-pod-container/security-context.md
@@ -1,7 +1,7 @@
 ---
 title: Podとコンテナにセキュリティコンテキストを設定する
 content_type: task
-weight: 80
+weight: 110
 ---
 
 <!-- overview -->
diff --git a/content/ja/docs/tasks/configure-pod-container/share-process-namespace.md b/content/ja/docs/tasks/configure-pod-container/share-process-namespace.md
index b5fd61777e6..b6be6e07e1d 100644
--- a/content/ja/docs/tasks/configure-pod-container/share-process-namespace.md
+++ b/content/ja/docs/tasks/configure-pod-container/share-process-namespace.md
@@ -2,7 +2,7 @@
 title: Pod内のコンテナ間でプロセス名前空間を共有する
 min-kubernetes-server-version: v1.10
 content_type: task
-weight: 160
+weight: 200
 ---
 
 <!-- overview -->
diff --git a/content/ja/docs/tasks/configure-pod-container/static-pod.md b/content/ja/docs/tasks/configure-pod-container/static-pod.md
index 8c5f9f67c82..851ef4e1610 100644
--- a/content/ja/docs/tasks/configure-pod-container/static-pod.md
+++ b/content/ja/docs/tasks/configure-pod-container/static-pod.md
@@ -1,6 +1,6 @@
 ---
 title: static Podを作成する
-weight: 170
+weight: 220
 content_type: task
 ---
 
diff --git a/content/ja/docs/tasks/debug/_index.md b/content/ja/docs/tasks/debug/_index.md
index 21e34075fd2..7013b3ec48b 100644
--- a/content/ja/docs/tasks/debug/_index.md
+++ b/content/ja/docs/tasks/debug/_index.md
@@ -1,7 +1,7 @@
 ---
 title: "監視、ログ、デバッグ"
 description: クラスターのトラブルシューティングや、コンテナ化したアプリケーションのデバッグのために、監視とログをセットアップします。
-weight: 20
+weight: 40
 content_type: concept
 no_list: true
 ---
diff --git a/content/ja/docs/tasks/debug/debug-application/determine-reason-pod-failure.md b/content/ja/docs/tasks/debug/debug-application/determine-reason-pod-failure.md
index 1fbdb763aad..8f9c9c361bf 100644
--- a/content/ja/docs/tasks/debug/debug-application/determine-reason-pod-failure.md
+++ b/content/ja/docs/tasks/debug/debug-application/determine-reason-pod-failure.md
@@ -1,6 +1,7 @@
 ---
 title: Pod障害の原因を特定する
 content_type: task
+weight: 30
 ---
 
 <!-- overview -->
diff --git a/content/ja/docs/tasks/inject-data-application/_index.md b/content/ja/docs/tasks/inject-data-application/_index.md
index a28c380a268..46e24f4ff88 100644
--- a/content/ja/docs/tasks/inject-data-application/_index.md
+++ b/content/ja/docs/tasks/inject-data-application/_index.md
@@ -1,5 +1,5 @@
 ---
 title: "アプリケーションへのデータ注入"
 description: ワークロードを実行するPodの構成とその他のデータを指定します。
-weight: 30
+weight: 70
 ---
diff --git a/content/ja/docs/tasks/job/_index.md b/content/ja/docs/tasks/job/_index.md
index bde073017bc..a8773cebf52 100644
--- a/content/ja/docs/tasks/job/_index.md
+++ b/content/ja/docs/tasks/job/_index.md
@@ -1,6 +1,6 @@
 ---
 title: "Jobの実行"
 description: 並列処理を使用してJobを実行します。
-weight: 50
+weight: 90
 ---
 
diff --git a/content/ja/docs/tasks/manage-kubernetes-objects/_index.md b/content/ja/docs/tasks/manage-kubernetes-objects/_index.md
index 16150cf3d77..09c10037431 100644
--- a/content/ja/docs/tasks/manage-kubernetes-objects/_index.md
+++ b/content/ja/docs/tasks/manage-kubernetes-objects/_index.md
@@ -1,5 +1,5 @@
 ---
 title: "Kubernetesオブジェクトの管理"
 description: Kubernetes APIと対話するための宣言型および命令型のパラダイム。
-weight: 25
+weight: 50
 ---
diff --git a/content/ja/docs/tasks/network/_index.md b/content/ja/docs/tasks/network/_index.md
index 1d5796f7b7d..09669b981b3 100644
--- a/content/ja/docs/tasks/network/_index.md
+++ b/content/ja/docs/tasks/network/_index.md
@@ -1,6 +1,6 @@
 ---
 title: "ネットワーク"
 description: クラスターのネットワークの設定方法を学びます。
-weight: 160
+weight: 140
 ---
 
diff --git a/content/ja/docs/tasks/run-application/_index.md b/content/ja/docs/tasks/run-application/_index.md
index 17d2339e7e1..fc1a4e9de90 100644
--- a/content/ja/docs/tasks/run-application/_index.md
+++ b/content/ja/docs/tasks/run-application/_index.md
@@ -1,6 +1,6 @@
 ---
 title: "アプリケーションの実行"
 description: ステートレスアプリケーションとステートフルアプリケーションの両方を実行および管理します。
-weight: 40
+weight: 80
 ---
 
diff --git a/content/ja/docs/tasks/tls/_index.md b/content/ja/docs/tasks/tls/_index.md
index 42234c709ea..11844cf63dc 100644
--- a/content/ja/docs/tasks/tls/_index.md
+++ b/content/ja/docs/tasks/tls/_index.md
@@ -1,6 +1,6 @@
 ---
 title: "TLS"
-weight: 100
+weight: 120
 description: Transport Layer Security(TLS)を使用して、クラスター内のトラフィックを保護する方法について理解します。
 ---
 

From 53641dfce9a0701acf7fa15b885669ba8f7d93b1 Mon Sep 17 00:00:00 2001
From: Sascha Grunert <sgrunert@redhat.com>
Date: Fri, 10 Mar 2023 08:24:11 +0100
Subject: [PATCH 116/272] [KEP-2731] Add docs for Kubelet OpenTelemetry Tracing
 graduation

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
---
 .../cluster-administration/system-traces.md   | 22 ++++++++++++++-----
 .../feature-gates.md                          |  3 ++-
 2 files changed, 19 insertions(+), 6 deletions(-)

diff --git a/content/en/docs/concepts/cluster-administration/system-traces.md b/content/en/docs/concepts/cluster-administration/system-traces.md
index e43def4436a..52cf194a882 100644
--- a/content/en/docs/concepts/cluster-administration/system-traces.md
+++ b/content/en/docs/concepts/cluster-administration/system-traces.md
@@ -76,7 +76,7 @@ For more information about the `TracingConfiguration` struct, see
 
 ### kubelet traces
 
-{{< feature-state for_k8s_version="v1.25" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
 
 The kubelet CRI interface and authenticated http servers are instrumented to generate
 trace spans. As with the apiserver, the endpoint and sampling rate are configurable.
@@ -86,10 +86,7 @@ Enabled without a configured endpoint, the default OpenTelemetry Collector recei
 
 #### Enabling tracing in the kubelet
 
-To enable tracing, enable the `KubeletTracing`
-[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
-on the kubelet. Also, provide the kubelet with a
-[tracing configuration](https://github.com/kubernetes/component-base/blob/release-1.25/tracing/api/v1/types.go).
+To enable tracing, apply the [tracing configuration](https://github.com/kubernetes/component-base/blob/release-1.27/tracing/api/v1/types.go).
 This is an example snippet of a kubelet config that records spans for 1 in 10000 requests, and uses the default OpenTelemetry endpoint:
 
 ```yaml
@@ -103,6 +100,21 @@ tracing:
   samplingRatePerMillion: 100
 ```
 
+If the `samplingRatePerMillion` is set to one million (`1000000`), then every
+span will be sent to the exporter.
+
+The kubelet in Kubernetes v{{< skew currentVersion >}} collects spans from
+the garbage collection, pod synchronization routine as well as every gRPC
+method. Connected container runtimes like CRI-O and containerd can link the
+traces to their exported spans to provide additional context of information.
+
+Please note that exporting spans always comes with a small performance overhead
+on the networking and CPU side, depending on the overall configuration of the
+system. If there is any issue like that in a cluster which is running with
+tracing enabled, then mitigate the problem by either reducing the
+`samplingRatePerMillion` or disabling tracing completely by removing the
+configuration.
+
 ## Stability
 
 Tracing instrumentation is still under active development, and may change
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 9c31844ba18..898c623876a 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
@@ -131,7 +131,8 @@ For a reference to old feature gates that are removed, please refer to
 | `KubeletPodResourcesGetAllocatable` | `false` | Alpha | 1.21 | 1.22 |
 | `KubeletPodResourcesGetAllocatable` | `true` | Beta | 1.23 | |
 | `KubeletPodResourcesDynamicResources` | `false` | Alpha | 1.27 | |
-| `KubeletTracing` | `false` | Alpha | 1.25 | |
+| `KubeletTracing` | `false` | Alpha | 1.25 | 1.26 |
+| `KubeletTracing` | `true` | Beta | 1.27 | |
 | `LegacyServiceAccountTokenTracking` | `false` | Alpha | 1.26 | 1.26 |
 | `LegacyServiceAccountTokenTracking` | `true` | Beta | 1.27 | |
 | `LocalStorageCapacityIsolationFSQuotaMonitoring` | `false` | Alpha | 1.15 | - |

From 4e1b4f7f43a70cdb86cbcc439292cd0d7866c286 Mon Sep 17 00:00:00 2001
From: Kensei Nakada <handbomusic@gmail.com>
Date: Wed, 5 Apr 2023 21:56:27 +0900
Subject: [PATCH 117/272] fix based on the suggestion

---
 .../_posts/2023-04-11-topology-spread-features.md  | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/content/en/blog/_posts/2023-04-11-topology-spread-features.md b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
index bd908eece73..422e8dd2869 100644
--- a/content/en/blog/_posts/2023-04-11-topology-spread-features.md
+++ b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
@@ -11,11 +11,11 @@ evergreen: true
 In Kubernetes v1.19, [Pod Topology Spread Constraints](https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/) went to GA.
 It is the feature to control how Pods are spread to each failure-domain (regions, zones, nodes etc).
 
-As time passes, we've got further feedbacks from users,
-and we're actively working on improving the Topology Spread via three KEPs from v1.25.
-All of these features have reached beta in Kubernetes v1.27 and been enabled by default.
+As time passed, we received feedback from users,
+and, as a result, we're actively working on improving the Topology Spread feature via three KEPs.
+All of these features have reached beta in Kubernetes v1.27 and are enabled by default.
 
-This blog post is going to introduce each feature and the usecase/issue behind them.
+This blog post introduces each feature and the use case behind each of them.
 
 ## KEP-3022: min domains in Pod Topology Spread
 
@@ -27,8 +27,8 @@ Some users want to force spreading Pods over a minimum number of domains, and if
 Then, we introduced the `minDomains` parameter in the Pod Topology Spread. 
 Via `minDomains` parameter, you can define the minimum number of domains. 
 
-For example, there are 3 Nodes with the enough capacity, 
-and newly created replicaset has the following `topologySpreadConstraints` in template.
+For example, assume there are 3 Nodes with the enough capacity, 
+and a newly created replicaset has the following `topologySpreadConstraints` in template.
 
 ```yaml
 topologySpreadConstraints:
@@ -41,7 +41,7 @@ topologySpreadConstraints:
         foo: bar
 ```
 
-This case, 3 Pods will be scheduled to those 3 Nodes,
+In this case, 3 Pods will be scheduled to those 3 Nodes,
 but other 2 Pods from this replicaset will be unschedulable until more Nodes join the cluster.
 
 The cluster autoscaler provisions new Nodes based on these unschedulable Pods,

From e64805f21c3e750ec9cdba91cc1c25b2adcb876a Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Wed, 5 Apr 2023 21:33:11 +0800
Subject: [PATCH 118/272] sync determine-reason-pod-failure

sync determine-reason-pod-failure
---
 .../debug/debug-application/determine-reason-pod-failure.md   | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/zh-cn/docs/tasks/debug/debug-application/determine-reason-pod-failure.md b/content/zh-cn/docs/tasks/debug/debug-application/determine-reason-pod-failure.md
index 697459bb065..ce1059ecac1 100644
--- a/content/zh-cn/docs/tasks/debug/debug-application/determine-reason-pod-failure.md
+++ b/content/zh-cn/docs/tasks/debug/debug-application/determine-reason-pod-failure.md
@@ -203,11 +203,11 @@ is empty and the container exited with an error. The log output is limited to
 * See the `terminationMessagePath` field in
   [Container](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#container-v1-core).
 * Learn about [retrieving logs](/docs/concepts/cluster-administration/logging/).
-* Learn about [Go templates](https://golang.org/pkg/text/template/).
+* Learn about [Go templates](https://pkg.go.dev/text/template).
 -->
 
 * 参考 [Container](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#container-v1-core)
   资源的 `terminationMessagePath` 字段。
 * 了解[检索日志](/zh-cn/docs/concepts/cluster-administration/logging/)。
-* 了解 [Go 模板](https://golang.org/pkg/text/template/)。
+* 了解 [Go 模板](https://pkg.go.dev/text/template)。
 

From 81482cfcef87e1c71a431ed140dd7006e3a63ea3 Mon Sep 17 00:00:00 2001
From: Alex Wang <wangqingcan1990@gmail.com>
Date: Wed, 5 Apr 2023 22:59:17 +0800
Subject: [PATCH 119/272] blog: update content about matchLabelKeys

Signed-off-by: Alex Wang <wangqingcan1990@gmail.com>
---
 .../2023-04-11-topology-spread-features.md    | 25 +++++++++++--------
 1 file changed, 15 insertions(+), 10 deletions(-)

diff --git a/content/en/blog/_posts/2023-04-11-topology-spread-features.md b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
index 422e8dd2869..328017e2ffc 100644
--- a/content/en/blog/_posts/2023-04-11-topology-spread-features.md
+++ b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
@@ -93,18 +93,23 @@ this feature to beta and it was enabled by default since.
 
 ## KEP-3243: Respect PodTopologySpread after rolling upgrades
 
-Pod Topology Spread uses the fields `topologyKey` or `labelSelector` to identify the group of pods over which
-spreading will be calculated. But it applies to all pods in a Deployment irrespective of their owning
-ReplicaSet. As a result, when a new revision is rolled out, spreading will apply across pods from both the
-old and new ReplicaSets, and so by the time the new ReplicaSet is completely rolled out and the old one is
-rolled back, the actual spreading we are left with may not match expectations because the deleted pods from
-the older ReplicaSet will cause skewed distribution for the remaining pods.
+Pod Topology Spread uses the field `labelSelector` to identify the group of pods over which
+spreading will be calculated. When using topology spreading with Deployments, it is common
+practice to use the `labelSelector` of the Deployment as the `labelSelector` in the topology
+spread constraints. However, this implies that all pods of a Deployment are part of the spreading
+calculation, regardless of whether they belong to different revisions. As a result, when a new revision
+is rolled out, spreading will apply across pods from both the old and new ReplicaSets, and so by the
+time the new ReplicaSet is completely rolled out and the old one is rolled back, the actual spreading
+we are left with may not match expectations because the deleted pods from the older ReplicaSet will cause
+skewed distribution for the remaining pods. To avoid this problem, in the past users needed to add a
+revision label to Deployment and update it manually at each rolling upgrade (both the label on the
+podTemplate and the `labelSelector` in the `topologySpreadConstraints`).
 
-In order to solve this problem and to make more accurate decisions in scheduling, we added a new named
+To solve this problem once and for all, and to make more accurate decisions in scheduling, we added a new named
 `matchLabelKeys` to `topologySpreadConstraints`. `matchLabelKeys` is a list of pod label keys to select
-the pods over which spreading will be calculated. The keys are used to lookup values from the pod labels,
-those key-value labels are ANDed with `labelSelector` to select the group of existing pods over
-which spreading will be calculated for the incoming pod.
+the pods over which spreading will be calculated. The keys are used to lookup values from the labels of
+the Pod being scheduled, those key-value labels are ANDed with `labelSelector` to select the group of
+existing pods over which spreading will be calculated for the incoming pod.
 
 With `matchLabelKeys`, you don't need to update the `pod.spec` between different revisions.
 The controller/operator just needs to set different values to the same label key for different revisions.

From 01e5986d92d013948012c50027ce4d5b63eae1fc Mon Sep 17 00:00:00 2001
From: harshitasao <harshitasao@gmail.com>
Date: Wed, 5 Apr 2023 23:58:33 +0530
Subject: [PATCH 120/272] Added v1.27 Release blog

---
 .../_posts/2023-04-11-kubernetes-1.27-blog.md | 36 +++++++++----------
 1 file changed, 18 insertions(+), 18 deletions(-)

diff --git a/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md b/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
index 7d933b4119d..1e6c5603314 100644
--- a/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
+++ b/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
@@ -31,17 +31,17 @@ Special thanks to [Britnee Laverack](https://www.instagram.com/artsyfie/) for cr
 ## Freeze `k8s.gcr.io` image registry
 
 Replacing the old image registry, [k8s.gcr.io](https://cloud.google.com/container-registry/) with [registry.k8s.io](https://github.com/kubernetes/registry.k8s.io) which has been generally available for several months. The Kubernetes project created and runs the `registry.k8s.io` image registry, which is fully controlled by the community.
-This means that the old registry `k8s.gcr.io` will be frozen and no further images for Kubernetes and related subprojects will be pushed to the old registry. 
+This means that the old registry `k8s.gcr.io` will be frozen and no further images for Kubernetes and related sub-projects will be published to the old registry. 
 
-What does this change mean for contributors:
+What does this change mean for contributors?
 
-* If you are a maintainer of a subproject, you will need to update your manifests and Helm charts to use the new registry.
+* If you are a maintainer of a sub-project, you will need to update your manifests and Helm charts to use the new registry. For more information, checkout this [project](https://github.com/kubernetes-sigs/community-images).
 
-What does this change mean for end users:
+What does this change mean for end users?
 
-* This Kubernetes release will not be published to the old registry.
+* Kubernetes `v1.27` release will not be published to the `k8s.gcr.io` registry.
 
-* Patch releases for v1.24, v1.25, and v1.26 will no longer be published to the old registry after April. 
+* Patch releases for `v1.24`, `v1.25`, and `v1.26` will no longer be published to the old registry after April. 
 
 * Starting in v1.25, the default image registry has been set to `registry.k8s.io`. This value is overridable in kubeadm and kubelet but setting it to `k8s.gcr.io` will fail for new releases after April as they won’t be present in the old registry.
 
@@ -53,7 +53,7 @@ What does this change mean for end users:
 To use seccomp profile defaulting, you must run the kubelet with the `--seccomp-default` [command line flag](/docs/reference/command-line-tools-reference/kubelet) enabled for each node where you want to use it. 
 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.
 
-You can find more detailed information about a possible upgrade and downgrade strategy in the related Kubernetes Enhancement Proposal (KEP): [Enable seccomp by default](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2413-seccomp-by-default).
+You can find detailed information about a possible upgrade and downgrade strategy in the related Kubernetes Enhancement Proposal (KEP): [Enable seccomp by default](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2413-seccomp-by-default).
 
 ## Mutable scheduling directives for Jobs graduates to GA
 
@@ -63,7 +63,7 @@ This feature allows updating a Job's scheduling directives before it starts, whi
 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 and [scheduling gates](/docs/concepts/scheduling-eviction/pod-scheduling-readiness/).
+,annotations, and [scheduling gates](/docs/concepts/scheduling-eviction/pod-scheduling-readiness/).
 Find more details in the KEP:
 [Allow updating scheduling directives of jobs](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/2926-job-mutable-scheduling-directives).
 
@@ -76,32 +76,32 @@ This feature graduates to stable in this release. You can find more details in t
 
 ## Pod Scheduling Readiness goes to beta 
 
-Pods were considered ready for scheduling once created. Kubernetes scheduler does its due diligence to find nodes to place all pending Pods. However, in a real-world case, some Pods may stay in a _missing-essential-resources_ state for a long period. These Pods actually churn the scheduler (and downstream integrators like Cluster Autoscaler) in an unnecessary manner.
+Upon creation, Pods are ready for scheduling. Kubernetes scheduler does its due diligence to find nodes to place all pending Pods. However, in a real-world case, some Pods may stay in a _missing-essential-resources_ state for a long period. These Pods actually churn the scheduler (and downstream integrators like Cluster Autoscaler) in an unnecessary manner.
 
 By specifying/removing a Pod's `.spec.schedulingGates`, you can control when a Pod is ready to be considered for scheduling.
 
-The `schedulingGates` field contains a list of strings, and each string literal is perceived as a criteria that Pod should be satisfied before considered schedulable. This field can be initialized only when a Pod is created (either by the client, or mutated during admission). After creation, each schedulingGate can be removed in an arbitrary order, but addition of a new scheduling gate is disallowed.
+The `schedulingGates` field contains a list of strings, and each string literal is perceived as a criteria that must be satisfied before a Pod is considered schedulable. This field can be initialized only when a Pod is created (either by the client, or mutated during admission). After creation, each schedulingGate can be removed in an arbitrary order, but addition of a new scheduling gate is disallowed.
 
 ## Node log access via Kubernetes API
 
-This feature helps cluster administrators debug issues with services running on nodes by allowing them to query service logs. To use the feature, ensure that the `NodeLogQuery` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled for that node, and that the kubelet configuration options `enableSystemLogHandler` and `enableSystemLogQuery` are both set to true. 
+This feature helps cluster administrators debug issues with services running on nodes by allowing them to query service logs. To use this feature, ensure that the `NodeLogQuery` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled on that node, and that the kubelet configuration options `enableSystemLogHandler` and `enableSystemLogQuery` are both set to true. 
 On Linux, we assume that service logs are available via journald. On Windows, we assume that service logs are available in the application log provider. You can also fetch logs from the `/var/log/` and `C:\var\log` directories on Linux and Windows, respectively.
 
-A cluster administrator can try out this alpha feature on all their nodes, or on just a subset.
+A cluster administrator can try out this alpha feature across all nodes of their cluster, or on a subset of them.
 
 ## ReadWriteOncePod PersistentVolume access mode goes to beta 
 
-ReadWriteOncePod is a new access mode for [PersistentVolumes](/docs/concepts/storage/persistent-volumes/#persistent-volumes) (PVs) and [PersistentVolumeClaims](/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims) (PVCs) introduced in Kubernetes v1.22. This access mode enables you to restrict volume access to a single pod in the cluster, ensuring that only one pod can write to the volume at a time. This can be particularly useful for stateful workloads that require single-writer access to storage.
+Kuberentes `v1.22` introduced a new access mode `ReadWriteOncePod` for [PersistentVolumes](/docs/concepts/storage/persistent-volumes/#persistent-volumes) (PVs) and [PersistentVolumeClaims](/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims) (PVCs). This access mode enables you to restrict volume access to a single pod in the cluster, ensuring that only one pod can write to the volume at a time. This can be particularly useful for stateful workloads that require single-writer access to storage.
 
 The ReadWriteOncePod beta adds support for [scheduler preemption](/docs/concepts/scheduling-eviction/pod-priority-preemption/)
 of pods that use ReadWriteOncePod PVCs.
-Scheduler preemption allows higher-priority pods to preempt lower-priority pods, for example when a pod (A) with a ReadWriteOncePod PVC is scheduled, and if another pod (B) is found using the same PVC and pod (A) has higher priority, the scheduler will return an "Unschedulable" status and attempt to preempt pod (B).
+Scheduler preemption allows higher-priority pods to preempt lower-priority pods. For example when a pod (A) with a `ReadWriteOncePod` PVC is scheduled, if another pod (B) is found using the same PVC and pod (A) has higher priority, the scheduler will return an `Unschedulable` status and attempt to preempt pod (B).
 For more context, see the KEP: [ReadWriteOncePod PersistentVolume AccessMode](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/2485-read-write-once-pod-pv-access-mode).
 
 
 ## Respect PodTopologySpread after rolling upgrades
 
-`matchLabelKeys` is a list of pod label keys to select the pods over which spreading will be calculated. The keys are used to lookup values from the pod labels, those key-value labels are ANDed with `labelSelector` to select the group of existing pods over which spreading will be calculated for the incoming pod. Keys that don't exist in the pod labels will be ignored. A null or empty list means only match against the `labelSelector`.
+`matchLabelKeys` is a list of pod label keys used to select the pods over which spreading will be calculated. The keys are used to lookup values from the pod labels. Those key-value labels are ANDed with `labelSelector` to select the group of existing pods over which spreading will be calculated for the incoming pod. Keys that don't exist in the pod labels will be ignored. A null or empty list means only match against the `labelSelector`.
 
 With `matchLabelKeys`, users don't need to update the `pod.spec` between different revisions. The controller/operator just needs to set different values to the same `label` key for different revisions. The scheduler will assume the values automatically based on `matchLabelKeys`. For example, if users use Deployment, they can use the label keyed with `pod-template-hash`, which is added automatically by the Deployment controller, to distinguish between different revisions in a single Deployment.
 
@@ -125,7 +125,7 @@ Get more information on this from the KEP: [Speed up SELinux volume relabeling u
 
 This is a volume manager refactoring that allows the kubelet to populate additional information about how
 existing volumes are mounted during the kubelet startup. In general, this makes volume cleanup more robust. 
-By adding `NewVolumeManagerReconstruction` feature gate and enabling it by default will enhance the discovery of mounted volumes during kubelet startup.
+If you enable the `NewVolumeManagerReconstruction` feature gate on a node, you'll get enhanced discovery of mounted volumes during kubelet startup.
 
 Before Kubernetes v1.25, the kubelet used different default behavior for discovering mounted volumes during the kubelet startup. If you disable this feature gate (it's enabled by default), you select the legacy discovery behavior.
 
@@ -133,7 +133,7 @@ In Kubernetes v1.25 and v1.26, this behavior toggle was part of the `SELinuxMoun
 
 ## Mutable Pod Scheduling Directives goes to beta
 
-This allows mutating a pod that is blocked on a scheduling readiness gate with a more constrained node affinity/selector. It gives the ability to mutate a pods scheduling directives before it is allowed to be scheduled, and gives an external resource controller the ability to influence pod placement while at the same time offload actual pod-to-node assignment to kube-scheduler.
+This allows mutating a pod that is blocked on a scheduling readiness gate with a more constrained node affinity/selector. It gives the ability to mutate a pods scheduling directives before it is allowed to be scheduled and gives an external resource controller the ability to influence pod placement while at the same time offload actual pod-to-node assignment to kube-scheduler.
 
 This opens the door for a new pattern of adding scheduling features to Kubernetes.  Specifically, building lightweight schedulers that implement features not supported by kube-scheduler, while relying on the existing kube-scheduler to support all upstream features and handle the pod-to-node binding. This pattern should be the preferred one if the custom feature doesn't require implementing a schedule plugin, which entails re-building and maintaining a custom kube-scheduler binary.
 
@@ -181,7 +181,7 @@ Kubernetes v1.27 is available for download on [GitHub](https://github.com/kubern
  
 ## Release team
 
-Kubernetes is only possible with the support, commitment, and hard work of its community. Each release team is made up of dedicated community volunteers who work together to build the many pieces that make up the Kubernetes releases you rely on. This requires the specialized skills of people from all corners of our community, from the code itself to its documentation and project management.
+Kubernetes is only possible with the support, commitment, and hard work of its community. Each release team is made up of dedicated community volunteers who work together to build the many pieces that make up the Kubernetes releases you rely on. This requires people with specialised skills from all corners of our community, from the code itself to its documentation and project management.
 
 Special thanks to our Release Lead Xander Grzywinski for guiding us through a smooth and successful release cycle and to all members of the release team for supporting one another and working so hard to produce the v1.27 release for the community.
 

From e475112590fe2e8c2b09a4c1a50dc25f1af95344 Mon Sep 17 00:00:00 2001
From: Paco Xu <paco.xu@daocloud.io>
Date: Thu, 6 Apr 2023 11:42:37 +0800
Subject: [PATCH 121/272] add memory qos

---
 .../en/docs/concepts/workloads/pods/pod-qos.md   | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/content/en/docs/concepts/workloads/pods/pod-qos.md b/content/en/docs/concepts/workloads/pods/pod-qos.md
index fa0385e11e6..d95b0815ad7 100644
--- a/content/en/docs/concepts/workloads/pods/pod-qos.md
+++ b/content/en/docs/concepts/workloads/pods/pod-qos.md
@@ -85,6 +85,22 @@ CPU limit or a CPU request.
 Containers in a Pod can request other resources (not CPU or memory) and still be classified as
 `BestEffort`.
 
+## Memory QoS with cgroup v2
+
+{{< feature-state for_k8s_version="v1.22" state="alpha" >}}
+
+Memory QoS uses the memory controller of cgroup v2 to guarantee memory resources in Kubernetes.
+Memory requests and limits of containers in pod are used to set specific interfaces `memory.min`
+and `memory.high` provided by the memory controller. When `memory.min` is set to memory requests,
+memory resources are reserved and never reclaimed by the kernel; this is how Memory QoS ensures
+memory availability for Kubernetes pods. And if memory limits are set in the container,
+this means that the system needs to limit container memory usage; Memory QoS uses `memory.high`
+to throttle workload approaching its memory limit, ensuring that the system is not overwhelmed
+by instantaneous memory allocation.
+
+Memory QoS relies on QoS class to determine which settings to apply; however, these are different
+mechanisms that both provide controls over quality of service.
+
 ## Some behavior is independent of QoS class {#class-independent-behavior}
 
 Certain behavior is independent of the QoS class assigned by Kubernetes. For example:

From a1419760642e99897ffec04010de197327b4c758 Mon Sep 17 00:00:00 2001
From: Kante Yin <kerthcet@gmail.com>
Date: Thu, 6 Apr 2023 14:49:15 +0800
Subject: [PATCH 122/272] Address the comment about NodeInclusionPolicy

Signed-off-by: Kante Yin <kerthcet@gmail.com>
---
 .../2023-04-11-topology-spread-features.md    | 41 ++++++++++---------
 1 file changed, 21 insertions(+), 20 deletions(-)

diff --git a/content/en/blog/_posts/2023-04-11-topology-spread-features.md b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
index 328017e2ffc..44e27aaeb18 100644
--- a/content/en/blog/_posts/2023-04-11-topology-spread-features.md
+++ b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
@@ -19,15 +19,15 @@ This blog post introduces each feature and the use case behind each of them.
 
 ## KEP-3022: min domains in Pod Topology Spread
 
-Pod Topology Spread has the `maxSkew` parameter to define the degree to which Pods may be unevenly distributed. 
+Pod Topology Spread has the `maxSkew` parameter to define the degree to which Pods may be unevenly distributed.
 
-But, there wasn't a way to control the number of domains over which we should spread. 
+But, there wasn't a way to control the number of domains over which we should spread.
 Some users want to force spreading Pods over a minimum number of domains, and if there aren't enough already present, make the cluster-autoscaler provision them.
 
-Then, we introduced the `minDomains` parameter in the Pod Topology Spread. 
-Via `minDomains` parameter, you can define the minimum number of domains. 
+Then, we introduced the `minDomains` parameter in the Pod Topology Spread.
+Via `minDomains` parameter, you can define the minimum number of domains.
 
-For example, assume there are 3 Nodes with the enough capacity, 
+For example, assume there are 3 Nodes with the enough capacity,
 and a newly created replicaset has the following `topologySpreadConstraints` in template.
 
 ```yaml
@@ -35,7 +35,7 @@ topologySpreadConstraints:
 - maxSkew: 1
   minDomains: 5 # requires 5 Nodes at least.
   whenUnsatisfiable: DoNotSchedule # minDomains is valid only when DoNotSchedule is used.
-  topologyKey: kubernetes.io/hostname 
+  topologyKey: kubernetes.io/hostname
   labelSelector:
     matchLabels:
         foo: bar
@@ -49,15 +49,16 @@ and as a result, the replicas are finally spread over 5 Nodes.
 
 ## KEP-3094: Take taints/tolerations into consideration when calculating PodTopologySpread skew
 
-Before this, when we deploy a pod with `podTopologySpread` configured, we'll take all
-affinity nodes(satisfied with pod nodeAffinity and nodeSelector) into consideration
-in filtering and scoring, but a node with pod untolerated taint may also be a candidate
-because we didn't take care of node taints, which will lead to the pod pending.
+Before this enhancement, when you deploy a pod with `podTopologySpread` configured, kube-scheduler would
+take all inclined nodes(satisfied with pod nodeAffinity and nodeSelector) into consideration
+in filtering and scoring, but would not care about whether the node taints are tolerated by the incoming pod or not.
+This may lead to a node with untolerated taint best fit the pod in podTopologySpread plugin, and as a result,
+the pod will stuck in pending for it violates the nodeTaint plugin.
 
-To avoid this and make a more fine-gained decision in scheduling, we introduced two new fields in
-`TopologySpreadConstraint` to define node inclusion policies including nodeAffinity and nodeTaint.
+ To allow more fine-gained decisions about which Nodes to account for when calculating spreading skew, we introduced
+ two new fields in `TopologySpreadConstraint` to define node inclusion policies including nodeAffinity and nodeTaint.
 
-It mostly looks like:
+A manifest that applies these policies looks like the following:
 
 ```yaml
 apiVersion: v1
@@ -75,17 +76,17 @@ spec:
 ```
 
 **nodeAffinityPolicy** indicates how we'll treat Pod's nodeAffinity/nodeSelector in pod topology spreading.
-If `Honor`, we'll filter out nodes not matching nodeAffinity/nodeSelector in calculation.
-If `Ignore`, these nodes will be included instead.
+If `Honor`, kube-scheduler will filter out nodes not matching nodeAffinity/nodeSelector in the calculation of spreading skew.
+If `Ignore`, all nodes will be included, regardless of whether they match the Pod's nodeAffinity/nodeSelector or not.
 
-For backwards-compatibility, nodeAffinityPolicy is default to `Honor`.
+For backwards-compatibility, nodeAffinityPolicy defaults to `Honor`.
 
 **nodeTaintsPolicy** indicates how we'll treat node taints in pod topology spreading.
-If `Honor`, only tainted nodes for which the incoming pod has a toleration, will be included in calculation.
-If `Ignore`, we'll not consider the node taints at all in calculation, so a node with pod untolerated taint
-will also be included.
+If `Honor`, only tainted nodes for which the incoming pod has a toleration, will be included in the calculation of spreading skew.
+If `Ignore`, kube-scheduler will not consider the node taints at all in the calculation of spreading skew, so a node with
+pod untolerated taint will also be included.
 
-For backwards-compatibility, nodeTaintsPolicy is default to the `Ignore`.
+For backwards-compatibility, nodeTaintsPolicy defaults to the `Ignore`.
 
 The feature was introduced in v1.25 as alpha level. By default, it was disabled, so if you want to use this feature in v1.25,
 you have to enable the feature gate `NodeInclusionPolicyInPodTopologySpread` actively. In the following v1.26, we graduated

From 5c70b42c21e57196dc7ccfd3b552031f84e0849a Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Thu, 6 Apr 2023 18:24:52 +0800
Subject: [PATCH 123/272] sync garbage-collection

sync garbage-collection
---
 .../zh-cn/docs/concepts/architecture/garbage-collection.md    | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/zh-cn/docs/concepts/architecture/garbage-collection.md b/content/zh-cn/docs/concepts/architecture/garbage-collection.md
index 4c18685ec23..bcde52e62a4 100644
--- a/content/zh-cn/docs/concepts/architecture/garbage-collection.md
+++ b/content/zh-cn/docs/concepts/architecture/garbage-collection.md
@@ -351,9 +351,9 @@ configure garbage collection:
 <!--
 * Learn more about [ownership of Kubernetes objects](/docs/concepts/overview/working-with-objects/owners-dependents/).
 * Learn more about Kubernetes [finalizers](/docs/concepts/overview/working-with-objects/finalizers/).
-* Learn about the [TTL controller](/docs/concepts/workloads/controllers/ttlafterfinished/) (beta) that cleans up finished Jobs.
+* Learn about the [TTL controller](/docs/concepts/workloads/controllers/ttlafterfinished/) that cleans up finished Jobs.
 -->
 * 进一步了解 [Kubernetes 对象的属主关系](/zh-cn/docs/concepts/overview/working-with-objects/owners-dependents/)。
 * 进一步了解 Kubernetes [finalizers](/zh-cn/docs/concepts/overview/working-with-objects/finalizers/)。
-* 进一步了解 [TTL 控制器](/zh-cn/docs/concepts/workloads/controllers/ttlafterfinished/) (Beta)，
+* 进一步了解 [TTL 控制器](/zh-cn/docs/concepts/workloads/controllers/ttlafterfinished/)，
   该控制器负责清理已完成的 Job。

From 1c376d1b74a0c811b62edabe7a8e1ed6fee24845 Mon Sep 17 00:00:00 2001
From: harshitasao <harshitasao@gmail.com>
Date: Thu, 6 Apr 2023 20:38:47 +0530
Subject: [PATCH 124/272] some nits

---
 content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md b/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
index 1e6c5603314..5969990535a 100644
--- a/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
+++ b/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
@@ -48,7 +48,7 @@ What does this change mean for end users?
 * If you want to increase the reliability of your cluster and remove dependency on the community-owned registry or you are running Kubernetes in networks where external traffic is restricted, you should consider hosting local image registry mirrors. Some cloud vendors may offer hosted solutions for this.
 
 
-## SeccompDefault graduates to stable
+## `SeccompDefault` graduates to stable
 
 To use seccomp profile defaulting, you must run the kubelet with the `--seccomp-default` [command line flag](/docs/reference/command-line-tools-reference/kubelet) enabled for each node where you want to use it. 
 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.

From a601eb520f9ada4846875daf13e06df59ed8a3fe Mon Sep 17 00:00:00 2001
From: Nate W <natew@cncf.io>
Date: Thu, 6 Apr 2023 10:42:49 -0700
Subject: [PATCH 125/272] Update schedule.yaml. Updated with correct 1.27.1
 patch and cherry pick dates

Signed-off-by: Nate W <natew@cncf.io>
---
 data/releases/schedule.yaml | 66 +++++++------------------------------
 1 file changed, 12 insertions(+), 54 deletions(-)

diff --git a/data/releases/schedule.yaml b/data/releases/schedule.yaml
index 16f1526065f..19ce450ae92 100644
--- a/data/releases/schedule.yaml
+++ b/data/releases/schedule.yaml
@@ -1,4 +1,16 @@
 schedules:
+- release: 1.27
+  releaseDate: 2024-04-11
+  maintenanceModeStartDate: 2024-04-28
+  endOfLifeDate: 2024-06-28
+  next:
+    release: 1.27.1
+    cherryPickDeadline: 2023-04-07
+    targetDate: 2023-04-12
+  previousPatches:
+    - release: 1.27.0
+      cherryPickDeadline: ""
+      targetDate: 2023-04-11
 - release: 1.26
   releaseDate: 2022-12-09
   maintenanceModeStartDate: 2023-12-28
@@ -64,57 +76,3 @@ schedules:
     - release: 1.25.0
       cherryPickDeadline: ""
       targetDate: 2022-08-23
-- release: 1.24
-  releaseDate: 2022-05-03
-  maintenanceModeStartDate: 2023-05-28
-  endOfLifeDate: 2023-07-28
-  next:
-    release: 1.24.13
-    cherryPickDeadline: 2023-04-07
-    targetDate: 2023-04-12
-  previousPatches:
-    - release: 1.24.12
-      cherryPickDeadline: 2023-03-10
-      targetDate: 2023-03-15
-    - release: 1.24.11
-      cherryPickDeadline: 2023-02-10
-      targetDate: 2023-02-15
-      note: >-
-        [Some container images might be **unsigned** due to a temporary issue with the promotion process](https://groups.google.com/a/kubernetes.io/g/dev/c/MwSx761slM0/m/4ajkeUl0AQAJ)
-    - release: 1.24.10
-      cherryPickDeadline: 2023-01-13
-      targetDate: 2023-01-18
-    - release: 1.24.9
-      cherryPickDeadline: 2022-12-02
-      targetDate: 2022-12-08
-    - release: 1.24.8
-      cherryPickDeadline: 2022-11-04
-      targetDate: 2022-11-09
-    - release: 1.24.7
-      cherryPickDeadline: 2022-10-07
-      targetDate: 2022-10-12
-    - release: 1.24.6
-      cherryPickDeadline: 2022-09-20
-      targetDate: 2022-09-21
-      note: >-
-        [Out-of-Band release to fix the regression introduced in 1.24.5](https://groups.google.com/a/kubernetes.io/g/dev/c/tA6LNOQTR4Q/m/zL73maPTAQAJ)
-    - release: 1.24.5
-      cherryPickDeadline: 2022-09-09
-      targetDate: 2022-09-14
-      note: >-
-        [Regression](https://groups.google.com/a/kubernetes.io/g/dev/c/tA6LNOQTR4Q/m/zL73maPTAQAJ)
-    - release: 1.24.4
-      cherryPickDeadline: 2022-08-12
-      targetDate: 2022-08-17
-    - release: 1.24.3
-      cherryPickDeadline: 2022-07-08
-      targetDate: 2022-07-13
-    - release: 1.24.2
-      cherryPickDeadline: 2022-06-10
-      targetDate: 2022-06-15
-    - release: 1.24.1
-      cherryPickDeadline: 2022-05-20
-      targetDate: 2022-05-24
-    - release: 1.24.0
-      cherryPickDeadline: ""
-      targetDate: 2022-05-03

From 4b91b4abde1fb9fad6c0a92d848a85abf9e9091a Mon Sep 17 00:00:00 2001
From: harshitasao <harshitasao@gmail.com>
Date: Fri, 7 Apr 2023 00:20:03 +0530
Subject: [PATCH 126/272] added release webinar date and time

---
 content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md b/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
index 5969990535a..128c03ceac4 100644
--- a/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
+++ b/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
@@ -198,7 +198,7 @@ In the v1.27 release cycle, which [ran for 14 weeks](https://github.com/kubernet
 
 ## Upcoming release webinar
 
-Join members of the Kubernetes v1.27 release team on <date> to learn about the major features of this release, as well as deprecations and removals to help plan for upgrades. For more information and registration, visit the [event page](#) on the CNCF Online Programs site.
+Join members of the Kubernetes v1.27 release team on Friday, April 14, 2023, at 10 a.m. PDT to learn about the major features of this release, as well as deprecations and removals to help plan for upgrades. For more information and registration, visit the [event page](https://community.cncf.io/events/details/cncf-cncf-online-programs-presents-cncf-live-webinar-kubernetes-v127-release/) on the CNCF Online Programs site.
 
 ## Get Involved
 

From 249dfc0d1cdd74517400aa78f72d289ed1b02fbc Mon Sep 17 00:00:00 2001
From: Arhell <arhell333@gmail.com>
Date: Fri, 7 Apr 2023 00:27:31 +0300
Subject: [PATCH 127/272] [id] Updated kubectl describe svc output

---
 .../services-networking/connect-applications-service.md       | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/content/id/docs/concepts/services-networking/connect-applications-service.md b/content/id/docs/concepts/services-networking/connect-applications-service.md
index f2264ed9aa6..5fcd5593b34 100644
--- a/content/id/docs/concepts/services-networking/connect-applications-service.md
+++ b/content/id/docs/concepts/services-networking/connect-applications-service.md
@@ -93,8 +93,12 @@ Labels:              run=my-nginx
 Annotations:         <none>
 Selector:            run=my-nginx
 Type:                ClusterIP
+IP Family Policy:    SingleStack
+IP Families:         IPv4
 IP:                  10.0.162.149
+IPs:                 10.0.162.149
 Port:                <unset> 80/TCP
+TargetPort:          80/TCP
 Endpoints:           10.244.2.5:80,10.244.3.4:80
 Session Affinity:    None
 Events:              <none>

From ae626b96c61d9e397d98b140853e2fff149cbb0f Mon Sep 17 00:00:00 2001
From: Kensei Nakada <handbomusic@gmail.com>
Date: Fri, 7 Apr 2023 08:54:39 +0900
Subject: [PATCH 128/272] fix based on reviews

---
 .../_posts/2023-04-11-topology-spread-features.md    | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/content/en/blog/_posts/2023-04-11-topology-spread-features.md b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
index 44e27aaeb18..f8fa99cdc5c 100644
--- a/content/en/blog/_posts/2023-04-11-topology-spread-features.md
+++ b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
@@ -9,7 +9,7 @@ evergreen: true
 **Authors:** [Alex Wang](https://github.com/denkensk)(Shopee), [Kante Yin](https://github.com/kerthcet)(DaoCloud), [Kensei Nakada](https://github.com/sanposhiho)(Mercari)
 
 In Kubernetes v1.19, [Pod Topology Spread Constraints](https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/) went to GA.
-It is the feature to control how Pods are spread to each failure-domain (regions, zones, nodes etc).
+It is the feature to control how Pods are spread in the cluster topology or failure domains (regions, zones, nodes etc).
 
 As time passed, we received feedback from users,
 and, as a result, we're actively working on improving the Topology Spread feature via three KEPs.
@@ -50,10 +50,10 @@ and as a result, the replicas are finally spread over 5 Nodes.
 ## KEP-3094: Take taints/tolerations into consideration when calculating PodTopologySpread skew
 
 Before this enhancement, when you deploy a pod with `podTopologySpread` configured, kube-scheduler would
-take all inclined nodes(satisfied with pod nodeAffinity and nodeSelector) into consideration
+take the Nodes that satisfy the Pod's nodeAffinity and nodeSelector into consideration
 in filtering and scoring, but would not care about whether the node taints are tolerated by the incoming pod or not.
-This may lead to a node with untolerated taint best fit the pod in podTopologySpread plugin, and as a result,
-the pod will stuck in pending for it violates the nodeTaint plugin.
+This may lead to a node with untolerated taint as the only candidate for spreading, and as a result,
+the pod will stuck in Pending if it doesn't tolerate the taint.
 
  To allow more fine-gained decisions about which Nodes to account for when calculating spreading skew, we introduced
  two new fields in `TopologySpreadConstraint` to define node inclusion policies including nodeAffinity and nodeTaint.
@@ -106,14 +106,14 @@ skewed distribution for the remaining pods. To avoid this problem, in the past u
 revision label to Deployment and update it manually at each rolling upgrade (both the label on the
 podTemplate and the `labelSelector` in the `topologySpreadConstraints`).
 
-To solve this problem once and for all, and to make more accurate decisions in scheduling, we added a new named
+To solve this problem with a simpler API, we added a new field named
 `matchLabelKeys` to `topologySpreadConstraints`. `matchLabelKeys` is a list of pod label keys to select
 the pods over which spreading will be calculated. The keys are used to lookup values from the labels of
 the Pod being scheduled, those key-value labels are ANDed with `labelSelector` to select the group of
 existing pods over which spreading will be calculated for the incoming pod.
 
 With `matchLabelKeys`, you don't need to update the `pod.spec` between different revisions.
-The controller/operator just needs to set different values to the same label key for different revisions.
+The controller or operator managing rollouts just needs to set different values to the same label key for different revisions.
 The scheduler will assume the values automatically based on `matchLabelKeys`.
 For example, if you are configuring a Deployment, you can use the label keyed with
 [pod-template-hash](https://kubernetes.io//docs/concepts/workloads/controllers/deployment/#pod-template-hash-label),

From 43f5b0cd1a76f128d996965a0e0848660fbb6fb1 Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Wed, 5 Apr 2023 21:44:11 +0800
Subject: [PATCH 129/272] sync rbac

sync rbac
---
 .../docs/reference/access-authn-authz/rbac.md | 64 +++++++++++--------
 1 file changed, 36 insertions(+), 28 deletions(-)

diff --git a/content/zh-cn/docs/reference/access-authn-authz/rbac.md b/content/zh-cn/docs/reference/access-authn-authz/rbac.md
index 482be53b4dc..604af3ea733 100644
--- a/content/zh-cn/docs/reference/access-authn-authz/rbac.md
+++ b/content/zh-cn/docs/reference/access-authn-authz/rbac.md
@@ -431,19 +431,19 @@ There are two reasons for this restriction:
 
 <!--
 1. Making `roleRef` immutable allows granting someone `update` permission on an existing binding
-object, so that they can manage the list of subjects, without being able to change
-the role that is granted to those subjects.
+   object, so that they can manage the list of subjects, without being able to change
+   the role that is granted to those subjects.
 -->
 1. 将 `roleRef` 设置为不可以改变，这使得可以为用户授予对现有绑定对象的 `update` 权限，
    这样可以让他们管理主体列表，同时不能更改被授予这些主体的角色。
 
 <!--
 1. A binding to a different role is a fundamentally different binding.
-Requiring a binding to be deleted/recreated in order to change the `roleRef`
-ensures the full list of subjects in the binding is intended to be granted
-the new role (as opposed to enabling or accidentally modifying only the roleRef
-without verifying all of the existing subjects should be given the new role's
-permissions).
+   Requiring a binding to be deleted/recreated in order to change the `roleRef`
+   ensures the full list of subjects in the binding is intended to be granted
+   the new role (as opposed to enabling or accidentally modifying only the roleRef
+   without verifying all of the existing subjects should be given the new role's
+   permissions).
 -->
 2. 针对不同角色的绑定是完全不一样的绑定。要求通过删除/重建绑定来更改 `roleRef`，
    这样可以确保要赋予绑定的所有主体会被授予新的角色（而不是在允许或者不小心修改了
@@ -559,17 +559,19 @@ For example, `kubectl get configmaps --field-selector=metadata.name=my-configmap
 {{< /note >}}
 
 <!--
-Rather than referring to individual `resources` and `verbs`
-you can use the wildcard `*` symbol to refer to all such objects.
-For `nonResourceURLs` you can use the wildcard `*` symbol as a suffix glob match and
-for `apiGroups` and `resourceNames` an empty set means that everything is allowed.
+Rather than referring to individual `resources`、`apiGroups`, and `verbs`,
+you can use the wildcard `*` symbol to refer to all such objects. 
+For `nonResourceURLs`, you can use the wildcard `*` as a suffix glob match.
+For `resourceNames`, an empty set means that everything is allowed.
 Here is an example that allows access to perform any current and future action on
-all current and future resources (note, this is similar to the built-in `cluster-admin` role).
+all current and future resources in the `example.com` API group.
+This is similar to the built-in `cluster-admin` role.
 -->
-使用通配符 `*` 可以批量引用所有的 `resources` 和 `verbs` 对象，无需逐一引用。
-对于 `nonResourceURLs`，可以将通配符 `*` 作为后缀实现全局通配，
-对于 `apiGroups` 和 `resourceNames`，空集表示没有任何限制。
-下面的示例允许对所有当前和未来资源执行所有动作（注意，这类似于内置的 `cluster-admin`）。
+你可愈使用通配符 `*` 可以批量引用所有的 `resources`、`apiGroups` 和 `verbs` 对象， 无需逐一引用。
+对于 `nonResourceURLs`，你可以将通配符 `*` 作为后缀实现全局通配，
+对于 `resourceNames`，空集表示没有任何限制。
+下面的示例对 `example.com` API 组中所有当前和未来资源执行所有动作。
+这类似于内置的 `cluster-admin`。
 
 ```yaml
 apiVersion: rbac.authorization.k8s.io/v1
@@ -585,14 +587,13 @@ rules:
 
 {{< caution >}}
 <!--
-Using wildcards in resource and verb entries could result in 
-overly permissive access being granted to sensitive resources.
+Using wildcards in resource and verb entries could result in overly permissive access being granted
+to sensitive resources.
 For instance, if a new resource type is added, or a new subresource is added,
-or a new custom verb is checked, the wildcard entry automatically grants access,
-which may be undesirable.
+or a new custom verb is checked, the wildcard entry automatically grants access, which may be undesirable.
 The [principle of least privilege](/docs/concepts/security/rbac-good-practices/#least-privilege)
-should be employed, using specific resources and verbs to ensure
-only the permissions required for the workload to function correctly are applied.
+should be employed, using specific resources and verbs to ensure only the permissions required for the
+workload to function correctly are applied.
 -->
 在 resources 和 verbs 条目中使用通配符会为敏感资源授予过多的访问权限。
 例如，如果添加了新的资源类型、新的子资源或新的自定义动词，
@@ -953,7 +954,7 @@ Subjects can be groups, users or
 
 Kubernetes represents usernames as strings.
 These can be: plain names, such as "alice"; email-style names, like "bob@example.com";
-or numeric user IDs represented as a string.  It is up to you as a cluster administrator
+or numeric user IDs represented as a string. It is up to you as a cluster administrator
 to configure the [authentication modules](/docs/reference/access-authn-authz/authentication/)
 so that authentication produces usernames in the format you want.
 -->
@@ -1168,7 +1169,10 @@ Auto-reconciliation is enabled by default if the RBAC authorizer is active.
 <!--
 ### API discovery roles {#discovery-roles}
 
-Default role bindings authorize unauthenticated and authenticated users to read API information that is deemed safe to be publicly accessible (including CustomResourceDefinitions). To disable anonymous unauthenticated access, add `--anonymous-auth=false` to the API server configuration.
+Default role bindings authorize unauthenticated and authenticated users to read API information
+that is deemed safe to be publicly accessible (including CustomResourceDefinitions).
+To disable anonymous unauthenticated access, add `--anonymous-auth=false` to
+the API server configuration.
 
 To view the configuration of these roles via `kubectl` run:
 -->
@@ -1717,8 +1721,9 @@ RBAC API 会阻止用户通过编辑角色或者角色绑定来提升权限。
 You can only create/update a role if at least one of the following things is true:
 
 1. You already have all the permissions contained in the role, at the same scope as the object being modified
-(cluster-wide for a ClusterRole, within the same namespace or cluster-wide for a Role).
-2. You are granted explicit permission to perform the `escalate` verb on the `roles` or `clusterroles` resource in the `rbac.authorization.k8s.io` API group.
+   (cluster-wide for a ClusterRole, within the same namespace or cluster-wide for a Role).
+2. You are granted explicit permission to perform the `escalate` verb on the `roles` or
+   `clusterroles` resource in the `rbac.authorization.k8s.io` API group.
 -->
 ### 对角色创建或更新的限制 {#restrictions-on-role-creation-or-update}
 
@@ -1735,8 +1740,11 @@ containing that permission. To allow a user to create/update roles:
 
 1. Grant them a role that allows them to create/update Role or ClusterRole objects, as desired.
 2. Grant them permission to include specific permissions in the roles they create/update:
-    * implicitly, by giving them those permissions (if they attempt to create or modify a Role or ClusterRole with permissions they themselves have not been granted, the API request will be forbidden)
-    * or explicitly allow specifying any permission in a `Role` or `ClusterRole` by giving them permission to perform the `escalate` verb on `roles` or `clusterroles` resources in the `rbac.authorization.k8s.io` API group
+    * implicitly, by giving them those permissions (if they attempt to create or modify a Role or
+     ClusterRole with permissions they themselves have not been granted, the API request will be forbidden)
+    * or explicitly allow specifying any permission in a `Role` or `ClusterRole` by giving them
+     permission to perform the `escalate` verb on `roles` or `clusterroles` resources in the
+     `rbac.authorization.k8s.io` API group
 -->
 例如，如果 `user-1` 没有列举集群范围所有 Secret 的权限，他将不能创建包含该权限的 ClusterRole。
 若要允许用户创建/更新角色：

From 4343803804c9b2eb541eb82f3d5fafa0d9a8ecb3 Mon Sep 17 00:00:00 2001
From: Swati Sehgal <swsehgal@redhat.com>
Date: Fri, 7 Apr 2023 06:51:14 +0530
Subject: [PATCH 130/272] node: topologymgr: docs: Kubelet Topology Manager
 graduation to GA (#40044)

* node: topologymgr: docs: Kubelet Topology Manager graduation to GA

Signed-off-by: Swati Sehgal <swsehgal@redhat.com>

* Update content/en/docs/reference/command-line-tools-reference/feature-gates.md

---------

Signed-off-by: Swati Sehgal <swsehgal@redhat.com>
Co-authored-by: Qiming Teng <tengqm@outlook.com>
---
 .../command-line-tools-reference/feature-gates.md         | 5 +++--
 .../en/docs/tasks/administer-cluster/topology-manager.md  | 8 +-------
 2 files changed, 4 insertions(+), 9 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 898c623876a..8441f0bc186 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
@@ -206,8 +206,6 @@ For a reference to old feature gates that are removed, please refer to
 | `TopologyAwareHints` | `false` | Alpha | 1.21 | 1.22 |
 | `TopologyAwareHints` | `false` | Beta | 1.23 | 1.23 |
 | `TopologyAwareHints` | `true` | Beta | 1.24 | |
-| `TopologyManager` | `false` | Alpha | 1.16 | 1.17 |
-| `TopologyManager` | `true` | Beta | 1.18 | |
 | `TopologyManagerPolicyAlphaOptions` | `false` | Alpha | 1.26 | |
 | `TopologyManagerPolicyBetaOptions` | `false` | Beta | 1.26 | |
 | `TopologyManagerPolicyOptions` | `false` | Alpha | 1.26 | |
@@ -348,6 +346,9 @@ For a reference to old feature gates that are removed, please refer to
 | `StatefulSetMinReadySeconds` | `false` | Alpha | 1.22 | 1.22 |
 | `StatefulSetMinReadySeconds` | `true` | Beta | 1.23 | 1.24 |
 | `StatefulSetMinReadySeconds` | `true` | GA | 1.25 | - |
+| `TopologyManager` | `false` | Alpha | 1.16 | 1.17 |
+| `TopologyManager` | `true` | Beta | 1.18 | 1.26 |
+| `TopologyManager` | `true` | GA | 1.27 | - |
 | `WatchBookmark` | `false` | Alpha | 1.15 | 1.15 |
 | `WatchBookmark` | `true` | Beta | 1.16 | 1.16 |
 | `WatchBookmark` | `true` | GA | 1.17 | - |
diff --git a/content/en/docs/tasks/administer-cluster/topology-manager.md b/content/en/docs/tasks/administer-cluster/topology-manager.md
index 7dac6b42562..7d06ebe14c8 100644
--- a/content/en/docs/tasks/administer-cluster/topology-manager.md
+++ b/content/en/docs/tasks/administer-cluster/topology-manager.md
@@ -15,7 +15,7 @@ weight: 150
 
 <!-- overview -->
 
-{{< feature-state state="beta" for_k8s_version="v1.18" >}}
+{{< feature-state state="stable" for_k8s_version="v1.27" >}}
 
 An increasing number of systems leverage a combination of CPUs and hardware accelerators to
 support latency-critical execution and high-throughput parallel computation. These include
@@ -60,12 +60,6 @@ the pod can be accepted or rejected from the node based on the selected hint.
 The hint is then stored in the Topology Manager for use by the *Hint Providers* when making the
 resource allocation decisions.
 
-### Enable the Topology Manager feature
-
-Support for the Topology Manager requires `TopologyManager`
-[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) to be enabled.
-It is enabled by default starting with Kubernetes 1.18.
-
 ## Topology Manager Scopes and Policies
 
 The Topology Manager currently:

From b15fe215660258f9efcbffc7302ec4044e5bb23b Mon Sep 17 00:00:00 2001
From: windsonsea <haifeng.yao@daocloud.io>
Date: Thu, 23 Mar 2023 23:38:25 +0800
Subject: [PATCH 131/272] [zh] sync /workloads/pods/pod-qos.md

---
 .../docs/concepts/workloads/pods/pod-qos.md   | 213 ++++++++++++++++++
 1 file changed, 213 insertions(+)
 create mode 100644 content/zh-cn/docs/concepts/workloads/pods/pod-qos.md

diff --git a/content/zh-cn/docs/concepts/workloads/pods/pod-qos.md b/content/zh-cn/docs/concepts/workloads/pods/pod-qos.md
new file mode 100644
index 00000000000..10647dfc16f
--- /dev/null
+++ b/content/zh-cn/docs/concepts/workloads/pods/pod-qos.md
@@ -0,0 +1,213 @@
+---
+title: Pod QoS 类
+content_type: concept
+weight: 85
+---
+<!--
+title: Pod Quality of Service Classes
+content_type: concept
+weight: 85
+-->
+
+<!-- overview -->
+
+<!--
+This page introduces _Quality of Service (QoS) classes_ in Kubernetes, and explains
+how Kubernetes assigns a QoS class to each Pods as a consequence of the resource
+constraints that you specify for the containers in that Pod. Kubernetes relies on this
+classification to make decisions about which Pods to evict when there are not enough
+available resources on a Node.
+-->
+本页介绍 Kubernetes 中的 **服务质量（Quality of Service，QoS）** 类，
+阐述 Kubernetes 如何根据为 Pod 中的容器指定的资源约束为每个 Pod 设置 QoS 类。
+Kubernetes 依赖这种分类来决定当 Node 上没有足够可用资源时要驱逐哪些 Pod。
+
+<!-- body -->
+
+<!--
+## Quality of Service classes
+-->
+## QoS 类   {#qos-class}
+
+<!--
+Kubernetes classifies the Pods that you run and allocates each Pod into a specific
+_quality of service (QoS) class_. Kubernetes uses that classification to influence how different
+pods are handled. Kubernetes does this classification based on the
+[resource requests](/docs/concepts/configuration/manage-resources-containers/)
+of the {{< glossary_tooltip text="Containers" term_id="container" >}} in that Pod, along with
+how those requests relate to resource limits.
+This is known as {{< glossary_tooltip text="Quality of Service" term_id="qos-class" >}}
+(QoS) class. Kubernetes assigns every Pod a QoS class based on the resource requests
+and limits of its component Containers. QoS classes are used by Kubernetes to decide
+which Pods to evict from a Node experiencing
+[Node Pressure](/docs/concepts/scheduling-eviction/node-pressure-eviction/). The possible
+QoS classes are `Guaranteed`, `Burstable`, and `BestEffort`. When a Node runs out of resources,
+Kubernetes will first evict `BestEffort` Pods running on that Node, followed by `Burstable` and
+finally `Guaranteed` Pods. When this eviction is due to resource pressure, only Pods exceeding
+resource requests are candidates for eviction.
+-->
+Kubernetes 对你运行的 Pod 进行分类，并将每个 Pod 分配到特定的 **QoS 类**中。
+Kubernetes 使用这种分类来影响不同 Pod 被处理的方式。Kubernetes 基于 Pod
+中{{< glossary_tooltip text="容器" term_id="container" >}}的[资源请求](/zh-cn/docs/concepts/configuration/manage-resources-containers/)进行分类，
+同时确定这些请求如何与资源限制相关。
+这称为{{< glossary_tooltip text="服务质量" term_id="qos-class" >}} (QoS) 类。
+Kubernetes 基于每个 Pod 中容器的资源请求和限制为 Pod 设置 QoS 类。Kubernetes 使用 QoS
+类来决定从遇到[节点压力](/zh-cn/docs/concepts/scheduling-eviction/node-pressure-eviction/)的
+Node 中驱逐哪些 Pod。可选的 QoS 类有 `Guaranteed`、`Burstable` 和 `BestEffort`。
+当一个 Node 耗尽资源时，Kubernetes 将首先驱逐在该 Node 上运行的 `BestEffort` Pod，
+然后是 `Burstable` Pod，最后是 `Guaranteed` Pod。当这种驱逐是由于资源压力时，
+只有超出资源请求的 Pod 才是被驱逐的候选对象。
+
+### Guaranteed
+
+<!--
+Pods that are `Guaranteed` have the strictest resource limits and are least likely
+to face eviction. They are guaranteed not to be killed until they exceed their limits
+or there are no lower-priority Pods that can be preempted from the Node. They may
+not acquire resources beyond their specified limits. These Pods can also make
+use of exclusive CPUs using the
+[`static`](/docs/tasks/administer-cluster/cpu-management-policies/#static-policy) CPU management policy.
+-->
+`Guaranteed` Pod 具有最严格的资源限制，并且最不可能面临驱逐。
+在这些 Pod 超过其自身的限制或者从 Node 上没有可以抢占的低优先级 Pod 之前，
+这些 Pod 保证不会被杀死。这些 Pod 不可以获得超出其指定 limit 的资源。这些 Pod 也可以使用
+[`static`](/zh-cn/docs/tasks/administer-cluster/cpu-management-policies/#static-policy)
+CPU 管理策略来使用独占的 CPU。
+
+<!--
+#### Criteria
+
+For a Pod to be given a QoS class of `Guaranteed`:
+-->
+#### 判据
+
+Pod 被赋予 `Guaranteed` QoS 类的几个判据：
+
+<!--
+* Every Container in the Pod must have a memory limit and a memory request.
+* For every Container in the Pod, the memory limit must equal the memory request.
+* Every Container in the Pod must have a CPU limit and a CPU request.
+* For every Container in the Pod, the CPU limit must equal the CPU request.
+-->
+* Pod 中的每个容器必须有内存 limit 和内存 request。
+* 对于 Pod 中的每个容器，内存 limit 必须等于内存 request。
+* Pod 中的每个容器必须有 CPU limit 和 CPU request。
+* 对于 Pod 中的每个容器，CPU limit 必须等于 CPU request。
+
+### Burstable
+
+<!--
+Pods that are `Burstable` have some lower-bound resource guarantees based on the request, but
+do not require a specific limit. If a limit is not specified, it defaults to a
+limit equivalent to the capacity of the Node, which allows the Pods to flexibly increase
+their resources if resources are available. In the event of Pod eviction due to Node
+resource pressure, these Pods are evicted only after all `BestEffort` Pods are evicted.
+Because a `Burstable` Pod can include a Container that has no resource limits or requests, a Pod
+that is `Burstable` can try to use any amount of node resources.
+-->
+`Burstable` Pod 有一些基于 request 的资源下限保证，但不需要特定的 limit。
+如果未指定 limit，则默认为其 limit 等于 Node 容量，这允许 Pod 在资源可用时灵活地增加其资源。
+在由于 Node 资源压力导致 Pod 被驱逐的情况下，只有在所有 `BestEffort` Pod 被驱逐后
+这些 Pod 才会被驱逐。因为 `Burstable` Pod 可以包括没有资源 limit 或资源 request 的容器，
+所以 `Burstable` Pod 可以尝试使用任意数量的节点资源。
+
+<!--
+#### Criteria
+
+A Pod is given a QoS class of `Burstable` if:
+
+* The Pod does not meet the criteria for QoS class `Guaranteed`.
+* At least one Container in the Pod has a memory or CPU request or limit.
+-->
+#### 判据
+
+Pod 被赋予 `Burstable` QoS 类的几个判据：
+
+* Pod 不满足针对 QoS 类 `Guaranteed` 的判据。
+* Pod 中至少一个容器有内存或 CPU request 或 limit。
+
+### BestEffort
+
+<!--
+Pods in the `BestEffort` QoS class can use node resources that aren't specifically assigned
+to Pods in other QoS classes. For example, if you have a node with 16 CPU cores available to the
+kubelet, and you assign 4 CPU cores to a `Guaranteed` Pod, then a Pod in the `BestEffort`
+QoS class can try to use any amount of the remaining 12 CPU cores.
+
+The kubelet prefers to evict `BestEffort` Pods if the node comes under resource pressure.
+-->
+`BestEffort` QoS 类中的 Pod 可以使用未专门分配给其他 QoS 类中的 Pod 的节点资源。
+例如若你有一个节点有 16 核 CPU 可供 kubelet 使用，并且你将 4 核 CPU 分配给一个 `Guaranteed` Pod，
+那么 `BestEffort` QoS 类中的 Pod 可以尝试任意使用剩余的 12 核 CPU。
+
+如果节点遇到资源压力，kubelet 将优先驱逐 `BestEffort` Pod。
+
+<!--
+#### Criteria
+
+A Pod has a QoS class of `BestEffort` if it doesn't meet the criteria for either `Guaranteed`
+or `Burstable`. In other words, a Pod is `BestEffort` only if none of the Containers in the Pod have a
+memory limit or a memory request, and none of the Containers in the Pod have a
+CPU limit or a CPU request.
+Containers in a Pod can request other resources (not CPU or memory) and still be classified as
+`BestEffort`.
+-->
+#### 判据
+
+如果 Pod 不满足 `Guaranteed` 或 `Burstable` 的判据，则它的 QoS 类为 `BestEffort`。
+换言之，只有当 Pod 中的所有容器没有内存 limit 或内存 request，也没有 CPU limit 或
+CPU request 时，Pod 才是 `BestEffort`。Pod 中的容器可以请求（除 CPU 或内存之外的）
+其他资源并且仍然被归类为 `BestEffort`。
+
+<!--
+## Some behavior is independent of QoS class {#class-independent-behavior}
+
+Certain behavior is independent of the QoS class assigned by Kubernetes. For example:
+-->
+## 某些行为独立于 QoS 类 {#class-independent-behavior}
+
+某些行为独立于 Kubernetes 分配的 QoS 类。例如：
+
+<!--
+* Any Container exceeding a resource limit will be killed and restarted by the kubelet without
+  affecting other Containers in that Pod.
+* If a Container exceeds its resource request and the node it runs on faces
+  resource pressure, the Pod it is in becomes a candidate for [eviction](/docs/concepts/scheduling-eviction/node-pressure-eviction/).
+  If this occurs, all Containers in the Pod will be terminated. Kubernetes may create a
+  replacement Pod, usually on a different node.
+-->
+* 所有超过资源 limit 的容器都将被 kubelet 杀死并重启，而不会影响该 Pod 中的其他容器。
+* 如果一个容器超出了自身的资源 request，且该容器运行的节点面临资源压力，则该容器所在的 Pod
+  就会成为被[驱逐](/zh-cn/docs/concepts/scheduling-eviction/node-pressure-eviction/)的候选对象。
+  如果出现这种情况，Pod 中的所有容器都将被终止。Kubernetes 通常会在不同的节点上创建一个替代的 Pod。
+<!--
+* The resource request of a Pod is equal to the sum of the resource requests of
+  its component Containers, and the resource limit of a Pod is equal to the sum of
+  the resource limits of its component Containers.
+* The kube-scheduler does not consider QoS class when selecting which Pods to
+  [preempt](/docs/concepts/scheduling-eviction/pod-priority-preemption/#preemption).
+  Preemption can occur when a cluster does not have enough resources to run all the Pods
+  you defined.
+-->
+* Pod 的资源 request 等于其成员容器的资源 request 之和，Pod 的资源 limit 等于其组成容器的资源 limit 之和。
+* kube-scheduler 在选择要[抢占](/zh-cn/docs/concepts/scheduling-eviction/pod-priority-preemption/#preemption)的
+  Pod 时不考虑 QoS 类。当集群没有足够的资源来运行你所定义的所有 Pod 时，就会发生抢占。
+
+## {{% heading "whatsnext" %}}
+
+<!--
+* Learn about [resource management for Pods and Containers](/docs/concepts/configuration/manage-resources-containers/).
+* Learn about [Node-pressure eviction](/docs/concepts/scheduling-eviction/node-pressure-eviction/).
+* Learn about [Pod priority and preemption](/docs/concepts/scheduling-eviction/pod-priority-preemption/).
+* Learn about [Pod disruptions](/docs/concepts/workload/pods/disruptions/).
+* Learn how to [assign memory resources to containers and pods](/docs/tasks/configure-pod-container/assign-memory-resource/).
+* Learn how to [assign CPU resources to containers and pods](/docs/tasks/configure-pod-container/assign-cpu-resource/).
+* Learn how to [configure Quality of Service for Pods](/docs/tasks/configure-pod-container/quality-service-pod/).
+-->
+* 进一步了解[为 Pod 和容器管理资源](/zh-cn/docs/concepts/configuration/manage-resources-containers/)。
+* 进一步了解[节点压力驱逐](/zh-cn/docs/concepts/scheduling-eviction/node-pressure-eviction/)。
+* 进一步了解 [Pod 优先级和抢占](/zh-cn/docs/concepts/scheduling-eviction/pod-priority-preemption/)。
+* 进一步了解 [Pod 干扰](/zh-cn/docs/concepts/workloads/pods/disruptions/)。
+* 进一步了解如何[为容器和 Pod 分配内存资源](/zh-cn/docs/tasks/configure-pod-container/assign-memory-resource/)。
+* 进一步了解如何[为容器和 Pod 分配 CPU 资源](/zh-cn/docs/tasks/configure-pod-container/assign-cpu-resource/)。
+* 进一步了解如何[配置 Pod 的服务质量](/zh-cn/docs/tasks/configure-pod-container/quality-service-pod/)。

From b8651be9c2e8dc42a6825a752d4cbfb904bdbf1d Mon Sep 17 00:00:00 2001
From: Madhav Jivrajani <madhav.jiv@gmail.com>
Date: Tue, 7 Mar 2023 10:22:43 +0530
Subject: [PATCH 132/272] reference/kubectl: Update docs for moving feaature to
 beta

Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com>
---
 content/en/docs/reference/kubectl/conventions.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/content/en/docs/reference/kubectl/conventions.md b/content/en/docs/reference/kubectl/conventions.md
index 2b2cb34ceca..0aaf4ef3daf 100644
--- a/content/en/docs/reference/kubectl/conventions.md
+++ b/content/en/docs/reference/kubectl/conventions.md
@@ -22,9 +22,11 @@ For a stable output in a script:
 
 ## Subresources
 
-* You can use the `--subresource` alpha flag for kubectl commands like `get`, `patch`,
+* You can use the `--subresource` beta flag for kubectl commands like `get`, `patch`,
 `edit` and `replace` to fetch and update subresources for all resources that
 support them. Currently, only the `status` and `scale` subresources are supported.
+  * For `kubectl edit`, the `scale` subresource is not supported. If you use  `--subresource` with
+    `kubectl edit` and specify `scale` as the subresource, the command will error out.
 * The API contract against a subresource is identical to a full resource. While updating the
 `status` subresource to a new value, keep in mind that the subresource could be potentially
 reconciled by a controller to a different value.

From 10681a686fd24909aea8ee126ecd19ad8829d238 Mon Sep 17 00:00:00 2001
From: Guangwen Feng <fenggw-fnst@fujitsu.com>
Date: Thu, 6 Apr 2023 15:50:13 +0800
Subject: [PATCH 133/272] [zh-cn] Sync and add anchors for
 tasks/access-application-cluster/*

Signed-off-by: Guangwen Feng <fenggw-fnst@fujitsu.com>
---
 ...icate-containers-same-pod-shared-volume.md |  4 +--
 .../connecting-frontend-backend.md            |  8 +++---
 .../list-all-running-container-images.md      | 12 ++++----
 ...port-forward-access-application-cluster.md |  8 +++---
 .../web-ui-dashboard.md                       | 28 +++++++++----------
 5 files changed, 30 insertions(+), 30 deletions(-)

diff --git a/content/zh-cn/docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume.md b/content/zh-cn/docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume.md
index ed057170d86..21ca5b0a649 100644
--- a/content/zh-cn/docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume.md
+++ b/content/zh-cn/docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume.md
@@ -33,7 +33,7 @@ In this exercise, you create a Pod that runs two Containers. The two containers
 share a Volume that they can use to communicate. Here is the configuration file
 for the Pod:
 -->
-## 创建一个包含两个容器的 Pod
+## 创建一个包含两个容器的 Pod   {#creating-a-pod-that-runs-two-containers}
 
 在这个练习中，你会创建一个包含两个容器的 Pod。两个容器共享一个卷用于他们之间的通信。
 Pod 的配置文件如下：
@@ -184,7 +184,7 @@ Typically this is done through a shared filesystem, as shown in this exercise,
 or through the loopback network interface, localhost. An example of this pattern is a
 web server along with a helper program that polls a Git repository for new updates.
 -->
-## 讨论
+## 讨论   {#discussion}
 
 Pod 能有多个容器的主要原因是为了支持辅助应用（helper applications），以协助主应用（primary application）。
 辅助应用的典型例子是数据抽取，数据推送和代理。辅助应用和主应用经常需要相互通信。
diff --git a/content/zh-cn/docs/tasks/access-application-cluster/connecting-frontend-backend.md b/content/zh-cn/docs/tasks/access-application-cluster/connecting-frontend-backend.md
index 90583761edc..f66af51711d 100644
--- a/content/zh-cn/docs/tasks/access-application-cluster/connecting-frontend-backend.md
+++ b/content/zh-cn/docs/tasks/access-application-cluster/connecting-frontend-backend.md
@@ -61,7 +61,7 @@ require a supported environment. If your environment does not support this, you
 The backend is a simple hello greeter microservice. Here is the configuration
 file for the backend Deployment:
 -->
-### 使用部署对象（Deployment）创建后端
+### 使用部署对象（Deployment）创建后端   {#creating-the-backend-using-a-deployment}
 
 后端是一个简单的 hello 欢迎微服务应用。这是后端应用的 Deployment 配置文件：
 
@@ -136,7 +136,7 @@ the Pods that it routes traffic to.
 
 First, explore the Service configuration file:
 -->
-### 创建 `hello` Service 对象
+### 创建 `hello` Service 对象   {#creating-the-hello-service-object}
 
 将请求从前端发送到后端的关键是后端 Service。Service 创建一个固定 IP 和 DNS 解析名入口，
 使得后端微服务总是可达。Service 使用
@@ -185,7 +185,7 @@ configuration file.
 The Pods in the frontend Deployment run a nginx image that is configured
 to proxy requests to the `hello` backend Service. Here is the nginx configuration file:
 -->
-### 创建前端应用
+### 创建前端   {#creating-the-frontend}
 
 现在你已经有了运行中的后端应用，你可以创建一个可在集群外部访问的前端，并通过代理
 前端的请求连接到后端。
@@ -299,7 +299,7 @@ cluster.
 The frontend and backend are now connected. You can hit the endpoint
 by using the curl command on the external IP of your frontend Service.
 -->
-### 通过前端发送流量
+### 通过前端发送流量   {#send-traffic-through-the-frontend}
 
 前端和后端已经完成连接了。你可以使用 curl 命令通过你的前端 Service 的外部
 IP 访问服务端点。
diff --git a/content/zh-cn/docs/tasks/access-application-cluster/list-all-running-container-images.md b/content/zh-cn/docs/tasks/access-application-cluster/list-all-running-container-images.md
index 3ae5e5cee81..571b51b5dda 100644
--- a/content/zh-cn/docs/tasks/access-application-cluster/list-all-running-container-images.md
+++ b/content/zh-cn/docs/tasks/access-application-cluster/list-all-running-container-images.md
@@ -45,7 +45,7 @@ of Containers for each.
   - Use `sort` to sort the results
   - Use `uniq` to aggregate image counts
 -->
-## 列出所有命名空间下的所有容器镜像
+## 列出所有命名空间下的所有容器镜像   {#list-all-container-images-in-all-namespaces}
 
 - 使用 `kubectl get pods --all-namespaces` 获取所有命名空间下的所有 Pod
 - 使用 `-o jsonpath={.items[*].spec.containers[*].image}` 来格式化输出，以仅包含容器镜像名称。
@@ -95,7 +95,7 @@ Pod is returned instead of a list of items.
 The formatting can be controlled further by using the `range` operation to
 iterate over elements individually.
 -->
-## 按 Pod 列出容器镜像
+## 按 Pod 列出容器镜像   {#list-container-images-by-pod}
 
 可以使用 `range` 操作进一步控制格式化，以单独操作每个元素。
 
@@ -110,7 +110,7 @@ sort
 To target only Pods matching a specific label, use the -l flag.  The
 following matches only Pods with labels matching `app=nginx`.
 -->
-## 列出以标签过滤后的 Pod 的所有容器镜像
+## 列出以标签过滤后的 Pod 的所有容器镜像   {#list-container-images-filtering-by-pod-label}
 
 要获取匹配特定标签的 Pod，请使用 -l 参数。以下匹配仅与标签 `app=nginx` 相符的 Pod。
 
@@ -124,7 +124,7 @@ kubectl get pods --all-namespaces -o jsonpath="{.items[*].spec.containers[*].ima
 To target only pods in a specific namespace, use the namespace flag. The
 following matches only Pods in the `kube-system` namespace.
 -->
-## 列出以命名空间过滤后的 Pod 的所有容器镜像
+## 列出以命名空间过滤后的 Pod 的所有容器镜像   {#list-container-images-filtering-by-pod-namespace}
 
 要获取匹配特定命名空间的 Pod，请使用 namespace 参数。以下仅匹配 `kube-system` 命名空间下的 Pod。
 
@@ -138,7 +138,7 @@ kubectl get pods --namespace kube-system -o jsonpath="{.items[*].spec.containers
 As an alternative to jsonpath, Kubectl supports using [go-templates](https://pkg.go.dev/text/template)
 for formatting the output:
 -->
-## 使用 go-template 代替 jsonpath 来获取容器镜像
+## 使用 go-template 代替 jsonpath 来获取容器镜像   {#list-container-images-using-a-go-template-instead-of-jsonpath}
 
 作为 jsonpath 的替代，Kubectl 支持使用 [go-templates](https://pkg.go.dev/text/template) 来格式化输出：
 
@@ -154,7 +154,7 @@ kubectl get pods --all-namespaces -o go-template --template="{{range .items}}{{r
 * [Jsonpath](/docs/reference/kubectl/jsonpath/) reference guide
 * [Go template](https://pkg.go.dev/text/template) reference guide
 -->
-### 参考
+### 参考   {#reference}
 
 * [Jsonpath](/zh-cn/docs/reference/kubectl/jsonpath/) 参考指南
 * [Go template](https://pkg.go.dev/text/template) 参考指南
diff --git a/content/zh-cn/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md b/content/zh-cn/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md
index 69a376cfa2d..1f67c2d9dbe 100644
--- a/content/zh-cn/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md
+++ b/content/zh-cn/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md
@@ -36,7 +36,7 @@ for database debugging.
 
 1. Create a Deployment that runs MongoDB:
 -->
-## 创建 MongoDB Deployment 和服务
+## 创建 MongoDB Deployment 和服务   {#creating-mongodb-deployment-and-service}
 
 1. 创建一个运行 MongoDB 的 Deployment：
 
@@ -183,7 +183,7 @@ for database debugging.
 
 1. `kubectl port-forward` allows using resource name, such as a pod name, to select a matching pod to port forward to.
 -->
-## 转发一个本地端口到 Pod 端口
+## 转发一个本地端口到 Pod 端口   {#forward-a-local-port-to-a-port-on-the-pod}
 
 1. `kubectl port-forward` 允许使用资源名称
    （例如 Pod 名称）来选择匹配的 Pod 来进行端口转发。
@@ -237,7 +237,7 @@ for database debugging.
    ```
    Forwarding from 127.0.0.1:28015 -> 27017
    Forwarding from [::1]:28015 -> 27017
-    ```
+   ```
 
    {{< note >}}
    <!--
@@ -257,7 +257,7 @@ for database debugging.
    ```
 
 <!--
-3.  At the MongoDB command line prompt, enter the `ping` command:
+3. At the MongoDB command line prompt, enter the `ping` command:
 -->
 3. 在 MongoDB 命令行提示符下，输入 `ping` 命令：
 
diff --git a/content/zh-cn/docs/tasks/access-application-cluster/web-ui-dashboard.md b/content/zh-cn/docs/tasks/access-application-cluster/web-ui-dashboard.md
index 654c5d11a19..c76c95bd0cd 100644
--- a/content/zh-cn/docs/tasks/access-application-cluster/web-ui-dashboard.md
+++ b/content/zh-cn/docs/tasks/access-application-cluster/web-ui-dashboard.md
@@ -56,7 +56,7 @@ Dashboard 同时展示了 Kubernetes 集群中的资源状态信息和所有报
 
 The Dashboard UI is not deployed by default. To deploy it, run the following command:
 -->
-## 部署 Dashboard UI
+## 部署 Dashboard UI   {#deploying-the-dashboard-ui}
 默认情况下不会部署 Dashboard。可以通过以下命令部署：
 
 ```
@@ -71,7 +71,7 @@ Currently, Dashboard only supports logging in with a Bearer Token.
 To create a token for this demo, you can follow our guide on
 [creating a sample user](https://github.com/kubernetes/dashboard/blob/master/docs/user/access-control/creating-sample-user.md).
 -->
-## 访问 Dashboard 用户界面
+## 访问 Dashboard 用户界面   {#accessing-the-dashboard-ui}
 
 为了保护你的集群数据，默认情况下，Dashboard 会使用最少的 RBAC 配置进行部署。
 当前，Dashboard 仅支持使用 Bearer 令牌登录。
@@ -92,7 +92,7 @@ The sample user created in the tutorial will have administrative privileges and
 You can enable access to the Dashboard using the `kubectl` command-line tool,
 by running the following command:
 -->
-### 命令行代理
+### 命令行代理   {#command-line-proxy}
 
 你可以使用 `kubectl` 命令行工具来启用 Dashboard 访问，命令如下：
 
@@ -121,7 +121,7 @@ Kubeconfig 身份验证方法**不**支持外部身份提供程序或基于 x509
 <!--
 ## Welcome view
 -->
-## 欢迎界面
+## 欢迎界面   {#welcome-view}
 
 <!--
 When you access Dashboard on an empty cluster, you'll see the welcome page.
@@ -145,7 +145,7 @@ In addition, you can view which system applications are running by default in th
 Dashboard lets you create and deploy a containerized application as a Deployment and optional Service with a simple wizard.
 You can either manually specify application details, or upload a YAML or JSON _manifest_ file containing application configuration.
 -->
-## 部署容器化应用
+## 部署容器化应用   {#deploying-containerized-applications}
 
 通过一个简单的部署向导，你可以使用 Dashboard 将容器化应用作为一个 Deployment 和可选的
 Service 进行创建和部署。你可以手工指定应用的详细配置，或者上传一个包含应用配置的 YAML
@@ -161,7 +161,7 @@ Click the **CREATE** button in the upper right corner of any page to begin.
 
 The deploy wizard expects that you provide the following information:
 -->
-### 指定应用的详细配置
+### 指定应用的详细配置   {#specifying-application-details}
 
 部署向导需要你提供以下信息：
 
@@ -380,7 +380,7 @@ Kubernetes supports declarative configuration.
 In this style, all configuration is stored in manifests (YAML or JSON configuration files).
 The manifests use Kubernetes [API](/docs/concepts/overview/kubernetes-api/) resource schemas.
 -->
-### 上传 YAML 或者 JSON 文件
+### 上传 YAML 或者 JSON 文件   {#uploading-a-yaml-or-json-file}
 
 Kubernetes 支持声明式配置。所有的配置都存储在清单文件
 （YAML 或者 JSON 配置文件）中。这些
@@ -398,7 +398,7 @@ Dashboard 上传文件。
 
 Following sections describe views of the Kubernetes Dashboard UI; what they provide and how can they be used.
 -->
-## 使用 Dashboard
+## 使用 Dashboard   {#using-dashboard}
 
 以下各节描述了 Kubernetes Dashboard UI 视图；包括它们提供的内容，以及怎么使用它们。
 
@@ -409,7 +409,7 @@ When there are Kubernetes objects defined in the cluster, Dashboard shows them i
 By default only objects from the _default_ namespace are shown and
 this can be changed using the namespace selector located in the navigation menu.
 -->
-### 导航
+### 导航   {#navigation}
 
 当在集群中定义 Kubernetes 对象时，Dashboard 会在初始视图中显示它们。
 默认情况下只会显示 _默认_ 名字空间中的对象，可以通过更改导航栏菜单中的名字空间筛选器进行改变。
@@ -427,7 +427,7 @@ Node list view contains CPU and memory usage metrics aggregated across all Nodes
 The details view shows the metrics for a Node, its specification, status,
 allocated resources, events and pods running on the node.
 -->
-#### 管理概述
+#### 管理概述   {#admin-overview}
 
 集群和名字空间管理的视图，Dashboard 会列出节点、名字空间和持久卷，并且有它们的详细视图。
 节点列表视图包含从所有节点聚合的 CPU 和内存使用的度量值。
@@ -442,7 +442,7 @@ Each workload kind can be viewed separately.
 The lists summarize actionable information about the workloads,
 such as the number of ready pods for a ReplicaSet or current memory usage for a Pod.
  -->
-#### 负载
+#### 负载   {#workloads}
 
 显示选中的名字空间中所有运行的应用。
 视图按照负载类型（例如：Deployment、ReplicaSet、StatefulSet）罗列应用，并且每种负载都可以单独查看。
@@ -465,7 +465,7 @@ discovering them within a cluster.
 For that reason, Service and Ingress views show Pods targeted by them,
 internal endpoints for cluster connections and external endpoints for external users.
 -->
-#### 服务
+#### 服务   {#services}
 
 展示允许暴露给外网服务和允许集群内部发现的 Kubernetes 资源。
 因此，Service 和 Ingress 视图展示他们关联的 Pod、给集群连接使用的内部端点和给外部用户使用的外部端点。
@@ -475,7 +475,7 @@ internal endpoints for cluster connections and external endpoints for external u
 
 Storage view shows PersistentVolumeClaim resources which are used by applications for storing data.
 -->
-#### 存储
+#### 存储   {#storage}
 
 存储视图展示持久卷申领（PVC）资源，这些资源被应用程序用来存储数据。
 
@@ -496,7 +496,7 @@ The view allows for editing and managing config objects and displays secrets hid
 Pod lists and detail pages link to a logs viewer that is built into Dashboard.
 The viewer allows for drilling down logs from containers belonging to a single Pod.
 -->
-#### 日志查看器
+#### 日志查看器   {#logs-viewer}
 
 Pod 列表和详细信息页面可以链接到 Dashboard 内置的日志查看器。
 查看器可以深入查看属于同一个 Pod 的不同容器的日志。

From c1f4c5c4a2802dab33cf4ee605298d96bafdaaf4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E6=9C=B1=E6=AD=A3=E6=B5=A9=2CZhu=20Zhenghao?=
 <zhenghao.zhu@daocloud.io>
Date: Wed, 5 Apr 2023 22:36:28 +0800
Subject: [PATCH 134/272] Cleanup page rbac

---
 content/en/docs/reference/access-authn-authz/rbac.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/content/en/docs/reference/access-authn-authz/rbac.md b/content/en/docs/reference/access-authn-authz/rbac.md
index a5bb85f5029..06d84c8e06f 100644
--- a/content/en/docs/reference/access-authn-authz/rbac.md
+++ b/content/en/docs/reference/access-authn-authz/rbac.md
@@ -929,8 +929,8 @@ to a role that grants that permission. To allow a user to create/update role bin
 
 1. Grant them a role that allows them to create/update RoleBinding or ClusterRoleBinding objects, as desired.
 2. Grant them permissions needed to bind a particular role:
-    * implicitly, by giving them the permissions contained in the role.
-    * explicitly, by giving them permission to perform the `bind` verb on the particular Role (or ClusterRole).
+   * implicitly, by giving them the permissions contained in the role.
+   * explicitly, by giving them permission to perform the `bind` verb on the particular Role (or ClusterRole).
 
 For example, this ClusterRole and RoleBinding would allow `user-1` to grant other users the `admin`, `edit`, and `view` roles in the namespace `user-1-namespace`:
 
@@ -1105,7 +1105,7 @@ Examples:
 
 * Test applying a manifest file of RBAC objects, displaying changes that would be made:
 
-  ```
+  ```shell
   kubectl auth reconcile -f my-rbac-rules.yaml --dry-run=client
   ```
 
@@ -1260,7 +1260,7 @@ Here are two approaches for managing this transition:
 Run both the RBAC and ABAC authorizers, and specify a policy file that contains
 the [legacy ABAC policy](/docs/reference/access-authn-authz/abac/#policy-file-format):
 
-```
+```shell
 --authorization-mode=...,RBAC,ABAC --authorization-policy-file=mypolicy.json
 ```
 

From 19718a26feee94756ea8afe6d9057ff79f407abb Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Thu, 6 Apr 2023 20:08:32 +0800
Subject: [PATCH 135/272] localize blog:
 2023-04-06-keeping-kubernetes-secure-with-updated-go-versions

localize blog: 2023-04-06-keeping-kubernetes-secure-with-updated-go-versions
---
 ...ernetes-secure-with-updated-go-versions.md | 177 ++++++++++++++++++
 1 file changed, 177 insertions(+)
 create mode 100644 content/zh-cn/blog/_posts/2023-04-06-keeping-kubernetes-secure-with-updated-go-versions.md

diff --git a/content/zh-cn/blog/_posts/2023-04-06-keeping-kubernetes-secure-with-updated-go-versions.md b/content/zh-cn/blog/_posts/2023-04-06-keeping-kubernetes-secure-with-updated-go-versions.md
new file mode 100644
index 00000000000..9376d9410fc
--- /dev/null
+++ b/content/zh-cn/blog/_posts/2023-04-06-keeping-kubernetes-secure-with-updated-go-versions.md
@@ -0,0 +1,177 @@
+---
+layout: blog
+title: “使用更新后的 Go 版本保持 Kubernetes 安全”
+date: 2023-04-06
+slug: keeping-kubernetes-secure-with-updated-go-versions
+---
+<!--
+layout: blog
+title: "Keeping Kubernetes Secure with Updated Go Versions"
+date: 2023-04-06
+slug: keeping-kubernetes-secure-with-updated-go-versions
+-->
+
+<!--
+**Author**: [Jordan Liggitt](https://github.com/liggitt) (Google)
+-->
+
+**作者**：[Jordan Liggitt](https://github.com/liggitt) (Google)
+
+**译者**：顾欣 (ICBC)
+
+### 问题 {#the-problem}
+
+<!--
+Since v1.19 (released in 2020), the Kubernetes project provides 12-14 months of patch releases for each minor version.
+This enables users to qualify and adopt Kubernetes versions in an annual upgrade cycle and receive security fixes for a year.
+-->
+从 2020 年发布的 v1.19 版本以来，Kubernetes 项目为每个次要版本提供 12-14 个月的补丁维护期。
+这使得用户可以按照年度升级周期来评估和选用 Kubernetes 版本，并持续一年获得安全修复。
+
+<!--
+The [Go project](https://github.com/golang/go/wiki/Go-Release-Cycle#release-maintenance) releases new minor versions twice a year,
+and provides security fixes for the last two minor versions, resulting in about a year of support for each Go version.
+Even though each new Kubernetes minor version is built with a supported Go version when it is first released,
+that Go version falls out of support before the Kubernetes minor version does,
+and the lengthened Kubernetes patch support since v1.19 only widened that gap.
+-->
+[Go 项目](https://github.com/golang/go/wiki/Go-Release-Cycle#release-maintenance)每年发布两个新的次要版本，
+并为最近的两个版本提供安全修复，每个 Go 版本的维护期约为一年。
+尽管每个新的 Kubernetes 次要版本在最初发布时都是使用受支持的 Go 版本编译构建的，
+但在这一 Kubernetes 次要版本被停止支持之前，对应的 Go 版本就已经不被支持，
+并且由于 Kubernetes 从 v1.19 开始延长了补丁支持期，这个差距被进一步扩大。
+
+<!--
+At the time this was written, just over half of all [Go patch releases](https://go.dev/doc/devel/release) (88/171) have contained fixes for issues with possible security implications.
+Even though many of these issues were not relevant to Kubernetes, some were, so it remained important to use supported Go versions that received those fixes.
+-->
+在编写本文时，包含了可能对安全产生影响的问题修复的 [Go 补丁发布版本](https://go.dev/doc/devel/release)
+刚刚过半（88/171）。尽管这些问题中很多都与 Kubernetes 无关，但有些确实相关，
+因此使用受支持的、已包含了这类修复的 Go 版本是非常重要的。
+
+<!--
+An obvious solution would be to simply update Kubernetes release branches to new minor versions of Go.
+However, Kubernetes avoids [destabilizing changes in patch releases](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-release/cherry-picks.md#what-kind-of-prs-are-good-for-cherry-picks),
+and historically, this prevented updating existing release branches to new minor versions of Go, due to changes that were considered prohibitively complex, risky, or breaking to include in a patch release.
+Examples include:
+-->
+显而易见的解决方案之一是直接更新 Kubernetes 的发布分支，使用 Go 的新次要版本。
+然而，Kubernetes 避免在[补丁发布中引入破坏稳定性的变更](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-release/cherry-picks.md#what-kind-of-prs-are-good-for-cherry-picks)，
+过去，因为这些变更被认为包含过高的复杂性、风险或破坏性，不适合包含在补丁发布中，
+所以不能将现有发布分支更新到 Go 的新次要版本。
+示例包括：
+
+<!--
+* Go 1.6: enabling http/2 by default
+* Go 1.14: EINTR handling issues
+* Go 1.17: dropping x509 CN support, ParseIP changes
+* Go 1.18: disabling x509 SHA-1 certificate support by default
+* Go 1.19: dropping current-dir LookPath behavior
+-->
+* Go 1.6: 默认支持 http/2
+* Go 1.14: EINTR 问题处理
+* Go 1.17: 取消 x509 CN 支持, ParseIP 更改
+* Go 1.18: 默认禁用 x509 SHA-1 证书支持
+* Go 1.19: 取消当前目录 LookPath 行为
+
+<!--
+Some of these changes could be easily mitigated in Kubernetes code,
+some could only be opted out of via a user-specified `GODEBUG` envvar,
+and others required invasive code changes or could not be avoided at all.
+Because of this inconsistency, Kubernetes release branches have typically remained on a single Go minor version,
+and risked being unable to pick up relevant Go security fixes for the last several months of each Kubernetes minor version's support lifetime.
+-->
+其中一些更改可以基本不会影响 Kubernetes 代码，
+有些只能通过用户指定的 `GODEBUG` 环境变量来选择放弃更新，
+而其他变更则需要侵入式的代码变更或完全无法避免。
+由于这种不一致性，Kubernetes 的发布分支通常保持使用某个固定的 Go 次要版本，
+并在每个 Kubernetes 次要版本支持生命周期的最后几个月内，面临无法得到重要的 Go 安全修复的风险。
+
+<!--
+When a relevant Go security fix was only available in newer Kubernetes minor versions,
+users would have to upgrade away from older Kubernetes minor versions before their 12-14 month support period ended, just to pick up those fixes.
+If a user was not prepared to do that upgrade, it could result in vulnerable Kubernetes clusters.
+Even if a user could accommodate the unexpected upgrade, the uncertainty made Kubernetes' annual support less reliable for planning.
+-->
+当某项重要的 Go 安全修复仅出现在较新的 Kubernetes 次要版本时，
+用户必须在旧的 Kubernetes 次要版本的 12-14 个月支持期结束之前完成升级，以获取这些修复。
+如果用户没有准备好升级，可能导致 Kubernetes 集群的安全漏洞。
+即使用户可以接受这种意外升级，这种不确定性也使得 Kubernetes 在年度支持从规划角度看变得不太可靠。
+
+### 解决方案 {#the-solution}
+
+<!--
+We're happy to announce that the gap between supported Kubernetes versions and supported Go versions has been resolved as of January 2023.
+-->
+我们很高兴地宣布，自2023年1月起，受支持的 Kubernetes 版本与受支持的 Go 版本之间的差距已得到解决。
+
+<!--
+We worked closely with the Go team over the past year to address the difficulties adopting new Go versions.
+This prompted a [discussion](https://github.com/golang/go/discussions/55090), [proposal](https://github.com/golang/go/issues/56986),
+[talk at GopherCon](https://www.youtube.com/watch?v=v24wrd3RwGo), and a [design](https://go.dev/design/56986-godebug) for improving backward compatibility in Go,
+ensuring new Go versions can maintain compatible runtime behavior with previous Go versions for a minimum of two years (four Go releases).
+This allows projects like Kubernetes to update release branches to supported Go versions without exposing users to behavior changes.
+-->
+在过去的一年里，我们与 Go 团队密切合作，以解决采用新的 Go 版本的困难。
+这些工作推动了一场[讨论](https://github.com/golang/go/discussions/55090)、
+[提案](https://github.com/golang/go/issues/56986)、
+[GopherCon 演讲](https://www.youtube.com/watch?v=v24wrd3RwGo)和[设计](https://go.dev/design/56986-godebug)，
+以提高 Go 的向后兼容性，
+确保新的 Go 版本至少在两年（四个 Go 版本）内能够与之前的 Go 版本保持兼容的运行时行为。
+这使得像 Kubernetes 这样的项目能够将发布分支更新到受支持的 Go 版本，
+而不是将行为上的变更暴露给用户。
+
+<!--
+The proposed improvements are on track to be [included in Go 1.21](https://tip.golang.org/doc/godebug), and the Go team already delivered targeted compatibility improvements in a Go 1.19 patch release in late 2022.
+Those changes enabled Kubernetes 1.23+ to update to Go 1.19 in January of 2023, while avoiding any user-facing configuration or behavior changes.
+All supported Kubernetes release branches now use supported Go versions, and can pick up new Go patch releases with available security fixes.
+-->
+所提议的改进正按计划[包含在 Go 1.21 中](https://tip.golang.org/doc/godebug)，
+而且 Go 团队已经在 2022 年底的 Go 1.19 补丁发布中提供了针对兼容性的改进。
+这些更改使 Kubernetes 1.23+ 在 2023 年 1 月升级到 Go 1.19，并避免了任何用户可见的配置或行为变化。
+现在所有受支持的 Kubernetes 发布分支都使用受支持的 Go 版本，
+并且可以使用包含可用的安全修复的、新的 Go 补丁发布。
+
+<!--
+Going forward, Kubernetes maintainers remain committed to making Kubernetes patch releases as safe and non-disruptive as possible,
+so there are several requirements a new Go minor version must meet before existing Kubernetes release branches will update to use it:
+-->
+展望未来，Kubernetes 维护者仍致力于使 Kubernetes 补丁发布尽可能安全且不会造成破坏，
+因此在现有的 Kubernetes 发布分支更新使用新的 Go 次要版本之前，新的 Go 次要版本必须满足几个要求：
+
+<!--
+1. The new Go version must be available for at least 3 months.
+   This gives time for adoption by the Go community, and for reports of issues or regressions.
+2. The new Go version must be used in a new Kubernetes minor release for at least 1 month.
+   This ensures all Kubernetes release-blocking tests pass on the new Go version,
+   and gives time for feedback from the Kubernetes community on release candidates and early adoption of the new minor release.
+3. There must be no regressions from the previous Go version known to impact Kubernetes.
+4. Runtime behavior must be preserved by default, without requiring any action by Kubernetes users / administrators.
+5. Kubernetes libraries like `k8s.io/client-go` must remain compatible with the original Go version used for each minor release,
+   so consumers won't *have* to update Go versions to pick up a library patch release (though they are encouraged to build with supported Go versions,
+   which is made even easier with the [compatibility improvements](https://go.dev/design/56986-godebug) planned in Go 1.21).
+-->
+1. 新的 Go 版本必须至少已经推出 3 个月。
+   这给了 Go 社区足够的时间进行报告并解决问题。
+2. 新的 Go 版本在新的 Kubernetes 次要版本中至少已经使用了 1 个月。
+   这确保 Kubernetes 所有可能阻塞发布的测试都需要能在新的 Go 版本下通过，
+   并在早期为 Kubernetes 社区对发布候选版本和新次要版本提供反馈时间。
+3. 与先前的 Go 版本相比，不能出现新的已知会影响 Kubernetes 的问题。
+4. 默认情况下必须保持运行时行为，而无需 Kubernetes 用户/管理员采取任何操作。
+5. Kubernetes 库，如 `k8s.io/client-go` 必须与每个次要版本最初使用的 Go 版本保持兼容，
+   以便在获取库补丁时，用户不必更新 Go 版本（不过还是鼓励他们使用受支持的 Go 版本构建，
+   因为 Go 1.21 计划中的[兼容性改进](https://go.dev/design/56986-godebug)会使得这一操作变简单）。
+
+<!--
+The goal of all of this work is to unobtrusively make Kubernetes patch releases safer and more secure,
+and to make Kubernetes minor versions safe to use for the entire duration of their support lifetime.
+-->
+所有这些工作的目标是在不引人注意的情况下使 Kubernetes 补丁发布更加安全可靠，
+并确保在整个支持周期内 Kubernetes 次要版本用起来都是安全的。
+
+<!--
+Many thanks to the Go team, especially Russ Cox, for helping drive these improvements in ways that will benefit all Go users, not just Kubernetes.
+-->
+非常感谢 Go 团队，尤其是 Russ Cox，他们推动了这些改进，
+使所有 Go 用户受益，而不仅仅是 Kubernetes。
+

From 32fb48222db3cedd2c8cb9e6a8046f73d48146c8 Mon Sep 17 00:00:00 2001
From: Fabian B <fabian.baumanis@mailbox.org>
Date: Fri, 7 Apr 2023 19:31:17 +0200
Subject: [PATCH 136/272] Make meaning of "you" on the main page consistent

---
 data/i18n/de/de.toml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/data/i18n/de/de.toml b/data/i18n/de/de.toml
index cd4c3d79242..e6f10daaab4 100644
--- a/data/i18n/de/de.toml
+++ b/data/i18n/de/de.toml
@@ -79,7 +79,7 @@ other = "Kubernetes Features"
 other = """Wir sind ein <a href="https://cncf.io/">CNCF</a> Abschlussprojekt</p>"""
 
 [main_kubeweekly_baseline]
-other = "Möchten Sie die neuesten Nachrichten von Kubernetes erhalten? Melden Sie sich für KubeWeekly an."
+other = "Möchtest du die neuesten Nachrichten von Kubernetes erhalten? Melde dich für KubeWeekly an."
 
 [main_kubernetes_past_link]
 other = "Frühere Newsletter anzeigen"

From 393919cca5c0a46e97a08b424904073960ab22e1 Mon Sep 17 00:00:00 2001
From: Arhell <arhell333@gmail.com>
Date: Sat, 8 Apr 2023 02:22:41 +0300
Subject: [PATCH 137/272] [id] Update branch name in ingress-nginx github link

---
 content/id/docs/concepts/services-networking/ingress.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/id/docs/concepts/services-networking/ingress.md b/content/id/docs/concepts/services-networking/ingress.md
index 6baae2adc96..84db01b37e8 100644
--- a/content/id/docs/concepts/services-networking/ingress.md
+++ b/content/id/docs/concepts/services-networking/ingress.md
@@ -91,7 +91,7 @@ spec:
  Seperti layaknya *resource* Kubernetes yang lain, sebuah Ingress membutuhkan *field* `apiVersion`, `kind`, dan `metadata`.
  Untuk informasi umum soal bagaimana cara bekerja dengan menggunakan berkas konfigurasi, silahkan merujuk pada [melakukan deploy aplikasi](/docs/tasks/run-application/run-stateless-application-deployment/), [konfigurasi kontainer](/id/docs/tasks/configure-pod-container/configure-pod-configmap/), [mengatur *resource*](/id/docs/concepts/cluster-administration/manage-deployment/).
  Ingress seringkali menggunakan anotasi untuk melakukan konfigurasi beberapa opsi yang ada bergantung pada kontroler Ingress yang digunakan, sebagai contohnya
- adalah [anotasi rewrite-target](https://github.com/kubernetes/ingress-nginx/blob/master/docs/examples/rewrite/README.md).
+ adalah [anotasi rewrite-target](https://github.com/kubernetes/ingress-nginx/blob/main/docs/examples/rewrite/README.md).
  [Kontroler Ingress](/id/docs/concepts/services-networking/ingress-controllers) yang berbeda memiliki jenis anotasi yang berbeda. Pastikan kamu sudah terlebih dahulu memahami dokumentasi
  kontroler Ingress yang akan kamu pakai untuk mengetahui jenis anotasi apa sajakah yang disediakan.
 

From 937d9b472d1d5a0a7fb6cc66a8b3976fe7828e38 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E6=9C=B1=E6=AD=A3=E6=B5=A9=2CZhu=20Zhenghao?=
 <zhenghao.zhu@daocloud.io>
Date: Wed, 5 Apr 2023 22:04:22 +0800
Subject: [PATCH 138/272] [zh] translate page validating-admission-policy

---
 .../validating-admission-policy.md            | 562 ++++++++++++++++++
 1 file changed, 562 insertions(+)
 create mode 100644 content/zh-cn/docs/reference/access-authn-authz/validating-admission-policy.md

diff --git a/content/zh-cn/docs/reference/access-authn-authz/validating-admission-policy.md b/content/zh-cn/docs/reference/access-authn-authz/validating-admission-policy.md
new file mode 100644
index 00000000000..a470aa45db2
--- /dev/null
+++ b/content/zh-cn/docs/reference/access-authn-authz/validating-admission-policy.md
@@ -0,0 +1,562 @@
+---
+title: 验证准入策略（ValidatingAdmissionPolicy）
+content_type: concept
+---
+<!--
+reviewers:
+- liggitt
+- jpbetz
+- cici37
+title: Validating Admission Policy
+content_type: concept
+-->
+
+<!-- overview -->
+
+{{< feature-state state="alpha" for_k8s_version="v1.26" >}}
+
+<!--
+This page provides an overview of Validating Admission Policy.
+-->
+
+本页面提供验证准入策略（Validating Admission Policy）的概述。
+
+<!-- body -->
+
+<!--
+## What is Validating Admission Policy?
+
+Validating admission policies offer a declarative, in-process alternative to validating admission webhooks.
+
+Validating admission policies use the Common Expression Language (CEL) to declare the validation
+rules of a policy.
+Validation admission policies are highly configurable, enabling policy authors to define policies
+that can be parameterized and scoped to resources as needed by cluster administrators.
+-->
+## 什么是验证准入策略？ {#what-is-validating-admission-policy}
+
+验证准入策略提供一种声明式的、进程内的替代方案来验证准入 Webhook。
+
+验证准入策略使用通用表达语言 (Common Expression Language，CEL) 来声明策略的验证规则。
+验证准入策略是高度可配置的，使配置策略的作者能够根据集群管理员的需要，
+定义可以参数化并限定到资源的策略。
+
+<!--
+## What Resources Make a Policy
+
+A policy is generally made up of three resources:
+-->
+## 哪些资源构成策略  {#what-resources-make-a-policy}
+
+策略通常由三种资源构成：
+
+<!--
+- The `ValidatingAdmissionPolicy` describes the abstract logic of a policy
+  (think: "this policy makes sure a particular label is set to a particular value").
+
+- A `ValidatingAdmissionPolicyBinding` links the above resources together and provides scoping.
+  If you only want to require an `owner` label to be set for `Pods`, the binding is where you would
+  specify this restriction.
+
+- A parameter resource provides information to a ValidatingAdmissionPolicy to make it a concrete
+  statement (think "the `owner` label must be set to something that ends in `.company.com`").
+  A native type such as ConfigMap or a CRD defines the schema of a parameter resource.
+  `ValidatingAdmissionPolicy` objects specify what Kind they are expecting for their parameter resource.
+-->
+
+- `ValidatingAdmissionPolicy` 描述策略的抽象逻辑（想想看：“这个策略确保一个特定标签被设置为一个特定值”）。
+
+- 一个 `ValidatingAdmissionPolicyBinding` 将上述资源联系在一起，并提供作用域。
+  如果你只想为 `Pods` 设置一个 `owner` 标签，你就需要在这个绑定中指定这个限制。
+
+- 参数资源为 `ValidatingAdmissionPolicy` 提供信息，使其成为一个具体的声明
+  （想想看：“`owner` 标签必须被设置为以 `.company.com` 结尾的形式"）。
+  参数资源的模式（Schema）使用诸如 ConfigMap 或 CRD 这类原生类型定义。
+  `ValidatingAdmissionPolicy` 对象指定它们期望参数资源所呈现的类型。
+
+<!--
+At least a `ValidatingAdmissionPolicy` and a corresponding `ValidatingAdmissionPolicyBinding`
+must be defined for a policy to have an effect.
+
+If a `ValidatingAdmissionPolicy` does not need to be configured via parameters, simply leave
+`spec.paramKind` in  `ValidatingAdmissionPolicy` unset.
+-->
+至少要定义一个 `ValidatingAdmissionPolicy` 和一个相对应的 `ValidatingAdmissionPolicyBinding` 才能使策略生效。
+
+如果 `ValidatingAdmissionPolicy` 不需要参数配置，不设置 `ValidatingAdmissionPolicy` 中的
+`spec.paramKind` 即可。
+
+## {{% heading "prerequisites" %}}
+
+<!--
+- Ensure the `ValidatingAdmissionPolicy` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled.
+- Ensure that the `admissionregistration.k8s.io/v1alpha1` API is enabled.
+-->
+- 确保 `ValidatingAdmissionPolicy` [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)被启用。
+- 确保 `admissionregistration.k8s.io/v1alpha1` API 被启用。
+
+<!--
+## Getting Started with Validating Admission Policy
+
+Validating Admission Policy is part of the cluster control-plane. You should write and deploy them
+with great caution. The following describes how to quickly experiment with Validating Admission Policy.
+-->
+
+## 开始使用验证准入策略  {#getting-started-with-validating-admission-policy}
+
+验证准入策略是集群控制平面的一部分。你应该非常谨慎地编写和部署它们。下面介绍如何快速试验验证准入策略。
+
+<!--
+### Creating a ValidatingAdmissionPolicy
+
+The following is an example of a ValidatingAdmissionPolicy.
+-->
+### 创建一个 ValidatingAdmissionPolicy
+
+以下是一个 ValidatingAdmissionPolicy 的示例：
+
+```yaml
+apiVersion: admissionregistration.k8s.io/v1alpha1
+kind: ValidatingAdmissionPolicy
+metadata:
+  name: "demo-policy.example.com"
+spec:
+  failurePolicy: Fail
+  matchConstraints:
+    resourceRules:
+    - apiGroups: ["apps"]
+      apiVersions: ["v1"]
+      operations: ["CREATE", "UPDATE"]
+      resources: ["deployments"]
+  validations:
+    - expression: "object.spec.replicas <= 5"
+```
+
+<!--
+`spec.validations` contains CEL expressions which use the [Common Expression Language (CEL)](https://github.com/google/cel-spec)
+to validate the request. If an expression evaluates to false, the validation check is enforced
+according to the `spec.failurePolicy` field.
+
+To configure a validating admission policy for use in a cluster, a binding is required.
+The following is an example of a ValidatingAdmissionPolicyBinding.:
+-->
+`spec.validations` 包含使用[通用表达式语言 (CEL)](https://github.com/google/cel-spec)
+来验证请求的 CEL 表达式。
+如果表达式的计算结果为 false，则根据 `spec.failurePolicy` 字段强制执行验证检查处理。
+
+要配置一个在某集群中使用的验证准入策略，需要一个绑定。
+以下是一个 ValidatingAdmissionPolicyBinding 的示例：
+
+```yaml
+apiVersion: admissionregistration.k8s.io/v1alpha1
+kind: ValidatingAdmissionPolicyBinding
+metadata:
+  name: "demo-binding-test.example.com"
+spec:
+  policyName: "demo-policy.example.com"
+  matchResources:
+    namespaceSelector:
+      matchLabels:
+        environment: test
+```
+
+<!--
+When trying to create a deployment with replicas set not satisfying the validation expression, an
+error will return containing message:
+-->
+尝试创建副本集合不满足验证表达式的 Deployment 时，将返回包含以下消息的错误：
+
+```none
+ValidatingAdmissionPolicy 'demo-policy.example.com' with binding 'demo-binding-test.example.com' denied request: failed expression: object.spec.replicas <= 5
+```
+
+<!--
+The above provides a simple example of using ValidatingAdmissionPolicy without a parameter configured.
+-->
+上面提供的是一个简单的、无配置参数的 ValidatingAdmissionPolicy。
+
+<!--
+#### Parameter resources
+
+Parameter resources allow a policy configuration to be separate from its definition.
+A policy can define paramKind, which outlines GVK of the parameter resource,
+and then a policy binding ties a policy by name (via policyName) to a particular parameter resource via paramRef.
+
+If parameter configuration is needed, the following is an example of a ValidatingAdmissionPolicy
+with parameter configuration.
+-->
+#### 参数资源
+
+参数资源允许策略配置与其定义分开。
+一个策略可以定义 paramKind，给出参数资源的 GVK，
+然后一个策略绑定可以通过名称（通过 policyName）将某策略与某特定的参数资源（通过 paramRef）联系起来。
+
+如果需要参数配置，下面是一个带有参数配置的 ValidatingAdmissionPolicy 的例子：
+
+```yaml
+apiVersion: admissionregistration.k8s.io/v1alpha1
+kind: ValidatingAdmissionPolicy
+metadata:
+  name: "replicalimit-policy.example.com"
+spec:
+  failurePolicy: Fail
+  paramKind:
+    apiVersion: rules.example.com/v1
+    kind: ReplicaLimit
+  matchConstraints:
+    resourceRules:
+    - apiGroups: ["apps"]
+      apiVersions: ["v1"]
+      operations: ["CREATE", "UPDATE"]
+      resources: ["deployments"]
+  validations:
+    - expression: "object.spec.replicas <= params.maxReplicas"
+      reason: Invalid
+```
+
+<!--
+The `spec.paramKind` field of the ValidatingAdmissionPolicy specifies the kind of resources used
+to parameterize this policy. For this example, it is configured by ReplicaLimit custom resources.
+Note in this example how the CEL expression references the parameters via the CEL params variable,
+e.g. `params.maxReplicas`. `spec.matchConstraints` specifies what resources this policy is
+designed to validate. Note that the native types such like `ConfigMap` could also be used as
+parameter reference.
+-->
+ValidatingAdmissionPolicy 的 `spec.paramKind` 字段指定用于参数化此策略的资源类型。
+在这个例子中，它是由自定义资源 ReplicaLimit 配置的。
+在这个例子中请注意 CEL 表达式是如何通过 CEL params 变量引用参数的，如：`params.maxReplicas`。
+`spec.matchConstraints` 指定此策略要检查哪些资源。
+请注意，诸如 `ConfigMap` 之类的原生类型也可以用作参数引用。
+
+<!--
+The `spec.validations` fields contain CEL expressions. If an expression evaluates to false, the
+validation check is enforced according to the `spec.failurePolicy` field.
+
+The validating admission policy author is responsible for providing the ReplicaLimit parameter CRD.
+
+To configure an validating admission policy for use in a cluster, a binding and parameter resource
+are created. The following is an example of a ValidatingAdmissionPolicyBinding.
+-->
+`spec.validations` 字段包含 CEL 表达式。
+如果表达式的计算结果为 false，则根据 `spec.failurePolicy` 字段强制执行验证检查操作。
+
+验证准入策略的作者负责提供 ReplicaLimit 参数 CRD。
+
+要配置一个在某集群中使用的验证准入策略，需要创建绑定和参数资源。
+以下是 ValidatingAdmissionPolicyBinding 的示例：
+
+```yaml
+apiVersion: admissionregistration.k8s.io/v1alpha1
+kind: ValidatingAdmissionPolicyBinding
+metadata:
+  name: "replicalimit-binding-test.example.com"
+spec:
+  policyName: "replicalimit-policy.example.com"
+  paramRef:
+    name: "replica-limit-test.example.com"
+  matchResources:
+    namespaceSelector:
+      matchLabels:
+        environment: test
+```
+
+<!--
+The parameter resource could be as following:
+-->
+参数资源可以如下：
+
+```yaml
+apiVersion: rules.example.com/v1
+kind: ReplicaLimit
+metadata:
+  name: "replica-limit-test.example.com"
+maxReplicas: 3
+```
+
+<!--
+This policy parameter resource limits deployments to a max of 3 replicas in all namespaces in the
+test environment. An admission policy may have multiple bindings. To bind all other environments
+environment to have a maxReplicas limit of 100, create another ValidatingAdmissionPolicyBinding:
+-->
+此策略参数资源将限制测试环境所有名字空间中的 Deployment 最多有 3 个副本。
+一个准入策略可以有多个绑定。
+要绑定所有的其他环境，限制 maxReplicas 为 100，请创建另一个 ValidatingAdmissionPolicyBinding：
+
+```yaml
+apiVersion: admissionregistration.k8s.io/v1alpha1
+kind: ValidatingAdmissionPolicyBinding
+metadata:
+  name: "replicalimit-binding-nontest"
+spec:
+  policyName: "replicalimit-policy.example.com"
+  paramRef:
+    name: "replica-limit-clusterwide.example.com"
+  matchResources:
+    namespaceSelector:
+      matchExpressions:
+      - key: environment
+        operator: NotIn
+        values:
+        - test
+```
+
+<!--
+And have a parameter resource like:
+-->
+并有一个参数资源，如下：
+
+```yaml
+apiVersion: rules.example.com/v1
+kind: ReplicaLimit
+metadata:
+  name: "replica-limit-clusterwide.example.com"
+maxReplicas: 100
+```
+
+<!--
+Bindings can have overlapping match criteria. The policy is evaluated for each matching binding.
+In the above example, the "nontest" policy binding could instead have been defined as a global policy:
+-->
+绑定可以包含相互重叠的匹配条件。策略会针对每个匹配的绑定进行计算。
+在上面的例子中，`nontest` 策略绑定可以被定义为一个全局策略：
+
+```yaml
+apiVersion: admissionregistration.k8s.io/v1alpha1
+kind: ValidatingAdmissionPolicyBinding
+metadata:
+  name: "replicalimit-binding-global"
+spec:
+  policyName: "replicalimit-policy.example.com"
+  params: "replica-limit-clusterwide.example.com"
+  matchResources:
+    namespaceSelector:
+      matchExpressions:
+      - key: environment
+        operator: Exists
+```
+
+<!--
+The params object representing a parameter resource will not be set if a parameter resource has
+not been bound, so for policies requiring a parameter resource, it can be useful to add a check to
+ensure one has been bound.
+
+For the use cases require parameter configuration, we recommend to add a param check in
+`spec.validations[0].expression`:
+-->
+如果参数资源尚未被绑定，代表参数资源的 params 对象将不会被设置，
+所以对于需要参数资源的策略，添加一个检查来确保参数资源被绑定，这会很有用。
+
+对于需要参数配置的场景，我们建议在 `spec.validations[0].expression` 中添加一个参数检查：
+
+```
+- expression: "params != null"
+  message: "params missing but required to bind to this policy"
+```
+
+<!--
+It can be convenient to be able to have optional parameters as part of a parameter resource, and
+only validate them if present. CEL provides `has()`, which checks if the key passed to it exists.
+CEL also implements Boolean short-circuiting. If the first half of a logical OR evaluates to true,
+it won’t evaluate the other half (since the result of the entire OR will be true regardless).
+
+Combining the two, we can provide a way to validate optional parameters:
+-->
+将可选参数作为参数资源的一部分，并且只在参数存在时执行检查操作，这样做会比较方便。
+CEL 提供了 `has()` 方法，它检查传递给它的键是否存在。CEL 还实现了布尔短路逻辑。
+如果逻辑 OR 的前半部分计算为 true，则不会计算另一半（因为无论如何整个 OR 的结果都为真）。
+
+结合这两者，我们可以提供一种验证可选参数的方法：
+
+`!has(params.optionalNumber) || (params.optionalNumber >= 5 && params.optionalNumber <= 10)`
+
+<!--
+Here, we first check that the optional parameter is present with `!has(params.optionalNumber)`.
+- If `optionalNumber` hasn’t been defined, then the expression short-circuits since
+  `!has(params.optionalNumber)` will evaluate to true.
+- If `optionalNumber` has been defined, then the latter half of the CEL expression will be
+  evaluated, and optionalNumber will be checked to ensure that it contains a value between 5 and
+  10 inclusive.
+-->
+在这里，我们首先用 `!has(params.optionalNumber)` 检查可选参数是否存在。
+
+- 如果 `optionalNumber` 没有被定义，那么表达式就会短路，因为 `!has(params.optionalNumber)` 的计算结果为 true。
+- 如果 `optionalNumber` 被定义了，那么将计算 CEL 表达式的后半部分，
+  并且 `optionalNumber` 将被检查以确保它包含一个 5 到 10 之间的值（含 5 到 10）。
+
+<!--
+#### Authorization Check
+
+We introduced the authorization check for parameter resources.
+User is expected to have `read` access to the resources referenced by `paramKind` in
+`ValidatingAdmissionPolicy` and `paramRef` in `ValidatingAdmissionPolicyBinding`.
+
+Note that if a resource in `paramKind` fails resolving via the restmapper, `read` access to all
+resources of groups is required.
+-->
+#### 鉴权检查
+
+我们为参数资源引入了鉴权检查。
+用户应该对 `ValidatingAdmissionPolicy` 中的 `paramKind`
+和 `ValidatingAdmissionPolicyBinding` 中的 `paramRef` 所引用的资源有 `read` 权限。
+
+请注意，如果 `paramKind` 中的资源没能通过 restmapper 解析，则用户需要拥有对组的所有资源的
+`read` 访问权限。
+
+<!--
+### Failure Policy
+
+`failurePolicy` defines how mis-configurations and CEL expressions evaluating to error from the
+admission policy are handled. Allowed values are `Ignore` or `Fail`.
+
+- `Ignore` means that an error calling the ValidatingAdmissionPolicy is ignored and the API
+  request is allowed to continue.
+- `Fail` means that an error calling the ValidatingAdmissionPolicy causes the admission to fail
+  and the API request to be rejected.
+
+Note that the `failurePolicy` is defined inside `ValidatingAdmissionPolicy`:
+-->
+### 失效策略
+
+`failurePolicy` 定义了如何处理错误配置和准入策略的 CEL 表达式取值为 error 的情况。
+
+允许的值是 `Ignore` 或 `Fail`。
+
+- `Ignore` 意味着调用 ValidatingAdmissionPolicy 的错误被忽略，允许 API 请求继续。
+- `Fail` 意味着调用 ValidatingAdmissionPolicy 的错误导致准入失败并拒绝 API 请求。
+
+请注意，`failurePolicy` 是在 `ValidatingAdmissionPolicy` 中定义的：
+
+```yaml
+apiVersion: admissionregistration.k8s.io/v1alpha1
+kind: ValidatingAdmissionPolicy
+spec:
+...
+failurePolicy: Ignore # 默认值是 "Fail"
+validations:
+- expression: "object.spec.xyz == params.x"
+```
+
+<!--
+### Validation Expression
+
+`spec.validations[i].expression` represents the expression which will be evaluated by CEL.
+To learn more, see the [CEL language specification](https://github.com/google/cel-spec)
+CEL expressions have access to the contents of the Admission request/response, organized into CEL
+variables as well as some other useful variables:
+
+- 'object' - The object from the incoming request. The value is null for DELETE requests.
+- 'oldObject' - The existing object. The value is null for CREATE requests.
+- 'request' - Attributes of the [admission request](/docs/reference/config-api/apiserver-admission.v1/#admission-k8s-io-v1-AdmissionRequest).
+- 'params' - Parameter resource referred to by the policy binding being evaluated. The value is
+  null if `ParamKind` is unset.
+-->
+### 检查表达式
+
+`spec.validations[i].expression` 代表将使用 CEL 来计算表达式。
+要了解更多信息，请参阅 [CEL 语言规范](https://github.com/google/cel-spec)。
+CEL 表达式可以访问按 CEL 变量来组织的 Admission 请求/响应的内容，以及其他一些有用的变量 :
+
+- 'object' - 来自传入请求的对象。对于 DELETE 请求，该值为 null。
+- 'oldObject' - 现有对象。对于 CREATE 请求，该值为 null。
+- 'request' - [准入请求](/zh-cn/docs/reference/config-api/apiserver-admission.v1/#admission-k8s-io-v1-AdmissionRequest)的属性。
+- 'params' - 被计算的策略绑定引用的参数资源。如果未设置 `paramKind`，该值为 null。
+
+<!--
+The `apiVersion`, `kind`, `metadata.name` and `metadata.generateName` are always accessible from
+the root of the object. No other metadata properties are accessible.
+
+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:
+-->
+总是可以从对象的根访问的属性有 `apiVersion`、`kind`、`metadata.name` 和 `metadata.generateName`。
+其他元数据属性不能访问。
+
+只有符合 `[a-zA-Z_.-/][a-zA-Z0-9_.-/]*` 形式的属性名称是可访问的。
+可访问的属性名称在表达式中被访问时，根据以下规则进行转义：
+
+| 转义序列                | 属性名称等效            |
+| ----------------------- | -----------------------|
+| `__underscores__`       | `__`                  |
+| `__dot__`               | `.`                   |
+| `__dash__`              | `-`                   |
+| `__slash__`             | `/`                   |
+| `__{keyword}__`         | [CEL 保留关键字](https://github.com/google/cel-spec/blob/v0.6.0/doc/langdef.md#syntax)       |
+
+{{< note >}}
+<!--
+A **CEL reserved** keyword only needs to be escaped if the token is an exact match
+for the reserved keyword.
+For example, `int` in the word “sprint” would not be escaped.
+-->
+**CEL 保留**关键字仅在字符串与保留关键字完全匹配时才需要转义。
+例如，单词 “sprint” 中的 `int` 不需要被转义。
+{{< /note >}}
+
+<!--
+Examples on escaping:
+-->
+转义示例：
+
+| 属性名      | 具有转义属性名称的规则            |
+| ----------- | --------------------------------- |
+| 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 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.
+-->
+列表类型为 "set" 或 "map" 的数组上的等价关系比较会忽略元素顺序，即 [1, 2] == [2, 1]。
+使用 x-kubernetes-list-type 连接数组时使用列表类型的语义：
+
+- 'set': `X + Y` 执行并集，其中 `X` 中所有元素的数组位置被保留，`Y` 中不相交的元素被追加，保留其元素的偏序关系。
+- 'map'：`X + Y` 执行合并，保留 `X` 中所有键的数组位置，但是当 `X` 和 `Y` 的键集相交时，其值被 `Y` 的值覆盖。
+  `Y` 中键值不相交的元素被追加，保留其元素之间的偏序关系。
+
+<!--
+#### Validation expression examples
+-->
+#### 检查表达式示例
+
+| 表达式                                                                                        | 目的                                                                     |
+| --------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
+| `object.minReplicas <= object.replicas && object.replicas <= object.maxReplicas`              | 检查定义副本的三个字段是否大小关系正确                                   |
+| `'Available' in object.stateCounts`                                                           | 检查映射中是否存在键为 `Available` 的条目                                |
+| `(size(object.list1) == 0) != (size(object.list2) == 0)`                                      | 检查两个列表是否有且只有一个非空                                         |
+| <code>!('MY_KEY' in object.map1) &#124;&#124; object['MY_KEY'].matches('^[a-zA-Z]\*$')</code> | 检查映射中存在特定的键时其取值符合某规则                                 |
+| `object.envars.filter(e, e.name == 'MY_ENV').all(e, e.value.matches('^[a-zA-Z]*$')`           | 验证 listMap 中所有键名为 "MY_ENV" 的条目的 “value” 字段，确保其符合规则 |
+| `has(object.expired) && object.created + object.ttl < object.expired`                         | 检查 expired 日期在 create 日期加上 ttl 时长之后                         |
+| `object.health.startsWith('ok')`                                                              | 检查 health 字符串字段的取值有 “ok” 前缀                                 |
+| `object.widgets.exists(w, w.key == 'x' && w.foo < 10)`                                        | 对于 listMap 中键为 “x” 的条目，检查该条目的 "foo" 属性的值是否小于 10   |
+| `type(object) == string ? object == '100%' : object == 1000`                                  | 对于 int-or-string 字段，分别处理类型为 int 或 string 的情况             |
+| `object.metadata.name.startsWith(object.prefix)`                                              | 检查对象名称是否以另一个字段值为前缀                                     |
+| `object.set1.all(e, !(e in object.set2))`                                                     | 检查两个 listSet 是否不相交                                              |
+| `size(object.names) == size(object.details) && object.names.all(n, n in object.details)`      | 检查映射 “details” 所有的键和 listSet “names” 中的条目是否一致           |
+| `size(object.clusters.filter(c, c.name == object.primary)) == 1`                              | 检查 “primary” 字段的值在 listMap “clusters” 中只出现一次                |
+
+<!--
+Read [Supported evaluation on CEL](https://github.com/google/cel-spec/blob/v0.6.0/doc/langdef.md#evaluation)
+for more information about CEL rules.
+-->
+了解关于 CEL 规则的更多信息, 请阅读
+[CEL 支持的求值表达式](https://github.com/google/cel-spec/blob/v0.6.0/doc/langdef.md#evaluation)。
+
+<!--
+`spec.validation[i].reason` represents a machine-readable description of why this validation failed.
+If this is the first validation in the list to fail, this reason, as well as the corresponding
+HTTP response code, are used in the HTTP response to the client.
+The currently supported reasons are: `Unauthorized`, `Forbidden`, `Invalid`, `RequestEntityTooLarge`.
+If not set, `StatusReasonInvalid` is used in the response to the client.
+-->
+`spec.validation[i].reason` 表示一个机器可读的描述，说明为什么这次检查失败。
+如果这是列表中第一个失败的检查，其原因以及相应的 HTTP 响应代码会被用在给客户端的 HTTP 响应中。
+目前支持的原因有：`Unauthorized`、`Forbidden`、`Invalid`、`RequestEntityTooLarge`。
+如果未设置，将在对客户端的响应中使用 `StatusReasonInvalid`。

From 4bb17a912cbb210c0044e92a41fdbdd50e875480 Mon Sep 17 00:00:00 2001
From: Arhell <arhell333@gmail.com>
Date: Sun, 9 Apr 2023 01:05:52 +0300
Subject: [PATCH 139/272] [fr] Update branch name in ingress-nginx github link

---
 content/fr/docs/concepts/services-networking/ingress.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/fr/docs/concepts/services-networking/ingress.md b/content/fr/docs/concepts/services-networking/ingress.md
index d8b489aa51b..f7a1f0c2404 100644
--- a/content/fr/docs/concepts/services-networking/ingress.md
+++ b/content/fr/docs/concepts/services-networking/ingress.md
@@ -94,7 +94,7 @@ spec:
 Comme pour toutes les autres ressources Kubernetes, un Ingress (une entrée) a besoin des champs `apiVersion`, `kind` et `metadata`.
  Pour des informations générales sur l'utilisation des fichiers de configuration, voir [déployer des applications](/docs/tasks/run-application/run-stateless-application-deployment/), [configurer des conteneurs](/docs/tasks/configure-pod-container/configure-pod-configmap/), [gestion des ressources](/docs/concepts/cluster-administration/manage-deployment/).
  Ingress utilise fréquemment des annotations pour configurer certaines options en fonction du contrôleur Ingress, dont un exemple
- est l'annotation [rewrite-target](https://github.com/kubernetes/ingress-nginx/blob/master/docs/examples/rewrite/README.md).
+ est l'annotation [rewrite-target](https://github.com/kubernetes/ingress-nginx/blob/main/docs/examples/rewrite/README.md).
  Différents [Ingress controller](/docs/concepts/services-networking/ingress-controllers) prennent en charge différentes annotations. Consultez la documentation du contrôleur Ingress de votre choix pour savoir quelles annotations sont prises en charge.
 
 La [spécification de la ressource Ingress](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status) dispose de toutes les informations nécessaires pour configurer un loadbalancer ou un serveur proxy. Plus important encore, il

From 5ba37294055d985a3f617362e0b9a737eb4d6756 Mon Sep 17 00:00:00 2001
From: Khush Patibandha <104303438+KhushPatibandha@users.noreply.github.com>
Date: Sun, 9 Apr 2023 04:49:14 +0530
Subject: [PATCH 140/272] Explain env vs envFrom for page Define Environment
 Variables for a Container (#40055)

* 'Define Environment Variables for a Container' does not explain env vs envFrom #39873

* suggested review changes done.

* tengqm suggested changes done.
---
 .../define-environment-variable-container.md     | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/content/en/docs/tasks/inject-data-application/define-environment-variable-container.md b/content/en/docs/tasks/inject-data-application/define-environment-variable-container.md
index 50cc57f1e5d..ba226f8f9f3 100644
--- a/content/en/docs/tasks/inject-data-application/define-environment-variable-container.md
+++ b/content/en/docs/tasks/inject-data-application/define-environment-variable-container.md
@@ -21,6 +21,22 @@ When you create a Pod, you can set environment variables for the containers
 that run in the Pod. To set environment variables, include the `env` or
 `envFrom` field in the configuration file.
 
+The `env` and `envFrom` fields have different effects.
+
+`env`
+: allows you to set environment variables for a container, specifying a value directly for each variable that you name.
+
+`envFrom`
+: allows you to set environment variables for a container by referencing either a ConfigMap or a Secret.
+ When you use `envFrom`, all the key-value pairs in the referenced ConfigMap or Secret
+ are set as environment variables for the container.
+ You can also specify a common prefix string.
+
+You can read more about [ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/#configure-all-key-value-pairs-in-a-configmap-as-container-environment-variables)
+and [Secret](/docs/tasks/inject-data-application/distribute-credentials-secure/#configure-all-key-value-pairs-in-a-secret-as-container-environment-variables).
+
+This page explains how to use `env`.
+
 In this exercise, you create a Pod that runs one container. The configuration
 file for the Pod defines an environment variable with name `DEMO_GREETING` and
 value `"Hello from the environment"`. Here is the configuration manifest for the

From 76729f07024faeee70e2bc97f949af5bc1d1249c Mon Sep 17 00:00:00 2001
From: "xin.li" <xin.li@daocloud.io>
Date: Sun, 9 Apr 2023 11:55:25 +0800
Subject: [PATCH 141/272] [zh-cn] sync statefulset conventions.md

Signed-off-by: xin.li <xin.li@daocloud.io>
---
 content/zh-cn/docs/reference/glossary/statefulset.md | 6 ++----
 content/zh-cn/docs/reference/kubectl/conventions.md  | 8 ++++++--
 2 files changed, 8 insertions(+), 6 deletions(-)

diff --git a/content/zh-cn/docs/reference/glossary/statefulset.md b/content/zh-cn/docs/reference/glossary/statefulset.md
index e94318e78ae..de43a53988c 100644
--- a/content/zh-cn/docs/reference/glossary/statefulset.md
+++ b/content/zh-cn/docs/reference/glossary/statefulset.md
@@ -14,13 +14,12 @@ tags:
 ---
 
 <!--
----
 title: StatefulSet
 id: statefulset
 date: 2018-04-12
 full_link: /docs/concepts/workloads/controllers/statefulset/
 short_description: >
-  Manages deployment and scaling of a set of Pods, with durable storage and persistent identifiers for each Pod.
+  A StatefulSet manages deployment and scaling of a set of Pods, with durable storage and persistent identifiers for each Pod.
 
 aka: 
 tags:
@@ -28,7 +27,6 @@ tags:
 - core-object
 - workload
 - storage
----
 -->
 
 <!--
@@ -39,7 +37,7 @@ StatefulSet 用来管理某 {{< glossary_tooltip text="Pod" term_id="pod" >}} 
 <!--more--> 
 
 <!--
-Like a {{< glossary_tooltip term_id="deployment" >}}, a StatefulSet manages Pods that are based on an identical container spec. Unlike a Deployment, a StatefulSet maintains a sticky identity for each of their Pods. These pods are created from the same spec, but are not interchangeable&#58; each has a persistent identifier that it maintains across any rescheduling.
+Like a {{< glossary_tooltip term_id="deployment" >}}, a StatefulSet manages Pods that are based on an identical container spec. Unlike a Deployment, a StatefulSet maintains a sticky identity for each of its Pods. These pods are created from the same spec, but are not interchangeable&#58; each has a persistent identifier that it maintains across any rescheduling.
 -->
 
 和 {{< glossary_tooltip text="Deployment" term_id="deployment" >}} 类似，
diff --git a/content/zh-cn/docs/reference/kubectl/conventions.md b/content/zh-cn/docs/reference/kubectl/conventions.md
index 2f6cc0f1908..1f67fdb2823 100644
--- a/content/zh-cn/docs/reference/kubectl/conventions.md
+++ b/content/zh-cn/docs/reference/kubectl/conventions.md
@@ -46,16 +46,20 @@ For a stable output in a script:
 ## 子资源    {#subresources}
 
 <!--
-* You can use the `--subresource` alpha flag for kubectl commands like `get`, `patch`,
+* You can use the `--subresource` beta flag for kubectl commands like `get`, `patch`,
 `edit` and `replace` to fetch and update subresources for all resources that
 support them. Currently, only the `status` and `scale` subresources are supported.
+  * For `kubectl edit`, the `scale` subresource is not supported. If you use  `--subresource` with
+    `kubectl edit` and specify `scale` as the subresource, the command will error out.
 * The API contract against a subresource is identical to a full resource. While updating the
 `status` subresource to a new value, keep in mind that the subresource could be potentially
 reconciled by a controller to a different value.
 -->
 
-* 你可以将 `--subresource` alpha 标志用于 kubectl 命令，例如 `get`、`patch`、`edit` 和 `replace`
+* 你可以将 `--subresource` Beta 标志用于 kubectl 命令，例如 `get`、`patch`、`edit` 和 `replace`
   来获取和更新所有支持子资源的资源的子资源。目前，仅支持 `status` 和 `scale` 子资源。
+  * 对于 `kubectl edit`，不支持 `scale` 子资源。如果将 `--subresource` 与 `kubectl edit` 一起使用，
+    并指定 `scale` 作为子资源，则命令将会报错。
 * 针对子资源的 API 协定与完整资源相同。在更新 `status` 子资源为一个新值时，请记住，
   子资源可能是潜在的由控制器调和为不同的值。
 

From 9ad93738bbf846a36b3a91bb5193c6375e179269 Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Sun, 9 Apr 2023 21:33:51 +0800
Subject: [PATCH 142/272] sync konnectivity-agent.yaml

sync konnectivity-agent.yaml
---
 .../zh-cn/examples/admin/konnectivity/konnectivity-agent.yaml   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/zh-cn/examples/admin/konnectivity/konnectivity-agent.yaml b/content/zh-cn/examples/admin/konnectivity/konnectivity-agent.yaml
index 2d34c2d69c8..0f7477e8d68 100644
--- a/content/zh-cn/examples/admin/konnectivity/konnectivity-agent.yaml
+++ b/content/zh-cn/examples/admin/konnectivity/konnectivity-agent.yaml
@@ -22,7 +22,7 @@ spec:
         - key: "CriticalAddonsOnly"
           operator: "Exists"
       containers:
-        - image: us.gcr.io/k8s-artifacts-prod/kas-network-proxy/proxy-agent:v0.0.16
+        - image: us.gcr.io/k8s-artifacts-prod/kas-network-proxy/proxy-agent:v0.0.37
           name: konnectivity-agent
           command: ["/proxy-agent"]
           args: [

From 8124e23890aa82b6dd8685c09f3ca04e2558f7ef Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Sun, 9 Apr 2023 21:37:03 +0800
Subject: [PATCH 143/272] sync konnectivity-server.yaml

sync konnectivity-server.yaml
---
 .../zh-cn/examples/admin/konnectivity/konnectivity-server.yaml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/content/zh-cn/examples/admin/konnectivity/konnectivity-server.yaml b/content/zh-cn/examples/admin/konnectivity/konnectivity-server.yaml
index df5ca13d410..9c24a63dc59 100644
--- a/content/zh-cn/examples/admin/konnectivity/konnectivity-server.yaml
+++ b/content/zh-cn/examples/admin/konnectivity/konnectivity-server.yaml
@@ -8,12 +8,13 @@ spec:
   hostNetwork: true
   containers:
   - name: konnectivity-server-container
-    image: registry.k8s.io/kas-network-proxy/proxy-server:v0.0.32
+    image: registry.k8s.io/kas-network-proxy/proxy-server:v0.0.37
     command: ["/proxy-server"]
     args: [
             "--logtostderr=true",
             # 下一行需与 egressSelectorConfiguration 中设置的值一致。
             "--uds-name=/etc/kubernetes/konnectivity-server/konnectivity-server.socket",
+            "--delete-existing-uds-file",
             # 下面两行假定 Konnectivity 服务器被部署在与 apiserver 相同的机器上，
             # 并且该 API 服务器的证书和密钥位于指定的位置。
             "--cluster-cert=/etc/kubernetes/pki/apiserver.crt",

From 8377a675cd4beef6da89eba9829a05c14b19a60f Mon Sep 17 00:00:00 2001
From: Tim Bannister <tim@scalefactory.com>
Date: Thu, 16 Mar 2023 13:00:31 -0700
Subject: [PATCH 144/272] ClusterTrustBundles: Add section to certificates page

Document the API types as they exist today, plus a hint of the future
integrations that will be available.

Co-Authored-By: Taahir Ahmed <taahm@google.com>
---
 .../certificate-signing-requests.md           | 89 +++++++++++++++++++
 1 file changed, 89 insertions(+)

diff --git a/content/en/docs/reference/access-authn-authz/certificate-signing-requests.md b/content/en/docs/reference/access-authn-authz/certificate-signing-requests.md
index aa95223bb05..ed61a6e3c51 100644
--- a/content/en/docs/reference/access-authn-authz/certificate-signing-requests.md
+++ b/content/en/docs/reference/access-authn-authz/certificate-signing-requests.md
@@ -459,6 +459,95 @@ status:
   certificate: "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JS..."
 ```
 
+## ClusterTrustBundles (Alpha Feature) {#ctb}
+
+{{< feature-state for_k8s_version="v1.27" state="alpha" >}}
+
+{{< note >}}
+Gated by the `ClusterTrustBundles` feature gate.
+{{< /note >}}
+
+ClusterTrustBundles are a cluster-scoped object for distributing X.509 trust
+anchors (root certificates) to workloads within the cluster.  They're designed
+to work well with the existing signer concept.
+
+Future Kubernetes releases will build on them with integrations like the ability
+to project their contents into the pod filesystem.
+
+ClusterTrustBundles can be used in two modes: signer-linked and signer-unlinked.
+
+### Common properties and validation {#ctb-common}
+
+All ClusterTrustBundle objects have strong validation on the contents of their
+`trustBundle` field.  It must contain one or more X.509 certificates,
+DER-serialized, each wrapped in a PEM `CERTIFICATE` block.  The certificates
+must parse as valid X.509 certificates.
+
+Esoteric PEM features like inter-block data and intra-block headers are either
+rejected during object validation, or filtered by consumers of the object
+(primarily Kubelet).  Additionally, consumers will reorder the certificates in
+the bundle with their own arbitrary but stable ordering.
+
+ClusterTrustBundle objects should be considered world-readable within the
+cluster.  All serviceaccounts have a default RBAC grant to get, list, and watch
+all ClusterTrustBundle objects.
+
+### Signer-linked ClusterTrustBundles {#ctb-signer-linked}
+
+Signer-linked ClusterTrustBundles are associated with a signer name, like this:
+
+```yaml
+apiVersion: certificates.k8s.io/v1alpha1
+kind: ClusterTrustBundle
+metadata:
+  name: example.com:mysigner:foo
+spec:
+  signerName: example.com/mysigner
+  trustBundle: "<... PEM data ...>"
+```
+
+These ClusterTrustBundles are intended to be maintained by a signer-specific
+controller in the cluster, so they have several security features:
+
+* To create or update a signer-linked ClusterTrustBundle, you must have the
+  `attest` verb on the signer (verbs: `attest`, group: `certificates.k8s.io`,
+  resource: `signers`, resourceName: `<signerNameDomain>/<signerNamePath>` or
+  `<signerNameDomain>/*`).
+* Signer-linked ClusterTrustBundles must be named with a prefix derived from
+  their `spec.signerName` field.  Slashes (`/`) are replaced with colons (`:`),
+  and a final colon is appended.  This is followed by an arbitary name.  For
+  example, the signer `example.com/mysigner` becomes
+  `example.com:mysigner:<arbitrary-name>`.
+
+Signer-linked ClusterTrustBundles will be consumed in workloads by a combination
+of field selector on the signer name and a label selector.  If this query
+matches multiple ClusterTrustBundle objects, their contents will be merged,
+deduplicated, and sorted before being provided to the workload.
+
+### Signer-unlinked ClusterTrustBundles {#ctb-signer-unlinked}
+
+Signer-unlinked ClusterTrustBundles have an empty `spec.signerName` field, like this:
+
+```yaml
+apiVersion: certificates.k8s.io/v1alpha1
+kind: ClusterTrustBundle
+metadata:
+  name: foo
+spec:
+  signerName: ""
+  trustBundle: "<... PEM data ...>"
+```
+
+They are primarily intended for cluster configuration use cases.  Each
+signer-unlinked ClusterTrustBundle is an independent object, in contrast to the
+customary grouping behavior of signer-linked ClusterTrustBundles.
+
+Signer-unlinked ClusterTrustBundles have no `attest` verb requirement.  Instead,
+control access to them using the standard RBAC verbs.
+
+To distinguish them from signer-linked ClusterTrustBundles, the names of
+signer-unlinked ClusterTrustBundles must not contain a colon (`:`).
+
 ## {{% heading "whatsnext" %}}
 
 * Read [Manage TLS Certificates in a Cluster](/docs/tasks/tls/managing-tls-in-a-cluster/)

From e95deae997ac01540211e0666e2b453a3829f3b2 Mon Sep 17 00:00:00 2001
From: Tim Bannister <tim@scalefactory.com>
Date: Sun, 9 Apr 2023 18:17:50 +0100
Subject: [PATCH 145/272] Update CSR page to encompass CSRs and trust bundles

Rather than mention trust bundles as a subtopic of certificate signing
requests, reshape the page so that:
- it's clear that CSRs are stable but ClusterTrustBundles are alpha
- the task for issuing a certificate to a user stands separately from
  the concepts explained elsewhere in the page
- it's clear that signers are relevant to both CSRs and
  ClusterTrustBundles
---
 .../certificate-signing-requests.md           | 517 ++++++++++--------
 1 file changed, 278 insertions(+), 239 deletions(-)

diff --git a/content/en/docs/reference/access-authn-authz/certificate-signing-requests.md b/content/en/docs/reference/access-authn-authz/certificate-signing-requests.md
index ed61a6e3c51..4ce299e5fb5 100644
--- a/content/en/docs/reference/access-authn-authz/certificate-signing-requests.md
+++ b/content/en/docs/reference/access-authn-authz/certificate-signing-requests.md
@@ -4,27 +4,33 @@ reviewers:
 - mikedanese
 - munnerz
 - enj
-title: Certificate Signing Requests
+title: Certificates and Certificate Signing Requests
 content_type: concept
 weight: 25
 ---
 
 <!-- overview -->
 
-{{< feature-state for_k8s_version="v1.19" state="stable" >}}
-
-The Certificates API enables automation of
+Kubernetes certificate and trust bundle APIs enable automation of
 [X.509](https://www.itu.int/rec/T-REC-X.509) credential provisioning by providing
 a programmatic interface for clients of the Kubernetes API to request and obtain
 X.509 {{< glossary_tooltip term_id="certificate" text="certificates" >}} from a Certificate Authority (CA).
 
+There is also experimental (alpha) support for distributing [trust bundles](#cluster-trust-bundles).
+
+<!-- body -->
+
+## Certificate signing requests
+
+{{< feature-state for_k8s_version="v1.19" state="stable" >}}
+
+
 A CertificateSigningRequest (CSR) resource is used to request that a certificate be signed
 by a denoted signer, after which the request may be approved or denied before
 finally being signed.
 
-<!-- body -->
 
-## Request signing process
+### Request signing process
 
 The CertificateSigningRequest resource type allows a client to ask for an X.509 certificate
 be issued, based on a signing request.
@@ -64,12 +70,46 @@ state for some duration:
 * Pending requests: automatically deleted after 24 hours
 * All requests: automatically deleted after the issued certificate has expired
 
+### Certificate signing authorization {#authorization}
+
+To allow creating a CertificateSigningRequest and retrieving any CertificateSigningRequest:
+
+* Verbs: `create`, `get`, `list`, `watch`, group: `certificates.k8s.io`, resource: `certificatesigningrequests`
+
+For example:
+
+{{< codenew file="access/certificate-signing-request/clusterrole-create.yaml" >}}
+
+To allow approving a CertificateSigningRequest:
+
+* Verbs: `get`, `list`, `watch`, group: `certificates.k8s.io`, resource: `certificatesigningrequests`
+* Verbs: `update`, group: `certificates.k8s.io`, resource: `certificatesigningrequests/approval`
+* Verbs: `approve`, group: `certificates.k8s.io`, resource: `signers`, resourceName: `<signerNameDomain>/<signerNamePath>` or `<signerNameDomain>/*`
+
+For example:
+
+{{< codenew file="access/certificate-signing-request/clusterrole-approve.yaml" >}}
+
+To allow signing a CertificateSigningRequest:
+
+* Verbs: `get`, `list`, `watch`, group: `certificates.k8s.io`, resource: `certificatesigningrequests`
+* Verbs: `update`, group: `certificates.k8s.io`, resource: `certificatesigningrequests/status`
+* Verbs: `sign`, group: `certificates.k8s.io`, resource: `signers`, resourceName: `<signerNameDomain>/<signerNamePath>` or `<signerNameDomain>/*`
+
+{{< codenew file="access/certificate-signing-request/clusterrole-sign.yaml" >}}
+
+
 ## Signers
 
-Custom signerNames can also be specified. All signers should provide information about how they work so that clients can predict what will happen to their CSRs.
+Signers abstractly represent the entity or entities that might sign, or have
+signed, a security certificate.
+
+Any signer that is made available for outside a particular cluster should provide information
+about how the signer works, so that consumers can understand what that means for CertifcateSigningRequests
+and (if enabled) [ClusterTrustBundles](#cluster-trust-bundles).  
 This includes:
 
-1. **Trust distribution**: how trust (CA bundles) are distributed.
+1. **Trust distribution**: how trust anchors (CA certificates or certificate bundles) are distributed.
 1. **Permitted subjects**: any restrictions on and behavior when a disallowed subject is requested.
 1. **Permitted x509 extensions**: including IP subjectAltNames, DNS subjectAltNames, Email subjectAltNames, URI subjectAltNames etc, and behavior when a disallowed extension is requested.
 1. **Permitted key usages / extended key usages**: any restrictions on and behavior when usages different than the signer-determined usages are specified in the CSR.
@@ -77,13 +117,17 @@ This includes:
    and the behavior when the signer-determined expiration is different from the CSR `spec.expirationSeconds` field.
 1. **CA bit allowed/disallowed**: and behavior if a CSR contains a request a for a CA certificate when the signer does not permit it.
 
-Commonly, the `status.certificate` field contains a single PEM-encoded X.509
-certificate once the CSR is approved and the certificate is issued. Some
-signers store multiple certificates into the `status.certificate` field. In
+Commonly, the `status.certificate` field of a CertificateSigningRequest contains a
+single PEM-encoded X.509 certificate once the CSR is approved and the certificate is issued.
+Some signers store multiple certificates into the `status.certificate` field. In
 that case, the documentation for the signer should specify the meaning of
 additional certificates; for example, this might be the certificate plus
 intermediates to be presented during TLS handshakes.
 
+If you want to make the _trust anchor_ (root certificate) available, this should be done
+separately from a CertificateSigningRequest and its `status.certificate` field. For example,
+you could use a ClusterTrustBundle.
+
 The PKCS#10 signing request format does not have a standard mechanism to specify a
 certificate expiration or lifetime. The expiration or lifetime therefore has to be set
 through the `spec.expirationSeconds` field of the CSR object. The built-in signers
@@ -153,9 +197,8 @@ Kubernetes provides built-in signers that each have a well-known `signerName`:
       of the `--cluster-signing-duration` option or, if specified, the `spec.expirationSeconds` field of the CSR object.
    1. CA bit allowed/disallowed - not allowed.
 
-{{< note >}}
-Failures for all of these are only reported in kube-controller-manager logs.
-{{< /note >}}
+The kube-controller-manager implements [control plane signing](#signer-control-plane) for each of the built in
+signers. Failures for all of these are only reported in kube-controller-manager logs.
 
 {{< note >}}
 The `spec.expirationSeconds` field was added in Kubernetes v1.22.  Earlier versions of Kubernetes do not honor this field.
@@ -168,156 +211,89 @@ kube-apiserver, but this is not a standard.
 None of these usages are related to ServiceAccount token secrets `.data[ca.crt]` in any way.  That CA bundle is only
 guaranteed to verify a connection to the API server using the default service (`kubernetes.default.svc`).
 
-## Authorization
+### Custom signers
 
-To allow creating a CertificateSigningRequest and retrieving any CertificateSigningRequest:
+You can also introduce your own custom signer, which should have a similar prefixed name but using your
+own domain name. For example, if you represent an open source project that uses the domain `open-fictional.example`
+then you might use `issuer.open-fictional.example/service-mesh` as a signer name.
 
-* Verbs: `create`, `get`, `list`, `watch`, group: `certificates.k8s.io`, resource: `certificatesigningrequests`
+A custom signer uses the Kubernetes API to issue a certificate. See [API-based signers](#signer-api).
 
-For example:
+## Signing
 
-{{< codenew file="access/certificate-signing-request/clusterrole-create.yaml" >}}
+### Control plane signer {#signer-control-plane}
 
-To allow approving a CertificateSigningRequest:
+The Kubernetes control plane implements each of the
+[Kubernetes signers](/docs/reference/access-authn-authz/certificate-signing-requests/#kubernetes-signers),
+as part of the kube-controller-manager.
 
-* Verbs: `get`, `list`, `watch`, group: `certificates.k8s.io`, resource: `certificatesigningrequests`
-* Verbs: `update`, group: `certificates.k8s.io`, resource: `certificatesigningrequests/approval`
-* Verbs: `approve`, group: `certificates.k8s.io`, resource: `signers`, resourceName: `<signerNameDomain>/<signerNamePath>` or `<signerNameDomain>/*`
+{{< note >}}
+Prior to Kubernetes v1.18, the kube-controller-manager would sign any CSRs that
+were marked as approved.
+{{< /note >}}
 
-For example:
+{{< note >}}
+The `spec.expirationSeconds` field was added in Kubernetes v1.22.  Earlier versions of Kubernetes do not honor this field.
+Kubernetes API servers prior to v1.22 will silently drop this field when the object is created.
+{{< /note >}}
 
-{{< codenew file="access/certificate-signing-request/clusterrole-approve.yaml" >}}
+### API-based signers {#signer-api}
 
-To allow signing a CertificateSigningRequest:
+Users of the REST API can sign CSRs by submitting an UPDATE request to the `status`
+subresource of the CSR to be signed.
 
-* Verbs: `get`, `list`, `watch`, group: `certificates.k8s.io`, resource: `certificatesigningrequests`
-* Verbs: `update`, group: `certificates.k8s.io`, resource: `certificatesigningrequests/status`
-* Verbs: `sign`, group: `certificates.k8s.io`, resource: `signers`, resourceName: `<signerNameDomain>/<signerNamePath>` or `<signerNameDomain>/*`
+As part of this request, the `status.certificate` field should be set to contain the
+signed certificate. This field contains one or more PEM-encoded certificates.
 
-{{< codenew file="access/certificate-signing-request/clusterrole-sign.yaml" >}}
+All PEM blocks must have the "CERTIFICATE" label, contain no headers,
+and the encoded data must be a BER-encoded ASN.1 Certificate structure
+as described in [section 4 of RFC5280](https://tools.ietf.org/html/rfc5280#section-4.1).
 
-## Normal user
+Example certificate content:
 
-A few steps are required in order to get a normal user to be able to
-authenticate and invoke an API. First, this user must have a certificate issued
-by the Kubernetes cluster, and then present that certificate to the Kubernetes API.
-
-### Create private key
-
-The following scripts show how to generate PKI private key and CSR. It is
-important to set CN and O attribute of the CSR. CN is the name of the user and
-O is the group that this user will belong to. You can refer to
-[RBAC](/docs/reference/access-authn-authz/rbac/) for standard groups.
-
-```shell
-openssl genrsa -out myuser.key 2048
-openssl req -new -key myuser.key -out myuser.csr
+```
+-----BEGIN CERTIFICATE-----
+MIIDgjCCAmqgAwIBAgIUC1N1EJ4Qnsd322BhDPRwmg3b/oAwDQYJKoZIhvcNAQEL
+BQAwXDELMAkGA1UEBhMCeHgxCjAIBgNVBAgMAXgxCjAIBgNVBAcMAXgxCjAIBgNV
+BAoMAXgxCjAIBgNVBAsMAXgxCzAJBgNVBAMMAmNhMRAwDgYJKoZIhvcNAQkBFgF4
+MB4XDTIwMDcwNjIyMDcwMFoXDTI1MDcwNTIyMDcwMFowNzEVMBMGA1UEChMMc3lz
+dGVtOm5vZGVzMR4wHAYDVQQDExVzeXN0ZW06bm9kZToxMjcuMC4wLjEwggEiMA0G
+CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDne5X2eQ1JcLZkKvhzCR4Hxl9+ZmU3
++e1zfOywLdoQxrPi+o4hVsUH3q0y52BMa7u1yehHDRSaq9u62cmi5ekgXhXHzGmm
+kmW5n0itRECv3SFsSm2DSghRKf0mm6iTYHWDHzUXKdm9lPPWoSOxoR5oqOsm3JEh
+Q7Et13wrvTJqBMJo1GTwQuF+HYOku0NF/DLqbZIcpI08yQKyrBgYz2uO51/oNp8a
+sTCsV4OUfyHhx2BBLUo4g4SptHFySTBwlpRWBnSjZPOhmN74JcpTLB4J5f4iEeA7
+2QytZfADckG4wVkhH3C2EJUmRtFIBVirwDn39GXkSGlnvnMgF3uLZ6zNAgMBAAGj
+YTBfMA4GA1UdDwEB/wQEAwIFoDATBgNVHSUEDDAKBggrBgEFBQcDAjAMBgNVHRMB
+Af8EAjAAMB0GA1UdDgQWBBTREl2hW54lkQBDeVCcd2f2VSlB1DALBgNVHREEBDAC
+ggAwDQYJKoZIhvcNAQELBQADggEBABpZjuIKTq8pCaX8dMEGPWtAykgLsTcD2jYr
+L0/TCrqmuaaliUa42jQTt2OVsVP/L8ofFunj/KjpQU0bvKJPLMRKtmxbhXuQCQi1
+qCRkp8o93mHvEz3mTUN+D1cfQ2fpsBENLnpS0F4G/JyY2Vrh19/X8+mImMEK5eOy
+o0BMby7byUj98WmcUvNCiXbC6F45QTmkwEhMqWns0JZQY+/XeDhEcg+lJvz9Eyo2
+aGgPsye1o3DpyXnyfJWAWMhOz7cikS5X2adesbgI86PhEHBXPIJ1v13ZdfCExmdd
+M1fLPhLyR54fGaY+7/X8P9AZzPefAkwizeXwe9ii6/a08vWoiE4=
+-----END CERTIFICATE-----
 ```
 
-### Create CertificateSigningRequest
+Non-PEM content may appear before or after the CERTIFICATE PEM blocks and is unvalidated,
+to allow for explanatory text as described in [section 5.2 of RFC7468](https://www.rfc-editor.org/rfc/rfc7468#section-5.2).
 
-Create a CertificateSigningRequest and submit it to a Kubernetes Cluster via kubectl. Below is a script to generate the CertificateSigningRequest.
+When encoded in JSON or YAML, this field is base-64 encoded.
+A CertificateSigningRequest containing the example certificate above would look like this:
 
-```shell
-cat <<EOF | kubectl apply -f -
+```yaml
 apiVersion: certificates.k8s.io/v1
 kind: CertificateSigningRequest
-metadata:
-  name: myuser
-spec:
-  request: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURSBSRVFVRVNULS0tLS0KTUlJQ1ZqQ0NBVDRDQVFBd0VURVBNQTBHQTFVRUF3d0dZVzVuWld4aE1JSUJJakFOQmdrcWhraUc5dzBCQVFFRgpBQU9DQVE4QU1JSUJDZ0tDQVFFQTByczhJTHRHdTYxakx2dHhWTTJSVlRWMDNHWlJTWWw0dWluVWo4RElaWjBOCnR2MUZtRVFSd3VoaUZsOFEzcWl0Qm0wMUFSMkNJVXBGd2ZzSjZ4MXF3ckJzVkhZbGlBNVhwRVpZM3ExcGswSDQKM3Z3aGJlK1o2MVNrVHF5SVBYUUwrTWM5T1Nsbm0xb0R2N0NtSkZNMUlMRVI3QTVGZnZKOEdFRjJ6dHBoaUlFMwpub1dtdHNZb3JuT2wzc2lHQ2ZGZzR4Zmd4eW8ybmlneFNVekl1bXNnVm9PM2ttT0x1RVF6cXpkakJ3TFJXbWlECklmMXBMWnoyalVnald4UkhCM1gyWnVVV1d1T09PZnpXM01LaE8ybHEvZi9DdS8wYk83c0x0MCt3U2ZMSU91TFcKcW90blZtRmxMMytqTy82WDNDKzBERHk5aUtwbXJjVDBnWGZLemE1dHJRSURBUUFCb0FBd0RRWUpLb1pJaHZjTgpBUUVMQlFBRGdnRUJBR05WdmVIOGR4ZzNvK21VeVRkbmFjVmQ1N24zSkExdnZEU1JWREkyQTZ1eXN3ZFp1L1BVCkkwZXpZWFV0RVNnSk1IRmQycVVNMjNuNVJsSXJ3R0xuUXFISUh5VStWWHhsdnZsRnpNOVpEWllSTmU3QlJvYXgKQVlEdUI5STZXT3FYbkFvczFqRmxNUG5NbFpqdU5kSGxpT1BjTU1oNndLaTZzZFhpVStHYTJ2RUVLY01jSVUyRgpvU2djUWdMYTk0aEpacGk3ZnNMdm1OQUxoT045UHdNMGM1dVJVejV4T0dGMUtCbWRSeEgvbUNOS2JKYjFRQm1HCkkwYitEUEdaTktXTU0xMzhIQXdoV0tkNjVoVHdYOWl4V3ZHMkh4TG1WQzg0L1BHT0tWQW9FNkpsYWFHdTlQVmkKdjlOSjVaZlZrcXdCd0hKbzZXdk9xVlA3SVFjZmg3d0drWm89Ci0tLS0tRU5EIENFUlRJRklDQVRFIFJFUVVFU1QtLS0tLQo=
-  signerName: kubernetes.io/kube-apiserver-client
-  expirationSeconds: 86400  # one day
-  usages:
-  - client auth
-EOF
-```
-
-Some points to note:
-
-- `usages` has to be '`client auth`'
-- `expirationSeconds` could be made longer (i.e. `864000` for ten days) or shorter (i.e. `3600` for one hour)
-- `request` is the base64 encoded value of the CSR file content.
-  You can get the content using this command: 
-
-  ```shell
-  cat myuser.csr | base64 | tr -d "\n"
-  ```
-
-### Approve certificate signing request
-
-Use kubectl to create a CSR and approve it.
-
-Get the list of CSRs:
-
-```shell
-kubectl get csr
-```
-
-Approve the CSR:
-
-```shell
-kubectl certificate approve myuser
-```
-
-### Get the certificate
-
-Retrieve the certificate from the CSR:
-
-```shell
-kubectl get csr/myuser -o yaml
-```
-
-The certificate value is in Base64-encoded format under `status.certificate`.
-
-Export the issued certificate from the CertificateSigningRequest.
-
-```shell
-kubectl get csr myuser -o jsonpath='{.status.certificate}'| base64 -d > myuser.crt
-```
-
-### Create Role and RoleBinding
-
-With the certificate created it is time to define the Role and RoleBinding for
-this user to access Kubernetes cluster resources.
-
-This is a sample command to create a Role for this new user:
-
-```shell
-kubectl create role developer --verb=create --verb=get --verb=list --verb=update --verb=delete --resource=pods
-```
-
-This is a sample command to create a RoleBinding for this new user:
-
-```shell
-kubectl create rolebinding developer-binding-myuser --role=developer --user=myuser
-```
-
-### Add to kubeconfig
-
-The last step is to add this user into the kubeconfig file.
-
-First, you need to add new credentials:
-
-```shell
-kubectl config set-credentials myuser --client-key=myuser.key --client-certificate=myuser.crt --embed-certs=true
-
-```
-
-Then, you need to add the context:
-
-```shell
-kubectl config set-context myuser --cluster=kubernetes --user=myuser
-```
-
-To test it, change the context to `myuser`:
-
-```shell
-kubectl config use-context myuser
+...
+status:
+  certificate: "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JS..."
 ```
 
 ## Approval or rejection  {#approval-rejection}
 
+Before a [signer](#signers) issues a certificate based on a CertificateSigningRequest,
+the signer typically checks that the issuance for that CSR has been _approved_.
+
 ### Control plane automated approval {#approval-rejection-control-plane}
 
 The kube-controller-manager ships with a built-in approver for certificates with
@@ -389,112 +365,49 @@ code using TitleCase; this is a convention but you can set it to anything
 you like. If you want to add a note for human consumption, use the
 `status.conditions.message` field.
 
-## Signing
 
-### Control plane signer {#signer-control-plane}
-
-The Kubernetes control plane implements each of the
-[Kubernetes signers](/docs/reference/access-authn-authz/certificate-signing-requests/#kubernetes-signers),
-as part of the kube-controller-manager.
-
-{{< note >}}
-Prior to Kubernetes v1.18, the kube-controller-manager would sign any CSRs that
-were marked as approved.
-{{< /note >}}
-
-{{< note >}}
-The `spec.expirationSeconds` field was added in Kubernetes v1.22.  Earlier versions of Kubernetes do not honor this field.
-Kubernetes API servers prior to v1.22 will silently drop this field when the object is created.
-{{< /note >}}
-
-### API-based signers {#signer-api}
-
-Users of the REST API can sign CSRs by submitting an UPDATE request to the `status`
-subresource of the CSR to be signed.
-
-As part of this request, the `status.certificate` field should be set to contain the
-signed certificate. This field contains one or more PEM-encoded certificates.
-
-All PEM blocks must have the "CERTIFICATE" label, contain no headers,
-and the encoded data must be a BER-encoded ASN.1 Certificate structure
-as described in [section 4 of RFC5280](https://tools.ietf.org/html/rfc5280#section-4.1).
-
-Example certificate content:
-
-```
------BEGIN CERTIFICATE-----
-MIIDgjCCAmqgAwIBAgIUC1N1EJ4Qnsd322BhDPRwmg3b/oAwDQYJKoZIhvcNAQEL
-BQAwXDELMAkGA1UEBhMCeHgxCjAIBgNVBAgMAXgxCjAIBgNVBAcMAXgxCjAIBgNV
-BAoMAXgxCjAIBgNVBAsMAXgxCzAJBgNVBAMMAmNhMRAwDgYJKoZIhvcNAQkBFgF4
-MB4XDTIwMDcwNjIyMDcwMFoXDTI1MDcwNTIyMDcwMFowNzEVMBMGA1UEChMMc3lz
-dGVtOm5vZGVzMR4wHAYDVQQDExVzeXN0ZW06bm9kZToxMjcuMC4wLjEwggEiMA0G
-CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDne5X2eQ1JcLZkKvhzCR4Hxl9+ZmU3
-+e1zfOywLdoQxrPi+o4hVsUH3q0y52BMa7u1yehHDRSaq9u62cmi5ekgXhXHzGmm
-kmW5n0itRECv3SFsSm2DSghRKf0mm6iTYHWDHzUXKdm9lPPWoSOxoR5oqOsm3JEh
-Q7Et13wrvTJqBMJo1GTwQuF+HYOku0NF/DLqbZIcpI08yQKyrBgYz2uO51/oNp8a
-sTCsV4OUfyHhx2BBLUo4g4SptHFySTBwlpRWBnSjZPOhmN74JcpTLB4J5f4iEeA7
-2QytZfADckG4wVkhH3C2EJUmRtFIBVirwDn39GXkSGlnvnMgF3uLZ6zNAgMBAAGj
-YTBfMA4GA1UdDwEB/wQEAwIFoDATBgNVHSUEDDAKBggrBgEFBQcDAjAMBgNVHRMB
-Af8EAjAAMB0GA1UdDgQWBBTREl2hW54lkQBDeVCcd2f2VSlB1DALBgNVHREEBDAC
-ggAwDQYJKoZIhvcNAQELBQADggEBABpZjuIKTq8pCaX8dMEGPWtAykgLsTcD2jYr
-L0/TCrqmuaaliUa42jQTt2OVsVP/L8ofFunj/KjpQU0bvKJPLMRKtmxbhXuQCQi1
-qCRkp8o93mHvEz3mTUN+D1cfQ2fpsBENLnpS0F4G/JyY2Vrh19/X8+mImMEK5eOy
-o0BMby7byUj98WmcUvNCiXbC6F45QTmkwEhMqWns0JZQY+/XeDhEcg+lJvz9Eyo2
-aGgPsye1o3DpyXnyfJWAWMhOz7cikS5X2adesbgI86PhEHBXPIJ1v13ZdfCExmdd
-M1fLPhLyR54fGaY+7/X8P9AZzPefAkwizeXwe9ii6/a08vWoiE4=
------END CERTIFICATE-----
-```
-
-Non-PEM content may appear before or after the CERTIFICATE PEM blocks and is unvalidated,
-to allow for explanatory text as described in [section 5.2 of RFC7468](https://www.rfc-editor.org/rfc/rfc7468#section-5.2).
-
-When encoded in JSON or YAML, this field is base-64 encoded.
-A CertificateSigningRequest containing the example certificate above would look like this:
-
-```yaml
-apiVersion: certificates.k8s.io/v1
-kind: CertificateSigningRequest
-...
-status:
-  certificate: "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JS..."
-```
-
-## ClusterTrustBundles (Alpha Feature) {#ctb}
+## Cluster trust bundles {#cluster-trust-bundles}
 
 {{< feature-state for_k8s_version="v1.27" state="alpha" >}}
 
 {{< note >}}
-Gated by the `ClusterTrustBundles` feature gate.
+In Kubernetes {{< skew currentVersion >}}, you must enable the `ClusterTrustBundles`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+_and_ the `certificates.k8s.io/v1alpha1`
+{{< glossary_tooltip text="API group" term_id="api-group" >}} in order to use
+this API.
 {{< /note >}}
 
-ClusterTrustBundles are a cluster-scoped object for distributing X.509 trust
+A ClusterTrustBundles is a cluster-scoped object for distributing X.509 trust
 anchors (root certificates) to workloads within the cluster.  They're designed
-to work well with the existing signer concept.
+to work well with the [signer](#signers) concept from CertificateSigningRequests.
 
-Future Kubernetes releases will build on them with integrations like the ability
-to project their contents into the pod filesystem.
-
-ClusterTrustBundles can be used in two modes: signer-linked and signer-unlinked.
+ClusterTrustBundles can be used in two modes:
+[signer-linked](#ctb-signer-linked) and [signer-unlinked](#ctb-signer-unlinked).
 
 ### Common properties and validation {#ctb-common}
 
 All ClusterTrustBundle objects have strong validation on the contents of their
-`trustBundle` field.  It must contain one or more X.509 certificates,
+`trustBundle` field.  That field must contain one or more X.509 certificates,
 DER-serialized, each wrapped in a PEM `CERTIFICATE` block.  The certificates
 must parse as valid X.509 certificates.
 
 Esoteric PEM features like inter-block data and intra-block headers are either
-rejected during object validation, or filtered by consumers of the object
-(primarily Kubelet).  Additionally, consumers will reorder the certificates in
+rejected during object validation, or can be ignored by consumers of the object.
+Additionally, consumers are allowed to reorder the certificates in
 the bundle with their own arbitrary but stable ordering.
 
 ClusterTrustBundle objects should be considered world-readable within the
-cluster.  All serviceaccounts have a default RBAC grant to get, list, and watch
-all ClusterTrustBundle objects.
+cluster. If your cluster uses [RBAC](/docs/reference/access-authn-authz/rbac/)
+authorization, all ServiceAccounts have a default grant that allows them to
+**get**, **list**, and **watch** all ClusterTrustBundle objects.
+If you use your own authorization mechanism and you have enabled
+ClusterTrustBundles in your cluster, you should set up an equivalent rule to
+make these objects public within the cluster, so that they work as intended.
 
 ### Signer-linked ClusterTrustBundles {#ctb-signer-linked}
 
-Signer-linked ClusterTrustBundles are associated with a signer name, like this:
+Signer-linked ClusterTrustBundles are associated with a _signer name_, like this:
 
 ```yaml
 apiVersion: certificates.k8s.io/v1alpha1
@@ -509,20 +422,22 @@ spec:
 These ClusterTrustBundles are intended to be maintained by a signer-specific
 controller in the cluster, so they have several security features:
 
-* To create or update a signer-linked ClusterTrustBundle, you must have the
-  `attest` verb on the signer (verbs: `attest`, group: `certificates.k8s.io`,
-  resource: `signers`, resourceName: `<signerNameDomain>/<signerNamePath>` or
-  `<signerNameDomain>/*`).
-* Signer-linked ClusterTrustBundles must be named with a prefix derived from
+* To create or update a signer-linked ClusterTrustBundle, you must be permitted
+  to **attest** on the signer (custom authorization verb `attest`,
+  API group `certificates.k8s.io`; resource path `signers`). You can configure
+  authorization for the specific resource name
+  `<signerNameDomain>/<signerNamePath>` or match a pattern such as
+  `<signerNameDomain>/*`.
+* Signer-linked ClusterTrustBundles **must** be named with a prefix derived from
   their `spec.signerName` field.  Slashes (`/`) are replaced with colons (`:`),
   and a final colon is appended.  This is followed by an arbitary name.  For
-  example, the signer `example.com/mysigner` becomes
-  `example.com:mysigner:<arbitrary-name>`.
+  example, the signer `example.com/mysigner` can be linked to a
+  ClusterTrustBundle `example.com:mysigner:<arbitrary-name>`.
 
-Signer-linked ClusterTrustBundles will be consumed in workloads by a combination
-of field selector on the signer name and a label selector.  If this query
-matches multiple ClusterTrustBundle objects, their contents will be merged,
-deduplicated, and sorted before being provided to the workload.
+Signer-linked ClusterTrustBundles will typically be consumed in workloads
+by a combination of a
+[field selector](/docs/concepts/overview/working-with-objects/field-selectors/) on the signer name, and a separate
+[label selector](/docs/concepts/overview/working-with-objects/labels/#label-selectors).
 
 ### Signer-unlinked ClusterTrustBundles {#ctb-signer-unlinked}
 
@@ -534,7 +449,7 @@ kind: ClusterTrustBundle
 metadata:
   name: foo
 spec:
-  signerName: ""
+  # no signerName specified, so the field is blank
   trustBundle: "<... PEM data ...>"
 ```
 
@@ -542,11 +457,135 @@ They are primarily intended for cluster configuration use cases.  Each
 signer-unlinked ClusterTrustBundle is an independent object, in contrast to the
 customary grouping behavior of signer-linked ClusterTrustBundles.
 
-Signer-unlinked ClusterTrustBundles have no `attest` verb requirement.  Instead,
-control access to them using the standard RBAC verbs.
+Signer-unlinked ClusterTrustBundles have no `attest` verb requirement.
+Instead, you control access to them directly using the usual mechanisms,
+such as role-based access control.
 
 To distinguish them from signer-linked ClusterTrustBundles, the names of
-signer-unlinked ClusterTrustBundles must not contain a colon (`:`).
+signer-unlinked ClusterTrustBundles **must not** contain a colon (`:`).
+
+<!-- TODO this should become a task page -->
+## How to issue a certificate for a user {#normal-user}
+
+A few steps are required in order to get a normal user to be able to
+authenticate and invoke an API. First, this user must have a certificate issued
+by the Kubernetes cluster, and then present that certificate to the Kubernetes API.
+
+### Create private key
+
+The following scripts show how to generate PKI private key and CSR. It is
+important to set CN and O attribute of the CSR. CN is the name of the user and
+O is the group that this user will belong to. You can refer to
+[RBAC](/docs/reference/access-authn-authz/rbac/) for standard groups.
+
+```shell
+openssl genrsa -out myuser.key 2048
+openssl req -new -key myuser.key -out myuser.csr
+```
+
+### Create a CertificateSigningRequest {#create-certificatessigningrequest}
+
+Create a CertificateSigningRequest and submit it to a Kubernetes Cluster via kubectl. Below is a script to generate the CertificateSigningRequest.
+
+```shell
+cat <<EOF | kubectl apply -f -
+apiVersion: certificates.k8s.io/v1
+kind: CertificateSigningRequest
+metadata:
+  name: myuser
+spec:
+  request: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURSBSRVFVRVNULS0tLS0KTUlJQ1ZqQ0NBVDRDQVFBd0VURVBNQTBHQTFVRUF3d0dZVzVuWld4aE1JSUJJakFOQmdrcWhraUc5dzBCQVFFRgpBQU9DQVE4QU1JSUJDZ0tDQVFFQTByczhJTHRHdTYxakx2dHhWTTJSVlRWMDNHWlJTWWw0dWluVWo4RElaWjBOCnR2MUZtRVFSd3VoaUZsOFEzcWl0Qm0wMUFSMkNJVXBGd2ZzSjZ4MXF3ckJzVkhZbGlBNVhwRVpZM3ExcGswSDQKM3Z3aGJlK1o2MVNrVHF5SVBYUUwrTWM5T1Nsbm0xb0R2N0NtSkZNMUlMRVI3QTVGZnZKOEdFRjJ6dHBoaUlFMwpub1dtdHNZb3JuT2wzc2lHQ2ZGZzR4Zmd4eW8ybmlneFNVekl1bXNnVm9PM2ttT0x1RVF6cXpkakJ3TFJXbWlECklmMXBMWnoyalVnald4UkhCM1gyWnVVV1d1T09PZnpXM01LaE8ybHEvZi9DdS8wYk83c0x0MCt3U2ZMSU91TFcKcW90blZtRmxMMytqTy82WDNDKzBERHk5aUtwbXJjVDBnWGZLemE1dHJRSURBUUFCb0FBd0RRWUpLb1pJaHZjTgpBUUVMQlFBRGdnRUJBR05WdmVIOGR4ZzNvK21VeVRkbmFjVmQ1N24zSkExdnZEU1JWREkyQTZ1eXN3ZFp1L1BVCkkwZXpZWFV0RVNnSk1IRmQycVVNMjNuNVJsSXJ3R0xuUXFISUh5VStWWHhsdnZsRnpNOVpEWllSTmU3QlJvYXgKQVlEdUI5STZXT3FYbkFvczFqRmxNUG5NbFpqdU5kSGxpT1BjTU1oNndLaTZzZFhpVStHYTJ2RUVLY01jSVUyRgpvU2djUWdMYTk0aEpacGk3ZnNMdm1OQUxoT045UHdNMGM1dVJVejV4T0dGMUtCbWRSeEgvbUNOS2JKYjFRQm1HCkkwYitEUEdaTktXTU0xMzhIQXdoV0tkNjVoVHdYOWl4V3ZHMkh4TG1WQzg0L1BHT0tWQW9FNkpsYWFHdTlQVmkKdjlOSjVaZlZrcXdCd0hKbzZXdk9xVlA3SVFjZmg3d0drWm89Ci0tLS0tRU5EIENFUlRJRklDQVRFIFJFUVVFU1QtLS0tLQo=
+  signerName: kubernetes.io/kube-apiserver-client
+  expirationSeconds: 86400  # one day
+  usages:
+  - client auth
+EOF
+```
+
+Some points to note:
+
+- `usages` has to be '`client auth`'
+- `expirationSeconds` could be made longer (i.e. `864000` for ten days) or shorter (i.e. `3600` for one hour)
+- `request` is the base64 encoded value of the CSR file content.
+  You can get the content using this command: 
+
+  ```shell
+  cat myuser.csr | base64 | tr -d "\n"
+  ```
+
+
+### Approve the CertificateSigningRequest {#approve-certificate-signing-request}
+
+Use kubectl to create a CSR and approve it.
+
+Get the list of CSRs:
+
+```shell
+kubectl get csr
+```
+
+Approve the CSR:
+
+```shell
+kubectl certificate approve myuser
+```
+
+### Get the certificate
+
+Retrieve the certificate from the CSR:
+
+```shell
+kubectl get csr/myuser -o yaml
+```
+
+The certificate value is in Base64-encoded format under `status.certificate`.
+
+Export the issued certificate from the CertificateSigningRequest.
+
+```shell
+kubectl get csr myuser -o jsonpath='{.status.certificate}'| base64 -d > myuser.crt
+```
+
+### Create Role and RoleBinding
+
+With the certificate created it is time to define the Role and RoleBinding for
+this user to access Kubernetes cluster resources.
+
+This is a sample command to create a Role for this new user:
+
+```shell
+kubectl create role developer --verb=create --verb=get --verb=list --verb=update --verb=delete --resource=pods
+```
+
+This is a sample command to create a RoleBinding for this new user:
+
+```shell
+kubectl create rolebinding developer-binding-myuser --role=developer --user=myuser
+```
+
+### Add to kubeconfig
+
+The last step is to add this user into the kubeconfig file.
+
+First, you need to add new credentials:
+
+```shell
+kubectl config set-credentials myuser --client-key=myuser.key --client-certificate=myuser.crt --embed-certs=true
+
+```
+
+Then, you need to add the context:
+
+```shell
+kubectl config set-context myuser --cluster=kubernetes --user=myuser
+```
+
+To test it, change the context to `myuser`:
+
+```shell
+kubectl config use-context myuser
+```
+
 
 ## {{% heading "whatsnext" %}}
 

From ad7e7bae55016e1bf17c8bb4ce935cf3717d7079 Mon Sep 17 00:00:00 2001
From: my-git9 <xin.li@daocloud.io>
Date: Mon, 10 Apr 2023 08:51:25 +0800
Subject: [PATCH 146/272] [zh-cn]rync and improve using-api/_index.md (#40570)

Signed-off-by: xin.li <xin.li@daocloud.io>
---
 content/zh-cn/docs/reference/_index.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/content/zh-cn/docs/reference/_index.md b/content/zh-cn/docs/reference/_index.md
index d2674056720..61b2b4776dc 100644
--- a/content/zh-cn/docs/reference/_index.md
+++ b/content/zh-cn/docs/reference/_index.md
@@ -85,7 +85,7 @@ client libraries:
 * [kubectl](/zh-cn/docs/reference/kubectl/) —— 主要的 CLI 工具，用于运行命令和管理 Kubernetes 集群。
   * [JSONPath](/zh-cn/docs/reference/kubectl/jsonpath/) —— 通过 kubectl 使用
     [JSONPath 表达式](https://goessner.net/articles/JsonPath/)的语法指南。
-* [kubeadm](/zh-cn/docs/reference/setup-tools/kubeadm/) - 此 CLI 工具可轻松配置安全的 Kubernetes 集群。
+* [kubeadm](/zh-cn/docs/reference/setup-tools/kubeadm/) —— 此 CLI 工具可轻松配置安全的 Kubernetes 集群。
 
 <!--
 ## Components
@@ -139,6 +139,7 @@ operator to use or manage a cluster.
 * [kubeconfig (v1)](/docs/reference/config-api/kubeconfig.v1/)
 * [kube-apiserver admission (v1)](/docs/reference/config-api/apiserver-admission.v1/)
 * [kube-apiserver configuration (v1alpha1)](/docs/reference/config-api/apiserver-config.v1alpha1/) and
+  [kube-apiserver configuration (v1beta1)](/docs/reference/config-api/apiserver-config.v1beta1/) and
   [kube-apiserver configuration (v1)](/docs/reference/config-api/apiserver-config.v1/)
 * [kube-apiserver encryption (v1)](/docs/reference/config-api/apiserver-encryption.v1/)
 * [kube-apiserver event rate limit (v1alpha1)](/docs/reference/config-api/apiserver-eventratelimit.v1alpha1/)
@@ -168,6 +169,7 @@ operator to use or manage a cluster.
 * [kubeconfig (v1)](/zh-cn/docs/reference/config-api/kubeconfig.v1/)
 * [kube-apiserver 准入 (v1)](/zh-cn/docs/reference/config-api/apiserver-admission.v1/)
 * [kube-apiserver 配置 (v1alpha1)](/zh-cn/docs/reference/config-api/apiserver-config.v1alpha1/) 和
+  [kube-apiserver 配置 (v1beta1)](/zh-cn/docs/reference/config-api/apiserver-config.v1beta1/) 和
   [kube-apiserver 配置 (v1)](/zh-cn/docs/reference/config-api/apiserver-config.v1/)
 * [kube-apiserver 加密 (v1)](/zh-cn/docs/reference/config-api/apiserver-encryption.v1/)
 * [kube-apiserver 事件速率限制 (v1alpha1)](/zh-cn/docs/reference/config-api/apiserver-eventratelimit.v1alpha1/)
@@ -209,6 +211,6 @@ An archive of the design docs for Kubernetes functionality. Good starting points
 ## 设计文档   {#design-docs}
 
 Kubernetes 功能的设计文档归档，不妨考虑从
-[Kubernetes 架构](https://git.k8s.io/design-proposals-archive/architecture/architecture.md) 和
+[Kubernetes 架构](https://git.k8s.io/design-proposals-archive/architecture/architecture.md)和
 [Kubernetes 设计概述](https://git.k8s.io/design-proposals-archive)开始阅读。
 

From 2d14bb7c383b02cd924b9312eb9d9083a74d9af7 Mon Sep 17 00:00:00 2001
From: Kensei Nakada <handbomusic@gmail.com>
Date: Mon, 10 Apr 2023 10:31:38 +0900
Subject: [PATCH 147/272] fix link

---
 .../en/blog/_posts/2023-04-11-topology-spread-features.md   | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/content/en/blog/_posts/2023-04-11-topology-spread-features.md b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
index f8fa99cdc5c..2bd8e45f7dd 100644
--- a/content/en/blog/_posts/2023-04-11-topology-spread-features.md
+++ b/content/en/blog/_posts/2023-04-11-topology-spread-features.md
@@ -8,7 +8,7 @@ evergreen: true
 
 **Authors:** [Alex Wang](https://github.com/denkensk)(Shopee), [Kante Yin](https://github.com/kerthcet)(DaoCloud), [Kensei Nakada](https://github.com/sanposhiho)(Mercari)
 
-In Kubernetes v1.19, [Pod Topology Spread Constraints](https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/) went to GA.
+In Kubernetes v1.19, [Pod Topology Spread Constraints](/docs/concepts/scheduling-eviction/topology-spread-constraints/) went to GA.
 It is the feature to control how Pods are spread in the cluster topology or failure domains (regions, zones, nodes etc).
 
 As time passed, we received feedback from users,
@@ -116,7 +116,7 @@ With `matchLabelKeys`, you don't need to update the `pod.spec` between different
 The controller or operator managing rollouts just needs to set different values to the same label key for different revisions.
 The scheduler will assume the values automatically based on `matchLabelKeys`.
 For example, if you are configuring a Deployment, you can use the label keyed with
-[pod-template-hash](https://kubernetes.io//docs/concepts/workloads/controllers/deployment/#pod-template-hash-label),
+[pod-template-hash](/docs/concepts/workloads/controllers/deployment/#pod-template-hash-label),
 which is added automatically by the Deployment controller, to distinguish between different
 revisions in a single Deployment.
 
@@ -140,7 +140,7 @@ Please join us and share your feedback. We look forward to hearing from you!
 
 ## How can I learn more?
 
-- [Pod Topology Spread Constraints | Kubernetes](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#container-resource-metrics)
+- [Pod Topology Spread Constraints | Kubernetes](/docs/concepts/scheduling-eviction/topology-spread-constraints/)
 - [KEP-3022: min domains in Pod Topology Spread](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/3022-min-domains-in-pod-topology-spread)
 - [KEP-3094: Take taints/tolerations into consideration when calculating PodTopologySpread skew](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/3094-pod-topology-spread-considering-taints)
 - [KEP-3243: Respect PodTopologySpread after rolling upgrades](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/3243-respect-pod-topology-spread-after-rolling-upgrades)
\ No newline at end of file

From 78bddabd769997c5a1b8230238c5a06d09a52014 Mon Sep 17 00:00:00 2001
From: "xin.li" <xin.li@daocloud.io>
Date: Sun, 9 Apr 2023 11:40:13 +0800
Subject: [PATCH 148/272] [zh-cn]sync define-environment-variable-container.md

Signed-off-by: xin.li <xin.li@daocloud.io>
---
 .../define-environment-variable-container.md  | 35 +++++++++++++++++++
 1 file changed, 35 insertions(+)

diff --git a/content/zh-cn/docs/tasks/inject-data-application/define-environment-variable-container.md b/content/zh-cn/docs/tasks/inject-data-application/define-environment-variable-container.md
index 375d58dd440..3aba156c849 100644
--- a/content/zh-cn/docs/tasks/inject-data-application/define-environment-variable-container.md
+++ b/content/zh-cn/docs/tasks/inject-data-application/define-environment-variable-container.md
@@ -36,6 +36,41 @@ that run in the Pod. To set environment variables, include the `env` or
 -->
 创建 Pod 时，可以为其下的容器设置环境变量。通过配置文件的 `env` 或者 `envFrom` 字段来设置环境变量。
 
+<!--
+The `env` and `envFrom` fields have different effects.
+
+`env`
+: allows you to set environment variables for a container, specifying a value directly for each variable that you name.
+-->
+`env` 和 `envFrom` 字段具有不同的效果。
+
+`env`
+：可以为容器设置环境变量，直接为你所给的每个变量指定一个值。
+
+<!--
+`envFrom`
+: allows you to set environment variables for a container by referencing either a ConfigMap or a Secret.
+ When you use `envFrom`, all the key-value pairs in the referenced ConfigMap or Secret
+ are set as environment variables for the container.
+ You can also specify a common prefix string.
+-->
+`envFrom`
+：你可以通过引用 ConfigMap 或 Secret 来设置容器的环境变量。
+使用 `envFrom` 时，引用的 ConfigMap 或 Secret 中的所有键值对都被设置为容器的环境变量。
+你也可以指定一个通用的前缀字符串。
+
+<!--
+You can read more about [ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/#configure-all-key-value-pairs-in-a-configmap-as-container-environment-variables)
+and [Secret](/docs/tasks/inject-data-application/distribute-credentials-secure/#configure-all-key-value-pairs-in-a-secret-as-container-environment-variables).
+
+This page explains how to use `env`.
+-->
+你可以阅读有关 [ConfigMap](/zh-cn/docs/tasks/configure-pod-container/configure-pod-configmap/#configure-all-key-value-pairs-in-a-configmap-as-container-environment-variables)
+和 [Secret](/zh-cn/docs/tasks/inject-data-application/distribute-credentials-secure/#configure-all-key-value-pairs-in-a-secret-as-container-environment-variables)
+的更多信息。
+
+本页介绍如何使用 `env`。
+
 <!--
 In this exercise, you create a Pod that runs one container. The configuration
 file for the Pod defines an environment variable with name `DEMO_GREETING` and

From 8caa18ab83c3e7b12e8220912592a8a79e934c9d Mon Sep 17 00:00:00 2001
From: Guangwen Feng <fenggw-fnst@fujitsu.com>
Date: Mon, 10 Apr 2023 14:27:16 +0800
Subject: [PATCH 149/272] [zh-cn] Sync
 administer-cluster/dns-debugging-resolution.md

Signed-off-by: Guangwen Feng <fenggw-fnst@fujitsu.com>
---
 .../dns-debugging-resolution.md               | 30 +++++++++----------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/content/zh-cn/docs/tasks/administer-cluster/dns-debugging-resolution.md b/content/zh-cn/docs/tasks/administer-cluster/dns-debugging-resolution.md
index dd480adb414..31aa6068cb3 100644
--- a/content/zh-cn/docs/tasks/administer-cluster/dns-debugging-resolution.md
+++ b/content/zh-cn/docs/tasks/administer-cluster/dns-debugging-resolution.md
@@ -4,6 +4,15 @@ content_type: task
 min-kubernetes-server-version: v1.6
 weight: 170
 ---
+<!--
+reviewers:
+- bowei
+- zihongz
+title:  Debugging DNS Resolution
+content_type: task
+min-kubernetes-server-version: v1.6
+weight: 170
+-->
 
 <!-- overview -->
 <!--
@@ -11,8 +20,6 @@ This page provides hints on diagnosing DNS problems.
 -->
 这篇文章提供了一些关于 DNS 问题诊断的方法。
 
-<!-- steps -->
-
 ## {{% heading "prerequisites" %}}
 
 {{< include "task-tutorial-prereqs.md" >}}
@@ -28,6 +35,8 @@ kube-dns.
 
 {{< version-check >}}
 
+<!-- steps -->
+
 <!--
 ### Create a simple Pod to use as a test environment
 
@@ -40,17 +49,8 @@ services depends on the namespace of the pod. For more information, review
 {{< /note >}}
 
 Use that manifest to create a Pod:
-
-```shell
-kubectl create -f https://k8s.io/examples/admin/dns/busybox.yaml
-pod/busybox created
-
-kubectl get pods busybox
-NAME      READY     STATUS    RESTARTS   AGE
-busybox   1/1       Running   0          <some-time>
-```
 -->
-### 创建一个简单的 Pod 作为测试环境
+### 创建一个简单的 Pod 作为测试环境   {#create-a-simple-pod-to-use-as-a-test-environment}
 
 {{< codenew file="admin/dns/dnsutils.yaml" >}}
 
@@ -117,7 +117,7 @@ Take a look inside the resolv.conf file.
 (See [Customizing DNS Service](/docs/tasks/administer-cluster/dns-custom-nameservers) and
 [Known issues](#known-issues) below for more information)
 -->
-### 先检查本地的 DNS 配置
+### 先检查本地的 DNS 配置   {#check-the-local-dns-configuration-first}
 
 查看 resolv.conf 文件的内容
 （阅读[定制 DNS 服务](/zh-cn/docs/tasks/administer-cluster/dns-custom-nameservers/) 和
@@ -405,7 +405,7 @@ term_id="endpoint" >}} related resources to properly resolve service names.
 
 Sample error message:
 -->
-### CoreDNS 是否有足够的权限？
+### CoreDNS 是否有足够的权限？   {#does-coredns-have-sufficient-permissions}
 
 CoreDNS 必须能够列出 {{< glossary_tooltip text="service" term_id="service" >}} 和
 {{< glossary_tooltip text="endpoint" term_id="endpoint" >}} 相关的资源来正确解析服务名称。
@@ -476,7 +476,7 @@ the namespace of the service.
 
 This query is limited to the pod's namespace:
 -->
-### 你的服务在正确的名字空间中吗？
+### 你的服务在正确的名字空间中吗？   {#are-you-in-the-right-namespace-for-the-service}
 
 未指定名字空间的 DNS 查询仅作用于 Pod 所在的名字空间。
 

From 8aa1ec497dcf39e527feed4709b5af3ef7960fca Mon Sep 17 00:00:00 2001
From: Arhell <arhell333@gmail.com>
Date: Mon, 10 Apr 2023 11:44:26 +0300
Subject: [PATCH 150/272] [ja] Update branch name in ingress-nginx github link

---
 content/ja/docs/concepts/services-networking/ingress.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/ja/docs/concepts/services-networking/ingress.md b/content/ja/docs/concepts/services-networking/ingress.md
index 1ffa2299131..620a4580d29 100644
--- a/content/ja/docs/concepts/services-networking/ingress.md
+++ b/content/ja/docs/concepts/services-networking/ingress.md
@@ -51,7 +51,7 @@ Ingressリソースの最小構成の例は以下のとおりです。
 
 {{< codenew file="service/networking/minimal-ingress.yaml" >}}
 
-Ingressには`apiVersion`、`kind`、`metadata`や`spec`フィールドが必要です。Ingressオブジェクトの名前は、有効な[DNSサブドメイン名](/ja/docs/concepts/overview/working-with-objects/names#dns-subdomain-names)である必要があります。設定ファイルに関する一般的な情報は、[アプリケーションのデプロイ](/ja/docs/tasks/run-application/run-stateless-application-deployment/)、[コンテナの設定](/ja/docs/tasks/configure-pod-container/configure-pod-configmap/)、[リソースの管理](/ja/docs/concepts/cluster-administration/manage-deployment/)を参照してください。Ingressでは、Ingressコントローラーに依存しているいくつかのオプションの設定をするためにアノテーションを一般的に使用します。例としては、[rewrite-targetアノテーション](https://github.com/kubernetes/ingress-nginx/blob/master/docs/examples/rewrite/README.md)などがあります。[Ingressコントローラー](/ja/docs/concepts/services-networking/ingress-controllers)の種類が異なれば、サポートするアノテーションも異なります。サポートされているアノテーションについて学ぶためには、使用するIngressコントローラーのドキュメントを確認してください。
+Ingressには`apiVersion`、`kind`、`metadata`や`spec`フィールドが必要です。Ingressオブジェクトの名前は、有効な[DNSサブドメイン名](/ja/docs/concepts/overview/working-with-objects/names#dns-subdomain-names)である必要があります。設定ファイルに関する一般的な情報は、[アプリケーションのデプロイ](/ja/docs/tasks/run-application/run-stateless-application-deployment/)、[コンテナの設定](/ja/docs/tasks/configure-pod-container/configure-pod-configmap/)、[リソースの管理](/ja/docs/concepts/cluster-administration/manage-deployment/)を参照してください。Ingressでは、Ingressコントローラーに依存しているいくつかのオプションの設定をするためにアノテーションを一般的に使用します。例としては、[rewrite-targetアノテーション](https://github.com/kubernetes/ingress-nginx/blob/main/docs/examples/rewrite/README.md)などがあります。[Ingressコントローラー](/ja/docs/concepts/services-networking/ingress-controllers)の種類が異なれば、サポートするアノテーションも異なります。サポートされているアノテーションについて学ぶためには、使用するIngressコントローラーのドキュメントを確認してください。
 
 Ingress [Spec](https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status)は、ロードバランサーやプロキシーサーバーを設定するために必要な全ての情報を持っています。最も重要なものとして、外部からくる全てのリクエストに対して一致したルールのリストを含みます。IngressリソースはHTTP(S)トラフィックに対してのルールのみサポートしています。
 

From 811f1290e58947c585b6f85b7eacb51b9212d257 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Marko=20Mudrini=C4=87?= <mudrinic.mare@gmail.com>
Date: Mon, 10 Apr 2023 12:25:07 +0200
Subject: [PATCH 151/272] [pt-br] Replace k8s.gcr.io with registry.k8s.io in
 reference doc
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
---
 .../setup-tools/kubeadm/generated/kubeadm_config_images_pull.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/pt-br/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_images_pull.md b/content/pt-br/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_images_pull.md
index 15b6fd9195c..a4f3864a434 100644
--- a/content/pt-br/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_images_pull.md
+++ b/content/pt-br/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_images_pull.md
@@ -59,7 +59,7 @@ kubeadm config images pull [flags]
 </tr>
 
 <tr>
-<td colspan="2">--image-repository string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Padrão: "k8s.gcr.io"</td>
+<td colspan="2">--image-repository string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Padrão: "registry.k8s.io"</td>
 </tr>
 <tr>
 <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Escolha um registro de contêineres para baixar imagens da camada de gerenciamento</p></td>

From 2d7cc470c2ba7898483a8bd537846af1c931e5ec Mon Sep 17 00:00:00 2001
From: Katrina Verey <katrina.verey@shopify.com>
Date: Tue, 4 Apr 2023 14:51:33 -0400
Subject: [PATCH 152/272] Add blog post introducing ApplySet-based pruning

---
 ...ore-Performant-Pruning-in-kubectl-apply.md | 71 +++++++++++++++++++
 1 file changed, 71 insertions(+)
 create mode 100644 content/en/blog/_posts/2023-05-09-Safer-More-Performant-Pruning-in-kubectl-apply.md

diff --git a/content/en/blog/_posts/2023-05-09-Safer-More-Performant-Pruning-in-kubectl-apply.md b/content/en/blog/_posts/2023-05-09-Safer-More-Performant-Pruning-in-kubectl-apply.md
new file mode 100644
index 00000000000..d8d1b9a138c
--- /dev/null
+++ b/content/en/blog/_posts/2023-05-09-Safer-More-Performant-Pruning-in-kubectl-apply.md
@@ -0,0 +1,71 @@
+---
+layout: blog
+title: "Kubernetes 1.27: Safer, More Performant Pruning in kubectl apply"
+date: 2023-05-09
+slug: introducing-kubectl-applyset-pruning
+---
+
+**Authors:** Katrina Verey (Shopify) and Justin Santa Barbara (Google)
+
+Declarative configuration management with the `kubectl apply` command is the gold standard approach
+to creating or modifying Kubernetes resources. However, one challenge it presents is the deletion
+of resources that are no longer needed. In Kubernetes version 1.5, the `--prune` flag was
+introduced to address this issue, allowing kubectl apply to automatically clean up previously
+applied resources removed from the current configuration.
+
+Unfortunately, that existing implementation of `--prune` has design flaws that diminish its
+performance and can result in unexpected behaviors. The main issue stems from the lack of explicit
+encoding of the previously applied set by the preceding `apply` operation, necessitating
+error-prone dynamic discovery. Object leakage, inadvertent over-selection of resources, and limited
+compatibility with custom resources are a few notable drawbacks of this implementation. Moreover,
+its coupling to client-side apply hinders user upgrades to the superior server-side apply
+mechanism.
+
+Version 1.27 of `kubectl` introduces an alpha version of a revamped pruning implementation that
+addresses these issues. This new implementation, based on a concept called _ApplySet_, promises
+better performance and safety.
+
+An _ApplySet_ is a group of resources associated with a _parent_ object on the cluster, as
+identified and configured through standardized labels and annotations. Additional standardized
+metadata allows for accurate identification of ApplySet _member_ objects within the cluster,
+simplifying operations like pruning.
+
+To leverage ApplySet-based pruning, set the `KUBECTL_APPLYSET=true` environment variable and include
+the flags `--prune` and `--applyset` in your `kubectl apply` invocation:
+
+```shell
+KUBECTL_APPLYSET=true kubectl apply -f <directory/> --prune --applyset=<name>
+```
+
+By default, ApplySet uses a Secret as the parent object. However, you can also use
+a ConfigMap with the format `--applyset=configmaps/<name>`. If your desired Secret or
+ConfigMap object does not yet exist, `kubectl` will create it for you. Furthermore, custom
+resources can be enabled for use as ApplySet parent objects.
+
+The ApplySet implementation is based on a new low-level specification that can support higher-level
+ecosystem tools by improving their interoperability. The lightweight nature of this specification
+enables these tools to continue to use existing object grouping systems while opting in to
+ApplySet's metadata conventions to prevent inadvertent changes by other tools (such as `kubectl`).
+
+ApplySet-based pruning offers a promising solution to the shortcomings of the previous `--prune`
+implementation in `kubectl` and can help streamline your Kubernetes resource management. Please
+give this new feature a try and share your experiences with the community—ApplySet is under active
+development, and your feedback is invaluable!
+
+
+### Additional resources
+
+- For more information how to use ApplySet-based pruning, read
+  [Declarative Management of Kubernetes Objects Using Configuration Files](/docs/tasks/manage-kubernetes-objects/declarative-config/) in the Kubernetes documentation.
+- For a deeper dive into the technical design of this feature or to learn how to implement the
+  ApplySet specification in your own tools, refer to [KEP&nbsp;3659](https://git.k8s.io/enhancements/keps/sig-cli/3659-kubectl-apply-prune/README.md):
+  _ApplySet: `kubectl apply --prune` redesign and graduation strategy_.
+
+
+### How do I get involved?
+
+If you want to get involved in ApplySet development, you can get in touch with the developers at
+[SIG CLI](https://git.k8s.io/community/sig-cli). To provide feedback on the feature, please
+[file a bug](https://github.com/kubernetes/kubectl/issues/new?assignees=knverey,justinsb&labels=kind%2Fbug&template=bug-report.md)
+or [request an enhancement](https://github.com/kubernetes/kubectl/issues/new?assignees=knverey,justinsb&labels=kind%2Fbug&template=enhancement.md)
+on the `kubernetes/kubectl` repository.

From fe00b86c3eca67f82d95d3c2d9d8aa237e921d1a Mon Sep 17 00:00:00 2001
From: Nate W <natew@cncf.io>
Date: Mon, 10 Apr 2023 12:28:48 -0700
Subject: [PATCH 153/272] Update data/releases/schedule.yaml

Co-authored-by: Rey Lejano <rlejano@gmail.com>
---
 data/releases/schedule.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/data/releases/schedule.yaml b/data/releases/schedule.yaml
index 19ce450ae92..c41858faf34 100644
--- a/data/releases/schedule.yaml
+++ b/data/releases/schedule.yaml
@@ -5,7 +5,7 @@ schedules:
   endOfLifeDate: 2024-06-28
   next:
     release: 1.27.1
-    cherryPickDeadline: 2023-04-07
+    cherryPickDeadline: 2023-05-10
     targetDate: 2023-04-12
   previousPatches:
     - release: 1.27.0

From e7b492194a12c6ad0f67a42b263db9efddaafc4a Mon Sep 17 00:00:00 2001
From: Nate W <natew@cncf.io>
Date: Mon, 10 Apr 2023 12:29:07 -0700
Subject: [PATCH 154/272] Update data/releases/schedule.yaml

Co-authored-by: Rey Lejano <rlejano@gmail.com>
---
 data/releases/schedule.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/data/releases/schedule.yaml b/data/releases/schedule.yaml
index c41858faf34..4673097d521 100644
--- a/data/releases/schedule.yaml
+++ b/data/releases/schedule.yaml
@@ -6,7 +6,7 @@ schedules:
   next:
     release: 1.27.1
     cherryPickDeadline: 2023-05-10
-    targetDate: 2023-04-12
+    targetDate: 2023-05-17
   previousPatches:
     - release: 1.27.0
       cherryPickDeadline: ""

From 99dedbabf9094f47ac5e9b30d96159fb429befa5 Mon Sep 17 00:00:00 2001
From: Rob Scott <robertjscott@google.com>
Date: Fri, 17 Mar 2023 02:01:38 +0000
Subject: [PATCH 155/272] Updating documentation for Topology Aware Routing in
 1.27

---
 .../services-networking/service-topology.md   |  4 +-
 ...are-hints.md => topology-aware-routing.md} | 91 +++++++++++++------
 static/_redirects                             |  1 +
 3 files changed, 68 insertions(+), 28 deletions(-)
 rename content/en/docs/concepts/services-networking/{topology-aware-hints.md => topology-aware-routing.md} (62%)

diff --git a/content/en/docs/concepts/services-networking/service-topology.md b/content/en/docs/concepts/services-networking/service-topology.md
index b833ff6e3b0..081a58cc851 100644
--- a/content/en/docs/concepts/services-networking/service-topology.md
+++ b/content/en/docs/concepts/services-networking/service-topology.md
@@ -16,8 +16,8 @@ weight: 150
 
 This feature, specifically the alpha `topologyKeys` API, is deprecated since
 Kubernetes v1.21.
-[Topology Aware Hints](/docs/concepts/services-networking/topology-aware-hints/),
-introduced in Kubernetes v1.21, provide similar functionality.
+[Topology Aware Routing](/docs/concepts/services-networking/topology-aware-routing/),
+introduced in Kubernetes v1.21, provides similar functionality.
 {{</ note >}}
 
 _Service Topology_ enables a service to route traffic based upon the Node
diff --git a/content/en/docs/concepts/services-networking/topology-aware-hints.md b/content/en/docs/concepts/services-networking/topology-aware-routing.md
similarity index 62%
rename from content/en/docs/concepts/services-networking/topology-aware-hints.md
rename to content/en/docs/concepts/services-networking/topology-aware-routing.md
index 7a6d212476e..1977f199d0c 100644
--- a/content/en/docs/concepts/services-networking/topology-aware-hints.md
+++ b/content/en/docs/concepts/services-networking/topology-aware-routing.md
@@ -1,11 +1,11 @@
 ---
 reviewers:
 - robscott
-title: Topology Aware Hints
+title: Topology Aware Routing
 content_type: concept
 weight: 100
 description: >-
-  _Topology Aware Hints_ provides a mechanism to help keep network traffic within the zone
+  _Topology Aware Routing_ provides a mechanism to help keep network traffic within the zone
   where it originated. Preferring same-zone traffic between Pods in your cluster can help
   with reliability, performance (network latency and throughput), or cost.
 ---
@@ -15,45 +15,68 @@ description: >-
 
 {{< 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
-consumers of EndpointSlice (or Endpoints) objects, so that traffic to
-those network endpoints can be routed closer to where it originated.
+{{< note >}}
+Prior to Kubernetes 1.27, this feature was known as _Topology Aware Hints_.
+{{</ note >}}
 
-For example, you can route traffic within a locality to reduce
-costs, or to improve network performance.
+_Topology Aware Routing_ adjusts routing behavior to prefer keeping traffic in
+the zone it originated from. In some cases this can help reduce costs or improve
+network performance.
 
 <!-- body -->
 
 ## Motivation
 
 Kubernetes clusters are increasingly deployed in multi-zone environments.
-_Topology Aware Hints_ provides a mechanism to help keep traffic within the zone
-it originated from. This concept is commonly referred to as "Topology Aware
-Routing". When calculating the endpoints for a {{< glossary_tooltip term_id="Service" >}},
-the EndpointSlice controller considers the topology (region and zone) of each endpoint
-and populates the hints field to allocate it to a zone.
-Cluster components such as the {{< glossary_tooltip term_id="kube-proxy" text="kube-proxy" >}}
-can then consume those hints, and use them to influence how the traffic is routed
-(favoring topologically closer endpoints).
+_Topology Aware Routing_ provides a mechanism to help keep traffic within the
+zone it originated from. When calculating the endpoints for a {{<
+glossary_tooltip term_id="Service" >}}, the EndpointSlice controller considers
+the topology (region and zone) of each endpoint and populates the hints field to
+allocate it to a zone. Cluster components such as {{< glossary_tooltip
+term_id="kube-proxy" text="kube-proxy" >}} can then consume those hints, and use
+them to influence how the traffic is routed (favoring topologically closer
+endpoints).
 
-## Using Topology Aware Hints
+## Enabling Topology Aware Routing
 
-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.
+{{< note >}}
+Prior to Kubernetes 1.27, this behavior was controlled using the
+`service.kubernetes.io/topology-aware-hints` annotation.
+{{</ note >}}
 
-## How it works {#implementation}
+You can enable Topology Aware Routing for a Service by setting the
+`service.kubernetes.io/topology-mode` annotation to `Auto`. When there are
+enough endpoints available in each zone, Topology Hints will be populated on
+EndpointSlices to allocate individual endpoints to specific zones, resulting in
+traffic being routed closer to where it originated from.
 
-The functionality enabling this feature is split into two components: The
-EndpointSlice controller and the kube-proxy. This section provides a high level overview
-of how each component implements this feature.
+## When it works best
+
+This feature works best when:
+
+### 1. Incoming traffic is evenly distributed
+
+If a large proportion of traffic is originating from a single zone, that traffic
+could overload the subset of endpoints that have been allocated to that zone.
+This feature is not recommended when incoming traffic is expected to originate
+from a single zone.
+
+### 2. The Service has 3 or more endpoints per zone {#three-or-more-endpoints-per-zone}
+In a three zone cluster, this means 9 or more endpoints. If there are fewer than
+3 endpoints per zone, there is a high (≈50%) probability that the EndpointSlice
+controller will not be able to allocate endpoints evenly and instead will fall
+back to the default cluster-wide routing approach.
+
+## How It Works
+
+The "Auto" heuristic attempts to proportionally allocate a number of endpoints
+to each zone. Note that this heuristic works best for Services that have a
+significant number of endpoints.
 
 ### EndpointSlice controller {#implementation-control-plane}
 
 The EndpointSlice controller is responsible for setting hints on EndpointSlices
-when this feature is enabled. The controller allocates a proportional amount of
+when this heuristic is enabled. The controller allocates a proportional amount of
 endpoints to each zone. This proportion is based on the
 [allocatable](/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable)
 CPU cores for nodes running in that zone. For example, if one zone had 2 CPU
@@ -145,6 +168,11 @@ zone.
   proportions of each zone. This could have unintended consequences if a large
   portion of nodes are unready.
 
+* The EndpointSlice controller ignores nodes with the
+  `node-role.kubernetes.io/control-plane` or `node-role.kubernetes.io/master`
+  label set. This could be problematic if workloads are also running on those
+  nodes.
+
 * The EndpointSlice controller does not take into account {{< glossary_tooltip
   text="tolerations" term_id="toleration" >}} when deploying or calculating the
   proportions of each zone. If the Pods backing a Service are limited to a
@@ -157,6 +185,17 @@ zone.
   either not picking up on this event, or newly added pods starting in a
   different zone.
 
+
+## Custom heuristics
+
+Kubernetes is deployed in many different ways, there is no single heuristic for
+allocating endpoints to zones will work for every use case. A key goal of this
+feature is to enable custom heuristics to be developed if the built in heuristic
+does not work for your use case. The first steps to enable custom heuristics
+were included in the 1.27 release. This is a limited implementation that may not
+yet cover some relevant and plausible situations.
+
+
 ## {{% heading "whatsnext" %}}
 
 * Follow the [Connecting Applications with Services](/docs/tutorials/services/connect-applications-service/) tutorial
diff --git a/static/_redirects b/static/_redirects
index f4bd3250907..b720f758cb7 100644
--- a/static/_redirects
+++ b/static/_redirects
@@ -94,6 +94,7 @@
 /docs/concepts/service-catalog/     /docs/concepts/extend-kubernetes/service-catalog/ 301
 /docs/concepts/services-networking/networkpolicies/     /docs/concepts/services-networking/network-policies/ 301
 /docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/     /docs/tasks/network/customize-hosts-file-for-pods/ 301
+/docs/concepts/services-networking/topology-aware-hints/     /docs/concepts/services-networking/topology-aware-routing/ 302
 /docs/concepts/storage/etcd-store-api-object/     /docs/tasks/administer-cluster/configure-upgrade-etcd/ 301
 /docs/concepts/storage/volumes/emptyDirapiVersion/     /docs/concepts/storage/volumes/#emptydir/ 301
 /docs/concepts/tools/kubectl/object-management-overview/     /docs/concepts/overview/object-management-kubectl/overview/ 301

From 738428a02dfd37104349b311d9b0e9a0f80842fd Mon Sep 17 00:00:00 2001
From: Arhell <arhell333@gmail.com>
Date: Tue, 11 Apr 2023 00:40:42 +0300
Subject: [PATCH 156/272] [ru] Fix mismatch in Labels and Selectors concept
 page

---
 .../ru/docs/concepts/overview/working-with-objects/labels.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/ru/docs/concepts/overview/working-with-objects/labels.md b/content/ru/docs/concepts/overview/working-with-objects/labels.md
index 572454f1815..6e1bdb5fbce 100644
--- a/content/ru/docs/concepts/overview/working-with-objects/labels.md
+++ b/content/ru/docs/concepts/overview/working-with-objects/labels.md
@@ -166,7 +166,7 @@ kubectl get pods -l 'environment in (production),tier in (frontend)'
 kubectl get pods -l 'environment in (production, qa)'
 ```
 
-Либо можно воспользоваться исключающим сопоставлением с помощью оператора _exists_:
+Либо можно воспользоваться исключающим сопоставлением с помощью оператора _notin_:
 
 ```shell
 kubectl get pods -l 'environment,environment notin (frontend)'

From 5b7e267207ba8b11e89e145037a1f3d33c92c811 Mon Sep 17 00:00:00 2001
From: Jan Safranek <jsafrane@redhat.com>
Date: Tue, 7 Mar 2023 13:11:13 +0100
Subject: [PATCH 157/272] Add blog for Speed up recursive SELinux label change
 beta
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Co-authored-by: Roman Bednář <rbednar@redhat.com>
Co-authored-by: Jonathan Dobson <dobsonj@gmail.com>
Co-authored-by: Tim Bannister <tim@scalefactory.com>
---
 ...04-18-efficient-selinux-relabeling-beta.md | 120 ++++++++++++++++++
 1 file changed, 120 insertions(+)
 create mode 100644 content/en/blog/_posts/2023-04-18-efficient-selinux-relabeling-beta.md

diff --git a/content/en/blog/_posts/2023-04-18-efficient-selinux-relabeling-beta.md b/content/en/blog/_posts/2023-04-18-efficient-selinux-relabeling-beta.md
new file mode 100644
index 00000000000..d9a3a880640
--- /dev/null
+++ b/content/en/blog/_posts/2023-04-18-efficient-selinux-relabeling-beta.md
@@ -0,0 +1,120 @@
+---
+layout: blog
+title: "Kubernetes 1.27: Efficient SELinux volume relabeling (Beta)"
+date: 2023-04-18T10:00:00-08:00
+slug: kubernetes-1-27-efficient-selinux-relabeling-beta
+---
+
+**Author:** Jan Šafránek (Red Hat)
+
+# The problem
+
+On Linux with Security-Enhanced Linux (SELinux) enabled, it's traditionally
+the container runtime that applies SELinux labels to a Pod and all its volumes.
+Kubernetes only provides the SELinux label from Pod's Security Context fields
+to the container runtime.
+
+The container runtime then recursively changes SELinux label on all files that
+are visible to the Pod's containers. This can be time-consuming if there are
+many files on the volume, especially when the volume is on a remote filesystem.
+
+{{% alert title="Note" color="info" %}}
+If a container uses `subPath` of a volume, only that `subPath` of the whole
+volume is relabeled. This allows two pods that have two different SELinux labels
+to use the same volume, as long as they use different subpaths of it.
+{{% /alert %}}
+
+If a Pod does not have any SELinux label assigned in Kubernetes API, the
+container runtime assigns a unique random one, so a process that potentially
+escapes the container boundary cannot access data of any other container on the
+host. The container runtime still recursively relabels all pod volumes with this
+random SELinux label.
+
+# Improvement using mount options
+
+If a Pod and its volume meet **all** of the following conditions, Kubernetes will
+_mount_ the volume directly with the right SELinux label. Such mount will happen
+in a constant time and the container runtime will not need to recursively
+relabel any files on it.
+
+1. The operating system must support SELinux.
+
+   Without SELinux support detected, kubelet and the container runtime do not
+   do anything with regard to SELinux.
+
+1. The [feature gates](/docs/reference/command-line-tools-reference/feature-gates/)
+   `ReadWriteOncePod` and `SELinuxMountReadWriteOncePod` must be enabled.
+   These feature gates are Beta in Kubernetes 1.27 and Alpha in 1.25.
+
+   With any of these feature gates disabled, SELinux labels will be always
+   applied by the container runtime by a recursive walk through the volume
+   (or its subPaths).
+
+1. The Pod must have at least `seLinuxOptions.level` assigned in its [Pod Security Context](/docs/reference/kubernetes-api/workload-resources/pod-v1/#security-context) or all Pod containers must have it set in their [Security Contexts](/docs/reference/kubernetes-api/workload-resources/pod-v1/#security-context-1).
+   Kubernetes will read the default `user`, `role` and `type` from the operating
+   system defaults (typically `system_u`, `system_r` and `container_t`).
+
+   Without Kubernetes knowing at least the SELinux `level`, the container
+   runtime will assign a random one _after_ the volumes are mounted. The
+   container runtime will still relabel the volumes recursively in that case.
+
+1. The volume must be a Persistent Volume with
+   [Access Mode](/docs/concepts/storage/persistent-volumes/#access-modes)
+   `ReadWriteOncePod`.
+
+   This is a limitation of the initial implementation. As described above,
+   two Pods can have a different SELinux label and still use the same volume,
+   as long as they use a different `subPath` of it. This use case is not
+   possible when the volumes are _mounted_ with the SELinux label, because the
+   whole volume is mounted and most filesystems don't support mounting a single
+   volume multiple times with multiple SELinux labels.
+
+   If running two Pods with two different SELinux contexts and using
+   different `subPaths` of the same volume is necessary in your deployments,
+   please comment in the [KEP](https://github.com/kubernetes/enhancements/issues/1710)
+   issue (or upvote any existing comment - it's best not to duplicate).
+   Such pods may not run when the feature is extended to cover all volume access modes.
+
+1. The volume plugin or the CSI driver responsible for the volume supports
+   mounting with SELinux mount options.
+
+   These in-tree volume plugins support mounting with SELinux mount options:
+   `fc`, `iscsi`, and `rbd`.
+
+   CSI drivers that support mounting with SELinux mount options must announce
+   that in their
+   [CSIDriver](/docs/reference/kubernetes-api/config-and-storage-resources/csi-driver-v1/)
+   instance by setting `seLinuxMount` field.
+
+   Volumes managed by other volume plugins or CSI drivers that don't
+   set `seLinuxMount: true` will be recursively relabelled by the container
+   runtime.
+
+## Mounting with SELinux context
+
+When all aforementioned conditions are met, kubelet will
+pass `-o context=<SELinux label>` mount option to the volume plugin or CSI
+driver. CSI driver vendors must ensure that this mount option is supported
+by their CSI driver and, if necessary, the CSI driver appends other mount
+options that are needed for `-o context` to work.
+
+For example, NFS may need `-o context=<SELinux label>,nosharecache`, so each
+volume mounted from the same NFS server can have a different SELinux label
+value. Similarly, CIFS may need `-o context=<SELinux label>,nosharesock`.
+
+It's up to the CSI driver vendor to test their CSI driver in a SELinux enabled
+environment before setting `seLinuxMount: true` in the CSIDriver instance.
+
+# How can I learn more?
+SELinux in containers: see excellent
+[visual SELinux guide](https://opensource.com/business/13/11/selinux-policy-guide)
+by Daniel J Walsh. Note that the guide is older than Kubernetes, it describes
+*Multi-Category Security* (MCS) mode using virtual machines as an example,
+however, a similar concept is used for containers.
+
+See a series of blog posts for details how exactly SELinux is applied to
+containers by container runtimes:
+* [How SELinux separates containers using Multi-Level Security](https://www.redhat.com/en/blog/how-selinux-separates-containers-using-multi-level-security)
+* [Why you should be using Multi-Category Security for your Linux containers](https://www.redhat.com/en/blog/why-you-should-be-using-multi-category-security-your-linux-containers)
+
+Read the KEP: [Speed up SELinux volume relabeling using mounts](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1710-selinux-relabeling)

From 4a658ee6a3f61240de7d007252d9b2f294367121 Mon Sep 17 00:00:00 2001
From: Aravindh Puthiyaparambil <aravindh@redhat.com>
Date: Mon, 24 Oct 2022 14:52:49 -0700
Subject: [PATCH 158/272] Add blog about Node Log Query alpha

Enhancement:  https://github.com/kubernetes/enhancements/tree/master/keps/sig-windows/2258-node-service-log-viewer
Feature PR: https://github.com/kubernetes/kubernetes/pull/96120
---
 .../_posts/2023-04-21-node-log-query-alpha.md | 78 +++++++++++++++++++
 1 file changed, 78 insertions(+)
 create mode 100644 content/en/blog/_posts/2023-04-21-node-log-query-alpha.md

diff --git a/content/en/blog/_posts/2023-04-21-node-log-query-alpha.md b/content/en/blog/_posts/2023-04-21-node-log-query-alpha.md
new file mode 100644
index 00000000000..5791f865a4f
--- /dev/null
+++ b/content/en/blog/_posts/2023-04-21-node-log-query-alpha.md
@@ -0,0 +1,78 @@
+---
+layout: blog
+title: "Kubernetes 1.27: Query Node Logs Using The Kubelet API"
+date: 2023-04-21
+slug: node-log-query-alpha
+---
+
+**Author:** Aravindh Puthiyaparambil (Red Hat)
+
+Kubernetes 1.27 introduced a new feature called _Node log query_ that allows
+viewing logs of services running on the node.
+
+## What problem does it solve?
+Cluster administrators face issues when debugging malfunctioning services
+running on the node. They usually have to SSH or RDP into the node to view the
+logs of the service to debug the issue. The _Node log query_ feature helps with
+this scenario by allowing the cluster administrator to view the logs using
+_kubectl_. This is especially useful with Windows nodes where you run into the
+issue of the node going to the ready state but containers not coming up due to
+CNI misconfigurations and other issues that are not easily identifiable by
+looking at the Pod status.
+
+## How does it work?
+
+The kubelet already has a _/var/log/_ viewer that is accessible via the node
+proxy endpoint. The feature supplements this endpoint with a shim that shells
+out to `journalctl`, on Linux nodes, and the `Get-WinEvent` cmdlet on Windows
+nodes. It then uses the existing filters provided by the commands to allow
+filtering the logs. The kubelet also uses heuristics to retrieve the logs.
+If the user is not aware if a given system services logs to a file or to the
+native system logger, the heuristics first checks the native operating system
+logger and if that is not available it attempts to retrieve the first logs
+from `/var/log/<servicename>` or `/var/log/<servicename>.log` or
+`/var/log/<servicename>/<servicename>.log`.
+
+On Linux we assume that service logs are available via journald, and that
+`journalctl` is installed. On Windows we assume that service logs are available
+in the application log provider. Also note that fetching node logs is only
+available if you are authorized to do so (in RBAC, that's **get** and
+**create** access to `nodes/proxy`). The privileges that you need to fetch node
+logs also allow elevation-of-privilege attacks, so be careful about how you
+manage them.
+
+## How do I use it?
+
+To use the feature, ensure that the `NodeLogQuery`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is
+enabled for that node, and that the kubelet configuration options
+`enableSystemLogHandler` and `enableSystemLogQuery` are both set to true. You can
+then query the logs from all your nodes or just a subset. Here is an example to
+retrieve the kubelet service logs from a node:
+```shell
+# Fetch kubelet logs from a node named node-1.example
+kubectl get --raw "/api/v1/nodes/node-1.example/proxy/logs/?query=kubelet"
+```
+
+You can further filter the query to narrow down the results:
+```shell
+# Fetch kubelet logs from a node named node-1.example that have the word "error"
+kubectl get --raw "/api/v1/nodes/node-1.example/proxy/logs/?query=kubelet&pattern=error"
+```
+
+You can also fetch files from `/var/log/` on a Linux node:
+```shell
+kubectl get --raw "/api/v1/nodes/<insert-node-name-here>/proxy/logs/?query=/<insert-log-file-name-here>"
+```
+
+You can read the
+[documentation](/docs/concepts/cluster-administration/system-logs/#log-query)
+for all the available options.
+
+## How do I help?
+
+Please use the feature and provide feedback by opening GitHub issues or
+reaching out to us on the
+[#sig-windows](https://kubernetes.slack.com/archives/C0SJ4AFB7) channel on the
+Kubernetes Slack or the SIG Windows
+[mailing list](https://groups.google.com/g/kubernetes-sig-windows).

From b7b35304dd389442b3e211619fa82061225e8cfe Mon Sep 17 00:00:00 2001
From: Chris Henzie <chrishenzie@google.com>
Date: Mon, 6 Mar 2023 10:52:44 -0800
Subject: [PATCH 159/272] Feature blog for ReadWriteOncePod beta graduation

---
 ...20-read-write-once-pod-access-mode-beta.md | 105 ++++++++++++++++++
 1 file changed, 105 insertions(+)
 create mode 100644 content/en/blog/_posts/2023-04-20-read-write-once-pod-access-mode-beta.md

diff --git a/content/en/blog/_posts/2023-04-20-read-write-once-pod-access-mode-beta.md b/content/en/blog/_posts/2023-04-20-read-write-once-pod-access-mode-beta.md
new file mode 100644
index 00000000000..1e3f83d806d
--- /dev/null
+++ b/content/en/blog/_posts/2023-04-20-read-write-once-pod-access-mode-beta.md
@@ -0,0 +1,105 @@
+---
+layout: blog
+title: "Kubernetes 1.27: Single Pod Access Mode for PersistentVolumes Graduates to Beta"
+date: 2023-04-20
+slug: read-write-once-pod-access-mode-beta
+---
+
+**Author:** Chris Henzie (Google)
+
+With the release of Kubernetes v1.27 the ReadWriteOncePod feature has graduated
+to beta. In this blog post, we'll take a closer look at this feature, what it
+does, and how it has evolved in the beta release.
+
+## What is ReadWriteOncePod?
+
+ReadWriteOncePod is a new access mode for
+[PersistentVolumes](/docs/concepts/storage/persistent-volumes/#persistent-volumes) (PVs)
+and [PersistentVolumeClaims](/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims) (PVCs)
+introduced in Kubernetes v1.22. This access mode enables you to restrict volume
+access to a single pod in the cluster, ensuring that only one pod can write to
+the volume at a time. This can be particularly useful for stateful workloads
+that require single-writer access to storage.
+
+For more context on access modes and how ReadWriteOncePod works read
+[What are access modes and why are they important?](/blog/2021/09/13/read-write-once-pod-access-mode-alpha/#what-are-access-modes-and-why-are-they-important)
+in the _Introducing Single Pod Access Mode for PersistentVolumes_ article from 2021.
+
+## Changes in the ReadWriteOncePod beta
+
+The ReadWriteOncePod beta adds support for
+[scheduler preemption](/docs/concepts/scheduling-eviction/pod-priority-preemption/)
+of pods using ReadWriteOncePod PVCs.
+
+Scheduler preemption allows higher-priority pods to preempt lower-priority pods,
+so that they can start running on the same node. With this release, pods using
+ReadWriteOncePod PVCs can also be preempted if a higher-priority pod requires
+the same PVC.
+
+## How can I start using ReadWriteOncePod?
+
+With ReadWriteOncePod now in beta, it will be enabled by default in cluster
+versions v1.27 and beyond.
+
+Note that ReadWriteOncePod is
+[only supported for CSI volumes](/docs/concepts/storage/persistent-volumes/#access-modes).
+Before using this feature you will need to update the following
+[CSI sidecars](https://kubernetes-csi.github.io/docs/sidecar-containers.html)
+to these versions or greater:
+
+- [csi-provisioner:v3.0.0+](https://github.com/kubernetes-csi/external-provisioner/releases/tag/v3.0.0)
+- [csi-attacher:v3.3.0+](https://github.com/kubernetes-csi/external-attacher/releases/tag/v3.3.0)
+- [csi-resizer:v1.3.0+](https://github.com/kubernetes-csi/external-resizer/releases/tag/v1.3.0)
+
+To start using ReadWriteOncePod, create a PVC with the ReadWriteOncePod access mode:
+
+```yaml
+kind: PersistentVolumeClaim
+apiVersion: v1
+metadata:
+  name: single-writer-only
+spec:
+  accessModes:
+  - ReadWriteOncePod # Allow only a single pod to access single-writer-only.
+  resources:
+    requests:
+      storage: 1Gi
+```
+
+If your storage plugin supports
+[dynamic provisioning](/docs/concepts/storage/dynamic-provisioning/),
+new PersistentVolumes will be created with the ReadWriteOncePod access mode applied.
+
+Read [Migrating existing PersistentVolumes](/blog/2021/09/13/read-write-once-pod-access-mode-alpha/#migrating-existing-persistentvolumes)
+for details on migrating existing volumes to use ReadWriteOncePod.
+
+## How can I learn more?
+
+Please see the [alpha blog post](/blog/2021/09/13/read-write-once-pod-access-mode-alpha)
+and [KEP-2485](https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/2485-read-write-once-pod-pv-access-mode/README.md)
+for more details on the ReadWriteOncePod access mode and motivations for CSI spec changes.
+
+## How do I get involved?
+
+The [Kubernetes #csi Slack channel](https://kubernetes.slack.com/messages/csi)
+and any of the standard
+[SIG Storage communication channels](https://github.com/kubernetes/community/blob/master/sig-storage/README.md#contact)
+are great mediums to reach out to the SIG Storage and the CSI teams.
+
+Special thanks to the following people whose thoughtful reviews and feedback helped shape this feature:
+
+* Abdullah Gharaibeh (ahg-g)
+* Aldo Culquicondor (alculquicondor)
+* Antonio Ojea (aojea)
+* David Eads (deads2k)
+* Jan Šafránek (jsafrane)
+* Joe Betz (jpbetz)
+* Kante Yin (kerthcet)
+* Michelle Au (msau42)
+* Tim Bannister (sftim)
+* Xing Yang (xing-yang)
+
+If you’re interested in getting involved with the design and development of CSI
+or any part of the Kubernetes storage system, join the
+[Kubernetes Storage Special Interest Group](https://github.com/kubernetes/community/tree/master/sig-storage) (SIG).
+We’re rapidly growing and always welcome new contributors.

From 9411b28ffbed23e6b94d69806855301fe0b95a1f Mon Sep 17 00:00:00 2001
From: Cailyn <cailyn.s.e@gmail.com>
Date: Tue, 4 Apr 2023 19:45:38 -0400
Subject: [PATCH 160/272] Update
 content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md

Co-authored-by: Nate W. <natew@cncf.io>
---
 .../index.md                                  | 39 -----------
 .../index.md                                  | 64 +++++++++++++++++++
 2 files changed, 64 insertions(+), 39 deletions(-)
 delete mode 100644 content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
 create mode 100644 content/en/blog/_posts/2023-04-25-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md

diff --git a/content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md b/content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
deleted file mode 100644
index 9cfa0d4b9ce..00000000000
--- a/content/en/blog/_posts/2023-04-04-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-layout: blog 
-title: Updates to the Auto-refreshing Official CVE Feed
-date: 2023-04-04
-slug: k8s-cve-feed-beta
----
-
-**Author**: Cailyn Edwards (Shopify)
-
-Since launching the [Auto-refreshing Official CVE feed](/docs/reference/issues-security/official-cve-feed/) as an `alpha`
-feature in the 1.25 release, we have made significant improvements and updates. We are excited to announce the release of the
-`beta` version of the feed. This blog post will outline the changes made, and talk about what is planned for the to expect for 
-the `stable` release.
-
-## Updates
-| **\#** | **Title**                                                                                                    | **Issue**                                                       | **Status**                                                                                                                                                                                                                      |
-| ------ | ------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 1 | Support RSS feeds by generating data in Atom format | [kubernetes/sig-security#77](https://github.com/kubernetes/sig-security/issues/77) | open, addressed by [kubernetes/website#39513](https://github.com/kubernetes/website/pull/39513)|
-| 2 | CVE Feed: Sort Markdown Table from most recent to least recently announced CVE | [kubernetes/sig-security#73](https://github.com/kubernetes/sig-security/issues/73) | open, no PR open |
-| 3 | CVE Feed: Add Prow job link as a metadata field | [kubernetes/sig-security#71](https://github.com/kubernetes/sig-security/issues/71) | open, no PR open |
-| 4 | CVE Feed: Add lastUpdatedAt as a metadata field | [kubernetes/sig-security#72](https://github.com/kubernetes/sig-security/issues/72) | open, addressed by [kubernetes/sig-security#76](https://github.com/kubernetes/sig-security/pull/76) |
-| 5 | CVE Feed: JSON feed should pass jsonfeed spec validator | [kubernetes/webite#36808](https://github.com/kubernetes/website/issues/36808) | open, addressed by [kubernetes/sig-security#76](https://github.com/kubernetes/sig-security/pull/76) |
-| 6 | CVE Feed: Include a timestamp field for each CVE indicating when it was last updated | [kubernetes/sig-security#63](https://github.com/kubernetes/sig-security/issues/63) | open, no PR |
-| 7 | CVE Feed: Sort Markdown Table from most recent to least recently announced CVE | [kubernetes/sig-security#73](https://github.com/kubernetes/sig-security/issues/73) | open, no PR |
-
-## Summary of Changes
-TODO - add details of changes
-
-## What's Next?
-
-In preparation for the graduation of this feature, SIG Security
-is still gathering feedback from end users who are using the updated beta feed.
-
-To help us continue to improve the feed in future Kubernetes Releases please share feedback by adding a comment to
-this [tracking issue](https://github.com/kubernetes/sig-security/issues/1) or
-let us know on
-[#sig-security-tooling](https://kubernetes.slack.com/archives/C01CUSVMHPY)
-Kubernetes Slack channel.
-(Join [Kubernetes Slack here](https://slack.k8s.io))
\ No newline at end of file
diff --git a/content/en/blog/_posts/2023-04-25-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md b/content/en/blog/_posts/2023-04-25-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
new file mode 100644
index 00000000000..846369d082d
--- /dev/null
+++ b/content/en/blog/_posts/2023-04-25-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md
@@ -0,0 +1,64 @@
+---
+layout: blog
+title: Updates to the Auto-refreshing Official CVE Feed
+date: 2023-04-25
+slug: k8s-cve-feed-beta
+---
+
+**Authors**: Cailyn Edwards (Shopify), Mahé Tardy (Isovalent), Pushkar Joglekar
+
+Since launching the [Auto-refreshing Official CVE feed](/docs/reference/issues-security/official-cve-feed/) as an alpha
+feature in the 1.25 release, we have made significant improvements and updates. We are excited to announce the release of the
+beta version of the feed. This blog post will outline the feedback received, the changes made, and talk about how you can help 
+as we prepare to make this a stable feature in a future Kubernetes Release.
+
+
+## Feedback from end-users
+
+SIG Security received some feedback from end-users:
+- The JSON CVE Feed [did not comply](https://github.com/kubernetes/website/issues/36808)
+  with the [JSON Feed specification](https://www.jsonfeed.org/) as its name would suggest.
+- The feed could also [support RSS](https://github.com/kubernetes/sig-security/issues/77)
+  in addition to JSON Feed format.
+- Some metadata could be [added](https://github.com/kubernetes/sig-security/issues/72) to indicate the freshness of
+  the feed overall, or [specific CVEs](https://github.com/kubernetes/sig-security/issues/63). Another suggestion was 
+  to [indicate](https://github.com/kubernetes/sig-security/issues/71) which Prow job recently updated the feed. See 
+  more ideas directly on the [the umbrella issue](https://github.com/kubernetes/sig-security/issues/1).
+- The feed Markdown table on the website [should be ordered](https://github.com/kubernetes/sig-security/issues/73)
+  from the most recent to the least recently announced CVE.
+
+## Summary of changes
+
+In response, the SIG did a [rework of the script generating the JSON feed](https://github.com/kubernetes/sig-security/pull/76)
+to comply with the JSON Feed specification from generation and add a
+`last_updated` root field to indicate overall freshness. This redesign needed a
+[corresponding fix on the Kubernetes website side](https://github.com/kubernetes/website/pull/38579)
+for the CVE feed page to continue to work with the new format.
+
+After that, [RSS feed support](https://github.com/kubernetes/website/pull/39513)
+could be added transparently so that end-users can consume the feed in their
+preferred format.
+
+Overall, the redesign based on the JSON Feed specification, which this time broke
+backward compatibility, will allow updates in the future to address the rest of
+the issue while being more transparent and less disruptive to end-users.
+
+### Updates
+| **Title**                                                                                                    | **Issue**                                                       | **Status**                                                                                                                                                                                                                      |
+| ------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| CVE Feed: JSON feed should pass jsonfeed spec validator | [kubernetes/webite#36808](https://github.com/kubernetes/website/issues/36808) | closed, addressed by [kubernetes/sig-security#76](https://github.com/kubernetes/sig-security/pull/76) |
+| CVE Feed: Add lastUpdatedAt as a metadata field | [kubernetes/sig-security#72](https://github.com/kubernetes/sig-security/issues/72) | closed, addressed by [kubernetes/sig-security#76](https://github.com/kubernetes/sig-security/pull/76) |
+| Support RSS feeds by generating data in Atom format | [kubernetes/sig-security#77](https://github.com/kubernetes/sig-security/issues/77) | closed, addressed by [kubernetes/website#39513](https://github.com/kubernetes/website/pull/39513)|
+| CVE Feed: Sort Markdown Table from most recent to least recently announced CVE | [kubernetes/sig-security#73](https://github.com/kubernetes/sig-security/issues/73) | closed, addressed by [kubernetes/sig-security#76](https://github.com/kubernetes/sig-security/pull/76) |
+| CVE Feed: Include a timestamp field for each CVE indicating when it was last updated | [kubernetes/sig-security#63](https://github.com/kubernetes/sig-security/issues/63) | closed, addressed by [kubernetes/sig-security#76](https://github.com/kubernetes/sig-security/pull/76) |
+| CVE Feed: Add Prow job link as a metadata field | [kubernetes/sig-security#71](https://github.com/kubernetes/sig-security/issues/71) | closed, addressed by [kubernetes/sig-security#83](https://github.com/kubernetes/sig-security/pull/83) |
+
+## What's next?
+
+In preparation to [graduate](https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/#feature-stages) the feed 
+to stable i.e. `General Availability` stage, SIG Security is still gathering feedback from end users who are using the updated beta feed.
+
+To help us continue to improve the feed in future Kubernetes Releases please share feedback by adding a comment to
+this [tracking issue](https://github.com/kubernetes/sig-security/issues/1) or
+let us know on [#sig-security-tooling](https://kubernetes.slack.com/archives/C01CUSVMHPY)
+Kubernetes Slack channel, join [Kubernetes Slack here](https://slack.k8s.io).
\ No newline at end of file

From 9d1d924691641fb981eae98797b8f6eb35f7bc0a Mon Sep 17 00:00:00 2001
From: Arhell <arhell333@gmail.com>
Date: Wed, 12 Apr 2023 00:45:27 +0300
Subject: [PATCH 161/272] [ja] Fix mismatch in Labels and Selectors concept
 page

---
 .../ja/docs/concepts/overview/working-with-objects/labels.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/ja/docs/concepts/overview/working-with-objects/labels.md b/content/ja/docs/concepts/overview/working-with-objects/labels.md
index fbe8432b453..0af7384a6ad 100644
--- a/content/ja/docs/concepts/overview/working-with-objects/labels.md
+++ b/content/ja/docs/concepts/overview/working-with-objects/labels.md
@@ -192,7 +192,7 @@ kubectl get pods -l 'environment in (production),tier in (frontend)'
 kubectl get pods -l 'environment in (production, qa)'
 ```
 
-もしくは、_exists_ オペレーターを介して、否定マッチングによる制限もできます。  
+もしくは、_notin_ オペレーターを介して、否定マッチングによる制限もできます。  
 
 ```shell
 kubectl get pods -l 'environment,environment notin (frontend)'

From 944de8f44e699819765e07321d8dc116fff0479d Mon Sep 17 00:00:00 2001
From: Qiming Teng <tengqm@outlook.com>
Date: Wed, 12 Apr 2023 08:05:58 +0800
Subject: [PATCH 162/272] Update configuration API reference for v1.27

---
 content/en/docs/reference/_index.md           |    1 -
 .../config-api/apiserver-admission.v1.md      |   12 +-
 .../config-api/apiserver-audit.v1.md          |   16 +-
 .../config-api/apiserver-config.v1alpha1.md   |   63 +-
 .../config-api/apiserver-config.v1beta1.md    |   71 +-
 .../config-api/apiserver-encryption.v1.md     |   50 +-
 .../config-api/client-authentication.v1.md    |    2 +-
 .../client-authentication.v1beta1.md          |    2 +-
 .../config-api/imagepolicy.v1alpha1.md        |    2 +-
 ...kube-controller-manager-config.v1alpha1.md |  627 ++++----
 .../config-api/kube-proxy-config.v1alpha1.md  |   10 +-
 .../config-api/kube-scheduler-config.v1.md    |   18 +-
 .../kube-scheduler-config.v1beta2.md          |   14 +-
 .../kube-scheduler-config.v1beta3.md          |   14 +-
 .../config-api/kubeadm-config.v1beta2.md      | 1311 -----------------
 .../config-api/kubeadm-config.v1beta3.md      |  215 +--
 .../reference/config-api/kubelet-config.v1.md |  209 +--
 .../config-api/kubelet-config.v1alpha1.md     |    4 +-
 .../config-api/kubelet-config.v1beta1.md      |   72 +-
 19 files changed, 732 insertions(+), 1981 deletions(-)
 delete mode 100644 content/en/docs/reference/config-api/kubeadm-config.v1beta2.md

diff --git a/content/en/docs/reference/_index.md b/content/en/docs/reference/_index.md
index 960881e77f0..7fa6d578fde 100644
--- a/content/en/docs/reference/_index.md
+++ b/content/en/docs/reference/_index.md
@@ -100,7 +100,6 @@ operator to use or manage a cluster.
 
 ## Config API for kubeadm
 
-* [v1beta2](/docs/reference/config-api/kubeadm-config.v1beta2/)
 * [v1beta3](/docs/reference/config-api/kubeadm-config.v1beta3/)
 
 ## Design Docs
diff --git a/content/en/docs/reference/config-api/apiserver-admission.v1.md b/content/en/docs/reference/config-api/apiserver-admission.v1.md
index a4c70ac9f0f..946b011e771 100644
--- a/content/en/docs/reference/config-api/apiserver-admission.v1.md
+++ b/content/en/docs/reference/config-api/apiserver-admission.v1.md
@@ -72,14 +72,14 @@ It is suitable for correlating log entries between the webhook and apiserver, fo
 </td>
 </tr>
 <tr><td><code>kind</code> <B>[Required]</B><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#groupversionkind-v1-meta"><code>meta/v1.GroupVersionKind</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#groupversionkind-v1-meta"><code>meta/v1.GroupVersionKind</code></a>
 </td>
 <td>
    <p>Kind is the fully-qualified type of object being submitted (for example, v1.Pod or autoscaling.v1.Scale)</p>
 </td>
 </tr>
 <tr><td><code>resource</code> <B>[Required]</B><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#groupversionresource-v1-meta"><code>meta/v1.GroupVersionResource</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#groupversionresource-v1-meta"><code>meta/v1.GroupVersionResource</code></a>
 </td>
 <td>
    <p>Resource is the fully-qualified resource being requested (for example, v1.pods)</p>
@@ -93,7 +93,7 @@ It is suitable for correlating log entries between the webhook and apiserver, fo
 </td>
 </tr>
 <tr><td><code>requestKind</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#groupversionkind-v1-meta"><code>meta/v1.GroupVersionKind</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#groupversionkind-v1-meta"><code>meta/v1.GroupVersionKind</code></a>
 </td>
 <td>
    <p>RequestKind is the fully-qualified type of the original API request (for example, v1.Pod or autoscaling.v1.Scale).
@@ -107,7 +107,7 @@ and <code>requestKind: {group:&quot;apps&quot;, version:&quot;v1beta1&quot;, kin
 </td>
 </tr>
 <tr><td><code>requestResource</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#groupversionresource-v1-meta"><code>meta/v1.GroupVersionResource</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#groupversionresource-v1-meta"><code>meta/v1.GroupVersionResource</code></a>
 </td>
 <td>
    <p>RequestResource is the fully-qualified resource of the original API request (for example, v1.pods).
@@ -153,7 +153,7 @@ requested. e.g. a patch can result in either a CREATE or UPDATE Operation.</p>
 </td>
 </tr>
 <tr><td><code>userInfo</code> <B>[Required]</B><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#userinfo-v1-authentication"><code>authentication/v1.UserInfo</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#userinfo-v1-authentication"><code>authentication/v1.UserInfo</code></a>
 </td>
 <td>
    <p>UserInfo is information about the requesting user</p>
@@ -227,7 +227,7 @@ This must be copied over from the corresponding AdmissionRequest.</p>
 </td>
 </tr>
 <tr><td><code>status</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#status-v1-meta"><code>meta/v1.Status</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#status-v1-meta"><code>meta/v1.Status</code></a>
 </td>
 <td>
    <p>Result contains extra details into why an admission request was denied.
diff --git a/content/en/docs/reference/config-api/apiserver-audit.v1.md b/content/en/docs/reference/config-api/apiserver-audit.v1.md
index ffef0b7f2b0..e89270a91a3 100644
--- a/content/en/docs/reference/config-api/apiserver-audit.v1.md
+++ b/content/en/docs/reference/config-api/apiserver-audit.v1.md
@@ -72,14 +72,14 @@ For non-resource requests, this is the lower-cased HTTP method.</p>
 </td>
 </tr>
 <tr><td><code>user</code> <B>[Required]</B><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#userinfo-v1-authentication"><code>authentication/v1.UserInfo</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#userinfo-v1-authentication"><code>authentication/v1.UserInfo</code></a>
 </td>
 <td>
    <p>Authenticated user information.</p>
 </td>
 </tr>
 <tr><td><code>impersonatedUser</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#userinfo-v1-authentication"><code>authentication/v1.UserInfo</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#userinfo-v1-authentication"><code>authentication/v1.UserInfo</code></a>
 </td>
 <td>
    <p>Impersonated user information.</p>
@@ -117,7 +117,7 @@ Does not apply for List-type requests, or non-resource requests.</p>
 </td>
 </tr>
 <tr><td><code>responseStatus</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#status-v1-meta"><code>meta/v1.Status</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#status-v1-meta"><code>meta/v1.Status</code></a>
 </td>
 <td>
    <p>The response status, populated even when the ResponseObject is not a Status type.
@@ -145,14 +145,14 @@ at Response Level.</p>
 </td>
 </tr>
 <tr><td><code>requestReceivedTimestamp</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#microtime-v1-meta"><code>meta/v1.MicroTime</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#microtime-v1-meta"><code>meta/v1.MicroTime</code></a>
 </td>
 <td>
    <p>Time the request reached the apiserver.</p>
 </td>
 </tr>
 <tr><td><code>stageTimestamp</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#microtime-v1-meta"><code>meta/v1.MicroTime</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#microtime-v1-meta"><code>meta/v1.MicroTime</code></a>
 </td>
 <td>
    <p>Time the request reached current audit stage.</p>
@@ -189,7 +189,7 @@ should be short. Annotations are included in the Metadata level.</p>
     
   
 <tr><td><code>metadata</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta"><code>meta/v1.ListMeta</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#listmeta-v1-meta"><code>meta/v1.ListMeta</code></a>
 </td>
 <td>
    <span class="text-muted">No description provided.</span></td>
@@ -224,7 +224,7 @@ categories are logged.</p>
     
   
 <tr><td><code>metadata</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta"><code>meta/v1.ObjectMeta</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#objectmeta-v1-meta"><code>meta/v1.ObjectMeta</code></a>
 </td>
 <td>
    <p>ObjectMeta is included for interoperability with API infrastructure.</p>
@@ -279,7 +279,7 @@ in a rule will override the global default.</p>
     
   
 <tr><td><code>metadata</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta"><code>meta/v1.ListMeta</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#listmeta-v1-meta"><code>meta/v1.ListMeta</code></a>
 </td>
 <td>
    <span class="text-muted">No description provided.</span></td>
diff --git a/content/en/docs/reference/config-api/apiserver-config.v1alpha1.md b/content/en/docs/reference/config-api/apiserver-config.v1alpha1.md
index f2dc0bf5950..0c85b397f61 100644
--- a/content/en/docs/reference/config-api/apiserver-config.v1alpha1.md
+++ b/content/en/docs/reference/config-api/apiserver-config.v1alpha1.md
@@ -81,23 +81,11 @@ auto_generated: true
 <tr><td><code>kind</code><br/>string</td><td><code>TracingConfiguration</code></td></tr>
     
   
-<tr><td><code>endpoint</code><br/>
-<code>string</code>
+<tr><td><code>TracingConfiguration</code> <B>[Required]</B><br/>
+<a href="#TracingConfiguration"><code>TracingConfiguration</code></a>
 </td>
-<td>
-   <p>Endpoint of the collector that's running on the control-plane node.
-The APIServer uses the egressType ControlPlane when sending data to the collector.
-The syntax is defined in https://github.com/grpc/grpc/blob/master/doc/naming.md.
-Defaults to the otlpgrpc default, localhost:4317
-The connection is insecure, and does not support TLS.</p>
-</td>
-</tr>
-<tr><td><code>samplingRatePerMillion</code><br/>
-<code>int32</code>
-</td>
-<td>
-   <p>SamplingRatePerMillion is the number of samples to collect per million spans.
-Defaults to 0.</p>
+<td>(Members of <code>TracingConfiguration</code> are embedded into this type.)
+   <p>Embed the component config tracing configuration struct</p>
 </td>
 </tr>
 </tbody>
@@ -372,4 +360,45 @@ This does not use a unix:// prefix. (Eg: /etc/srv/kubernetes/konnectivity-server
 </tr>
 </tbody>
 </table>
-  
\ No newline at end of file
+  
+  
+    
+
+## `TracingConfiguration`     {#TracingConfiguration}
+    
+
+**Appears in:**
+
+- [KubeletConfiguration](#kubelet-config-k8s-io-v1beta1-KubeletConfiguration)
+
+- [TracingConfiguration](#apiserver-k8s-io-v1alpha1-TracingConfiguration)
+
+
+<p>TracingConfiguration provides versioned configuration for OpenTelemetry tracing clients.</p>
+
+
+<table class="table">
+<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
+<tbody>
+    
+  
+<tr><td><code>endpoint</code><br/>
+<code>string</code>
+</td>
+<td>
+   <p>Endpoint of the collector this component will report traces to.
+The connection is insecure, and does not currently support TLS.
+Recommended is unset, and endpoint is the otlp grpc default, localhost:4317.</p>
+</td>
+</tr>
+<tr><td><code>samplingRatePerMillion</code><br/>
+<code>int32</code>
+</td>
+<td>
+   <p>SamplingRatePerMillion is the number of samples to collect per million spans.
+Recommended is unset. If unset, sampler respects its parent span's sampling
+rate, but otherwise never samples.</p>
+</td>
+</tr>
+</tbody>
+</table>
\ No newline at end of file
diff --git a/content/en/docs/reference/config-api/apiserver-config.v1beta1.md b/content/en/docs/reference/config-api/apiserver-config.v1beta1.md
index 0ed8e17a44d..6acb3540cd0 100644
--- a/content/en/docs/reference/config-api/apiserver-config.v1beta1.md
+++ b/content/en/docs/reference/config-api/apiserver-config.v1beta1.md
@@ -11,6 +11,7 @@ auto_generated: true
 
 
 - [EgressSelectorConfiguration](#apiserver-k8s-io-v1beta1-EgressSelectorConfiguration)
+- [TracingConfiguration](#apiserver-k8s-io-v1beta1-TracingConfiguration)
   
     
 
@@ -39,6 +40,31 @@ auto_generated: true
 </tbody>
 </table>
 
+## `TracingConfiguration`     {#apiserver-k8s-io-v1beta1-TracingConfiguration}
+    
+
+
+<p>TracingConfiguration provides versioned configuration for tracing clients.</p>
+
+
+<table class="table">
+<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
+<tbody>
+    
+<tr><td><code>apiVersion</code><br/>string</td><td><code>apiserver.k8s.io/v1beta1</code></td></tr>
+<tr><td><code>kind</code><br/>string</td><td><code>TracingConfiguration</code></td></tr>
+    
+  
+<tr><td><code>TracingConfiguration</code> <B>[Required]</B><br/>
+<a href="#TracingConfiguration"><code>TracingConfiguration</code></a>
+</td>
+<td>(Members of <code>TracingConfiguration</code> are embedded into this type.)
+   <p>Embed the component config tracing configuration struct</p>
+</td>
+</tr>
+</tbody>
+</table>
+
 ## `Connection`     {#apiserver-k8s-io-v1beta1-Connection}
     
 
@@ -265,4 +291,47 @@ This does not use a unix:// prefix. (Eg: /etc/srv/kubernetes/konnectivity-server
 </tr>
 </tbody>
 </table>
-  
\ No newline at end of file
+  
+  
+    
+
+## `TracingConfiguration`     {#TracingConfiguration}
+    
+
+**Appears in:**
+
+- [KubeletConfiguration](#kubelet-config-k8s-io-v1beta1-KubeletConfiguration)
+
+- [TracingConfiguration](#apiserver-k8s-io-v1alpha1-TracingConfiguration)
+
+- [TracingConfiguration](#apiserver-k8s-io-v1beta1-TracingConfiguration)
+
+
+<p>TracingConfiguration provides versioned configuration for OpenTelemetry tracing clients.</p>
+
+
+<table class="table">
+<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
+<tbody>
+    
+  
+<tr><td><code>endpoint</code><br/>
+<code>string</code>
+</td>
+<td>
+   <p>Endpoint of the collector this component will report traces to.
+The connection is insecure, and does not currently support TLS.
+Recommended is unset, and endpoint is the otlp grpc default, localhost:4317.</p>
+</td>
+</tr>
+<tr><td><code>samplingRatePerMillion</code><br/>
+<code>int32</code>
+</td>
+<td>
+   <p>SamplingRatePerMillion is the number of samples to collect per million spans.
+Recommended is unset. If unset, sampler respects its parent span's sampling
+rate, but otherwise never samples.</p>
+</td>
+</tr>
+</tbody>
+</table>
\ No newline at end of file
diff --git a/content/en/docs/reference/config-api/apiserver-encryption.v1.md b/content/en/docs/reference/config-api/apiserver-encryption.v1.md
index bd12284f306..ecc82b7db7c 100644
--- a/content/en/docs/reference/config-api/apiserver-encryption.v1.md
+++ b/content/en/docs/reference/config-api/apiserver-encryption.v1.md
@@ -18,7 +18,45 @@ auto_generated: true
     
 
 
-<p>EncryptionConfiguration stores the complete configuration for encryption providers.</p>
+<p>EncryptionConfiguration stores the complete configuration for encryption providers.
+It also allows the use of wildcards to specify the resources that should be encrypted.
+Use '<em>.<!-- raw HTML omitted -->' to encrypt all resources within a group or '</em>.<em>' to encrypt all resources.
+'</em>.' can be used to encrypt all resource in the core group.  '<em>.</em>' will encrypt all
+resources, even custom resources that are added after API server start.
+Use of wildcards that overlap within the same resource list or across multiple
+entries are not allowed since part of the configuration would be ineffective.
+Resource lists are processed in order, with earlier lists taking precedence.</p>
+<p>Example:</p>
+<pre><code>kind: EncryptionConfiguration
+apiVersion: apiserver.config.k8s.io/v1
+resources:
+- resources:
+  - events
+  providers:
+  - identity: {}  # do not encrypt events even though *.* is specified below
+- resources:
+  - secrets
+  - configmaps
+  - pandas.awesome.bears.example
+  providers:
+  - aescbc:
+      keys:
+      - name: key1
+        secret: c2VjcmV0IGlzIHNlY3VyZQ==
+- resources:
+  - '*.apps'
+  providers:
+  - aescbc:
+      keys:
+      - name: key2
+        secret: c2VjcmV0IGlzIHNlY3VyZSwgb3IgaXMgaXQ/Cg==
+- resources:
+  - '*.*'
+  providers:
+  - aescbc:
+      keys:
+      - name: key3
+        secret: c2VjcmV0IGlzIHNlY3VyZSwgSSB0aGluaw==</code></pre>
 
 
 <table class="table">
@@ -114,7 +152,7 @@ Each key has to be 32 bytes long for AES-CBC and 16, 24 or 32 bytes for AES-GCM.
 </td>
 <td>
    <p>cachesize is the maximum number of secrets which are cached in memory. The default value is 1000.
-Set to a negative value to disable caching.</p>
+Set to a negative value to disable caching. This field is only allowed for KMS v1 providers.</p>
 </td>
 </tr>
 <tr><td><code>endpoint</code> <B>[Required]</B><br/>
@@ -243,7 +281,11 @@ Set to a negative value to disable caching.</p>
 <code>[]string</code>
 </td>
 <td>
-   <p>resources is a list of kubernetes resources which have to be encrypted.</p>
+   <p>resources is a list of kubernetes resources which have to be encrypted. The resource names are derived from <code>resource</code> or <code>resource.group</code> of the group/version/resource.
+eg: pandas.awesome.bears.example is a custom resource with 'group': awesome.bears.example, 'resource': pandas.
+Use '<em>.</em>' to encrypt all resources and '<em>.<!-- raw HTML omitted -->' to encrypt all resources in a specific group.
+eg: '</em>.awesome.bears.example' will encrypt all resources in the group 'awesome.bears.example'.
+eg: '*.' will encrypt all resources in the core group (such as pods, configmaps, etc).</p>
 </td>
 </tr>
 <tr><td><code>providers</code> <B>[Required]</B><br/>
@@ -251,7 +293,7 @@ Set to a negative value to disable caching.</p>
 </td>
 <td>
    <p>providers is a list of transformers to be used for reading and writing the resources to disk.
-eg: aesgcm, aescbc, secretbox, identity.</p>
+eg: aesgcm, aescbc, secretbox, identity, kms.</p>
 </td>
 </tr>
 </tbody>
diff --git a/content/en/docs/reference/config-api/client-authentication.v1.md b/content/en/docs/reference/config-api/client-authentication.v1.md
index 0a3fab1a5c4..63bbeb00176 100644
--- a/content/en/docs/reference/config-api/client-authentication.v1.md
+++ b/content/en/docs/reference/config-api/client-authentication.v1.md
@@ -206,7 +206,7 @@ itself should at least be protected via file permissions.</p>
     
   
 <tr><td><code>expirationTimestamp</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta"><code>meta/v1.Time</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#time-v1-meta"><code>meta/v1.Time</code></a>
 </td>
 <td>
    <p>ExpirationTimestamp indicates a time when the provided credentials expire.</p>
diff --git a/content/en/docs/reference/config-api/client-authentication.v1beta1.md b/content/en/docs/reference/config-api/client-authentication.v1beta1.md
index 09aa4dcc875..f8cab963cdd 100644
--- a/content/en/docs/reference/config-api/client-authentication.v1beta1.md
+++ b/content/en/docs/reference/config-api/client-authentication.v1beta1.md
@@ -206,7 +206,7 @@ itself should at least be protected via file permissions.</p>
     
   
 <tr><td><code>expirationTimestamp</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta"><code>meta/v1.Time</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#time-v1-meta"><code>meta/v1.Time</code></a>
 </td>
 <td>
    <p>ExpirationTimestamp indicates a time when the provided credentials expire.</p>
diff --git a/content/en/docs/reference/config-api/imagepolicy.v1alpha1.md b/content/en/docs/reference/config-api/imagepolicy.v1alpha1.md
index 0eaa8f14ade..fb55f9a06b5 100644
--- a/content/en/docs/reference/config-api/imagepolicy.v1alpha1.md
+++ b/content/en/docs/reference/config-api/imagepolicy.v1alpha1.md
@@ -29,7 +29,7 @@ auto_generated: true
     
   
 <tr><td><code>metadata</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta"><code>meta/v1.ObjectMeta</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#objectmeta-v1-meta"><code>meta/v1.ObjectMeta</code></a>
 </td>
 <td>
    <p>Standard object's metadata.
diff --git a/content/en/docs/reference/config-api/kube-controller-manager-config.v1alpha1.md b/content/en/docs/reference/config-api/kube-controller-manager-config.v1alpha1.md
index 4ec29226a5d..1b4b120abd0 100644
--- a/content/en/docs/reference/config-api/kube-controller-manager-config.v1alpha1.md
+++ b/content/en/docs/reference/config-api/kube-controller-manager-config.v1alpha1.md
@@ -1,7 +1,7 @@
 ---
 title: kube-controller-manager Configuration (v1alpha1)
 content_type: tool-reference
-package: controllermanager.config.k8s.io/v1alpha1
+package: cloudcontrollermanager.config.k8s.io/v1alpha1
 auto_generated: true
 ---
 
@@ -9,11 +9,358 @@ auto_generated: true
 ## Resource Types 
 
 
-- [KubeControllerManagerConfiguration](#kubecontrollermanager-config-k8s-io-v1alpha1-KubeControllerManagerConfiguration)
 - [CloudControllerManagerConfiguration](#cloudcontrollermanager-config-k8s-io-v1alpha1-CloudControllerManagerConfiguration)
+- [LeaderMigrationConfiguration](#controllermanager-config-k8s-io-v1alpha1-LeaderMigrationConfiguration)
+- [KubeControllerManagerConfiguration](#kubecontrollermanager-config-k8s-io-v1alpha1-KubeControllerManagerConfiguration)
   
     
 
+## `NodeControllerConfiguration`     {#NodeControllerConfiguration}
+    
+
+**Appears in:**
+
+- [CloudControllerManagerConfiguration](#cloudcontrollermanager-config-k8s-io-v1alpha1-CloudControllerManagerConfiguration)
+
+
+<p>NodeControllerConfiguration contains elements describing NodeController.</p>
+
+
+<table class="table">
+<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
+<tbody>
+    
+  
+<tr><td><code>ConcurrentNodeSyncs</code> <B>[Required]</B><br/>
+<code>int32</code>
+</td>
+<td>
+   <p>ConcurrentNodeSyncs is the number of workers
+concurrently synchronizing nodes</p>
+</td>
+</tr>
+</tbody>
+</table>
+
+## `ServiceControllerConfiguration`     {#ServiceControllerConfiguration}
+    
+
+**Appears in:**
+
+- [CloudControllerManagerConfiguration](#cloudcontrollermanager-config-k8s-io-v1alpha1-CloudControllerManagerConfiguration)
+
+- [KubeControllerManagerConfiguration](#kubecontrollermanager-config-k8s-io-v1alpha1-KubeControllerManagerConfiguration)
+
+
+<p>ServiceControllerConfiguration contains elements describing ServiceController.</p>
+
+
+<table class="table">
+<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
+<tbody>
+    
+  
+<tr><td><code>ConcurrentServiceSyncs</code> <B>[Required]</B><br/>
+<code>int32</code>
+</td>
+<td>
+   <p>concurrentServiceSyncs is the number of services that are
+allowed to sync concurrently. Larger number = more responsive service
+management, but more CPU (and network) load.</p>
+</td>
+</tr>
+</tbody>
+</table>
+  
+    
+
+## `CloudControllerManagerConfiguration`     {#cloudcontrollermanager-config-k8s-io-v1alpha1-CloudControllerManagerConfiguration}
+    
+
+
+<p>CloudControllerManagerConfiguration contains elements describing cloud-controller manager.</p>
+
+
+<table class="table">
+<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
+<tbody>
+    
+<tr><td><code>apiVersion</code><br/>string</td><td><code>cloudcontrollermanager.config.k8s.io/v1alpha1</code></td></tr>
+<tr><td><code>kind</code><br/>string</td><td><code>CloudControllerManagerConfiguration</code></td></tr>
+    
+  
+<tr><td><code>Generic</code> <B>[Required]</B><br/>
+<a href="#controllermanager-config-k8s-io-v1alpha1-GenericControllerManagerConfiguration"><code>GenericControllerManagerConfiguration</code></a>
+</td>
+<td>
+   <p>Generic holds configuration for a generic controller-manager</p>
+</td>
+</tr>
+<tr><td><code>KubeCloudShared</code> <B>[Required]</B><br/>
+<a href="#cloudcontrollermanager-config-k8s-io-v1alpha1-KubeCloudSharedConfiguration"><code>KubeCloudSharedConfiguration</code></a>
+</td>
+<td>
+   <p>KubeCloudSharedConfiguration holds configuration for shared related features
+both in cloud controller manager and kube-controller manager.</p>
+</td>
+</tr>
+<tr><td><code>NodeController</code> <B>[Required]</B><br/>
+<a href="#NodeControllerConfiguration"><code>NodeControllerConfiguration</code></a>
+</td>
+<td>
+   <p>NodeController holds configuration for node controller
+related features.</p>
+</td>
+</tr>
+<tr><td><code>ServiceController</code> <B>[Required]</B><br/>
+<a href="#ServiceControllerConfiguration"><code>ServiceControllerConfiguration</code></a>
+</td>
+<td>
+   <p>ServiceControllerConfiguration holds configuration for ServiceController
+related features.</p>
+</td>
+</tr>
+<tr><td><code>NodeStatusUpdateFrequency</code> <B>[Required]</B><br/>
+<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
+</td>
+<td>
+   <p>NodeStatusUpdateFrequency is the frequency at which the controller updates nodes' status</p>
+</td>
+</tr>
+<tr><td><code>Webhook</code> <B>[Required]</B><br/>
+<a href="#cloudcontrollermanager-config-k8s-io-v1alpha1-WebhookConfiguration"><code>WebhookConfiguration</code></a>
+</td>
+<td>
+   <p>Webhook is the configuration for cloud-controller-manager hosted webhooks</p>
+</td>
+</tr>
+</tbody>
+</table>
+
+## `CloudProviderConfiguration`     {#cloudcontrollermanager-config-k8s-io-v1alpha1-CloudProviderConfiguration}
+    
+
+**Appears in:**
+
+- [KubeCloudSharedConfiguration](#cloudcontrollermanager-config-k8s-io-v1alpha1-KubeCloudSharedConfiguration)
+
+
+<p>CloudProviderConfiguration contains basically elements about cloud provider.</p>
+
+
+<table class="table">
+<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
+<tbody>
+    
+  
+<tr><td><code>Name</code> <B>[Required]</B><br/>
+<code>string</code>
+</td>
+<td>
+   <p>Name is the provider for cloud services.</p>
+</td>
+</tr>
+<tr><td><code>CloudConfigFile</code> <B>[Required]</B><br/>
+<code>string</code>
+</td>
+<td>
+   <p>cloudConfigFile is the path to the cloud provider configuration file.</p>
+</td>
+</tr>
+</tbody>
+</table>
+
+## `KubeCloudSharedConfiguration`     {#cloudcontrollermanager-config-k8s-io-v1alpha1-KubeCloudSharedConfiguration}
+    
+
+**Appears in:**
+
+- [CloudControllerManagerConfiguration](#cloudcontrollermanager-config-k8s-io-v1alpha1-CloudControllerManagerConfiguration)
+
+- [KubeControllerManagerConfiguration](#kubecontrollermanager-config-k8s-io-v1alpha1-KubeControllerManagerConfiguration)
+
+
+<p>KubeCloudSharedConfiguration contains elements shared by both kube-controller manager
+and cloud-controller manager, but not genericconfig.</p>
+
+
+<table class="table">
+<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
+<tbody>
+    
+  
+<tr><td><code>CloudProvider</code> <B>[Required]</B><br/>
+<a href="#cloudcontrollermanager-config-k8s-io-v1alpha1-CloudProviderConfiguration"><code>CloudProviderConfiguration</code></a>
+</td>
+<td>
+   <p>CloudProviderConfiguration holds configuration for CloudProvider related features.</p>
+</td>
+</tr>
+<tr><td><code>ExternalCloudVolumePlugin</code> <B>[Required]</B><br/>
+<code>string</code>
+</td>
+<td>
+   <p>externalCloudVolumePlugin specifies the plugin to use when cloudProvider is &quot;external&quot;.
+It is currently used by the in repo cloud providers to handle node and volume control in the KCM.</p>
+</td>
+</tr>
+<tr><td><code>UseServiceAccountCredentials</code> <B>[Required]</B><br/>
+<code>bool</code>
+</td>
+<td>
+   <p>useServiceAccountCredentials indicates whether controllers should be run with
+individual service account credentials.</p>
+</td>
+</tr>
+<tr><td><code>AllowUntaggedCloud</code> <B>[Required]</B><br/>
+<code>bool</code>
+</td>
+<td>
+   <p>run with untagged cloud instances</p>
+</td>
+</tr>
+<tr><td><code>RouteReconciliationPeriod</code> <B>[Required]</B><br/>
+<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
+</td>
+<td>
+   <p>routeReconciliationPeriod is the period for reconciling routes created for Nodes by cloud provider..</p>
+</td>
+</tr>
+<tr><td><code>NodeMonitorPeriod</code> <B>[Required]</B><br/>
+<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
+</td>
+<td>
+   <p>nodeMonitorPeriod is the period for syncing NodeStatus in NodeController.</p>
+</td>
+</tr>
+<tr><td><code>ClusterName</code> <B>[Required]</B><br/>
+<code>string</code>
+</td>
+<td>
+   <p>clusterName is the instance prefix for the cluster.</p>
+</td>
+</tr>
+<tr><td><code>ClusterCIDR</code> <B>[Required]</B><br/>
+<code>string</code>
+</td>
+<td>
+   <p>clusterCIDR is CIDR Range for Pods in cluster.</p>
+</td>
+</tr>
+<tr><td><code>AllocateNodeCIDRs</code> <B>[Required]</B><br/>
+<code>bool</code>
+</td>
+<td>
+   <p>AllocateNodeCIDRs enables CIDRs for Pods to be allocated and, if
+ConfigureCloudRoutes is true, to be set on the cloud provider.</p>
+</td>
+</tr>
+<tr><td><code>CIDRAllocatorType</code> <B>[Required]</B><br/>
+<code>string</code>
+</td>
+<td>
+   <p>CIDRAllocatorType determines what kind of pod CIDR allocator will be used.</p>
+</td>
+</tr>
+<tr><td><code>ConfigureCloudRoutes</code> <B>[Required]</B><br/>
+<code>bool</code>
+</td>
+<td>
+   <p>configureCloudRoutes enables CIDRs allocated with allocateNodeCIDRs
+to be configured on the cloud provider.</p>
+</td>
+</tr>
+<tr><td><code>NodeSyncPeriod</code> <B>[Required]</B><br/>
+<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
+</td>
+<td>
+   <p>nodeSyncPeriod is the period for syncing nodes from cloudprovider. Longer
+periods will result in fewer calls to cloud provider, but may delay addition
+of new nodes to cluster.</p>
+</td>
+</tr>
+</tbody>
+</table>
+
+## `WebhookConfiguration`     {#cloudcontrollermanager-config-k8s-io-v1alpha1-WebhookConfiguration}
+    
+
+**Appears in:**
+
+- [CloudControllerManagerConfiguration](#cloudcontrollermanager-config-k8s-io-v1alpha1-CloudControllerManagerConfiguration)
+
+
+<p>WebhookConfiguration contains configuration related to
+cloud-controller-manager hosted webhooks</p>
+
+
+<table class="table">
+<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
+<tbody>
+    
+  
+<tr><td><code>Webhooks</code> <B>[Required]</B><br/>
+<code>[]string</code>
+</td>
+<td>
+   <p>Webhooks is the list of webhooks to enable or disable
+'*' means &quot;all enabled by default webhooks&quot;
+'foo' means &quot;enable 'foo'&quot;
+'-foo' means &quot;disable 'foo'&quot;
+first item for a particular name wins</p>
+</td>
+</tr>
+</tbody>
+</table>
+  
+  
+    
+
+## `LeaderMigrationConfiguration`     {#controllermanager-config-k8s-io-v1alpha1-LeaderMigrationConfiguration}
+    
+
+**Appears in:**
+
+- [GenericControllerManagerConfiguration](#controllermanager-config-k8s-io-v1alpha1-GenericControllerManagerConfiguration)
+
+
+<p>LeaderMigrationConfiguration provides versioned configuration for all migrating leader locks.</p>
+
+
+<table class="table">
+<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
+<tbody>
+    
+<tr><td><code>apiVersion</code><br/>string</td><td><code>controllermanager.config.k8s.io/v1alpha1</code></td></tr>
+<tr><td><code>kind</code><br/>string</td><td><code>LeaderMigrationConfiguration</code></td></tr>
+    
+  
+<tr><td><code>leaderName</code> <B>[Required]</B><br/>
+<code>string</code>
+</td>
+<td>
+   <p>LeaderName is the name of the leader election resource that protects the migration
+E.g. 1-20-KCM-to-1-21-CCM</p>
+</td>
+</tr>
+<tr><td><code>resourceLock</code> <B>[Required]</B><br/>
+<code>string</code>
+</td>
+<td>
+   <p>ResourceLock indicates the resource object type that will be used to lock
+Should be &quot;leases&quot; or &quot;endpoints&quot;</p>
+</td>
+</tr>
+<tr><td><code>controllerLeaders</code> <B>[Required]</B><br/>
+<a href="#controllermanager-config-k8s-io-v1alpha1-ControllerLeaderConfiguration"><code>[]ControllerLeaderConfiguration</code></a>
+</td>
+<td>
+   <p>ControllerLeaders contains a list of migrating leader lock configurations</p>
+</td>
+</tr>
+</tbody>
+</table>
+
 ## `ControllerLeaderConfiguration`     {#controllermanager-config-k8s-io-v1alpha1-ControllerLeaderConfiguration}
     
 
@@ -146,48 +493,6 @@ first item for a particular name wins</p>
 </tr>
 </tbody>
 </table>
-
-## `LeaderMigrationConfiguration`     {#controllermanager-config-k8s-io-v1alpha1-LeaderMigrationConfiguration}
-    
-
-**Appears in:**
-
-- [GenericControllerManagerConfiguration](#controllermanager-config-k8s-io-v1alpha1-GenericControllerManagerConfiguration)
-
-
-<p>LeaderMigrationConfiguration provides versioned configuration for all migrating leader locks.</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>leaderName</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p>LeaderName is the name of the leader election resource that protects the migration
-E.g. 1-20-KCM-to-1-21-CCM</p>
-</td>
-</tr>
-<tr><td><code>resourceLock</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p>ResourceLock indicates the resource object type that will be used to lock
-Should be &quot;leases&quot; or &quot;endpoints&quot;</p>
-</td>
-</tr>
-<tr><td><code>controllerLeaders</code> <B>[Required]</B><br/>
-<a href="#controllermanager-config-k8s-io-v1alpha1-ControllerLeaderConfiguration"><code>[]ControllerLeaderConfiguration</code></a>
-</td>
-<td>
-   <p>ControllerLeaders contains a list of migrating leader lock configurations</p>
-</td>
-</tr>
-</tbody>
-</table>
   
   
     
@@ -1115,14 +1420,6 @@ allowed to sync concurrently.</p>
 <tbody>
     
   
-<tr><td><code>EnableTaintManager</code> <B>[Required]</B><br/>
-<code>bool</code>
-</td>
-<td>
-   <p>If set to true enables NoExecute Taints and will evict all not-tolerating
-Pod running on Nodes tainted with this kind of Taints.</p>
-</td>
-</tr>
 <tr><td><code>NodeEvictionRate</code> <B>[Required]</B><br/>
 <code>float32</code>
 </td>
@@ -1582,230 +1879,4 @@ volume plugin should search for additional third party volume plugins</p>
 </tr>
 </tbody>
 </table>
-  
-  
-    
-
-## `ServiceControllerConfiguration`     {#ServiceControllerConfiguration}
-    
-
-**Appears in:**
-
-- [CloudControllerManagerConfiguration](#cloudcontrollermanager-config-k8s-io-v1alpha1-CloudControllerManagerConfiguration)
-
-- [KubeControllerManagerConfiguration](#kubecontrollermanager-config-k8s-io-v1alpha1-KubeControllerManagerConfiguration)
-
-
-<p>ServiceControllerConfiguration contains elements describing ServiceController.</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>ConcurrentServiceSyncs</code> <B>[Required]</B><br/>
-<code>int32</code>
-</td>
-<td>
-   <p>concurrentServiceSyncs is the number of services that are
-allowed to sync concurrently. Larger number = more responsive service
-management, but more CPU (and network) load.</p>
-</td>
-</tr>
-</tbody>
-</table>
-  
-    
-
-## `CloudControllerManagerConfiguration`     {#cloudcontrollermanager-config-k8s-io-v1alpha1-CloudControllerManagerConfiguration}
-    
-
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-<tr><td><code>apiVersion</code><br/>string</td><td><code>cloudcontrollermanager.config.k8s.io/v1alpha1</code></td></tr>
-<tr><td><code>kind</code><br/>string</td><td><code>CloudControllerManagerConfiguration</code></td></tr>
-    
-  
-<tr><td><code>Generic</code> <B>[Required]</B><br/>
-<a href="#controllermanager-config-k8s-io-v1alpha1-GenericControllerManagerConfiguration"><code>GenericControllerManagerConfiguration</code></a>
-</td>
-<td>
-   <p>Generic holds configuration for a generic controller-manager</p>
-</td>
-</tr>
-<tr><td><code>KubeCloudShared</code> <B>[Required]</B><br/>
-<a href="#cloudcontrollermanager-config-k8s-io-v1alpha1-KubeCloudSharedConfiguration"><code>KubeCloudSharedConfiguration</code></a>
-</td>
-<td>
-   <p>KubeCloudSharedConfiguration holds configuration for shared related features
-both in cloud controller manager and kube-controller manager.</p>
-</td>
-</tr>
-<tr><td><code>ServiceController</code> <B>[Required]</B><br/>
-<a href="#ServiceControllerConfiguration"><code>ServiceControllerConfiguration</code></a>
-</td>
-<td>
-   <p>ServiceControllerConfiguration holds configuration for ServiceController
-related features.</p>
-</td>
-</tr>
-<tr><td><code>NodeStatusUpdateFrequency</code> <B>[Required]</B><br/>
-<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
-</td>
-<td>
-   <p>NodeStatusUpdateFrequency is the frequency at which the controller updates nodes' status</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `CloudProviderConfiguration`     {#cloudcontrollermanager-config-k8s-io-v1alpha1-CloudProviderConfiguration}
-    
-
-**Appears in:**
-
-- [KubeCloudSharedConfiguration](#cloudcontrollermanager-config-k8s-io-v1alpha1-KubeCloudSharedConfiguration)
-
-
-<p>CloudProviderConfiguration contains basically elements about cloud provider.</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>Name</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p>Name is the provider for cloud services.</p>
-</td>
-</tr>
-<tr><td><code>CloudConfigFile</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p>cloudConfigFile is the path to the cloud provider configuration file.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `KubeCloudSharedConfiguration`     {#cloudcontrollermanager-config-k8s-io-v1alpha1-KubeCloudSharedConfiguration}
-    
-
-**Appears in:**
-
-- [CloudControllerManagerConfiguration](#cloudcontrollermanager-config-k8s-io-v1alpha1-CloudControllerManagerConfiguration)
-
-- [KubeControllerManagerConfiguration](#kubecontrollermanager-config-k8s-io-v1alpha1-KubeControllerManagerConfiguration)
-
-
-<p>KubeCloudSharedConfiguration contains elements shared by both kube-controller manager
-and cloud-controller manager, but not genericconfig.</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>CloudProvider</code> <B>[Required]</B><br/>
-<a href="#cloudcontrollermanager-config-k8s-io-v1alpha1-CloudProviderConfiguration"><code>CloudProviderConfiguration</code></a>
-</td>
-<td>
-   <p>CloudProviderConfiguration holds configuration for CloudProvider related features.</p>
-</td>
-</tr>
-<tr><td><code>ExternalCloudVolumePlugin</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p>externalCloudVolumePlugin specifies the plugin to use when cloudProvider is &quot;external&quot;.
-It is currently used by the in repo cloud providers to handle node and volume control in the KCM.</p>
-</td>
-</tr>
-<tr><td><code>UseServiceAccountCredentials</code> <B>[Required]</B><br/>
-<code>bool</code>
-</td>
-<td>
-   <p>useServiceAccountCredentials indicates whether controllers should be run with
-individual service account credentials.</p>
-</td>
-</tr>
-<tr><td><code>AllowUntaggedCloud</code> <B>[Required]</B><br/>
-<code>bool</code>
-</td>
-<td>
-   <p>run with untagged cloud instances</p>
-</td>
-</tr>
-<tr><td><code>RouteReconciliationPeriod</code> <B>[Required]</B><br/>
-<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
-</td>
-<td>
-   <p>routeReconciliationPeriod is the period for reconciling routes created for Nodes by cloud provider..</p>
-</td>
-</tr>
-<tr><td><code>NodeMonitorPeriod</code> <B>[Required]</B><br/>
-<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
-</td>
-<td>
-   <p>nodeMonitorPeriod is the period for syncing NodeStatus in NodeController.</p>
-</td>
-</tr>
-<tr><td><code>ClusterName</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p>clusterName is the instance prefix for the cluster.</p>
-</td>
-</tr>
-<tr><td><code>ClusterCIDR</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p>clusterCIDR is CIDR Range for Pods in cluster.</p>
-</td>
-</tr>
-<tr><td><code>AllocateNodeCIDRs</code> <B>[Required]</B><br/>
-<code>bool</code>
-</td>
-<td>
-   <p>AllocateNodeCIDRs enables CIDRs for Pods to be allocated and, if
-ConfigureCloudRoutes is true, to be set on the cloud provider.</p>
-</td>
-</tr>
-<tr><td><code>CIDRAllocatorType</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p>CIDRAllocatorType determines what kind of pod CIDR allocator will be used.</p>
-</td>
-</tr>
-<tr><td><code>ConfigureCloudRoutes</code> <B>[Required]</B><br/>
-<code>bool</code>
-</td>
-<td>
-   <p>configureCloudRoutes enables CIDRs allocated with allocateNodeCIDRs
-to be configured on the cloud provider.</p>
-</td>
-</tr>
-<tr><td><code>NodeSyncPeriod</code> <B>[Required]</B><br/>
-<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
-</td>
-<td>
-   <p>nodeSyncPeriod is the period for syncing nodes from cloudprovider. Longer
-periods will result in fewer calls to cloud provider, but may delay addition
-of new nodes to cluster.</p>
-</td>
-</tr>
-</tbody>
-</table>
   
\ No newline at end of file
diff --git a/content/en/docs/reference/config-api/kube-proxy-config.v1alpha1.md b/content/en/docs/reference/config-api/kube-proxy-config.v1alpha1.md
index 6dfcb913e9f..96baf232678 100644
--- a/content/en/docs/reference/config-api/kube-proxy-config.v1alpha1.md
+++ b/content/en/docs/reference/config-api/kube-proxy-config.v1alpha1.md
@@ -531,12 +531,12 @@ will exit with an error.</p>
 
 - [KubeProxyConfiguration](#kubeproxy-config-k8s-io-v1alpha1-KubeProxyConfiguration)
 
-- [KubeSchedulerConfiguration](#kubescheduler-config-k8s-io-v1-KubeSchedulerConfiguration)
-
 - [KubeSchedulerConfiguration](#kubescheduler-config-k8s-io-v1beta2-KubeSchedulerConfiguration)
 
 - [KubeSchedulerConfiguration](#kubescheduler-config-k8s-io-v1beta3-KubeSchedulerConfiguration)
 
+- [KubeSchedulerConfiguration](#kubescheduler-config-k8s-io-v1-KubeSchedulerConfiguration)
+
 - [GenericControllerManagerConfiguration](#controllermanager-config-k8s-io-v1alpha1-GenericControllerManagerConfiguration)
 
 
@@ -593,12 +593,12 @@ client.</p>
 
 **Appears in:**
 
-- [KubeSchedulerConfiguration](#kubescheduler-config-k8s-io-v1-KubeSchedulerConfiguration)
-
 - [KubeSchedulerConfiguration](#kubescheduler-config-k8s-io-v1beta2-KubeSchedulerConfiguration)
 
 - [KubeSchedulerConfiguration](#kubescheduler-config-k8s-io-v1beta3-KubeSchedulerConfiguration)
 
+- [KubeSchedulerConfiguration](#kubescheduler-config-k8s-io-v1-KubeSchedulerConfiguration)
+
 - [GenericControllerManagerConfiguration](#controllermanager-config-k8s-io-v1alpha1-GenericControllerManagerConfiguration)
 
 
@@ -621,7 +621,7 @@ client.</p>
 <code>bool</code>
 </td>
 <td>
-   <p>enableContentionProfiling enables lock contention profiling, if
+   <p>enableContentionProfiling enables block profiling, if
 enableProfiling is true.</p>
 </td>
 </tr>
diff --git a/content/en/docs/reference/config-api/kube-scheduler-config.v1.md b/content/en/docs/reference/config-api/kube-scheduler-config.v1.md
index 876122ef541..1ef0143f311 100644
--- a/content/en/docs/reference/config-api/kube-scheduler-config.v1.md
+++ b/content/en/docs/reference/config-api/kube-scheduler-config.v1.md
@@ -85,6 +85,14 @@ that play a role in the number of candidates shortlisted. Must be at least
 matching hard affinity to the incoming pod.</p>
 </td>
 </tr>
+<tr><td><code>ignorePreferredTermsOfExistingPods</code> <B>[Required]</B><br/>
+<code>bool</code>
+</td>
+<td>
+   <p>IgnorePreferredTermsOfExistingPods configures the scheduler to ignore existing pods' preferred affinity
+rules when scoring candidate nodes, unless the incoming pod has inter-pod affinities.</p>
+</td>
+</tr>
 </tbody>
 </table>
 
@@ -202,7 +210,7 @@ with the extender. These extenders are shared by all scheduler profiles.</p>
     
   
 <tr><td><code>addedAffinity</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#nodeaffinity-v1-core"><code>core/v1.NodeAffinity</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#nodeaffinity-v1-core"><code>core/v1.NodeAffinity</code></a>
 </td>
 <td>
    <p>AddedAffinity is applied to all Pods additionally to the NodeAffinity
@@ -301,7 +309,7 @@ The default strategy is LeastAllocated with an equal &quot;cpu&quot; and &quot;m
     
   
 <tr><td><code>defaultConstraints</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#topologyspreadconstraint-v1-core"><code>[]core/v1.TopologySpreadConstraint</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#topologyspreadconstraint-v1-core"><code>[]core/v1.TopologySpreadConstraint</code></a>
 </td>
 <td>
    <p>DefaultConstraints defines topology spread constraints to be applied to
@@ -1176,7 +1184,7 @@ client.</p>
 <code>bool</code>
 </td>
 <td>
-   <p>enableContentionProfiling enables lock contention profiling, if
+   <p>enableContentionProfiling enables block profiling, if
 enableProfiling is true.</p>
 </td>
 </tr>
@@ -1188,12 +1196,12 @@ enableProfiling is true.</p>
 
 **Appears in:**
 
+- [KubeSchedulerConfiguration](#kubescheduler-config-k8s-io-v1beta2-KubeSchedulerConfiguration)
+
 - [KubeSchedulerConfiguration](#kubescheduler-config-k8s-io-v1beta3-KubeSchedulerConfiguration)
 
 - [KubeSchedulerConfiguration](#kubescheduler-config-k8s-io-v1-KubeSchedulerConfiguration)
 
-- [KubeSchedulerConfiguration](#kubescheduler-config-k8s-io-v1beta2-KubeSchedulerConfiguration)
-
 
 <p>LeaderElectionConfiguration defines the configuration of leader election
 clients for components that can run with leader election enabled.</p>
diff --git a/content/en/docs/reference/config-api/kube-scheduler-config.v1beta2.md b/content/en/docs/reference/config-api/kube-scheduler-config.v1beta2.md
index edf1071e18a..bcd0377d7ca 100644
--- a/content/en/docs/reference/config-api/kube-scheduler-config.v1beta2.md
+++ b/content/en/docs/reference/config-api/kube-scheduler-config.v1beta2.md
@@ -85,6 +85,14 @@ that play a role in the number of candidates shortlisted. Must be at least
 matching hard affinity to the incoming pod.</p>
 </td>
 </tr>
+<tr><td><code>ignorePreferredTermsOfExistingPods</code> <B>[Required]</B><br/>
+<code>bool</code>
+</td>
+<td>
+   <p>IgnorePreferredTermsOfExistingPods configures the scheduler to ignore existing pods' preferred affinity
+rules when scoring candidate nodes, unless the incoming pod has inter-pod affinities.</p>
+</td>
+</tr>
 </tbody>
 </table>
 
@@ -218,7 +226,7 @@ with the extender. These extenders are shared by all scheduler profiles.</p>
     
   
 <tr><td><code>addedAffinity</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#nodeaffinity-v1-core"><code>core/v1.NodeAffinity</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#nodeaffinity-v1-core"><code>core/v1.NodeAffinity</code></a>
 </td>
 <td>
    <p>AddedAffinity is applied to all Pods additionally to the NodeAffinity
@@ -317,7 +325,7 @@ The default strategy is LeastAllocated with an equal &quot;cpu&quot; and &quot;m
     
   
 <tr><td><code>defaultConstraints</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#topologyspreadconstraint-v1-core"><code>[]core/v1.TopologySpreadConstraint</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#topologyspreadconstraint-v1-core"><code>[]core/v1.TopologySpreadConstraint</code></a>
 </td>
 <td>
    <p>DefaultConstraints defines topology spread constraints to be applied to
@@ -1153,7 +1161,7 @@ client.</p>
 <code>bool</code>
 </td>
 <td>
-   <p>enableContentionProfiling enables lock contention profiling, if
+   <p>enableContentionProfiling enables block profiling, if
 enableProfiling is true.</p>
 </td>
 </tr>
diff --git a/content/en/docs/reference/config-api/kube-scheduler-config.v1beta3.md b/content/en/docs/reference/config-api/kube-scheduler-config.v1beta3.md
index 1f67ffce6c4..278b9637270 100644
--- a/content/en/docs/reference/config-api/kube-scheduler-config.v1beta3.md
+++ b/content/en/docs/reference/config-api/kube-scheduler-config.v1beta3.md
@@ -85,6 +85,14 @@ that play a role in the number of candidates shortlisted. Must be at least
 matching hard affinity to the incoming pod.</p>
 </td>
 </tr>
+<tr><td><code>ignorePreferredTermsOfExistingPods</code> <B>[Required]</B><br/>
+<code>bool</code>
+</td>
+<td>
+   <p>IgnorePreferredTermsOfExistingPods configures the scheduler to ignore existing pods' preferred affinity
+rules when scoring candidate nodes, unless the incoming pod has inter-pod affinities.</p>
+</td>
+</tr>
 </tbody>
 </table>
 
@@ -202,7 +210,7 @@ with the extender. These extenders are shared by all scheduler profiles.</p>
     
   
 <tr><td><code>addedAffinity</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#nodeaffinity-v1-core"><code>core/v1.NodeAffinity</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#nodeaffinity-v1-core"><code>core/v1.NodeAffinity</code></a>
 </td>
 <td>
    <p>AddedAffinity is applied to all Pods additionally to the NodeAffinity
@@ -301,7 +309,7 @@ The default strategy is LeastAllocated with an equal &quot;cpu&quot; and &quot;m
     
   
 <tr><td><code>defaultConstraints</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#topologyspreadconstraint-v1-core"><code>[]core/v1.TopologySpreadConstraint</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#topologyspreadconstraint-v1-core"><code>[]core/v1.TopologySpreadConstraint</code></a>
 </td>
 <td>
    <p>DefaultConstraints defines topology spread constraints to be applied to
@@ -1157,7 +1165,7 @@ client.</p>
 <code>bool</code>
 </td>
 <td>
-   <p>enableContentionProfiling enables lock contention profiling, if
+   <p>enableContentionProfiling enables block profiling, if
 enableProfiling is true.</p>
 </td>
 </tr>
diff --git a/content/en/docs/reference/config-api/kubeadm-config.v1beta2.md b/content/en/docs/reference/config-api/kubeadm-config.v1beta2.md
deleted file mode 100644
index dca15f101f9..00000000000
--- a/content/en/docs/reference/config-api/kubeadm-config.v1beta2.md
+++ /dev/null
@@ -1,1311 +0,0 @@
----
-title: kubeadm Configuration (v1beta2)
-content_type: tool-reference
-package: kubeadm.k8s.io/v1beta2
-auto_generated: true
----
-<h2>Overview</h2>
-<p>Package v1beta2 has been DEPRECATED by v1beta3.</p>
-<p>Package v1beta2 defines the v1beta2 version of the kubeadm configuration file format.
-This version improves on the v1beta1 format by fixing some minor issues and adding a few new fields.</p>
-<p>A list of changes since v1beta1:</p>
-<ul>
-<li>&quot;certificateKey&quot; field is added to InitConfiguration and JoinConfiguration.</li>
-<li>&quot;ignorePreflightErrors&quot; field is added to the NodeRegistrationOptions.</li>
-<li>The JSON &quot;omitempty&quot; tag is used in a more places where appropriate.</li>
-<li>The JSON &quot;omitempty&quot; tag of the &quot;taints&quot; field (inside NodeRegistrationOptions) is removed.</li>
-</ul>
-<p>See the Kubernetes 1.15 changelog for further details.</p>
-<h1>Migration from old kubeadm config versions</h1>
-<p>Please convert your v1beta1 configuration files to v1beta2 using the &quot;kubeadm config migrate&quot; command of kubeadm v1.15.x
-(conversion from older releases of kubeadm config files requires older release of kubeadm as well e.g.</p>
-<ul>
-<li>kubeadm v1.11 should be used to migrate v1alpha1 to v1alpha2; kubeadm v1.12 should be used to translate v1alpha2 to v1alpha3;</li>
-<li>kubeadm v1.13 or v1.14 should be used to translate v1alpha3 to v1beta1)</li>
-</ul>
-<p>Nevertheless, kubeadm v1.15.x will support reading from v1beta1 version of the kubeadm config file format.</p>
-<h2>Basics</h2>
-<p>The preferred way to configure kubeadm is to pass an YAML configuration file with the <code>--config</code> option. Some of the
-configuration options defined in the kubeadm config file are also available as command line flags, but only
-the most common/simple use case are supported with this approach.</p>
-<p>A kubeadm config file could contain multiple configuration types separated using three dashes (<code>---</code>).</p>
-<p>kubeadm supports the following configuration types:</p>
-<pre style="background-color:#fff"><span style="color:#000;font-weight:bold">apiVersion</span>:<span style="color:#bbb"> </span>kubeadm.k8s.io/v1beta2<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">kind</span>:<span style="color:#bbb"> </span>InitConfiguration<span style="color:#bbb">
-</span><span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">apiVersion</span>:<span style="color:#bbb"> </span>kubeadm.k8s.io/v1beta2<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">kind</span>:<span style="color:#bbb"> </span>ClusterConfiguration<span style="color:#bbb">
-</span><span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">apiVersion</span>:<span style="color:#bbb"> </span>kubelet.config.k8s.io/v1beta1<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">kind</span>:<span style="color:#bbb"> </span>KubeletConfiguration<span style="color:#bbb">
-</span><span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">apiVersion</span>:<span style="color:#bbb"> </span>kubeproxy.config.k8s.io/v1alpha1<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">kind</span>:<span style="color:#bbb"> </span>KubeProxyConfiguration<span style="color:#bbb">
-</span><span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">apiVersion</span>:<span style="color:#bbb"> </span>kubeadm.k8s.io/v1beta2<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">kind</span>:<span style="color:#bbb"> </span>JoinConfiguration<span style="color:#bbb">
-</span></pre><p>To print the defaults for &quot;init&quot; and &quot;join&quot; actions use the following commands:</p>
-<pre style="background-color:#fff">kubeadm config print init-defaults
-kubeadm config print join-defaults
-</pre><p>The list of configuration types that must be included in a configuration file depends by the action you are
-performing (<code>init</code> or <code>join</code>) and by the configuration options you are going to use (defaults or advanced customization).</p>
-<p>If some configuration types are not provided, or provided only partially, kubeadm will use default values; defaults
-provided by kubeadm includes also enforcing consistency of values across components when required (e.g.
-<code>--cluster-cidr</code> flag on controller manager and <code>clusterCIDR</code> on kube-proxy).</p>
-<p>Users are always allowed to override default values, with the only exception of a small subset of setting with
-relevance for security (e.g. enforce authorization-mode Node and RBAC on API server)</p>
-<p>If the user provides a configuration types that is not expected for the action you are performing, kubeadm will
-ignore those types and print a warning.</p>
-<h2>Kubeadm init configuration types</h2>
-<p>When executing kubeadm init with the <code>--config</code> option, the following configuration types could be used:
-InitConfiguration, ClusterConfiguration, KubeProxyConfiguration, KubeletConfiguration, but only one
-between InitConfiguration and ClusterConfiguration is mandatory.</p>
-<pre style="background-color:#fff"><span style="color:#000;font-weight:bold">apiVersion</span>:<span style="color:#bbb"> </span>kubeadm.k8s.io/v1beta2<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">kind</span>:<span style="color:#bbb"> </span>InitConfiguration<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">bootstrapTokens</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">  </span>...<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">nodeRegistration</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">  </span>...<span style="color:#bbb">
-</span></pre><p>The InitConfiguration type should be used to configure runtime settings, that in case of <code>kubeadm init</code>
-are the configuration of the bootstrap token and all the setting which are specific to the node where kubeadm
-is executed, including:</p>
-<ul>
-<li>
-<p><code>nodeRegistration</code>, that holds fields that relate to registering the new node to the cluster;
-use it to customize the node name, the CRI socket to use or any other settings that should apply to this
-node only (e.g. the node ip).</p>
-</li>
-<li>
-<p><code>localAPIEndpoint</code>, that represents the endpoint of the instance of the API server to be deployed on this node;
-use it e.g. to customize the API server advertise address.</p>
-</li>
-</ul>
-<pre style="background-color:#fff"><span style="color:#000;font-weight:bold">apiVersion</span>:<span style="color:#bbb"> </span>kubeadm.k8s.io/v1beta2<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">kind</span>:<span style="color:#bbb"> </span>ClusterConfiguration<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">networking</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">  </span>...<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">etcd</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">  </span>...<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">apiServer</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">extraArgs</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">    </span>...<span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">extraVolumes</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">    </span>...<span style="color:#bbb">
-</span><span style="color:#bbb"></span>...<span style="color:#bbb">
-</span></pre><p>The ClusterConfiguration type should be used to configure cluster-wide settings,
-including settings for:</p>
-<ul>
-<li>
-<p>Networking, that holds configuration for the networking topology of the cluster; use it e.g. to customize
-pod subnet or services subnet.</p>
-</li>
-<li>
-<p>Etcd configurations; use it e.g. to customize the local etcd or to configure the API server
-for using an external etcd cluster.</p>
-</li>
-<li>
-<p>kube-apiserver, kube-scheduler, kube-controller-manager configurations; use it to customize control-plane
-components by adding customized setting or overriding kubeadm default settings.</p>
-</li>
-</ul>
-<pre style="background-color:#fff"><span style="color:#000;font-weight:bold">apiVersion</span>:<span style="color:#bbb"> </span>kubeproxy.config.k8s.io/v1alpha1<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">kind</span>:<span style="color:#bbb"> </span>KubeProxyConfiguration<span style="color:#bbb">
-</span><span style="color:#bbb"> </span>...<span style="color:#bbb">
-</span></pre><p>The KubeProxyConfiguration type should be used to change the configuration passed to kube-proxy instances deployed
-in the cluster. If this object is not provided or provided only partially, kubeadm applies defaults.</p>
-<p>See https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/ or
-https://pkg.go.dev/k8s.io/kube-proxy/config/v1alpha1#KubeProxyConfiguration
-for kube proxy official documentation.</p>
-<pre style="background-color:#fff"><span style="color:#000;font-weight:bold">apiVersion</span>:<span style="color:#bbb"> </span>kubelet.config.k8s.io/v1beta1<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">kind</span>:<span style="color:#bbb"> </span>KubeletConfiguration<span style="color:#bbb">
-</span><span style="color:#bbb"> </span>...<span style="color:#bbb">
-</span></pre><p>The KubeletConfiguration type should be used to change the configurations that will be passed to all kubelet instances
-deployed in the cluster. If this object is not provided or provided only partially, kubeadm applies defaults.</p>
-<p>See https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/ or
-https://pkg.go.dev/k8s.io/kubelet/config/v1beta1#KubeletConfiguration
-for kubelet official documentation.</p>
-<p>Here is a fully populated example of a single YAML file containing multiple
-configuration types to be used during a <code>kubeadm init</code> run.</p>
-<pre style="background-color:#fff"><span style="color:#000;font-weight:bold">apiVersion</span>:<span style="color:#bbb"> </span>kubeadm.k8s.io/v1beta2<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">kind</span>:<span style="color:#bbb"> </span>InitConfiguration<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">bootstrapTokens</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">  </span>- <span style="color:#000;font-weight:bold">token</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;9a08jv.c0izixklcxtmnze7&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">    </span><span style="color:#000;font-weight:bold">description</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;kubeadm bootstrap token&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">    </span><span style="color:#000;font-weight:bold">ttl</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;24h&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">  </span>- <span style="color:#000;font-weight:bold">token</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;783bde.3f89s0fje9f38fhf&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">    </span><span style="color:#000;font-weight:bold">description</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;another bootstrap token&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">    </span><span style="color:#000;font-weight:bold">usages</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">      </span>- authentication<span style="color:#bbb">
-</span><span style="color:#bbb">      </span>- signing<span style="color:#bbb">
-</span><span style="color:#bbb">    </span><span style="color:#000;font-weight:bold">groups</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">      </span>- system:bootstrappers:kubeadm:default-node-token<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">nodeRegistration</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">name</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;ec2-10-100-0-1&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">criSocket</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;/var/run/dockershim.sock&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">taints</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">    </span>- <span style="color:#000;font-weight:bold">key</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;kubeadmNode&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">      </span><span style="color:#000;font-weight:bold">value</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;someValue&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">      </span><span style="color:#000;font-weight:bold">effect</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;NoSchedule&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">kubeletExtraArgs</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">    </span><span style="color:#000;font-weight:bold">v</span>:<span style="color:#bbb"> </span><span style="color:#099">4</span><span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">ignorePreflightErrors</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">    </span>- IsPrivilegedUser<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">localAPIEndpoint</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">advertiseAddress</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;10.100.0.1&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">bindPort</span>:<span style="color:#bbb"> </span><span style="color:#099">6443</span><span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">certificateKey</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;e6a2eb8581237ab72a4f494f30285ec12a9694d750b9785706a83bfcbbbd2204&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb"></span>---<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">apiVersion</span>:<span style="color:#bbb"> </span>kubeadm.k8s.io/v1beta2<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">kind</span>:<span style="color:#bbb"> </span>ClusterConfiguration<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">etcd</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#998;font-style:italic"># one of local or external</span><span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">local</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">    </span><span style="color:#000;font-weight:bold">imageRepository</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;registry.k8s.io&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">    </span><span style="color:#000;font-weight:bold">imageTag</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;3.2.24&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">    </span><span style="color:#000;font-weight:bold">dataDir</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;/var/lib/etcd&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">    </span><span style="color:#000;font-weight:bold">extraArgs</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">      </span><span style="color:#000;font-weight:bold">listen-client-urls</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;http://10.100.0.1:2379&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">    </span><span style="color:#000;font-weight:bold">serverCertSANs</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">      </span>- <span style="color:#bbb"> </span><span style="color:#d14">&#34;ec2-10-100-0-1.compute-1.amazonaws.com&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">    </span><span style="color:#000;font-weight:bold">peerCertSANs</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">      </span>- <span style="color:#d14">&#34;10.100.0.1&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#998;font-style:italic"># external:</span><span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#998;font-style:italic">#   endpoints:</span><span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#998;font-style:italic">#     - &#34;10.100.0.1:2379&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#998;font-style:italic">#     - &#34;10.100.0.2:2379&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#998;font-style:italic">#   caFile: &#34;/etcd/kubernetes/pki/etcd/etcd-ca.crt&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#998;font-style:italic">#   certFile: &#34;/etcd/kubernetes/pki/etcd/etcd.crt&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#998;font-style:italic">#   keyFile: &#34;/etcd/kubernetes/pki/etcd/etcd.key&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">networking</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">serviceSubnet</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;10.96.0.0/16&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">podSubnet</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;10.244.0.0/24&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">dnsDomain</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;cluster.local&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">kubernetesVersion</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;v1.12.0&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">controlPlaneEndpoint</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;10.100.0.1:6443&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">apiServer</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">extraArgs</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">    </span><span style="color:#000;font-weight:bold">authorization-mode</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;Node,RBAC&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">extraVolumes</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">    </span>- <span style="color:#000;font-weight:bold">name</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;some-volume&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">      </span><span style="color:#000;font-weight:bold">hostPath</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;/etc/some-path&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">      </span><span style="color:#000;font-weight:bold">mountPath</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;/etc/some-pod-path&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">      </span><span style="color:#000;font-weight:bold">readOnly</span>:<span style="color:#bbb"> </span><span style="color:#000;font-weight:bold">false</span><span style="color:#bbb">
-</span><span style="color:#bbb">      </span><span style="color:#000;font-weight:bold">pathType</span>:<span style="color:#bbb"> </span>File<span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">certSANs</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">    </span>- <span style="color:#d14">&#34;10.100.1.1&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">    </span>- <span style="color:#d14">&#34;ec2-10-100-0-1.compute-1.amazonaws.com&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">timeoutForControlPlane</span>:<span style="color:#bbb"> </span>4m0s<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">controllerManager</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">extraArgs</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">    </span><span style="color:#000;font-weight:bold">&#34;node-cidr-mask-size&#34;: </span><span style="color:#d14">&#34;20&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">extraVolumes</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">    </span>- <span style="color:#000;font-weight:bold">name</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;some-volume&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">      </span><span style="color:#000;font-weight:bold">hostPath</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;/etc/some-path&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">      </span><span style="color:#000;font-weight:bold">mountPath</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;/etc/some-pod-path&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">      </span><span style="color:#000;font-weight:bold">readOnly</span>:<span style="color:#bbb"> </span><span style="color:#000;font-weight:bold">false</span><span style="color:#bbb">
-</span><span style="color:#bbb">      </span><span style="color:#000;font-weight:bold">pathType</span>:<span style="color:#bbb"> </span>File<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">scheduler</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">extraArgs</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">    </span><span style="color:#000;font-weight:bold">address</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;10.100.0.1&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">extraVolumes</span>:<span style="color:#bbb">
-</span><span style="color:#bbb">    </span>- <span style="color:#000;font-weight:bold">name</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;some-volume&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">      </span><span style="color:#000;font-weight:bold">hostPath</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;/etc/some-path&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">      </span><span style="color:#000;font-weight:bold">mountPath</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;/etc/some-pod-path&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb">      </span><span style="color:#000;font-weight:bold">readOnly</span>:<span style="color:#bbb"> </span><span style="color:#000;font-weight:bold">false</span><span style="color:#bbb">
-</span><span style="color:#bbb">      </span><span style="color:#000;font-weight:bold">pathType</span>:<span style="color:#bbb"> </span>File<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">certificatesDir</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;/etc/kubernetes/pki&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">imageRepository</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;registry.k8s.io&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">useHyperKubeImage</span>:<span style="color:#bbb"> </span><span style="color:#000;font-weight:bold">false</span><span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">clusterName</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;example-cluster&#34;</span><span style="color:#bbb">
-</span><span style="color:#bbb"></span>---<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">apiVersion</span>:<span style="color:#bbb"> </span>kubelet.config.k8s.io/v1beta1<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">kind</span>:<span style="color:#bbb"> </span>KubeletConfiguration<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#998;font-style:italic"># kubelet specific options here</span><span style="color:#bbb">
-</span><span style="color:#bbb"></span>---<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">apiVersion</span>:<span style="color:#bbb"> </span>kubeproxy.config.k8s.io/v1alpha1<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">kind</span>:<span style="color:#bbb"> </span>KubeProxyConfiguration<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#998;font-style:italic"># kube-proxy specific options here</span><span style="color:#bbb">
-</span></pre><h2>Kubeadm join configuration types</h2>
-<p>When executing kubeadm join with the <code>--config</code> option, the JoinConfiguration type should be provided.</p>
-<pre style="background-color:#fff"><span style="color:#000;font-weight:bold">apiVersion</span>:<span style="color:#bbb"> </span>kubeadm.k8s.io/v1beta2<span style="color:#bbb">
-</span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">kind</span>:<span style="color:#bbb"> </span>JoinConfiguration<span style="color:#bbb">
-</span><span style="color:#bbb"> </span>...<span style="color:#bbb">
-</span></pre><p>The JoinConfiguration type should be used to configure runtime settings, that in case of <code>kubeadm join</code>
-are the discovery method used for accessing the cluster info and all the setting which are specific
-to the node where kubeadm is executed, including:</p>
-<ul>
-<li>
-<p><code>nodeRegistration</code>, that holds fields that relate to registering the new node to the cluster;
-use it to customize the node name, the CRI socket to use or any other settings that should apply to this
-node only (e.g. the node IP).</p>
-</li>
-<li>
-<p><code>apiEndpoint</code>, that represents the endpoint of the instance of the API server to be eventually deployed on this node.</p>
-</li>
-</ul>
-
-
-## Resource Types 
-
-
-- [ClusterConfiguration](#kubeadm-k8s-io-v1beta2-ClusterConfiguration)
-- [ClusterStatus](#kubeadm-k8s-io-v1beta2-ClusterStatus)
-- [InitConfiguration](#kubeadm-k8s-io-v1beta2-InitConfiguration)
-- [JoinConfiguration](#kubeadm-k8s-io-v1beta2-JoinConfiguration)
-  
-    
-
-## `ClusterConfiguration`     {#kubeadm-k8s-io-v1beta2-ClusterConfiguration}
-    
-
-
-<p>ClusterConfiguration contains cluster-wide configuration for a kubeadm cluster</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-<tr><td><code>apiVersion</code><br/>string</td><td><code>kubeadm.k8s.io/v1beta2</code></td></tr>
-<tr><td><code>kind</code><br/>string</td><td><code>ClusterConfiguration</code></td></tr>
-    
-  
-<tr><td><code>etcd</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-Etcd"><code>Etcd</code></a>
-</td>
-<td>
-   <p><code>etcd</code> holds configuration for etcd.</p>
-</td>
-</tr>
-<tr><td><code>networking</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-Networking"><code>Networking</code></a>
-</td>
-<td>
-   <p><code>networking</code> holds configuration for the networking topology of the cluster.</p>
-</td>
-</tr>
-<tr><td><code>kubernetesVersion</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>kubernetesVersion</code> is the target version of the control plane.</p>
-</td>
-</tr>
-<tr><td><code>controlPlaneEndpoint</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>controlPlaneEndpoint</code> sets a stable IP address or DNS name for the control plane; it
-can be a valid IP address or a RFC-1123 DNS subdomain, both with optional TCP port.
-In case the <code>controlPlaneEndpoint</code> is not specified, the <code>advertiseAddress</code> + <code>bindPort</code>
-are used; in case the <code>controlPlaneEndpoint</code> is specified but without a TCP port,
-the <code>bindPort</code> is used.
-Possible usages are:</p>
-<ul>
-<li>In a cluster with more than one control plane instances, this field should be
-assigned the address of the external load balancer in front of the
-control plane instances.</li>
-<li>In environments with enforced node recycling, the <code>controlPlaneEndpoint</code>
-could be used for assigning a stable DNS to the control plane.</li>
-</ul>
-</td>
-</tr>
-<tr><td><code>apiServer</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-APIServer"><code>APIServer</code></a>
-</td>
-<td>
-   <p><code>apiServer</code> contains extra settings for the API server.</p>
-</td>
-</tr>
-<tr><td><code>controllerManager</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-ControlPlaneComponent"><code>ControlPlaneComponent</code></a>
-</td>
-<td>
-   <p><code>controllerManager</code> contains extra settings for the controller manager.</p>
-</td>
-</tr>
-<tr><td><code>scheduler</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-ControlPlaneComponent"><code>ControlPlaneComponent</code></a>
-</td>
-<td>
-   <p><code>scheduler</code> contains extra settings for the scheduler.</p>
-</td>
-</tr>
-<tr><td><code>dns</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-DNS"><code>DNS</code></a>
-</td>
-<td>
-   <p><code>dns</code> defines the options for the DNS add-on installed in the cluster.</p>
-</td>
-</tr>
-<tr><td><code>certificatesDir</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>certificatesDir</code> specifies where to store or look for all required certificates.</p>
-</td>
-</tr>
-<tr><td><code>imageRepository</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>imageRepository</code> sets the container registry to pull images from.
-If empty, <code>registry.k8s.io</code> will be used by default; in case of kubernetes version is
-a CI build (kubernetes version starts with <code>ci/</code>) <code>gcr.io/k8s-staging-ci-images</code>
-is used as a default for control plane components and for kube-proxy, while
-<code>registry.k8s.io</code> will be used for all the other images.</p>
-</td>
-</tr>
-<tr><td><code>useHyperKubeImage</code> <B>[Required]</B><br/>
-<code>bool</code>
-</td>
-<td>
-   <p><code>useHyperKubeImage</code> controls if hyperkube should be used for Kubernetes components
-instead of their respective separate images.
-DEPRECATED: As <code>hyperkube</code> is itself deprecated, this fields is too. It will be
-removed in future kubeadm config versions, kubeadm will print multiple warnings
-when this set to true, and at some point it may become ignored.</p>
-</td>
-</tr>
-<tr><td><code>featureGates</code> <B>[Required]</B><br/>
-<code>map[string]bool</code>
-</td>
-<td>
-   <p><code>featureGates</code> contains the feature gates enabled by the user.</p>
-</td>
-</tr>
-<tr><td><code>clusterName</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p>The cluster name.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `ClusterStatus`     {#kubeadm-k8s-io-v1beta2-ClusterStatus}
-    
-
-
-<p>ClusterStatus contains the cluster status. The ClusterStatus will be stored in
-the kubeadm-config ConfigMap in the cluster, and then updated by kubeadm when
-additional control plane instance joins or leaves the cluster.</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-<tr><td><code>apiVersion</code><br/>string</td><td><code>kubeadm.k8s.io/v1beta2</code></td></tr>
-<tr><td><code>kind</code><br/>string</td><td><code>ClusterStatus</code></td></tr>
-    
-  
-<tr><td><code>apiEndpoints</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-APIEndpoint"><code>map[string]github.com/tengqm/kubeconfig/config/kubeadm/v1beta2.APIEndpoint</code></a>
-</td>
-<td>
-   <p><code>apiEndpoints</code> currently available in the cluster, one for each control
-plane/API server instance.
-The key of the map is the IP of the host's default interface.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `InitConfiguration`     {#kubeadm-k8s-io-v1beta2-InitConfiguration}
-    
-
-
-<p>InitConfiguration contains a list of elements that is specific &quot;kubeadm init&quot;-only runtime
-information.</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-<tr><td><code>apiVersion</code><br/>string</td><td><code>kubeadm.k8s.io/v1beta2</code></td></tr>
-<tr><td><code>kind</code><br/>string</td><td><code>InitConfiguration</code></td></tr>
-    
-  
-<tr><td><code>bootstrapTokens</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-BootstrapToken"><code>[]BootstrapToken</code></a>
-</td>
-<td>
-   <p><code>bootstrapTokens</code> is respected at <code>kubeadm init</code> time and describes a set of bootstrap tokens to create.
-This information IS NOT uploaded to the kubeadm cluster ConfigMap, partly because of its sensitive nature.</p>
-</td>
-</tr>
-<tr><td><code>nodeRegistration</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-NodeRegistrationOptions"><code>NodeRegistrationOptions</code></a>
-</td>
-<td>
-   <p><code>nodeRegistration</code> holds fields that relate to registering the new control-plane node to the cluster.</p>
-</td>
-</tr>
-<tr><td><code>localAPIEndpoint</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-APIEndpoint"><code>APIEndpoint</code></a>
-</td>
-<td>
-   <p><code>localAPIEndpoint</code> represents the endpoint of the API server instance that's deployed on this control plane node.
-In HA setups, this differs from <code>ClusterConfiguration.controlPlaneEndpoint</code> in the sense that ControlPlaneEndpoint
-is the global endpoint for the cluster, which then load-balances the requests to each individual API server. This
-configuration object lets you customize what IP/DNS name and port the local API server advertises it's accessible
-on. By default, kubeadm tries to auto-detect the IP of the default interface and use that, but in case that process
-fails you may set the desired value here.</p>
-</td>
-</tr>
-<tr><td><code>certificateKey</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>certificateKey</code> sets the key with which certificates and keys are encrypted prior to being uploaded in
-a secret in the cluster during the <code>uploadcerts init</code> phase.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `JoinConfiguration`     {#kubeadm-k8s-io-v1beta2-JoinConfiguration}
-    
-
-
-<p>JoinConfiguration contains elements describing a particular node.</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-<tr><td><code>apiVersion</code><br/>string</td><td><code>kubeadm.k8s.io/v1beta2</code></td></tr>
-<tr><td><code>kind</code><br/>string</td><td><code>JoinConfiguration</code></td></tr>
-    
-  
-<tr><td><code>nodeRegistration</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-NodeRegistrationOptions"><code>NodeRegistrationOptions</code></a>
-</td>
-<td>
-   <p><code>nodeRegistration</code> holds fields that relate to registering the new
-control-plane node to the cluster</p>
-</td>
-</tr>
-<tr><td><code>caCertPath</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>caCertPath</code> is the path to the SSL certificate authority used to
-secure comunications between a node and the control-plane.
-Defaults to &quot;/etc/kubernetes/pki/ca.crt&quot;.</p>
-</td>
-</tr>
-<tr><td><code>discovery</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-Discovery"><code>Discovery</code></a>
-</td>
-<td>
-   <p><code>discovery</code> specifies the options for the kubelet to use during the TLS
-bootstrap process.</p>
-</td>
-</tr>
-<tr><td><code>controlPlane</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-JoinControlPlane"><code>JoinControlPlane</code></a>
-</td>
-<td>
-   <p><code>controlPlane</code> defines the additional control plane instance to be deployed
-on the joining node. If nil, no additional control plane instance will be deployed.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `APIEndpoint`     {#kubeadm-k8s-io-v1beta2-APIEndpoint}
-    
-
-**Appears in:**
-
-- [ClusterStatus](#kubeadm-k8s-io-v1beta2-ClusterStatus)
-
-- [InitConfiguration](#kubeadm-k8s-io-v1beta2-InitConfiguration)
-
-- [JoinControlPlane](#kubeadm-k8s-io-v1beta2-JoinControlPlane)
-
-
-<p>APIEndpoint struct contains elements of API server instance deployed on a node.</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>advertiseAddress</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>advertiseAddress</code> sets the IP address for the API server to advertise.</p>
-</td>
-</tr>
-<tr><td><code>bindPort</code> <B>[Required]</B><br/>
-<code>int32</code>
-</td>
-<td>
-   <p><code>bindPort</code> sets the secure port for the API Server to bind to.
-Defaults to 6443.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `APIServer`     {#kubeadm-k8s-io-v1beta2-APIServer}
-    
-
-**Appears in:**
-
-- [ClusterConfiguration](#kubeadm-k8s-io-v1beta2-ClusterConfiguration)
-
-
-<p>APIServer holds settings necessary for API server deployments in the cluster.</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>ControlPlaneComponent</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-ControlPlaneComponent"><code>ControlPlaneComponent</code></a>
-</td>
-<td>(Members of <code>ControlPlaneComponent</code> are embedded into this type.)
-   <span class="text-muted">No description provided.</span></td>
-</tr>
-<tr><td><code>certSANs</code> <B>[Required]</B><br/>
-<code>[]string</code>
-</td>
-<td>
-   <p><code>certSANs</code> sets extra Subject Alternative Names (SANs) for the API Server
-signing certificate.</p>
-</td>
-</tr>
-<tr><td><code>timeoutForControlPlane</code> <B>[Required]</B><br/>
-<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
-</td>
-<td>
-   <p><code>timeoutForControlPlane</code> controls the timeout that we wait for the API server
-to appear.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `BootstrapToken`     {#kubeadm-k8s-io-v1beta2-BootstrapToken}
-    
-
-**Appears in:**
-
-- [InitConfiguration](#kubeadm-k8s-io-v1beta2-InitConfiguration)
-
-
-<p>BootstrapToken describes one bootstrap token, stored as a Secret in the cluster</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>token</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-BootstrapTokenString"><code>BootstrapTokenString</code></a>
-</td>
-<td>
-   <p><code>token</code> is used for establishing bidirectional trust between nodes and control-planes.
-Used for joining nodes in the cluster.</p>
-</td>
-</tr>
-<tr><td><code>description</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>description</code> sets a human-friendly message why this token exists and what it's used
-for, so other administrators can know its purpose.</p>
-</td>
-</tr>
-<tr><td><code>ttl</code> <B>[Required]</B><br/>
-<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
-</td>
-<td>
-   <p><code>ttl</code> defines the time to live for this token. Defaults to '24h'.
-<code>expires</code> and <code>ttl</code> are mutually exclusive.</p>
-</td>
-</tr>
-<tr><td><code>expires</code> <B>[Required]</B><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta"><code>meta/v1.Time</code></a>
-</td>
-<td>
-   <p><code>expires</code> specifies the timestamp when this token expires. Defaults to being set
-dynamically at runtime based on the <code>ttl</code>. <code>expires</code> and <code>ttl</code> are mutually exclusive.</p>
-</td>
-</tr>
-<tr><td><code>usages</code> <B>[Required]</B><br/>
-<code>[]string</code>
-</td>
-<td>
-   <p><code>usages</code> describes the ways in which this token can be used. Can by default be used
-for establishing bidirectional trust, but that can be changed here.</p>
-</td>
-</tr>
-<tr><td><code>groups</code> <B>[Required]</B><br/>
-<code>[]string</code>
-</td>
-<td>
-   <p><code>groups</code> specifies the extra groups that this token will authenticate as when/if
-used for authentication.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `BootstrapTokenDiscovery`     {#kubeadm-k8s-io-v1beta2-BootstrapTokenDiscovery}
-    
-
-**Appears in:**
-
-- [Discovery](#kubeadm-k8s-io-v1beta2-Discovery)
-
-
-<p>BootstrapTokenDiscovery is used to set the options for bootstrap token based discovery</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>token</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>token</code> is a token used to validate cluster information fetched from
-the control-plane.</p>
-</td>
-</tr>
-<tr><td><code>apiServerEndpoint</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>apiServerEndpoint</code> is an IP or domain name to the API server from which information
-will be fetched.</p>
-</td>
-</tr>
-<tr><td><code>caCertHashes</code> <B>[Required]</B><br/>
-<code>[]string</code>
-</td>
-<td>
-   <p><code>caCertHashes</code> specifies a set of public key pins to verify when token-based discovery
-is used. The root CA found during discovery must match one of these values.
-Specifying an empty set disables root CA pinning, which can be unsafe.
-Each hash is specified as &quot;<!-- raw HTML omitted -->:<!-- raw HTML omitted -->&quot;, where the only currently supported type is &quot;sha256&quot;.
-This is a hex-encoded SHA-256 hash of the Subject Public Key Info (SPKI) object in
-DER-encoded ASN.1. These hashes can be calculated using, for example, OpenSSL.</p>
-</td>
-</tr>
-<tr><td><code>unsafeSkipCAVerification</code> <B>[Required]</B><br/>
-<code>bool</code>
-</td>
-<td>
-   <p><code>unsafeSkipCAVerification</code> allows token-based discovery without CA verification via
-<code>caCertHashes</code>. This can weaken the security of kubeadm since other nodes can
-impersonate the control-plane.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `BootstrapTokenString`     {#kubeadm-k8s-io-v1beta2-BootstrapTokenString}
-    
-
-**Appears in:**
-
-- [BootstrapToken](#kubeadm-k8s-io-v1beta2-BootstrapToken)
-
-
-<p>BootstrapTokenString is a token of the format abcdef.abcdef0123456789 that is used
-for both validation of the practically of the API server from a joining node's point
-of view and as an authentication method for the node in the bootstrap phase of
-&quot;kubeadm join&quot;. This token is and should be short-lived</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>-</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <span class="text-muted">No description provided.</span></td>
-</tr>
-<tr><td><code>-</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <span class="text-muted">No description provided.</span></td>
-</tr>
-</tbody>
-</table>
-
-## `ControlPlaneComponent`     {#kubeadm-k8s-io-v1beta2-ControlPlaneComponent}
-    
-
-**Appears in:**
-
-- [ClusterConfiguration](#kubeadm-k8s-io-v1beta2-ClusterConfiguration)
-
-- [APIServer](#kubeadm-k8s-io-v1beta2-APIServer)
-
-
-<p>ControlPlaneComponent holds settings common to control plane component of the cluster</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>extraArgs</code> <B>[Required]</B><br/>
-<code>map[string]string</code>
-</td>
-<td>
-   <p><code>extraArgs</code> is an extra set of flags to pass to a control plane component.
-A key in this map is the flag name as it appears on the command line except
-without leading dash(es).</p>
-</td>
-</tr>
-<tr><td><code>extraVolumes</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-HostPathMount"><code>[]HostPathMount</code></a>
-</td>
-<td>
-   <p><code>extraVolumes</code> is an extra set of host volumes mounted to the control plane
-component.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `DNS`     {#kubeadm-k8s-io-v1beta2-DNS}
-    
-
-**Appears in:**
-
-- [ClusterConfiguration](#kubeadm-k8s-io-v1beta2-ClusterConfiguration)
-
-
-<p>DNS defines the DNS addon that should be used in the cluster</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>type</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-DNSAddOnType"><code>DNSAddOnType</code></a>
-</td>
-<td>
-   <p><code>type</code> defines the DNS add-on to be used.</p>
-</td>
-</tr>
-<tr><td><code>ImageMeta</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-ImageMeta"><code>ImageMeta</code></a>
-</td>
-<td>(Members of <code>ImageMeta</code> are embedded into this type.)
-   <p>ImageMeta allows to customize the image used for the DNS component</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `DNSAddOnType`     {#kubeadm-k8s-io-v1beta2-DNSAddOnType}
-    
-(Alias of `string`)
-
-**Appears in:**
-
-- [DNS](#kubeadm-k8s-io-v1beta2-DNS)
-
-
-<p>DNSAddOnType defines string identifying DNS add-on types.</p>
-
-
-
-
-## `Discovery`     {#kubeadm-k8s-io-v1beta2-Discovery}
-    
-
-**Appears in:**
-
-- [JoinConfiguration](#kubeadm-k8s-io-v1beta2-JoinConfiguration)
-
-
-<p>Discovery specifies the options for the kubelet to use during the TLS Bootstrap process</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>bootstrapToken</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-BootstrapTokenDiscovery"><code>BootstrapTokenDiscovery</code></a>
-</td>
-<td>
-   <p><code>bootstrapToken</code> is used to set the options for bootstrap token based discovery.
-<code>bootstrapToken</code> and <code>file</code> are mutually exclusive.</p>
-</td>
-</tr>
-<tr><td><code>file</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-FileDiscovery"><code>FileDiscovery</code></a>
-</td>
-<td>
-   <p><code>file</code> is used to specify a file or URL to a kubeconfig file from which to load
-cluster information.
-<code>bootstrapToken</code> and <code>file</code> are mutually exclusive.</p>
-</td>
-</tr>
-<tr><td><code>tlsBootstrapToken</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>tlsBootstrapToken</code> is a token used for TLS bootstrapping.
-If <code>bootstrapToken</code> is set, this field is defaulted to <code>.bootstrapToken.token</code>,
-but can be overridden.
-If <code>file</code> is set, this field <strong>must be set</strong> in case the KubeConfigFile does not
-contain any other authentication information.</p>
-</td>
-</tr>
-<tr><td><code>timeout</code> <B>[Required]</B><br/>
-<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
-</td>
-<td>
-   <p><code>timeout</code> modifies the discovery timeout.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `Etcd`     {#kubeadm-k8s-io-v1beta2-Etcd}
-    
-
-**Appears in:**
-
-- [ClusterConfiguration](#kubeadm-k8s-io-v1beta2-ClusterConfiguration)
-
-
-<p>Etcd contains elements describing Etcd configuration.</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>local</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-LocalEtcd"><code>LocalEtcd</code></a>
-</td>
-<td>
-   <p><code>local</code> provides configuration knobs for configuring the local etcd instance.
-<code>local</code> and <code>external</code> are mutually exclusive.</p>
-</td>
-</tr>
-<tr><td><code>external</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-ExternalEtcd"><code>ExternalEtcd</code></a>
-</td>
-<td>
-   <p><code>external</code> describes how to connect to an external etcd cluster.
-<code>local</code> and <code>external</code> are mutually exclusive.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `ExternalEtcd`     {#kubeadm-k8s-io-v1beta2-ExternalEtcd}
-    
-
-**Appears in:**
-
-- [Etcd](#kubeadm-k8s-io-v1beta2-Etcd)
-
-
-<p>ExternalEtcd describes an external etcd cluster.
-Kubeadm has no knowledge of where certificate files live and they must be supplied.</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>endpoints</code> <B>[Required]</B><br/>
-<code>[]string</code>
-</td>
-<td>
-   <p><code>endpoints</code> of etcd members. Required for external etcd.</p>
-</td>
-</tr>
-<tr><td><code>caFile</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>caFile</code> is an SSL Certificate Authority (CA) file used to secure etcd communication.
-Required if using a TLS connection.</p>
-</td>
-</tr>
-<tr><td><code>certFile</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>certFile</code> is an SSL certification file used to secure etcd communication.
-Required if using a TLS connection.</p>
-</td>
-</tr>
-<tr><td><code>keyFile</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>keyFile</code> is an SSL key file used to secure etcd communication.
-Required if using a TLS connection.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `FileDiscovery`     {#kubeadm-k8s-io-v1beta2-FileDiscovery}
-    
-
-**Appears in:**
-
-- [Discovery](#kubeadm-k8s-io-v1beta2-Discovery)
-
-
-<p>FileDiscovery is used to specify a file or URL to a kubeconfig file from which to load cluster information</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>kubeConfigPath</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>kubeConfigPath</code> is used to specify the actual file path or URL to the kubeconfig file
-from which to load cluster information.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `HostPathMount`     {#kubeadm-k8s-io-v1beta2-HostPathMount}
-    
-
-**Appears in:**
-
-- [ControlPlaneComponent](#kubeadm-k8s-io-v1beta2-ControlPlaneComponent)
-
-
-<p>HostPathMount contains elements describing volumes that are mounted from the host.</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>name</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>name</code> of the volume inside the Pod template.</p>
-</td>
-</tr>
-<tr><td><code>hostPath</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>hostPath</code> is the path in the host that will be mounted inside the Pod.</p>
-</td>
-</tr>
-<tr><td><code>mountPath</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>mountPath</code>is the path inside the Pod where hostPath volume will be mounted.</p>
-</td>
-</tr>
-<tr><td><code>readOnly</code> <B>[Required]</B><br/>
-<code>bool</code>
-</td>
-<td>
-   <p><code>readOnly</code> controls write access to the volume.</p>
-</td>
-</tr>
-<tr><td><code>pathType</code> <B>[Required]</B><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#hostpathtype-v1-core"><code>core/v1.HostPathType</code></a>
-</td>
-<td>
-   <p><code>pathType</code> is the type of the HostPath.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `ImageMeta`     {#kubeadm-k8s-io-v1beta2-ImageMeta}
-    
-
-**Appears in:**
-
-- [DNS](#kubeadm-k8s-io-v1beta2-DNS)
-
-- [LocalEtcd](#kubeadm-k8s-io-v1beta2-LocalEtcd)
-
-
-<p>ImageMeta allows to customize the image used for components that are not
-originated from the Kubernetes/Kubernetes release process</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>imageRepository</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>imageRepository</code> sets the container registry to pull images from.
-If not set, the <code>imageRepository</code> defined in ClusterConfiguration will be used.</p>
-</td>
-</tr>
-<tr><td><code>imageTag</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>imageTag</code> allows for specifying a tag for the image.
-In case this value is set, kubeadm does not change automatically the
-version of the above components during upgrades.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `JoinControlPlane`     {#kubeadm-k8s-io-v1beta2-JoinControlPlane}
-    
-
-**Appears in:**
-
-- [JoinConfiguration](#kubeadm-k8s-io-v1beta2-JoinConfiguration)
-
-
-<p>JoinControlPlane contains elements describing an additional control plane instance
-to be deployed on the joining node.</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>localAPIEndpoint</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-APIEndpoint"><code>APIEndpoint</code></a>
-</td>
-<td>
-   <p><code>localAPIEndpoint</code> represents the endpoint of the API server instance
-to be deployed on this node.</p>
-</td>
-</tr>
-<tr><td><code>certificateKey</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>certificateKey</code> is the key that is used for decryption of certificates after
-they are downloaded from the secret upon joining a new control plane node.
-The corresponding encryption key is in the InitConfiguration.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `LocalEtcd`     {#kubeadm-k8s-io-v1beta2-LocalEtcd}
-    
-
-**Appears in:**
-
-- [Etcd](#kubeadm-k8s-io-v1beta2-Etcd)
-
-
-<p>LocalEtcd describes that kubeadm should run an etcd cluster locally.</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>ImageMeta</code> <B>[Required]</B><br/>
-<a href="#kubeadm-k8s-io-v1beta2-ImageMeta"><code>ImageMeta</code></a>
-</td>
-<td>(Members of <code>ImageMeta</code> are embedded into this type.)
-   <p>ImageMeta allows to customize the container used for etcd.</p>
-</td>
-</tr>
-<tr><td><code>dataDir</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>dataDir</code> is the directory etcd will place its data.
-Defaults to &quot;/var/lib/etcd&quot;.</p>
-</td>
-</tr>
-<tr><td><code>extraArgs</code> <B>[Required]</B><br/>
-<code>map[string]string</code>
-</td>
-<td>
-   <p><code>extraArgs</code> are extra arguments provided to the etcd binary when run
-inside a static pod.
-A key in this map is the flag name as it appears on the
-command line except without leading dash(es).</p>
-</td>
-</tr>
-<tr><td><code>serverCertSANs</code> <B>[Required]</B><br/>
-<code>[]string</code>
-</td>
-<td>
-   <p><code>serverCertSANs</code> sets extra Subject Alternative Names (SANs) for the
-etcd server signing certificate.</p>
-</td>
-</tr>
-<tr><td><code>peerCertSANs</code> <B>[Required]</B><br/>
-<code>[]string</code>
-</td>
-<td>
-   <p><code>peerCertSANs</code> sets extra Subject Alternative Names (SANs) for the
-etcd peer signing certificate.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `Networking`     {#kubeadm-k8s-io-v1beta2-Networking}
-    
-
-**Appears in:**
-
-- [ClusterConfiguration](#kubeadm-k8s-io-v1beta2-ClusterConfiguration)
-
-
-<p>Networking contains elements describing cluster's networking configuration</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>serviceSubnet</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>serviceSubnet</code> is the subnet used by kubernetes Services. Defaults to &quot;10.96.0.0/12&quot;.</p>
-</td>
-</tr>
-<tr><td><code>podSubnet</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>podSubnet</code> is the subnet used by Pods.</p>
-</td>
-</tr>
-<tr><td><code>dnsDomain</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>dnsDomain</code> is the DNS domain used by kubernetes Services. Defaults to &quot;cluster.local&quot;.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `NodeRegistrationOptions`     {#kubeadm-k8s-io-v1beta2-NodeRegistrationOptions}
-    
-
-**Appears in:**
-
-- [InitConfiguration](#kubeadm-k8s-io-v1beta2-InitConfiguration)
-
-- [JoinConfiguration](#kubeadm-k8s-io-v1beta2-JoinConfiguration)
-
-
-<p>NodeRegistrationOptions holds fields that relate to registering a new control-plane
-or node to the cluster, either via &quot;kubeadm init&quot; or &quot;kubeadm join&quot;.</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>name</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>name</code> is the <code>.Metadata.Name</code> field of the Node API object that will be created
-in this <code>kubeadm init</code> or <code>kubeadm join</code> operation.
-This field is also used in the <code>CommonName</code> field of the kubelet's client certificate
-to the API server.
-Defaults to the hostname of the node if not provided.</p>
-</td>
-</tr>
-<tr><td><code>criSocket</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>criSocket</code> is used to retrieve container runtime information. This information will
-be annotated to the Node API object, for later re-use.</p>
-</td>
-</tr>
-<tr><td><code>taints</code> <B>[Required]</B><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#taint-v1-core"><code>[]core/v1.Taint</code></a>
-</td>
-<td>
-   <p><code>taints</code> specifies the taints the Node API object should be registered with.
-If this field is unset, i.e. nil, in the <code>kubeadm init</code> process it will be defaulted with
-a control-plane taint for control-plane nodes. If you don't want to taint your control-plane
-node, set this field to an empty list, i.e. <code>taints: []</code>, in the YAML file. This field is
-solely used for Node registration.</p>
-</td>
-</tr>
-<tr><td><code>kubeletExtraArgs</code> <B>[Required]</B><br/>
-<code>map[string]string</code>
-</td>
-<td>
-   <p><code>kubeletExtraArgs</code> passes through extra arguments to the kubelet. The arguments here are
-passed to the kubelet command line via the environment file kubeadm writes at runtime for
-the kubelet to source. This overrides the generic base-level configuration in the
-'kubelet-config-1.X' ConfigMap.
-Flags have higher priority when parsing. These values are local and specific to the node
-kubeadm is executing on.
-A key in this map is the flag name as it appears on the command line except without leading dash(es).</p>
-</td>
-</tr>
-<tr><td><code>ignorePreflightErrors</code> <B>[Required]</B><br/>
-<code>[]string</code>
-</td>
-<td>
-   <p><code>ignorePreflightErrors</code> provides a list of pre-flight errors to be ignored when the
-current node is registered.</p>
-</td>
-</tr>
-</tbody>
-</table>
-  
\ No newline at end of file
diff --git a/content/en/docs/reference/config-api/kubeadm-config.v1beta3.md b/content/en/docs/reference/config-api/kubeadm-config.v1beta3.md
index 8abeb61fe35..5504f6070e1 100644
--- a/content/en/docs/reference/config-api/kubeadm-config.v1beta3.md
+++ b/content/en/docs/reference/config-api/kubeadm-config.v1beta3.md
@@ -30,6 +30,7 @@ the user to configure a directory from which to take patches for components depl
 <ul>
 <li>kubeadm v1.15.x and newer can be used to migrate from v1beta1 to v1beta2.</li>
 <li>kubeadm v1.22.x and newer no longer support v1beta1 and older APIs, but can be used to migrate v1beta2 to v1beta3.</li>
+<li>kubeadm v1.27.x and newer no longer support v1beta2 and older APIs,</li>
 </ul>
 <h2>Basics</h2>
 <p>The preferred way to configure kubeadm is to pass an YAML configuration file with the <code>--config</code> option. Some of the
@@ -264,109 +265,6 @@ node only (e.g. the node ip).</p>
   
     
 
-## `BootstrapToken`     {#BootstrapToken}
-    
-
-**Appears in:**
-
-- [InitConfiguration](#kubeadm-k8s-io-v1beta3-InitConfiguration)
-
-
-<p>BootstrapToken describes one bootstrap token, stored as a Secret in the cluster</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>token</code> <B>[Required]</B><br/>
-<a href="#BootstrapTokenString"><code>BootstrapTokenString</code></a>
-</td>
-<td>
-   <p><code>token</code> is used for establishing bidirectional trust between nodes and control-planes.
-Used for joining nodes in the cluster.</p>
-</td>
-</tr>
-<tr><td><code>description</code><br/>
-<code>string</code>
-</td>
-<td>
-   <p><code>description</code> sets a human-friendly message why this token exists and what it's used
-for, so other administrators can know its purpose.</p>
-</td>
-</tr>
-<tr><td><code>ttl</code><br/>
-<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
-</td>
-<td>
-   <p><code>ttl</code> defines the time to live for this token. Defaults to <code>24h</code>.
-<code>expires</code> and <code>ttl</code> are mutually exclusive.</p>
-</td>
-</tr>
-<tr><td><code>expires</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta"><code>meta/v1.Time</code></a>
-</td>
-<td>
-   <p><code>expires</code> specifies the timestamp when this token expires. Defaults to being set
-dynamically at runtime based on the <code>ttl</code>. <code>expires</code> and <code>ttl</code> are mutually exclusive.</p>
-</td>
-</tr>
-<tr><td><code>usages</code><br/>
-<code>[]string</code>
-</td>
-<td>
-   <p><code>usages</code> describes the ways in which this token can be used. Can by default be used
-for establishing bidirectional trust, but that can be changed here.</p>
-</td>
-</tr>
-<tr><td><code>groups</code><br/>
-<code>[]string</code>
-</td>
-<td>
-   <p><code>groups</code> specifies the extra groups that this token will authenticate as when/if
-used for authentication</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `BootstrapTokenString`     {#BootstrapTokenString}
-    
-
-**Appears in:**
-
-- [BootstrapToken](#BootstrapToken)
-
-
-<p>BootstrapTokenString is a token of the format <code>abcdef.abcdef0123456789</code> that is used
-for both validation of the practically of the API server from a joining node's point
-of view and as an authentication method for the node in the bootstrap phase of
-&quot;kubeadm join&quot;. This token is and should be short-lived.</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>-</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <span class="text-muted">No description provided.</span></td>
-</tr>
-<tr><td><code>-</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <span class="text-muted">No description provided.</span></td>
-</tr>
-</tbody>
-</table>
-  
-    
-
 ## `ClusterConfiguration`     {#kubeadm-k8s-io-v1beta3-ClusterConfiguration}
     
 
@@ -1036,7 +934,7 @@ file from which to load cluster information.</p>
 </td>
 </tr>
 <tr><td><code>pathType</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#hostpathtype-v1-core"><code>core/v1.HostPathType</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#hostpathtype-v1-core"><code>core/v1.HostPathType</code></a>
 </td>
 <td>
    <p><code>pathType</code> is the type of the <code>hostPath</code>.</p>
@@ -1259,7 +1157,7 @@ This information will be annotated to the Node API object, for later re-use</p>
 </td>
 </tr>
 <tr><td><code>taints</code> <B>[Required]</B><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#taint-v1-core"><code>[]core/v1.Taint</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#taint-v1-core"><code>[]core/v1.Taint</code></a>
 </td>
 <td>
    <p><code>taints</code> specifies the taints the Node API object should be registered with.
@@ -1290,7 +1188,7 @@ the current node is registered.</p>
 </td>
 </tr>
 <tr><td><code>imagePullPolicy</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#pullpolicy-v1-core"><code>core/v1.PullPolicy</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#pullpolicy-v1-core"><code>core/v1.PullPolicy</code></a>
 </td>
 <td>
    <p><code>imagePullPolicy</code> specifies the policy for image pulling during kubeadm &quot;init&quot; and
@@ -1338,4 +1236,107 @@ first alpha-numerically.</p>
 </tr>
 </tbody>
 </table>
-  
\ No newline at end of file
+  
+  
+    
+
+## `BootstrapToken`     {#BootstrapToken}
+    
+
+**Appears in:**
+
+- [InitConfiguration](#kubeadm-k8s-io-v1beta3-InitConfiguration)
+
+
+<p>BootstrapToken describes one bootstrap token, stored as a Secret in the cluster</p>
+
+
+<table class="table">
+<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
+<tbody>
+    
+  
+<tr><td><code>token</code> <B>[Required]</B><br/>
+<a href="#BootstrapTokenString"><code>BootstrapTokenString</code></a>
+</td>
+<td>
+   <p><code>token</code> is used for establishing bidirectional trust between nodes and control-planes.
+Used for joining nodes in the cluster.</p>
+</td>
+</tr>
+<tr><td><code>description</code><br/>
+<code>string</code>
+</td>
+<td>
+   <p><code>description</code> sets a human-friendly message why this token exists and what it's used
+for, so other administrators can know its purpose.</p>
+</td>
+</tr>
+<tr><td><code>ttl</code><br/>
+<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
+</td>
+<td>
+   <p><code>ttl</code> defines the time to live for this token. Defaults to <code>24h</code>.
+<code>expires</code> and <code>ttl</code> are mutually exclusive.</p>
+</td>
+</tr>
+<tr><td><code>expires</code><br/>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#time-v1-meta"><code>meta/v1.Time</code></a>
+</td>
+<td>
+   <p><code>expires</code> specifies the timestamp when this token expires. Defaults to being set
+dynamically at runtime based on the <code>ttl</code>. <code>expires</code> and <code>ttl</code> are mutually exclusive.</p>
+</td>
+</tr>
+<tr><td><code>usages</code><br/>
+<code>[]string</code>
+</td>
+<td>
+   <p><code>usages</code> describes the ways in which this token can be used. Can by default be used
+for establishing bidirectional trust, but that can be changed here.</p>
+</td>
+</tr>
+<tr><td><code>groups</code><br/>
+<code>[]string</code>
+</td>
+<td>
+   <p><code>groups</code> specifies the extra groups that this token will authenticate as when/if
+used for authentication</p>
+</td>
+</tr>
+</tbody>
+</table>
+
+## `BootstrapTokenString`     {#BootstrapTokenString}
+    
+
+**Appears in:**
+
+- [BootstrapToken](#BootstrapToken)
+
+
+<p>BootstrapTokenString is a token of the format <code>abcdef.abcdef0123456789</code> that is used
+for both validation of the practically of the API server from a joining node's point
+of view and as an authentication method for the node in the bootstrap phase of
+&quot;kubeadm join&quot;. This token is and should be short-lived.</p>
+
+
+<table class="table">
+<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
+<tbody>
+    
+  
+<tr><td><code>-</code> <B>[Required]</B><br/>
+<code>string</code>
+</td>
+<td>
+   <span class="text-muted">No description provided.</span></td>
+</tr>
+<tr><td><code>-</code> <B>[Required]</B><br/>
+<code>string</code>
+</td>
+<td>
+   <span class="text-muted">No description provided.</span></td>
+</tr>
+</tbody>
+</table>
\ No newline at end of file
diff --git a/content/en/docs/reference/config-api/kubelet-config.v1.md b/content/en/docs/reference/config-api/kubelet-config.v1.md
index abaf48ec4bb..407ce5f1a9d 100644
--- a/content/en/docs/reference/config-api/kubelet-config.v1.md
+++ b/content/en/docs/reference/config-api/kubelet-config.v1.md
@@ -169,211 +169,4 @@ credential plugin.</p>
 </tr>
 </tbody>
 </table>
-  
-  
-    
-
-## `FormatOptions`     {#FormatOptions}
-    
-
-**Appears in:**
-
-- [LoggingConfiguration](#LoggingConfiguration)
-
-
-<p>FormatOptions contains options for the different logging formats.</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>json</code> <B>[Required]</B><br/>
-<a href="#JSONOptions"><code>JSONOptions</code></a>
-</td>
-<td>
-   <p>[Alpha] JSON contains options for logging format &quot;json&quot;.
-Only available when the LoggingAlphaOptions feature gate is enabled.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `JSONOptions`     {#JSONOptions}
-    
-
-**Appears in:**
-
-- [FormatOptions](#FormatOptions)
-
-
-<p>JSONOptions contains options for logging format &quot;json&quot;.</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>splitStream</code> <B>[Required]</B><br/>
-<code>bool</code>
-</td>
-<td>
-   <p>[Alpha] SplitStream redirects error messages to stderr while
-info messages go to stdout, with buffering. The default is to write
-both to stdout, without buffering. Only available when
-the LoggingAlphaOptions feature gate is enabled.</p>
-</td>
-</tr>
-<tr><td><code>infoBufferSize</code> <B>[Required]</B><br/>
-<a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/api/resource#QuantityValue"><code>k8s.io/apimachinery/pkg/api/resource.QuantityValue</code></a>
-</td>
-<td>
-   <p>[Alpha] InfoBufferSize sets the size of the info stream when
-using split streams. The default is zero, which disables buffering.
-Only available when the LoggingAlphaOptions feature gate is enabled.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `LogFormatFactory`     {#LogFormatFactory}
-    
-
-
-<p>LogFormatFactory provides support for a certain additional,
-non-default log format.</p>
-
-
-
-
-## `LoggingConfiguration`     {#LoggingConfiguration}
-    
-
-**Appears in:**
-
-- [KubeletConfiguration](#kubelet-config-k8s-io-v1beta1-KubeletConfiguration)
-
-
-<p>LoggingConfiguration contains logging options.</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>format</code> <B>[Required]</B><br/>
-<code>string</code>
-</td>
-<td>
-   <p>Format Flag specifies the structure of log messages.
-default value of format is <code>text</code></p>
-</td>
-</tr>
-<tr><td><code>flushFrequency</code> <B>[Required]</B><br/>
-<a href="https://pkg.go.dev/time#Duration"><code>time.Duration</code></a>
-</td>
-<td>
-   <p>Maximum number of nanoseconds (i.e. 1s = 1000000000) between log
-flushes. Ignored if the selected logging backend writes log
-messages without buffering.</p>
-</td>
-</tr>
-<tr><td><code>verbosity</code> <B>[Required]</B><br/>
-<a href="#VerbosityLevel"><code>VerbosityLevel</code></a>
-</td>
-<td>
-   <p>Verbosity is the threshold that determines which log messages are
-logged. Default is zero which logs only the most important
-messages. Higher values enable additional messages. Error messages
-are always logged.</p>
-</td>
-</tr>
-<tr><td><code>vmodule</code> <B>[Required]</B><br/>
-<a href="#VModuleConfiguration"><code>VModuleConfiguration</code></a>
-</td>
-<td>
-   <p>VModule overrides the verbosity threshold for individual files.
-Only supported for &quot;text&quot; log format.</p>
-</td>
-</tr>
-<tr><td><code>options</code> <B>[Required]</B><br/>
-<a href="#FormatOptions"><code>FormatOptions</code></a>
-</td>
-<td>
-   <p>[Alpha] Options holds additional parameters that are specific
-to the different logging formats. Only the options for the selected
-format get used, but all of them get validated.
-Only available when the LoggingAlphaOptions feature gate is enabled.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `TracingConfiguration`     {#TracingConfiguration}
-    
-
-**Appears in:**
-
-- [KubeletConfiguration](#kubelet-config-k8s-io-v1beta1-KubeletConfiguration)
-
-
-<p>TracingConfiguration provides versioned configuration for OpenTelemetry tracing clients.</p>
-
-
-<table class="table">
-<thead><tr><th width="30%">Field</th><th>Description</th></tr></thead>
-<tbody>
-    
-  
-<tr><td><code>endpoint</code><br/>
-<code>string</code>
-</td>
-<td>
-   <p>Endpoint of the collector this component will report traces to.
-The connection is insecure, and does not currently support TLS.
-Recommended is unset, and endpoint is the otlp grpc default, localhost:4317.</p>
-</td>
-</tr>
-<tr><td><code>samplingRatePerMillion</code><br/>
-<code>int32</code>
-</td>
-<td>
-   <p>SamplingRatePerMillion is the number of samples to collect per million spans.
-Recommended is unset. If unset, sampler respects its parent span's sampling
-rate, but otherwise never samples.</p>
-</td>
-</tr>
-</tbody>
-</table>
-
-## `VModuleConfiguration`     {#VModuleConfiguration}
-    
-(Alias of `[]k8s.io/component-base/logs/api/v1.VModuleItem`)
-
-**Appears in:**
-
-- [LoggingConfiguration](#LoggingConfiguration)
-
-
-<p>VModuleConfiguration is a collection of individual file names or patterns
-and the corresponding verbosity threshold.</p>
-
-
-
-
-## `VerbosityLevel`     {#VerbosityLevel}
-    
-(Alias of `uint32`)
-
-**Appears in:**
-
-- [LoggingConfiguration](#LoggingConfiguration)
-
-
-
-<p>VerbosityLevel represents a klog or logr verbosity threshold.</p>
-
-
+  
\ No newline at end of file
diff --git a/content/en/docs/reference/config-api/kubelet-config.v1alpha1.md b/content/en/docs/reference/config-api/kubelet-config.v1alpha1.md
index 079c36a9329..6082c2f7ecf 100644
--- a/content/en/docs/reference/config-api/kubelet-config.v1alpha1.md
+++ b/content/en/docs/reference/config-api/kubelet-config.v1alpha1.md
@@ -169,6 +169,4 @@ credential plugin.</p>
 </tr>
 </tbody>
 </table>
-  
-  
-    
\ No newline at end of file
+  
\ No newline at end of file
diff --git a/content/en/docs/reference/config-api/kubelet-config.v1beta1.md b/content/en/docs/reference/config-api/kubelet-config.v1beta1.md
index a11c179a58a..b40fb3f5e96 100644
--- a/content/en/docs/reference/config-api/kubelet-config.v1beta1.md
+++ b/content/en/docs/reference/config-api/kubelet-config.v1beta1.md
@@ -262,7 +262,7 @@ Default: 10</p>
 <td>
    <p>eventRecordQPS is the maximum event creations per second. If 0, there
 is no limit enforced. The value cannot be a negative number.
-Default: 5</p>
+Default: 50</p>
 </td>
 </tr>
 <tr><td><code>eventBurst</code><br/>
@@ -273,7 +273,7 @@ Default: 5</p>
 allows event creations to burst to this number, while still not exceeding
 eventRecordQPS. This field canot be a negative number and it is only used
 when eventRecordQPS &gt; 0.
-Default: 10</p>
+Default: 100</p>
 </td>
 </tr>
 <tr><td><code>enableDebuggingHandlers</code><br/>
@@ -290,7 +290,7 @@ Default: true</p>
 <code>bool</code>
 </td>
 <td>
-   <p>enableContentionProfiling enables lock contention profiling, if enableDebuggingHandlers is true.
+   <p>enableContentionProfiling enables block profiling, if enableDebuggingHandlers is true.
 Default: false</p>
 </td>
 </tr>
@@ -529,8 +529,7 @@ resources;</li>
 <li><code>single-numa-node</code>: kubelet only allows pods with a single NUMA alignment
 of CPU and device resources.</li>
 </ul>
-<p>Policies other than &quot;none&quot; require the TopologyManager feature gate to be enabled.
-Default: &quot;none&quot;</p>
+<p>Default: &quot;none&quot;</p>
 </td>
 </tr>
 <tr><td><code>topologyManagerScope</code><br/>
@@ -543,8 +542,7 @@ that topology manager requests and hint providers generate. Valid values include
 <li><code>container</code>: topology policy is applied on a per-container basis.</li>
 <li><code>pod</code>: topology policy is applied on a per-pod basis.</li>
 </ul>
-<p>&quot;pod&quot; scope requires the TopologyManager feature gate to be enabled.
-Default: &quot;container&quot;</p>
+<p>Default: &quot;container&quot;</p>
 </td>
 </tr>
 <tr><td><code>topologyManagerPolicyOptions</code><br/>
@@ -692,7 +690,7 @@ Default: &quot;application/vnd.kubernetes.protobuf&quot;</p>
 </td>
 <td>
    <p>kubeAPIQPS is the QPS to use while talking with kubernetes apiserver.
-Default: 5</p>
+Default: 50</p>
 </td>
 </tr>
 <tr><td><code>kubeAPIBurst</code><br/>
@@ -701,7 +699,7 @@ Default: 5</p>
 <td>
    <p>kubeAPIBurst is the burst to allow while talking with kubernetes API server.
 This field cannot be a negative number.
-Default: 10</p>
+Default: 100</p>
 </td>
 </tr>
 <tr><td><code>serializeImagePulls</code><br/>
@@ -715,6 +713,16 @@ Issue #10959 has more details.
 Default: true</p>
 </td>
 </tr>
+<tr><td><code>maxParallelImagePulls</code><br/>
+<code>int32</code>
+</td>
+<td>
+   <p>MaxParallelImagePulls sets the maximum number of image pulls in parallel.
+This field cannot be set if SerializeImagePulls is true.
+Setting it to nil means no limit.
+Default: nil</p>
+</td>
+</tr>
 <tr><td><code>evictionHard</code><br/>
 <code>map[string]string</code>
 </td>
@@ -953,7 +961,7 @@ Default: &quot;&quot;</p>
 <td>
    <p>systemReservedCgroup helps the kubelet identify absolute name of top level CGroup used
 to enforce <code>systemReserved</code> compute resource reservation for OS system daemons.
-Refer to <a href="https://git.k8s.io/community/contributors/design-proposals/node/node-allocatable.md">Node Allocatable</a>
+Refer to <a href="https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable">Node Allocatable</a>
 doc for more information.
 Default: &quot;&quot;</p>
 </td>
@@ -964,7 +972,7 @@ Default: &quot;&quot;</p>
 <td>
    <p>kubeReservedCgroup helps the kubelet identify absolute name of top level CGroup used
 to enforce <code>KubeReserved</code> compute resource reservation for Kubernetes node system daemons.
-Refer to <a href="https://git.k8s.io/community/contributors/design-proposals/node/node-allocatable.md">Node Allocatable</a>
+Refer to <a href="https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable">Node Allocatable</a>
 doc for more information.
 Default: &quot;&quot;</p>
 </td>
@@ -980,7 +988,7 @@ If <code>none</code> is specified, no other options may be specified.
 When <code>system-reserved</code> is in the list, systemReservedCgroup must be specified.
 When <code>kube-reserved</code> is in the list, kubeReservedCgroup must be specified.
 This field is supported only when <code>cgroupsPerQOS</code> is set to true.
-Refer to <a href="https://git.k8s.io/community/contributors/design-proposals/node/node-allocatable.md">Node Allocatable</a>
+Refer to <a href="https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable">Node Allocatable</a>
 for more information.
 Default: [&quot;pods&quot;]</p>
 </td>
@@ -1042,6 +1050,15 @@ Format: text</p>
 Default: true</p>
 </td>
 </tr>
+<tr><td><code>enableSystemLogQuery</code><br/>
+<code>bool</code>
+</td>
+<td>
+   <p>enableSystemLogQuery enables the node log query feature on the /logs endpoint.
+EnableSystemLogHandler has to be enabled in addition for this feature to work.
+Default: false</p>
+</td>
+</tr>
 <tr><td><code>shutdownGracePeriod</code><br/>
 <a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a>
 </td>
@@ -1143,7 +1160,6 @@ Default: true</p>
 </td>
 <td>
    <p>SeccompDefault enables the use of <code>RuntimeDefault</code> as the default seccomp profile for all workloads.
-This requires the corresponding SeccompDefault feature gate to be enabled as well.
 Default: false</p>
 </td>
 </tr>
@@ -1156,11 +1172,11 @@ when setting the cgroupv2 memory.high value to enforce MemoryQoS.
 Decreasing this factor will set lower high limit for container cgroups and put heavier reclaim pressure
 while increasing will put less reclaim pressure.
 See https://kep.k8s.io/2570 for more details.
-Default: 0.8</p>
+Default: 0.9</p>
 </td>
 </tr>
 <tr><td><code>registerWithTaints</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#taint-v1-core"><code>[]core/v1.Taint</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#taint-v1-core"><code>[]core/v1.Taint</code></a>
 </td>
 <td>
    <p>registerWithTaints are an array of taints to add to a node object when
@@ -1182,7 +1198,8 @@ Default: true</p>
 </td>
 <td>
    <p>Tracing specifies the versioned configuration for OpenTelemetry tracing clients.
-See https://kep.k8s.io/2832 for more details.</p>
+See https://kep.k8s.io/2832 for more details.
+Default: nil</p>
 </td>
 </tr>
 <tr><td><code>localStorageCapacityIsolation</code><br/>
@@ -1199,6 +1216,25 @@ disabled. Once disabled, user should not set request/limit for container's ephem
 Default: true</p>
 </td>
 </tr>
+<tr><td><code>containerRuntimeEndpoint</code> <B>[Required]</B><br/>
+<code>string</code>
+</td>
+<td>
+   <p>ContainerRuntimeEndpoint is the endpoint of container runtime.
+Unix Domain Sockets are supported on Linux, while npipe and tcp endpoints are supported on Windows.
+Examples:'unix:///path/to/runtime.sock', 'npipe:////./pipe/runtime'</p>
+</td>
+</tr>
+<tr><td><code>imageServiceEndpoint</code><br/>
+<code>string</code>
+</td>
+<td>
+   <p>ImageServiceEndpoint is the endpoint of container image service.
+Unix Domain Socket are supported on Linux, while npipe and tcp endpoints are supported on Windows.
+Examples:'unix:///path/to/runtime.sock', 'npipe:////./pipe/runtime'.
+If not specified, the value in containerRuntimeEndpoint is used.</p>
+</td>
+</tr>
 </tbody>
 </table>
 
@@ -1220,7 +1256,7 @@ It exists in the kubeletconfig API group because it is classified as a versioned
     
   
 <tr><td><code>source</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#nodeconfigsource-v1-core"><code>core/v1.NodeConfigSource</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#nodeconfigsource-v1-core"><code>core/v1.NodeConfigSource</code></a>
 </td>
 <td>
    <p>source is the source that we are serializing.</p>
@@ -1581,7 +1617,7 @@ and groups corresponding to the Organization in the client certificate.</p>
    <span class="text-muted">No description provided.</span></td>
 </tr>
 <tr><td><code>limits</code> <B>[Required]</B><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#resourcelist-v1-core"><code>core/v1.ResourceList</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#resourcelist-v1-core"><code>core/v1.ResourceList</code></a>
 </td>
 <td>
    <span class="text-muted">No description provided.</span></td>

From 8895af3e9b8a392f5b14292464375573a80fc572 Mon Sep 17 00:00:00 2001
From: Qiming Teng <tengqm@outlook.com>
Date: Wed, 12 Apr 2023 08:26:09 +0800
Subject: [PATCH 163/272] Update component reference for 1.27

---
 .../kube-apiserver.md                         | 24 +++++++++++++++----
 .../kube-controller-manager.md                |  6 ++---
 .../kube-proxy.md                             |  2 +-
 .../kube-scheduler.md                         |  4 ++--
 .../generated/kubeadm_config_images_list.md   |  2 +-
 .../generated/kubeadm_config_images_pull.md   |  2 +-
 .../kubeadm/generated/kubeadm_init.md         |  2 +-
 .../generated/kubeadm_init_phase_addon_all.md |  2 +-
 .../kubeadm_init_phase_addon_coredns.md       |  2 +-
 .../kubeadm_init_phase_control-plane_all.md   |  2 +-
 ...eadm_init_phase_control-plane_apiserver.md |  2 +-
 .../generated/kubeadm_init_phase_preflight.md |  7 ++++++
 .../kubeadm_init_phase_upload-config_all.md   |  7 ++++++
 ...ubeadm_init_phase_upload-config_kubeadm.md |  7 ++++++
 ...ubeadm_init_phase_upload-config_kubelet.md |  7 ++++++
 .../generated/kubeadm_kubeconfig_user.md      |  3 +++
 .../generated/kubeadm_upgrade_apply.md        |  2 +-
 .../kubeadm/generated/kubeadm_upgrade_plan.md |  2 +-
 18 files changed, 65 insertions(+), 20 deletions(-)

diff --git a/content/en/docs/reference/command-line-tools-reference/kube-apiserver.md b/content/en/docs/reference/command-line-tools-reference/kube-apiserver.md
index af3687662e6..8aa21abe024 100644
--- a/content/en/docs/reference/command-line-tools-reference/kube-apiserver.md
+++ b/content/en/docs/reference/command-line-tools-reference/kube-apiserver.md
@@ -421,14 +421,21 @@ kube-apiserver [flags]
 <td colspan="2">--contention-profiling</td>
 </tr>
 <tr>
-<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Enable lock contention profiling, if profiling is enabled</p></td>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Enable block profiling, if profiling is enabled</p></td>
 </tr>
 
 <tr>
 <td colspan="2">--cors-allowed-origins strings</td>
 </tr>
 <tr>
-<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>List of allowed origins for CORS, comma separated.  An allowed origin can be a regular expression to support subdomain matching. If this list is empty CORS will not be enabled.</p></td>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>List of allowed origins for CORS, comma separated. An allowed origin can be a regular expression to support subdomain matching. If this list is empty CORS will not be enabled. Please ensure each expression matches the entire hostname by anchoring to the start with '^' or including the '//' prefix, and by anchoring to the end with '$' or including the ':' port separator suffix. Examples of valid expressions are '//example.com(:|$)' and '^https://example.com(:|$)'</p></td>
+</tr>
+
+<tr>
+<td colspan="2">--debug-socket-path string</td>
+</tr>
+<tr>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Use an unprotected (no authn/authz) unix-domain socket for profiling with the given path</p></td>
 </tr>
 
 <tr>
@@ -456,7 +463,7 @@ kube-apiserver [flags]
 <td colspan="2">--disable-admission-plugins strings</td>
 </tr>
 <tr>
-<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>admission plugins that should be disabled although they are in the default enabled plugins list (NamespaceLifecycle, LimitRanger, ServiceAccount, TaintNodesByCondition, PodSecurity, Priority, DefaultTolerationSeconds, DefaultStorageClass, StorageObjectInUseProtection, PersistentVolumeClaimResize, RuntimeClass, CertificateApproval, CertificateSigning, CertificateSubjectRestriction, DefaultIngressClass, MutatingAdmissionWebhook, ValidatingAdmissionPolicy, ValidatingAdmissionWebhook, ResourceQuota). Comma-delimited list of admission plugins: AlwaysAdmit, AlwaysDeny, AlwaysPullImages, CertificateApproval, CertificateSigning, CertificateSubjectRestriction, DefaultIngressClass, DefaultStorageClass, DefaultTolerationSeconds, DenyServiceExternalIPs, EventRateLimit, ExtendedResourceToleration, ImagePolicyWebhook, LimitPodHardAntiAffinityTopology, LimitRanger, MutatingAdmissionWebhook, NamespaceAutoProvision, NamespaceExists, NamespaceLifecycle, NodeRestriction, OwnerReferencesPermissionEnforcement, PersistentVolumeClaimResize, PersistentVolumeLabel, PodNodeSelector, PodSecurity, PodTolerationRestriction, Priority, ResourceQuota, RuntimeClass, SecurityContextDeny, ServiceAccount, StorageObjectInUseProtection, TaintNodesByCondition, ValidatingAdmissionPolicy, ValidatingAdmissionWebhook. The order of plugins in this flag does not matter.</p></td>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>admission plugins that should be disabled although they are in the default enabled plugins list (NamespaceLifecycle, LimitRanger, ServiceAccount, TaintNodesByCondition, PodSecurity, Priority, DefaultTolerationSeconds, DefaultStorageClass, StorageObjectInUseProtection, PersistentVolumeClaimResize, RuntimeClass, CertificateApproval, CertificateSigning, ClusterTrustBundleAttest, CertificateSubjectRestriction, DefaultIngressClass, MutatingAdmissionWebhook, ValidatingAdmissionPolicy, ValidatingAdmissionWebhook, ResourceQuota). Comma-delimited list of admission plugins: AlwaysAdmit, AlwaysDeny, AlwaysPullImages, CertificateApproval, CertificateSigning, CertificateSubjectRestriction, ClusterTrustBundleAttest, DefaultIngressClass, DefaultStorageClass, DefaultTolerationSeconds, DenyServiceExternalIPs, EventRateLimit, ExtendedResourceToleration, ImagePolicyWebhook, LimitPodHardAntiAffinityTopology, LimitRanger, MutatingAdmissionWebhook, NamespaceAutoProvision, NamespaceExists, NamespaceLifecycle, NodeRestriction, OwnerReferencesPermissionEnforcement, PersistentVolumeClaimResize, PersistentVolumeLabel, PodNodeSelector, PodSecurity, PodTolerationRestriction, Priority, ResourceQuota, RuntimeClass, SecurityContextDeny, ServiceAccount, StorageObjectInUseProtection, TaintNodesByCondition, ValidatingAdmissionPolicy, ValidatingAdmissionWebhook. The order of plugins in this flag does not matter.</p></td>
 </tr>
 
 <tr>
@@ -477,7 +484,7 @@ kube-apiserver [flags]
 <td colspan="2">--enable-admission-plugins strings</td>
 </tr>
 <tr>
-<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>admission plugins that should be enabled in addition to default enabled ones (NamespaceLifecycle, LimitRanger, ServiceAccount, TaintNodesByCondition, PodSecurity, Priority, DefaultTolerationSeconds, DefaultStorageClass, StorageObjectInUseProtection, PersistentVolumeClaimResize, RuntimeClass, CertificateApproval, CertificateSigning, CertificateSubjectRestriction, DefaultIngressClass, MutatingAdmissionWebhook, ValidatingAdmissionPolicy, ValidatingAdmissionWebhook, ResourceQuota). Comma-delimited list of admission plugins: AlwaysAdmit, AlwaysDeny, AlwaysPullImages, CertificateApproval, CertificateSigning, CertificateSubjectRestriction, DefaultIngressClass, DefaultStorageClass, DefaultTolerationSeconds, DenyServiceExternalIPs, EventRateLimit, ExtendedResourceToleration, ImagePolicyWebhook, LimitPodHardAntiAffinityTopology, LimitRanger, MutatingAdmissionWebhook, NamespaceAutoProvision, NamespaceExists, NamespaceLifecycle, NodeRestriction, OwnerReferencesPermissionEnforcement, PersistentVolumeClaimResize, PersistentVolumeLabel, PodNodeSelector, PodSecurity, PodTolerationRestriction, Priority, ResourceQuota, RuntimeClass, SecurityContextDeny, ServiceAccount, StorageObjectInUseProtection, TaintNodesByCondition, ValidatingAdmissionPolicy, ValidatingAdmissionWebhook. The order of plugins in this flag does not matter.</p></td>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>admission plugins that should be enabled in addition to default enabled ones (NamespaceLifecycle, LimitRanger, ServiceAccount, TaintNodesByCondition, PodSecurity, Priority, DefaultTolerationSeconds, DefaultStorageClass, StorageObjectInUseProtection, PersistentVolumeClaimResize, RuntimeClass, CertificateApproval, CertificateSigning, ClusterTrustBundleAttest, CertificateSubjectRestriction, DefaultIngressClass, MutatingAdmissionWebhook, ValidatingAdmissionPolicy, ValidatingAdmissionWebhook, ResourceQuota). Comma-delimited list of admission plugins: AlwaysAdmit, AlwaysDeny, AlwaysPullImages, CertificateApproval, CertificateSigning, CertificateSubjectRestriction, ClusterTrustBundleAttest, DefaultIngressClass, DefaultStorageClass, DefaultTolerationSeconds, DenyServiceExternalIPs, EventRateLimit, ExtendedResourceToleration, ImagePolicyWebhook, LimitPodHardAntiAffinityTopology, LimitRanger, MutatingAdmissionWebhook, NamespaceAutoProvision, NamespaceExists, NamespaceLifecycle, NodeRestriction, OwnerReferencesPermissionEnforcement, PersistentVolumeClaimResize, PersistentVolumeLabel, PodNodeSelector, PodSecurity, PodTolerationRestriction, Priority, ResourceQuota, RuntimeClass, SecurityContextDeny, ServiceAccount, StorageObjectInUseProtection, TaintNodesByCondition, ValidatingAdmissionPolicy, ValidatingAdmissionWebhook. The order of plugins in this flag does not matter.</p></td>
 </tr>
 
 <tr>
@@ -624,7 +631,7 @@ kube-apiserver [flags]
 <td colspan="2">--feature-gates &lt;comma-separated 'key=True|False' pairs&gt;</td>
 </tr>
 <tr>
-<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for alpha/experimental features. Options are:<br/>APIListChunking=true|false (BETA - default=true)<br/>APIPriorityAndFairness=true|false (BETA - default=true)<br/>APIResponseCompression=true|false (BETA - default=true)<br/>APISelfSubjectReview=true|false (ALPHA - default=false)<br/>APIServerIdentity=true|false (BETA - default=true)<br/>APIServerTracing=true|false (ALPHA - default=false)<br/>AggregatedDiscoveryEndpoint=true|false (ALPHA - default=false)<br/>AllAlpha=true|false (ALPHA - default=false)<br/>AllBeta=true|false (BETA - default=false)<br/>AnyVolumeDataSource=true|false (BETA - default=true)<br/>AppArmor=true|false (BETA - default=true)<br/>CPUManagerPolicyAlphaOptions=true|false (ALPHA - default=false)<br/>CPUManagerPolicyBetaOptions=true|false (BETA - default=true)<br/>CPUManagerPolicyOptions=true|false (BETA - default=true)<br/>CSIMigrationPortworx=true|false (BETA - default=false)<br/>CSIMigrationRBD=true|false (ALPHA - default=false)<br/>CSINodeExpandSecret=true|false (ALPHA - default=false)<br/>CSIVolumeHealth=true|false (ALPHA - default=false)<br/>ComponentSLIs=true|false (ALPHA - default=false)<br/>ContainerCheckpoint=true|false (ALPHA - default=false)<br/>ContextualLogging=true|false (ALPHA - default=false)<br/>CronJobTimeZone=true|false (BETA - default=true)<br/>CrossNamespaceVolumeDataSource=true|false (ALPHA - default=false)<br/>CustomCPUCFSQuotaPeriod=true|false (ALPHA - default=false)<br/>CustomResourceValidationExpressions=true|false (BETA - default=true)<br/>DisableCloudProviders=true|false (ALPHA - default=false)<br/>DisableKubeletCloudCredentialProviders=true|false (ALPHA - default=false)<br/>DownwardAPIHugePages=true|false (BETA - default=true)<br/>DynamicResourceAllocation=true|false (ALPHA - default=false)<br/>EventedPLEG=true|false (ALPHA - default=false)<br/>ExpandedDNSConfig=true|false (BETA - default=true)<br/>ExperimentalHostUserNamespaceDefaulting=true|false (BETA - default=false)<br/>GRPCContainerProbe=true|false (BETA - default=true)<br/>GracefulNodeShutdown=true|false (BETA - default=true)<br/>GracefulNodeShutdownBasedOnPodPriority=true|false (BETA - default=true)<br/>HPAContainerMetrics=true|false (ALPHA - default=false)<br/>HPAScaleToZero=true|false (ALPHA - default=false)<br/>HonorPVReclaimPolicy=true|false (ALPHA - default=false)<br/>IPTablesOwnershipCleanup=true|false (ALPHA - default=false)<br/>InTreePluginAWSUnregister=true|false (ALPHA - default=false)<br/>InTreePluginAzureDiskUnregister=true|false (ALPHA - default=false)<br/>InTreePluginAzureFileUnregister=true|false (ALPHA - default=false)<br/>InTreePluginGCEUnregister=true|false (ALPHA - default=false)<br/>InTreePluginOpenStackUnregister=true|false (ALPHA - default=false)<br/>InTreePluginPortworxUnregister=true|false (ALPHA - default=false)<br/>InTreePluginRBDUnregister=true|false (ALPHA - default=false)<br/>InTreePluginvSphereUnregister=true|false (ALPHA - default=false)<br/>JobMutableNodeSchedulingDirectives=true|false (BETA - default=true)<br/>JobPodFailurePolicy=true|false (BETA - default=true)<br/>JobReadyPods=true|false (BETA - default=true)<br/>KMSv2=true|false (ALPHA - default=false)<br/>KubeletInUserNamespace=true|false (ALPHA - default=false)<br/>KubeletPodResources=true|false (BETA - default=true)<br/>KubeletPodResourcesGetAllocatable=true|false (BETA - default=true)<br/>KubeletTracing=true|false (ALPHA - default=false)<br/>LegacyServiceAccountTokenTracking=true|false (ALPHA - default=false)<br/>LocalStorageCapacityIsolationFSQuotaMonitoring=true|false (ALPHA - default=false)<br/>LogarithmicScaleDown=true|false (BETA - default=true)<br/>LoggingAlphaOptions=true|false (ALPHA - default=false)<br/>LoggingBetaOptions=true|false (BETA - default=true)<br/>MatchLabelKeysInPodTopologySpread=true|false (ALPHA - default=false)<br/>MaxUnavailableStatefulSet=true|false (ALPHA - default=false)<br/>MemoryManager=true|false (BETA - default=true)<br/>MemoryQoS=true|false (ALPHA - default=false)<br/>MinDomainsInPodTopologySpread=true|false (BETA - default=false)<br/>MinimizeIPTablesRestore=true|false (ALPHA - default=false)<br/>MultiCIDRRangeAllocator=true|false (ALPHA - default=false)<br/>NetworkPolicyStatus=true|false (ALPHA - default=false)<br/>NodeInclusionPolicyInPodTopologySpread=true|false (BETA - default=true)<br/>NodeOutOfServiceVolumeDetach=true|false (BETA - default=true)<br/>NodeSwap=true|false (ALPHA - default=false)<br/>OpenAPIEnums=true|false (BETA - default=true)<br/>OpenAPIV3=true|false (BETA - default=true)<br/>PDBUnhealthyPodEvictionPolicy=true|false (ALPHA - default=false)<br/>PodAndContainerStatsFromCRI=true|false (ALPHA - default=false)<br/>PodDeletionCost=true|false (BETA - default=true)<br/>PodDisruptionConditions=true|false (BETA - default=true)<br/>PodHasNetworkCondition=true|false (ALPHA - default=false)<br/>PodSchedulingReadiness=true|false (ALPHA - default=false)<br/>ProbeTerminationGracePeriod=true|false (BETA - default=true)<br/>ProcMountType=true|false (ALPHA - default=false)<br/>ProxyTerminatingEndpoints=true|false (BETA - default=true)<br/>QOSReserved=true|false (ALPHA - default=false)<br/>ReadWriteOncePod=true|false (ALPHA - default=false)<br/>RecoverVolumeExpansionFailure=true|false (ALPHA - default=false)<br/>RemainingItemCount=true|false (BETA - default=true)<br/>RetroactiveDefaultStorageClass=true|false (BETA - default=true)<br/>RotateKubeletServerCertificate=true|false (BETA - default=true)<br/>SELinuxMountReadWriteOncePod=true|false (ALPHA - default=false)<br/>SeccompDefault=true|false (BETA - default=true)<br/>ServerSideFieldValidation=true|false (BETA - default=true)<br/>SizeMemoryBackedVolumes=true|false (BETA - default=true)<br/>StatefulSetAutoDeletePVC=true|false (ALPHA - default=false)<br/>StatefulSetStartOrdinal=true|false (ALPHA - default=false)<br/>StorageVersionAPI=true|false (ALPHA - default=false)<br/>StorageVersionHash=true|false (BETA - default=true)<br/>TopologyAwareHints=true|false (BETA - default=true)<br/>TopologyManager=true|false (BETA - default=true)<br/>TopologyManagerPolicyAlphaOptions=true|false (ALPHA - default=false)<br/>TopologyManagerPolicyBetaOptions=true|false (BETA - default=false)<br/>TopologyManagerPolicyOptions=true|false (ALPHA - default=false)<br/>UserNamespacesStatelessPodsSupport=true|false (ALPHA - default=false)<br/>ValidatingAdmissionPolicy=true|false (ALPHA - default=false)<br/>VolumeCapacityPriority=true|false (ALPHA - default=false)<br/>WinDSR=true|false (ALPHA - default=false)<br/>WinOverlay=true|false (BETA - default=true)<br/>WindowsHostNetwork=true|false (ALPHA - default=true)</p></td>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for alpha/experimental features. Options are:<br/>APIListChunking=true|false (BETA - default=true)<br/>APIPriorityAndFairness=true|false (BETA - default=true)<br/>APIResponseCompression=true|false (BETA - default=true)<br/>APISelfSubjectReview=true|false (BETA - default=true)<br/>APIServerIdentity=true|false (BETA - default=true)<br/>APIServerTracing=true|false (BETA - default=true)<br/>AdmissionWebhookMatchConditions=true|false (ALPHA - default=false)<br/>AggregatedDiscoveryEndpoint=true|false (BETA - default=true)<br/>AllAlpha=true|false (ALPHA - default=false)<br/>AllBeta=true|false (BETA - default=false)<br/>AnyVolumeDataSource=true|false (BETA - default=true)<br/>AppArmor=true|false (BETA - default=true)<br/>CPUManagerPolicyAlphaOptions=true|false (ALPHA - default=false)<br/>CPUManagerPolicyBetaOptions=true|false (BETA - default=true)<br/>CPUManagerPolicyOptions=true|false (BETA - default=true)<br/>CSIMigrationPortworx=true|false (BETA - default=false)<br/>CSIMigrationRBD=true|false (ALPHA - default=false)<br/>CSINodeExpandSecret=true|false (BETA - default=true)<br/>CSIVolumeHealth=true|false (ALPHA - default=false)<br/>CloudControllerManagerWebhook=true|false (ALPHA - default=false)<br/>CloudDualStackNodeIPs=true|false (ALPHA - default=false)<br/>ClusterTrustBundle=true|false (ALPHA - default=false)<br/>ComponentSLIs=true|false (BETA - default=true)<br/>ContainerCheckpoint=true|false (ALPHA - default=false)<br/>ContextualLogging=true|false (ALPHA - default=false)<br/>CrossNamespaceVolumeDataSource=true|false (ALPHA - default=false)<br/>CustomCPUCFSQuotaPeriod=true|false (ALPHA - default=false)<br/>CustomResourceValidationExpressions=true|false (BETA - default=true)<br/>DisableCloudProviders=true|false (ALPHA - default=false)<br/>DisableKubeletCloudCredentialProviders=true|false (ALPHA - default=false)<br/>DynamicResourceAllocation=true|false (ALPHA - default=false)<br/>ElasticIndexedJob=true|false (BETA - default=true)<br/>EventedPLEG=true|false (BETA - default=false)<br/>ExpandedDNSConfig=true|false (BETA - default=true)<br/>ExperimentalHostUserNamespaceDefaulting=true|false (BETA - default=false)<br/>GracefulNodeShutdown=true|false (BETA - default=true)<br/>GracefulNodeShutdownBasedOnPodPriority=true|false (BETA - default=true)<br/>HPAContainerMetrics=true|false (BETA - default=true)<br/>HPAScaleToZero=true|false (ALPHA - default=false)<br/>HonorPVReclaimPolicy=true|false (ALPHA - default=false)<br/>IPTablesOwnershipCleanup=true|false (BETA - default=true)<br/>InPlacePodVerticalScaling=true|false (ALPHA - default=false)<br/>InTreePluginAWSUnregister=true|false (ALPHA - default=false)<br/>InTreePluginAzureDiskUnregister=true|false (ALPHA - default=false)<br/>InTreePluginAzureFileUnregister=true|false (ALPHA - default=false)<br/>InTreePluginGCEUnregister=true|false (ALPHA - default=false)<br/>InTreePluginOpenStackUnregister=true|false (ALPHA - default=false)<br/>InTreePluginPortworxUnregister=true|false (ALPHA - default=false)<br/>InTreePluginRBDUnregister=true|false (ALPHA - default=false)<br/>InTreePluginvSphereUnregister=true|false (ALPHA - default=false)<br/>JobPodFailurePolicy=true|false (BETA - default=true)<br/>JobReadyPods=true|false (BETA - default=true)<br/>KMSv2=true|false (BETA - default=true)<br/>KubeletInUserNamespace=true|false (ALPHA - default=false)<br/>KubeletPodResources=true|false (BETA - default=true)<br/>KubeletPodResourcesDynamicResources=true|false (ALPHA - default=false)<br/>KubeletPodResourcesGet=true|false (ALPHA - default=false)<br/>KubeletPodResourcesGetAllocatable=true|false (BETA - default=true)<br/>KubeletTracing=true|false (BETA - default=true)<br/>LegacyServiceAccountTokenTracking=true|false (BETA - default=true)<br/>LocalStorageCapacityIsolationFSQuotaMonitoring=true|false (ALPHA - default=false)<br/>LogarithmicScaleDown=true|false (BETA - default=true)<br/>LoggingAlphaOptions=true|false (ALPHA - default=false)<br/>LoggingBetaOptions=true|false (BETA - default=true)<br/>MatchLabelKeysInPodTopologySpread=true|false (BETA - default=true)<br/>MaxUnavailableStatefulSet=true|false (ALPHA - default=false)<br/>MemoryManager=true|false (BETA - default=true)<br/>MemoryQoS=true|false (ALPHA - default=false)<br/>MinDomainsInPodTopologySpread=true|false (BETA - default=true)<br/>MinimizeIPTablesRestore=true|false (BETA - default=true)<br/>MultiCIDRRangeAllocator=true|false (ALPHA - default=false)<br/>MultiCIDRServiceAllocator=true|false (ALPHA - default=false)<br/>NetworkPolicyStatus=true|false (ALPHA - default=false)<br/>NewVolumeManagerReconstruction=true|false (BETA - default=true)<br/>NodeInclusionPolicyInPodTopologySpread=true|false (BETA - default=true)<br/>NodeLogQuery=true|false (ALPHA - default=false)<br/>NodeOutOfServiceVolumeDetach=true|false (BETA - default=true)<br/>NodeSwap=true|false (ALPHA - default=false)<br/>OpenAPIEnums=true|false (BETA - default=true)<br/>PDBUnhealthyPodEvictionPolicy=true|false (BETA - default=true)<br/>PodAndContainerStatsFromCRI=true|false (ALPHA - default=false)<br/>PodDeletionCost=true|false (BETA - default=true)<br/>PodDisruptionConditions=true|false (BETA - default=true)<br/>PodHasNetworkCondition=true|false (ALPHA - default=false)<br/>PodSchedulingReadiness=true|false (BETA - default=true)<br/>ProbeTerminationGracePeriod=true|false (BETA - default=true)<br/>ProcMountType=true|false (ALPHA - default=false)<br/>ProxyTerminatingEndpoints=true|false (BETA - default=true)<br/>QOSReserved=true|false (ALPHA - default=false)<br/>ReadWriteOncePod=true|false (BETA - default=true)<br/>RecoverVolumeExpansionFailure=true|false (ALPHA - default=false)<br/>RemainingItemCount=true|false (BETA - default=true)<br/>RetroactiveDefaultStorageClass=true|false (BETA - default=true)<br/>RotateKubeletServerCertificate=true|false (BETA - default=true)<br/>SELinuxMountReadWriteOncePod=true|false (BETA - default=true)<br/>SecurityContextDeny=true|false (ALPHA - default=false)<br/>ServiceNodePortStaticSubrange=true|false (ALPHA - default=false)<br/>SizeMemoryBackedVolumes=true|false (BETA - default=true)<br/>StableLoadBalancerNodeSet=true|false (BETA - default=true)<br/>StatefulSetAutoDeletePVC=true|false (BETA - default=true)<br/>StatefulSetStartOrdinal=true|false (BETA - default=true)<br/>StorageVersionAPI=true|false (ALPHA - default=false)<br/>StorageVersionHash=true|false (BETA - default=true)<br/>TopologyAwareHints=true|false (BETA - default=true)<br/>TopologyManagerPolicyAlphaOptions=true|false (ALPHA - default=false)<br/>TopologyManagerPolicyBetaOptions=true|false (BETA - default=false)<br/>TopologyManagerPolicyOptions=true|false (ALPHA - default=false)<br/>UserNamespacesStatelessPodsSupport=true|false (ALPHA - default=false)<br/>ValidatingAdmissionPolicy=true|false (ALPHA - default=false)<br/>VolumeCapacityPriority=true|false (ALPHA - default=false)<br/>WatchList=true|false (ALPHA - default=false)<br/>WinDSR=true|false (ALPHA - default=false)<br/>WinOverlay=true|false (BETA - default=true)<br/>WindowsHostNetwork=true|false (ALPHA - default=true)</p></td>
 </tr>
 
 <tr>
@@ -984,6 +991,13 @@ kube-apiserver [flags]
 <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>If true the HTTP Server will continue listening until all non long running request(s) in flight have been drained, during this window all incoming requests will be rejected with a status code 429 and a 'Retry-After' response header, in addition 'Connection: close' response header is set in order to tear down the TCP connection when idle.</p></td>
 </tr>
 
+<tr>
+<td colspan="2">--shutdown-watch-termination-grace-period duration</td>
+</tr>
+<tr>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>This option, if set, represents the maximum amount of grace period the apiserver will wait for active watch request(s) to drain during the graceful server shutdown window.</p></td>
+</tr>
+
 <tr>
 <td colspan="2">--storage-backend string</td>
 </tr>
diff --git a/content/en/docs/reference/command-line-tools-reference/kube-controller-manager.md b/content/en/docs/reference/command-line-tools-reference/kube-controller-manager.md
index 0d448987d06..98316ac6851 100644
--- a/content/en/docs/reference/command-line-tools-reference/kube-controller-manager.md
+++ b/content/en/docs/reference/command-line-tools-reference/kube-controller-manager.md
@@ -369,7 +369,7 @@ kube-controller-manager [flags]
 <td colspan="2">--contention-profiling</td>
 </tr>
 <tr>
-<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Enable lock contention profiling, if profiling is enabled</p></td>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Enable block profiling, if profiling is enabled</p></td>
 </tr>
 
 <tr>
@@ -453,7 +453,7 @@ kube-controller-manager [flags]
 <td colspan="2">--feature-gates &lt;comma-separated 'key=True|False' pairs&gt;</td>
 </tr>
 <tr>
-<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for alpha/experimental features. Options are:<br/>APIListChunking=true|false (BETA - default=true)<br/>APIPriorityAndFairness=true|false (BETA - default=true)<br/>APIResponseCompression=true|false (BETA - default=true)<br/>APISelfSubjectReview=true|false (ALPHA - default=false)<br/>APIServerIdentity=true|false (BETA - default=true)<br/>APIServerTracing=true|false (ALPHA - default=false)<br/>AggregatedDiscoveryEndpoint=true|false (ALPHA - default=false)<br/>AllAlpha=true|false (ALPHA - default=false)<br/>AllBeta=true|false (BETA - default=false)<br/>AnyVolumeDataSource=true|false (BETA - default=true)<br/>AppArmor=true|false (BETA - default=true)<br/>CPUManagerPolicyAlphaOptions=true|false (ALPHA - default=false)<br/>CPUManagerPolicyBetaOptions=true|false (BETA - default=true)<br/>CPUManagerPolicyOptions=true|false (BETA - default=true)<br/>CSIMigrationPortworx=true|false (BETA - default=false)<br/>CSIMigrationRBD=true|false (ALPHA - default=false)<br/>CSINodeExpandSecret=true|false (ALPHA - default=false)<br/>CSIVolumeHealth=true|false (ALPHA - default=false)<br/>ComponentSLIs=true|false (ALPHA - default=false)<br/>ContainerCheckpoint=true|false (ALPHA - default=false)<br/>ContextualLogging=true|false (ALPHA - default=false)<br/>CronJobTimeZone=true|false (BETA - default=true)<br/>CrossNamespaceVolumeDataSource=true|false (ALPHA - default=false)<br/>CustomCPUCFSQuotaPeriod=true|false (ALPHA - default=false)<br/>CustomResourceValidationExpressions=true|false (BETA - default=true)<br/>DisableCloudProviders=true|false (ALPHA - default=false)<br/>DisableKubeletCloudCredentialProviders=true|false (ALPHA - default=false)<br/>DownwardAPIHugePages=true|false (BETA - default=true)<br/>DynamicResourceAllocation=true|false (ALPHA - default=false)<br/>EventedPLEG=true|false (ALPHA - default=false)<br/>ExpandedDNSConfig=true|false (BETA - default=true)<br/>ExperimentalHostUserNamespaceDefaulting=true|false (BETA - default=false)<br/>GRPCContainerProbe=true|false (BETA - default=true)<br/>GracefulNodeShutdown=true|false (BETA - default=true)<br/>GracefulNodeShutdownBasedOnPodPriority=true|false (BETA - default=true)<br/>HPAContainerMetrics=true|false (ALPHA - default=false)<br/>HPAScaleToZero=true|false (ALPHA - default=false)<br/>HonorPVReclaimPolicy=true|false (ALPHA - default=false)<br/>IPTablesOwnershipCleanup=true|false (ALPHA - default=false)<br/>InTreePluginAWSUnregister=true|false (ALPHA - default=false)<br/>InTreePluginAzureDiskUnregister=true|false (ALPHA - default=false)<br/>InTreePluginAzureFileUnregister=true|false (ALPHA - default=false)<br/>InTreePluginGCEUnregister=true|false (ALPHA - default=false)<br/>InTreePluginOpenStackUnregister=true|false (ALPHA - default=false)<br/>InTreePluginPortworxUnregister=true|false (ALPHA - default=false)<br/>InTreePluginRBDUnregister=true|false (ALPHA - default=false)<br/>InTreePluginvSphereUnregister=true|false (ALPHA - default=false)<br/>JobMutableNodeSchedulingDirectives=true|false (BETA - default=true)<br/>JobPodFailurePolicy=true|false (BETA - default=true)<br/>JobReadyPods=true|false (BETA - default=true)<br/>KMSv2=true|false (ALPHA - default=false)<br/>KubeletInUserNamespace=true|false (ALPHA - default=false)<br/>KubeletPodResources=true|false (BETA - default=true)<br/>KubeletPodResourcesGetAllocatable=true|false (BETA - default=true)<br/>KubeletTracing=true|false (ALPHA - default=false)<br/>LegacyServiceAccountTokenTracking=true|false (ALPHA - default=false)<br/>LocalStorageCapacityIsolationFSQuotaMonitoring=true|false (ALPHA - default=false)<br/>LogarithmicScaleDown=true|false (BETA - default=true)<br/>LoggingAlphaOptions=true|false (ALPHA - default=false)<br/>LoggingBetaOptions=true|false (BETA - default=true)<br/>MatchLabelKeysInPodTopologySpread=true|false (ALPHA - default=false)<br/>MaxUnavailableStatefulSet=true|false (ALPHA - default=false)<br/>MemoryManager=true|false (BETA - default=true)<br/>MemoryQoS=true|false (ALPHA - default=false)<br/>MinDomainsInPodTopologySpread=true|false (BETA - default=false)<br/>MinimizeIPTablesRestore=true|false (ALPHA - default=false)<br/>MultiCIDRRangeAllocator=true|false (ALPHA - default=false)<br/>NetworkPolicyStatus=true|false (ALPHA - default=false)<br/>NodeInclusionPolicyInPodTopologySpread=true|false (BETA - default=true)<br/>NodeOutOfServiceVolumeDetach=true|false (BETA - default=true)<br/>NodeSwap=true|false (ALPHA - default=false)<br/>OpenAPIEnums=true|false (BETA - default=true)<br/>OpenAPIV3=true|false (BETA - default=true)<br/>PDBUnhealthyPodEvictionPolicy=true|false (ALPHA - default=false)<br/>PodAndContainerStatsFromCRI=true|false (ALPHA - default=false)<br/>PodDeletionCost=true|false (BETA - default=true)<br/>PodDisruptionConditions=true|false (BETA - default=true)<br/>PodHasNetworkCondition=true|false (ALPHA - default=false)<br/>PodSchedulingReadiness=true|false (ALPHA - default=false)<br/>ProbeTerminationGracePeriod=true|false (BETA - default=true)<br/>ProcMountType=true|false (ALPHA - default=false)<br/>ProxyTerminatingEndpoints=true|false (BETA - default=true)<br/>QOSReserved=true|false (ALPHA - default=false)<br/>ReadWriteOncePod=true|false (ALPHA - default=false)<br/>RecoverVolumeExpansionFailure=true|false (ALPHA - default=false)<br/>RemainingItemCount=true|false (BETA - default=true)<br/>RetroactiveDefaultStorageClass=true|false (BETA - default=true)<br/>RotateKubeletServerCertificate=true|false (BETA - default=true)<br/>SELinuxMountReadWriteOncePod=true|false (ALPHA - default=false)<br/>SeccompDefault=true|false (BETA - default=true)<br/>ServerSideFieldValidation=true|false (BETA - default=true)<br/>SizeMemoryBackedVolumes=true|false (BETA - default=true)<br/>StatefulSetAutoDeletePVC=true|false (ALPHA - default=false)<br/>StatefulSetStartOrdinal=true|false (ALPHA - default=false)<br/>StorageVersionAPI=true|false (ALPHA - default=false)<br/>StorageVersionHash=true|false (BETA - default=true)<br/>TopologyAwareHints=true|false (BETA - default=true)<br/>TopologyManager=true|false (BETA - default=true)<br/>TopologyManagerPolicyAlphaOptions=true|false (ALPHA - default=false)<br/>TopologyManagerPolicyBetaOptions=true|false (BETA - default=false)<br/>TopologyManagerPolicyOptions=true|false (ALPHA - default=false)<br/>UserNamespacesStatelessPodsSupport=true|false (ALPHA - default=false)<br/>ValidatingAdmissionPolicy=true|false (ALPHA - default=false)<br/>VolumeCapacityPriority=true|false (ALPHA - default=false)<br/>WinDSR=true|false (ALPHA - default=false)<br/>WinOverlay=true|false (BETA - default=true)<br/>WindowsHostNetwork=true|false (ALPHA - default=true)</p></td>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for alpha/experimental features. Options are:<br/>APIListChunking=true|false (BETA - default=true)<br/>APIPriorityAndFairness=true|false (BETA - default=true)<br/>APIResponseCompression=true|false (BETA - default=true)<br/>APISelfSubjectReview=true|false (BETA - default=true)<br/>APIServerIdentity=true|false (BETA - default=true)<br/>APIServerTracing=true|false (BETA - default=true)<br/>AdmissionWebhookMatchConditions=true|false (ALPHA - default=false)<br/>AggregatedDiscoveryEndpoint=true|false (BETA - default=true)<br/>AllAlpha=true|false (ALPHA - default=false)<br/>AllBeta=true|false (BETA - default=false)<br/>AnyVolumeDataSource=true|false (BETA - default=true)<br/>AppArmor=true|false (BETA - default=true)<br/>CPUManagerPolicyAlphaOptions=true|false (ALPHA - default=false)<br/>CPUManagerPolicyBetaOptions=true|false (BETA - default=true)<br/>CPUManagerPolicyOptions=true|false (BETA - default=true)<br/>CSIMigrationPortworx=true|false (BETA - default=false)<br/>CSIMigrationRBD=true|false (ALPHA - default=false)<br/>CSINodeExpandSecret=true|false (BETA - default=true)<br/>CSIVolumeHealth=true|false (ALPHA - default=false)<br/>CloudControllerManagerWebhook=true|false (ALPHA - default=false)<br/>CloudDualStackNodeIPs=true|false (ALPHA - default=false)<br/>ClusterTrustBundle=true|false (ALPHA - default=false)<br/>ComponentSLIs=true|false (BETA - default=true)<br/>ContainerCheckpoint=true|false (ALPHA - default=false)<br/>ContextualLogging=true|false (ALPHA - default=false)<br/>CrossNamespaceVolumeDataSource=true|false (ALPHA - default=false)<br/>CustomCPUCFSQuotaPeriod=true|false (ALPHA - default=false)<br/>CustomResourceValidationExpressions=true|false (BETA - default=true)<br/>DisableCloudProviders=true|false (ALPHA - default=false)<br/>DisableKubeletCloudCredentialProviders=true|false (ALPHA - default=false)<br/>DynamicResourceAllocation=true|false (ALPHA - default=false)<br/>ElasticIndexedJob=true|false (BETA - default=true)<br/>EventedPLEG=true|false (BETA - default=false)<br/>ExpandedDNSConfig=true|false (BETA - default=true)<br/>ExperimentalHostUserNamespaceDefaulting=true|false (BETA - default=false)<br/>GracefulNodeShutdown=true|false (BETA - default=true)<br/>GracefulNodeShutdownBasedOnPodPriority=true|false (BETA - default=true)<br/>HPAContainerMetrics=true|false (BETA - default=true)<br/>HPAScaleToZero=true|false (ALPHA - default=false)<br/>HonorPVReclaimPolicy=true|false (ALPHA - default=false)<br/>IPTablesOwnershipCleanup=true|false (BETA - default=true)<br/>InPlacePodVerticalScaling=true|false (ALPHA - default=false)<br/>InTreePluginAWSUnregister=true|false (ALPHA - default=false)<br/>InTreePluginAzureDiskUnregister=true|false (ALPHA - default=false)<br/>InTreePluginAzureFileUnregister=true|false (ALPHA - default=false)<br/>InTreePluginGCEUnregister=true|false (ALPHA - default=false)<br/>InTreePluginOpenStackUnregister=true|false (ALPHA - default=false)<br/>InTreePluginPortworxUnregister=true|false (ALPHA - default=false)<br/>InTreePluginRBDUnregister=true|false (ALPHA - default=false)<br/>InTreePluginvSphereUnregister=true|false (ALPHA - default=false)<br/>JobPodFailurePolicy=true|false (BETA - default=true)<br/>JobReadyPods=true|false (BETA - default=true)<br/>KMSv2=true|false (BETA - default=true)<br/>KubeletInUserNamespace=true|false (ALPHA - default=false)<br/>KubeletPodResources=true|false (BETA - default=true)<br/>KubeletPodResourcesDynamicResources=true|false (ALPHA - default=false)<br/>KubeletPodResourcesGet=true|false (ALPHA - default=false)<br/>KubeletPodResourcesGetAllocatable=true|false (BETA - default=true)<br/>KubeletTracing=true|false (BETA - default=true)<br/>LegacyServiceAccountTokenTracking=true|false (BETA - default=true)<br/>LocalStorageCapacityIsolationFSQuotaMonitoring=true|false (ALPHA - default=false)<br/>LogarithmicScaleDown=true|false (BETA - default=true)<br/>LoggingAlphaOptions=true|false (ALPHA - default=false)<br/>LoggingBetaOptions=true|false (BETA - default=true)<br/>MatchLabelKeysInPodTopologySpread=true|false (BETA - default=true)<br/>MaxUnavailableStatefulSet=true|false (ALPHA - default=false)<br/>MemoryManager=true|false (BETA - default=true)<br/>MemoryQoS=true|false (ALPHA - default=false)<br/>MinDomainsInPodTopologySpread=true|false (BETA - default=true)<br/>MinimizeIPTablesRestore=true|false (BETA - default=true)<br/>MultiCIDRRangeAllocator=true|false (ALPHA - default=false)<br/>MultiCIDRServiceAllocator=true|false (ALPHA - default=false)<br/>NetworkPolicyStatus=true|false (ALPHA - default=false)<br/>NewVolumeManagerReconstruction=true|false (BETA - default=true)<br/>NodeInclusionPolicyInPodTopologySpread=true|false (BETA - default=true)<br/>NodeLogQuery=true|false (ALPHA - default=false)<br/>NodeOutOfServiceVolumeDetach=true|false (BETA - default=true)<br/>NodeSwap=true|false (ALPHA - default=false)<br/>OpenAPIEnums=true|false (BETA - default=true)<br/>PDBUnhealthyPodEvictionPolicy=true|false (BETA - default=true)<br/>PodAndContainerStatsFromCRI=true|false (ALPHA - default=false)<br/>PodDeletionCost=true|false (BETA - default=true)<br/>PodDisruptionConditions=true|false (BETA - default=true)<br/>PodHasNetworkCondition=true|false (ALPHA - default=false)<br/>PodSchedulingReadiness=true|false (BETA - default=true)<br/>ProbeTerminationGracePeriod=true|false (BETA - default=true)<br/>ProcMountType=true|false (ALPHA - default=false)<br/>ProxyTerminatingEndpoints=true|false (BETA - default=true)<br/>QOSReserved=true|false (ALPHA - default=false)<br/>ReadWriteOncePod=true|false (BETA - default=true)<br/>RecoverVolumeExpansionFailure=true|false (ALPHA - default=false)<br/>RemainingItemCount=true|false (BETA - default=true)<br/>RetroactiveDefaultStorageClass=true|false (BETA - default=true)<br/>RotateKubeletServerCertificate=true|false (BETA - default=true)<br/>SELinuxMountReadWriteOncePod=true|false (BETA - default=true)<br/>SecurityContextDeny=true|false (ALPHA - default=false)<br/>ServiceNodePortStaticSubrange=true|false (ALPHA - default=false)<br/>SizeMemoryBackedVolumes=true|false (BETA - default=true)<br/>StableLoadBalancerNodeSet=true|false (BETA - default=true)<br/>StatefulSetAutoDeletePVC=true|false (BETA - default=true)<br/>StatefulSetStartOrdinal=true|false (BETA - default=true)<br/>StorageVersionAPI=true|false (ALPHA - default=false)<br/>StorageVersionHash=true|false (BETA - default=true)<br/>TopologyAwareHints=true|false (BETA - default=true)<br/>TopologyManagerPolicyAlphaOptions=true|false (ALPHA - default=false)<br/>TopologyManagerPolicyBetaOptions=true|false (BETA - default=false)<br/>TopologyManagerPolicyOptions=true|false (ALPHA - default=false)<br/>UserNamespacesStatelessPodsSupport=true|false (ALPHA - default=false)<br/>ValidatingAdmissionPolicy=true|false (ALPHA - default=false)<br/>VolumeCapacityPriority=true|false (ALPHA - default=false)<br/>WatchList=true|false (ALPHA - default=false)<br/>WinDSR=true|false (ALPHA - default=false)<br/>WinOverlay=true|false (BETA - default=true)<br/>WindowsHostNetwork=true|false (ALPHA - default=true)</p></td>
 </tr>
 
 <tr>
@@ -537,7 +537,7 @@ kube-controller-manager [flags]
 <td colspan="2">--kubeconfig string</td>
 </tr>
 <tr>
-<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Path to kubeconfig file with authorization and master location information.</p></td>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Path to kubeconfig file with authorization and master location information (the master location can be overridden by the master flag).</p></td>
 </tr>
 
 <tr>
diff --git a/content/en/docs/reference/command-line-tools-reference/kube-proxy.md b/content/en/docs/reference/command-line-tools-reference/kube-proxy.md
index 15b1aa9d2f4..34f71db84b9 100644
--- a/content/en/docs/reference/command-line-tools-reference/kube-proxy.md
+++ b/content/en/docs/reference/command-line-tools-reference/kube-proxy.md
@@ -144,7 +144,7 @@ kube-proxy [flags]
 <td colspan="2">--feature-gates &lt;comma-separated 'key=True|False' pairs&gt;</td>
 </tr>
 <tr>
-<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for alpha/experimental features. Options are:<br/>APIListChunking=true|false (BETA - default=true)<br/>APIPriorityAndFairness=true|false (BETA - default=true)<br/>APIResponseCompression=true|false (BETA - default=true)<br/>APISelfSubjectReview=true|false (ALPHA - default=false)<br/>APIServerIdentity=true|false (BETA - default=true)<br/>APIServerTracing=true|false (ALPHA - default=false)<br/>AggregatedDiscoveryEndpoint=true|false (ALPHA - default=false)<br/>AllAlpha=true|false (ALPHA - default=false)<br/>AllBeta=true|false (BETA - default=false)<br/>AnyVolumeDataSource=true|false (BETA - default=true)<br/>AppArmor=true|false (BETA - default=true)<br/>CPUManagerPolicyAlphaOptions=true|false (ALPHA - default=false)<br/>CPUManagerPolicyBetaOptions=true|false (BETA - default=true)<br/>CPUManagerPolicyOptions=true|false (BETA - default=true)<br/>CSIMigrationPortworx=true|false (BETA - default=false)<br/>CSIMigrationRBD=true|false (ALPHA - default=false)<br/>CSINodeExpandSecret=true|false (ALPHA - default=false)<br/>CSIVolumeHealth=true|false (ALPHA - default=false)<br/>ComponentSLIs=true|false (ALPHA - default=false)<br/>ContainerCheckpoint=true|false (ALPHA - default=false)<br/>CronJobTimeZone=true|false (BETA - default=true)<br/>CrossNamespaceVolumeDataSource=true|false (ALPHA - default=false)<br/>CustomCPUCFSQuotaPeriod=true|false (ALPHA - default=false)<br/>CustomResourceValidationExpressions=true|false (BETA - default=true)<br/>DisableCloudProviders=true|false (ALPHA - default=false)<br/>DisableKubeletCloudCredentialProviders=true|false (ALPHA - default=false)<br/>DownwardAPIHugePages=true|false (BETA - default=true)<br/>DynamicResourceAllocation=true|false (ALPHA - default=false)<br/>EventedPLEG=true|false (ALPHA - default=false)<br/>ExpandedDNSConfig=true|false (BETA - default=true)<br/>ExperimentalHostUserNamespaceDefaulting=true|false (BETA - default=false)<br/>GRPCContainerProbe=true|false (BETA - default=true)<br/>GracefulNodeShutdown=true|false (BETA - default=true)<br/>GracefulNodeShutdownBasedOnPodPriority=true|false (BETA - default=true)<br/>HPAContainerMetrics=true|false (ALPHA - default=false)<br/>HPAScaleToZero=true|false (ALPHA - default=false)<br/>HonorPVReclaimPolicy=true|false (ALPHA - default=false)<br/>IPTablesOwnershipCleanup=true|false (ALPHA - default=false)<br/>InTreePluginAWSUnregister=true|false (ALPHA - default=false)<br/>InTreePluginAzureDiskUnregister=true|false (ALPHA - default=false)<br/>InTreePluginAzureFileUnregister=true|false (ALPHA - default=false)<br/>InTreePluginGCEUnregister=true|false (ALPHA - default=false)<br/>InTreePluginOpenStackUnregister=true|false (ALPHA - default=false)<br/>InTreePluginPortworxUnregister=true|false (ALPHA - default=false)<br/>InTreePluginRBDUnregister=true|false (ALPHA - default=false)<br/>InTreePluginvSphereUnregister=true|false (ALPHA - default=false)<br/>JobMutableNodeSchedulingDirectives=true|false (BETA - default=true)<br/>JobPodFailurePolicy=true|false (BETA - default=true)<br/>JobReadyPods=true|false (BETA - default=true)<br/>KMSv2=true|false (ALPHA - default=false)<br/>KubeletInUserNamespace=true|false (ALPHA - default=false)<br/>KubeletPodResources=true|false (BETA - default=true)<br/>KubeletPodResourcesGetAllocatable=true|false (BETA - default=true)<br/>KubeletTracing=true|false (ALPHA - default=false)<br/>LegacyServiceAccountTokenTracking=true|false (ALPHA - default=false)<br/>LocalStorageCapacityIsolationFSQuotaMonitoring=true|false (ALPHA - default=false)<br/>LogarithmicScaleDown=true|false (BETA - default=true)<br/>MatchLabelKeysInPodTopologySpread=true|false (ALPHA - default=false)<br/>MaxUnavailableStatefulSet=true|false (ALPHA - default=false)<br/>MemoryManager=true|false (BETA - default=true)<br/>MemoryQoS=true|false (ALPHA - default=false)<br/>MinDomainsInPodTopologySpread=true|false (BETA - default=false)<br/>MinimizeIPTablesRestore=true|false (ALPHA - default=false)<br/>MultiCIDRRangeAllocator=true|false (ALPHA - default=false)<br/>NetworkPolicyStatus=true|false (ALPHA - default=false)<br/>NodeInclusionPolicyInPodTopologySpread=true|false (BETA - default=true)<br/>NodeOutOfServiceVolumeDetach=true|false (BETA - default=true)<br/>NodeSwap=true|false (ALPHA - default=false)<br/>OpenAPIEnums=true|false (BETA - default=true)<br/>OpenAPIV3=true|false (BETA - default=true)<br/>PDBUnhealthyPodEvictionPolicy=true|false (ALPHA - default=false)<br/>PodAndContainerStatsFromCRI=true|false (ALPHA - default=false)<br/>PodDeletionCost=true|false (BETA - default=true)<br/>PodDisruptionConditions=true|false (BETA - default=true)<br/>PodHasNetworkCondition=true|false (ALPHA - default=false)<br/>PodSchedulingReadiness=true|false (ALPHA - default=false)<br/>ProbeTerminationGracePeriod=true|false (BETA - default=true)<br/>ProcMountType=true|false (ALPHA - default=false)<br/>ProxyTerminatingEndpoints=true|false (BETA - default=true)<br/>QOSReserved=true|false (ALPHA - default=false)<br/>ReadWriteOncePod=true|false (ALPHA - default=false)<br/>RecoverVolumeExpansionFailure=true|false (ALPHA - default=false)<br/>RemainingItemCount=true|false (BETA - default=true)<br/>RetroactiveDefaultStorageClass=true|false (BETA - default=true)<br/>RotateKubeletServerCertificate=true|false (BETA - default=true)<br/>SELinuxMountReadWriteOncePod=true|false (ALPHA - default=false)<br/>SeccompDefault=true|false (BETA - default=true)<br/>ServerSideFieldValidation=true|false (BETA - default=true)<br/>SizeMemoryBackedVolumes=true|false (BETA - default=true)<br/>StatefulSetAutoDeletePVC=true|false (ALPHA - default=false)<br/>StatefulSetStartOrdinal=true|false (ALPHA - default=false)<br/>StorageVersionAPI=true|false (ALPHA - default=false)<br/>StorageVersionHash=true|false (BETA - default=true)<br/>TopologyAwareHints=true|false (BETA - default=true)<br/>TopologyManager=true|false (BETA - default=true)<br/>TopologyManagerPolicyAlphaOptions=true|false (ALPHA - default=false)<br/>TopologyManagerPolicyBetaOptions=true|false (BETA - default=false)<br/>TopologyManagerPolicyOptions=true|false (ALPHA - default=false)<br/>UserNamespacesStatelessPodsSupport=true|false (ALPHA - default=false)<br/>ValidatingAdmissionPolicy=true|false (ALPHA - default=false)<br/>VolumeCapacityPriority=true|false (ALPHA - default=false)<br/>WinDSR=true|false (ALPHA - default=false)<br/>WinOverlay=true|false (BETA - default=true)<br/>WindowsHostNetwork=true|false (ALPHA - default=true)<br/>This parameter is ignored if a config file is specified by --config.</p></td>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for alpha/experimental features. Options are:<br/>APIListChunking=true|false (BETA - default=true)<br/>APIPriorityAndFairness=true|false (BETA - default=true)<br/>APIResponseCompression=true|false (BETA - default=true)<br/>APISelfSubjectReview=true|false (BETA - default=true)<br/>APIServerIdentity=true|false (BETA - default=true)<br/>APIServerTracing=true|false (BETA - default=true)<br/>AdmissionWebhookMatchConditions=true|false (ALPHA - default=false)<br/>AggregatedDiscoveryEndpoint=true|false (BETA - default=true)<br/>AllAlpha=true|false (ALPHA - default=false)<br/>AllBeta=true|false (BETA - default=false)<br/>AnyVolumeDataSource=true|false (BETA - default=true)<br/>AppArmor=true|false (BETA - default=true)<br/>CPUManagerPolicyAlphaOptions=true|false (ALPHA - default=false)<br/>CPUManagerPolicyBetaOptions=true|false (BETA - default=true)<br/>CPUManagerPolicyOptions=true|false (BETA - default=true)<br/>CSIMigrationPortworx=true|false (BETA - default=false)<br/>CSIMigrationRBD=true|false (ALPHA - default=false)<br/>CSINodeExpandSecret=true|false (BETA - default=true)<br/>CSIVolumeHealth=true|false (ALPHA - default=false)<br/>CloudControllerManagerWebhook=true|false (ALPHA - default=false)<br/>CloudDualStackNodeIPs=true|false (ALPHA - default=false)<br/>ClusterTrustBundle=true|false (ALPHA - default=false)<br/>ComponentSLIs=true|false (BETA - default=true)<br/>ContainerCheckpoint=true|false (ALPHA - default=false)<br/>ContextualLogging=true|false (ALPHA - default=false)<br/>CrossNamespaceVolumeDataSource=true|false (ALPHA - default=false)<br/>CustomCPUCFSQuotaPeriod=true|false (ALPHA - default=false)<br/>CustomResourceValidationExpressions=true|false (BETA - default=true)<br/>DisableCloudProviders=true|false (ALPHA - default=false)<br/>DisableKubeletCloudCredentialProviders=true|false (ALPHA - default=false)<br/>DynamicResourceAllocation=true|false (ALPHA - default=false)<br/>ElasticIndexedJob=true|false (BETA - default=true)<br/>EventedPLEG=true|false (BETA - default=false)<br/>ExpandedDNSConfig=true|false (BETA - default=true)<br/>ExperimentalHostUserNamespaceDefaulting=true|false (BETA - default=false)<br/>GracefulNodeShutdown=true|false (BETA - default=true)<br/>GracefulNodeShutdownBasedOnPodPriority=true|false (BETA - default=true)<br/>HPAContainerMetrics=true|false (BETA - default=true)<br/>HPAScaleToZero=true|false (ALPHA - default=false)<br/>HonorPVReclaimPolicy=true|false (ALPHA - default=false)<br/>IPTablesOwnershipCleanup=true|false (BETA - default=true)<br/>InPlacePodVerticalScaling=true|false (ALPHA - default=false)<br/>InTreePluginAWSUnregister=true|false (ALPHA - default=false)<br/>InTreePluginAzureDiskUnregister=true|false (ALPHA - default=false)<br/>InTreePluginAzureFileUnregister=true|false (ALPHA - default=false)<br/>InTreePluginGCEUnregister=true|false (ALPHA - default=false)<br/>InTreePluginOpenStackUnregister=true|false (ALPHA - default=false)<br/>InTreePluginPortworxUnregister=true|false (ALPHA - default=false)<br/>InTreePluginRBDUnregister=true|false (ALPHA - default=false)<br/>InTreePluginvSphereUnregister=true|false (ALPHA - default=false)<br/>JobPodFailurePolicy=true|false (BETA - default=true)<br/>JobReadyPods=true|false (BETA - default=true)<br/>KMSv2=true|false (BETA - default=true)<br/>KubeletInUserNamespace=true|false (ALPHA - default=false)<br/>KubeletPodResources=true|false (BETA - default=true)<br/>KubeletPodResourcesDynamicResources=true|false (ALPHA - default=false)<br/>KubeletPodResourcesGet=true|false (ALPHA - default=false)<br/>KubeletPodResourcesGetAllocatable=true|false (BETA - default=true)<br/>KubeletTracing=true|false (BETA - default=true)<br/>LegacyServiceAccountTokenTracking=true|false (BETA - default=true)<br/>LocalStorageCapacityIsolationFSQuotaMonitoring=true|false (ALPHA - default=false)<br/>LogarithmicScaleDown=true|false (BETA - default=true)<br/>LoggingAlphaOptions=true|false (ALPHA - default=false)<br/>LoggingBetaOptions=true|false (BETA - default=true)<br/>MatchLabelKeysInPodTopologySpread=true|false (BETA - default=true)<br/>MaxUnavailableStatefulSet=true|false (ALPHA - default=false)<br/>MemoryManager=true|false (BETA - default=true)<br/>MemoryQoS=true|false (ALPHA - default=false)<br/>MinDomainsInPodTopologySpread=true|false (BETA - default=true)<br/>MinimizeIPTablesRestore=true|false (BETA - default=true)<br/>MultiCIDRRangeAllocator=true|false (ALPHA - default=false)<br/>MultiCIDRServiceAllocator=true|false (ALPHA - default=false)<br/>NetworkPolicyStatus=true|false (ALPHA - default=false)<br/>NewVolumeManagerReconstruction=true|false (BETA - default=true)<br/>NodeInclusionPolicyInPodTopologySpread=true|false (BETA - default=true)<br/>NodeLogQuery=true|false (ALPHA - default=false)<br/>NodeOutOfServiceVolumeDetach=true|false (BETA - default=true)<br/>NodeSwap=true|false (ALPHA - default=false)<br/>OpenAPIEnums=true|false (BETA - default=true)<br/>PDBUnhealthyPodEvictionPolicy=true|false (BETA - default=true)<br/>PodAndContainerStatsFromCRI=true|false (ALPHA - default=false)<br/>PodDeletionCost=true|false (BETA - default=true)<br/>PodDisruptionConditions=true|false (BETA - default=true)<br/>PodHasNetworkCondition=true|false (ALPHA - default=false)<br/>PodSchedulingReadiness=true|false (BETA - default=true)<br/>ProbeTerminationGracePeriod=true|false (BETA - default=true)<br/>ProcMountType=true|false (ALPHA - default=false)<br/>ProxyTerminatingEndpoints=true|false (BETA - default=true)<br/>QOSReserved=true|false (ALPHA - default=false)<br/>ReadWriteOncePod=true|false (BETA - default=true)<br/>RecoverVolumeExpansionFailure=true|false (ALPHA - default=false)<br/>RemainingItemCount=true|false (BETA - default=true)<br/>RetroactiveDefaultStorageClass=true|false (BETA - default=true)<br/>RotateKubeletServerCertificate=true|false (BETA - default=true)<br/>SELinuxMountReadWriteOncePod=true|false (BETA - default=true)<br/>SecurityContextDeny=true|false (ALPHA - default=false)<br/>ServiceNodePortStaticSubrange=true|false (ALPHA - default=false)<br/>SizeMemoryBackedVolumes=true|false (BETA - default=true)<br/>StableLoadBalancerNodeSet=true|false (BETA - default=true)<br/>StatefulSetAutoDeletePVC=true|false (BETA - default=true)<br/>StatefulSetStartOrdinal=true|false (BETA - default=true)<br/>StorageVersionAPI=true|false (ALPHA - default=false)<br/>StorageVersionHash=true|false (BETA - default=true)<br/>TopologyAwareHints=true|false (BETA - default=true)<br/>TopologyManagerPolicyAlphaOptions=true|false (ALPHA - default=false)<br/>TopologyManagerPolicyBetaOptions=true|false (BETA - default=false)<br/>TopologyManagerPolicyOptions=true|false (ALPHA - default=false)<br/>UserNamespacesStatelessPodsSupport=true|false (ALPHA - default=false)<br/>ValidatingAdmissionPolicy=true|false (ALPHA - default=false)<br/>VolumeCapacityPriority=true|false (ALPHA - default=false)<br/>WatchList=true|false (ALPHA - default=false)<br/>WinDSR=true|false (ALPHA - default=false)<br/>WinOverlay=true|false (BETA - default=true)<br/>WindowsHostNetwork=true|false (ALPHA - default=true)<br/>This parameter is ignored if a config file is specified by --config.</p></td>
 </tr>
 
 <tr>
diff --git a/content/en/docs/reference/command-line-tools-reference/kube-scheduler.md b/content/en/docs/reference/command-line-tools-reference/kube-scheduler.md
index d0032be6a16..7dc952537d4 100644
--- a/content/en/docs/reference/command-line-tools-reference/kube-scheduler.md
+++ b/content/en/docs/reference/command-line-tools-reference/kube-scheduler.md
@@ -145,7 +145,7 @@ kube-scheduler [flags]
 <td colspan="2">--contention-profiling&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: true</td>
 </tr>
 <tr>
-<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>DEPRECATED: enable lock contention profiling, if profiling is enabled. This parameter is ignored if a config file is specified in --config.</p></td>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>DEPRECATED: enable block profiling, if profiling is enabled. This parameter is ignored if a config file is specified in --config.</p></td>
 </tr>
 
 <tr>
@@ -159,7 +159,7 @@ kube-scheduler [flags]
 <td colspan="2">--feature-gates &lt;comma-separated 'key=True|False' pairs&gt;</td>
 </tr>
 <tr>
-<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for alpha/experimental features. Options are:<br/>APIListChunking=true|false (BETA - default=true)<br/>APIPriorityAndFairness=true|false (BETA - default=true)<br/>APIResponseCompression=true|false (BETA - default=true)<br/>APISelfSubjectReview=true|false (ALPHA - default=false)<br/>APIServerIdentity=true|false (BETA - default=true)<br/>APIServerTracing=true|false (ALPHA - default=false)<br/>AggregatedDiscoveryEndpoint=true|false (ALPHA - default=false)<br/>AllAlpha=true|false (ALPHA - default=false)<br/>AllBeta=true|false (BETA - default=false)<br/>AnyVolumeDataSource=true|false (BETA - default=true)<br/>AppArmor=true|false (BETA - default=true)<br/>CPUManagerPolicyAlphaOptions=true|false (ALPHA - default=false)<br/>CPUManagerPolicyBetaOptions=true|false (BETA - default=true)<br/>CPUManagerPolicyOptions=true|false (BETA - default=true)<br/>CSIMigrationPortworx=true|false (BETA - default=false)<br/>CSIMigrationRBD=true|false (ALPHA - default=false)<br/>CSINodeExpandSecret=true|false (ALPHA - default=false)<br/>CSIVolumeHealth=true|false (ALPHA - default=false)<br/>ComponentSLIs=true|false (ALPHA - default=false)<br/>ContainerCheckpoint=true|false (ALPHA - default=false)<br/>ContextualLogging=true|false (ALPHA - default=false)<br/>CronJobTimeZone=true|false (BETA - default=true)<br/>CrossNamespaceVolumeDataSource=true|false (ALPHA - default=false)<br/>CustomCPUCFSQuotaPeriod=true|false (ALPHA - default=false)<br/>CustomResourceValidationExpressions=true|false (BETA - default=true)<br/>DisableCloudProviders=true|false (ALPHA - default=false)<br/>DisableKubeletCloudCredentialProviders=true|false (ALPHA - default=false)<br/>DownwardAPIHugePages=true|false (BETA - default=true)<br/>DynamicResourceAllocation=true|false (ALPHA - default=false)<br/>EventedPLEG=true|false (ALPHA - default=false)<br/>ExpandedDNSConfig=true|false (BETA - default=true)<br/>ExperimentalHostUserNamespaceDefaulting=true|false (BETA - default=false)<br/>GRPCContainerProbe=true|false (BETA - default=true)<br/>GracefulNodeShutdown=true|false (BETA - default=true)<br/>GracefulNodeShutdownBasedOnPodPriority=true|false (BETA - default=true)<br/>HPAContainerMetrics=true|false (ALPHA - default=false)<br/>HPAScaleToZero=true|false (ALPHA - default=false)<br/>HonorPVReclaimPolicy=true|false (ALPHA - default=false)<br/>IPTablesOwnershipCleanup=true|false (ALPHA - default=false)<br/>InTreePluginAWSUnregister=true|false (ALPHA - default=false)<br/>InTreePluginAzureDiskUnregister=true|false (ALPHA - default=false)<br/>InTreePluginAzureFileUnregister=true|false (ALPHA - default=false)<br/>InTreePluginGCEUnregister=true|false (ALPHA - default=false)<br/>InTreePluginOpenStackUnregister=true|false (ALPHA - default=false)<br/>InTreePluginPortworxUnregister=true|false (ALPHA - default=false)<br/>InTreePluginRBDUnregister=true|false (ALPHA - default=false)<br/>InTreePluginvSphereUnregister=true|false (ALPHA - default=false)<br/>JobMutableNodeSchedulingDirectives=true|false (BETA - default=true)<br/>JobPodFailurePolicy=true|false (BETA - default=true)<br/>JobReadyPods=true|false (BETA - default=true)<br/>KMSv2=true|false (ALPHA - default=false)<br/>KubeletInUserNamespace=true|false (ALPHA - default=false)<br/>KubeletPodResources=true|false (BETA - default=true)<br/>KubeletPodResourcesGetAllocatable=true|false (BETA - default=true)<br/>KubeletTracing=true|false (ALPHA - default=false)<br/>LegacyServiceAccountTokenTracking=true|false (ALPHA - default=false)<br/>LocalStorageCapacityIsolationFSQuotaMonitoring=true|false (ALPHA - default=false)<br/>LogarithmicScaleDown=true|false (BETA - default=true)<br/>LoggingAlphaOptions=true|false (ALPHA - default=false)<br/>LoggingBetaOptions=true|false (BETA - default=true)<br/>MatchLabelKeysInPodTopologySpread=true|false (ALPHA - default=false)<br/>MaxUnavailableStatefulSet=true|false (ALPHA - default=false)<br/>MemoryManager=true|false (BETA - default=true)<br/>MemoryQoS=true|false (ALPHA - default=false)<br/>MinDomainsInPodTopologySpread=true|false (BETA - default=false)<br/>MinimizeIPTablesRestore=true|false (ALPHA - default=false)<br/>MultiCIDRRangeAllocator=true|false (ALPHA - default=false)<br/>NetworkPolicyStatus=true|false (ALPHA - default=false)<br/>NodeInclusionPolicyInPodTopologySpread=true|false (BETA - default=true)<br/>NodeOutOfServiceVolumeDetach=true|false (BETA - default=true)<br/>NodeSwap=true|false (ALPHA - default=false)<br/>OpenAPIEnums=true|false (BETA - default=true)<br/>OpenAPIV3=true|false (BETA - default=true)<br/>PDBUnhealthyPodEvictionPolicy=true|false (ALPHA - default=false)<br/>PodAndContainerStatsFromCRI=true|false (ALPHA - default=false)<br/>PodDeletionCost=true|false (BETA - default=true)<br/>PodDisruptionConditions=true|false (BETA - default=true)<br/>PodHasNetworkCondition=true|false (ALPHA - default=false)<br/>PodSchedulingReadiness=true|false (ALPHA - default=false)<br/>ProbeTerminationGracePeriod=true|false (BETA - default=true)<br/>ProcMountType=true|false (ALPHA - default=false)<br/>ProxyTerminatingEndpoints=true|false (BETA - default=true)<br/>QOSReserved=true|false (ALPHA - default=false)<br/>ReadWriteOncePod=true|false (ALPHA - default=false)<br/>RecoverVolumeExpansionFailure=true|false (ALPHA - default=false)<br/>RemainingItemCount=true|false (BETA - default=true)<br/>RetroactiveDefaultStorageClass=true|false (BETA - default=true)<br/>RotateKubeletServerCertificate=true|false (BETA - default=true)<br/>SELinuxMountReadWriteOncePod=true|false (ALPHA - default=false)<br/>SeccompDefault=true|false (BETA - default=true)<br/>ServerSideFieldValidation=true|false (BETA - default=true)<br/>SizeMemoryBackedVolumes=true|false (BETA - default=true)<br/>StatefulSetAutoDeletePVC=true|false (ALPHA - default=false)<br/>StatefulSetStartOrdinal=true|false (ALPHA - default=false)<br/>StorageVersionAPI=true|false (ALPHA - default=false)<br/>StorageVersionHash=true|false (BETA - default=true)<br/>TopologyAwareHints=true|false (BETA - default=true)<br/>TopologyManager=true|false (BETA - default=true)<br/>TopologyManagerPolicyAlphaOptions=true|false (ALPHA - default=false)<br/>TopologyManagerPolicyBetaOptions=true|false (BETA - default=false)<br/>TopologyManagerPolicyOptions=true|false (ALPHA - default=false)<br/>UserNamespacesStatelessPodsSupport=true|false (ALPHA - default=false)<br/>ValidatingAdmissionPolicy=true|false (ALPHA - default=false)<br/>VolumeCapacityPriority=true|false (ALPHA - default=false)<br/>WinDSR=true|false (ALPHA - default=false)<br/>WinOverlay=true|false (BETA - default=true)<br/>WindowsHostNetwork=true|false (ALPHA - default=true)</p></td>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for alpha/experimental features. Options are:<br/>APIListChunking=true|false (BETA - default=true)<br/>APIPriorityAndFairness=true|false (BETA - default=true)<br/>APIResponseCompression=true|false (BETA - default=true)<br/>APISelfSubjectReview=true|false (BETA - default=true)<br/>APIServerIdentity=true|false (BETA - default=true)<br/>APIServerTracing=true|false (BETA - default=true)<br/>AdmissionWebhookMatchConditions=true|false (ALPHA - default=false)<br/>AggregatedDiscoveryEndpoint=true|false (BETA - default=true)<br/>AllAlpha=true|false (ALPHA - default=false)<br/>AllBeta=true|false (BETA - default=false)<br/>AnyVolumeDataSource=true|false (BETA - default=true)<br/>AppArmor=true|false (BETA - default=true)<br/>CPUManagerPolicyAlphaOptions=true|false (ALPHA - default=false)<br/>CPUManagerPolicyBetaOptions=true|false (BETA - default=true)<br/>CPUManagerPolicyOptions=true|false (BETA - default=true)<br/>CSIMigrationPortworx=true|false (BETA - default=false)<br/>CSIMigrationRBD=true|false (ALPHA - default=false)<br/>CSINodeExpandSecret=true|false (BETA - default=true)<br/>CSIVolumeHealth=true|false (ALPHA - default=false)<br/>CloudControllerManagerWebhook=true|false (ALPHA - default=false)<br/>CloudDualStackNodeIPs=true|false (ALPHA - default=false)<br/>ClusterTrustBundle=true|false (ALPHA - default=false)<br/>ComponentSLIs=true|false (BETA - default=true)<br/>ContainerCheckpoint=true|false (ALPHA - default=false)<br/>ContextualLogging=true|false (ALPHA - default=false)<br/>CrossNamespaceVolumeDataSource=true|false (ALPHA - default=false)<br/>CustomCPUCFSQuotaPeriod=true|false (ALPHA - default=false)<br/>CustomResourceValidationExpressions=true|false (BETA - default=true)<br/>DisableCloudProviders=true|false (ALPHA - default=false)<br/>DisableKubeletCloudCredentialProviders=true|false (ALPHA - default=false)<br/>DynamicResourceAllocation=true|false (ALPHA - default=false)<br/>ElasticIndexedJob=true|false (BETA - default=true)<br/>EventedPLEG=true|false (BETA - default=false)<br/>ExpandedDNSConfig=true|false (BETA - default=true)<br/>ExperimentalHostUserNamespaceDefaulting=true|false (BETA - default=false)<br/>GracefulNodeShutdown=true|false (BETA - default=true)<br/>GracefulNodeShutdownBasedOnPodPriority=true|false (BETA - default=true)<br/>HPAContainerMetrics=true|false (BETA - default=true)<br/>HPAScaleToZero=true|false (ALPHA - default=false)<br/>HonorPVReclaimPolicy=true|false (ALPHA - default=false)<br/>IPTablesOwnershipCleanup=true|false (BETA - default=true)<br/>InPlacePodVerticalScaling=true|false (ALPHA - default=false)<br/>InTreePluginAWSUnregister=true|false (ALPHA - default=false)<br/>InTreePluginAzureDiskUnregister=true|false (ALPHA - default=false)<br/>InTreePluginAzureFileUnregister=true|false (ALPHA - default=false)<br/>InTreePluginGCEUnregister=true|false (ALPHA - default=false)<br/>InTreePluginOpenStackUnregister=true|false (ALPHA - default=false)<br/>InTreePluginPortworxUnregister=true|false (ALPHA - default=false)<br/>InTreePluginRBDUnregister=true|false (ALPHA - default=false)<br/>InTreePluginvSphereUnregister=true|false (ALPHA - default=false)<br/>JobPodFailurePolicy=true|false (BETA - default=true)<br/>JobReadyPods=true|false (BETA - default=true)<br/>KMSv2=true|false (BETA - default=true)<br/>KubeletInUserNamespace=true|false (ALPHA - default=false)<br/>KubeletPodResources=true|false (BETA - default=true)<br/>KubeletPodResourcesDynamicResources=true|false (ALPHA - default=false)<br/>KubeletPodResourcesGet=true|false (ALPHA - default=false)<br/>KubeletPodResourcesGetAllocatable=true|false (BETA - default=true)<br/>KubeletTracing=true|false (BETA - default=true)<br/>LegacyServiceAccountTokenTracking=true|false (BETA - default=true)<br/>LocalStorageCapacityIsolationFSQuotaMonitoring=true|false (ALPHA - default=false)<br/>LogarithmicScaleDown=true|false (BETA - default=true)<br/>LoggingAlphaOptions=true|false (ALPHA - default=false)<br/>LoggingBetaOptions=true|false (BETA - default=true)<br/>MatchLabelKeysInPodTopologySpread=true|false (BETA - default=true)<br/>MaxUnavailableStatefulSet=true|false (ALPHA - default=false)<br/>MemoryManager=true|false (BETA - default=true)<br/>MemoryQoS=true|false (ALPHA - default=false)<br/>MinDomainsInPodTopologySpread=true|false (BETA - default=true)<br/>MinimizeIPTablesRestore=true|false (BETA - default=true)<br/>MultiCIDRRangeAllocator=true|false (ALPHA - default=false)<br/>MultiCIDRServiceAllocator=true|false (ALPHA - default=false)<br/>NetworkPolicyStatus=true|false (ALPHA - default=false)<br/>NewVolumeManagerReconstruction=true|false (BETA - default=true)<br/>NodeInclusionPolicyInPodTopologySpread=true|false (BETA - default=true)<br/>NodeLogQuery=true|false (ALPHA - default=false)<br/>NodeOutOfServiceVolumeDetach=true|false (BETA - default=true)<br/>NodeSwap=true|false (ALPHA - default=false)<br/>OpenAPIEnums=true|false (BETA - default=true)<br/>PDBUnhealthyPodEvictionPolicy=true|false (BETA - default=true)<br/>PodAndContainerStatsFromCRI=true|false (ALPHA - default=false)<br/>PodDeletionCost=true|false (BETA - default=true)<br/>PodDisruptionConditions=true|false (BETA - default=true)<br/>PodHasNetworkCondition=true|false (ALPHA - default=false)<br/>PodSchedulingReadiness=true|false (BETA - default=true)<br/>ProbeTerminationGracePeriod=true|false (BETA - default=true)<br/>ProcMountType=true|false (ALPHA - default=false)<br/>ProxyTerminatingEndpoints=true|false (BETA - default=true)<br/>QOSReserved=true|false (ALPHA - default=false)<br/>ReadWriteOncePod=true|false (BETA - default=true)<br/>RecoverVolumeExpansionFailure=true|false (ALPHA - default=false)<br/>RemainingItemCount=true|false (BETA - default=true)<br/>RetroactiveDefaultStorageClass=true|false (BETA - default=true)<br/>RotateKubeletServerCertificate=true|false (BETA - default=true)<br/>SELinuxMountReadWriteOncePod=true|false (BETA - default=true)<br/>SecurityContextDeny=true|false (ALPHA - default=false)<br/>ServiceNodePortStaticSubrange=true|false (ALPHA - default=false)<br/>SizeMemoryBackedVolumes=true|false (BETA - default=true)<br/>StableLoadBalancerNodeSet=true|false (BETA - default=true)<br/>StatefulSetAutoDeletePVC=true|false (BETA - default=true)<br/>StatefulSetStartOrdinal=true|false (BETA - default=true)<br/>StorageVersionAPI=true|false (ALPHA - default=false)<br/>StorageVersionHash=true|false (BETA - default=true)<br/>TopologyAwareHints=true|false (BETA - default=true)<br/>TopologyManagerPolicyAlphaOptions=true|false (ALPHA - default=false)<br/>TopologyManagerPolicyBetaOptions=true|false (BETA - default=false)<br/>TopologyManagerPolicyOptions=true|false (ALPHA - default=false)<br/>UserNamespacesStatelessPodsSupport=true|false (ALPHA - default=false)<br/>ValidatingAdmissionPolicy=true|false (ALPHA - default=false)<br/>VolumeCapacityPriority=true|false (ALPHA - default=false)<br/>WatchList=true|false (ALPHA - default=false)<br/>WinDSR=true|false (ALPHA - default=false)<br/>WinOverlay=true|false (BETA - default=true)<br/>WindowsHostNetwork=true|false (ALPHA - default=true)</p></td>
 </tr>
 
 <tr>
diff --git a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_images_list.md b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_images_list.md
index 541d9892a15..92b045be4bf 100644
--- a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_images_list.md
+++ b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_images_list.md
@@ -55,7 +55,7 @@ kubeadm config images list [flags]
 <td colspan="2">--feature-gates string</td>
 </tr>
 <tr>
-<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for various features. Options are:<br/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)</p></td>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for various features. Options are:<br/>EtcdLearnerMode=true|false (ALPHA - default=false)<br/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)</p></td>
 </tr>
 
 <tr>
diff --git a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_images_pull.md b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_images_pull.md
index 3a78f260312..cad6279ee04 100644
--- a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_images_pull.md
+++ b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_images_pull.md
@@ -48,7 +48,7 @@ kubeadm config images pull [flags]
 <td colspan="2">--feature-gates string</td>
 </tr>
 <tr>
-<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for various features. Options are:<br/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)</p></td>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for various features. Options are:<br/>EtcdLearnerMode=true|false (ALPHA - default=false)<br/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)</p></td>
 </tr>
 
 <tr>
diff --git a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init.md b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init.md
index ad919d2e16e..385331d7af5 100644
--- a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init.md
+++ b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init.md
@@ -139,7 +139,7 @@ kubeadm init [flags]
 <td colspan="2">--feature-gates string</td>
 </tr>
 <tr>
-<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for various features. Options are:<br/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)</p></td>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for various features. Options are:<br/>EtcdLearnerMode=true|false (ALPHA - default=false)<br/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)</p></td>
 </tr>
 
 <tr>
diff --git a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_addon_all.md b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_addon_all.md
index dafa56360ac..621c1f8170b 100644
--- a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_addon_all.md
+++ b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_addon_all.md
@@ -69,7 +69,7 @@ kubeadm init phase addon all [flags]
 <td colspan="2">--feature-gates string</td>
 </tr>
 <tr>
-<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for various features. Options are:<br/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)</p></td>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for various features. Options are:<br/>EtcdLearnerMode=true|false (ALPHA - default=false)<br/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)</p></td>
 </tr>
 
 <tr>
diff --git a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_addon_coredns.md b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_addon_coredns.md
index 3225abfba1d..a44e72427fb 100644
--- a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_addon_coredns.md
+++ b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_addon_coredns.md
@@ -48,7 +48,7 @@ kubeadm init phase addon coredns [flags]
 <td colspan="2">--feature-gates string</td>
 </tr>
 <tr>
-<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for various features. Options are:<br/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)</p></td>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for various features. Options are:<br/>EtcdLearnerMode=true|false (ALPHA - default=false)<br/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)</p></td>
 </tr>
 
 <tr>
diff --git a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_all.md b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_all.md
index e168a6bb877..b28306a6477 100644
--- a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_all.md
+++ b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_all.md
@@ -101,7 +101,7 @@ kubeadm init phase control-plane all [flags]
 <td colspan="2">--feature-gates string</td>
 </tr>
 <tr>
-<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for various features. Options are:<br/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)</p></td>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for various features. Options are:<br/>EtcdLearnerMode=true|false (ALPHA - default=false)<br/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)</p></td>
 </tr>
 
 <tr>
diff --git a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_apiserver.md b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_apiserver.md
index 3f69982f8f1..67d775db2d1 100644
--- a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_apiserver.md
+++ b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_apiserver.md
@@ -83,7 +83,7 @@ kubeadm init phase control-plane apiserver [flags]
 <td colspan="2">--feature-gates string</td>
 </tr>
 <tr>
-<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for various features. Options are:<br/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)</p></td>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for various features. Options are:<br/>EtcdLearnerMode=true|false (ALPHA - default=false)<br/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)</p></td>
 </tr>
 
 <tr>
diff --git a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_preflight.md b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_preflight.md
index 21fc3f7feae..23013ec7e3a 100644
--- a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_preflight.md
+++ b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_preflight.md
@@ -44,6 +44,13 @@ kubeadm init phase preflight [flags]
 <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Path to a kubeadm configuration file.</p></td>
 </tr>
 
+<tr>
+<td colspan="2">--cri-socket string</td>
+</tr>
+<tr>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this value; use this option only if you have more than one CRI installed or if you have non-standard CRI socket.</p></td>
+</tr>
+
 <tr>
 <td colspan="2">--dry-run</td>
 </tr>
diff --git a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config_all.md b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config_all.md
index 2b15abac969..3feed3b1892 100644
--- a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config_all.md
+++ b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config_all.md
@@ -37,6 +37,13 @@ kubeadm init phase upload-config all [flags]
 <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Path to a kubeadm configuration file.</p></td>
 </tr>
 
+<tr>
+<td colspan="2">--cri-socket string</td>
+</tr>
+<tr>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this value; use this option only if you have more than one CRI installed or if you have non-standard CRI socket.</p></td>
+</tr>
+
 <tr>
 <td colspan="2">--dry-run</td>
 </tr>
diff --git a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config_kubeadm.md b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config_kubeadm.md
index d8f466b4094..4ef3f88e7e8 100644
--- a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config_kubeadm.md
+++ b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config_kubeadm.md
@@ -46,6 +46,13 @@ kubeadm init phase upload-config kubeadm [flags]
 <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Path to a kubeadm configuration file.</p></td>
 </tr>
 
+<tr>
+<td colspan="2">--cri-socket string</td>
+</tr>
+<tr>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this value; use this option only if you have more than one CRI installed or if you have non-standard CRI socket.</p></td>
+</tr>
+
 <tr>
 <td colspan="2">--dry-run</td>
 </tr>
diff --git a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config_kubelet.md b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config_kubelet.md
index ae2fd63e838..c83a86129e5 100644
--- a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config_kubelet.md
+++ b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config_kubelet.md
@@ -44,6 +44,13 @@ kubeadm init phase upload-config kubelet [flags]
 <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Path to a kubeadm configuration file.</p></td>
 </tr>
 
+<tr>
+<td colspan="2">--cri-socket string</td>
+</tr>
+<tr>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this value; use this option only if you have more than one CRI installed or if you have non-standard CRI socket.</p></td>
+</tr>
+
 <tr>
 <td colspan="2">--dry-run</td>
 </tr>
diff --git a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_kubeconfig_user.md b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_kubeconfig_user.md
index 7d8bda9389f..25edb297c20 100644
--- a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_kubeconfig_user.md
+++ b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_kubeconfig_user.md
@@ -24,6 +24,9 @@ kubeadm kubeconfig user [flags]
 ### Examples
 
 ```
+  # Output a kubeconfig file for an additional user named foo
+  kubeadm kubeconfig user --client-name=foo
+  
   # Output a kubeconfig file for an additional user named foo using a kubeadm config file bar
   kubeadm kubeconfig user --client-name=foo --config=bar
 ```
diff --git a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_apply.md b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_apply.md
index 2d1d3aa37dc..dca72b0cce9 100644
--- a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_apply.md
+++ b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_apply.md
@@ -76,7 +76,7 @@ kubeadm upgrade apply [version]
 <td colspan="2">--feature-gates string</td>
 </tr>
 <tr>
-<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for various features. Options are:<br/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)</p></td>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for various features. Options are:<br/>EtcdLearnerMode=true|false (ALPHA - default=false)<br/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)</p></td>
 </tr>
 
 <tr>
diff --git a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_plan.md b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_plan.md
index d235a065264..dddf17e1877 100644
--- a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_plan.md
+++ b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_plan.md
@@ -55,7 +55,7 @@ kubeadm upgrade plan [version] [flags]
 <td colspan="2">--feature-gates string</td>
 </tr>
 <tr>
-<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for various features. Options are:<br/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)</p></td>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A set of key=value pairs that describe feature gates for various features. Options are:<br/>EtcdLearnerMode=true|false (ALPHA - default=false)<br/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)</p></td>
 </tr>
 
 <tr>

From ec9d29c0dfcacc76bbc9750f0a159cd499678dbc Mon Sep 17 00:00:00 2001
From: Pushkar Joglekar <pushkar.joglekar1789@gmail.com>
Date: Tue, 11 Apr 2023 19:18:10 -0700
Subject: [PATCH 164/272] Make the switch from alpha -> beta

---
 content/en/docs/reference/issues-security/official-cve-feed.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/reference/issues-security/official-cve-feed.md b/content/en/docs/reference/issues-security/official-cve-feed.md
index 11eb4edee1d..70497a1adfe 100644
--- a/content/en/docs/reference/issues-security/official-cve-feed.md
+++ b/content/en/docs/reference/issues-security/official-cve-feed.md
@@ -9,7 +9,7 @@ outputs:
 layout: cve-feed
 ---
 
-{{< feature-state for_k8s_version="v1.25" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
 
 This is a community maintained list of official CVEs announced by
 the Kubernetes Security Response Committee. See

From 5eecfb009fdcd5f421e1c3dda39a68478b62efd5 Mon Sep 17 00:00:00 2001
From: Guangwen Feng <fenggw-fnst@fujitsu.com>
Date: Wed, 12 Apr 2023 11:42:37 +0800
Subject: [PATCH 165/272] [zh-cn] Sync
 scheduling-eviction/topology-spread-constraints.md

Signed-off-by: Guangwen Feng <fenggw-fnst@fujitsu.com>
---
 .../topology-spread-constraints.md            | 46 ++++++++++++-------
 1 file changed, 30 insertions(+), 16 deletions(-)

diff --git a/content/zh-cn/docs/concepts/scheduling-eviction/topology-spread-constraints.md b/content/zh-cn/docs/concepts/scheduling-eviction/topology-spread-constraints.md
index afb4aefbc39..398d92d8629 100644
--- a/content/zh-cn/docs/concepts/scheduling-eviction/topology-spread-constraints.md
+++ b/content/zh-cn/docs/concepts/scheduling-eviction/topology-spread-constraints.md
@@ -105,7 +105,7 @@ spec:
       topologyKey: <string>
       whenUnsatisfiable: <string>
       labelSelector: <object>
-      matchLabelKeys: <list> # 可选；自从 v1.25 开始成为 Alpha
+      matchLabelKeys: <list> # 可选；自从 v1.27 开始成为 Beta
       nodeAffinityPolicy: [Honor|Ignore] # 可选；自从 v1.26 开始成为 Beta
       nodeTaintsPolicy: [Honor|Ignore] # 可选；自从 v1.26 开始成为 Beta
   ### 其他 Pod 字段置于此处
@@ -223,40 +223,54 @@ your cluster. Those fields are:
 
 <!--
 - **matchLabelKeys** is a list of pod label keys to select the pods over which
-  spreading will be calculated. The keys are used to lookup values from the pod labels, those key-value labels are ANDed with `labelSelector` to select the group of existing pods over which spreading will be calculated for the incoming pod. Keys that don't exist in the pod labels will be ignored. A null or empty list means only match against the `labelSelector`.
+  spreading will be calculated. The keys are used to lookup values from the pod labels,
+  those key-value labels are ANDed with `labelSelector` to select the group of existing
+  pods over which spreading will be calculated for the incoming pod. The same key is
+  forbidden to exist in both `matchLabelKeys` and `labelSelector`. `matchLabelKeys` cannot
+  be set when `labelSelector` isn't set. Keys that don't exist in the pod labels will be
+  ignored. A null or empty list means only match against the `labelSelector`.
 
-  With `matchLabelKeys`, users don't need to update the `pod.spec` between different revisions. The controller/operator just needs to set different values to the same `label` key for different revisions. The scheduler will assume the values automatically based on `matchLabelKeys`. For example, if users use Deployment, they can use the label keyed with `pod-template-hash`, which is added automatically by the Deployment controller, to distinguish between different revisions in a single Deployment.
+  With `matchLabelKeys`, you don't need to update the `pod.spec` between different revisions.
+  The controller/operator just needs to set different values to the same label key for different
+  revisions. The scheduler will assume the values automatically based on `matchLabelKeys`. For
+  example, if you are configuring a Deployment, you can use the label keyed with
+  [pod-template-hash](/docs/concepts/workloads/controllers/deployment/#pod-template-hash-label), which
+  is added automatically by the Deployment controller, to distinguish between different revisions
+  in a single Deployment.
 -->
 - **matchLabelKeys** 是一个 Pod 标签键的列表，用于选择需要计算分布方式的 Pod 集合。
   这些键用于从 Pod 标签中查找值，这些键值标签与 `labelSelector` 进行逻辑与运算，以选择一组已有的 Pod，
-  通过这些 Pod 计算新来 Pod 的分布方式。Pod 标签中不存在的键将被忽略。
+  通过这些 Pod 计算新来 Pod 的分布方式。`matchLabelKeys` 和 `labelSelector` 中禁止存在相同的键。
+  未设置 `labelSelector` 时无法设置 `matchLabelKeys`。Pod 标签中不存在的键将被忽略。
   null 或空列表意味着仅与 `labelSelector` 匹配。
 
-  借助 `matchLabelKeys`，用户无需在变更 Pod 修订版本时更新 `pod.spec`。
-  控制器或 Operator 只需要将不同修订版的 `label` 键设为不同的值。
-  调度器将根据 `matchLabelKeys` 自动确定取值。例如，如果用户使用 Deployment，
-  则他们可以使用由 Deployment 控制器自动添加的、以 `pod-template-hash` 为键的标签来区分单个
-  Deployment 的不同修订版。
+  借助 `matchLabelKeys`，你无需在变更 Pod 修订版本时更新 `pod.spec`。
+  控制器或 Operator 只需要将不同修订版的标签键设为不同的值。
+  调度器将根据 `matchLabelKeys` 自动确定取值。例如，如果你正在配置一个 Deployment，
+  则你可以使用由 Deployment 控制器自动添加的、以
+  [pod-template-hash](/zh-cn/docs/concepts/workloads/controllers/deployment/#pod-template-hash-label)
+  为键的标签来区分同一个 Deployment 的不同修订版。
 
   ```yaml
       topologySpreadConstraints:
           - maxSkew: 1
             topologyKey: kubernetes.io/hostname
             whenUnsatisfiable: DoNotSchedule
+            labelSelector:
+              matchLabels:
+                app: foo
             matchLabelKeys:
-              - app
               - pod-template-hash
   ```
 
   {{< note >}}
   <!--
-  The `matchLabelKeys` field is an alpha field added in 1.25. You have to enable the
-  `MatchLabelKeysInPodTopologySpread` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
-  in order to use it.
+  The `matchLabelKeys` field is a beta-level field and enabled by default in 1.27. You can disable it by disabling the
+  `MatchLabelKeysInPodTopologySpread` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/).
   -->
-  `matchLabelKeys` 字段是 1.25 中新增的一个 Alpha 字段。
-  你必须启用 `MatchLabelKeysInPodTopologySpread`
-  [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)才能使用此字段。
+  `matchLabelKeys` 字段是 1.27 中默认启用的一个 Beta 级别字段。
+  你可以通过禁用 `MatchLabelKeysInPodTopologySpread`
+  [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)来禁用此字段。
   {{< /note >}}
 
 <!--

From e7a91fc6b059c0d936aea2daa61e9372a2e798f8 Mon Sep 17 00:00:00 2001
From: Qiming Teng <tengqm@outlook.com>
Date: Wed, 12 Apr 2023 08:56:48 +0800
Subject: [PATCH 166/272] Single page API reference for v1.27

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

diff --git a/static/docs/reference/generated/kubernetes-api/v1.27/index.html b/static/docs/reference/generated/kubernetes-api/v1.27/index.html
new file mode 100644
index 00000000000..91e4b069718
--- /dev/null
+++ b/static/docs/reference/generated/kubernetes-api/v1.27/index.html
@@ -0,0 +1,43312 @@
+<!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="#clustercidr-v1alpha1-networking-k8s-io" class="nav-item">ClusterCIDR v1alpha1 networking.k8s.io</A></LI>
+ <UL id="clustercidr-v1alpha1-networking-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-clustercidr-v1alpha1-networking-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-clustercidr-v1alpha1-networking-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-clustercidr-v1alpha1-networking-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-clustercidr-v1alpha1-networking-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-clustercidr-v1alpha1-networking-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-clustercidr-v1alpha1-networking-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-clustercidr-v1alpha1-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-clustercidr-v1alpha1-networking-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-clustercidr-v1alpha1-networking-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-clustercidr-v1alpha1-networking-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-clustercidr-v1alpha1-networking-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-clustercidr-v1alpha1-networking-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-clustercidr-v1alpha1-networking-k8s-io" class="nav-item">Watch List</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-v1-storage-k8s-io" class="nav-item">CSIStorageCapacity v1 storage.k8s.io</A></LI>
+ <UL id="csistoragecapacity-v1-storage-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-csistoragecapacity-v1-storage-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-csistoragecapacity-v1-storage-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-csistoragecapacity-v1-storage-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-csistoragecapacity-v1-storage-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-csistoragecapacity-v1-storage-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-csistoragecapacity-v1-storage-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-csistoragecapacity-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-csistoragecapacity-v1-storage-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-csistoragecapacity-v1-storage-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-csistoragecapacity-v1-storage-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-csistoragecapacity-v1-storage-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-csistoragecapacity-v1-storage-k8s-io" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-csistoragecapacity-v1-storage-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-csistoragecapacity-v1-storage-k8s-io" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-csistoragecapacity-v1-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="#clustertrustbundle-v1alpha1-certificates-k8s-io" class="nav-item">ClusterTrustBundle v1alpha1 certificates.k8s.io</A></LI>
+ <UL id="clustertrustbundle-v1alpha1-certificates-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-clustertrustbundle-v1alpha1-certificates-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-clustertrustbundle-v1alpha1-certificates-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-clustertrustbundle-v1alpha1-certificates-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-clustertrustbundle-v1alpha1-certificates-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-clustertrustbundle-v1alpha1-certificates-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-clustertrustbundle-v1alpha1-certificates-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-clustertrustbundle-v1alpha1-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-clustertrustbundle-v1alpha1-certificates-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-clustertrustbundle-v1alpha1-certificates-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-clustertrustbundle-v1alpha1-certificates-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-clustertrustbundle-v1alpha1-certificates-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-clustertrustbundle-v1alpha1-certificates-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-clustertrustbundle-v1alpha1-certificates-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</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-v2-autoscaling" class="nav-item">HorizontalPodAutoscaler v2 autoscaling</A></LI>
+ <UL id="horizontalpodautoscaler-v2-autoscaling-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-horizontalpodautoscaler-v2-autoscaling-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-horizontalpodautoscaler-v2-autoscaling-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-horizontalpodautoscaler-v2-autoscaling-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-horizontalpodautoscaler-v2-autoscaling-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-horizontalpodautoscaler-v2-autoscaling" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-horizontalpodautoscaler-v2-autoscaling" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-horizontalpodautoscaler-v2-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-v2-autoscaling-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-horizontalpodautoscaler-v2-autoscaling-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-horizontalpodautoscaler-v2-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="#podschedulingcontext-v1alpha2-resource-k8s-io" class="nav-item">PodSchedulingContext v1alpha2 resource.k8s.io</A></LI>
+ <UL id="podschedulingcontext-v1alpha2-resource-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-podschedulingcontext-v1alpha2-resource-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-podschedulingcontext-v1alpha2-resource-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-podschedulingcontext-v1alpha2-resource-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-podschedulingcontext-v1alpha2-resource-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-podschedulingcontext-v1alpha2-resource-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-podschedulingcontext-v1alpha2-resource-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-podschedulingcontext-v1alpha2-resource-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-podschedulingcontext-v1alpha2-resource-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-podschedulingcontext-v1alpha2-resource-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-podschedulingcontext-v1alpha2-resource-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-podschedulingcontext-v1alpha2-resource-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-podschedulingcontext-v1alpha2-resource-k8s-io" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-podschedulingcontext-v1alpha2-resource-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-podschedulingcontext-v1alpha2-resource-k8s-io" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-podschedulingcontext-v1alpha2-resource-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-podschedulingcontext-v1alpha2-resource-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-podschedulingcontext-v1alpha2-resource-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-podschedulingcontext-v1alpha2-resource-k8s-io" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-podschedulingcontext-v1alpha2-resource-k8s-io" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-podschedulingcontext-v1alpha2-resource-k8s-io" class="nav-item">Replace Status</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="#resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">ResourceClaim v1alpha2 resource.k8s.io</A></LI>
+ <UL id="resourceclaim-v1alpha2-resource-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-resourceclaim-v1alpha2-resource-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-resourceclaim-v1alpha2-resource-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-resourceclaim-v1alpha2-resource-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-resourceclaim-v1alpha2-resource-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-resourceclaim-v1alpha2-resource-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-resourceclaim-v1alpha2-resource-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-resourceclaim-v1alpha2-resource-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#resourceclaimtemplate-v1alpha2-resource-k8s-io" class="nav-item">ResourceClaimTemplate v1alpha2 resource.k8s.io</A></LI>
+ <UL id="resourceclaimtemplate-v1alpha2-resource-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-resourceclaimtemplate-v1alpha2-resource-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-resourceclaimtemplate-v1alpha2-resource-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-resourceclaimtemplate-v1alpha2-resource-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-resourceclaimtemplate-v1alpha2-resource-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-resourceclaimtemplate-v1alpha2-resource-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-resourceclaimtemplate-v1alpha2-resource-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-resourceclaimtemplate-v1alpha2-resource-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-resourceclaimtemplate-v1alpha2-resource-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-resourceclaimtemplate-v1alpha2-resource-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-resourceclaimtemplate-v1alpha2-resource-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-resourceclaimtemplate-v1alpha2-resource-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-resourceclaimtemplate-v1alpha2-resource-k8s-io" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-resourceclaimtemplate-v1alpha2-resource-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-resourceclaimtemplate-v1alpha2-resource-k8s-io" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-resourceclaimtemplate-v1alpha2-resource-k8s-io" class="nav-item">Watch List All Namespaces</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#resourceclass-v1alpha2-resource-k8s-io" class="nav-item">ResourceClass v1alpha2 resource.k8s.io</A></LI>
+ <UL id="resourceclass-v1alpha2-resource-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-resourceclass-v1alpha2-resource-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-resourceclass-v1alpha2-resource-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-resourceclass-v1alpha2-resource-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-resourceclass-v1alpha2-resource-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-resourceclass-v1alpha2-resource-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-resourceclass-v1alpha2-resource-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-resourceclass-v1alpha2-resource-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-resourceclass-v1alpha2-resource-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-resourceclass-v1alpha2-resource-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-resourceclass-v1alpha2-resource-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-resourceclass-v1alpha2-resource-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-resourceclass-v1alpha2-resource-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-resourceclass-v1alpha2-resource-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">ValidatingAdmissionPolicy v1alpha1 admissionregistration.k8s.io</A></LI>
+ <UL id="validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-validatingadmissionpolicy-v1alpha1-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-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">Watch List</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io" class="nav-item">ValidatingAdmissionPolicyBinding v1alpha1 admissionregistration.k8s.io</A></LI>
+ <UL id="validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-validatingadmissionpolicybinding-v1alpha1-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-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io" 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-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">FlowSchema v1beta3 flowcontrol.apiserver.k8s.io</A></LI>
+ <UL id="flowschema-v1beta3-flowcontrol-apiserver-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-flowschema-v1beta3-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-flowschema-v1beta3-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-flowschema-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-flowschema-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-flowschema-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-flowschema-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-flowschema-v1beta3-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-v1beta3-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-flowschema-v1beta3-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-flowschema-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-flowschema-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-flowschema-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-flowschema-v1beta3-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-v1beta3-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-flowschema-v1beta3-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-flowschema-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-flowschema-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-flowschema-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><A href="#ipaddress-v1alpha1-networking-k8s-io" class="nav-item">IPAddress v1alpha1 networking.k8s.io</A></LI>
+ <UL id="ipaddress-v1alpha1-networking-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-ipaddress-v1alpha1-networking-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-ipaddress-v1alpha1-networking-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-ipaddress-v1alpha1-networking-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-ipaddress-v1alpha1-networking-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-ipaddress-v1alpha1-networking-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-ipaddress-v1alpha1-networking-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-ipaddress-v1alpha1-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-ipaddress-v1alpha1-networking-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-ipaddress-v1alpha1-networking-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-ipaddress-v1alpha1-networking-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-ipaddress-v1alpha1-networking-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-ipaddress-v1alpha1-networking-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-ipaddress-v1alpha1-networking-k8s-io" class="nav-item">Watch List</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-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">PriorityLevelConfiguration v1beta3 flowcontrol.apiserver.k8s.io</A></LI>
+ <UL id="prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-prioritylevelconfiguration-v1beta3-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-v1beta3-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-prioritylevelconfiguration-v1beta3-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-v1beta3-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-prioritylevelconfiguration-v1beta3-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="#selfsubjectreview-v1beta1-authentication-k8s-io" class="nav-item">SelfSubjectReview v1beta1 authentication.k8s.io</A></LI>
+ <UL id="selfsubjectreview-v1beta1-authentication-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-selfsubjectreview-v1beta1-authentication-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-selfsubjectreview-v1beta1-authentication-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-selfsubjectreview-v1beta1-authentication-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>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-networkpolicy-v1-networking-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-networkpolicy-v1-networking-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-networkpolicy-v1-networking-k8s-io" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-networkpolicy-v1-networking-k8s-io" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-networkpolicy-v1-networking-k8s-io" class="nav-item">Replace Status</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="#allocationresult-v1alpha2-resource-k8s-io" class="nav-item">AllocationResult v1alpha2 resource.k8s.io</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="#auditannotation-v1alpha1-admissionregistration-k8s-io" class="nav-item">AuditAnnotation v1alpha1 admissionregistration.k8s.io</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="#claimsource-v1-core" class="nav-item">ClaimSource 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="#containerresizepolicy-v1-core" class="nav-item">ContainerResizePolicy 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-v2-autoscaling" class="nav-item">CrossVersionObjectReference v2 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="#expressionwarning-v1alpha1-admissionregistration-k8s-io" class="nav-item">ExpressionWarning v1alpha1 admissionregistration.k8s.io</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="#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-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">FlowDistinguisherMethod v1beta3 flowcontrol.apiserver.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#flowschemacondition-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">FlowSchemaCondition v1beta3 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-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">GroupSubject v1beta3 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="#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="#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="#ingressloadbalanceringress-v1-networking-k8s-io" class="nav-item">IngressLoadBalancerIngress v1 networking.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#ingressloadbalancerstatus-v1-networking-k8s-io" class="nav-item">IngressLoadBalancerStatus v1 networking.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#ingressportstatus-v1-networking-k8s-io" class="nav-item">IngressPortStatus 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-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">LimitResponse v1beta3 flowcontrol.apiserver.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#limitedprioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">LimitedPriorityLevelConfiguration v1beta3 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="#matchcondition-v1-admissionregistration-k8s-io" class="nav-item">MatchCondition v1 admissionregistration.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#matchresources-v1alpha1-admissionregistration-k8s-io" class="nav-item">MatchResources v1alpha1 admissionregistration.k8s.io</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="#namedrulewithoperations-v1alpha1-admissionregistration-k8s-io" class="nav-item">NamedRuleWithOperations v1alpha1 admissionregistration.k8s.io</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-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">NonResourcePolicyRule v1beta3 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="#paramkind-v1alpha1-admissionregistration-k8s-io" class="nav-item">ParamKind v1alpha1 admissionregistration.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#paramref-v1alpha1-admissionregistration-k8s-io" class="nav-item">ParamRef v1alpha1 admissionregistration.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#parentreference-v1alpha1-networking-k8s-io" class="nav-item">ParentReference v1alpha1 networking.k8s.io</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="#podfailurepolicy-v1-batch" class="nav-item">PodFailurePolicy v1 batch</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#podfailurepolicyonexitcodesrequirement-v1-batch" class="nav-item">PodFailurePolicyOnExitCodesRequirement v1 batch</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#podfailurepolicyonpodconditionspattern-v1-batch" class="nav-item">PodFailurePolicyOnPodConditionsPattern v1 batch</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#podfailurepolicyrule-v1-batch" class="nav-item">PodFailurePolicyRule v1 batch</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="#podresourceclaim-v1-core" class="nav-item">PodResourceClaim v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#podschedulinggate-v1-core" class="nav-item">PodSchedulingGate 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-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">PolicyRulesWithSubjects v1beta3 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="#prioritylevelconfigurationcondition-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">PriorityLevelConfigurationCondition v1beta3 flowcontrol.apiserver.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#prioritylevelconfigurationreference-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">PriorityLevelConfigurationReference v1beta3 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-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">QueuingConfiguration v1beta3 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="#resourceclaim-v1-core" class="nav-item">ResourceClaim v1 core</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#resourceclaimconsumerreference-v1alpha2-resource-k8s-io" class="nav-item">ResourceClaimConsumerReference v1alpha2 resource.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#resourceclaimparametersreference-v1alpha2-resource-k8s-io" class="nav-item">ResourceClaimParametersReference v1alpha2 resource.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#resourceclaimschedulingstatus-v1alpha2-resource-k8s-io" class="nav-item">ResourceClaimSchedulingStatus v1alpha2 resource.k8s.io</A></LI>
+ </UL>
+  <UL>
+   <LI class="nav-level-2"><A href="#resourceclassparametersreference-v1alpha2-resource-k8s-io" class="nav-item">ResourceClassParametersReference v1alpha2 resource.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="#resourcehandle-v1alpha2-resource-k8s-io" class="nav-item">ResourceHandle v1alpha2 resource.k8s.io</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-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">ResourcePolicyRule v1beta3 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="#selinuxoptions-v1-core" class="nav-item">SELinuxOptions v1 core</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-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">ServiceAccountSubject v1beta3 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="#statefulsetordinals-v1-apps" class="nav-item">StatefulSetOrdinals 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-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">Subject v1beta3 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="#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="#typechecking-v1alpha1-admissionregistration-k8s-io" class="nav-item">TypeChecking v1alpha1 admissionregistration.k8s.io</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="#typedobjectreference-v1-core" class="nav-item">TypedObjectReference 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-v1beta3-flowcontrol-apiserver-k8s-io" class="nav-item">UserSubject v1beta3 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="#validation-v1alpha1-admissionregistration-k8s-io" class="nav-item">Validation v1alpha1 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="#crossversionobjectreference-v1-autoscaling" class="nav-item">CrossVersionObjectReference v1 autoscaling</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="#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="#eventseries-v1-core" class="nav-item">EventSeries v1 core</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><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-1"><A href="#flowschema-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">FlowSchema v1beta2 flowcontrol.apiserver.k8s.io</A></LI>
+ <UL id="flowschema-v1beta2-flowcontrol-apiserver-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-flowschema-v1beta2-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-flowschema-v1beta2-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-flowschema-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-flowschema-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-flowschema-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-flowschema-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-flowschema-v1beta2-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-v1beta2-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-flowschema-v1beta2-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-flowschema-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-flowschema-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-flowschema-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-flowschema-v1beta2-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-v1beta2-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-flowschema-v1beta2-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-flowschema-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-flowschema-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-flowschema-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><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-1"><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-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="#limitresponse-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">LimitResponse v1beta2 flowcontrol.apiserver.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><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-1"><A href="#matchcondition-v1alpha1-admissionregistration-k8s-io" class="nav-item">MatchCondition v1alpha1 admissionregistration.k8s.io</A></LI>
+</UL>
+<UL>
+ <LI class="nav-level-1"><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-1"><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-1"><A href="#prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">PriorityLevelConfiguration v1beta2 flowcontrol.apiserver.k8s.io</A></LI>
+ <UL id="prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-prioritylevelconfiguration-v1beta2-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-v1beta2-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-prioritylevelconfiguration-v1beta2-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-v1beta2-flowcontrol-apiserver-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><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-1"><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-1"><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-1"><A href="#resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">ResourceClaim v1alpha2 resource.k8s.io</A></LI>
+ <UL id="resourceclaim-v1alpha2-resource-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-resourceclaim-v1alpha2-resource-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-resourceclaim-v1alpha2-resource-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Create</A></LI>
+    <LI class="nav-level-2"><A href="#patch-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Patch</A></LI>
+    <LI class="nav-level-2"><A href="#replace-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Replace</A></LI>
+    <LI class="nav-level-2"><A href="#delete-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Delete</A></LI>
+    <LI class="nav-level-2"><A href="#delete-collection-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Delete Collection</A></LI>
+   </UL>
+  </UL>
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-resourceclaim-v1alpha2-resource-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
+   <UL id="-strong-read-operations-resourceclaim-v1alpha2-resource-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#read-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Read</A></LI>
+    <LI class="nav-level-2"><A href="#list-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">List</A></LI>
+    <LI class="nav-level-2"><A href="#list-all-namespaces-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">List All Namespaces</A></LI>
+    <LI class="nav-level-2"><A href="#watch-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Watch</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Watch List</A></LI>
+    <LI class="nav-level-2"><A href="#watch-list-all-namespaces-resourceclaim-v1alpha2-resource-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-resourceclaim-v1alpha2-resource-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
+   <UL id="-strong-status-operations-resourceclaim-v1alpha2-resource-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#patch-status-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Patch Status</A></LI>
+    <LI class="nav-level-2"><A href="#read-status-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Read Status</A></LI>
+    <LI class="nav-level-2"><A href="#replace-status-resourceclaim-v1alpha2-resource-k8s-io" class="nav-item">Replace Status</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><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-1"><A href="#selfsubjectreview-v1alpha1-authentication-k8s-io" class="nav-item">SelfSubjectReview v1alpha1 authentication.k8s.io</A></LI>
+ <UL id="selfsubjectreview-v1alpha1-authentication-k8s-io-nav" style="display: none;">
+  <UL>
+   <LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-selfsubjectreview-v1alpha1-authentication-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
+   <UL id="-strong-write-operations-selfsubjectreview-v1alpha1-authentication-k8s-io-strong--nav" style="display: none;">
+    <LI class="nav-level-2"><A href="#create-selfsubjectreview-v1alpha1-authentication-k8s-io" class="nav-item">Create</A></LI>
+   </UL>
+  </UL>
+ </UL>
+</UL>
+<UL>
+ <LI class="nav-level-1"><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-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-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">Subject v1beta2 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-v1beta2-flowcontrol-apiserver-k8s-io" class="nav-item">UserSubject v1beta2 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-2023 The Kubernetes Authors.</a>
+  </DIV>
+  <DIV class="col-md-6 text-right">
+    <DIV>Generated at: 2023-04-12 08:42:47 (CST)</DIV>
+    <DIV>API Version: <a href="https://github.com/kubernetes/kubernetes/blob/release-1.27/api/openapi-spec/swagger.json">v1.27.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, v1alpha1</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, v1beta1, v1alpha1</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>v2, v1</CODE></TD></TR>
+<TR><TD><CODE>batch</CODE></TD><TD><CODE>v1</CODE></TD></TR>
+<TR><TD><CODE>certificates.k8s.io</CODE></TD><TD><CODE>v1, v1alpha1</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</CODE></TD></TR>
+<TR><TD><CODE>events.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
+<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1beta3, v1beta2</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, v1alpha1</CODE></TD></TR>
+<TR><TD><CODE>node.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
+<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1</CODE></TD></TR>
+<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
+<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha2</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</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 container 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 container 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>Container 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</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. 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. Modifying this array with strategic merge patch may corrupt the data. For more information See https://github.com/kubernetes/kubernetes/issues/108255. 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>resizePolicy</CODE><BR /><I><a href="#containerresizepolicy-v1-core">ContainerResizePolicy</a> array</I></TD><TD>Resources resize policy for the container.</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.</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>allocatedResources</CODE><BR /><I>object</I></TD><TD>AllocatedResources represents the compute resources allocated for this container by the node. Kubelet sets this value to Container.Resources.Requests upon successful pod admission and after successfully admitting desired pod resize.</TD></TR>
+<TR><TD><CODE>containerID</CODE><BR /><I>string</I></TD><TD>ContainerID is the ID of the container in the format &#39;&lt;type&gt;://&lt;container_id&gt;&#39;. Where type is a container runtime identifier, returned from Version call of CRI API (for example &#34;containerd&#34;).</TD></TR>
+<TR><TD><CODE>image</CODE><BR /><I>string</I></TD><TD>Image is the name of container image that the container is running. The container image may not match the image used in the PodSpec, as it may have been resolved by the runtime. More info: https://kubernetes.io/docs/concepts/containers/images.</TD></TR>
+<TR><TD><CODE>imageID</CODE><BR /><I>string</I></TD><TD>ImageID is the image ID of the container&#39;s image. The image ID may not match the image ID of the image used in the PodSpec, as it may have been resolved by the runtime.</TD></TR>
+<TR><TD><CODE>lastState</CODE><BR /><I><a href="#containerstate-v1-core">ContainerState</a></I></TD><TD>LastTerminationState holds the last termination state of the container to help debug container crashes and restarts. This field is not populated if the container is still running and RestartCount is 0.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is a DNS_LABEL representing the unique name of the container. Each container in a pod must have a unique name across all container types. Cannot be updated.</TD></TR>
+<TR><TD><CODE>ready</CODE><BR /><I>boolean</I></TD><TD>Ready specifies whether the container is currently passing its readiness check. The value will change as readiness probes keep executing. If no readiness probes are specified, this field defaults to true once the container is fully started (see Started field).  The value is typically used to determine whether a container is ready to accept traffic.</TD></TR>
+<TR><TD><CODE>resources</CODE><BR /><I><a href="#resourcerequirements-v1-core">ResourceRequirements</a></I></TD><TD>Resources represents the compute resource requests and limits that have been successfully enacted on the running container after it has been started or has been successfully resized.</TD></TR>
+<TR><TD><CODE>restartCount</CODE><BR /><I>integer</I></TD><TD>RestartCount holds the number of times the container has been restarted. Kubelet makes an effort to always increment the value, but there are cases when the state may be lost due to node restarts and then the value may be reset to 0. The value is never negative.</TD></TR>
+<TR><TD><CODE>started</CODE><BR /><I>boolean</I></TD><TD>Started indicates whether the container has finished its postStart lifecycle hook and 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. In both cases, startup probes will run again. Is always true when no startupProbe is defined and container is running and has passed the postStart lifecycle hook. The null value must be treated the same as false.</TD></TR>
+<TR><TD><CODE>state</CODE><BR /><I><a href="#containerstate-v1-core">ContainerState</a></I></TD><TD>State holds 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-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</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>
+<TR><TD><CODE>timeZone</CODE><BR /><I>string</I></TD><TD>The time zone name for the given schedule, see https://en.wikipedia.org/wiki/List_of_tz_database_time_zones. If not specified, this will default to the time zone of the kube-controller-manager process. The set of valid time zone names and the time zone offset is loaded from the system-wide time zone database by the API server during CronJob validation and the controller manager during execution. If no system-wide time zone database can be found a bundled version of the database is used instead. If the time zone name becomes invalid during the lifetime of a CronJob or due to a change in host configuration, the controller will stop creating new new Jobs and will create a system event with the reason UnknownTimeZone. More information can be found in https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#time-zones</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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). The only allowed template.spec.restartPolicy value is &#34;Always&#34;. 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.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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. The only allowed template.spec.restartPolicy value is &#34;Always&#34;.</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.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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>
+ </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)`.  More completion modes can be added in the future. If the Job controller observes a mode that it doesn&#39;t recognize, which is possible during upgrades due to version skew, 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 null 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>podFailurePolicy</CODE><BR /><I><a href="#podfailurepolicy-v1-batch">PodFailurePolicy</a></I></TD><TD>Specifies the policy of handling failed pods. In particular, it allows to specify the set of actions and conditions which need to be satisfied to take the associated action. If empty, the default behaviour applies - the counter of failed pods, represented by the jobs&#39;s .status.failed field, is incremented and it is checked against the backoffLimit. This field cannot be used in combination with restartPolicy=OnFailure.  This field is alpha-level. To use this field, you must enable the `JobPodFailurePolicy` feature gate (disabled by default).</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.</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. The only allowed template.spec.restartPolicy values are &#34;Never&#34; or &#34;OnFailure&#34;. 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 beta-level. The job controller populates the field when the feature gate JobReadyPods is enabled (enabled 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.  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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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;.</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.</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>hostUsers</CODE><BR /><I>boolean</I></TD><TD>Use the host&#39;s user namespace. Optional: Default to true. If set to true or not present, the pod will be run in the host user namespace, useful for when the pod needs a feature only available to the host user namespace, such as loading a kernel module with CAP_SYS_MODULE. When set to false, a new userns is created for the pod. Setting false is useful for mitigating container breakout vulnerabilities even allowing users to run their containers as root without actually having root privileges on the host. This field is alpha-level and is only honored by servers that enable the UserNamespacesSupport feature.</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. 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.hostUsers - 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</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</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.</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>resourceClaims</CODE><BR /><I><a href="#podresourceclaim-v1-core">PodResourceClaim</a> array</I><BR /><B>patch strategy</B>: <I>merge,retainKeys</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>ResourceClaims defines which ResourceClaims must be allocated and reserved before the Pod is allowed to start. The resources will be made available to those containers which consume them by name.  This is an alpha field and requires enabling the DynamicResourceAllocation feature gate.  This field is immutable.</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. In some contexts, only a subset of those values may be permitted. Default to Always. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy</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</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>schedulingGates</CODE><BR /><I><a href="#podschedulinggate-v1-core">PodSchedulingGate</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>SchedulingGates is an opaque list of values that if specified will block scheduling the pod. If schedulingGates is not empty, the pod will stay in the SchedulingGated state and the scheduler will not attempt to schedule the pod.  SchedulingGates can only be set at pod creation time, and be removed only afterwards.  This is a beta feature enabled by the PodSchedulingReadiness feature gate.</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. 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.</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</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://kubernetes.io/docs/concepts/workloads/pods/pod-qos/#quality-of-service-classes</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>resize</CODE><BR /><I>string</I></TD><TD>Status of resources resize desired for pod&#39;s containers. It is empty if no resources resize is pending. Any changes to container resources will automatically set this to &#34;Proposed&#34;</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 observed 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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. The only allowed template.spec.restartPolicy value is &#34;Always&#34;. 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 observed 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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)</TD></TR>
+<TR><TD><CODE>ordinals</CODE><BR /><I><a href="#statefulsetordinals-v1-apps">StatefulSetOrdinals</a></I></TD><TD>ordinals controls the numbering of replica indices in a StatefulSet. The default ordinals behavior assigns a &#34;0&#34; index to the first replica and increments the index by one for each additional replica requested. Using the ordinals field requires the StatefulSetStartOrdinal feature gate to be enabled, which is beta.</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.</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. Each pod will be named with the format &lt;statefulsetname&gt;-&lt;podindex&gt;. For example, a pod in a StatefulSet named &#34;web&#34; with index number &#34;3&#34; would be named &#34;web-3&#34;. The only allowed template.spec.restartPolicy value is &#34;Always&#34;.</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.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-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.</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>items is the 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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="clustercidr-v1alpha1-networking-k8s-io">ClusterCIDR v1alpha1 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>v1alpha1</CODE></TD><TD><CODE>ClusterCIDR</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="#clustercidrlist-v1alpha1-networking-k8s-io">ClusterCIDRList [networking/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>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="#clustercidrspec-v1alpha1-networking-k8s-io">ClusterCIDRSpec</a></I></TD><TD>spec is the desired state of the ClusterCIDR. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="clustercidrspec-v1alpha1-networking-k8s-io">ClusterCIDRSpec v1alpha1 networking</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#clustercidr-v1alpha1-networking-k8s-io">ClusterCIDR [networking/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>ipv4</CODE><BR /><I>string</I></TD><TD>ipv4 defines an IPv4 IP block in CIDR notation(e.g. &#34;10.0.0.0/8&#34;). At least one of ipv4 and ipv6 must be specified. This field is immutable.</TD></TR>
+<TR><TD><CODE>ipv6</CODE><BR /><I>string</I></TD><TD>ipv6 defines an IPv6 IP block in CIDR notation(e.g. &#34;2001:db8::/64&#34;). At least one of ipv4 and ipv6 must be specified. This field is immutable.</TD></TR>
+<TR><TD><CODE>nodeSelector</CODE><BR /><I><a href="#nodeselector-v1-core">NodeSelector</a></I></TD><TD>nodeSelector defines which nodes the config is applicable to. An empty or nil nodeSelector selects all nodes. This field is immutable.</TD></TR>
+<TR><TD><CODE>perNodeHostBits</CODE><BR /><I>integer</I></TD><TD>perNodeHostBits defines the number of host bits to be configured per node. A subnet mask determines how much of the address is used for network bits and host bits. For example an IPv4 address of 192.168.0.0/24, splits the address into 24 bits for the network portion and 8 bits for the host portion. To allocate 256 IPs, set this field to 8 (a /24 mask for IPv4 or a /120 for IPv6). Minimum value is 4 (16 IPs). This field is immutable.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="clustercidrlist-v1alpha1-networking-k8s-io">ClusterCIDRList v1alpha1 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="#clustercidr-v1alpha1-networking-k8s-io">ClusterCIDR</a> array</I></TD><TD>items is the list of ClusterCIDRs.</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-clustercidr-v1alpha1-networking-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-clustercidr-v1alpha1-networking-k8s-io">Create</H2>
+<P>create a ClusterCIDR</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/networking.k8s.io/v1alpha1/clustercidrs</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#clustercidr-v1alpha1-networking-k8s-io">ClusterCIDR</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#clustercidr-v1alpha1-networking-k8s-io">ClusterCIDR</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#clustercidr-v1alpha1-networking-k8s-io">ClusterCIDR</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#clustercidr-v1alpha1-networking-k8s-io">ClusterCIDR</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-clustercidr-v1alpha1-networking-k8s-io">Patch</H2>
+<P>partially update the specified ClusterCIDR</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/networking.k8s.io/v1alpha1/clustercidrs/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterCIDR</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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="#clustercidr-v1alpha1-networking-k8s-io">ClusterCIDR</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#clustercidr-v1alpha1-networking-k8s-io">ClusterCIDR</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-clustercidr-v1alpha1-networking-k8s-io">Replace</H2>
+<P>replace the specified ClusterCIDR</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/networking.k8s.io/v1alpha1/clustercidrs/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterCIDR</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#clustercidr-v1alpha1-networking-k8s-io">ClusterCIDR</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#clustercidr-v1alpha1-networking-k8s-io">ClusterCIDR</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#clustercidr-v1alpha1-networking-k8s-io">ClusterCIDR</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-clustercidr-v1alpha1-networking-k8s-io">Delete</H2>
+<P>delete a ClusterCIDR</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/networking.k8s.io/v1alpha1/clustercidrs/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterCIDR</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error 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-clustercidr-v1alpha1-networking-k8s-io">Delete Collection</H2>
+<P>delete collection of ClusterCIDR</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/networking.k8s.io/v1alpha1/clustercidrs</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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-clustercidr-v1alpha1-networking-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-clustercidr-v1alpha1-networking-k8s-io">Read</H2>
+<P>read the specified ClusterCIDR</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1alpha1/clustercidrs/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterCIDR</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</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="#clustercidr-v1alpha1-networking-k8s-io">ClusterCIDR</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-clustercidr-v1alpha1-networking-k8s-io">List</H2>
+<P>list or watch objects of kind ClusterCIDR</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1alpha1/clustercidrs</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#clustercidrlist-v1alpha1-networking-k8s-io">ClusterCIDRList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-clustercidr-v1alpha1-networking-k8s-io">Watch</H2>
+<P>watch changes to an object of kind ClusterCIDR. 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/v1alpha1/watch/clustercidrs/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterCIDR</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-clustercidr-v1alpha1-networking-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of ClusterCIDR. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1alpha1/watch/clustercidrs</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 an IngressClass cluster resource. Ingress controller implementations use this field to know whether they should be serving this Ingress resource, by a transitive connection (controller -&gt; IngressClass -&gt; Ingress resource). Although the `kubernetes.io/ingress.class` annotation (simple constant name) was never formally defined, it was widely supported by Ingress controllers to create a direct binding between Ingress controller and Ingress resources. Newly created Ingress resources should prefer using the field. However, even though the annotation is officially deprecated, for backwards compatibility reasons, ingress controllers should still honor that annotation if present.</TD></TR>
+<TR><TD><CODE>rules</CODE><BR /><I><a href="#ingressrule-v1-networking-k8s-io">IngressRule</a> array</I></TD><TD>rules is 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 represents the 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="#ingressloadbalancerstatus-v1-networking-k8s-io">IngressLoadBalancerStatus</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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.</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 describes how nodes distribute service traffic they receive on one of the Service&#39;s &#34;externally-facing&#34; addresses (NodePorts, ExternalIPs, and LoadBalancer IPs). If set to &#34;Local&#34;, the proxy will configure the service in a way that assumes that external load balancers will take care of balancing the service traffic between nodes, and so each node will deliver traffic only to the node-local endpoints of the service, without masquerading the client source IP. (Traffic mistakenly sent to a node with no endpoints will be dropped.) The default value, &#34;Cluster&#34;, uses the standard behavior of routing to all endpoints evenly (possibly modified by topology and other features). Note that traffic sent to an External IP or LoadBalancer IP from within the cluster will always get &#34;Cluster&#34; semantics, but clients sending to a NodePort from within the cluster may need to take traffic policy into account when picking a node.</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). This field cannot be updated once set.</TD></TR>
+<TR><TD><CODE>internalTrafficPolicy</CODE><BR /><I>string</I></TD><TD>InternalTrafficPolicy describes how nodes distribute service traffic they receive on the ClusterIP. If set to &#34;Local&#34;, the proxy will assume that pods only want to talk to endpoints of the service on the same node as the pod, dropping the traffic if there are no local endpoints. The default value, &#34;Cluster&#34;, uses the standard behavior of routing to all endpoints evenly (possibly modified by topology and other features).</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. 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. Deprecated: This field was under-specified and its meaning varies across implementations, and it cannot support dual-stack. As of Kubernetes v1.24, users are encouraged to use implementation-specific annotations when available. This field may be removed in a future API version.</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</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</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>spec represents the 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>fsGroupPolicy 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>podInfoOnMount indicates this CSI volume driver requires additional pod information (like podName, podUID, etc.) during mount operations, if set to true. 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>seLinuxMount</CODE><BR /><I>boolean</I></TD><TD>seLinuxMount specifies if the CSI driver supports &#34;-o context&#34; mount option.  When &#34;true&#34;, the CSI driver must ensure that all volumes provided by this CSI driver can be mounted separately with different `-o context` options. This is typical for storage backends that provide volumes as filesystems on block devices or as independent shared volumes. Kubernetes will call NodeStage / NodePublish with &#34;-o context=xyz&#34; mount option when mounting a ReadWriteOncePod volume used in Pod that has explicitly set SELinux context. In the future, it may be expanded to other volume AccessModes. In any case, Kubernetes will ensure that the volume is mounted only with a single SELinux context.  When &#34;false&#34;, Kubernetes won&#39;t pass any special SELinux mount options to the driver. This is typical for volumes that represent subdirectories of a bigger shared filesystem.  Default is &#34;false&#34;.</TD></TR>
+<TR><TD><CODE>storageCapacity</CODE><BR /><I>boolean</I></TD><TD>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, if set to true.  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.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>Standard object&#39;s metadata. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>dataSource 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. When the AnyVolumeDataSource feature gate is enabled, dataSource contents will be copied to dataSourceRef, and dataSourceRef contents will be copied to dataSource when dataSourceRef.namespace is not specified. If the namespace is specified, then dataSourceRef will not be copied to dataSource.</TD></TR>
+<TR><TD><CODE>dataSourceRef</CODE><BR /><I><a href="#typedobjectreference-v1-core">TypedObjectReference</a></I></TD><TD>dataSourceRef specifies the object from which to populate the volume with data, if a non-empty volume is desired. This may be any 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, when namespace isn&#39;t specified in dataSourceRef, 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. When namespace is specified in dataSourceRef, dataSource isn&#39;t set to the same value and must be empty. There are three 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. * While dataSource only allows local objects, dataSourceRef allows objects   in any namespaces. (Beta) Using this field requires the AnyVolumeDataSource feature gate to be enabled. (Alpha) Using the namespace field of dataSourceRef requires the CrossNamespaceVolumeDataSource 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>selector is a label query over volumes to consider for binding.</TD></TR>
+<TR><TD><CODE>storageClassName</CODE><BR /><I>string</I></TD><TD>storageClassName is the 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>allocatedResources is 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>capacity 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>conditions is the 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.</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>items is 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>allowedTopologies 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>mountOptions controls the mountOptions for dynamically provisioned PersistentVolumes of this storage class. 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>reclaimPolicy controls the reclaimPolicy for dynamically provisioned PersistentVolumes of this storage class. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v1-storage-k8s-io">CSIStorageCapacity 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>CSIStorageCapacity</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="#csistoragecapacitylist-v1-storage-k8s-io">CSIStorageCapacityList [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>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.</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 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>storageClassName represents 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-v1-storage-k8s-io">CSIStorageCapacityList 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="#csistoragecapacity-v1-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-v1-storage-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-csistoragecapacity-v1-storage-k8s-io">Create</H2>
+<P>create a CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/storage.k8s.io/v1/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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-v1-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-v1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#csistoragecapacity-v1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#csistoragecapacity-v1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-csistoragecapacity-v1-storage-k8s-io">Patch</H2>
+<P>partially update the specified CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/storage.k8s.io/v1/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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-v1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#csistoragecapacity-v1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-csistoragecapacity-v1-storage-k8s-io">Replace</H2>
+<P>replace the specified CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/storage.k8s.io/v1/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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-v1-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-v1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#csistoragecapacity-v1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-csistoragecapacity-v1-storage-k8s-io">Delete</H2>
+<P>delete a CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/storage.k8s.io/v1/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-v1-storage-k8s-io">Delete Collection</H2>
+<P>delete collection of CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/storage.k8s.io/v1/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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-v1-storage-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-csistoragecapacity-v1-storage-k8s-io">Read</H2>
+<P>read the specified CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1/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-v1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-csistoragecapacity-v1-storage-k8s-io">List</H2>
+<P>list or watch objects of kind CSIStorageCapacity</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/storage.k8s.io/v1/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v1-storage-k8s-io">CSIStorageCapacityList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-csistoragecapacity-v1-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/v1/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v1-storage-k8s-io">CSIStorageCapacityList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-csistoragecapacity-v1-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/v1/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v1-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/v1/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v1-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/v1/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>name of the volume. 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>projected 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>spec represents 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 represents 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>nodeName represents 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>attachError represents 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>attached 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>attachmentMetadata is populated with any information returned by the attach operation, upon successful attach, 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>detachError represents 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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="clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle v1alpha1 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>v1alpha1</CODE></TD><TD><CODE>ClusterTrustBundle</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="#clustertrustbundlelist-v1alpha1-certificates-k8s-io">ClusterTrustBundleList [certificates/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>metadata contains the object metadata.</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#clustertrustbundlespec-v1alpha1-certificates-k8s-io">ClusterTrustBundleSpec</a></I></TD><TD>spec contains the signer (if any) and trust anchors.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="clustertrustbundlespec-v1alpha1-certificates-k8s-io">ClusterTrustBundleSpec v1alpha1 certificates</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle [certificates/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>signerName</CODE><BR /><I>string</I></TD><TD>signerName indicates the associated signer, if any.  In order to create or update a ClusterTrustBundle that sets signerName, you must have the following cluster-scoped permission: group=certificates.k8s.io resource=signers resourceName=&lt;the signer name&gt; verb=attest.  If signerName is not empty, then the ClusterTrustBundle object must be named with the signer name as a prefix (translating slashes to colons). For example, for the signer name `example.com/foo`, valid ClusterTrustBundle object names include `example.com:foo:abc` and `example.com:foo:v1`.  If signerName is empty, then the ClusterTrustBundle object&#39;s name must not have such a prefix.  List/watch requests for ClusterTrustBundles can filter on this field using a `spec.signerName=NAME` field selector.</TD></TR>
+<TR><TD><CODE>trustBundle</CODE><BR /><I>string</I></TD><TD>trustBundle contains the individual X.509 trust anchors for this bundle, as PEM bundle of PEM-wrapped, DER-formatted X.509 certificates.  The data must consist only of PEM certificate blocks that parse as valid X.509 certificates.  Each certificate must include a basic constraints extension with the CA bit set.  The API server will reject objects that contain duplicate certificates, or that use PEM block headers.  Users of ClusterTrustBundles, including Kubelet, are free to reorder and deduplicate certificate blocks in this file according to their own logic, as well as to drop PEM block headers and inter-block data.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="clustertrustbundlelist-v1alpha1-certificates-k8s-io">ClusterTrustBundleList v1alpha1 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="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a> array</I></TD><TD>items is a collection of ClusterTrustBundle 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 contains the list metadata.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-clustertrustbundle-v1alpha1-certificates-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-clustertrustbundle-v1alpha1-certificates-k8s-io">Create</H2>
+<P>create a ClusterTrustBundle</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/certificates.k8s.io/v1alpha1/clustertrustbundles</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-clustertrustbundle-v1alpha1-certificates-k8s-io">Patch</H2>
+<P>partially update the specified ClusterTrustBundle</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/certificates.k8s.io/v1alpha1/clustertrustbundles/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterTrustBundle</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-clustertrustbundle-v1alpha1-certificates-k8s-io">Replace</H2>
+<P>replace the specified ClusterTrustBundle</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/certificates.k8s.io/v1alpha1/clustertrustbundles/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterTrustBundle</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-clustertrustbundle-v1alpha1-certificates-k8s-io">Delete</H2>
+<P>delete a ClusterTrustBundle</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/certificates.k8s.io/v1alpha1/clustertrustbundles/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterTrustBundle</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error 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-clustertrustbundle-v1alpha1-certificates-k8s-io">Delete Collection</H2>
+<P>delete collection of ClusterTrustBundle</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/certificates.k8s.io/v1alpha1/clustertrustbundles</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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-clustertrustbundle-v1alpha1-certificates-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-clustertrustbundle-v1alpha1-certificates-k8s-io">Read</H2>
+<P>read the specified ClusterTrustBundle</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/certificates.k8s.io/v1alpha1/clustertrustbundles/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterTrustBundle</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</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="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-clustertrustbundle-v1alpha1-certificates-k8s-io">List</H2>
+<P>list or watch objects of kind ClusterTrustBundle</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/certificates.k8s.io/v1alpha1/clustertrustbundles</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#clustertrustbundlelist-v1alpha1-certificates-k8s-io">ClusterTrustBundleList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-clustertrustbundle-v1alpha1-certificates-k8s-io">Watch</H2>
+<P>watch changes to an object of kind ClusterTrustBundle. 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/v1alpha1/watch/clustertrustbundles/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterTrustBundle</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-clustertrustbundle-v1alpha1-certificates-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of ClusterTrustBundle. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/certificates.k8s.io/v1alpha1/watch/clustertrustbundles</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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="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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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/extend-kubernetes/custom-resources/custom-resource-definitions/#field-pruning 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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-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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v2-autoscaling">HorizontalPodAutoscaler 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>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-v1-autoscaling">v1</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>
+<H3 id="horizontalpodautoscalerspec-v2-autoscaling">HorizontalPodAutoscalerSpec v2 autoscaling</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscaler-v2-autoscaling">HorizontalPodAutoscaler [autoscaling/v2]</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-v2-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-v2-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-v2-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-v2-autoscaling">HorizontalPodAutoscalerStatus v2 autoscaling</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#horizontalpodautoscaler-v2-autoscaling">HorizontalPodAutoscaler [autoscaling/v2]</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-v2-autoscaling">HorizontalPodAutoscalerCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</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-v2-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-v2-autoscaling">HorizontalPodAutoscalerList v2 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-v2-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-v2-autoscaling-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-horizontalpodautoscaler-v2-autoscaling">Create</H2>
+<P>create a HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/autoscaling/v2/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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-v2-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-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#horizontalpodautoscaler-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-horizontalpodautoscaler-v2-autoscaling">Patch</H2>
+<P>partially update the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/autoscaling/v2/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-horizontalpodautoscaler-v2-autoscaling">Replace</H2>
+<P>replace the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/autoscaling/v2/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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-v2-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-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-horizontalpodautoscaler-v2-autoscaling">Delete</H2>
+<P>delete a HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/autoscaling/v2/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-v2-autoscaling">Delete Collection</H2>
+<P>delete collection of HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/autoscaling/v2/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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-v2-autoscaling-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-horizontalpodautoscaler-v2-autoscaling">Read</H2>
+<P>read the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v2/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-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-horizontalpodautoscaler-v2-autoscaling">List</H2>
+<P>list or watch objects of kind HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v2/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v2-autoscaling">HorizontalPodAutoscalerList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-horizontalpodautoscaler-v2-autoscaling">List All Namespaces</H2>
+<P>list or watch objects of kind HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v2/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v2-autoscaling">HorizontalPodAutoscalerList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-horizontalpodautoscaler-v2-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/v2/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v2-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/v2/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v2-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/v2/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v2-autoscaling-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-horizontalpodautoscaler-v2-autoscaling">Patch Status</H2>
+<P>partially update status of the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/autoscaling/v2/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-horizontalpodautoscaler-v2-autoscaling">Read Status</H2>
+<P>read status of the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/autoscaling/v2/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-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-horizontalpodautoscaler-v2-autoscaling">Replace Status</H2>
+<P>replace status of the specified HorizontalPodAutoscaler</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/autoscaling/v2/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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-v2-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-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2-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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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="podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext v1alpha2 resource.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>resource.k8s.io</CODE></TD><TD><CODE>v1alpha2</CODE></TD><TD><CODE>PodSchedulingContext</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="#podschedulingcontextlist-v1alpha2-resource-k8s-io">PodSchedulingContextList [resource/v1alpha2]</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</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#podschedulingcontextspec-v1alpha2-resource-k8s-io">PodSchedulingContextSpec</a></I></TD><TD>Spec describes where resources for the Pod are needed.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#podschedulingcontextstatus-v1alpha2-resource-k8s-io">PodSchedulingContextStatus</a></I></TD><TD>Status describes where resources for the Pod can be allocated.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="podschedulingcontextspec-v1alpha2-resource-k8s-io">PodSchedulingContextSpec v1alpha2 resource</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext [resource/v1alpha2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>potentialNodes</CODE><BR /><I>string array</I></TD><TD>PotentialNodes lists nodes where the Pod might be able to run.  The size of this field is limited to 128. This is large enough for many clusters. Larger clusters may need more attempts to find a node that suits all pending resources. This may get increased in the future, but not reduced.</TD></TR>
+<TR><TD><CODE>selectedNode</CODE><BR /><I>string</I></TD><TD>SelectedNode is the node for which allocation of ResourceClaims that are referenced by the Pod and that use &#34;WaitForFirstConsumer&#34; allocation is to be attempted.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="podschedulingcontextstatus-v1alpha2-resource-k8s-io">PodSchedulingContextStatus v1alpha2 resource</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext [resource/v1alpha2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>resourceClaims</CODE><BR /><I><a href="#resourceclaimschedulingstatus-v1alpha2-resource-k8s-io">ResourceClaimSchedulingStatus</a> array</I></TD><TD>ResourceClaims describes resource availability for each pod.spec.resourceClaim entry where the corresponding ResourceClaim uses &#34;WaitForFirstConsumer&#34; allocation mode.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="podschedulingcontextlist-v1alpha2-resource-k8s-io">PodSchedulingContextList v1alpha2 resource</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="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext</a> array</I></TD><TD>Items is the list of PodSchedulingContext 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-podschedulingcontext-v1alpha2-resource-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-podschedulingcontext-v1alpha2-resource-k8s-io">Create</H2>
+<P>create a PodSchedulingContext</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-podschedulingcontext-v1alpha2-resource-k8s-io">Patch</H2>
+<P>partially update the specified PodSchedulingContext</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodSchedulingContext</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-podschedulingcontext-v1alpha2-resource-k8s-io">Replace</H2>
+<P>replace the specified PodSchedulingContext</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodSchedulingContext</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-podschedulingcontext-v1alpha2-resource-k8s-io">Delete</H2>
+<P>delete a PodSchedulingContext</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodSchedulingContext</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error 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="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-podschedulingcontext-v1alpha2-resource-k8s-io">Delete Collection</H2>
+<P>delete collection of PodSchedulingContext</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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-podschedulingcontext-v1alpha2-resource-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-podschedulingcontext-v1alpha2-resource-k8s-io">Read</H2>
+<P>read the specified PodSchedulingContext</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodSchedulingContext</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</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="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-podschedulingcontext-v1alpha2-resource-k8s-io">List</H2>
+<P>list or watch objects of kind PodSchedulingContext</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#podschedulingcontextlist-v1alpha2-resource-k8s-io">PodSchedulingContextList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-podschedulingcontext-v1alpha2-resource-k8s-io">List All Namespaces</H2>
+<P>list or watch objects of kind PodSchedulingContext</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/podschedulingcontexts</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#podschedulingcontextlist-v1alpha2-resource-k8s-io">PodSchedulingContextList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-podschedulingcontext-v1alpha2-resource-k8s-io">Watch</H2>
+<P>watch changes to an object of kind PodSchedulingContext. 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/resource.k8s.io/v1alpha2/watch/namespaces/{namespace}/podschedulingcontexts/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the PodSchedulingContext</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and 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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-podschedulingcontext-v1alpha2-resource-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of PodSchedulingContext. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/watch/namespaces/{namespace}/podschedulingcontexts</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-podschedulingcontext-v1alpha2-resource-k8s-io">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of PodSchedulingContext. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/watch/podschedulingcontexts</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-podschedulingcontext-v1alpha2-resource-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-podschedulingcontext-v1alpha2-resource-k8s-io">Patch Status</H2>
+<P>partially update status of the specified PodSchedulingContext</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts/{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 PodSchedulingContext</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-podschedulingcontext-v1alpha2-resource-k8s-io">Read Status</H2>
+<P>read status of the specified PodSchedulingContext</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts/{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 PodSchedulingContext</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</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="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-podschedulingcontext-v1alpha2-resource-k8s-io">Replace Status</H2>
+<P>replace status of the specified PodSchedulingContext</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/podschedulingcontexts/{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 PodSchedulingContext</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext</a></I></TD><TD>Created</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-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>
+<TR><TD><CODE>unhealthyPodEvictionPolicy</CODE><BR /><I>string</I></TD><TD>UnhealthyPodEvictionPolicy defines the criteria for when unhealthy pods should be considered for eviction. Current implementation considers healthy pods, as pods that have status.conditions item with type=&#34;Ready&#34;,status=&#34;True&#34;.  Valid policies are IfHealthyBudget and AlwaysAllow. If no policy is specified, the default behavior will be used, which corresponds to the IfHealthyBudget policy.  IfHealthyBudget policy means that running pods (status.phase=&#34;Running&#34;), but not yet healthy can be evicted only if the guarded application is not disrupted (status.currentHealthy is at least equal to status.desiredHealthy). Healthy pods will be subject to the PDB for eviction.  AlwaysAllow policy means that all running pods (status.phase=&#34;Running&#34;), but not yet healthy are considered disrupted and can be evicted regardless of whether the criteria in a PDB is met. This means perspective running pods of a disrupted application might not get a chance to become healthy. Healthy pods will be subject to the PDB for eviction.  Additional policies may be added in the future. Clients making eviction decisions should disallow eviction of unhealthy pods if they encounter an unrecognized policy in this field.  This field is beta-level. The eviction API uses this field when the feature gate PDBUnhealthyPodEvictionPolicy is enabled (enabled by default).</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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.</TD></TR>
+<TR><TD><CODE>value</CODE><BR /><I>integer</I></TD><TD>value represents the integer 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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="resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim v1alpha2 resource.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>resource.k8s.io</CODE></TD><TD><CODE>v1alpha2</CODE></TD><TD><CODE>ResourceClaim</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="#resourceclaim-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="#resourceclaimlist-v1alpha2-resource-k8s-io">ResourceClaimList [resource/v1alpha2]</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</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#resourceclaimspec-v1alpha2-resource-k8s-io">ResourceClaimSpec</a></I></TD><TD>Spec describes the desired attributes of a resource that then needs to be allocated. It can only be set once when creating the ResourceClaim.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#resourceclaimstatus-v1alpha2-resource-k8s-io">ResourceClaimStatus</a></I></TD><TD>Status describes whether the resource is available and with which attributes.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="resourceclaimspec-v1alpha2-resource-k8s-io">ResourceClaimSpec v1alpha2 resource</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim [resource/v1alpha2]</a></LI>
+  <LI><a href="#resourceclaimtemplatespec-v1alpha2-resource-k8s-io">ResourceClaimTemplateSpec [resource/v1alpha2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allocationMode</CODE><BR /><I>string</I></TD><TD>Allocation can start immediately or when a Pod wants to use the resource. &#34;WaitForFirstConsumer&#34; is the default.</TD></TR>
+<TR><TD><CODE>parametersRef</CODE><BR /><I><a href="#resourceclaimparametersreference-v1alpha2-resource-k8s-io">ResourceClaimParametersReference</a></I></TD><TD>ParametersRef references a separate object with arbitrary parameters that will be used by the driver when allocating a resource for the claim.  The object must be in the same namespace as the ResourceClaim.</TD></TR>
+<TR><TD><CODE>resourceClassName</CODE><BR /><I>string</I></TD><TD>ResourceClassName references the driver and additional parameters via the name of a ResourceClass that was created as part of the driver deployment.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="resourceclaimstatus-v1alpha2-resource-k8s-io">ResourceClaimStatus v1alpha2 resource</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim [resource/v1alpha2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allocation</CODE><BR /><I><a href="#allocationresult-v1alpha2-resource-k8s-io">AllocationResult</a></I></TD><TD>Allocation is set by the resource driver once a resource or set of resources has been allocated successfully. If this is not specified, the resources have not been allocated yet.</TD></TR>
+<TR><TD><CODE>deallocationRequested</CODE><BR /><I>boolean</I></TD><TD>DeallocationRequested indicates that a ResourceClaim is to be deallocated.  The driver then must deallocate this claim and reset the field together with clearing the Allocation field.  While DeallocationRequested is set, no new consumers may be added to ReservedFor.</TD></TR>
+<TR><TD><CODE>driverName</CODE><BR /><I>string</I></TD><TD>DriverName is a copy of the driver name from the ResourceClass at the time when allocation started.</TD></TR>
+<TR><TD><CODE>reservedFor</CODE><BR /><I><a href="#resourceclaimconsumerreference-v1alpha2-resource-k8s-io">ResourceClaimConsumerReference</a> array</I></TD><TD>ReservedFor indicates which entities are currently allowed to use the claim. A Pod which references a ResourceClaim which is not reserved for that Pod will not be started.  There can be at most 32 such reservations. This may get increased in the future, but not reduced.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="resourceclaimlist-v1alpha2-resource-k8s-io">ResourceClaimList v1alpha2 resource</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="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a> array</I></TD><TD>Items is the list of resource claims.</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-resourceclaim-v1alpha2-resource-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-resourceclaim-v1alpha2-resource-k8s-io">Create</H2>
+<P>create a ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-resourceclaim-v1alpha2-resource-k8s-io">Patch</H2>
+<P>partially update the specified ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-resourceclaim-v1alpha2-resource-k8s-io">Replace</H2>
+<P>replace the specified ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-resourceclaim-v1alpha2-resource-k8s-io">Delete</H2>
+<P>delete a ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error 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="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-resourceclaim-v1alpha2-resource-k8s-io">Delete Collection</H2>
+<P>delete collection of ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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-resourceclaim-v1alpha2-resource-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-resourceclaim-v1alpha2-resource-k8s-io">Read</H2>
+<P>read the specified ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</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="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-resourceclaim-v1alpha2-resource-k8s-io">List</H2>
+<P>list or watch objects of kind ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourceclaimlist-v1alpha2-resource-k8s-io">ResourceClaimList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-resourceclaim-v1alpha2-resource-k8s-io">List All Namespaces</H2>
+<P>list or watch objects of kind ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/resourceclaims</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourceclaimlist-v1alpha2-resource-k8s-io">ResourceClaimList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-resourceclaim-v1alpha2-resource-k8s-io">Watch</H2>
+<P>watch changes to an object of kind ResourceClaim. 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/resource.k8s.io/v1alpha2/watch/namespaces/{namespace}/resourceclaims/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and 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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-resourceclaim-v1alpha2-resource-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of ResourceClaim. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/watch/namespaces/{namespace}/resourceclaims</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-resourceclaim-v1alpha2-resource-k8s-io">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of ResourceClaim. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/watch/resourceclaims</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-resourceclaim-v1alpha2-resource-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-resourceclaim-v1alpha2-resource-k8s-io">Patch Status</H2>
+<P>partially update status of the specified ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{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 ResourceClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-resourceclaim-v1alpha2-resource-k8s-io">Read Status</H2>
+<P>read status of the specified ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{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 ResourceClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</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="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-resourceclaim-v1alpha2-resource-k8s-io">Replace Status</H2>
+<P>replace status of the specified ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{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 ResourceClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="resourceclaimtemplate-v1alpha2-resource-k8s-io">ResourceClaimTemplate v1alpha2 resource.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>resource.k8s.io</CODE></TD><TD><CODE>v1alpha2</CODE></TD><TD><CODE>ResourceClaimTemplate</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="#resourceclaimtemplatelist-v1alpha2-resource-k8s-io">ResourceClaimTemplateList [resource/v1alpha2]</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</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#resourceclaimtemplatespec-v1alpha2-resource-k8s-io">ResourceClaimTemplateSpec</a></I></TD><TD>Describes the ResourceClaim that is to be generated.  This field is immutable. A ResourceClaim will get created by the control plane for a Pod when needed and then not get updated anymore.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="resourceclaimtemplatespec-v1alpha2-resource-k8s-io">ResourceClaimTemplateSpec v1alpha2 resource</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#resourceclaimtemplate-v1alpha2-resource-k8s-io">ResourceClaimTemplate [resource/v1alpha2]</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>ObjectMeta 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="#resourceclaimspec-v1alpha2-resource-k8s-io">ResourceClaimSpec</a></I></TD><TD>Spec for the ResourceClaim. The entire content is copied unchanged into the ResourceClaim that gets created from this template. The same fields as in a ResourceClaim are also valid here.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="resourceclaimtemplatelist-v1alpha2-resource-k8s-io">ResourceClaimTemplateList v1alpha2 resource</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="#resourceclaimtemplate-v1alpha2-resource-k8s-io">ResourceClaimTemplate</a> array</I></TD><TD>Items is the list of resource claim 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</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-resourceclaimtemplate-v1alpha2-resource-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-resourceclaimtemplate-v1alpha2-resource-k8s-io">Create</H2>
+<P>create a ResourceClaimTemplate</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaimtemplates</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclaimtemplate-v1alpha2-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourceclaimtemplate-v1alpha2-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#resourceclaimtemplate-v1alpha2-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#resourceclaimtemplate-v1alpha2-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-resourceclaimtemplate-v1alpha2-resource-k8s-io">Patch</H2>
+<P>partially update the specified ResourceClaimTemplate</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaimtemplates/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaimTemplate</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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="#resourceclaimtemplate-v1alpha2-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#resourceclaimtemplate-v1alpha2-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-resourceclaimtemplate-v1alpha2-resource-k8s-io">Replace</H2>
+<P>replace the specified ResourceClaimTemplate</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaimtemplates/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaimTemplate</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclaimtemplate-v1alpha2-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourceclaimtemplate-v1alpha2-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#resourceclaimtemplate-v1alpha2-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-resourceclaimtemplate-v1alpha2-resource-k8s-io">Delete</H2>
+<P>delete a ResourceClaimTemplate</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaimtemplates/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaimTemplate</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error 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="#resourceclaimtemplate-v1alpha2-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#resourceclaimtemplate-v1alpha2-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-resourceclaimtemplate-v1alpha2-resource-k8s-io">Delete Collection</H2>
+<P>delete collection of ResourceClaimTemplate</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaimtemplates</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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-resourceclaimtemplate-v1alpha2-resource-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-resourceclaimtemplate-v1alpha2-resource-k8s-io">Read</H2>
+<P>read the specified ResourceClaimTemplate</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaimtemplates/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaimTemplate</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</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="#resourceclaimtemplate-v1alpha2-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-resourceclaimtemplate-v1alpha2-resource-k8s-io">List</H2>
+<P>list or watch objects of kind ResourceClaimTemplate</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaimtemplates</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourceclaimtemplatelist-v1alpha2-resource-k8s-io">ResourceClaimTemplateList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-resourceclaimtemplate-v1alpha2-resource-k8s-io">List All Namespaces</H2>
+<P>list or watch objects of kind ResourceClaimTemplate</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/resourceclaimtemplates</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourceclaimtemplatelist-v1alpha2-resource-k8s-io">ResourceClaimTemplateList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-resourceclaimtemplate-v1alpha2-resource-k8s-io">Watch</H2>
+<P>watch changes to an object of kind ResourceClaimTemplate. 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/resource.k8s.io/v1alpha2/watch/namespaces/{namespace}/resourceclaimtemplates/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaimTemplate</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and 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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-resourceclaimtemplate-v1alpha2-resource-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of ResourceClaimTemplate. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/watch/namespaces/{namespace}/resourceclaimtemplates</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-resourceclaimtemplate-v1alpha2-resource-k8s-io">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of ResourceClaimTemplate. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/watch/resourceclaimtemplates</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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="resourceclass-v1alpha2-resource-k8s-io">ResourceClass v1alpha2 resource.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>resource.k8s.io</CODE></TD><TD><CODE>v1alpha2</CODE></TD><TD><CODE>ResourceClass</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="#resourceclasslist-v1alpha2-resource-k8s-io">ResourceClassList [resource/v1alpha2]</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>driverName</CODE><BR /><I>string</I></TD><TD>DriverName defines the name of the dynamic resource driver that is used for allocation of a ResourceClaim that uses this class.  Resource drivers have a unique name in forward domain order (acme.example.com).</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</TD></TR>
+<TR><TD><CODE>parametersRef</CODE><BR /><I><a href="#resourceclassparametersreference-v1alpha2-resource-k8s-io">ResourceClassParametersReference</a></I></TD><TD>ParametersRef references an arbitrary separate object that may hold parameters that will be used by the driver when allocating a resource that uses this class. A dynamic resource driver can distinguish between parameters stored here and and those stored in ResourceClaimSpec.</TD></TR>
+<TR><TD><CODE>suitableNodes</CODE><BR /><I><a href="#nodeselector-v1-core">NodeSelector</a></I></TD><TD>Only nodes matching the selector will be considered by the scheduler when trying to find a Node that fits a Pod when that Pod uses a ResourceClaim that has not been allocated yet.  Setting this field is optional. If null, all nodes are candidates.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="resourceclasslist-v1alpha2-resource-k8s-io">ResourceClassList v1alpha2 resource</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="#resourceclass-v1alpha2-resource-k8s-io">ResourceClass</a> array</I></TD><TD>Items is the list of resource classes.</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-resourceclass-v1alpha2-resource-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-resourceclass-v1alpha2-resource-k8s-io">Create</H2>
+<P>create a ResourceClass</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/resource.k8s.io/v1alpha2/resourceclasses</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclass-v1alpha2-resource-k8s-io">ResourceClass</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourceclass-v1alpha2-resource-k8s-io">ResourceClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#resourceclass-v1alpha2-resource-k8s-io">ResourceClass</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#resourceclass-v1alpha2-resource-k8s-io">ResourceClass</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-resourceclass-v1alpha2-resource-k8s-io">Patch</H2>
+<P>partially update the specified ResourceClass</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/resource.k8s.io/v1alpha2/resourceclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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="#resourceclass-v1alpha2-resource-k8s-io">ResourceClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#resourceclass-v1alpha2-resource-k8s-io">ResourceClass</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-resourceclass-v1alpha2-resource-k8s-io">Replace</H2>
+<P>replace the specified ResourceClass</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/resource.k8s.io/v1alpha2/resourceclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclass-v1alpha2-resource-k8s-io">ResourceClass</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourceclass-v1alpha2-resource-k8s-io">ResourceClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#resourceclass-v1alpha2-resource-k8s-io">ResourceClass</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-resourceclass-v1alpha2-resource-k8s-io">Delete</H2>
+<P>delete a ResourceClass</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/resource.k8s.io/v1alpha2/resourceclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error 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="#resourceclass-v1alpha2-resource-k8s-io">ResourceClass</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#resourceclass-v1alpha2-resource-k8s-io">ResourceClass</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-resourceclass-v1alpha2-resource-k8s-io">Delete Collection</H2>
+<P>delete collection of ResourceClass</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/resource.k8s.io/v1alpha2/resourceclasses</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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-resourceclass-v1alpha2-resource-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-resourceclass-v1alpha2-resource-k8s-io">Read</H2>
+<P>read the specified ResourceClass</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/resourceclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClass</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</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="#resourceclass-v1alpha2-resource-k8s-io">ResourceClass</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-resourceclass-v1alpha2-resource-k8s-io">List</H2>
+<P>list or watch objects of kind ResourceClass</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/resourceclasses</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourceclasslist-v1alpha2-resource-k8s-io">ResourceClassList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-resourceclass-v1alpha2-resource-k8s-io">Watch</H2>
+<P>watch changes to an object of kind ResourceClass. 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/resource.k8s.io/v1alpha2/watch/resourceclasses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClass</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-resourceclass-v1alpha2-resource-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of ResourceClass. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/watch/resourceclasses</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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="validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicy v1alpha1 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>v1alpha1</CODE></TD><TD><CODE>ValidatingAdmissionPolicy</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="#validatingadmissionpolicylist-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyList [admissionregistration/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>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="#validatingadmissionpolicyspec-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec</a></I></TD><TD>Specification of the desired behavior of the ValidatingAdmissionPolicy.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#validatingadmissionpolicystatus-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyStatus</a></I></TD><TD>The status of the ValidatingAdmissionPolicy, including warnings that are useful to determine if the policy behaves in the expected way. Populated by the system. Read-only.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="validatingadmissionpolicyspec-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec v1alpha1 admissionregistration</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicy [admissionregistration/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>auditAnnotations</CODE><BR /><I><a href="#auditannotation-v1alpha1-admissionregistration-k8s-io">AuditAnnotation</a> array</I></TD><TD>auditAnnotations contains CEL expressions which are used to produce audit annotations for the audit event of the API request. validations and auditAnnotations may not both be empty; a least one of validations or auditAnnotations is required.</TD></TR>
+<TR><TD><CODE>failurePolicy</CODE><BR /><I>string</I></TD><TD>failurePolicy defines how to handle failures for the admission policy. Failures can occur from CEL expression parse errors, type check errors, runtime errors and invalid or mis-configured policy definitions or bindings.  A policy is invalid if spec.paramKind refers to a non-existent Kind. A binding is invalid if spec.paramRef.name refers to a non-existent resource.  failurePolicy does not define how validations that evaluate to false are handled.  When failurePolicy is set to Fail, ValidatingAdmissionPolicyBinding validationActions define how failures are enforced.  Allowed values are Ignore or Fail. Defaults to Fail.</TD></TR>
+<TR><TD><CODE>matchConditions</CODE><BR /><I><a href="#matchcondition-v1alpha1-admissionregistration-k8s-io">MatchCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>MatchConditions is a list of conditions that must be met for a request to be validated. Match conditions filter requests that have already been matched by the rules, namespaceSelector, and objectSelector. An empty list of matchConditions matches all requests. There are a maximum of 64 match conditions allowed.  If a parameter object is provided, it can be accessed via the `params` handle in the same manner as validation expressions.  The exact matching logic is (in order):   1. If ANY matchCondition evaluates to FALSE, the policy is skipped.   2. If ALL matchConditions evaluate to TRUE, the policy is evaluated.   3. If any matchCondition evaluates to an error (but none are FALSE):      - If failurePolicy=Fail, reject the request      - If failurePolicy=Ignore, the policy is skipped</TD></TR>
+<TR><TD><CODE>matchConstraints</CODE><BR /><I><a href="#matchresources-v1alpha1-admissionregistration-k8s-io">MatchResources</a></I></TD><TD>MatchConstraints specifies what resources this policy is designed to validate. The AdmissionPolicy cares about a request if it matches _all_ Constraints. However, in order to prevent clusters from being put into an unstable state that cannot be recovered from via the API ValidatingAdmissionPolicy cannot match ValidatingAdmissionPolicy and ValidatingAdmissionPolicyBinding. Required.</TD></TR>
+<TR><TD><CODE>paramKind</CODE><BR /><I><a href="#paramkind-v1alpha1-admissionregistration-k8s-io">ParamKind</a></I></TD><TD>ParamKind specifies the kind of resources used to parameterize this policy. If absent, there are no parameters for this policy and the param CEL variable will not be provided to validation expressions. If ParamKind refers to a non-existent kind, this policy definition is mis-configured and the FailurePolicy is applied. If paramKind is specified but paramRef is unset in ValidatingAdmissionPolicyBinding, the params variable will be null.</TD></TR>
+<TR><TD><CODE>validations</CODE><BR /><I><a href="#validation-v1alpha1-admissionregistration-k8s-io">Validation</a> array</I></TD><TD>Validations contain CEL expressions which is used to apply the validation. Validations and AuditAnnotations may not both be empty; a minimum of one Validations or AuditAnnotations is required.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="validatingadmissionpolicystatus-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyStatus v1alpha1 admissionregistration</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicy [admissionregistration/v1alpha1]</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></TD><TD>The conditions represent the latest available observations of a policy&#39;s current state.</TD></TR>
+<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>The generation observed by the controller.</TD></TR>
+<TR><TD><CODE>typeChecking</CODE><BR /><I><a href="#typechecking-v1alpha1-admissionregistration-k8s-io">TypeChecking</a></I></TD><TD>The results of type checking for each expression. Presence of this field indicates the completion of the type checking.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="validatingadmissionpolicylist-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyList v1alpha1 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="#validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a> array</I></TD><TD>List of ValidatingAdmissionPolicy.</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-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">Create</H2>
+<P>create a ValidatingAdmissionPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">Patch</H2>
+<P>partially update the specified ValidatingAdmissionPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicy</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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="#validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">Replace</H2>
+<P>replace the specified ValidatingAdmissionPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicy</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">Delete</H2>
+<P>delete a ValidatingAdmissionPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicy</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error 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-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">Delete Collection</H2>
+<P>delete collection of ValidatingAdmissionPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">Read</H2>
+<P>read the specified ValidatingAdmissionPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicy</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</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="#validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">List</H2>
+<P>list or watch objects of kind ValidatingAdmissionPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#validatingadmissionpolicylist-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">Watch</H2>
+<P>watch changes to an object of kind ValidatingAdmissionPolicy. 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/v1alpha1/watch/validatingadmissionpolicies/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicy</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of ValidatingAdmissionPolicy. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/admissionregistration.k8s.io/v1alpha1/watch/validatingadmissionpolicies</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">Patch Status</H2>
+<P>partially update status of the specified ValidatingAdmissionPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{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 ValidatingAdmissionPolicy</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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="#validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">Read Status</H2>
+<P>read status of the specified ValidatingAdmissionPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{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 ValidatingAdmissionPolicy</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</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="#validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">Replace Status</H2>
+<P>replace status of the specified ValidatingAdmissionPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{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 ValidatingAdmissionPolicy</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding v1alpha1 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>v1alpha1</CODE></TD><TD><CODE>ValidatingAdmissionPolicyBinding</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="#validatingadmissionpolicybindinglist-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingList [admissionregistration/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>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="#validatingadmissionpolicybindingspec-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingSpec</a></I></TD><TD>Specification of the desired behavior of the ValidatingAdmissionPolicyBinding.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="validatingadmissionpolicybindingspec-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingSpec v1alpha1 admissionregistration</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding [admissionregistration/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>matchResources</CODE><BR /><I><a href="#matchresources-v1alpha1-admissionregistration-k8s-io">MatchResources</a></I></TD><TD>MatchResources declares what resources match this binding and will be validated by it. Note that this is intersected with the policy&#39;s matchConstraints, so only requests that are matched by the policy can be selected by this. If this is unset, all resources matched by the policy are validated by this binding When resourceRules is unset, it does not constrain resource matching. If a resource is matched by the other fields of this object, it will be validated. Note that this is differs from ValidatingAdmissionPolicy matchConstraints, where resourceRules are required.</TD></TR>
+<TR><TD><CODE>paramRef</CODE><BR /><I><a href="#paramref-v1alpha1-admissionregistration-k8s-io">ParamRef</a></I></TD><TD>ParamRef specifies the parameter resource used to configure the admission control policy. It should point to a resource of the type specified in ParamKind of the bound ValidatingAdmissionPolicy. If the policy specifies a ParamKind and the resource referred to by ParamRef does not exist, this binding is considered mis-configured and the FailurePolicy of the ValidatingAdmissionPolicy applied.</TD></TR>
+<TR><TD><CODE>policyName</CODE><BR /><I>string</I></TD><TD>PolicyName references a ValidatingAdmissionPolicy name which the ValidatingAdmissionPolicyBinding binds to. If the referenced resource does not exist, this binding is considered invalid and will be ignored Required.</TD></TR>
+<TR><TD><CODE>validationActions</CODE><BR /><I>string array</I></TD><TD>validationActions declares how Validations of the referenced ValidatingAdmissionPolicy are enforced. If a validation evaluates to false it is always enforced according to these actions.  Failures defined by the ValidatingAdmissionPolicy&#39;s FailurePolicy are enforced according to these actions only if the FailurePolicy is set to Fail, otherwise the failures are ignored. This includes compilation errors, runtime errors and misconfigurations of the policy.  validationActions is declared as a set of action values. Order does not matter. validationActions may not contain duplicates of the same action.  The supported actions values are:  &#34;Deny&#34; specifies that a validation failure results in a denied request.  &#34;Warn&#34; specifies that a validation failure is reported to the request client in HTTP Warning headers, with a warning code of 299. Warnings can be sent both for allowed or denied admission responses.  &#34;Audit&#34; specifies that a validation failure is included in the published audit event for the request. The audit event will contain a `validation.policy.admission.k8s.io/validation_failure` audit annotation with a value containing the details of the validation failures, formatted as a JSON list of objects, each with the following fields: - message: The validation failure message string - policy: The resource name of the ValidatingAdmissionPolicy - binding: The resource name of the ValidatingAdmissionPolicyBinding - expressionIndex: The index of the failed validations in the ValidatingAdmissionPolicy - validationActions: The enforcement actions enacted for the validation failure Example audit annotation: `&#34;validation.policy.admission.k8s.io/validation_failure&#34;: &#34;[{&#34;message&#34;: &#34;Invalid value&#34;, {&#34;policy&#34;: &#34;policy.example.com&#34;, {&#34;binding&#34;: &#34;policybinding.example.com&#34;, {&#34;expressionIndex&#34;: &#34;1&#34;, {&#34;validationActions&#34;: [&#34;Audit&#34;]}]&#34;`  Clients should expect to handle additional values by ignoring any values not recognized.  &#34;Deny&#34; and &#34;Warn&#34; may not be used together since this combination needlessly duplicates the validation failure both in the API response body and the HTTP warning headers.  Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="validatingadmissionpolicybindinglist-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingList v1alpha1 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="#validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a> array</I></TD><TD>List of PolicyBinding.</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-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">Create</H2>
+<P>create a ValidatingAdmissionPolicyBinding</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicybindings</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">Patch</H2>
+<P>partially update the specified ValidatingAdmissionPolicyBinding</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicybindings/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicyBinding</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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="#validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">Replace</H2>
+<P>replace the specified ValidatingAdmissionPolicyBinding</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicybindings/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicyBinding</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">Delete</H2>
+<P>delete a ValidatingAdmissionPolicyBinding</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicybindings/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicyBinding</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error 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-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">Delete Collection</H2>
+<P>delete collection of ValidatingAdmissionPolicyBinding</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicybindings</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">Read</H2>
+<P>read the specified ValidatingAdmissionPolicyBinding</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicybindings/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicyBinding</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</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="#validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">List</H2>
+<P>list or watch objects of kind ValidatingAdmissionPolicyBinding</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicybindings</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#validatingadmissionpolicybindinglist-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">Watch</H2>
+<P>watch changes to an object of kind ValidatingAdmissionPolicyBinding. 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/v1alpha1/watch/validatingadmissionpolicybindings/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicyBinding</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of ValidatingAdmissionPolicyBinding. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/admissionregistration.k8s.io/v1alpha1/watch/validatingadmissionpolicybindings</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchema v1beta3 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>v1beta3</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-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchemaList [flowcontrol/v1beta3]</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-v1beta3-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-v1beta3-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-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchemaSpec v1beta3 flowcontrol</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#flowschema-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchema [flowcontrol/v1beta3]</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-v1beta3-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-v1beta3-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-v1beta3-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-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchemaStatus v1beta3 flowcontrol</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#flowschema-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchema [flowcontrol/v1beta3]</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-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchemaCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>`conditions` is a list of the current states of FlowSchema.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="flowschemalist-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchemaList v1beta3 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-v1beta3-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-v1beta3-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-flowschema-v1beta3-flowcontrol-apiserver-k8s-io">Create</H2>
+<P>create a FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/flowcontrol.apiserver.k8s.io/v1beta3/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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-v1beta3-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-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#flowschema-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#flowschema-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-flowschema-v1beta3-flowcontrol-apiserver-k8s-io">Patch</H2>
+<P>partially update the specified FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/flowcontrol.apiserver.k8s.io/v1beta3/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#flowschema-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-flowschema-v1beta3-flowcontrol-apiserver-k8s-io">Replace</H2>
+<P>replace the specified FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/flowcontrol.apiserver.k8s.io/v1beta3/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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-v1beta3-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-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#flowschema-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-flowschema-v1beta3-flowcontrol-apiserver-k8s-io">Delete</H2>
+<P>delete a FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/flowcontrol.apiserver.k8s.io/v1beta3/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-v1beta3-flowcontrol-apiserver-k8s-io">Delete Collection</H2>
+<P>delete collection of FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/flowcontrol.apiserver.k8s.io/v1beta3/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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-v1beta3-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-flowschema-v1beta3-flowcontrol-apiserver-k8s-io">Read</H2>
+<P>read the specified FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta3/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-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-flowschema-v1beta3-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/v1beta3/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchemaList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-flowschema-v1beta3-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/v1beta3/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v1beta3-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/v1beta3/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v1beta3-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-flowschema-v1beta3-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/v1beta3/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#flowschema-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-flowschema-v1beta3-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/v1beta3/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-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-flowschema-v1beta3-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/v1beta3/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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-v1beta3-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-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#flowschema-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="ipaddress-v1alpha1-networking-k8s-io">IPAddress v1alpha1 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>v1alpha1</CODE></TD><TD><CODE>IPAddress</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="#ipaddresslist-v1alpha1-networking-k8s-io">IPAddressList [networking/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>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="#ipaddressspec-v1alpha1-networking-k8s-io">IPAddressSpec</a></I></TD><TD>spec is the desired state of the IPAddress. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="ipaddressspec-v1alpha1-networking-k8s-io">IPAddressSpec v1alpha1 networking</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#ipaddress-v1alpha1-networking-k8s-io">IPAddress [networking/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>parentRef</CODE><BR /><I><a href="#parentreference-v1alpha1-networking-k8s-io">ParentReference</a></I></TD><TD>ParentRef references the resource that an IPAddress is attached to. An IPAddress must reference a parent object.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="ipaddresslist-v1alpha1-networking-k8s-io">IPAddressList v1alpha1 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="#ipaddress-v1alpha1-networking-k8s-io">IPAddress</a> array</I></TD><TD>items is the list of IPAddresses.</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-ipaddress-v1alpha1-networking-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-ipaddress-v1alpha1-networking-k8s-io">Create</H2>
+<P>create an IPAddress</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/networking.k8s.io/v1alpha1/ipaddresses</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#ipaddress-v1alpha1-networking-k8s-io">IPAddress</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#ipaddress-v1alpha1-networking-k8s-io">IPAddress</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#ipaddress-v1alpha1-networking-k8s-io">IPAddress</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#ipaddress-v1alpha1-networking-k8s-io">IPAddress</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-ipaddress-v1alpha1-networking-k8s-io">Patch</H2>
+<P>partially update the specified IPAddress</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/networking.k8s.io/v1alpha1/ipaddresses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the IPAddress</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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="#ipaddress-v1alpha1-networking-k8s-io">IPAddress</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#ipaddress-v1alpha1-networking-k8s-io">IPAddress</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-ipaddress-v1alpha1-networking-k8s-io">Replace</H2>
+<P>replace the specified IPAddress</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/networking.k8s.io/v1alpha1/ipaddresses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the IPAddress</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#ipaddress-v1alpha1-networking-k8s-io">IPAddress</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#ipaddress-v1alpha1-networking-k8s-io">IPAddress</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#ipaddress-v1alpha1-networking-k8s-io">IPAddress</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-ipaddress-v1alpha1-networking-k8s-io">Delete</H2>
+<P>delete an IPAddress</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/networking.k8s.io/v1alpha1/ipaddresses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the IPAddress</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error 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-ipaddress-v1alpha1-networking-k8s-io">Delete Collection</H2>
+<P>delete collection of IPAddress</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/networking.k8s.io/v1alpha1/ipaddresses</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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-ipaddress-v1alpha1-networking-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-ipaddress-v1alpha1-networking-k8s-io">Read</H2>
+<P>read the specified IPAddress</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1alpha1/ipaddresses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the IPAddress</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</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="#ipaddress-v1alpha1-networking-k8s-io">IPAddress</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-ipaddress-v1alpha1-networking-k8s-io">List</H2>
+<P>list or watch objects of kind IPAddress</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1alpha1/ipaddresses</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#ipaddresslist-v1alpha1-networking-k8s-io">IPAddressList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-ipaddress-v1alpha1-networking-k8s-io">Watch</H2>
+<P>watch changes to an object of kind IPAddress. 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/v1alpha1/watch/ipaddresses/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the IPAddress</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-ipaddress-v1alpha1-networking-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of IPAddress. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1alpha1/watch/ipaddresses</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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="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>spec contains the 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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/</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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: Previously used to specify the source of the node&#39;s configuration for the DynamicKubeletConfig feature. This feature is removed.</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 https://pr.k8s.io/79391 for an example. Consumers should assume that addresses can change during the lifetime of a Node. However, there are some exceptions where this may not be possible, such as Pods that inherit a Node&#39;s address in its own status or consumers of the downward API (status.hostIP).</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.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>capacity is the 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>mountOptions is the 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>persistentVolumeReclaimPolicy defines 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</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>storageClassName is the 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>message is 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</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>items is a 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration v1beta3 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>v1beta3</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-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationList [flowcontrol/v1beta3]</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-v1beta3-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-v1beta3-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-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationSpec v1beta3 flowcontrol</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration [flowcontrol/v1beta3]</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-v1beta3-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-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationStatus v1beta3 flowcontrol</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration [flowcontrol/v1beta3]</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-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>`conditions` is the current state of &#34;request-priority&#34;.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="prioritylevelconfigurationlist-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationList v1beta3 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-v1beta3-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-v1beta3-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io">Create</H2>
+<P>create a PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/flowcontrol.apiserver.k8s.io/v1beta3/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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-v1beta3-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-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io">Patch</H2>
+<P>partially update the specified PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/flowcontrol.apiserver.k8s.io/v1beta3/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io">Replace</H2>
+<P>replace the specified PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/flowcontrol.apiserver.k8s.io/v1beta3/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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-v1beta3-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-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io">Delete</H2>
+<P>delete a PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/flowcontrol.apiserver.k8s.io/v1beta3/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-v1beta3-flowcontrol-apiserver-k8s-io">Delete Collection</H2>
+<P>delete collection of PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/flowcontrol.apiserver.k8s.io/v1beta3/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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-v1beta3-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io">Read</H2>
+<P>read the specified PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta3/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-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-prioritylevelconfiguration-v1beta3-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/v1beta3/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-prioritylevelconfiguration-v1beta3-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/v1beta3/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v1beta3-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/v1beta3/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v1beta3-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-prioritylevelconfiguration-v1beta3-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/v1beta3/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-prioritylevelconfiguration-v1beta3-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/v1beta3/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-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-prioritylevelconfiguration-v1beta3-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/v1beta3/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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-v1beta3-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-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1beta3-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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-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/</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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="selfsubjectreview-v1beta1-authentication-k8s-io">SelfSubjectReview v1beta1 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>v1beta1</CODE></TD><TD><CODE>SelfSubjectReview</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="#selfsubjectreview-v1alpha1-authentication-k8s-io">v1alpha1</a>
+</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>status</CODE><BR /><I><a href="#selfsubjectreviewstatus-v1beta1-authentication-k8s-io">SelfSubjectReviewStatus</a></I></TD><TD>Status is filled in by the server with the user attributes.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="selfsubjectreviewstatus-v1beta1-authentication-k8s-io">SelfSubjectReviewStatus v1beta1 authentication</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#selfsubjectreview-v1beta1-authentication-k8s-io">SelfSubjectReview [authentication/v1beta1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>userInfo</CODE><BR /><I><a href="#userinfo-v1-authentication-k8s-io">UserInfo</a></I></TD><TD>User attributes of the user making this request.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-selfsubjectreview-v1beta1-authentication-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-selfsubjectreview-v1beta1-authentication-k8s-io">Create</H2>
+<P>create a SelfSubjectReview</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/authentication.k8s.io/v1beta1/selfsubjectreviews</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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="#selfsubjectreview-v1beta1-authentication-k8s-io">SelfSubjectReview</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#selfsubjectreview-v1beta1-authentication-k8s-io">SelfSubjectReview</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#selfsubjectreview-v1beta1-authentication-k8s-io">SelfSubjectReview</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#selfsubjectreview-v1beta1-authentication-k8s-io">SelfSubjectReview</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 a list of the secrets in the same namespace that pods running using this ServiceAccount are allowed to use. Pods are only limited to this list if this service account has a &#34;kubernetes.io/enforce-mountable-secrets&#34; annotation set to &#34;true&#34;. This field should not be used to find auto-generated service account token secrets for use outside of pods. Instead, tokens can be requested directly using the TokenRequest API, or service account token secrets can be manually created. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 identify 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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>spec represents the specification of the desired behavior for this NetworkPolicy.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#networkpolicystatus-v1-networking-k8s-io">NetworkPolicyStatus</a></I></TD><TD>status represents the current state of the NetworkPolicy. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</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>egress is a 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>ingress is a 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>podSelector 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>policyTypes is a 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="networkpolicystatus-v1-networking-k8s-io">NetworkPolicyStatus 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>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 holds an array of metav1.Condition that describe the state of the NetworkPolicy. Current service state</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-networkpolicy-v1-networking-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-networkpolicy-v1-networking-k8s-io">Patch Status</H2>
+<P>partially update status of the specified NetworkPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{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 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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="read-status-networkpolicy-v1-networking-k8s-io">Read Status</H2>
+<P>read status of the specified NetworkPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{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 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="replace-status-networkpolicy-v1-networking-k8s-io">Replace Status</H2>
+<P>replace status of the specified NetworkPolicy</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{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 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>
+<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>fsType is the 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>partition is 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>readOnly value true will force the readOnly setting in VolumeMounts. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore</TD></TR>
+<TR><TD><CODE>volumeID</CODE><BR /><I>string</I></TD><TD>volumeID is 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="allocationresult-v1alpha2-resource-k8s-io">AllocationResult v1alpha2 resource.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>resource.k8s.io</CODE></TD><TD><CODE>v1alpha2</CODE></TD><TD><CODE>AllocationResult</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>AllocationResult contains attributes of an allocated resource.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#resourceclaimstatus-v1alpha2-resource-k8s-io">ResourceClaimStatus [resource/v1alpha2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>availableOnNodes</CODE><BR /><I><a href="#nodeselector-v1-core">NodeSelector</a></I></TD><TD>This field will get set by the resource driver after it has allocated the resource to inform the scheduler where it can schedule Pods using the ResourceClaim.  Setting this field is optional. If null, the resource is available everywhere.</TD></TR>
+<TR><TD><CODE>resourceHandles</CODE><BR /><I><a href="#resourcehandle-v1alpha2-resource-k8s-io">ResourceHandle</a> array</I></TD><TD>ResourceHandles contain the state associated with an allocation that should be maintained throughout the lifetime of a claim. Each ResourceHandle contains data that should be passed to a specific kubelet plugin once it lands on a node. This data is returned by the driver after a successful allocation and is opaque to Kubernetes. Driver documentation may explain to users how to interpret this data if needed.  Setting this field is optional. It has a maximum size of 32 entries. If null (or empty), it is assumed this allocation will be processed by a single kubelet plugin with no ResourceHandle data attached. The name of the kubelet plugin invoked will match the DriverName set in the ResourceClaimStatus this AllocationResult is embedded in.</TD></TR>
+<TR><TD><CODE>shareable</CODE><BR /><I>boolean</I></TD><TD>Shareable determines whether the resource supports more than one consumer at a time.</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="auditannotation-v1alpha1-admissionregistration-k8s-io">AuditAnnotation v1alpha1 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>v1alpha1</CODE></TD><TD><CODE>AuditAnnotation</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>AuditAnnotation describes how to produce an audit annotation for an API request.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#validatingadmissionpolicyspec-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec [admissionregistration/v1alpha1]</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>key specifies the audit annotation key. The audit annotation keys of a ValidatingAdmissionPolicy must be unique. The key must be a qualified name ([A-Za-z0-9][-A-Za-z0-9_.]*) no more than 63 bytes in length.  The key is combined with the resource name of the ValidatingAdmissionPolicy to construct an audit annotation key: &#34;{ValidatingAdmissionPolicy name}/{key}&#34;.  If an admission webhook uses the same resource name as this ValidatingAdmissionPolicy and the same audit annotation key, the annotation key will be identical. In this case, the first annotation written with the key will be included in the audit event and all subsequent annotations with the same key will be discarded.  Required.</TD></TR>
+<TR><TD><CODE>valueExpression</CODE><BR /><I>string</I></TD><TD>valueExpression represents the expression which is evaluated by CEL to produce an audit annotation value. The expression must evaluate to either a string or null value. If the expression evaluates to a string, the audit annotation is included with the string value. If the expression evaluates to null or empty string the audit annotation will be omitted. The valueExpression may be no longer than 5kb in length. If the result of the valueExpression is more than 10kb in length, it will be truncated to 10kb.  If multiple ValidatingAdmissionPolicyBinding resources match an API request, then the valueExpression will be evaluated for each binding. All unique values produced by the valueExpressions will be joined together in a comma-separated list.  Required.</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>cachingMode is the Host Caching mode: None, Read Only, Read Write.</TD></TR>
+<TR><TD><CODE>diskName</CODE><BR /><I>string</I></TD><TD>diskName is the Name of the data disk in the blob storage</TD></TR>
+<TR><TD><CODE>diskURI</CODE><BR /><I>string</I></TD><TD>diskURI is the URI of data disk in the blob storage</TD></TR>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>fsType is 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>kind expected values are 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>readOnly 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>readOnly 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>secretName is 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>secretNamespace is 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>shareName is the azure 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>readOnly 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>secretName is 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>shareName is the azure 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>name represents 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 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>fsType 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>nodeExpandSecretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>nodeExpandSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI NodeExpandVolume call. This is a beta field which is enabled default by CSINodeExpandSecret feature gate. This field is optional, may be omitted if no secret is required. If the secret object contains more than one secret, all secrets are passed.</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>readOnly value to pass to ControllerPublishVolumeRequest. Defaults to false (read/write).</TD></TR>
+<TR><TD><CODE>volumeAttributes</CODE><BR /><I>object</I></TD><TD>volumeAttributes 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>fsType 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>readOnly 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>monitors is 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>path is 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>readOnly is 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>secretFile is 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>secretRef is 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>user is 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>monitors is 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>path is 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>readOnly is 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>secretFile is 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>secretRef is 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>user is 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.</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>fsType 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>readOnly is 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>secretRef is 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>volumeID 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>fsType is the 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>readOnly 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>secretRef is 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>volumeID used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="claimsource-v1-core">ClaimSource 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>ClaimSource</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ClaimSource describes a reference to a ResourceClaim.
+
+Exactly one of these fields should be set.  Consumers of this type must treat an empty object as if it has an unknown value.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podresourceclaim-v1-core">PodResourceClaim [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>resourceClaimName</CODE><BR /><I>string</I></TD><TD>ResourceClaimName is the name of a ResourceClaim object in the same namespace as this pod.</TD></TR>
+<TR><TD><CODE>resourceClaimTemplateName</CODE><BR /><I>string</I></TD><TD>ResourceClaimTemplateName is the name of a ResourceClaimTemplate object in the same namespace as this pod.  The template will be used to create a new ResourceClaim, which will be bound to this pod. When this pod is deleted, the ResourceClaim will also be deleted. The name of the ResourceClaim will be &lt;pod name&gt;-&lt;resource name&gt;, where &lt;resource name&gt; is the PodResourceClaim.Name. Pod validation will reject the pod if the concatenated name is not valid for a ResourceClaim (e.g. too long).  An existing ResourceClaim with that name that is not owned by the pod will not be used for the pod to avoid using an unrelated resource by mistake. Scheduling and pod startup are then blocked until the unrelated ResourceClaim is removed.  This field is immutable and no changes will be made to the corresponding ResourceClaim by the control plane after creating the ResourceClaim.</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="#networkpolicystatus-v1-networking-k8s-io">NetworkPolicyStatus [networking/v1]</a></LI>
+  <LI><a href="#poddisruptionbudgetstatus-v1-policy">PodDisruptionBudgetStatus [policy/v1]</a></LI>
+  <LI><a href="#servicestatus-v1-core">ServiceStatus [core/v1]</a></LI>
+  <LI><a href="#validatingadmissionpolicystatus-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyStatus [admissionregistration/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>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>items 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>optional 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>defaultMode is 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>items 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>optional 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;kubernetes.example/hyperkube:v1.0.7&#34;, &#34;cloud-vendor.registry.example/cloud-vendor/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;.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="containerresizepolicy-v1-core">ContainerResizePolicy 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>ContainerResizePolicy</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ContainerResizePolicy represents resource resize policy for the 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>resourceName</CODE><BR /><I>string</I></TD><TD>Name of the resource to which this resource resize policy applies. Supported values: cpu, memory.</TD></TR>
+<TR><TD><CODE>restartPolicy</CODE><BR /><I>string</I></TD><TD>Restart policy to apply when specified resource is resized. If not specified, it defaults to NotRequired.</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-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-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;&lt;type&gt;://&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-v2-autoscaling">CrossVersionObjectReference 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>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-v1-autoscaling">v1</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>apiVersion is the API version of the referent</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>kind is the 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 is the name of the referent; More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#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: - `&#34;None&#34;`: The converter only change the apiVersion and would not touch any other field in the custom resource. - `&#34;Webhook&#34;`: 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 `&#34;Webhook&#34;`.</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.</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>medium represents 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>sizeLimit is the 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: https://kubernetes.io/docs/concepts/storage/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-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. These are all assumed to be fungible and clients may choose to only use the first element. Refer to: https://issue.k8s.io/106267</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.</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 or ::1), link-local (169.254.0.0/16 or fe80::/10), or link-local multicast (224.0.0.0/24 or ff02::/16).</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-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, except when the normal readiness behavior is being explicitly overridden, for example when the associated Service has set the publishNotReadyAddresses flag.</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.</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.</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-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-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 is used as a hint for implementations to offer richer behavior for protocols that they understand. This field follows standard Kubernetes label syntax. Valid values are either:  * Un-prefixed protocol names - reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names).  * Kubernetes-defined prefixed names:   * &#39;kubernetes.io/h2c&#39; - HTTP/2 over cleartext as described in https://www.rfc-editor.org/rfc/rfc7540  * Other protocols should use implementation-defined 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.</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.</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 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 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>Container 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</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>resizePolicy</CODE><BR /><I><a href="#containerresizepolicy-v1-core">ContainerResizePolicy</a> array</I></TD><TD>Resources resize policy for the container.</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.</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-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>
+ </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="expressionwarning-v1alpha1-admissionregistration-k8s-io">ExpressionWarning v1alpha1 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>v1alpha1</CODE></TD><TD><CODE>ExpressionWarning</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ExpressionWarning is a warning information that targets a specific expression.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#typechecking-v1alpha1-admissionregistration-k8s-io">TypeChecking [admissionregistration/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>fieldRef</CODE><BR /><I>string</I></TD><TD>The path to the field that refers the expression. For example, the reference to the expression of the first item of validations is &#34;spec.validations[0].expression&#34;</TD></TR>
+<TR><TD><CODE>warning</CODE><BR /><I>string</I></TD><TD>The content of type checking information in a human-readable form. Each line of the warning contains the type that the expression is checked against, followed by the type check error from the compiler.</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-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-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>fsType is the 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>lun is Optional: FC target lun number</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>readOnly is 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>targetWWNs is Optional: FC target worldwide names (WWNs)</TD></TR>
+<TR><TD><CODE>wwids</CODE><BR /><I>string array</I></TD><TD>wwids 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="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>fsType is the 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>options is Optional: this field holds extra command options if any.</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>readOnly is 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>secretRef is 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>fsType is the 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>options is Optional: this field holds extra command options if any.</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>readOnly is 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>secretRef is 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>datasetName is 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>datasetUUID is the UUID of the dataset. This is unique identifier of a Flocker dataset</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="flowdistinguishermethod-v1beta3-flowcontrol-apiserver-k8s-io">FlowDistinguisherMethod v1beta3 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>v1beta3</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-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-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchemaSpec [flowcontrol/v1beta3]</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="flowschemacondition-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchemaCondition v1beta3 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>v1beta3</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-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-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchemaStatus [flowcontrol/v1beta3]</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-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>fsType is 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>partition is 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>pdName is 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>directory is the 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 is the URL</TD></TR>
+<TR><TD><CODE>revision</CODE><BR /><I>string</I></TD><TD>revision is the 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>endpoints 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>endpoints 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-v1beta3-flowcontrol-apiserver-k8s-io">GroupSubject v1beta3 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>v1beta3</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-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-v1beta3-flowcontrol-apiserver-k8s-io">Subject [flowcontrol/v1beta3]</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-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-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.</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>paths is a collection of paths that map requests to backends.</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-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-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="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.0/24&#34;,&#34;2001:db8::/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 IPBlock Valid examples are &#34;192.168.1.0/24&#34; or &#34;2001:db8::/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 IPBlock Valid examples are &#34;192.168.1.0/24&#34; or &#34;2001:db8::/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>chapAuthDiscovery defines whether support iSCSI Discovery CHAP authentication</TD></TR>
+<TR><TD><CODE>chapAuthSession</CODE><BR /><I>boolean</I></TD><TD>chapAuthSession defines whether support iSCSI Session CHAP authentication</TD></TR>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>fsType is the 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>initiatorName is the 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>iqn is Target iSCSI Qualified Name.</TD></TR>
+<TR><TD><CODE>iscsiInterface</CODE><BR /><I>string</I></TD><TD>iscsiInterface is the 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>lun is iSCSI Target Lun number.</TD></TR>
+<TR><TD><CODE>portals</CODE><BR /><I>string array</I></TD><TD>portals is the 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>secretRef is the CHAP Secret for iSCSI target and initiator authentication</TD></TR>
+<TR><TD><CODE>targetPortal</CODE><BR /><I>string</I></TD><TD>targetPortal is 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>chapAuthDiscovery defines whether support iSCSI Discovery CHAP authentication</TD></TR>
+<TR><TD><CODE>chapAuthSession</CODE><BR /><I>boolean</I></TD><TD>chapAuthSession defines whether support iSCSI Session CHAP authentication</TD></TR>
+<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>fsType is the 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>initiatorName is the 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>iqn is the target iSCSI Qualified Name.</TD></TR>
+<TR><TD><CODE>iscsiInterface</CODE><BR /><I>string</I></TD><TD>iscsiInterface is the 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>lun represents iSCSI Target Lun number.</TD></TR>
+<TR><TD><CODE>portals</CODE><BR /><I>string array</I></TD><TD>portals is the 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>secretRef is the CHAP Secret for iSCSI target and initiator authentication</TD></TR>
+<TR><TD><CODE>targetPortal</CODE><BR /><I>string</I></TD><TD>targetPortal is 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="ingressloadbalanceringress-v1-networking-k8s-io">IngressLoadBalancerIngress 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>IngressLoadBalancerIngress</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>IngressLoadBalancerIngress represents the status of a load-balancer ingress point.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#ingressloadbalancerstatus-v1-networking-k8s-io">IngressLoadBalancerStatus [networking/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.</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.</TD></TR>
+<TR><TD><CODE>ports</CODE><BR /><I><a href="#ingressportstatus-v1-networking-k8s-io">IngressPortStatus</a> array</I></TD><TD>ports provides information about the ports exposed by this LoadBalancer.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="ingressloadbalancerstatus-v1-networking-k8s-io">IngressLoadBalancerStatus 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>IngressLoadBalancerStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>IngressLoadBalancerStatus 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>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>ingress</CODE><BR /><I><a href="#ingressloadbalanceringress-v1-networking-k8s-io">IngressLoadBalancerIngress</a> array</I></TD><TD>ingress is a list containing ingress points for the load-balancer.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="ingressportstatus-v1-networking-k8s-io">IngressPortStatus 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>IngressPortStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>IngressPortStatus represents the error condition of a service port</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#ingressloadbalanceringress-v1-networking-k8s-io">IngressLoadBalancerIngress [networking/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 ingress port.</TD></TR>
+<TR><TD><CODE>protocol</CODE><BR /><I>string</I></TD><TD>protocol is the protocol of the ingress port. The supported values are: &#34;TCP&#34;, &#34;UDP&#34;, &#34;SCTP&#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 is 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 &#34;Host&#34; 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.</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-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>key is the key to project.</TD></TR>
+<TR><TD><CODE>mode</CODE><BR /><I>integer</I></TD><TD>mode is 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>path is 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-v1-storage-k8s-io">CSIStorageCapacity [storage/v1]</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="#jobspec-v1-batch">JobSpec [batch/v1]</a></LI>
+  <LI><a href="#matchresources-v1alpha1-admissionregistration-k8s-io">MatchResources [admissionregistration/v1alpha1]</a></LI>
+  <LI><a href="#metricidentifier-v2-autoscaling">MetricIdentifier [autoscaling/v2]</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="#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="#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.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="limitresponse-v1beta3-flowcontrol-apiserver-k8s-io">LimitResponse v1beta3 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>v1beta3</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-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-v1beta3-flowcontrol-apiserver-k8s-io">LimitedPriorityLevelConfiguration [flowcontrol/v1beta3]</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-v1beta3-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-v1beta3-flowcontrol-apiserver-k8s-io">LimitedPriorityLevelConfiguration v1beta3 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>v1beta3</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-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-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationSpec [flowcontrol/v1beta3]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>borrowingLimitPercent</CODE><BR /><I>integer</I></TD><TD>`borrowingLimitPercent`, if present, configures a limit on how many seats this priority level can borrow from other priority levels. The limit is known as this level&#39;s BorrowingConcurrencyLimit (BorrowingCL) and is a limit on the total number of seats that this level may borrow at any one time. This field holds the ratio of that limit to the level&#39;s nominal concurrency limit. When this field is non-nil, it must hold a non-negative integer and the limit is calculated as follows.  BorrowingCL(i) = round( NominalCL(i) * borrowingLimitPercent(i)/100.0 )  The value of this field can be more than 100, implying that this priority level can borrow a number of seats that is greater than its own nominal concurrency limit (NominalCL). When this field is left `nil`, the limit is effectively infinite.</TD></TR>
+<TR><TD><CODE>lendablePercent</CODE><BR /><I>integer</I></TD><TD>`lendablePercent` prescribes the fraction of the level&#39;s NominalCL that can be borrowed by other priority levels. The value of this field must be between 0 and 100, inclusive, and it defaults to 0. The number of seats that other levels can borrow from this level, known as this level&#39;s LendableConcurrencyLimit (LendableCL), is defined as follows.  LendableCL(i) = round( NominalCL(i) * lendablePercent(i)/100.0 )</TD></TR>
+<TR><TD><CODE>limitResponse</CODE><BR /><I><a href="#limitresponse-v1beta3-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>
+<TR><TD><CODE>nominalConcurrencyShares</CODE><BR /><I>integer</I></TD><TD>`nominalConcurrencyShares` (NCS) contributes to the computation of the NominalConcurrencyLimit (NominalCL) of this level. This is the number of execution seats available at this priority level. This is used both for requests dispatched from this priority level as well as requests dispatched from other priority levels borrowing seats from this level. The server&#39;s concurrency limit (ServerCL) is divided among the Limited priority levels in proportion to their NCS values:  NominalCL(i)  = ceil( ServerCL * NCS(i) / sum_ncs ) sum_ncs = sum[limited priority level k] NCS(k)  Bigger numbers mean a larger nominal concurrency limit, at the expense of every other Limited priority level. This field has a default value of 30.</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-v1-storage-k8s-io">CSIStorageCapacityList [storage/v1]</a></LI>
+  <LI><a href="#certificatesigningrequestlist-v1-certificates-k8s-io">CertificateSigningRequestList [certificates/v1]</a></LI>
+  <LI><a href="#clustercidrlist-v1alpha1-networking-k8s-io">ClusterCIDRList [networking/v1alpha1]</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="#clustertrustbundlelist-v1alpha1-certificates-k8s-io">ClusterTrustBundleList [certificates/v1alpha1]</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="#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="#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="#flowschemalist-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchemaList [flowcontrol/v1beta3]</a></LI>
+  <LI><a href="#flowschemalist-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchemaList [flowcontrol/v1beta2]</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="#ipaddresslist-v1alpha1-networking-k8s-io">IPAddressList [networking/v1alpha1]</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="#podlist-v1-core">PodList [core/v1]</a></LI>
+  <LI><a href="#podschedulingcontextlist-v1alpha2-resource-k8s-io">PodSchedulingContextList [resource/v1alpha2]</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-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationList [flowcontrol/v1beta3]</a></LI>
+  <LI><a href="#prioritylevelconfigurationlist-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationList [flowcontrol/v1beta2]</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="#resourceclaimlist-v1alpha2-resource-k8s-io">ResourceClaimList [resource/v1alpha2]</a></LI>
+  <LI><a href="#resourceclaimtemplatelist-v1alpha2-resource-k8s-io">ResourceClaimTemplateList [resource/v1alpha2]</a></LI>
+  <LI><a href="#resourceclasslist-v1alpha2-resource-k8s-io">ResourceClassList [resource/v1alpha2]</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="#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="#validatingadmissionpolicybindinglist-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingList [admissionregistration/v1alpha1]</a></LI>
+  <LI><a href="#validatingadmissionpolicylist-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyList [admissionregistration/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>Deprecated: selfLink is a legacy read-only field that is no longer populated by the system.</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="#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>fsType is the 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>path of 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 the timestamp of when the ManagedFields entry was added. The timestamp will also be updated if a field is added, the manager changes any of the owned fields value or removes a field. The timestamp does not update when a field is removed from the entry because another manager took it over.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="matchcondition-v1-admissionregistration-k8s-io">MatchCondition 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>MatchCondition</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>MatchCondition represents a condition which must by fulfilled for a request to be sent to a webhook.</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="#matchcondition-v1alpha1-admissionregistration-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="#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>expression</CODE><BR /><I>string</I></TD><TD>Expression represents the expression which will be evaluated by CEL. Must evaluate to bool. CEL expressions have access to the contents of the AdmissionRequest and Authorizer, organized into CEL variables:  &#39;object&#39; - The object from the incoming request. The value is null for DELETE requests. &#39;oldObject&#39; - The existing object. The value is null for CREATE requests. &#39;request&#39; - Attributes of the admission request(/pkg/apis/admission/types.go#AdmissionRequest). &#39;authorizer&#39; - A CEL Authorizer. May be used to perform authorization checks for the principal (user or service account) of the request.   See https://pkg.go.dev/k8s.io/apiserver/pkg/cel/library#Authz &#39;authorizer.requestResource&#39; - A CEL ResourceCheck constructed from the &#39;authorizer&#39; and configured with the   request resource. Documentation on CEL: https://kubernetes.io/docs/reference/using-api/cel/  Required.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is an identifier for this match condition, used for strategic merging of MatchConditions, as well as providing an identifier for logging purposes. A good name should be descriptive of the associated expression. Name must be a qualified name consisting of alphanumeric characters, &#39;-&#39;, &#39;_&#39; or &#39;.&#39;, and must start and end with an alphanumeric character (e.g. &#39;MyName&#39;,  or &#39;my.name&#39;,  or &#39;123-abc&#39;, regex used for validation is &#39;([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]&#39;) with an optional DNS subdomain prefix and &#39;/&#39; (e.g. &#39;example.com/MyName&#39;)  Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="matchresources-v1alpha1-admissionregistration-k8s-io">MatchResources v1alpha1 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>v1alpha1</CODE></TD><TD><CODE>MatchResources</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>MatchResources decides whether to run the admission control policy on an object based on whether it meets the match criteria. The exclude rules take precedence over include rules (if a resource matches both, it is excluded)</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#validatingadmissionpolicybindingspec-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingSpec [admissionregistration/v1alpha1]</a></LI>
+  <LI><a href="#validatingadmissionpolicyspec-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec [admissionregistration/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>excludeResourceRules</CODE><BR /><I><a href="#namedrulewithoperations-v1alpha1-admissionregistration-k8s-io">NamedRuleWithOperations</a> array</I></TD><TD>ExcludeResourceRules describes what operations on what resources/subresources the ValidatingAdmissionPolicy should not care about. The exclude rules take precedence over include rules (if a resource matches both, it is excluded)</TD></TR>
+<TR><TD><CODE>matchPolicy</CODE><BR /><I>string</I></TD><TD>matchPolicy defines how the &#34;MatchResources&#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 ValidatingAdmissionPolicy.  - 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 ValidatingAdmissionPolicy.  Defaults to &#34;Equivalent&#34;</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 admission control policy 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 policy.  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 policy 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 validation based on if the object has matching labels. objectSelector is evaluated against both the oldObject and newObject that would be sent to the cel validation, 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>resourceRules</CODE><BR /><I><a href="#namedrulewithoperations-v1alpha1-admissionregistration-k8s-io">NamedRuleWithOperations</a> array</I></TD><TD>ResourceRules describes what operations on what resources/subresources the ValidatingAdmissionPolicy matches. The policy cares about an operation if it matches _any_ Rule.</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-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-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-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-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-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="#eventseries-v1-core">EventSeries [core/v1]</a></LI>
+  <LI><a href="#eventseries-v1-events-k8s-io">EventSeries [events/v1]</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>matchConditions</CODE><BR /><I><a href="#matchcondition-v1-admissionregistration-k8s-io">MatchCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>MatchConditions is a list of conditions that must be met for a request to be sent to this webhook. Match conditions filter requests that have already been matched by the rules, namespaceSelector, and objectSelector. An empty list of matchConditions matches all requests. There are a maximum of 64 match conditions allowed.  The exact matching logic is (in order):   1. If ANY matchCondition evaluates to FALSE, the webhook is skipped.   2. If ALL matchConditions evaluate to TRUE, the webhook is called.   3. If any matchCondition evaluates to an error (but none are FALSE):      - If failurePolicy=Fail, reject the request      - If failurePolicy=Ignore, the error is ignored and the webhook is skipped  This is an alpha feature and managed by the AdmissionWebhookMatchConditions feature gate.</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="namedrulewithoperations-v1alpha1-admissionregistration-k8s-io">NamedRuleWithOperations v1alpha1 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>v1alpha1</CODE></TD><TD><CODE>NamedRuleWithOperations</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>NamedRuleWithOperations is a tuple of Operations and Resources with ResourceNames.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#matchresources-v1alpha1-admissionregistration-k8s-io">MatchResources [admissionregistration/v1alpha1]</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>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.  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="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.</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>ports is a 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>to is a 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>from is a 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>ports is a 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>namespaceSelector 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>podSelector 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>endPort indicates that the range of ports from port to endPort if set, 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.</TD></TR>
+<TR><TD><CODE>port</CODE></TD><TD>port represents 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>protocol represents 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.</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.</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="#allocationresult-v1alpha2-resource-k8s-io">AllocationResult [resource/v1alpha2]</a></LI>
+  <LI><a href="#clustercidrspec-v1alpha1-networking-k8s-io">ClusterCIDRSpec [networking/v1alpha1]</a></LI>
+  <LI><a href="#nodeaffinity-v1-core">NodeAffinity [core/v1]</a></LI>
+  <LI><a href="#resourceclass-v1alpha2-resource-k8s-io">ResourceClass [resource/v1alpha2]</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.</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. containerd://1.4.2).</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-v1beta3-flowcontrol-apiserver-k8s-io">NonResourcePolicyRule v1beta3 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>v1beta3</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-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-v1beta3-flowcontrol-apiserver-k8s-io">PolicyRulesWithSubjects [flowcontrol/v1beta3]</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-v1-storage-k8s-io">CSIStorageCapacity [storage/v1]</a></LI>
+  <LI><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest [certificates/v1]</a></LI>
+  <LI><a href="#clustercidr-v1alpha1-networking-k8s-io">ClusterCIDR [networking/v1alpha1]</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="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle [certificates/v1alpha1]</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="#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="#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="#eviction-v1-policy">Eviction [policy/v1]</a></LI>
+  <LI><a href="#flowschema-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchema [flowcontrol/v1beta3]</a></LI>
+  <LI><a href="#flowschema-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchema [flowcontrol/v1beta2]</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="#ipaddress-v1alpha1-networking-k8s-io">IPAddress [networking/v1alpha1]</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="#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="#podschedulingcontext-v1alpha2-resource-k8s-io">PodSchedulingContext [resource/v1alpha2]</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-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration [flowcontrol/v1beta3]</a></LI>
+  <LI><a href="#prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration [flowcontrol/v1beta2]</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="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim [resource/v1alpha2]</a></LI>
+  <LI><a href="#resourceclaimtemplate-v1alpha2-resource-k8s-io">ResourceClaimTemplate [resource/v1alpha2]</a></LI>
+  <LI><a href="#resourceclaimtemplatespec-v1alpha2-resource-k8s-io">ResourceClaimTemplateSpec [resource/v1alpha2]</a></LI>
+  <LI><a href="#resourceclass-v1alpha2-resource-k8s-io">ResourceClass [resource/v1alpha2]</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="#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="#selfsubjectreview-v1beta1-authentication-k8s-io">SelfSubjectReview [authentication/v1beta1]</a></LI>
+  <LI><a href="#selfsubjectreview-v1alpha1-authentication-k8s-io">SelfSubjectReview [authentication/v1alpha1]</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="#validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicy [admissionregistration/v1alpha1]</a></LI>
+  <LI><a href="#validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding [admissionregistration/v1alpha1]</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: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations</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 return a 409.  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: https://kubernetes.io/docs/concepts/overview/working-with-objects/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: 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 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: https://kubernetes.io/docs/concepts/overview/working-with-objects/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>Deprecated: selfLink is a legacy read-only field that is no longer populated by the system.</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: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#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-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-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="#endpoint-v1-discovery-k8s-io">Endpoint [discovery/v1]</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="#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-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. See https://kubernetes.io/docs/concepts/architecture/garbage-collection/#foreground-deletion for how the garbage collector interacts with this field and enforces the foreground deletion. 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: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#names</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="paramkind-v1alpha1-admissionregistration-k8s-io">ParamKind v1alpha1 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>v1alpha1</CODE></TD><TD><CODE>ParamKind</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ParamKind is a tuple of Group Kind and Version.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#validatingadmissionpolicyspec-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec [admissionregistration/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 is the API group version the resources belong to. In format of &#34;group/version&#34;. Required.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind is the API kind the resources belong to. Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="paramref-v1alpha1-admissionregistration-k8s-io">ParamRef v1alpha1 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>v1alpha1</CODE></TD><TD><CODE>ParamRef</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ParamRef references a parameter resource</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#validatingadmissionpolicybindingspec-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingSpec [admissionregistration/v1alpha1]</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 resource being referenced.</TD></TR>
+<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace of the referenced resource. Should be empty for the cluster-scoped resources</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="parentreference-v1alpha1-networking-k8s-io">ParentReference v1alpha1 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>v1alpha1</CODE></TD><TD><CODE>ParentReference</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ParentReference describes a reference to a parent object.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#ipaddressspec-v1alpha1-networking-k8s-io">IPAddressSpec [networking/v1alpha1]</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 group of the object being referenced.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of the object being referenced.</TD></TR>
+<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace is the namespace of the object being referenced.</TD></TR>
+<TR><TD><CODE>resource</CODE><BR /><I>string</I></TD><TD>Resource is the resource of the object being referenced.</TD></TR>
+<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>UID is the uid of the object being referenced.</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 contains 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>lastProbeTime is the time we probed the condition.</TD></TR>
+<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>lastTransitionTime is the time the condition transitioned from one status to another.</TD></TR>
+<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>message is the 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, 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></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>readOnly 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>fsType is the 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>pdID is the 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.</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</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="podfailurepolicy-v1-batch">PodFailurePolicy 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>PodFailurePolicy</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PodFailurePolicy describes how failed pods influence the backoffLimit.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#jobspec-v1-batch">JobSpec [batch/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>rules</CODE><BR /><I><a href="#podfailurepolicyrule-v1-batch">PodFailurePolicyRule</a> array</I></TD><TD>A list of pod failure policy rules. The rules are evaluated in order. Once a rule matches a Pod failure, the remaining of the rules are ignored. When no rule matches the Pod failure, the default handling applies - the counter of pod failures is incremented and it is checked against the backoffLimit. At most 20 elements are allowed.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="podfailurepolicyonexitcodesrequirement-v1-batch">PodFailurePolicyOnExitCodesRequirement 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>PodFailurePolicyOnExitCodesRequirement</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PodFailurePolicyOnExitCodesRequirement describes the requirement for handling a failed pod based on its container exit codes. In particular, it lookups the .state.terminated.exitCode for each app container and init container status, represented by the .status.containerStatuses and .status.initContainerStatuses fields in the Pod status, respectively. Containers completed with success (exit code 0) are excluded from the requirement check.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podfailurepolicyrule-v1-batch">PodFailurePolicyRule [batch/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>Restricts the check for exit codes to the container with the specified name. When null, the rule applies to all containers. When specified, it should match one the container or initContainer names in the pod template.</TD></TR>
+<TR><TD><CODE>operator</CODE><BR /><I>string</I></TD><TD>Represents the relationship between the container exit code(s) and the specified values. Containers completed with success (exit code 0) are excluded from the requirement check. Possible values are:  - In: the requirement is satisfied if at least one container exit code   (might be multiple if there are multiple containers not restricted   by the &#39;containerName&#39; field) is in the set of specified values. - NotIn: the requirement is satisfied if at least one container exit code   (might be multiple if there are multiple containers not restricted   by the &#39;containerName&#39; field) is not in the set of specified values. Additional values are considered to be added in the future. Clients should react to an unknown operator by assuming the requirement is not satisfied.</TD></TR>
+<TR><TD><CODE>values</CODE><BR /><I>integer array</I></TD><TD>Specifies the set of values. Each returned container exit code (might be multiple in case of multiple containers) is checked against this set of values with respect to the operator. The list of values must be ordered and must not contain duplicates. Value &#39;0&#39; cannot be used for the In operator. At least one element is required. At most 255 elements are allowed.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="podfailurepolicyonpodconditionspattern-v1-batch">PodFailurePolicyOnPodConditionsPattern 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>PodFailurePolicyOnPodConditionsPattern</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PodFailurePolicyOnPodConditionsPattern describes a pattern for matching an actual pod condition type.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podfailurepolicyrule-v1-batch">PodFailurePolicyRule [batch/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Specifies the required Pod condition status. To match a pod condition it is required that the specified status equals the pod condition status. Defaults to True.</TD></TR>
+<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Specifies the required Pod condition type. To match a pod condition it is required that specified type equals the pod condition type.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="podfailurepolicyrule-v1-batch">PodFailurePolicyRule 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>PodFailurePolicyRule</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PodFailurePolicyRule describes how a pod failure is handled when the requirements are met. One of onExitCodes and onPodConditions, but not both, can be used in each rule.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podfailurepolicy-v1-batch">PodFailurePolicy [batch/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>Specifies the action taken on a pod failure when the requirements are satisfied. Possible values are:  - FailJob: indicates that the pod&#39;s job is marked as Failed and all   running pods are terminated. - Ignore: indicates that the counter towards the .backoffLimit is not   incremented and a replacement pod is created. - Count: indicates that the pod is handled in the default way - the   counter towards the .backoffLimit is incremented. Additional values are considered to be added in the future. Clients should react to an unknown action by skipping the rule.</TD></TR>
+<TR><TD><CODE>onExitCodes</CODE><BR /><I><a href="#podfailurepolicyonexitcodesrequirement-v1-batch">PodFailurePolicyOnExitCodesRequirement</a></I></TD><TD>Represents the requirement on the container exit codes.</TD></TR>
+<TR><TD><CODE>onPodConditions</CODE><BR /><I><a href="#podfailurepolicyonpodconditionspattern-v1-batch">PodFailurePolicyOnPodConditionsPattern</a> array</I></TD><TD>Represents the requirement on the pod conditions. The requirement is represented as a list of pod condition patterns. The requirement is satisfied if at least one pattern matches an actual pod condition. At most 20 elements are allowed.</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.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="podresourceclaim-v1-core">PodResourceClaim 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>PodResourceClaim</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PodResourceClaim references exactly one ResourceClaim through a ClaimSource. It adds a name to it that uniquely identifies the ResourceClaim inside the Pod. Containers that need access to the ResourceClaim reference it with this name.</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 uniquely identifies this resource claim inside the pod. This must be a DNS_LABEL.</TD></TR>
+<TR><TD><CODE>source</CODE><BR /><I><a href="#claimsource-v1-core">ClaimSource</a></I></TD><TD>Source describes where to find the ResourceClaim.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="podschedulinggate-v1-core">PodSchedulingGate 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>PodSchedulingGate</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>PodSchedulingGate is associated to a Pod to guard its scheduling.</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 of the scheduling gate. Each scheduling gate must have a unique name field.</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, the fsGroup (if specified), and group memberships defined in the container image for the uid of the container process. If unspecified, no additional groups are added to any container. Note that group memberships defined in the container image for the uid of the container process are still effective, even if they are not included in this list. 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-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-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. &#34;&#34; represents the core API group and &#34;*&#34; represents all API groups.</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-v1beta3-flowcontrol-apiserver-k8s-io">PolicyRulesWithSubjects v1beta3 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>v1beta3</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-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-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchemaSpec [flowcontrol/v1beta3]</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-v1beta3-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-v1beta3-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-v1beta3-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;</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>readOnly 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="prioritylevelconfigurationcondition-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationCondition v1beta3 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>v1beta3</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-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-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationStatus [flowcontrol/v1beta3]</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-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationReference v1beta3 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>v1beta3</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-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-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchemaSpec [flowcontrol/v1beta3]</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.</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>defaultMode are the 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>sources is the 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:
+
+- No precision is lost - No fractional digits will be emitted - 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-v1-storage-k8s-io">CSIStorageCapacity [storage/v1]</a></LI>
+  <LI><a href="#emptydirvolumesource-v1-core">EmptyDirVolumeSource [core/v1]</a></LI>
+  <LI><a href="#metrictarget-v2-autoscaling">MetricTarget [autoscaling/v2]</a></LI>
+  <LI><a href="#metricvaluestatus-v2-autoscaling">MetricValueStatus [autoscaling/v2]</a></LI>
+  <LI><a href="#resourcefieldselector-v1-core">ResourceFieldSelector [core/v1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+</TBODY>
+</TABLE>
+<H2 id="queuingconfiguration-v1beta3-flowcontrol-apiserver-k8s-io">QueuingConfiguration v1beta3 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>v1beta3</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-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-v1beta3-flowcontrol-apiserver-k8s-io">LimitResponse [flowcontrol/v1beta3]</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>fsType is the 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>image is 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>monitors is 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>pool is 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>user is 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>fsType is the 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>image is 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>monitors is 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>pool is 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>user is 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="resourceclaim-v1-core">ResourceClaim 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>ResourceClaim</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ResourceClaim references one entry in PodSpec.ResourceClaims.</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="#resourceclaim-v1alpha2-resource-k8s-io">v1alpha2</a>
+</DIV>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#resourcerequirements-v1-core">ResourceRequirements [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 must match the name of one entry in pod.spec.resourceClaims of the Pod where this field is used. It makes that resource available inside a container.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="resourceclaimconsumerreference-v1alpha2-resource-k8s-io">ResourceClaimConsumerReference v1alpha2 resource.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>resource.k8s.io</CODE></TD><TD><CODE>v1alpha2</CODE></TD><TD><CODE>ResourceClaimConsumerReference</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ResourceClaimConsumerReference contains enough information to let you locate the consumer of a ResourceClaim. The user must be a resource in the same namespace as the ResourceClaim.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#resourceclaimstatus-v1alpha2-resource-k8s-io">ResourceClaimStatus [resource/v1alpha2]</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. It is empty for the core API. This matches the group in the APIVersion that is used when creating the resources.</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>resource</CODE><BR /><I>string</I></TD><TD>Resource is the type of resource being referenced, for example &#34;pods&#34;.</TD></TR>
+<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>UID identifies exactly one incarnation of the resource.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="resourceclaimparametersreference-v1alpha2-resource-k8s-io">ResourceClaimParametersReference v1alpha2 resource.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>resource.k8s.io</CODE></TD><TD><CODE>v1alpha2</CODE></TD><TD><CODE>ResourceClaimParametersReference</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ResourceClaimParametersReference contains enough information to let you locate the parameters for a ResourceClaim. The object must be in the same namespace as the ResourceClaim.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#resourceclaimspec-v1alpha2-resource-k8s-io">ResourceClaimSpec [resource/v1alpha2]</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. It is empty for the core API. This matches the group in the APIVersion that is used when creating the resources.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind is the type of resource being referenced. This is the same value as in the parameter object&#39;s metadata, for example &#34;ConfigMap&#34;.</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="resourceclaimschedulingstatus-v1alpha2-resource-k8s-io">ResourceClaimSchedulingStatus v1alpha2 resource.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>resource.k8s.io</CODE></TD><TD><CODE>v1alpha2</CODE></TD><TD><CODE>ResourceClaimSchedulingStatus</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ResourceClaimSchedulingStatus contains information about one particular ResourceClaim with &#34;WaitForFirstConsumer&#34; allocation mode.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#podschedulingcontextstatus-v1alpha2-resource-k8s-io">PodSchedulingContextStatus [resource/v1alpha2]</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 matches the pod.spec.resourceClaims[*].Name field.</TD></TR>
+<TR><TD><CODE>unsuitableNodes</CODE><BR /><I>string array</I></TD><TD>UnsuitableNodes lists nodes that the ResourceClaim cannot be allocated for.  The size of this field is limited to 128, the same as for PodSchedulingSpec.PotentialNodes. This may get increased in the future, but not reduced.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="resourceclassparametersreference-v1alpha2-resource-k8s-io">ResourceClassParametersReference v1alpha2 resource.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>resource.k8s.io</CODE></TD><TD><CODE>v1alpha2</CODE></TD><TD><CODE>ResourceClassParametersReference</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ResourceClassParametersReference contains enough information to let you locate the parameters for a ResourceClass.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#resourceclass-v1alpha2-resource-k8s-io">ResourceClass [resource/v1alpha2]</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. It is empty for the core API. This matches the group in the APIVersion that is used when creating the resources.</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind is the type of resource being referenced. This is the same value as in the parameter object&#39;s metadata.</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 that contains the referenced resource. Must be empty for cluster-scoped resources and non-empty for namespaced resources.</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="resourcehandle-v1alpha2-resource-k8s-io">ResourceHandle v1alpha2 resource.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>resource.k8s.io</CODE></TD><TD><CODE>v1alpha2</CODE></TD><TD><CODE>ResourceHandle</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>ResourceHandle holds opaque resource data for processing by a specific kubelet plugin.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#allocationresult-v1alpha2-resource-k8s-io">AllocationResult [resource/v1alpha2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>data</CODE><BR /><I>string</I></TD><TD>Data contains the opaque data associated with this ResourceHandle. It is set by the controller component of the resource driver whose name matches the DriverName set in the ResourceClaimStatus this ResourceHandle is embedded in. It is set at allocation time and is intended for processing by the kubelet plugin whose name matches the DriverName set in this ResourceHandle.  The maximum size of this field is 16KiB. This may get increased in the future, but not reduced.</TD></TR>
+<TR><TD><CODE>driverName</CODE><BR /><I>string</I></TD><TD>DriverName specifies the name of the resource driver whose kubelet plugin should be invoked to process this ResourceHandle&#39;s data once it lands on a node. This may differ from the DriverName set in ResourceClaimStatus this ResourceHandle is embedded in.</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-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-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-v1beta3-flowcontrol-apiserver-k8s-io">ResourcePolicyRule v1beta3 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>v1beta3</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-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-v1beta3-flowcontrol-apiserver-k8s-io">PolicyRulesWithSubjects [flowcontrol/v1beta3]</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="#containerstatus-v1-core">ContainerStatus [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>claims</CODE><BR /><I><a href="#resourceclaim-v1-core">ResourceClaim</a> array</I></TD><TD>Claims lists the names of resources, defined in spec.resourceClaims, that are used by this container.  This is an alpha field and requires enabling the DynamicResourceAllocation feature gate.  This field is immutable. It can only be set for containers.</TD></TR>
+<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. Requests cannot exceed Limits. 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>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 up. This can not be 0. Defaults to 1. This field is alpha-level and is only honored by servers that enable the MaxUnavailableStatefulSet feature. The field applies to all pods in the range 0 to Replicas-1. That means if there is any unavailable pod in the range 0 to Replicas-1, it will be counted towards MaxUnavailable.</TD></TR>
+<TR><TD><CODE>partition</CODE><BR /><I>integer</I></TD><TD>Partition indicates the ordinal at which the StatefulSet should be partitioned for updates. During a rolling update, all pods from ordinal Replicas-1 to Partition are updated. All pods from ordinal Partition-1 to 0 remain untouched. This is helpful in being able to do a canary based deployment. The 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="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="#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="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>spec 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>status is the 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>fsType is the 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>gateway is the host address of the ScaleIO API Gateway.</TD></TR>
+<TR><TD><CODE>protectionDomain</CODE><BR /><I>string</I></TD><TD>protectionDomain is the name of the ScaleIO Protection Domain for the configured storage.</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>readOnly 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>sslEnabled is the flag to enable/disable SSL communication with Gateway, default false</TD></TR>
+<TR><TD><CODE>storageMode</CODE><BR /><I>string</I></TD><TD>storageMode 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>storagePool is the ScaleIO Storage Pool associated with the protection domain.</TD></TR>
+<TR><TD><CODE>system</CODE><BR /><I>string</I></TD><TD>system is the name of the storage system as configured in ScaleIO.</TD></TR>
+<TR><TD><CODE>volumeName</CODE><BR /><I>string</I></TD><TD>volumeName is 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>fsType is the 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>gateway is the host address of the ScaleIO API Gateway.</TD></TR>
+<TR><TD><CODE>protectionDomain</CODE><BR /><I>string</I></TD><TD>protectionDomain is the name of the ScaleIO Protection Domain for the configured storage.</TD></TR>
+<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>readOnly 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>sslEnabled Flag enable/disable SSL communication with Gateway, default false</TD></TR>
+<TR><TD><CODE>storageMode</CODE><BR /><I>string</I></TD><TD>storageMode 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>storagePool is the ScaleIO Storage Pool associated with the protection domain.</TD></TR>
+<TR><TD><CODE>system</CODE><BR /><I>string</I></TD><TD>system is the name of the storage system as configured in ScaleIO.</TD></TR>
+<TR><TD><CODE>volumeName</CODE><BR /><I>string</I></TD><TD>volumeName is 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-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.</TD></TR>
+<TR><TD><CODE>scopeName</CODE><BR /><I>string</I></TD><TD>The name of the scope that the selector applies to.</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.</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>items 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>optional field 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>defaultMode is 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>items 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>optional field specify whether the Secret or its keys must be defined</TD></TR>
+<TR><TD><CODE>secretName</CODE><BR /><I>string</I></TD><TD>secretName is the 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-v1beta3-flowcontrol-apiserver-k8s-io">ServiceAccountSubject v1beta3 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>v1beta3</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-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-v1beta3-flowcontrol-apiserver-k8s-io">Subject [flowcontrol/v1beta3]</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 https://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.</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="statefulsetordinals-v1-apps">StatefulSetOrdinals 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>StatefulSetOrdinals</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>StatefulSetOrdinals describes the policy used for replica ordinal assignment in this StatefulSet.</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>start</CODE><BR /><I>integer</I></TD><TD>start is the number representing the first replica&#39;s index. It may be used to number replicas from an alternate index (eg: 1-indexed) over the default 0-indexed names, or to orchestrate progressive movement of replicas from one StatefulSet to another. If set, replica indices will be in the range:   [.spec.ordinals.start, .spec.ordinals.start + .spec.replicas). If unset, defaults to 0. Replica indices will be in the range:   [0, .spec.replicas).</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.</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: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#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>fsType is the 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>readOnly 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>fsType is the 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>readOnly 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-v1beta3-flowcontrol-apiserver-k8s-io">Subject v1beta3 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>v1beta3</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-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-v1beta3-flowcontrol-apiserver-k8s-io">PolicyRulesWithSubjects [flowcontrol/v1beta3]</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-v1beta3-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-v1beta3-flowcontrol-apiserver-k8s-io">ServiceAccountSubject</a></I></TD><TD>`serviceAccount` matches ServiceAccounts.</TD></TR>
+<TR><TD><CODE>user</CODE><BR /><I><a href="#usersubject-v1beta3-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="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.</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="#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="#flowschemacondition-v1beta3-flowcontrol-apiserver-k8s-io">FlowSchemaCondition [flowcontrol/v1beta3]</a></LI>
+  <LI><a href="#flowschemacondition-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchemaCondition [flowcontrol/v1beta2]</a></LI>
+  <LI><a href="#horizontalpodautoscalercondition-v2-autoscaling">HorizontalPodAutoscalerCondition [autoscaling/v2]</a></LI>
+  <LI><a href="#horizontalpodautoscalerstatus-v2-autoscaling">HorizontalPodAutoscalerStatus [autoscaling/v2]</a></LI>
+  <LI><a href="#horizontalpodautoscalerstatus-v1-autoscaling">HorizontalPodAutoscalerStatus [autoscaling/v1]</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-v1beta3-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationCondition [flowcontrol/v1beta3]</a></LI>
+  <LI><a href="#prioritylevelconfigurationcondition-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationCondition [flowcontrol/v1beta2]</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>
+ </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.</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.</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>matchLabelKeys</CODE><BR /><I>string array</I></TD><TD>MatchLabelKeys is a set of pod label keys to select the pods over which spreading will be calculated. The keys are used to lookup values from the incoming pod labels, those key-value labels are ANDed with labelSelector to select the group of existing pods over which spreading will be calculated for the incoming pod. The same key is forbidden to exist in both MatchLabelKeys and LabelSelector. MatchLabelKeys cannot be set when LabelSelector isn&#39;t set. Keys that don&#39;t exist in the incoming pod labels will be ignored. A null or empty list means only match against labelSelector.  This is a beta field and requires the MatchLabelKeysInPodTopologySpread feature gate to be enabled (enabled by default).</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. The global minimum is the minimum number of matching pods in an eligible domain or zero if the number of eligible domains is less than MinDomains. For example, in a 3-zone cluster, MaxSkew is set to 1, and pods with the same labelSelector spread as 2/2/1: In this case, the global minimum is 1. | zone1 | zone2 | zone3 | |  P P  |  P P  |   P   | - if MaxSkew is 1, incoming pod can only be scheduled to zone3 to become 2/2/2; scheduling it onto zone1(zone2) would make the ActualSkew(3-1) 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>minDomains</CODE><BR /><I>integer</I></TD><TD>MinDomains indicates a minimum number of eligible domains. When the number of eligible domains with matching topology keys is less than minDomains, Pod Topology Spread treats &#34;global minimum&#34; as 0, and then the calculation of Skew is performed. And when the number of eligible domains with matching topology keys equals or greater than minDomains, this value has no effect on scheduling. As a result, when the number of eligible domains is less than minDomains, scheduler won&#39;t schedule more than maxSkew Pods to those domains. If value is nil, the constraint behaves as if MinDomains is equal to 1. Valid values are integers greater than 0. When value is not nil, WhenUnsatisfiable must be DoNotSchedule.  For example, in a 3-zone cluster, MaxSkew is set to 2, MinDomains is set to 5 and pods with the same labelSelector spread as 2/2/2: | zone1 | zone2 | zone3 | |  P P  |  P P  |  P P  | The number of domains is less than 5(MinDomains), so &#34;global minimum&#34; is treated as 0. In this situation, new pod with the same labelSelector cannot be scheduled, because computed skew will be 3(3 - 0) if new Pod is scheduled to any of the three zones, it will violate MaxSkew.  This is a beta field and requires the MinDomainsInPodTopologySpread feature gate to be enabled (enabled by default).</TD></TR>
+<TR><TD><CODE>nodeAffinityPolicy</CODE><BR /><I>string</I></TD><TD>NodeAffinityPolicy indicates how we will treat Pod&#39;s nodeAffinity/nodeSelector when calculating pod topology spread skew. Options are: - Honor: only nodes matching nodeAffinity/nodeSelector are included in the calculations. - Ignore: nodeAffinity/nodeSelector are ignored. All nodes are included in the calculations.  If this value is nil, the behavior is equivalent to the Honor policy. This is a beta-level feature default enabled by the NodeInclusionPolicyInPodTopologySpread feature flag.</TD></TR>
+<TR><TD><CODE>nodeTaintsPolicy</CODE><BR /><I>string</I></TD><TD>NodeTaintsPolicy indicates how we will treat node taints when calculating pod topology spread skew. Options are: - Honor: nodes without taints, along with tainted nodes for which the incoming pod has a toleration, are included. - Ignore: node taints are ignored. All nodes are included.  If this value is nil, the behavior is equivalent to the Ignore policy. This is a beta-level feature default enabled by the NodeInclusionPolicyInPodTopologySpread feature flag.</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. We define a domain as a particular instance of a topology. Also, we define an eligible domain as a domain whose nodes meet the requirements of nodeAffinityPolicy and nodeTaintsPolicy. e.g. If TopologyKey is &#34;kubernetes.io/hostname&#34;, each Node is a domain of that topology. And, if TopologyKey is &#34;topology.kubernetes.io/zone&#34;, each zone is a domain of that topology. 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.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="typechecking-v1alpha1-admissionregistration-k8s-io">TypeChecking v1alpha1 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>v1alpha1</CODE></TD><TD><CODE>TypeChecking</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>TypeChecking contains results of type checking the expressions in the ValidatingAdmissionPolicy</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#validatingadmissionpolicystatus-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicyStatus [admissionregistration/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>expressionWarnings</CODE><BR /><I><a href="#expressionwarning-v1alpha1-admissionregistration-k8s-io">ExpressionWarning</a> array</I></TD><TD>The type checking warnings for each expression.</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="typedobjectreference-v1-core">TypedObjectReference 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>TypedObjectReference</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="#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>
+<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace is the namespace of resource being referenced Note that when a namespace is specified, a gateway.networking.k8s.io/ReferenceGrant object is required in the referent namespace to allow that namespace&#39;s owner to accept the reference. See the ReferenceGrant documentation for details. (Alpha) This field requires the CrossNamespaceVolumeDataSource feature gate to be enabled.</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="#selfsubjectreviewstatus-v1beta1-authentication-k8s-io">SelfSubjectReviewStatus [authentication/v1beta1]</a></LI>
+  <LI><a href="#selfsubjectreviewstatus-v1alpha1-authentication-k8s-io">SelfSubjectReviewStatus [authentication/v1alpha1]</a></LI>
+  <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-v1beta3-flowcontrol-apiserver-k8s-io">UserSubject v1beta3 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>v1beta3</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-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-v1beta3-flowcontrol-apiserver-k8s-io">Subject [flowcontrol/v1beta3]</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>matchConditions</CODE><BR /><I><a href="#matchcondition-v1-admissionregistration-k8s-io">MatchCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>MatchConditions is a list of conditions that must be met for a request to be sent to this webhook. Match conditions filter requests that have already been matched by the rules, namespaceSelector, and objectSelector. An empty list of matchConditions matches all requests. There are a maximum of 64 match conditions allowed.  The exact matching logic is (in order):   1. If ANY matchCondition evaluates to FALSE, the webhook is skipped.   2. If ALL matchConditions evaluate to TRUE, the webhook is called.   3. If any matchCondition evaluates to an error (but none are FALSE):      - If failurePolicy=Fail, reject the request      - If failurePolicy=Ignore, the error is ignored and the webhook is skipped  This is an alpha feature and managed by the AdmissionWebhookMatchConditions feature gate.</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="validation-v1alpha1-admissionregistration-k8s-io">Validation v1alpha1 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>v1alpha1</CODE></TD><TD><CODE>Validation</CODE></TD></TR>
+</TBODY>
+</TABLE>
+<P>Validation specifies the CEL expression which is used to apply the validation.</P>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#validatingadmissionpolicyspec-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec [admissionregistration/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>expression</CODE><BR /><I>string</I></TD><TD>Expression represents the expression which will be evaluated by CEL. ref: https://github.com/google/cel-spec CEL expressions have access to the contents of the API request/response, organized into CEL variables as well as some other useful variables:  - &#39;object&#39; - The object from the incoming request. The value is null for DELETE requests. - &#39;oldObject&#39; - The existing object. The value is null for CREATE requests. - &#39;request&#39; - Attributes of the API request([ref](/pkg/apis/admission/types.go#AdmissionRequest)). - &#39;params&#39; - Parameter resource referred to by the policy binding being evaluated. Only populated if the policy has a ParamKind. - &#39;authorizer&#39; - A CEL Authorizer. May be used to perform authorization checks for the principal (user or service account) of the request.   See https://pkg.go.dev/k8s.io/apiserver/pkg/cel/library#Authz - &#39;authorizer.requestResource&#39; - A CEL ResourceCheck constructed from the &#39;authorizer&#39; and configured with the   request resource.  The `apiVersion`, `kind`, `metadata.name` and `metadata.generateName` are always accessible from the root of the object. No other metadata properties are accessible.  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:   - Expression accessing a property named &#34;namespace&#34;: {&#34;Expression&#34;: &#34;object.__namespace__ &gt; 0&#34;}   - Expression accessing a property named &#34;x-prop&#34;: {&#34;Expression&#34;: &#34;object.x__dash__prop &gt; 0&#34;}   - Expression accessing a property named &#34;redact__d&#34;: {&#34;Expression&#34;: &#34;object.redact__underscores__d &gt; 0&#34;}  Equality on arrays with 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. Required.</TD></TR>
+<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 Expression 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; If the Expression contains line breaks. Message is required. The message must not contain line breaks. If unset, the message is &#34;failed Expression: {Expression}&#34;.</TD></TR>
+<TR><TD><CODE>messageExpression</CODE><BR /><I>string</I></TD><TD>messageExpression declares a CEL expression that evaluates to the validation failure message that is returned when this rule fails. Since messageExpression is used as a failure message, it must evaluate to a string. If both message and messageExpression are present on a validation, then messageExpression will be used if validation fails. If messageExpression results in a runtime error, the runtime error is logged, and the validation failure message is produced as if the messageExpression field were unset. If messageExpression evaluates to an empty string, a string with only spaces, or a string that contains line breaks, then the validation failure message will also be produced as if the messageExpression field were unset, and the fact that messageExpression produced an empty string/string with only spaces/string with line breaks will be logged. messageExpression has access to all the same variables as the `expression` except for &#39;authorizer&#39; and &#39;authorizer.requestResource&#39;. Example: &#34;object.x must be less than max (&#34;+string(params.max)+&#34;)&#34;</TD></TR>
+<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>Reason represents a machine-readable description of why this validation failed. If this is the first validation in the list to fail, this reason, as well as the corresponding HTTP response code, are used in the HTTP response to the client. The currently supported reasons are: &#34;Unauthorized&#34;, &#34;Forbidden&#34;, &#34;Invalid&#34;, &#34;RequestEntityTooLarge&#34;. If not set, StatusReasonInvalid is used in the response to the client.</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>messageExpression</CODE><BR /><I>string</I></TD><TD>MessageExpression declares a CEL expression that evaluates to the validation failure message that is returned when this rule fails. Since messageExpression is used as a failure message, it must evaluate to a string. If both message and messageExpression are present on a rule, then messageExpression will be used if validation fails. If messageExpression results in a runtime error, the runtime error is logged, and the validation failure message is produced as if the messageExpression field were unset. If messageExpression evaluates to an empty string, a string with only spaces, or a string that contains line breaks, then the validation failure message will also be produced as if the messageExpression field were unset, and the fact that messageExpression produced an empty string/string with only spaces/string with line breaks will be logged. messageExpression has access to all the same variables as the rule; the only difference is the return type. Example: &#34;x must be less than max (&#34;+string(self.max)+&#34;)&#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>persistentVolumeName represents the 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>message represents 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 represents the 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>count indicates the 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>configMap 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>downwardAPI 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>secret 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>serviceAccountToken is 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>fsType is 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>storagePolicyID is the storage Policy Based Management (SPBM) profile ID associated with the StoragePolicyName.</TD></TR>
+<TR><TD><CODE>storagePolicyName</CODE><BR /><I>string</I></TD><TD>storagePolicyName is the storage Policy Based Management (SPBM) profile name.</TD></TR>
+<TR><TD><CODE>volumePath</CODE><BR /><I>string</I></TD><TD>volumePath is the 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="crossversionobjectreference-v1-autoscaling">CrossVersionObjectReference 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>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-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-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>apiVersion is the API version of the referent</TD></TR>
+<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>kind is the 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 is the name of the referent; More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</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-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 is used as a hint for implementations to offer richer behavior for protocols that they understand. This field follows standard Kubernetes label syntax. Valid values are either:  * Un-prefixed protocol names - reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names).  * Kubernetes-defined prefixed names:   * &#39;kubernetes.io/h2c&#39; - HTTP/2 over cleartext as described in https://www.rfc-editor.org/rfc/rfc7540  * Other protocols should use implementation-defined prefixed names such as mycompany.com/my-custom-protocol.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name represents 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>port represents 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>protocol represents the IP protocol for this port. Must be UDP, TCP, or SCTP. Default is TCP.</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-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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-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="flowdistinguishermethod-v1beta2-flowcontrol-apiserver-k8s-io">FlowDistinguisherMethod v1beta2 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>v1beta2</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-v1beta3-flowcontrol-apiserver-k8s-io">v1beta3</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>
+<H1 id="flowschema-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchema v1beta2 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>v1beta2</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-v1beta3-flowcontrol-apiserver-k8s-io">v1beta3</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>
+<H3 id="flowschemaspec-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchemaSpec v1beta2 flowcontrol</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#flowschema-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchema [flowcontrol/v1beta2]</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-v1beta2-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-v1beta2-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-v1beta2-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-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchemaStatus v1beta2 flowcontrol</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#flowschema-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchema [flowcontrol/v1beta2]</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-v1beta2-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-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchemaList v1beta2 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-v1beta2-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-v1beta2-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-flowschema-v1beta2-flowcontrol-apiserver-k8s-io">Create</H2>
+<P>create a FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/flowcontrol.apiserver.k8s.io/v1beta2/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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-v1beta2-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-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#flowschema-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#flowschema-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-flowschema-v1beta2-flowcontrol-apiserver-k8s-io">Patch</H2>
+<P>partially update the specified FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/flowcontrol.apiserver.k8s.io/v1beta2/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#flowschema-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-flowschema-v1beta2-flowcontrol-apiserver-k8s-io">Replace</H2>
+<P>replace the specified FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/flowcontrol.apiserver.k8s.io/v1beta2/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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-v1beta2-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-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#flowschema-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-flowschema-v1beta2-flowcontrol-apiserver-k8s-io">Delete</H2>
+<P>delete a FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/flowcontrol.apiserver.k8s.io/v1beta2/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-v1beta2-flowcontrol-apiserver-k8s-io">Delete Collection</H2>
+<P>delete collection of FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/flowcontrol.apiserver.k8s.io/v1beta2/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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-v1beta2-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-flowschema-v1beta2-flowcontrol-apiserver-k8s-io">Read</H2>
+<P>read the specified FlowSchema</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta2/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-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-flowschema-v1beta2-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/v1beta2/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchemaList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-flowschema-v1beta2-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/v1beta2/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v1beta2-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/v1beta2/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v1beta2-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-flowschema-v1beta2-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/v1beta2/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#flowschema-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-flowschema-v1beta2-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/v1beta2/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-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-flowschema-v1beta2-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/v1beta2/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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-v1beta2-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-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#flowschema-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="flowschemacondition-v1beta2-flowcontrol-apiserver-k8s-io">FlowSchemaCondition v1beta2 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>v1beta2</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-v1beta3-flowcontrol-apiserver-k8s-io">v1beta3</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>
+<H1 id="groupsubject-v1beta2-flowcontrol-apiserver-k8s-io">GroupSubject v1beta2 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>v1beta2</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-v1beta3-flowcontrol-apiserver-k8s-io">v1beta3</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>
+<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>
+</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>spec defines the 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>status is the 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>maxReplicas is the 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>targetCPUUtilizationPercentage is the 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>currentCPUUtilizationPercentage is the 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>currentReplicas is the current number of replicas of pods managed by this 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.</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-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>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>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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="limitresponse-v1beta2-flowcontrol-apiserver-k8s-io">LimitResponse v1beta2 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>v1beta2</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-v1beta3-flowcontrol-apiserver-k8s-io">v1beta3</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>
+<H1 id="limitedprioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">LimitedPriorityLevelConfiguration v1beta2 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>v1beta2</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-v1beta3-flowcontrol-apiserver-k8s-io">v1beta3</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>borrowingLimitPercent</CODE><BR /><I>integer</I></TD><TD>`borrowingLimitPercent`, if present, configures a limit on how many seats this priority level can borrow from other priority levels. The limit is known as this level&#39;s BorrowingConcurrencyLimit (BorrowingCL) and is a limit on the total number of seats that this level may borrow at any one time. This field holds the ratio of that limit to the level&#39;s nominal concurrency limit. When this field is non-nil, it must hold a non-negative integer and the limit is calculated as follows.  BorrowingCL(i) = round( NominalCL(i) * borrowingLimitPercent(i)/100.0 )  The value of this field can be more than 100, implying that this priority level can borrow a number of seats that is greater than its own nominal concurrency limit (NominalCL). When this field is left `nil`, the limit is effectively infinite.</TD></TR>
+<TR><TD><CODE>lendablePercent</CODE><BR /><I>integer</I></TD><TD>`lendablePercent` prescribes the fraction of the level&#39;s NominalCL that can be borrowed by other priority levels. The value of this field must be between 0 and 100, inclusive, and it defaults to 0. The number of seats that other levels can borrow from this level, known as this level&#39;s LendableConcurrencyLimit (LendableCL), is defined as follows.  LendableCL(i) = round( NominalCL(i) * lendablePercent(i)/100.0 )</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>
+<H1 id="matchcondition-v1alpha1-admissionregistration-k8s-io">MatchCondition v1alpha1 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>v1alpha1</CODE></TD><TD><CODE>MatchCondition</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="#matchcondition-v1-admissionregistration-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="#validatingadmissionpolicyspec-v1alpha1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec [admissionregistration/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>expression</CODE><BR /><I>string</I></TD><TD>Expression represents the expression which will be evaluated by CEL. Must evaluate to bool. CEL expressions have access to the contents of the AdmissionRequest and Authorizer, organized into CEL variables:  &#39;object&#39; - The object from the incoming request. The value is null for DELETE requests. &#39;oldObject&#39; - The existing object. The value is null for CREATE requests. &#39;request&#39; - Attributes of the admission request(/pkg/apis/admission/types.go#AdmissionRequest). &#39;authorizer&#39; - A CEL Authorizer. May be used to perform authorization checks for the principal (user or service account) of the request.   See https://pkg.go.dev/k8s.io/apiserver/pkg/cel/library#Authz &#39;authorizer.requestResource&#39; - A CEL ResourceCheck constructed from the &#39;authorizer&#39; and configured with the   request resource. Documentation on CEL: https://kubernetes.io/docs/reference/using-api/cel/  Required.</TD></TR>
+<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is an identifier for this match condition, used for strategic merging of MatchConditions, as well as providing an identifier for logging purposes. A good name should be descriptive of the associated expression. Name must be a qualified name consisting of alphanumeric characters, &#39;-&#39;, &#39;_&#39; or &#39;.&#39;, and must start and end with an alphanumeric character (e.g. &#39;MyName&#39;,  or &#39;my.name&#39;,  or &#39;123-abc&#39;, regex used for validation is &#39;([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]&#39;) with an optional DNS subdomain prefix and &#39;/&#39; (e.g. &#39;example.com/MyName&#39;)  Required.</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="nonresourcepolicyrule-v1beta2-flowcontrol-apiserver-k8s-io">NonResourcePolicyRule v1beta2 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>v1beta2</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-v1beta3-flowcontrol-apiserver-k8s-io">v1beta3</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>
+<H1 id="policyruleswithsubjects-v1beta2-flowcontrol-apiserver-k8s-io">PolicyRulesWithSubjects v1beta2 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>v1beta2</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-v1beta3-flowcontrol-apiserver-k8s-io">v1beta3</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>
+<H1 id="prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration v1beta2 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>v1beta2</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-v1beta3-flowcontrol-apiserver-k8s-io">v1beta3</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>
+<H3 id="prioritylevelconfigurationspec-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationSpec v1beta2 flowcontrol</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration [flowcontrol/v1beta2]</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-v1beta2-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-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationStatus v1beta2 flowcontrol</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration [flowcontrol/v1beta2]</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-v1beta2-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-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationList v1beta2 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-v1beta2-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-v1beta2-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">Create</H2>
+<P>create a PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/flowcontrol.apiserver.k8s.io/v1beta2/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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-v1beta2-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-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">Patch</H2>
+<P>partially update the specified PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/flowcontrol.apiserver.k8s.io/v1beta2/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">Replace</H2>
+<P>replace the specified PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/flowcontrol.apiserver.k8s.io/v1beta2/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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-v1beta2-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-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">Delete</H2>
+<P>delete a PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/flowcontrol.apiserver.k8s.io/v1beta2/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-v1beta2-flowcontrol-apiserver-k8s-io">Delete Collection</H2>
+<P>delete collection of PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/flowcontrol.apiserver.k8s.io/v1beta2/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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-v1beta2-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">Read</H2>
+<P>read the specified PriorityLevelConfiguration</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1beta2/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-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-prioritylevelconfiguration-v1beta2-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/v1beta2/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-prioritylevelconfiguration-v1beta2-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/v1beta2/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v1beta2-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/v1beta2/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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-v1beta2-flowcontrol-apiserver-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-prioritylevelconfiguration-v1beta2-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/v1beta2/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-prioritylevelconfiguration-v1beta2-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/v1beta2/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-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-prioritylevelconfiguration-v1beta2-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/v1beta2/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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>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-v1beta2-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-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="prioritylevelconfigurationcondition-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationCondition v1beta2 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>v1beta2</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-v1beta3-flowcontrol-apiserver-k8s-io">v1beta3</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>
+<H1 id="prioritylevelconfigurationreference-v1beta2-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationReference v1beta2 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>v1beta2</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-v1beta3-flowcontrol-apiserver-k8s-io">v1beta3</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>
+<H1 id="queuingconfiguration-v1beta2-flowcontrol-apiserver-k8s-io">QueuingConfiguration v1beta2 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>v1beta2</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-v1beta3-flowcontrol-apiserver-k8s-io">v1beta3</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>
+<H1 id="resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim v1alpha2 resource.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>resource.k8s.io</CODE></TD><TD><CODE>v1alpha2</CODE></TD><TD><CODE>ResourceClaim</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="#resourceclaim-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="#resourceclaimlist-v1alpha2-resource-k8s-io">ResourceClaimList [resource/v1alpha2]</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</TD></TR>
+<TR><TD><CODE>spec</CODE><BR /><I><a href="#resourceclaimspec-v1alpha2-resource-k8s-io">ResourceClaimSpec</a></I></TD><TD>Spec describes the desired attributes of a resource that then needs to be allocated. It can only be set once when creating the ResourceClaim.</TD></TR>
+<TR><TD><CODE>status</CODE><BR /><I><a href="#resourceclaimstatus-v1alpha2-resource-k8s-io">ResourceClaimStatus</a></I></TD><TD>Status describes whether the resource is available and with which attributes.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="resourceclaimspec-v1alpha2-resource-k8s-io">ResourceClaimSpec v1alpha2 resource</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim [resource/v1alpha2]</a></LI>
+  <LI><a href="#resourceclaimtemplatespec-v1alpha2-resource-k8s-io">ResourceClaimTemplateSpec [resource/v1alpha2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allocationMode</CODE><BR /><I>string</I></TD><TD>Allocation can start immediately or when a Pod wants to use the resource. &#34;WaitForFirstConsumer&#34; is the default.</TD></TR>
+<TR><TD><CODE>parametersRef</CODE><BR /><I><a href="#resourceclaimparametersreference-v1alpha2-resource-k8s-io">ResourceClaimParametersReference</a></I></TD><TD>ParametersRef references a separate object with arbitrary parameters that will be used by the driver when allocating a resource for the claim.  The object must be in the same namespace as the ResourceClaim.</TD></TR>
+<TR><TD><CODE>resourceClassName</CODE><BR /><I>string</I></TD><TD>ResourceClassName references the driver and additional parameters via the name of a ResourceClass that was created as part of the driver deployment.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="resourceclaimstatus-v1alpha2-resource-k8s-io">ResourceClaimStatus v1alpha2 resource</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim [resource/v1alpha2]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>allocation</CODE><BR /><I><a href="#allocationresult-v1alpha2-resource-k8s-io">AllocationResult</a></I></TD><TD>Allocation is set by the resource driver once a resource or set of resources has been allocated successfully. If this is not specified, the resources have not been allocated yet.</TD></TR>
+<TR><TD><CODE>deallocationRequested</CODE><BR /><I>boolean</I></TD><TD>DeallocationRequested indicates that a ResourceClaim is to be deallocated.  The driver then must deallocate this claim and reset the field together with clearing the Allocation field.  While DeallocationRequested is set, no new consumers may be added to ReservedFor.</TD></TR>
+<TR><TD><CODE>driverName</CODE><BR /><I>string</I></TD><TD>DriverName is a copy of the driver name from the ResourceClass at the time when allocation started.</TD></TR>
+<TR><TD><CODE>reservedFor</CODE><BR /><I><a href="#resourceclaimconsumerreference-v1alpha2-resource-k8s-io">ResourceClaimConsumerReference</a> array</I></TD><TD>ReservedFor indicates which entities are currently allowed to use the claim. A Pod which references a ResourceClaim which is not reserved for that Pod will not be started.  There can be at most 32 such reservations. This may get increased in the future, but not reduced.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="resourceclaimlist-v1alpha2-resource-k8s-io">ResourceClaimList v1alpha2 resource</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="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a> array</I></TD><TD>Items is the list of resource claims.</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-resourceclaim-v1alpha2-resource-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-resourceclaim-v1alpha2-resource-k8s-io">Create</H2>
+<P>create a ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="patch-resourceclaim-v1alpha2-resource-k8s-io">Patch</H2>
+<P>partially update the specified ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-resourceclaim-v1alpha2-resource-k8s-io">Replace</H2>
+<P>replace the specified ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-resourceclaim-v1alpha2-resource-k8s-io">Delete</H2>
+<P>delete a ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error 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="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
+<TR><TD>202<br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="delete-collection-resourceclaim-v1alpha2-resource-k8s-io">Delete Collection</H2>
+<P>delete collection of ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>DELETE /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</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-resourceclaim-v1alpha2-resource-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
+<H2 id="read-resourceclaim-v1alpha2-resource-k8s-io">Read</H2>
+<P>read the specified ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</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="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-resourceclaim-v1alpha2-resource-k8s-io">List</H2>
+<P>list or watch objects of kind ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourceclaimlist-v1alpha2-resource-k8s-io">ResourceClaimList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="list-all-namespaces-resourceclaim-v1alpha2-resource-k8s-io">List All Namespaces</H2>
+<P>list or watch objects of kind ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/resourceclaims</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourceclaimlist-v1alpha2-resource-k8s-io">ResourceClaimList</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="watch-resourceclaim-v1alpha2-resource-k8s-io">Watch</H2>
+<P>watch changes to an object of kind ResourceClaim. 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/resource.k8s.io/v1alpha2/watch/namespaces/{namespace}/resourceclaims/{name}</CODE>
+<H3>Path Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and 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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-resourceclaim-v1alpha2-resource-k8s-io">Watch List</H2>
+<P>watch individual changes to a list of ResourceClaim. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/watch/namespaces/{namespace}/resourceclaims</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-resourceclaim-v1alpha2-resource-k8s-io">Watch List All Namespaces</H2>
+<P>watch individual changes to a list of ResourceClaim. deprecated: use the 'watch' parameter with a list operation instead.</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/watch/resourceclaims</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>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event  will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.  When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan   is interpreted as "data at least as new as the provided `resourceVersion`"   and the bookmark event is send when the state is synced   to a `resourceVersion` at least as fresh as the one provided by the ListOptions.   If `resourceVersion` is unset, this is interpreted as "consistent read" and the   bookmark event is send when the state is synced at least to the moment   when request started being processed. - `resourceVersionMatch` set to any other value or unset   Invalid error is returned.  Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
+<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
+<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
+</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-resourceclaim-v1alpha2-resource-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
+<H2 id="patch-status-resourceclaim-v1alpha2-resource-k8s-io">Patch Status</H2>
+<P>partially update status of the specified ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>PATCH /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{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 ResourceClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="read-status-resourceclaim-v1alpha2-resource-k8s-io">Read Status</H2>
+<P>read status of the specified ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>GET /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{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 ResourceClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</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="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="replace-status-resourceclaim-v1alpha2-resource-k8s-io">Replace Status</H2>
+<P>replace status of the specified ResourceClaim</P>
+<H3>HTTP Request</H3>
+<CODE>PUT /apis/resource.k8s.io/v1alpha2/namespaces/{namespace}/resourceclaims/{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 ResourceClaim</TD></TR>
+<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Query Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
+<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
+<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. 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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
+</TBODY>
+</TABLE>
+<H3>Body Parameters</H3>
+<TABLE>
+<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#resourceclaim-v1alpha2-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="resourcepolicyrule-v1beta2-flowcontrol-apiserver-k8s-io">ResourcePolicyRule v1beta2 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>v1beta2</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-v1beta3-flowcontrol-apiserver-k8s-io">v1beta3</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>
+<H1 id="selfsubjectreview-v1alpha1-authentication-k8s-io">SelfSubjectReview v1alpha1 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>v1alpha1</CODE></TD><TD><CODE>SelfSubjectReview</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="#selfsubjectreview-v1beta1-authentication-k8s-io">v1beta1</a>
+</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>status</CODE><BR /><I><a href="#selfsubjectreviewstatus-v1alpha1-authentication-k8s-io">SelfSubjectReviewStatus</a></I></TD><TD>Status is filled in by the server with the user attributes.</TD></TR>
+</TBODY>
+</TABLE>
+<H3 id="selfsubjectreviewstatus-v1alpha1-authentication-k8s-io">SelfSubjectReviewStatus v1alpha1 authentication</H3>
+<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
+ <UL>
+  <LI><a href="#selfsubjectreview-v1alpha1-authentication-k8s-io">SelfSubjectReview [authentication/v1alpha1]</a></LI>
+ </UL>
+</DIV>
+<TABLE>
+<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD><CODE>userInfo</CODE><BR /><I><a href="#userinfo-v1-authentication-k8s-io">UserInfo</a></I></TD><TD>User attributes of the user making this request.</TD></TR>
+</TBODY>
+</TABLE>
+<H2 id="-strong-write-operations-selfsubjectreview-v1alpha1-authentication-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
+<H2 id="create-selfsubjectreview-v1alpha1-authentication-k8s-io">Create</H2>
+<P>create a SelfSubjectReview</P>
+<H3>HTTP Request</H3>
+<CODE>POST /apis/authentication.k8s.io/v1alpha1/selfsubjectreviews</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 instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</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="#selfsubjectreview-v1alpha1-authentication-k8s-io">SelfSubjectReview</a></I></TD><TD></TD></TR>
+</TBODY>
+</TABLE>
+<H3>Response</H3>
+<TABLE>
+<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
+<TBODY>
+<TR><TD>200<br /><I><a href="#selfsubjectreview-v1alpha1-authentication-k8s-io">SelfSubjectReview</a></I></TD><TD>OK</TD></TR>
+<TR><TD>201<br /><I><a href="#selfsubjectreview-v1alpha1-authentication-k8s-io">SelfSubjectReview</a></I></TD><TD>Created</TD></TR>
+<TR><TD>202<br /><I><a href="#selfsubjectreview-v1alpha1-authentication-k8s-io">SelfSubjectReview</a></I></TD><TD>Accepted</TD></TR>
+</TBODY>
+</TABLE>
+<H1 id="serviceaccountsubject-v1beta2-flowcontrol-apiserver-k8s-io">ServiceAccountSubject v1beta2 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>v1beta2</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-v1beta3-flowcontrol-apiserver-k8s-io">v1beta3</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>
+<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-v1beta3-flowcontrol-apiserver-k8s-io">v1beta3</a>
+<a href="#subject-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="#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-v1beta2-flowcontrol-apiserver-k8s-io">Subject v1beta2 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>v1beta2</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-v1beta3-flowcontrol-apiserver-k8s-io">v1beta3</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>
+<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-v1beta2-flowcontrol-apiserver-k8s-io">UserSubject v1beta2 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>v1beta2</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-v1beta3-flowcontrol-apiserver-k8s-io">v1beta3</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>
+<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.6.0.min.js"></SCRIPT>
+<SCRIPT src="/js/jquery.scrollTo-2.1.3.min.js"></SCRIPT>
+<SCRIPT src="/js/bootstrap-4.6.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.27/js/navData.js b/static/docs/reference/generated/kubernetes-api/v1.27/js/navData.js
new file mode 100644
index 00000000000..da9e235fb18
--- /dev/null
+++ b/static/docs/reference/generated/kubernetes-api/v1.27/js/navData.js
@@ -0,0 +1 @@
+(function(){navData={"toc":[{"section":"webhookclientconfig-v1-apiextensions-k8s-io","subsections":[]},{"section":"usersubject-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"tokenrequest-v1-storage-k8s-io","subsections":[]},{"section":"subject-v1beta2-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-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"selfsubjectreview-v1alpha1-authentication-k8s-io","subsections":[{"section":"-strong-write-operations-selfsubjectreview-v1alpha1-authentication-k8s-io-strong-","subsections":[{"section":"create-selfsubjectreview-v1alpha1-authentication-k8s-io","subsections":[]}]}]},{"section":"resourcepolicyrule-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"resourceclaim-v1alpha2-resource-k8s-io","subsections":[{"section":"-strong-status-operations-resourceclaim-v1alpha2-resource-k8s-io-strong-","subsections":[{"section":"replace-status-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"read-status-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"patch-status-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]}]},{"section":"-strong-read-operations-resourceclaim-v1alpha2-resource-k8s-io-strong-","subsections":[{"section":"watch-list-all-namespaces-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"watch-list-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"watch-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"list-all-namespaces-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"list-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"read-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-resourceclaim-v1alpha2-resource-k8s-io-strong-","subsections":[{"section":"delete-collection-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"delete-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"replace-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"patch-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"create-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]}]}]},{"section":"queuingconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","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":"-strong-status-operations-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"replace-status-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"read-status-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"patch-status-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]}]},{"section":"-strong-read-operations-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"watch-list-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"watch-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"list-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"read-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"delete-collection-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"delete-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"replace-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"patch-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"create-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]}]}]},{"section":"policyruleswithsubjects-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"nonresourcepolicyrule-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"matchcondition-v1alpha1-admissionregistration-k8s-io","subsections":[]},{"section":"limitedprioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"limitresponse-v1beta2-flowcontrol-apiserver-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":"groupsubject-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"flowschemacondition-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"flowschema-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[{"section":"-strong-status-operations-flowschema-v1beta2-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"replace-status-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"read-status-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"patch-status-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]}]},{"section":"-strong-read-operations-flowschema-v1beta2-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"watch-list-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"watch-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"list-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"read-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-flowschema-v1beta2-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"delete-collection-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"delete-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"replace-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"patch-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"create-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]}]}]},{"section":"flowdistinguishermethod-v1beta2-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"eventseries-v1-core","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":"endpointport-v1-discovery-k8s-io","subsections":[]},{"section":"crossversionobjectreference-v1-autoscaling","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":"validation-v1alpha1-admissionregistration-k8s-io","subsections":[]},{"section":"validatingwebhook-v1-admissionregistration-k8s-io","subsections":[]},{"section":"usersubject-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"userinfo-v1-authentication-k8s-io","subsections":[]},{"section":"uncountedterminatedpods-v1-batch","subsections":[]},{"section":"typedobjectreference-v1-core","subsections":[]},{"section":"typedlocalobjectreference-v1-core","subsections":[]},{"section":"typechecking-v1alpha1-admissionregistration-k8s-io","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":"subjectrulesreviewstatus-v1-authorization-k8s-io","subsections":[]},{"section":"subject-v1beta3-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":"statefulsetordinals-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-v1beta3-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":"selinuxoptions-v1-core","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-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"resourcemetricstatus-v2-autoscaling","subsections":[]},{"section":"resourcemetricsource-v2-autoscaling","subsections":[]},{"section":"resourcehandle-v1alpha2-resource-k8s-io","subsections":[]},{"section":"resourcefieldselector-v1-core","subsections":[]},{"section":"resourceclassparametersreference-v1alpha2-resource-k8s-io","subsections":[]},{"section":"resourceclaimschedulingstatus-v1alpha2-resource-k8s-io","subsections":[]},{"section":"resourceclaimparametersreference-v1alpha2-resource-k8s-io","subsections":[]},{"section":"resourceclaimconsumerreference-v1alpha2-resource-k8s-io","subsections":[]},{"section":"resourceclaim-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-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"quantity-resource-core","subsections":[]},{"section":"projectedvolumesource-v1-core","subsections":[]},{"section":"probe-v1-core","subsections":[]},{"section":"prioritylevelconfigurationreference-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"prioritylevelconfigurationcondition-v1beta3-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-v1beta3-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":"podschedulinggate-v1-core","subsections":[]},{"section":"podresourceclaim-v1-core","subsections":[]},{"section":"podreadinessgate-v1-core","subsections":[]},{"section":"podos-v1-core","subsections":[]},{"section":"podip-v1-core","subsections":[]},{"section":"podfailurepolicyrule-v1-batch","subsections":[]},{"section":"podfailurepolicyonpodconditionspattern-v1-batch","subsections":[]},{"section":"podfailurepolicyonexitcodesrequirement-v1-batch","subsections":[]},{"section":"podfailurepolicy-v1-batch","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":"parentreference-v1alpha1-networking-k8s-io","subsections":[]},{"section":"paramref-v1alpha1-admissionregistration-k8s-io","subsections":[]},{"section":"paramkind-v1alpha1-admissionregistration-k8s-io","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-v1beta3-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":"namedrulewithoperations-v1alpha1-admissionregistration-k8s-io","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":"matchresources-v1alpha1-admissionregistration-k8s-io","subsections":[]},{"section":"matchcondition-v1-admissionregistration-k8s-io","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-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"limitresponse-v1beta3-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":"ingressportstatus-v1-networking-k8s-io","subsections":[]},{"section":"ingressloadbalancerstatus-v1-networking-k8s-io","subsections":[]},{"section":"ingressloadbalanceringress-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":"hostpathvolumesource-v1-core","subsections":[]},{"section":"hostalias-v1-core","subsections":[]},{"section":"horizontalpodautoscalercondition-v2-autoscaling","subsections":[]},{"section":"horizontalpodautoscalerbehavior-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-v1beta3-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-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"flowdistinguishermethod-v1beta3-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":"fcvolumesource-v1-core","subsections":[]},{"section":"externalmetricstatus-v2-autoscaling","subsections":[]},{"section":"externalmetricsource-v2-autoscaling","subsections":[]},{"section":"externaldocumentation-v1-apiextensions-k8s-io","subsections":[]},{"section":"expressionwarning-v1alpha1-admissionregistration-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-v2-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":"containerresizepolicy-v1-core","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":"claimsource-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":"auditannotation-v1alpha1-admissionregistration-k8s-io","subsections":[]},{"section":"attachedvolume-v1-core","subsections":[]},{"section":"allocationresult-v1alpha2-resource-k8s-io","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-status-operations-networkpolicy-v1-networking-k8s-io-strong-","subsections":[{"section":"replace-status-networkpolicy-v1-networking-k8s-io","subsections":[]},{"section":"read-status-networkpolicy-v1-networking-k8s-io","subsections":[]},{"section":"patch-status-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":"selfsubjectreview-v1beta1-authentication-k8s-io","subsections":[{"section":"-strong-write-operations-selfsubjectreview-v1beta1-authentication-k8s-io-strong-","subsections":[{"section":"create-selfsubjectreview-v1beta1-authentication-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-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[{"section":"-strong-status-operations-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"replace-status-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"read-status-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"patch-status-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]}]},{"section":"-strong-read-operations-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"watch-list-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"watch-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"list-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"read-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"delete-collection-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"delete-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"replace-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"patch-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"create-prioritylevelconfiguration-v1beta3-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":"ipaddress-v1alpha1-networking-k8s-io","subsections":[{"section":"-strong-read-operations-ipaddress-v1alpha1-networking-k8s-io-strong-","subsections":[{"section":"watch-list-ipaddress-v1alpha1-networking-k8s-io","subsections":[]},{"section":"watch-ipaddress-v1alpha1-networking-k8s-io","subsections":[]},{"section":"list-ipaddress-v1alpha1-networking-k8s-io","subsections":[]},{"section":"read-ipaddress-v1alpha1-networking-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-ipaddress-v1alpha1-networking-k8s-io-strong-","subsections":[{"section":"delete-collection-ipaddress-v1alpha1-networking-k8s-io","subsections":[]},{"section":"delete-ipaddress-v1alpha1-networking-k8s-io","subsections":[]},{"section":"replace-ipaddress-v1alpha1-networking-k8s-io","subsections":[]},{"section":"patch-ipaddress-v1alpha1-networking-k8s-io","subsections":[]},{"section":"create-ipaddress-v1alpha1-networking-k8s-io","subsections":[]}]}]},{"section":"flowschema-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[{"section":"-strong-status-operations-flowschema-v1beta3-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"replace-status-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"read-status-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"patch-status-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]}]},{"section":"-strong-read-operations-flowschema-v1beta3-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"watch-list-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"watch-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"list-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"read-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-flowschema-v1beta3-flowcontrol-apiserver-k8s-io-strong-","subsections":[{"section":"delete-collection-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"delete-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"replace-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"patch-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","subsections":[]},{"section":"create-flowschema-v1beta3-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":"validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io","subsections":[{"section":"-strong-read-operations-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io-strong-","subsections":[{"section":"watch-list-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io","subsections":[]},{"section":"watch-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io","subsections":[]},{"section":"list-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io","subsections":[]},{"section":"read-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io-strong-","subsections":[{"section":"delete-collection-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io","subsections":[]},{"section":"delete-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io","subsections":[]},{"section":"replace-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io","subsections":[]},{"section":"patch-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io","subsections":[]},{"section":"create-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io","subsections":[]}]}]},{"section":"validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","subsections":[{"section":"-strong-status-operations-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io-strong-","subsections":[{"section":"replace-status-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","subsections":[]},{"section":"read-status-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","subsections":[]},{"section":"patch-status-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","subsections":[]}]},{"section":"-strong-read-operations-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io-strong-","subsections":[{"section":"watch-list-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","subsections":[]},{"section":"watch-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","subsections":[]},{"section":"list-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","subsections":[]},{"section":"read-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io-strong-","subsections":[{"section":"delete-collection-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","subsections":[]},{"section":"delete-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","subsections":[]},{"section":"replace-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","subsections":[]},{"section":"patch-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","subsections":[]},{"section":"create-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","subsections":[]}]}]},{"section":"resourceclass-v1alpha2-resource-k8s-io","subsections":[{"section":"-strong-read-operations-resourceclass-v1alpha2-resource-k8s-io-strong-","subsections":[{"section":"watch-list-resourceclass-v1alpha2-resource-k8s-io","subsections":[]},{"section":"watch-resourceclass-v1alpha2-resource-k8s-io","subsections":[]},{"section":"list-resourceclass-v1alpha2-resource-k8s-io","subsections":[]},{"section":"read-resourceclass-v1alpha2-resource-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-resourceclass-v1alpha2-resource-k8s-io-strong-","subsections":[{"section":"delete-collection-resourceclass-v1alpha2-resource-k8s-io","subsections":[]},{"section":"delete-resourceclass-v1alpha2-resource-k8s-io","subsections":[]},{"section":"replace-resourceclass-v1alpha2-resource-k8s-io","subsections":[]},{"section":"patch-resourceclass-v1alpha2-resource-k8s-io","subsections":[]},{"section":"create-resourceclass-v1alpha2-resource-k8s-io","subsections":[]}]}]},{"section":"resourceclaimtemplate-v1alpha2-resource-k8s-io","subsections":[{"section":"-strong-read-operations-resourceclaimtemplate-v1alpha2-resource-k8s-io-strong-","subsections":[{"section":"watch-list-all-namespaces-resourceclaimtemplate-v1alpha2-resource-k8s-io","subsections":[]},{"section":"watch-list-resourceclaimtemplate-v1alpha2-resource-k8s-io","subsections":[]},{"section":"watch-resourceclaimtemplate-v1alpha2-resource-k8s-io","subsections":[]},{"section":"list-all-namespaces-resourceclaimtemplate-v1alpha2-resource-k8s-io","subsections":[]},{"section":"list-resourceclaimtemplate-v1alpha2-resource-k8s-io","subsections":[]},{"section":"read-resourceclaimtemplate-v1alpha2-resource-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-resourceclaimtemplate-v1alpha2-resource-k8s-io-strong-","subsections":[{"section":"delete-collection-resourceclaimtemplate-v1alpha2-resource-k8s-io","subsections":[]},{"section":"delete-resourceclaimtemplate-v1alpha2-resource-k8s-io","subsections":[]},{"section":"replace-resourceclaimtemplate-v1alpha2-resource-k8s-io","subsections":[]},{"section":"patch-resourceclaimtemplate-v1alpha2-resource-k8s-io","subsections":[]},{"section":"create-resourceclaimtemplate-v1alpha2-resource-k8s-io","subsections":[]}]}]},{"section":"resourceclaim-v1alpha2-resource-k8s-io","subsections":[{"section":"-strong-status-operations-resourceclaim-v1alpha2-resource-k8s-io-strong-","subsections":[{"section":"replace-status-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"read-status-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"patch-status-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]}]},{"section":"-strong-read-operations-resourceclaim-v1alpha2-resource-k8s-io-strong-","subsections":[{"section":"watch-list-all-namespaces-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"watch-list-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"watch-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"list-all-namespaces-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"list-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"read-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-resourceclaim-v1alpha2-resource-k8s-io-strong-","subsections":[{"section":"delete-collection-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"delete-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"replace-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"patch-resourceclaim-v1alpha2-resource-k8s-io","subsections":[]},{"section":"create-resourceclaim-v1alpha2-resource-k8s-io","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":"podschedulingcontext-v1alpha2-resource-k8s-io","subsections":[{"section":"-strong-status-operations-podschedulingcontext-v1alpha2-resource-k8s-io-strong-","subsections":[{"section":"replace-status-podschedulingcontext-v1alpha2-resource-k8s-io","subsections":[]},{"section":"read-status-podschedulingcontext-v1alpha2-resource-k8s-io","subsections":[]},{"section":"patch-status-podschedulingcontext-v1alpha2-resource-k8s-io","subsections":[]}]},{"section":"-strong-read-operations-podschedulingcontext-v1alpha2-resource-k8s-io-strong-","subsections":[{"section":"watch-list-all-namespaces-podschedulingcontext-v1alpha2-resource-k8s-io","subsections":[]},{"section":"watch-list-podschedulingcontext-v1alpha2-resource-k8s-io","subsections":[]},{"section":"watch-podschedulingcontext-v1alpha2-resource-k8s-io","subsections":[]},{"section":"list-all-namespaces-podschedulingcontext-v1alpha2-resource-k8s-io","subsections":[]},{"section":"list-podschedulingcontext-v1alpha2-resource-k8s-io","subsections":[]},{"section":"read-podschedulingcontext-v1alpha2-resource-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-podschedulingcontext-v1alpha2-resource-k8s-io-strong-","subsections":[{"section":"delete-collection-podschedulingcontext-v1alpha2-resource-k8s-io","subsections":[]},{"section":"delete-podschedulingcontext-v1alpha2-resource-k8s-io","subsections":[]},{"section":"replace-podschedulingcontext-v1alpha2-resource-k8s-io","subsections":[]},{"section":"patch-podschedulingcontext-v1alpha2-resource-k8s-io","subsections":[]},{"section":"create-podschedulingcontext-v1alpha2-resource-k8s-io","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-v2-autoscaling","subsections":[{"section":"-strong-status-operations-horizontalpodautoscaler-v2-autoscaling-strong-","subsections":[{"section":"replace-status-horizontalpodautoscaler-v2-autoscaling","subsections":[]},{"section":"read-status-horizontalpodautoscaler-v2-autoscaling","subsections":[]},{"section":"patch-status-horizontalpodautoscaler-v2-autoscaling","subsections":[]}]},{"section":"-strong-read-operations-horizontalpodautoscaler-v2-autoscaling-strong-","subsections":[{"section":"watch-list-all-namespaces-horizontalpodautoscaler-v2-autoscaling","subsections":[]},{"section":"watch-list-horizontalpodautoscaler-v2-autoscaling","subsections":[]},{"section":"watch-horizontalpodautoscaler-v2-autoscaling","subsections":[]},{"section":"list-all-namespaces-horizontalpodautoscaler-v2-autoscaling","subsections":[]},{"section":"list-horizontalpodautoscaler-v2-autoscaling","subsections":[]},{"section":"read-horizontalpodautoscaler-v2-autoscaling","subsections":[]}]},{"section":"-strong-write-operations-horizontalpodautoscaler-v2-autoscaling-strong-","subsections":[{"section":"delete-collection-horizontalpodautoscaler-v2-autoscaling","subsections":[]},{"section":"delete-horizontalpodautoscaler-v2-autoscaling","subsections":[]},{"section":"replace-horizontalpodautoscaler-v2-autoscaling","subsections":[]},{"section":"patch-horizontalpodautoscaler-v2-autoscaling","subsections":[]},{"section":"create-horizontalpodautoscaler-v2-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":"clustertrustbundle-v1alpha1-certificates-k8s-io","subsections":[{"section":"-strong-read-operations-clustertrustbundle-v1alpha1-certificates-k8s-io-strong-","subsections":[{"section":"watch-list-clustertrustbundle-v1alpha1-certificates-k8s-io","subsections":[]},{"section":"watch-clustertrustbundle-v1alpha1-certificates-k8s-io","subsections":[]},{"section":"list-clustertrustbundle-v1alpha1-certificates-k8s-io","subsections":[]},{"section":"read-clustertrustbundle-v1alpha1-certificates-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-clustertrustbundle-v1alpha1-certificates-k8s-io-strong-","subsections":[{"section":"delete-collection-clustertrustbundle-v1alpha1-certificates-k8s-io","subsections":[]},{"section":"delete-clustertrustbundle-v1alpha1-certificates-k8s-io","subsections":[]},{"section":"replace-clustertrustbundle-v1alpha1-certificates-k8s-io","subsections":[]},{"section":"patch-clustertrustbundle-v1alpha1-certificates-k8s-io","subsections":[]},{"section":"create-clustertrustbundle-v1alpha1-certificates-k8s-io","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-v1-storage-k8s-io","subsections":[{"section":"-strong-read-operations-csistoragecapacity-v1-storage-k8s-io-strong-","subsections":[{"section":"watch-list-all-namespaces-csistoragecapacity-v1-storage-k8s-io","subsections":[]},{"section":"watch-list-csistoragecapacity-v1-storage-k8s-io","subsections":[]},{"section":"watch-csistoragecapacity-v1-storage-k8s-io","subsections":[]},{"section":"list-all-namespaces-csistoragecapacity-v1-storage-k8s-io","subsections":[]},{"section":"list-csistoragecapacity-v1-storage-k8s-io","subsections":[]},{"section":"read-csistoragecapacity-v1-storage-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-csistoragecapacity-v1-storage-k8s-io-strong-","subsections":[{"section":"delete-collection-csistoragecapacity-v1-storage-k8s-io","subsections":[]},{"section":"delete-csistoragecapacity-v1-storage-k8s-io","subsections":[]},{"section":"replace-csistoragecapacity-v1-storage-k8s-io","subsections":[]},{"section":"patch-csistoragecapacity-v1-storage-k8s-io","subsections":[]},{"section":"create-csistoragecapacity-v1-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":"clustercidr-v1alpha1-networking-k8s-io","subsections":[{"section":"-strong-read-operations-clustercidr-v1alpha1-networking-k8s-io-strong-","subsections":[{"section":"watch-list-clustercidr-v1alpha1-networking-k8s-io","subsections":[]},{"section":"watch-clustercidr-v1alpha1-networking-k8s-io","subsections":[]},{"section":"list-clustercidr-v1alpha1-networking-k8s-io","subsections":[]},{"section":"read-clustercidr-v1alpha1-networking-k8s-io","subsections":[]}]},{"section":"-strong-write-operations-clustercidr-v1alpha1-networking-k8s-io-strong-","subsections":[{"section":"delete-collection-clustercidr-v1alpha1-networking-k8s-io","subsections":[]},{"section":"delete-clustercidr-v1alpha1-networking-k8s-io","subsections":[]},{"section":"replace-clustercidr-v1alpha1-networking-k8s-io","subsections":[]},{"section":"patch-clustercidr-v1alpha1-networking-k8s-io","subsections":[]},{"section":"create-clustercidr-v1alpha1-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-v1beta2-flowcontrol-apiserver-k8s-io","tokenrequest-v1-storage-k8s-io","subject-v1beta2-flowcontrol-apiserver-k8s-io","subject-v1-rbac-authorization-k8s-io","servicereference-v1-apiregistration-k8s-io","servicereference-v1-apiextensions-k8s-io","serviceaccountsubject-v1beta2-flowcontrol-apiserver-k8s-io","create-selfsubjectreview-v1alpha1-authentication-k8s-io","-strong-write-operations-selfsubjectreview-v1alpha1-authentication-k8s-io-strong-","selfsubjectreview-v1alpha1-authentication-k8s-io","resourcepolicyrule-v1beta2-flowcontrol-apiserver-k8s-io","replace-status-resourceclaim-v1alpha2-resource-k8s-io","read-status-resourceclaim-v1alpha2-resource-k8s-io","patch-status-resourceclaim-v1alpha2-resource-k8s-io","-strong-status-operations-resourceclaim-v1alpha2-resource-k8s-io-strong-","watch-list-all-namespaces-resourceclaim-v1alpha2-resource-k8s-io","watch-list-resourceclaim-v1alpha2-resource-k8s-io","watch-resourceclaim-v1alpha2-resource-k8s-io","list-all-namespaces-resourceclaim-v1alpha2-resource-k8s-io","list-resourceclaim-v1alpha2-resource-k8s-io","read-resourceclaim-v1alpha2-resource-k8s-io","-strong-read-operations-resourceclaim-v1alpha2-resource-k8s-io-strong-","delete-collection-resourceclaim-v1alpha2-resource-k8s-io","delete-resourceclaim-v1alpha2-resource-k8s-io","replace-resourceclaim-v1alpha2-resource-k8s-io","patch-resourceclaim-v1alpha2-resource-k8s-io","create-resourceclaim-v1alpha2-resource-k8s-io","-strong-write-operations-resourceclaim-v1alpha2-resource-k8s-io-strong-","resourceclaim-v1alpha2-resource-k8s-io","queuingconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","prioritylevelconfigurationreference-v1beta2-flowcontrol-apiserver-k8s-io","prioritylevelconfigurationcondition-v1beta2-flowcontrol-apiserver-k8s-io","replace-status-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","read-status-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","patch-status-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","-strong-status-operations-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io-strong-","watch-list-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","watch-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","list-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","read-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","-strong-read-operations-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io-strong-","delete-collection-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","delete-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","replace-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","patch-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","create-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","-strong-write-operations-prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io-strong-","prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","policyruleswithsubjects-v1beta2-flowcontrol-apiserver-k8s-io","nonresourcepolicyrule-v1beta2-flowcontrol-apiserver-k8s-io","matchcondition-v1alpha1-admissionregistration-k8s-io","limitedprioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io","limitresponse-v1beta2-flowcontrol-apiserver-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","groupsubject-v1beta2-flowcontrol-apiserver-k8s-io","flowschemacondition-v1beta2-flowcontrol-apiserver-k8s-io","replace-status-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","read-status-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","patch-status-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","-strong-status-operations-flowschema-v1beta2-flowcontrol-apiserver-k8s-io-strong-","watch-list-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","watch-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","list-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","read-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","-strong-read-operations-flowschema-v1beta2-flowcontrol-apiserver-k8s-io-strong-","delete-collection-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","delete-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","replace-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","patch-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","create-flowschema-v1beta2-flowcontrol-apiserver-k8s-io","-strong-write-operations-flowschema-v1beta2-flowcontrol-apiserver-k8s-io-strong-","flowschema-v1beta2-flowcontrol-apiserver-k8s-io","flowdistinguishermethod-v1beta2-flowcontrol-apiserver-k8s-io","eventseries-v1-core","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","endpointport-v1-discovery-k8s-io","crossversionobjectreference-v1-autoscaling","-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","validation-v1alpha1-admissionregistration-k8s-io","validatingwebhook-v1-admissionregistration-k8s-io","usersubject-v1beta3-flowcontrol-apiserver-k8s-io","userinfo-v1-authentication-k8s-io","uncountedterminatedpods-v1-batch","typedobjectreference-v1-core","typedlocalobjectreference-v1-core","typechecking-v1alpha1-admissionregistration-k8s-io","topologyspreadconstraint-v1-core","topologyselectorterm-v1-core","topologyselectorlabelrequirement-v1-core","toleration-v1-core","time-v1-meta","taint-v1-core","tcpsocketaction-v1-core","sysctl-v1-core","subjectrulesreviewstatus-v1-authorization-k8s-io","subject-v1beta3-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","statefulsetordinals-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-v1beta3-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","selinuxoptions-v1-core","rulewithoperations-v1-admissionregistration-k8s-io","rollingupdatestatefulsetstrategy-v1-apps","roleref-v1-rbac-authorization-k8s-io","resourcerule-v1-authorization-k8s-io","resourcerequirements-v1-core","resourcepolicyrule-v1beta3-flowcontrol-apiserver-k8s-io","resourcemetricstatus-v2-autoscaling","resourcemetricsource-v2-autoscaling","resourcehandle-v1alpha2-resource-k8s-io","resourcefieldselector-v1-core","resourceclassparametersreference-v1alpha2-resource-k8s-io","resourceclaimschedulingstatus-v1alpha2-resource-k8s-io","resourceclaimparametersreference-v1alpha2-resource-k8s-io","resourceclaimconsumerreference-v1alpha2-resource-k8s-io","resourceclaim-v1-core","resourceattributes-v1-authorization-k8s-io","replicationcontrollercondition-v1-core","replicasetcondition-v1-apps","rbdvolumesource-v1-core","rbdpersistentvolumesource-v1-core","quobytevolumesource-v1-core","queuingconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","quantity-resource-core","projectedvolumesource-v1-core","probe-v1-core","prioritylevelconfigurationreference-v1beta3-flowcontrol-apiserver-k8s-io","prioritylevelconfigurationcondition-v1beta3-flowcontrol-apiserver-k8s-io","preferredschedulingterm-v1-core","preconditions-v1-meta","portworxvolumesource-v1-core","portstatus-v1-core","policyruleswithsubjects-v1beta3-flowcontrol-apiserver-k8s-io","policyrule-v1-rbac-authorization-k8s-io","podsmetricstatus-v2-autoscaling","podsmetricsource-v2-autoscaling","podsecuritycontext-v1-core","podschedulinggate-v1-core","podresourceclaim-v1-core","podreadinessgate-v1-core","podos-v1-core","podip-v1-core","podfailurepolicyrule-v1-batch","podfailurepolicyonpodconditionspattern-v1-batch","podfailurepolicyonexitcodesrequirement-v1-batch","podfailurepolicy-v1-batch","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","parentreference-v1alpha1-networking-k8s-io","paramref-v1alpha1-admissionregistration-k8s-io","paramkind-v1alpha1-admissionregistration-k8s-io","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-v1beta3-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","namedrulewithoperations-v1alpha1-admissionregistration-k8s-io","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","matchresources-v1alpha1-admissionregistration-k8s-io","matchcondition-v1-admissionregistration-k8s-io","managedfieldsentry-v1-meta","localvolumesource-v1-core","localobjectreference-v1-core","loadbalancerstatus-v1-core","loadbalanceringress-v1-core","listmeta-v1-meta","limitedprioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","limitresponse-v1beta3-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","ingressportstatus-v1-networking-k8s-io","ingressloadbalancerstatus-v1-networking-k8s-io","ingressloadbalanceringress-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","hostpathvolumesource-v1-core","hostalias-v1-core","horizontalpodautoscalercondition-v2-autoscaling","horizontalpodautoscalerbehavior-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-v1beta3-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-v1beta3-flowcontrol-apiserver-k8s-io","flowdistinguishermethod-v1beta3-flowcontrol-apiserver-k8s-io","flockervolumesource-v1-core","flexvolumesource-v1-core","flexpersistentvolumesource-v1-core","fieldsv1-v1-meta","fcvolumesource-v1-core","externalmetricstatus-v2-autoscaling","externalmetricsource-v2-autoscaling","externaldocumentation-v1-apiextensions-k8s-io","expressionwarning-v1alpha1-admissionregistration-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-v2-autoscaling","containerstatewaiting-v1-core","containerstateterminated-v1-core","containerstaterunning-v1-core","containerstate-v1-core","containerresourcemetricstatus-v2-autoscaling","containerresourcemetricsource-v2-autoscaling","containerresizepolicy-v1-core","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","claimsource-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","auditannotation-v1alpha1-admissionregistration-k8s-io","attachedvolume-v1-core","allocationresult-v1alpha2-resource-k8s-io","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-","replace-status-networkpolicy-v1-networking-k8s-io","read-status-networkpolicy-v1-networking-k8s-io","patch-status-networkpolicy-v1-networking-k8s-io","-strong-status-operations-networkpolicy-v1-networking-k8s-io-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-selfsubjectreview-v1beta1-authentication-k8s-io","-strong-write-operations-selfsubjectreview-v1beta1-authentication-k8s-io-strong-","selfsubjectreview-v1beta1-authentication-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-v1beta3-flowcontrol-apiserver-k8s-io","read-status-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","patch-status-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","-strong-status-operations-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io-strong-","watch-list-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","watch-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","list-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","read-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","-strong-read-operations-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io-strong-","delete-collection-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","delete-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","replace-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","patch-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","create-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io","-strong-write-operations-prioritylevelconfiguration-v1beta3-flowcontrol-apiserver-k8s-io-strong-","prioritylevelconfiguration-v1beta3-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","watch-list-ipaddress-v1alpha1-networking-k8s-io","watch-ipaddress-v1alpha1-networking-k8s-io","list-ipaddress-v1alpha1-networking-k8s-io","read-ipaddress-v1alpha1-networking-k8s-io","-strong-read-operations-ipaddress-v1alpha1-networking-k8s-io-strong-","delete-collection-ipaddress-v1alpha1-networking-k8s-io","delete-ipaddress-v1alpha1-networking-k8s-io","replace-ipaddress-v1alpha1-networking-k8s-io","patch-ipaddress-v1alpha1-networking-k8s-io","create-ipaddress-v1alpha1-networking-k8s-io","-strong-write-operations-ipaddress-v1alpha1-networking-k8s-io-strong-","ipaddress-v1alpha1-networking-k8s-io","replace-status-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","read-status-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","patch-status-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","-strong-status-operations-flowschema-v1beta3-flowcontrol-apiserver-k8s-io-strong-","watch-list-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","watch-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","list-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","read-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","-strong-read-operations-flowschema-v1beta3-flowcontrol-apiserver-k8s-io-strong-","delete-collection-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","delete-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","replace-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","patch-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","create-flowschema-v1beta3-flowcontrol-apiserver-k8s-io","-strong-write-operations-flowschema-v1beta3-flowcontrol-apiserver-k8s-io-strong-","flowschema-v1beta3-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-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io","watch-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io","list-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io","read-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io","-strong-read-operations-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io-strong-","delete-collection-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io","delete-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io","replace-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io","patch-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io","create-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io","-strong-write-operations-validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io-strong-","validatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io","replace-status-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","read-status-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","patch-status-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","-strong-status-operations-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io-strong-","watch-list-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","watch-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","list-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","read-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","-strong-read-operations-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io-strong-","delete-collection-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","delete-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","replace-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","patch-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","create-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","-strong-write-operations-validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io-strong-","validatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io","watch-list-resourceclass-v1alpha2-resource-k8s-io","watch-resourceclass-v1alpha2-resource-k8s-io","list-resourceclass-v1alpha2-resource-k8s-io","read-resourceclass-v1alpha2-resource-k8s-io","-strong-read-operations-resourceclass-v1alpha2-resource-k8s-io-strong-","delete-collection-resourceclass-v1alpha2-resource-k8s-io","delete-resourceclass-v1alpha2-resource-k8s-io","replace-resourceclass-v1alpha2-resource-k8s-io","patch-resourceclass-v1alpha2-resource-k8s-io","create-resourceclass-v1alpha2-resource-k8s-io","-strong-write-operations-resourceclass-v1alpha2-resource-k8s-io-strong-","resourceclass-v1alpha2-resource-k8s-io","watch-list-all-namespaces-resourceclaimtemplate-v1alpha2-resource-k8s-io","watch-list-resourceclaimtemplate-v1alpha2-resource-k8s-io","watch-resourceclaimtemplate-v1alpha2-resource-k8s-io","list-all-namespaces-resourceclaimtemplate-v1alpha2-resource-k8s-io","list-resourceclaimtemplate-v1alpha2-resource-k8s-io","read-resourceclaimtemplate-v1alpha2-resource-k8s-io","-strong-read-operations-resourceclaimtemplate-v1alpha2-resource-k8s-io-strong-","delete-collection-resourceclaimtemplate-v1alpha2-resource-k8s-io","delete-resourceclaimtemplate-v1alpha2-resource-k8s-io","replace-resourceclaimtemplate-v1alpha2-resource-k8s-io","patch-resourceclaimtemplate-v1alpha2-resource-k8s-io","create-resourceclaimtemplate-v1alpha2-resource-k8s-io","-strong-write-operations-resourceclaimtemplate-v1alpha2-resource-k8s-io-strong-","resourceclaimtemplate-v1alpha2-resource-k8s-io","replace-status-resourceclaim-v1alpha2-resource-k8s-io","read-status-resourceclaim-v1alpha2-resource-k8s-io","patch-status-resourceclaim-v1alpha2-resource-k8s-io","-strong-status-operations-resourceclaim-v1alpha2-resource-k8s-io-strong-","watch-list-all-namespaces-resourceclaim-v1alpha2-resource-k8s-io","watch-list-resourceclaim-v1alpha2-resource-k8s-io","watch-resourceclaim-v1alpha2-resource-k8s-io","list-all-namespaces-resourceclaim-v1alpha2-resource-k8s-io","list-resourceclaim-v1alpha2-resource-k8s-io","read-resourceclaim-v1alpha2-resource-k8s-io","-strong-read-operations-resourceclaim-v1alpha2-resource-k8s-io-strong-","delete-collection-resourceclaim-v1alpha2-resource-k8s-io","delete-resourceclaim-v1alpha2-resource-k8s-io","replace-resourceclaim-v1alpha2-resource-k8s-io","patch-resourceclaim-v1alpha2-resource-k8s-io","create-resourceclaim-v1alpha2-resource-k8s-io","-strong-write-operations-resourceclaim-v1alpha2-resource-k8s-io-strong-","resourceclaim-v1alpha2-resource-k8s-io","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","replace-status-podschedulingcontext-v1alpha2-resource-k8s-io","read-status-podschedulingcontext-v1alpha2-resource-k8s-io","patch-status-podschedulingcontext-v1alpha2-resource-k8s-io","-strong-status-operations-podschedulingcontext-v1alpha2-resource-k8s-io-strong-","watch-list-all-namespaces-podschedulingcontext-v1alpha2-resource-k8s-io","watch-list-podschedulingcontext-v1alpha2-resource-k8s-io","watch-podschedulingcontext-v1alpha2-resource-k8s-io","list-all-namespaces-podschedulingcontext-v1alpha2-resource-k8s-io","list-podschedulingcontext-v1alpha2-resource-k8s-io","read-podschedulingcontext-v1alpha2-resource-k8s-io","-strong-read-operations-podschedulingcontext-v1alpha2-resource-k8s-io-strong-","delete-collection-podschedulingcontext-v1alpha2-resource-k8s-io","delete-podschedulingcontext-v1alpha2-resource-k8s-io","replace-podschedulingcontext-v1alpha2-resource-k8s-io","patch-podschedulingcontext-v1alpha2-resource-k8s-io","create-podschedulingcontext-v1alpha2-resource-k8s-io","-strong-write-operations-podschedulingcontext-v1alpha2-resource-k8s-io-strong-","podschedulingcontext-v1alpha2-resource-k8s-io","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-v2-autoscaling","read-status-horizontalpodautoscaler-v2-autoscaling","patch-status-horizontalpodautoscaler-v2-autoscaling","-strong-status-operations-horizontalpodautoscaler-v2-autoscaling-strong-","watch-list-all-namespaces-horizontalpodautoscaler-v2-autoscaling","watch-list-horizontalpodautoscaler-v2-autoscaling","watch-horizontalpodautoscaler-v2-autoscaling","list-all-namespaces-horizontalpodautoscaler-v2-autoscaling","list-horizontalpodautoscaler-v2-autoscaling","read-horizontalpodautoscaler-v2-autoscaling","-strong-read-operations-horizontalpodautoscaler-v2-autoscaling-strong-","delete-collection-horizontalpodautoscaler-v2-autoscaling","delete-horizontalpodautoscaler-v2-autoscaling","replace-horizontalpodautoscaler-v2-autoscaling","patch-horizontalpodautoscaler-v2-autoscaling","create-horizontalpodautoscaler-v2-autoscaling","-strong-write-operations-horizontalpodautoscaler-v2-autoscaling-strong-","horizontalpodautoscaler-v2-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","watch-list-clustertrustbundle-v1alpha1-certificates-k8s-io","watch-clustertrustbundle-v1alpha1-certificates-k8s-io","list-clustertrustbundle-v1alpha1-certificates-k8s-io","read-clustertrustbundle-v1alpha1-certificates-k8s-io","-strong-read-operations-clustertrustbundle-v1alpha1-certificates-k8s-io-strong-","delete-collection-clustertrustbundle-v1alpha1-certificates-k8s-io","delete-clustertrustbundle-v1alpha1-certificates-k8s-io","replace-clustertrustbundle-v1alpha1-certificates-k8s-io","patch-clustertrustbundle-v1alpha1-certificates-k8s-io","create-clustertrustbundle-v1alpha1-certificates-k8s-io","-strong-write-operations-clustertrustbundle-v1alpha1-certificates-k8s-io-strong-","clustertrustbundle-v1alpha1-certificates-k8s-io","-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-v1-storage-k8s-io","watch-list-csistoragecapacity-v1-storage-k8s-io","watch-csistoragecapacity-v1-storage-k8s-io","list-all-namespaces-csistoragecapacity-v1-storage-k8s-io","list-csistoragecapacity-v1-storage-k8s-io","read-csistoragecapacity-v1-storage-k8s-io","-strong-read-operations-csistoragecapacity-v1-storage-k8s-io-strong-","delete-collection-csistoragecapacity-v1-storage-k8s-io","delete-csistoragecapacity-v1-storage-k8s-io","replace-csistoragecapacity-v1-storage-k8s-io","patch-csistoragecapacity-v1-storage-k8s-io","create-csistoragecapacity-v1-storage-k8s-io","-strong-write-operations-csistoragecapacity-v1-storage-k8s-io-strong-","csistoragecapacity-v1-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-clustercidr-v1alpha1-networking-k8s-io","watch-clustercidr-v1alpha1-networking-k8s-io","list-clustercidr-v1alpha1-networking-k8s-io","read-clustercidr-v1alpha1-networking-k8s-io","-strong-read-operations-clustercidr-v1alpha1-networking-k8s-io-strong-","delete-collection-clustercidr-v1alpha1-networking-k8s-io","delete-clustercidr-v1alpha1-networking-k8s-io","replace-clustercidr-v1alpha1-networking-k8s-io","patch-clustercidr-v1alpha1-networking-k8s-io","create-clustercidr-v1alpha1-networking-k8s-io","-strong-write-operations-clustercidr-v1alpha1-networking-k8s-io-strong-","clustercidr-v1alpha1-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

From 7046c173da64fdc0768b79fcc9cb010d1e6d5b07 Mon Sep 17 00:00:00 2001
From: Guangwen Feng <fenggw-fnst@fujitsu.com>
Date: Wed, 12 Apr 2023 15:33:55 +0800
Subject: [PATCH 167/272] [zh-cn] Sync issues-security/official-cve-feed.md

Signed-off-by: Guangwen Feng <fenggw-fnst@fujitsu.com>
---
 .../docs/reference/issues-security/official-cve-feed.md    | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/content/zh-cn/docs/reference/issues-security/official-cve-feed.md b/content/zh-cn/docs/reference/issues-security/official-cve-feed.md
index 76f373f627b..84673783bec 100644
--- a/content/zh-cn/docs/reference/issues-security/official-cve-feed.md
+++ b/content/zh-cn/docs/reference/issues-security/official-cve-feed.md
@@ -7,7 +7,7 @@ layout: cve-feed
 <!--
 title: Official CVE Feed
 linkTitle: CVE feed
-weight: 25feed
+weight: 25
 outputs:
   - json
   - html
@@ -15,7 +15,7 @@ outputs:
 layout: cve-feed
 -->
 
-{{< feature-state for_k8s_version="v1.25" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
 
 <!--
 This is a community maintained list of official CVEs announced by
@@ -73,7 +73,8 @@ from the time a CVE is announced to the time it is accessible in this feed.
 
 The source of truth of this feed is a set of GitHub Issues, filtered by a controlled and
 restricted label `official-cve-feed`. The raw data is stored in a Google Cloud
-Bucket which is writable only by a small number of trusted members of the Community.
+Bucket which is writable only by a small number of trusted members of the
+Community.
 -->
 此订阅源会自动刷新，但从宣布 CVE 到可在此订阅源中找到对应的 CVE 会有一个明显却很小的延迟（几分钟到几小时）。
 

From 9b0af72e3531b20d407375e86af6dc108d451f5a Mon Sep 17 00:00:00 2001
From: Sascha Grunert <sgrunert@redhat.com>
Date: Wed, 12 Apr 2023 09:36:40 +0200
Subject: [PATCH 168/272] Re-add v1.24 schedule to patch releases

We removed them as part of https://github.com/kubernetes/website/pull/40551,
but v1.24 is not EOL yet.

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
---
 data/releases/schedule.yaml | 54 +++++++++++++++++++++++++++++++++++++
 1 file changed, 54 insertions(+)

diff --git a/data/releases/schedule.yaml b/data/releases/schedule.yaml
index 4673097d521..933fffc79d1 100644
--- a/data/releases/schedule.yaml
+++ b/data/releases/schedule.yaml
@@ -76,3 +76,57 @@ schedules:
     - release: 1.25.0
       cherryPickDeadline: ""
       targetDate: 2022-08-23
+- release: 1.24
+  releaseDate: 2022-05-03
+  maintenanceModeStartDate: 2023-05-28
+  endOfLifeDate: 2023-07-28
+  next:
+    release: 1.24.13
+    cherryPickDeadline: 2023-04-07
+    targetDate: 2023-04-12
+  previousPatches:
+    - release: 1.24.12
+      cherryPickDeadline: 2023-03-10
+      targetDate: 2023-03-15
+    - release: 1.24.11
+      cherryPickDeadline: 2023-02-10
+      targetDate: 2023-02-15
+      note: >-
+        [Some container images might be **unsigned** due to a temporary issue with the promotion process](https://groups.google.com/a/kubernetes.io/g/dev/c/MwSx761slM0/m/4ajkeUl0AQAJ)
+    - release: 1.24.10
+      cherryPickDeadline: 2023-01-13
+      targetDate: 2023-01-18
+    - release: 1.24.9
+      cherryPickDeadline: 2022-12-02
+      targetDate: 2022-12-08
+    - release: 1.24.8
+      cherryPickDeadline: 2022-11-04
+      targetDate: 2022-11-09
+    - release: 1.24.7
+      cherryPickDeadline: 2022-10-07
+      targetDate: 2022-10-12
+    - release: 1.24.6
+      cherryPickDeadline: 2022-09-20
+      targetDate: 2022-09-21
+      note: >-
+        [Out-of-Band release to fix the regression introduced in 1.24.5](https://groups.google.com/a/kubernetes.io/g/dev/c/tA6LNOQTR4Q/m/zL73maPTAQAJ)
+    - release: 1.24.5
+      cherryPickDeadline: 2022-09-09
+      targetDate: 2022-09-14
+      note: >-
+        [Regression](https://groups.google.com/a/kubernetes.io/g/dev/c/tA6LNOQTR4Q/m/zL73maPTAQAJ)
+    - release: 1.24.4
+      cherryPickDeadline: 2022-08-12
+      targetDate: 2022-08-17
+    - release: 1.24.3
+      cherryPickDeadline: 2022-07-08
+      targetDate: 2022-07-13
+    - release: 1.24.2
+      cherryPickDeadline: 2022-06-10
+      targetDate: 2022-06-15
+    - release: 1.24.1
+      cherryPickDeadline: 2022-05-20
+      targetDate: 2022-05-24
+    - release: 1.24.0
+      cherryPickDeadline: ""
+      targetDate: 2022-05-03

From 3292ae8e09657100bd3b7b47c5b3effd1f04c5f9 Mon Sep 17 00:00:00 2001
From: xuzhenglun <xuzhenglun@gmail.com>
Date: Wed, 22 Mar 2023 10:06:38 +0800
Subject: [PATCH 169/272] add blog document for feature
 ServiceNodePortStaticSubrange

---
 ...-nodeport-dynamic-and-static-allocation.md | 173 ++++++++++++++++++
 1 file changed, 173 insertions(+)
 create mode 100644 content/en/blog/_posts/2023-05-11-nodeport-dynamic-and-static-allocation.md

diff --git a/content/en/blog/_posts/2023-05-11-nodeport-dynamic-and-static-allocation.md b/content/en/blog/_posts/2023-05-11-nodeport-dynamic-and-static-allocation.md
new file mode 100644
index 00000000000..fde6ed1c1d5
--- /dev/null
+++ b/content/en/blog/_posts/2023-05-11-nodeport-dynamic-and-static-allocation.md
@@ -0,0 +1,173 @@
+---
+layout: blog
+title: "Kubernetes 1.27: Avoid Collisions Assigning Ports to NodePort Services"
+date: 2023-05-11
+slug: nodeport-dynamic-and-static-allocation
+---
+
+**Author:** Xu Zhenglun (Alibaba)
+
+In Kubernetes, a Service can be used to provide a unified traffic endpoint for 
+applications running on a set of Pods. Clients can use the virtual IP address (or _VIP_) provided
+by the Service for access, and Kubernetes provides load balancing for traffic accessing
+different back-end Pods, but a ClusterIP type of Service is limited to providing access to
+nodes within the cluster, while traffic from outside the cluster cannot be routed.
+One way to solve this problem is to use a `type: NodePort` Service, which sets up a mapping
+to a specific port of all nodes in the cluster, thus redirecting traffic from the
+outside to the inside of the cluster.
+
+## How Kubernetes allocates node ports to Services?
+
+When a `type: NodePort` Service is created, its corresponding port(s) are allocated in one
+of two ways:
+
+- **Dynamic** : If the Service type is `NodePort` and you do not set a `nodePort` 
+  value explicitly in the `spec` for that Service, the Kubernetes control plane will
+  automatically allocate an unused port to it at creation time.
+
+- **Static** : In addition to the dynamic auto-assignment described above, you can also
+  explicitly assign a port that is within the nodeport port range configuration.
+
+The value of `nodePort` that you manually assign must be unique across the whole cluster.
+Attempting to create a Service of `type: NodePort` where you explicitly specify a node port that
+was already allocated results in an error.
+
+## Why do you need to reserve ports of NodePort Service? 
+Sometimes, you may want to have a NodePort Service running on well-known ports
+so that other components and users inside o r outside the cluster can use them.
+
+In some complex cluster deployments with a mix of Kubernetes nodes and other servers on the same network, 
+it may be necessary to use some pre-defined ports for communication. In particular, some fundamental
+components cannot rely on the VIPs that back `type: LoadBalancer` Services
+because the virtual IP address mapping implementation for that cluster also relies on
+these foundational components.
+
+Now suppose you need to expose a Minio object storage service on Kubernetes to clients 
+running outside the Kubernetes cluster, and the agreed port is `30009`, we need to 
+create a Service as follows:
+
+```yaml
+apiVersion: v1
+kind: Service
+metadata:
+  name: minio
+spec:
+  ports:
+  - name: api
+    nodePort: 30009
+    port: 9000
+    protocol: TCP
+    targetPort: 9000
+  selector:
+    app: minio
+  type: NodePort
+```
+
+However, as mentioned before, if the port (30009) required for the `minio` Service is not reserved,
+and another `type: NodePort` (or possibly `type: LoadBalancer`) Service is created and dynamically
+allocated before or concurrently with the `minio` Service, TCP port 30009 might be allocated to that
+other Service; if so, creation of the `minio` Service will fail due to a node port collision.
+
+## How can you avoid NodePort Service port conflicts? 
+Kubernetes 1.24 introduced changes for `type: ClusterIP` Services, dividing the CIDR range for cluster
+IP addresses into two blocks that use different allocation policies to [reduce the risk of conflicts](/docs/reference/networking/virtual-ips/#avoiding-collisions).
+In Kubernetes 1.27, as an alpha feature, you can adopt a similar policy for `type: NodePort` Servies.
+You can enable a new [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+`ServiceNodePortStaticSubrange`. Turning this on allows you to use a different port allocation strategy
+for `type: NodePort` Services, and reduce the risk of collision.
+
+The port range for `NodePort` will be divided, based on the formula `min(max(16, nodeport-size / 32), 128)`. 
+The outcome of the formula will be a number between 16 and 128, with a step size that increases as the 
+size of the nodeport range increases. The outcome of the formula determine that the size of static port 
+range. When the port range is less than 16, the size of static port range will be set to 0, 
+which means that all ports will be dynamically allocated.
+
+Dynamic port assignment will use the upper band by default, once this has been exhausted it will use the lower range.
+This will allow users to use static allocations on the lower band with a low risk of collision.
+
+## Examples
+
+### default range: 30000-32767
+| Range properties        | Values                                                |
+|-------------------------|-------------------------------------------------------|
+| service-node-port-range | 30000-32767                                           |
+| Band Offset             | &ensp; `min(max(16, 2768/32), 128)` <br>= `min(max(16, 86), 128)` <br>= `min(86, 128)` <br>= 86 |
+| Static band start       | 30000                                                 |
+| Static band end         | 30085                                                 |
+| Dynamic band start      | 30086                                                 |
+| Dynamic band end        | 32767                                                 |
+
+{{< mermaid >}}
+pie showData
+    title 30000-32767
+    "Static" : 86
+    "Dynamic" : 2682
+{{< /mermaid >}}
+
+### very small range: 30000-30015
+| Range properties        | Values                                                |
+|-------------------------|-------------------------------------------------------|
+| service-node-port-range | 30000-30015                                           |
+| Band Offset             | 0                                                     |
+| Static band start       | -                                                     |
+| Static band end         | -                                                     |
+| Dynamic band start      | 30000                                                 |
+| Dynamic band end        | 30015                                                 |
+
+{{< mermaid >}}
+pie showData
+    title 30000-30015
+    "Static" : 0
+    "Dynamic" : 16
+{{< /mermaid >}}
+
+### small(lower boundary) range: 30000-30127
+| Range properties        | Values                                                |
+|-------------------------|-------------------------------------------------------|
+| service-node-port-range | 30000-30127                                           |
+| Band Offset             | &ensp; `min(max(16, 128/32), 128)` <br>= `min(max(16, 4), 128)` <br>= `min(16, 128)` <br>= 16 |
+| Static band start       | 30000                                                 |
+| Static band end         | 30015                                                 |
+| Dynamic band start      | 30016                                                 |
+| Dynamic band end        | 30127                                                 |
+
+{{< mermaid >}}
+pie showData
+    title 30000-30127
+    "Static" : 16
+    "Dynamic" : 112
+{{< /mermaid >}}
+
+### large(upper boundary) range: 30000-34095
+| Range properties        | Values                                                |
+|-------------------------|-------------------------------------------------------|
+| service-node-port-range | 30000-34095                                           |
+| Band Offset             | &ensp; `min(max(16, 4096/32), 128)` <br>= `min(max(16, 128), 128)` <br>= `min(128, 128)` <br>= 128 |
+| Static band start       | 30000                                                 |
+| Static band end         | 30127                                                 |
+| Dynamic band start      | 30128                                                 |
+| Dynamic band end        | 34095                                                 |
+
+{{< mermaid >}}
+pie showData
+    title 30000-34095
+    "Static" : 128
+    "Dynamic" : 3968
+{{< /mermaid >}}
+
+### very large range: 30000-38191
+| Range properties        | Values                                                |
+|-------------------------|-------------------------------------------------------|
+| service-node-port-range | 30000-38191                                           |
+| Band Offset             | &ensp; `min(max(16, 8192/32), 128)` <br>= `min(max(16, 256), 128)` <br>= `min(256, 128)` <br>= 128 |
+| Static band start       | 30000                                                 |
+| Static band end         | 30127                                                 |
+| Dynamic band start      | 30128                                                 |
+| Dynamic band end        | 38191                                                 |
+
+{{< mermaid >}}
+pie showData
+    title 30000-38191
+    "Static" : 128
+    "Dynamic" : 8064
+{{< /mermaid >}}
\ No newline at end of file

From aecfbf10b8443fb01041112b1487386d6cbeeae1 Mon Sep 17 00:00:00 2001
From: Guangwen Feng <fenggw-fnst@fujitsu.com>
Date: Wed, 12 Apr 2023 16:41:06 +0800
Subject: [PATCH 170/272] [zh-cn] Sync pod-qos.md

Signed-off-by: Guangwen Feng <fenggw-fnst@fujitsu.com>
---
 .../docs/concepts/workloads/pods/pod-qos.md   | 38 +++++++++++++++++--
 1 file changed, 34 insertions(+), 4 deletions(-)

diff --git a/content/zh-cn/docs/concepts/workloads/pods/pod-qos.md b/content/zh-cn/docs/concepts/workloads/pods/pod-qos.md
index 10647dfc16f..f47384643a3 100644
--- a/content/zh-cn/docs/concepts/workloads/pods/pod-qos.md
+++ b/content/zh-cn/docs/concepts/workloads/pods/pod-qos.md
@@ -79,7 +79,7 @@ CPU 管理策略来使用独占的 CPU。
 
 For a Pod to be given a QoS class of `Guaranteed`:
 -->
-#### 判据
+#### 判据   {#criteria}
 
 Pod 被赋予 `Guaranteed` QoS 类的几个判据：
 
@@ -119,7 +119,7 @@ A Pod is given a QoS class of `Burstable` if:
 * The Pod does not meet the criteria for QoS class `Guaranteed`.
 * At least one Container in the Pod has a memory or CPU request or limit.
 -->
-#### 判据
+#### 判据   {#criteria-1}
 
 Pod 被赋予 `Burstable` QoS 类的几个判据：
 
@@ -152,13 +152,43 @@ CPU limit or a CPU request.
 Containers in a Pod can request other resources (not CPU or memory) and still be classified as
 `BestEffort`.
 -->
-#### 判据
+#### 判据   {#criteria-2}
 
 如果 Pod 不满足 `Guaranteed` 或 `Burstable` 的判据，则它的 QoS 类为 `BestEffort`。
 换言之，只有当 Pod 中的所有容器没有内存 limit 或内存 request，也没有 CPU limit 或
 CPU request 时，Pod 才是 `BestEffort`。Pod 中的容器可以请求（除 CPU 或内存之外的）
 其他资源并且仍然被归类为 `BestEffort`。
 
+<!--
+## Memory QoS with cgroup v2
+-->
+## 使用 cgroup v2 的内存 QoS   {#memory-qos-with-cgroup-v2}
+
+{{< feature-state for_k8s_version="v1.22" state="alpha" >}}
+
+<!--
+Memory QoS uses the memory controller of cgroup v2 to guarantee memory resources in Kubernetes.
+Memory requests and limits of containers in pod are used to set specific interfaces `memory.min`
+and `memory.high` provided by the memory controller. When `memory.min` is set to memory requests,
+memory resources are reserved and never reclaimed by the kernel; this is how Memory QoS ensures
+memory availability for Kubernetes pods. And if memory limits are set in the container,
+this means that the system needs to limit container memory usage; Memory QoS uses `memory.high`
+to throttle workload approaching its memory limit, ensuring that the system is not overwhelmed
+by instantaneous memory allocation.
+-->
+内存 QoS 使用 cgroup v2 的内存控制器来保证 Kubernetes 中的内存资源。
+Pod 中容器的内存请求和限制用于设置由内存控制器所提供的特定接口 `memory.min` 和 `memory.high`。
+当 `memory.min` 被设置为内存请求时，内存资源被保留并且永远不会被内核回收；
+这就是内存 QoS 确保 Kubernetes Pod 的内存可用性的方式。而如果容器中设置了内存限制，
+这意味着系统需要限制容器内存的使用；内存 QoS 使用 `memory.high` 来限制接近其内存限制的工作负载，
+确保系统不会因瞬时内存分配而不堪重负。
+
+<!--
+Memory QoS relies on QoS class to determine which settings to apply; however, these are different
+mechanisms that both provide controls over quality of service.
+-->
+内存 QoS 依赖于 QoS 类来确定应用哪些设置；它们的机制不同，但都提供对服务质量的控制。
+
 <!--
 ## Some behavior is independent of QoS class {#class-independent-behavior}
 
@@ -199,7 +229,7 @@ Certain behavior is independent of the QoS class assigned by Kubernetes. For exa
 * Learn about [resource management for Pods and Containers](/docs/concepts/configuration/manage-resources-containers/).
 * Learn about [Node-pressure eviction](/docs/concepts/scheduling-eviction/node-pressure-eviction/).
 * Learn about [Pod priority and preemption](/docs/concepts/scheduling-eviction/pod-priority-preemption/).
-* Learn about [Pod disruptions](/docs/concepts/workload/pods/disruptions/).
+* Learn about [Pod disruptions](/docs/concepts/workloads/pods/disruptions/).
 * Learn how to [assign memory resources to containers and pods](/docs/tasks/configure-pod-container/assign-memory-resource/).
 * Learn how to [assign CPU resources to containers and pods](/docs/tasks/configure-pod-container/assign-cpu-resource/).
 * Learn how to [configure Quality of Service for Pods](/docs/tasks/configure-pod-container/quality-service-pod/).

From ac0dd6ba06030858fd4e563a035571079c72024e Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Wed, 12 Apr 2023 17:11:31 +0800
Subject: [PATCH 171/272] sync dynamic-resource-allocation.md

sync dynamic-resource-allocation.md
---
 .../dynamic-resource-allocation.md            | 36 +++++++++++++------
 1 file changed, 25 insertions(+), 11 deletions(-)

diff --git a/content/zh-cn/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md b/content/zh-cn/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md
index e839068e04a..fe7ee05f975 100644
--- a/content/zh-cn/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md
+++ b/content/zh-cn/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md
@@ -14,7 +14,7 @@ weight: 65
 
 <!-- overview -->
 
-{{< feature-state for_k8s_version="v1.26" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.27" state="alpha" >}}
 
 <!-- 
 Dynamic resource allocation is a new API for requesting and sharing resources
@@ -48,10 +48,10 @@ Kubernetes v{{< skew currentVersion >}} 包含用于动态资源分配的集群
 
 ## API {#api}
 <!-- 
-The new `resource.k8s.io/v1alpha1` {{< glossary_tooltip text="API group"
+The `resource.k8s.io/v1alpha2` {{< glossary_tooltip text="API group"
 term_id="api-group" >}} provides four new types:
 -->
-新的 `resource.k8s.io/v1alpha1`
+`resource.k8s.io/v1alpha2`
 {{< glossary_tooltip text="API 组" term_id="api-group" >}}提供四种新类型：
 
 <!-- 
@@ -72,7 +72,7 @@ ResourceClaimTemplate
 : Defines the spec and some meta data for creating
   ResourceClaims. Created by a user when deploying a workload.
 
-PodScheduling
+PodSchedulingContext
 : Used internally by the control plane and resource drivers
   to coordinate pod scheduling when ResourceClaims need to be allocated
   for a Pod.
@@ -91,7 +91,7 @@ ResourceClaimTemplate
 : 定义用于创建 ResourceClaim 的 spec 和一些元数据。
   部署工作负载时由用户创建。
 
-PodScheduling
+PodSchedulingContext
 : 供控制平面和资源驱动程序内部使用，
   在需要为 Pod 分配 ResourceClaim 时协调 Pod 调度。
 
@@ -134,7 +134,7 @@ will get created for this Pod and each container gets access to one of them.
 该示例将为此 Pod 创建两个 ResourceClaim 对象，每个容器都可以访问其中一个。
 
 ```yaml
-apiVersion: resource.k8s.io/v1alpha1
+apiVersion: resource.k8s.io/v1alpha2
 kind: ResourceClass
 name: resource.example.com
 driverName: resource-driver.example.com
@@ -146,7 +146,7 @@ spec:
   color: black
   size: large
 ---
-apiVersion: resource.k8s.io/v1alpha1
+apiVersion: resource.k8s.io/v1alpha2
 kind: ResourceClaimTemplate
 metadata:
   name: large-black-cat-claim-template
@@ -252,6 +252,19 @@ set aside for it.
 这避免了 Pod 被调度到一个节点但无法在那里运行的情况，
 这种情况很糟糕，因为被挂起 Pod 也会阻塞为其保留的其他资源，如 RAM 或 CPU。
 
+<!-- 
+## Monitoring resources
+-->
+## 监控资源  {#monitoring-resources}
+
+<!-- 
+The kubelet provides a gRPC service to enable discovery of dynamic resources of
+running Pods. For more information on the gRPC endpoints, see the
+[resource allocation reporting](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#monitoring-device-plugin-resources).
+-->
+kubelet 提供了一个 gRPC 服务，以便发现正在运行的 Pod 的动态资源。
+有关 gRPC 端点的更多信息，请参阅[资源分配报告](/zh-cn/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#monitoring-device-plugin-resources)。
+
 <!-- 
 ## Limitations
 -->
@@ -279,7 +292,7 @@ future.
 Dynamic resource allocation is an *alpha feature* and only enabled when the
 `DynamicResourceAllocation` [feature
 gate](/docs/reference/command-line-tools-reference/feature-gates/) and the
-`resource.k8s.io/v1alpha1` {{< glossary_tooltip text="API group"
+`resource.k8s.io/v1alpha2` {{< glossary_tooltip text="API group"
 term_id="api-group" >}} are enabled. For details on that, see the
 `--feature-gates` and `--runtime-config` [kube-apiserver
 parameters](/docs/reference/command-line-tools-reference/kube-apiserver/).
@@ -322,10 +335,11 @@ error: the server doesn't have a resource type "resourceclasses"
 
 <!-- 
 The default configuration of kube-scheduler enables the "DynamicResources"
-plugin if and only if the feature gate is enabled. Custom configurations may
-have to be modified to include it.
+plugin if and only if the feature gate is enabled and when using
+the v1 configuration API. Custom configurations may have to be modified to
+include it.
 -->
-kube-scheduler 的默认配置仅在启用特性门控时才启用 "DynamicResources" 插件。
+kube-scheduler 的默认配置仅在启用特性门控且使用 v1 配置 API 时才启用 "DynamicResources" 插件。
 自定义配置可能需要被修改才能启用它。
 
 <!-- 

From 4a1f225b7e1d4eef43e28932db12f85a188421c3 Mon Sep 17 00:00:00 2001
From: Mengjiao Liu <mengjiao.liu@daocloud.io>
Date: Wed, 12 Apr 2023 17:22:01 +0800
Subject: [PATCH 172/272] [zh-cn] Remove the duplicate line in
 change-runtime-containerd.md

---
 .../migrating-from-dockershim/change-runtime-containerd.md       | 1 -
 1 file changed, 1 deletion(-)

diff --git a/content/zh-cn/docs/tasks/administer-cluster/migrating-from-dockershim/change-runtime-containerd.md b/content/zh-cn/docs/tasks/administer-cluster/migrating-from-dockershim/change-runtime-containerd.md
index 1052ba0d64d..d3e5a64fa08 100644
--- a/content/zh-cn/docs/tasks/administer-cluster/migrating-from-dockershim/change-runtime-containerd.md
+++ b/content/zh-cn/docs/tasks/administer-cluster/migrating-from-dockershim/change-runtime-containerd.md
@@ -172,7 +172,6 @@ Users using kubeadm should be aware that the `kubeadm` tool stores the CRI socke
 an annotation in the Node object for that host. To change it you can execute the following command
 on a machine that has the kubeadm `/etc/kubernetes/admin.conf` file.
 -->
-`kubeadm` 工具将每个主机的 CRI 套接字保存在该主机对应的 Node 对象的注解中。
 使用 `kubeadm` 的用户应该知道，`kubeadm` 工具将每个主机的 CRI 套接字保存在该主机对应的
 Node 对象的注解中。
 要更改这一注解信息，你可以在一台包含 kubeadm `/etc/kubernetes/admin.conf` 文件的机器上执行以下命令：

From 6b9bc4223306b3a33f26dc3dd2d9cb6c1c817703 Mon Sep 17 00:00:00 2001
From: xuzhenglun <xuzhenglun@gmail.com>
Date: Wed, 12 Apr 2023 19:15:26 +0800
Subject: [PATCH 173/272] fix typo for blog ServiceNodePortStaticSubrange

---
 .../_posts/2023-05-11-nodeport-dynamic-and-static-allocation.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/blog/_posts/2023-05-11-nodeport-dynamic-and-static-allocation.md b/content/en/blog/_posts/2023-05-11-nodeport-dynamic-and-static-allocation.md
index fde6ed1c1d5..78c2ca1d2fa 100644
--- a/content/en/blog/_posts/2023-05-11-nodeport-dynamic-and-static-allocation.md
+++ b/content/en/blog/_posts/2023-05-11-nodeport-dynamic-and-static-allocation.md
@@ -71,7 +71,7 @@ other Service; if so, creation of the `minio` Service will fail due to a node po
 ## How can you avoid NodePort Service port conflicts? 
 Kubernetes 1.24 introduced changes for `type: ClusterIP` Services, dividing the CIDR range for cluster
 IP addresses into two blocks that use different allocation policies to [reduce the risk of conflicts](/docs/reference/networking/virtual-ips/#avoiding-collisions).
-In Kubernetes 1.27, as an alpha feature, you can adopt a similar policy for `type: NodePort` Servies.
+In Kubernetes 1.27, as an alpha feature, you can adopt a similar policy for `type: NodePort` Services.
 You can enable a new [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
 `ServiceNodePortStaticSubrange`. Turning this on allows you to use a different port allocation strategy
 for `type: NodePort` Services, and reduce the risk of collision.

From c82cb982a0578d80eb5cbeeff1cd4cd7eb286138 Mon Sep 17 00:00:00 2001
From: James Harmison <jharmison@gmail.com>
Date: Wed, 12 Apr 2023 14:06:41 -0400
Subject: [PATCH 174/272] fix typo in blog post on 1.27 release

Kuberentes -> Kubernetes
---
 content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md b/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
index 128c03ceac4..def80c55e40 100644
--- a/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
+++ b/content/en/blog/_posts/2023-04-11-kubernetes-1.27-blog.md
@@ -91,7 +91,7 @@ A cluster administrator can try out this alpha feature across all nodes of their
 
 ## ReadWriteOncePod PersistentVolume access mode goes to beta 
 
-Kuberentes `v1.22` introduced a new access mode `ReadWriteOncePod` for [PersistentVolumes](/docs/concepts/storage/persistent-volumes/#persistent-volumes) (PVs) and [PersistentVolumeClaims](/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims) (PVCs). This access mode enables you to restrict volume access to a single pod in the cluster, ensuring that only one pod can write to the volume at a time. This can be particularly useful for stateful workloads that require single-writer access to storage.
+Kubernetes `v1.22` introduced a new access mode `ReadWriteOncePod` for [PersistentVolumes](/docs/concepts/storage/persistent-volumes/#persistent-volumes) (PVs) and [PersistentVolumeClaims](/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims) (PVCs). This access mode enables you to restrict volume access to a single pod in the cluster, ensuring that only one pod can write to the volume at a time. This can be particularly useful for stateful workloads that require single-writer access to storage.
 
 The ReadWriteOncePod beta adds support for [scheduler preemption](/docs/concepts/scheduling-eviction/pod-priority-preemption/)
 of pods that use ReadWriteOncePod PVCs.

From 555d454924bb968dd859d55e818bd19360fcd40e Mon Sep 17 00:00:00 2001
From: Arhell <arhell333@gmail.com>
Date: Thu, 13 Apr 2023 01:06:14 +0300
Subject: [PATCH 175/272] [es] Fix mismatch in Labels and Selectors concept
 page

---
 .../es/docs/concepts/overview/working-with-objects/labels.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/es/docs/concepts/overview/working-with-objects/labels.md b/content/es/docs/concepts/overview/working-with-objects/labels.md
index 7420aac5c6d..2b0954ff193 100644
--- a/content/es/docs/concepts/overview/working-with-objects/labels.md
+++ b/content/es/docs/concepts/overview/working-with-objects/labels.md
@@ -151,7 +151,7 @@ Como ya se ha comentado, los requisitos _basados en conjunto_ son más expresivo
 kubectl get pods -l 'environment in (production, qa)'
 ```
 
-o restringir la coincidencia negativa mediante el operador _exists_:
+o restringir la coincidencia negativa mediante el operador _notin_:
 
 ```shell
 kubectl get pods -l 'environment,environment notin (frontend)'

From 1499edaaf2923f97375bd5c37d941e696aca42d5 Mon Sep 17 00:00:00 2001
From: windsonsea <haifeng.yao@daocloud.io>
Date: Wed, 12 Apr 2023 15:57:18 +0800
Subject: [PATCH 176/272] [zh] sync 1.27 /concepts/architecture/nodes.md

---
 .../zh-cn/docs/concepts/architecture/nodes.md | 102 ++++++++----------
 1 file changed, 46 insertions(+), 56 deletions(-)

diff --git a/content/zh-cn/docs/concepts/architecture/nodes.md b/content/zh-cn/docs/concepts/architecture/nodes.md
index 655b017d9d3..e7c9c5a6adf 100644
--- a/content/zh-cn/docs/concepts/architecture/nodes.md
+++ b/content/zh-cn/docs/concepts/architecture/nodes.md
@@ -158,11 +158,6 @@ For self-registration, the kubelet is started with the following options:
   {{< glossary_tooltip text="taints" term_id="taint" >}} (comma separated `<key>=<value>:<effect>`).
 
   No-op if `register-node` is false.
-- `--node-ip` - IP address of the node.
-- `--node-labels` - {{< glossary_tooltip text="Labels" term_id="label" >}} to add when registering the node
-  in the cluster (see label restrictions enforced by the
-  [NodeRestriction admission plugin](/docs/reference/access-authn-authz/admission-controllers/#noderestriction)).
-- `--node-status-update-frequency` - Specifies how often kubelet posts its node status to the API server.
 -->
 - `--kubeconfig` - 用于向 API 服务器执行身份认证所用的凭据的路径。
 - `--cloud-provider` - 与某{{< glossary_tooltip text="云驱动" term_id="cloud-provider" >}}
@@ -170,7 +165,29 @@ For self-registration, the kubelet is started with the following options:
 - `--register-node` - 自动向 API 服务注册。
 - `--register-with-taints` - 使用所给的{{< glossary_tooltip text="污点" term_id="taint" >}}列表
   （逗号分隔的 `<key>=<value>:<effect>`）注册节点。当 `register-node` 为 false 时无效。
-- `--node-ip` - 节点 IP 地址。
+<!--
+- `--node-ip` - Optional comma-separated list of the IP addresses for the node.
+  You can only specify a single address for each address family.
+  For example, in a single-stack IPv4 cluster, you set this value to be the IPv4 address that the
+  kubelet should use for the node.
+  See [configure IPv4/IPv6 dual stack](/docs/concepts/services-networking/dual-stack/#configure-ipv4-ipv6-dual-stack)
+  for details of running a dual-stack cluster.
+
+  If you don't provide this argument, the kubelet uses the node's default IPv4 address, if any;
+  if the node has no IPv4 addresses then the kubelet uses the node's default IPv6 address.
+-->
+- `--node-ip` - 可选的以英文逗号隔开的节点 IP 地址列表。你只能为每个地址簇指定一个地址。
+  例如在单协议栈 IPv4 集群中，需要将此值设置为 kubelet 应使用的节点 IPv4 地址。
+  参阅[配置 IPv4/IPv6 双协议栈](/zh-cn/docs/concepts/services-networking/dual-stack/#configure-ipv4-ipv6-dual-stack)了解运行双协议栈集群的详情。
+
+  如果你未提供这个参数，kubelet 将使用节点默认的 IPv4 地址（如果有）；
+  如果节点没有 IPv4 地址，则 kubelet 使用节点的默认 IPv6 地址。
+<!--
+- `--node-labels` - {{< glossary_tooltip text="Labels" term_id="label" >}} to add when registering the node
+  in the cluster (see label restrictions enforced by the
+  [NodeRestriction admission plugin](/docs/reference/access-authn-authz/admission-controllers/#noderestriction)).
+- `--node-status-update-frequency` - Specifies how often kubelet posts its node status to the API server.
+-->
 - `--node-labels` - 在集群中注册节点时要添加的{{< glossary_tooltip text="标签" term_id="label" >}}。
   （参见 [NodeRestriction 准入控制插件](/zh-cn/docs/reference/access-authn-authz/admission-controllers/#noderestriction)所实施的标签限制）。
 - `--node-status-update-frequency` - 指定 kubelet 向 API 服务器发送其节点状态的频率。
@@ -389,66 +406,39 @@ of the Node resource. For example, the following JSON structure describes a heal
 ]
 ```
 
-<!--
-If the `status` of the Ready condition remains `Unknown` or `False` for longer
-than the `pod-eviction-timeout` (an argument passed to the
-{{< glossary_tooltip text="kube-controller-manager" term_id="kube-controller-manager"
->}}), then the [node controller](#node-controller) triggers
-{{< glossary_tooltip text="API-initiated eviction" term_id="api-eviction" >}}
-for all Pods assigned to that node. The default eviction timeout duration is
-**five minutes**.
--->
-如果 Ready 状况的 `status` 处于 `Unknown` 或者 `False` 状态的时间超过了
-`pod-eviction-timeout` 值（一个传递给
-{{< glossary_tooltip text="kube-controller-manager" term_id="kube-controller-manager" >}}
-的参数），[节点控制器](#node-controller)会对节点上的所有 Pod 触发
-{{< glossary_tooltip text="API 发起的驱逐" term_id="api-eviction" >}}。
-默认的逐出超时时长为 **5 分钟**。
-
-<!--
-In some cases when the node is unreachable, the API server is unable to communicate
-with the kubelet on the node. The decision to delete the pods cannot be communicated to
-the kubelet until communication with the API server is re-established. In the meantime,
-the pods that are scheduled for deletion may continue to run on the partitioned node.
--->
-某些情况下，当节点不可达时，API 服务器不能和其上的 kubelet 通信。
-删除 Pod 的决定不能传达给 kubelet，直到它重新建立和 API 服务器的连接为止。
-与此同时，被计划删除的 Pod 可能会继续在游离的节点上运行。
-
-<!--
-The node controller does not force delete pods until it is confirmed that they have stopped
-running in the cluster. You can see the pods that might be running on an unreachable node as
-being in the `Terminating` or `Unknown` state. In cases where Kubernetes cannot deduce from the
-underlying infrastructure if a node has permanently left a cluster, the cluster administrator
-may need to delete the node object by hand. Deleting the node object from Kubernetes causes
-all the Pod objects running on the node to be deleted from the API server and frees up their
-names.
--->
-节点控制器在确认 Pod 在集群中已经停止运行前，不会强制删除它们。
-你可以看到可能在这些无法访问的节点上运行的 Pod 处于 `Terminating` 或者 `Unknown` 状态。
-如果 Kubernetes 不能基于下层基础设施推断出某节点是否已经永久离开了集群，
-集群管理员可能需要手动删除该节点对象。
-从 Kubernetes 删除节点对象将导致 API 服务器删除节点上所有运行的 Pod 对象并释放它们的名字。
-
 <!--
 When problems occur on nodes, the Kubernetes control plane automatically creates
 [taints](/docs/concepts/scheduling-eviction/taint-and-toleration/) that match the conditions
-affecting the node.
-The scheduler takes the Node's taints into consideration when assigning a Pod to a Node.
-Pods can also have {{< glossary_tooltip text="tolerations" term_id="toleration" >}} that let
-them run on a Node even though it has a specific taint.
+affecting the node.  An example of this is when the `status` of the Ready condition
+remains `Unknown` or `False` for longer than the kube-controller-manager's `NodeMonitorGracePeriod`,
+which defaults to 40 seconds.  This will cause either an `node.kubernetes.io/unreachable` taint, for an `Unknown` status,
+or a `node.kubernetes.io/not-ready` taint, for a `False` status, to be added to the Node.
 -->
 当节点上出现问题时，Kubernetes 控制面会自动创建与影响节点的状况对应的
 [污点](/zh-cn/docs/concepts/scheduling-eviction/taint-and-toleration/)。
-调度器在将 Pod 指派到某 Node 时会考虑 Node 上的污点设置。
-Pod 也可以设置{{< glossary_tooltip text="容忍度" term_id="toleration" >}}，
-以便能够在设置了特定污点的 Node 上运行。
+例如当 Ready 状况的 `status` 保持 `Unknown` 或 `False` 的时间长于
+kube-controller-manager 的 `NodeMonitorGracePeriod`（默认为 40 秒）时，
+会造成 `Unknown` 状态下为节点添加 `node.kubernetes.io/unreachable` 污点或在
+`False` 状态下为节点添加 `node.kubernetes.io/not-ready` 污点。
 
 <!--
-See [Taint Nodes by Condition](/docs/concepts/scheduling-eviction/taint-and-toleration/#taint-nodes-by-condition)
+These taints affect pending pods as the scheduler takes the Node's taints into consideration when
+assigning a pod to a Node. Existing pods scheduled to the node may be evicted due to the application
+of `NoExecute` taints. Pods may also have {{< glossary_tooltip text="tolerations" term_id="toleration" >}} that let
+them schedule to and continue running on a Node even though it has a specific taint.
+-->
+这些污点会影响悬决的 Pod，因为调度器在将 Pod 分配到 Node 时会考虑 Node 的污点。
+已调度到节点的当前 Pod 可能会由于施加的 `NoExecute` 污点被驱逐。
+Pod 还可以设置{{< glossary_tooltip text="容忍度" term_id="toleration" >}}，
+使得这些 Pod 仍然能够调度到且继续运行在设置了特定污点的 Node 上。
+
+<!--
+See [Taint Based Evictions](/docs/concepts/scheduling-eviction/taint-and-toleration/#taint-based-evictions) and
+[Taint Nodes by Condition](/docs/concepts/scheduling-eviction/taint-and-toleration/#taint-nodes-by-condition)
 for more details.
 -->
-进一步的细节可参阅[根据状况为节点设置污点](/zh-cn/docs/concepts/scheduling-eviction/taint-and-toleration/#taint-nodes-by-condition)。
+进一步的细节可参阅[基于污点的驱逐](/zh-cn/docs/concepts/scheduling-eviction/taint-and-toleration/#taint-based-evictions)
+和[根据状况为节点设置污点](/zh-cn/docs/concepts/scheduling-eviction/taint-and-toleration/#taint-nodes-by-condition)。
 
 <!--
 ### Capacity and Allocatable {#capacity}

From e5c5374b9f2f8d01899878282718da662144efd2 Mon Sep 17 00:00:00 2001
From: windsonsea <haifeng.yao@daocloud.io>
Date: Wed, 12 Apr 2023 17:42:01 +0800
Subject: [PATCH 177/272] [zh] sync 1.27 system-traces.md

---
 .../cluster-administration/system-traces.md   | 108 +++++++++++++-----
 1 file changed, 82 insertions(+), 26 deletions(-)

diff --git a/content/zh-cn/docs/concepts/cluster-administration/system-traces.md b/content/zh-cn/docs/concepts/cluster-administration/system-traces.md
index d313716a210..56a4373bf06 100644
--- a/content/zh-cn/docs/concepts/cluster-administration/system-traces.md
+++ b/content/zh-cn/docs/concepts/cluster-administration/system-traces.md
@@ -14,7 +14,7 @@ weight: 90
 
 <!-- overview -->
 
-{{< feature-state for_k8s_version="v1.22" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
 
 <!-- 
 System component traces record the latency of and relationships between operations in the cluster.
@@ -57,10 +57,25 @@ the following receiver configuration will collect spans and log them to standard
 -->
 默认情况下，Kubernetes 组件使用 gRPC 的 OTLP 导出器来导出追踪信息，将信息写到
 [IANA OpenTelemetry 端口](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=opentelemetry)。
-举例来说，如果收集器以 Kubernetes 组件的边车模式运行，以下接收器配置会收集 span 信息，并将它们写入到标准输出。
+举例来说，如果收集器以 Kubernetes 组件的边车模式运行，
+以下接收器配置会收集 span 信息，并将它们写入到标准输出。
 
 <!-- 
-# Replace this exporter with the exporter for your backend
+```yaml
+receivers:
+  otlp:
+    protocols:
+      grpc:
+exporters:
+  # Replace this exporter with the exporter for your backend
+  logging:
+    logLevel: debug
+service:
+  pipelines:
+    traces:
+      receivers: [otlp]
+      exporters: [logging]
+```
 -->
 ```yaml
 receivers:
@@ -105,38 +120,43 @@ kube-apiserver 为传入的 HTTP 请求、传出到 webhook 和 etcd 的请求
 #### 在 kube-apiserver 中启用追踪 {#enabling-tracing-in-the-kube-apiserver}
 
 <!-- 
-To enable tracing, enable the `APIServerTracing`
-[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
-on the kube-apiserver. Also, provide the kube-apiserver with a tracing configuration file
+To enable tracing, provide the kube-apiserver with a tracing configuration file
 with `--tracing-config-file=<path-to-config>`. This is an example config that records
 spans for 1 in 10000 requests, and uses the default OpenTelemetry endpoint:
--->
-要启用追踪特性，需要启用 kube-apiserver 上的  `APIServerTracing`
-[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)。
-然后，使用 `--tracing-config-file=<<配置文件路径>` 为 kube-apiserver 提供追踪配置文件。
-下面是一个示例配置，它为万分之一的请求记录 spans，并使用了默认的 OpenTelemetry 端口。
 
 ```yaml
-apiVersion: apiserver.config.k8s.io/v1alpha1
+apiVersion: apiserver.config.k8s.io/v1beta1
 kind: TracingConfiguration
 # default value
 #endpoint: localhost:4317
 samplingRatePerMillion: 100
 ```
+-->
+要启用追踪特性，需要使用 `--tracing-config-file=<<配置文件路径>` 为
+kube-apiserver 提供追踪配置文件。下面是一个示例配置，它为万分之一的请求记录
+span，并使用了默认的 OpenTelemetry 端点。
+
+```yaml
+apiVersion: apiserver.config.k8s.io/v1beta1
+kind: TracingConfiguration
+# 默认值
+#endpoint: localhost:4317
+samplingRatePerMillion: 100
+```
 
 <!-- 
 For more information about the `TracingConfiguration` struct, see
-[API server config API (v1alpha1)](/docs/reference/config-api/apiserver-config.v1alpha1/#apiserver-k8s-io-v1alpha1-TracingConfiguration).
+[API server config API (v1beta1)](/docs/reference/config-api/apiserver-config.v1beta1/#apiserver-k8s-io-v1beta1-TracingConfiguration).
 -->
 有关 TracingConfiguration 结构体的更多信息，请参阅
-[API 服务器配置 API (v1alpha1)](/zh-cn/docs/reference/config-api/apiserver-config.v1alpha1/#apiserver-k8s-io-v1alpha1-TracingConfiguration)。
+[API 服务器配置 API (v1beta1)](/zh-cn/docs/reference/config-api/apiserver-config.v1beta1/#apiserver-k8s-io-v1beta1-TracingConfiguration)。
 
 <!--
 ### kubelet traces
 -->
-### kubelet 追踪 {#kubelet-traces}
+### kubelet 追踪   {#kubelet-traces}
 
-{{< feature-state for_k8s_version="v1.25" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
 
 <!--
 The kubelet CRI interface and authenticated http servers are instrumented to generate
@@ -149,23 +169,31 @@ kubelet CRI 接口和实施身份验证的 HTTP 服务器被插桩以生成追
 与 API 服务器一样，端点和采样率是可配置的。
 追踪上下文传播也是可以配置的。始终优先采用父 span 的采样决策。
 用户所提供的追踪配置采样率将被应用到不带父级的 span。
-如果在没有配置端点的情况下启用，将使用默认的 OpenTelemetry Collector 接收器地址 “localhost:4317”。
+如果在没有配置端点的情况下启用，将使用默认的 OpenTelemetry Collector
+接收器地址 “localhost:4317”。
 
 <!--
 #### Enabling tracing in the kubelet
 
-To enable tracing, enable the `KubeletTracing`
-[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
-on the kubelet. Also, provide the kubelet with a
-[tracing configuration](https://github.com/kubernetes/component-base/blob/release-1.25/tracing/api/v1/types.go).
+To enable tracing, apply the [tracing configuration](https://github.com/kubernetes/component-base/blob/release-1.27/tracing/api/v1/types.go).
 This is an example snippet of a kubelet config that records spans for 1 in 10000 requests, and uses the default OpenTelemetry endpoint:
+
+```yaml
+apiVersion: kubelet.config.k8s.io/v1beta1
+kind: KubeletConfiguration
+featureGates:
+  KubeletTracing: true
+tracing:
+  # default value
+  #endpoint: localhost:4317
+  samplingRatePerMillion: 100
+```
 -->
 #### 在 kubelet 中启用追踪 {#enabling-tracing-in-the-kubelet}
 
-要启用 span，需在 kubelet 上启用 `KubeletTracing`
-[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)。
-另外，为 kubelet 提供[追踪配置](https://github.com/kubernetes/component-base/blob/release-1.25/tracing/api/v1/types.go)。
-以下是 kubelet 配置的示例代码片段，每 10000 个请求中记录一个请求的 span，并使用默认的 OpenTelemetry 端点：
+要启用追踪，需应用[追踪配置](https://github.com/kubernetes/component-base/blob/release-1.27/tracing/api/v1/types.go)。
+以下是 kubelet 配置的示例代码片段，每 10000 个请求中记录一个请求的
+span，并使用默认的 OpenTelemetry 端点：
 
 ```yaml
 apiVersion: kubelet.config.k8s.io/v1beta1
@@ -178,6 +206,34 @@ tracing:
   samplingRatePerMillion: 100
 ```
 
+<!--
+If the `samplingRatePerMillion` is set to one million (`1000000`), then every
+span will be sent to the exporter.
+-->
+如果 `samplingRatePerMillion` 被设置为一百万 (`1000000`)，则所有 span 都将被发送到导出器。
+
+<!--
+The kubelet in Kubernetes v{{< skew currentVersion >}} collects spans from
+the garbage collection, pod synchronization routine as well as every gRPC
+method. Connected container runtimes like CRI-O and containerd can link the
+traces to their exported spans to provide additional context of information.
+-->
+Kubernetes v{{< skew currentVersion >}} 中的 kubelet 从垃圾回收、Pod
+同步例程以及每个 gRPC 方法中收集 span。CRI-O 和 containerd
+这类关联的容器运行时可以将链路链接到其导出的 span，以提供更多上下文信息。
+
+<!--
+Please note that exporting spans always comes with a small performance overhead
+on the networking and CPU side, depending on the overall configuration of the
+system. If there is any issue like that in a cluster which is running with
+tracing enabled, then mitigate the problem by either reducing the
+`samplingRatePerMillion` or disabling tracing completely by removing the
+configuration.
+-->
+请注意导出 span 始终会对网络和 CPU 产生少量性能开销，具体取决于系统的总体配置。
+如果在启用追踪的集群中出现类似性能问题，可以通过降低 `samplingRatePerMillion`
+或通过移除此配置来彻底禁用追踪来缓解问题。
+
 <!-- 
 ## Stability
 -->
@@ -198,4 +254,4 @@ there are no guarantees of backwards compatibility for tracing instrumentation.
 <!-- 
 * Read about [Getting Started with the OpenTelemetry Collector](https://opentelemetry.io/docs/collector/getting-started/)
 -->
-* 阅读[Getting Started with the OpenTelemetry Collector](https://opentelemetry.io/docs/collector/getting-started/)
+* 阅读 [Getting Started with the OpenTelemetry Collector](https://opentelemetry.io/docs/collector/getting-started/)

From 29856082897c1d78c14e8240666167699558fb28 Mon Sep 17 00:00:00 2001
From: ystkfujii <ystk.fujii0731@gmail.com>
Date: Sat, 11 Mar 2023 17:34:29 +0900
Subject: [PATCH 178/272] Translate blog:forensic-container-analysis into ja

---
 .../index.md                                  | 315 ++++++++++++++++++
 1 file changed, 315 insertions(+)
 create mode 100644 content/ja/blog/_posts/2023-03-10-forensic-container-analysis/index.md

diff --git a/content/ja/blog/_posts/2023-03-10-forensic-container-analysis/index.md b/content/ja/blog/_posts/2023-03-10-forensic-container-analysis/index.md
new file mode 100644
index 00000000000..a78cd333332
--- /dev/null
+++ b/content/ja/blog/_posts/2023-03-10-forensic-container-analysis/index.md
@@ -0,0 +1,315 @@
+---
+layout: blog
+title: "フォレンジックコンテナ分析"
+date: 2023-03-10
+slug: forensic-container-analysis
+---
+
+**Authors:** Adrian Reber (Red Hat)
+
+前回投稿した[Kubernetesにおけるフォレンジックコンテナチェックポイント処理][forensic-blog]では、Kubernetesでのチェックポイントの作成や、それがどのようにセットアップされ、どのように使用されるのかを紹介しました。
+機能の名前はフォレンジックコンテナチェックポイントですが、Kubernetesによって作成されたチェックポイントの実際の分析方法については、詳細を説明しませんでした。
+この記事では、チェックポイントがどのように分析されるのかについての詳細を提供します。
+
+チェックポイントの作成はまだKubernetesでalpha機能であり、この記事ではその機能が将来どのように動作するのかについてのプレビューを提供します。
+
+## 準備
+
+チェックポイント作成のサポートを有効にするためのKubernetesの設定方法や、基盤となるCRI実装方法についての詳細は[Kubernetesにおけるフォレンジックコンテナチェックポイント処理][forensic-blog]を参照してください。
+
+一例として、この記事内でチェックポイントを作成し分析するコンテナイメージ(`quay.io/adrianreber/counter:blog`)を準備しました。
+このコンテナはコンテナ内でファイルを作成することができ、後でチェックポイント内で探したい情報をメモリーに格納しておくこともできます。
+
+コンテナを実行するためにはPodが必要であり、この例では下記のPodマニフェストを使用します。
+
+```yaml
+apiVersion: v1
+kind: Pod
+metadata:
+  name: counters
+spec:
+  containers:
+  - name: counter
+    image: quay.io/adrianreber/counter:blog
+```
+
+この結果、`counter`と呼ばれるコンテナが`counters`と呼ばれるPod内で実行されます。
+
+一度コンテナが実行されると、コンテナで下記アクションが行えます。
+
+```console
+$ kubectl get pod counters --template '{{.status.podIP}}'
+10.88.0.25
+$ curl 10.88.0.25:8088/create?test-file
+$ curl 10.88.0.25:8088/secret?RANDOM_1432_KEY
+$ curl 10.88.0.25:8088
+```
+
+最初のアクセスはコンテナ内で`test-file`という内容で`test-file`と呼ばれるファイルを作成します。
+次のアクセスで、コンテナのメモリー内のどこかにシークレット情報(`RANDOM_1432_KEY`)を記憶します。
+最後のアクセスは内部のログファイルに1行追加するだけです。
+
+チェックポイントを分析する前の最後のステップは、チェックポイントを作成することをKubernetesに指示することです。
+前回の記事で説明したように、これには*kubelet*限定の`チェックポイント`APIエンドポイントへのアクセスを必要とします。
+
+*default*名前空間内の*counters*という名前のPod内の*counter*という名前のコンテナに対して、*kubelet* APIエンドポイントが次の場所で到達可能です。
+```shell
+# Podが実行されているNode上で実行する
+curl -X POST "https://localhost:10250/checkpoint/default/counters/counter"
+```
+
+厳密には、*kubelet*の自己署名証明書を許容し*kubelet* `チェックポイント`APIの使用を認可するために、下記の`curl`コマンドのオプションが必要です。
+
+```shell
+--insecure --cert /var/run/kubernetes/client-admin.crt --key /var/run/kubernetes/client-admin.key
+```
+
+チェックポイントの作成が終了すると、`/var/lib/kubelet/checkpoints/checkpoint-<pod-name>_<namespace-name>-<container-name>-<timestamp>.tar`でチェックポイントが利用可能になります。
+
+この記事の後述のステップでは、チェックポイントアーカイブを分析する際に`checkpoint.tar`という名前を使用します。
+
+## `checkpointctl`を使用したチェックポイントアーカイブの分析
+
+チェックポイントが作成したコンテナに関するいくつかの初期情報を得るためには、このように[checkpointctl][checkpointctl]を使用します。
+
+```console
+$ checkpointctl show checkpoint.tar --print-stats
++-----------+----------------------------------+--------------+---------+---------------------+--------+------------+------------+-------------------+
+| CONTAINER |              IMAGE               |      ID      | RUNTIME |       CREATED       | ENGINE |     IP     | CHKPT SIZE | ROOT FS DIFF SIZE |
++-----------+----------------------------------+--------------+---------+---------------------+--------+------------+------------+-------------------+
+| counter   | quay.io/adrianreber/counter:blog | 059a219a22e5 | runc    | 2023-03-02T06:06:49 | CRI-O  | 10.88.0.23 | 8.6 MiB    | 3.0 KiB           |
++-----------+----------------------------------+--------------+---------+---------------------+--------+------------+------------+-------------------+
+CRIU dump statistics
++---------------+-------------+--------------+---------------+---------------+---------------+
+| FREEZING TIME | FROZEN TIME | MEMDUMP TIME | MEMWRITE TIME | PAGES SCANNED | PAGES WRITTEN |
++---------------+-------------+--------------+---------------+---------------+---------------+
+| 100809 us     | 119627 us   | 11602 us     | 7379 us       |          7800 |          2198 |
++---------------+-------------+--------------+---------------+---------------+---------------+
+```
+
+これによって、チェックポイントアーカイブ内のチェックポイントについてのいくつかの情報が、すでに取得できています。
+コンテナの名前やコンテナランタイムやコンテナエンジンについての情報を見ることができます。
+チェックポイントのサイズ(`CHKPT SIZE`)もリスト化されます。
+これは大部分がチェックポイントに含まれるメモリーページのサイズですが、コンテナ内の全ての変更されたファイルのサイズ(`ROOT FS DIFF SIZE`)についての情報もあります。
+
+追加のパラメーター`--print-stats`はチェックポイントアーカイブ内の情報を復号化し、2番目のテーブル(*CRIU dump statistics*)で表示します。
+この情報はチェックポイント作成中に収集され、CRIUがコンテナ内のプロセスをチェックポイントするために必要な時間と、チェックポイント作成中に分析され書き込まれたメモリーページ数の概要を示します。
+
+## より深く掘り下げる
+
+`checkpointctl`の助けを借りて、チェックポイントアーカイブについてのハイレベルな情報を得ることができます。
+チェックポイントアーカイブをさらに分析するには、それを展開する必要があります。
+チェックポイントアーカイブは*tar*アーカイブであり、`tar xf checkpoint.tar`の助けを借りて展開可能です。
+
+チェックポイントアーカイブを展開すると、下記のファイルやディレクトリが作成されます。
+
+* `bind.mounts` - このファイルにはバインドマウントについての情報が含まれており、復元中に全ての外部ファイルとディレクトリを正しい場所にマウントするために必要になります。
+* `checkpoint/` - このディレクトリにはCRIUによって作成された実際のチェックポイントが含まれています。
+* `config.dump`と`spec.dump` - これらのファイルには、復元中に必要とされるコンテナについてのメタデータが含まれています。
+* `dump.log` - このファイルにはチェックポイント作成中に作成されたCRIUのデバッグ出力が含まれています。
+* `stats-dump` - このファイルには、`checkpointctl`が`--print-stats`でダンプ統計情報を表示するために使用するデータが含まれています。
+* `rootfs-diff.tar` - このファイルには、コンテナのファイルシステム上で変更された全てのファイルが含まれています。
+
+### ファイルシステムの変更 - `rootfs-diff.tar`
+
+コンテナのチェックポイントをさらに分析するための最初のステップは、コンテナ内で変更されたファイルを見ることです。
+これは`rootfs-diff.tar`ファイルを参照することで行えます。
+
+```console
+$ tar xvf rootfs-diff.tar
+home/counter/logfile
+home/counter/test-file
+```
+
+これでコンテナ内で変更されたファイルを調べられます。
+
+```console
+$ cat home/counter/logfile
+10.88.0.1 - - [02/Mar/2023 06:07:29] "GET /create?test-file HTTP/1.1" 200 -
+10.88.0.1 - - [02/Mar/2023 06:07:40] "GET /secret?RANDOM_1432_KEY HTTP/1.1" 200 -
+10.88.0.1 - - [02/Mar/2023 06:07:43] "GET / HTTP/1.1" 200 -
+$ cat home/counter/test-file
+test-file 
+```
+
+このコンテナのベースになっているコンテナイメージ(`quay.io/adrianreber/counter:blog`)と比較すると、コンテナが提供するサービスへの全てのアクセス情報を含んだ`logfile`や予想通り作成された`test-file`ファイルを確認することができます。
+
+`rootfs-diff.tar`の助けを借りることで、作成または変更された全てのファイルを、コンテナのベースイメージと比較して検査することが可能です。
+
+### チェックポイント処理したプロセスを分析する - `checkpoint/`
+
+ディレクトリ`checkpoint/`はコンテナ内でプロセスをチェックポイントしている間にCRIUによって作成されたデータを含んでいます。
+ディレクトリ`checkpoint/`の内容は、CRIUの一部として配布されている[CRIT][crit]ツールを使用して分析できるさまざまな[イメージファイル][image-files]で構成されています。
+
+まず、コンテナの内部プロセスの概要を取得してみましょう。
+
+```console
+$ crit show checkpoint/pstree.img | jq .entries[].pid
+1
+7
+8
+```
+
+この出力はコンテナのPID名前空間の内部に3つのプロセス(PIDが1と7と8)があることを意味しています。
+
+これはコンテナのPID名前空間の内部からの視界を表示しているだけです。
+復元中に正確にそれらのPIDが再作成されます。
+コンテナのPID名前空間の外部からPIDは復元後に変更されます。
+
+次のステップは、それらの3つのプロセスについての追加情報を取得することです。
+
+```console
+$ crit show checkpoint/core-1.img | jq .entries[0].tc.comm
+"bash"
+$ crit show checkpoint/core-7.img | jq .entries[0].tc.comm
+"counter.py"
+$ crit show checkpoint/core-8.img | jq .entries[0].tc.comm
+"tee"
+```
+
+これは、コンテナ内の3つのプロセスが`bash`と`counter.py`(Pythonインタプリター)と`tee`であることを意味しています。
+プロセスの親子関係についての詳細は、`checkpoint/pstree.img`に分析するデータがさらにあります。
+
+ここまでで収集した情報をまだ実行中のコンテナと比較してみましょう。
+
+```console
+$ crictl inspect --output go-template --template "{{(index .info.pid)}}" 059a219a22e56
+722520
+$ ps auxf | grep -A 2 722520
+fedora    722520  \_ bash -c /home/counter/counter.py 2>&1 | tee /home/counter/logfile
+fedora    722541      \_ /usr/bin/python3 /home/counter/counter.py
+fedora    722542      \_ /usr/bin/coreutils --coreutils-prog-shebang=tee /usr/bin/tee /home/counter/logfile
+$ cat /proc/722520/comm
+bash
+$ cat /proc/722541/comm
+counter.py
+$ cat /proc/722542/comm
+tee
+```
+
+この出力では、まずコンテナ内の最初のプロセスのPIDを取得しています。
+そしてコンテナを実行しているシステム上で、そのPIDと子プロセスを探しています。
+3つのプロセスが表示され、最初のものはコンテナPID名前空間の中でPID 1である"bash"です。
+次に`/proc/<PID>/comm`を見ると、チェックポイントイメージと正確に同じ値を見つけることができます。
+
+覚えておく重要なことは、チェックポイントはコンテナのPID名前空間内の視界が含まれていることです。
+なぜなら、これらの情報はプロセスを復元するために重要だからです。
+
+`crit`がコンテナについて教えてくれる最後の例は、UTS名前空間に関する情報です。
+
+```console
+$ crit show checkpoint/utsns-12.img
+{
+    "magic": "UTSNS",
+    "entries": [
+        {
+            "nodename": "counters",
+            "domainname": "(none)"
+        }
+    ]
+}
+```
+
+UTS名前空間内のホストネームが`counters`であることを教えてくれます。
+
+チェックポイント作成中に収集された各リソースCRIUについて、`checkpoint/`ディレクトリは対応するイメージファイルを含んでいます。
+このイメージファイルは`crit`を使用することで分析可能です。
+
+#### メモリーページを見る
+
+CRITを使用して復号化できるCRIUからの情報に加えて、CRIUがディスクに書き込んだ生のメモリーページを含んでいるファイルもあります。
+
+```console
+$ ls  checkpoint/pages-*
+checkpoint/pages-1.img  checkpoint/pages-2.img  checkpoint/pages-3.img
+```
+
+最初にコンテナを使用した際に、メモリー内のどこかにランダムキー(`RANDOM_1432_KEY`)を保存しました。
+見つけることができるかどうか見てみましょう。
+
+```console
+$ grep -ao RANDOM_1432_KEY checkpoint/pages-*
+checkpoint/pages-2.img:RANDOM_1432_KEY
+```
+
+そして実際に、私のデータがあります。
+この方法で、コンテナ内のプロセスの全てのメモリーページの内容を簡単に見ることができます。
+しかし、チェックポイントアーカイブにアクセスできるなら誰でも、コンテナのプロセスのメモリー内に保存された全ての情報にアクセスできることを覚えておくことも重要です。
+
+#### さらなる分析のためにgdbを使用する
+
+チェックポイントイメージを見るための他の方法は`gdb`です。
+CRIUリポジトリは、チェックポイントをコアダンプファイルに変換する[coredump][criu-coredump]スクリプトを含んでいます。
+
+```console
+$ /home/criu/coredump/coredump-python3
+$ ls -al core*
+core.1  core.7  core.8
+```
+
+`coredump-python3`スクリプトを実行すると、チェックポイントイメージがコンテナ内の各プロセスに対し1つのコアダンプファイルに変換されます。
+`gdb`を使用してプロセスの詳細を見ることもできます。
+
+```console
+$ echo info registers | gdb --core checkpoint/core.1 -q
+
+[New LWP 1]
+
+Core was generated by `bash -c /home/counter/counter.py 2>&1 | tee /home/counter/logfile'.
+
+#0  0x00007fefba110198 in ?? ()
+(gdb)
+rax            0x3d                61
+rbx            0x8                 8
+rcx            0x7fefba11019a      140667595587994
+rdx            0x0                 0
+rsi            0x7fffed9c1110      140737179816208
+rdi            0xffffffff          4294967295
+rbp            0x1                 0x1
+rsp            0x7fffed9c10e8      0x7fffed9c10e8
+r8             0x1                 1
+r9             0x0                 0
+r10            0x0                 0
+r11            0x246               582
+r12            0x0                 0
+r13            0x7fffed9c1170      140737179816304
+r14            0x0                 0
+r15            0x0                 0
+rip            0x7fefba110198      0x7fefba110198
+eflags         0x246               [ PF ZF IF ]
+cs             0x33                51
+ss             0x2b                43
+ds             0x0                 0
+es             0x0                 0
+fs             0x0                 0
+gs             0x0                 0
+```
+
+この例では、チェックポイント中の全てのレジストリの値を見ることができ、コンテナのPID 1のプロセスの完全なコマンドライン(`bash -c /home/counter/counter.py 2>&1 | tee /home/counter/logfile`)を見ることもできます。
+
+## まとめ
+
+コンテナチェックポイントを作成することで、コンテナを停止することやチェックポイントが作成されたことを知ることなく、実行中のコンテナのチェックポイントを作成することが可能です。
+Kubernetesにおいてコンテナのチェックポイントを作成した結果がチェックポイントアーカイブです。
+`checkpointctl`や`tar`、`crit`、`gdb`のような異なるツールを使用して、チェックポイントを分析できます。
+`grep`のようなシンプルなツールでさえ、チェックポイントアーカイブ内の情報を見つけることが可能です。
+
+この記事で示したチェックポイントの分析方法のさまざまな例は出発点にすぎません。
+この記事ではチェックポイントの分析を始める方法を紹介しましたが、要件によってはかなり詳細に特定の物事を見ることも可能です。
+
+## 参加するためにはどうすればよいですか？
+
+SIG Nodeにはいくつかの方法でアクセスできます。
+
+* Slack: [#sig-node][slack-sig-node]
+* Slack: [#sig-security][slack-sig-security]
+* [メーリングリスト][sig-node-ml]
+
+[forensic-blog]: https://kubernetes.io/ja/blog/2022/12/05/forensic-container-checkpointing-alpha/
+[checkpointctl]: https://github.com/checkpoint-restore/checkpointctl
+[image-files]: https://criu.org/Images
+[crit]: https://criu.org/CRIT
+[slack-sig-node]: https://kubernetes.slack.com/messages/sig-node
+[slack-sig-security]: https://kubernetes.slack.com/messages/sig-security
+[sig-node-ml]: https://groups.google.com/forum/#!forum/kubernetes-sig-node
+[criu-coredump]: https://github.com/checkpoint-restore/criu/tree/criu-dev/coredump

From c0c46070979e69ac16ea551f9f7d42fb455be511 Mon Sep 17 00:00:00 2001
From: windsonsea <haifeng.yao@daocloud.io>
Date: Thu, 13 Apr 2023 09:46:22 +0800
Subject: [PATCH 179/272] [zh] sync 1.27 device-plugins.md

---
 .../compute-storage-net/device-plugins.md     | 173 +++++++++++++++++-
 1 file changed, 172 insertions(+), 1 deletion(-)

diff --git a/content/zh-cn/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md b/content/zh-cn/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md
index 2b0a54b4e2d..cd03b2d62b0 100644
--- a/content/zh-cn/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md
+++ b/content/zh-cn/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md
@@ -371,6 +371,16 @@ identifying containers using `pod`, `namespace`, and `container` prometheus labe
 <!--
 The kubelet provides a gRPC service to enable discovery of in-use devices, and to provide metadata
 for these devices:
+
+```gRPC
+// PodResourcesLister is a service provided by the kubelet that provides information about the
+// node resources consumed by pods and containers on the node
+service PodResourcesLister {
+    rpc List(ListPodResourcesRequest) returns (ListPodResourcesResponse) {}
+    rpc GetAllocatableResources(AllocatableResourcesRequest) returns (AllocatableResourcesResponse) {}
+    rpc Get(GetPodResourcesRequest) returns (GetPodResourcesResponse) {}
+}
+```
 -->
 kubelet 提供了 gRPC 服务来使得正在使用中的设备被发现，并且还为这些设备提供了元数据：
 
@@ -380,6 +390,7 @@ kubelet 提供了 gRPC 服务来使得正在使用中的设备被发现，并且
 service PodResourcesLister {
     rpc List(ListPodResourcesRequest) returns (ListPodResourcesResponse) {}
     rpc GetAllocatableResources(AllocatableResourcesRequest) returns (AllocatableResourcesResponse) {}
+    rpc Get(GetPodResourcesRequest) returns (GetPodResourcesResponse) {}
 }
 ```
 
@@ -398,6 +409,89 @@ information about memory and hugepages reserved for a container.
 CPU ID、设备插件所报告的设备 ID 以及这些设备分配所处的 NUMA 节点 ID。
 此外，对于基于 NUMA 的机器，它还会包含为容器保留的内存和大页的信息。
 
+<!--
+Starting from Kubernetes v1.27, the `List` enpoint can provide information on resources
+of running pods allocated in `ResourceClaims` by the `DynamicResourceAllocation` API. To enable
+this feature `kubelet` must be started with the following flags:
+-->
+从 Kubernetes v1.27 开始，`List` 端点可以通过 `DynamicResourceAllocation` API 提供在
+`ResourceClaims` 中分配的当前运行 Pod 的资源信息。
+要启用此特性，必须使用以下标志启动 `kubelet`：
+
+```
+--feature-gates=DynamicResourceAllocation=true,KubeletPodResourcesDynamiceResources=true
+```
+
+<!--
+```gRPC
+// ListPodResourcesResponse is the response returned by List function
+message ListPodResourcesResponse {
+    repeated PodResources pod_resources = 1;
+}
+
+// PodResources contains information about the node resources assigned to a pod
+message PodResources {
+    string name = 1;
+    string namespace = 2;
+    repeated ContainerResources containers = 3;
+}
+
+// ContainerResources contains information about the resources assigned to a container
+message ContainerResources {
+    string name = 1;
+    repeated ContainerDevices devices = 2;
+    repeated int64 cpu_ids = 3;
+    repeated ContainerMemory memory = 4;
+    repeated DynamicResource dynamic_resources = 5;
+}
+
+// ContainerMemory contains information about memory and hugepages assigned to a container
+message ContainerMemory {
+    string memory_type = 1;
+    uint64 size = 2;
+    TopologyInfo topology = 3;
+}
+
+// Topology describes hardware topology of the resource
+message TopologyInfo {
+        repeated NUMANode nodes = 1;
+}
+
+// NUMA representation of NUMA node
+message NUMANode {
+        int64 ID = 1;
+}
+
+// ContainerDevices contains information about the devices assigned to a container
+message ContainerDevices {
+    string resource_name = 1;
+    repeated string device_ids = 2;
+    TopologyInfo topology = 3;
+}
+
+// DynamicResource contains information about the devices assigned to a container by Dynamic Resource Allocation
+message DynamicResource {
+    string class_name = 1;
+    string claim_name = 2;
+    string claim_namespace = 3;
+    repeated ClaimResource claim_resources = 4;
+}
+
+// ClaimResource contains per-plugin resource information
+message ClaimResource {
+    repeated CDIDevice cdi_devices = 1 [(gogoproto.customname) = "CDIDevices"];
+}
+
+// CDIDevice specifies a CDI device information
+message CDIDevice {
+    // Fully qualified CDI device name
+    // for example: vendor.com/gpu=gpudevice1
+    // see more details in the CDI specification:
+    // https://github.com/container-orchestrated-devices/container-device-interface/blob/main/SPEC.md
+    string name = 1;
+}
+```
+-->
 ```gRPC
 // ListPodResourcesResponse 是 List 函数的响应
 message ListPodResourcesResponse {
@@ -417,6 +511,7 @@ message ContainerResources {
     repeated ContainerDevices devices = 2;
     repeated int64 cpu_ids = 3;
     repeated ContainerMemory memory = 4;
+    repeated DynamicResource dynamic_resources = 5;
 }
 
 // ContainerMemory 包含分配给容器的内存和大页信息
@@ -442,6 +537,28 @@ message ContainerDevices {
     repeated string device_ids = 2;
     TopologyInfo topology = 3;
 }
+
+// DynamicResource 包含通过 Dynamic Resource Allocation 分配到容器的设备信息
+message DynamicResource {
+    string class_name = 1;
+    string claim_name = 2;
+    string claim_namespace = 3;
+    repeated ClaimResource claim_resources = 4;
+}
+
+// ClaimResource 包含每个插件的资源信息
+message ClaimResource {
+    repeated CDIDevice cdi_devices = 1 [(gogoproto.customname) = "CDIDevices"];
+}
+
+// CDIDevice 指定 CDI 设备信息
+message CDIDevice {
+    // 完全合格的 CDI 设备名称
+    // 例如：vendor.com/gpu=gpudevice1
+    // 参阅 CDI 规范中的更多细节：
+    // https://github.com/container-orchestrated-devices/container-device-interface/blob/main/SPEC.md
+    string name = 1;
+}
 ```
 
 {{< note >}}
@@ -560,6 +677,59 @@ gRPC 服务通过 `/var/lib/kubelet/pod-resources/kubelet.sock` 的 UNIX 套接
 [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)。
 从 Kubernetes 1.15 开始默认启用，自从 Kubernetes 1.20 开始为 v1。
 
+<!--
+### `Get` gRPC endpoint {#grpc-endpoint-get}
+-->
+### `Get` gRPC 端点   {#grpc-endpoint-get}
+
+{{< feature-state state="alpha" for_k8s_version="v1.27" >}}
+
+<!--
+The `Get` endpoint provides information on resources of a running Pod. It exposes information
+similar to those described in the `List` endpoint. The `Get` endpoint requires `PodName`
+and `PodNamespace` of the running Pod.
+-->
+`Get` 端点提供了当前运行 Pod 的资源信息。它会暴露与 `List` 端点中所述类似的信息。
+`Get` 端点需要当前运行 Pod 的 `PodName` 和 `PodNamespace`。
+
+<!--
+```gRPC
+// GetPodResourcesRequest contains information about the pod
+message GetPodResourcesRequest {
+    string pod_name = 1;
+    string pod_namespace = 2;
+}
+```
+-->
+```gRPC
+// GetPodResourcesRequest 包含 Pod 相关信息
+message GetPodResourcesRequest {
+    string pod_name = 1;
+    string pod_namespace = 2;
+}
+```
+
+<!--
+To enable this feature, you must start your kubelet services with the following flag:
+-->
+要启用此特性，你必须使用以下标志启动 kubelet 服务：
+
+```
+--feature-gates=KubeletPodResourcesGet=true
+```
+
+<!--
+The `Get` endpoint can provide Pod information related to dynamic resources
+allocated by the dynamic resource allocation API. To enable this feature, you must
+ensure your kubelet services are started with the following flags:
+-->
+`Get` 端点可以提供与动态资源分配 API 所分配的动态资源相关的 Pod 信息。
+要启用此特性，你必须确保使用以下标志启动 kubelet 服务：
+
+```
+--feature-gates=KubeletPodResourcesGet=true,DynamicResourceAllocation=true,KubeletPodResourcesDynamiceResources=true
+```
+
 <!--
 ## Device plugin integration with the Topology Manager
 -->
@@ -639,7 +809,8 @@ Here are some examples of device plugin implementations:
 下面是一些设备插件实现的示例：
 
 * [AMD GPU 设备插件](https://github.com/RadeonOpenCompute/k8s-device-plugin)
-* [Intel 设备插件](https://github.com/intel/intel-device-plugins-for-kubernetes)支持 Intel GPU、FPGA、QAT、VPU、SGX、DSA、DLB 和 IAA 设备
+* [Intel 设备插件](https://github.com/intel/intel-device-plugins-for-kubernetes)支持
+  Intel GPU、FPGA、QAT、VPU、SGX、DSA、DLB 和 IAA 设备
 * [KubeVirt 设备插件](https://github.com/kubevirt/kubernetes-device-plugins) 用于硬件辅助的虚拟化
 * [为 Container-Optimized OS 所提供的 NVIDIA GPU 设备插件](https://github.com/GoogleCloudPlatform/container-engine-accelerators/tree/master/cmd/nvidia_gpu)
 * [RDMA 设备插件](https://github.com/hustcat/k8s-rdma-device-plugin)

From 48b79a8044c7bb9bbb189716a30663ba8799b72e Mon Sep 17 00:00:00 2001
From: windsonsea <haifeng.yao@daocloud.io>
Date: Wed, 12 Apr 2023 17:01:41 +0800
Subject: [PATCH 180/272] [zh] sync 1.27 system-logs.md

---
 .../cluster-administration/system-logs.md     | 103 ++++++++++++++++++
 1 file changed, 103 insertions(+)

diff --git a/content/zh-cn/docs/concepts/cluster-administration/system-logs.md b/content/zh-cn/docs/concepts/cluster-administration/system-logs.md
index adb09c51187..54ac577a398 100644
--- a/content/zh-cn/docs/concepts/cluster-administration/system-logs.md
+++ b/content/zh-cn/docs/concepts/cluster-administration/system-logs.md
@@ -387,6 +387,109 @@ The `logrotate` tool rotates logs daily, or once the log size is greater than 10
 在 `kube-up.sh` 脚本创建的 Kubernetes 集群中，日志轮转由 `logrotate` 工具配置。
 `logrotate` 工具，每天或者当日志大于 100MB 时，轮转日志。
 
+<!--
+## Log query
+-->
+## 日志查询   {#log-query}
+
+{{< feature-state for_k8s_version="v1.27" state="alpha" >}}
+
+<!--
+To help with debugging issues on nodes, Kubernetes v1.27 introduced a feature that allows viewing logs of services
+running on the node. To use the feature, ensure that the `NodeLogQuery`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled for that node, and that the
+kubelet configuration options `enableSystemLogHandler` and `enableSystemLogQuery` are both set to true. On Linux
+we assume that service logs are available via journald. On Windows we assume that service logs are available
+in the application log provider. On both operating systems, logs are also available by reading files within
+`/var/log/`.
+-->
+为了帮助在节点上调试问题，Kubernetes v1.27 引入了一个特性来查看节点上当前运行服务的日志。
+要使用此特性，请确保已为节点启用了 `NodeLogQuery`
+[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)，
+且 kubelet 配置选项 `enableSystemLogHandler` 和 `enableSystemLogQuery` 均被设置为 true。
+在 Linux 上，我们假设可以通过 journald 查看服务日志。
+在 Windows 上，我们假设可以在应用日志提供程序中查看服务日志。
+在两种操作系统上，都可以通过读取 `/var/log/` 内的文件查看日志。
+
+<!--
+Provided you are authorized to interact with node objects, you can try out this alpha feature on all your nodes or
+just a subset. Here is an example to retrieve the kubelet service logs from a node:
+
+```shell
+# Fetch kubelet logs from a node named node-1.example
+kubectl get --raw "/api/v1/nodes/node-1.example/proxy/logs/?query=kubelet"
+```
+-->
+假如你被授权与节点对象交互，你可以在所有节点或只是某个子集上试用此 Alpha 特性。
+这里有一个从节点中检索 kubelet 服务日志的例子：
+
+```shell
+# 从名为 node-1.example 的节点中获取 kubelet 日志
+kubectl get --raw "/api/v1/nodes/node-1.example/proxy/logs/?query=kubelet"
+```
+
+<!--
+You can also fetch files, provided that the files are in a directory that the kubelet allows for log
+fetches. For example, you can fetch a log from `/var/log` on a Linux node:
+-->
+你也可以获取文件，前提是日志文件位于 kubelet 允许进行日志获取的目录中。
+例如你可以从 Linux 节点上的 `/var/log` 中获取日志。
+
+```shell
+kubectl get --raw "/api/v1/nodes/<insert-node-name-here>/proxy/logs/?query=/<insert-log-file-name-here>"
+```
+
+<!--
+The kubelet uses heuristics to retrieve logs. This helps if you are not aware whether a given system service is
+writing logs to the operating system's native logger like journald or to a log file in `/var/log/`. The heuristics
+first checks the native logger and if that is not available attempts to retrieve the first logs from
+`/var/log/<servicename>` or `/var/log/<servicename>.log` or `/var/log/<servicename>/<servicename>.log`.
+
+The complete list of options that can be used are:
+-->
+kubelet 使用启发方式来检索日志。
+如果你还未意识到给定的系统服务正将日志写入到操作系统的原生日志记录程序（例如 journald）
+或 `/var/log/` 中的日志文件，这会很有帮助。
+这种启发方式先检查原生的日志记录程序，如果不可用，则尝试从
+`/var/log/<servicename>`、`/var/log/<servicename>.log` 或 `/var/log/<servicename>/<servicename>.log`
+中检索第一批日志。
+
+可用选项的完整列表如下：
+
+<!--
+Option | Description
+------ | -----------
+`boot` | boot show messages from a specific system boot
+`pattern` | pattern filters log entries by the provided PERL-compatible regular expression
+`query` | query specifies services(s) or files from which to return logs (required)
+`sinceTime` | an [RFC3339](https://www.rfc-editor.org/rfc/rfc3339) timestamp from which to show logs (inclusive)
+`untilTime` | an [RFC3339](https://www.rfc-editor.org/rfc/rfc3339) timestamp until which to show logs (inclusive)
+`tailLines` | specify how many lines from the end of the log to retrieve; the default is to fetch the whole log
+-->
+选项 | 描述
+------ | -----------
+`boot` | `boot` 显示来自特定系统引导的消息
+`pattern` | `pattern` 通过提供的兼容 PERL 的正则表达式来过滤日志条目
+`query` | `query` 是必需的，指定返回日志的服务或文件
+`sinceTime` | 显示日志的 [RFC3339](https://www.rfc-editor.org/rfc/rfc3339) 起始时间戳（包含）
+`untilTime` | 显示日志的 [RFC3339](https://www.rfc-editor.org/rfc/rfc3339) 结束时间戳（包含）
+`tailLines` | 指定要从日志的末尾检索的行数；默认为获取全部日志
+
+<!--
+Example of a more complex query:
+
+```shell
+# Fetch kubelet logs from a node named node-1.example that have the word "error"
+kubectl get --raw "/api/v1/nodes/node-1.example/proxy/logs/?query=kubelet&pattern=error"
+```
+-->
+更复杂的查询示例：
+
+```shell
+# 从名为 node-1.example 且带有单词 "error" 的节点中获取 kubelet 日志
+kubectl get --raw "/api/v1/nodes/node-1.example/proxy/logs/?query=kubelet&pattern=error"
+```
+
 ## {{% heading "whatsnext" %}}
 
 <!--

From ddce013b4765202f33a66152c290599f587f8b01 Mon Sep 17 00:00:00 2001
From: Jin Li <qlijin@gmail.com>
Date: Mon, 10 Apr 2023 18:34:35 +0800
Subject: [PATCH 181/272] [zh-cn] update pod-qos.md

---
 content/zh-cn/docs/concepts/workloads/pods/pod-qos.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/content/zh-cn/docs/concepts/workloads/pods/pod-qos.md b/content/zh-cn/docs/concepts/workloads/pods/pod-qos.md
index f47384643a3..aa110cff4d2 100644
--- a/content/zh-cn/docs/concepts/workloads/pods/pod-qos.md
+++ b/content/zh-cn/docs/concepts/workloads/pods/pod-qos.md
@@ -69,7 +69,7 @@ use of exclusive CPUs using the
 [`static`](/docs/tasks/administer-cluster/cpu-management-policies/#static-policy) CPU management policy.
 -->
 `Guaranteed` Pod 具有最严格的资源限制，并且最不可能面临驱逐。
-在这些 Pod 超过其自身的限制或者从 Node 上没有可以抢占的低优先级 Pod 之前，
+在这些 Pod 超过其自身的限制或者没有可以从 Node 抢占的低优先级 Pod 之前，
 这些 Pod 保证不会被杀死。这些 Pod 不可以获得超出其指定 limit 的资源。这些 Pod 也可以使用
 [`static`](/zh-cn/docs/tasks/administer-cluster/cpu-management-policies/#static-policy)
 CPU 管理策略来使用独占的 CPU。
@@ -124,7 +124,7 @@ A Pod is given a QoS class of `Burstable` if:
 Pod 被赋予 `Burstable` QoS 类的几个判据：
 
 * Pod 不满足针对 QoS 类 `Guaranteed` 的判据。
-* Pod 中至少一个容器有内存或 CPU request 或 limit。
+* Pod 中至少一个容器有内存或 CPU 的 request 或 limit。
 
 ### BestEffort
 
@@ -219,7 +219,7 @@ Certain behavior is independent of the QoS class assigned by Kubernetes. For exa
   Preemption can occur when a cluster does not have enough resources to run all the Pods
   you defined.
 -->
-* Pod 的资源 request 等于其成员容器的资源 request 之和，Pod 的资源 limit 等于其组成容器的资源 limit 之和。
+* Pod 的资源 request 等于其成员容器的资源 request 之和，Pod 的资源 limit 等于其成员容器的资源 limit 之和。
 * kube-scheduler 在选择要[抢占](/zh-cn/docs/concepts/scheduling-eviction/pod-priority-preemption/#preemption)的
   Pod 时不考虑 QoS 类。当集群没有足够的资源来运行你所定义的所有 Pod 时，就会发生抢占。
 

From f03ac425ebefcda184408057be07226fb326d0ac Mon Sep 17 00:00:00 2001
From: Kensei Nakada <handbomusic@gmail.com>
Date: Thu, 13 Apr 2023 12:23:02 +0900
Subject: [PATCH 182/272] fix based on the suggestion

---
 ...=> 2023-04-17-topology-spread-features.md} | 57 ++++++++++---------
 1 file changed, 31 insertions(+), 26 deletions(-)
 rename content/en/blog/_posts/{2023-04-11-topology-spread-features.md => 2023-04-17-topology-spread-features.md} (71%)

diff --git a/content/en/blog/_posts/2023-04-11-topology-spread-features.md b/content/en/blog/_posts/2023-04-17-topology-spread-features.md
similarity index 71%
rename from content/en/blog/_posts/2023-04-11-topology-spread-features.md
rename to content/en/blog/_posts/2023-04-17-topology-spread-features.md
index 2bd8e45f7dd..170496742c8 100644
--- a/content/en/blog/_posts/2023-04-11-topology-spread-features.md
+++ b/content/en/blog/_posts/2023-04-17-topology-spread-features.md
@@ -1,17 +1,16 @@
 ---
 layout: blog
 title: "Kubernetes 1.27: More fine-grained pod topology spread policies reached beta"
-date: 2023-04-11
+date: 2023-04-17
 slug: fine-grained-pod-topology-spread-features-beta
-evergreen: true
 ---
 
 **Authors:** [Alex Wang](https://github.com/denkensk)(Shopee), [Kante Yin](https://github.com/kerthcet)(DaoCloud), [Kensei Nakada](https://github.com/sanposhiho)(Mercari)
 
-In Kubernetes v1.19, [Pod Topology Spread Constraints](/docs/concepts/scheduling-eviction/topology-spread-constraints/) went to GA.
-It is the feature to control how Pods are spread in the cluster topology or failure domains (regions, zones, nodes etc).
+In Kubernetes v1.19, [Pod topology spread constraints](/docs/concepts/scheduling-eviction/topology-spread-constraints/)
+went to general availability (GA).
 
-As time passed, we received feedback from users,
+As time passed, we - SIG Scheduling - received feedback from users,
 and, as a result, we're actively working on improving the Topology Spread feature via three KEPs.
 All of these features have reached beta in Kubernetes v1.27 and are enabled by default.
 
@@ -24,16 +23,18 @@ Pod Topology Spread has the `maxSkew` parameter to define the degree to which Po
 But, there wasn't a way to control the number of domains over which we should spread.
 Some users want to force spreading Pods over a minimum number of domains, and if there aren't enough already present, make the cluster-autoscaler provision them.
 
-Then, we introduced the `minDomains` parameter in the Pod Topology Spread.
+Kubernetes v1.24 introduced the `minDomains` parameter for pod topology spread constraints,
+as an alpha feature.
 Via `minDomains` parameter, you can define the minimum number of domains.
 
 For example, assume there are 3 Nodes with the enough capacity,
-and a newly created replicaset has the following `topologySpreadConstraints` in template.
+and a newly created ReplicaSet has the following `topologySpreadConstraints` in its Pod template.
 
 ```yaml
+...
 topologySpreadConstraints:
 - maxSkew: 1
-  minDomains: 5 # requires 5 Nodes at least.
+  minDomains: 5 # requires 5 Nodes at least (because each Node has a unique hostname).
   whenUnsatisfiable: DoNotSchedule # minDomains is valid only when DoNotSchedule is used.
   topologyKey: kubernetes.io/hostname
   labelSelector:
@@ -44,10 +45,10 @@ topologySpreadConstraints:
 In this case, 3 Pods will be scheduled to those 3 Nodes,
 but other 2 Pods from this replicaset will be unschedulable until more Nodes join the cluster.
 
-The cluster autoscaler provisions new Nodes based on these unschedulable Pods,
+You can imagine that the cluster autoscaler provisions new Nodes based on these unschedulable Pods,
 and as a result, the replicas are finally spread over 5 Nodes.
 
-## KEP-3094: Take taints/tolerations into consideration when calculating PodTopologySpread skew
+## KEP-3094: Take taints/tolerations into consideration when calculating podTopologySpread skew
 
 Before this enhancement, when you deploy a pod with `podTopologySpread` configured, kube-scheduler would
 take the Nodes that satisfy the Pod's nodeAffinity and nodeSelector into consideration
@@ -55,8 +56,9 @@ in filtering and scoring, but would not care about whether the node taints are t
 This may lead to a node with untolerated taint as the only candidate for spreading, and as a result,
 the pod will stuck in Pending if it doesn't tolerate the taint.
 
- To allow more fine-gained decisions about which Nodes to account for when calculating spreading skew, we introduced
- two new fields in `TopologySpreadConstraint` to define node inclusion policies including nodeAffinity and nodeTaint.
+To allow more fine-gained decisions about which Nodes to account for when calculating spreading skew,
+Kubernetes 1.25 introduced two new fields within `topologySpreadConstraints` to define node inclusion policies:
+`nodeAffinityPolicy` and `nodeTaintPolicy`.
 
 A manifest that applies these policies looks like the following:
 
@@ -75,24 +77,27 @@ spec:
   # other Pod fields go here
 ```
 
-**nodeAffinityPolicy** indicates how we'll treat Pod's nodeAffinity/nodeSelector in pod topology spreading.
-If `Honor`, kube-scheduler will filter out nodes not matching nodeAffinity/nodeSelector in the calculation of spreading skew.
-If `Ignore`, all nodes will be included, regardless of whether they match the Pod's nodeAffinity/nodeSelector or not.
+The `nodeAffinityPolicy` field indicates how Kubernetes treats a Pod's `nodeAffinity` or `nodeSelector` for
+pod topology spreading.
+If `Honor`, kube-scheduler filters out nodes not matching `nodeAffinity`/`nodeSelector` in the calculation of
+spreading skew.
+If `Ignore`, all nodes will be included, regardless of whether they match the Pod's `nodeAffinity`/`nodeSelector`
+or not.
 
-For backwards-compatibility, nodeAffinityPolicy defaults to `Honor`.
+For backwards compatibility, `nodeAffinityPolicy` defaults to `Honor`.
 
-**nodeTaintsPolicy** indicates how we'll treat node taints in pod topology spreading.
+The `nodeTaintsPolicy` field defines how Kubernetes considers node taints for pod topology spreading.
 If `Honor`, only tainted nodes for which the incoming pod has a toleration, will be included in the calculation of spreading skew.
 If `Ignore`, kube-scheduler will not consider the node taints at all in the calculation of spreading skew, so a node with
 pod untolerated taint will also be included.
 
-For backwards-compatibility, nodeTaintsPolicy defaults to the `Ignore`.
+For backwards compatibility, `nodeTaintsPolicy` defaults to `Ignore`.
 
-The feature was introduced in v1.25 as alpha level. By default, it was disabled, so if you want to use this feature in v1.25,
-you have to enable the feature gate `NodeInclusionPolicyInPodTopologySpread` actively. In the following v1.26, we graduated
-this feature to beta and it was enabled by default since.
+The feature was introduced in v1.25 as alpha. By default, it was disabled, so if you want to use this feature in v1.25,
+you had to explictly enable the feature gate `NodeInclusionPolicyInPodTopologySpread`. In the following v1.26
+release, that associated feature graduated to beta and is enabled by default.
 
-## KEP-3243: Respect PodTopologySpread after rolling upgrades
+## KEP-3243: Respect Pod topology spread after rolling upgrades
 
 Pod Topology Spread uses the field `labelSelector` to identify the group of pods over which
 spreading will be calculated. When using topology spreading with Deployments, it is common
@@ -104,9 +109,9 @@ time the new ReplicaSet is completely rolled out and the old one is rolled back,
 we are left with may not match expectations because the deleted pods from the older ReplicaSet will cause
 skewed distribution for the remaining pods. To avoid this problem, in the past users needed to add a
 revision label to Deployment and update it manually at each rolling upgrade (both the label on the
-podTemplate and the `labelSelector` in the `topologySpreadConstraints`).
+pod template and the `labelSelector` in the `topologySpreadConstraints`).
 
-To solve this problem with a simpler API, we added a new field named
+To solve this problem with a simpler API, Kubernetes v1.25 introduced a new field named
 `matchLabelKeys` to `topologySpreadConstraints`. `matchLabelKeys` is a list of pod label keys to select
 the pods over which spreading will be calculated. The keys are used to lookup values from the labels of
 the Pod being scheduled, those key-value labels are ANDed with `labelSelector` to select the group of
@@ -134,13 +139,13 @@ topologySpreadConstraints:
 
 ## Getting involved
 
-These features are managed by the [SIG/Scheduling](https://github.com/kubernetes/community/tree/master/sig-scheduling).
+These features are managed by Kubernetes [SIG Scheduling](https://github.com/kubernetes/community/tree/master/sig-scheduling).
 
 Please join us and share your feedback. We look forward to hearing from you!
 
 ## How can I learn more?
 
-- [Pod Topology Spread Constraints | Kubernetes](/docs/concepts/scheduling-eviction/topology-spread-constraints/)
+- [Pod Topology Spread Constraints](/docs/concepts/scheduling-eviction/topology-spread-constraints/) in the Kubernetes documentation
 - [KEP-3022: min domains in Pod Topology Spread](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/3022-min-domains-in-pod-topology-spread)
 - [KEP-3094: Take taints/tolerations into consideration when calculating PodTopologySpread skew](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/3094-pod-topology-spread-considering-taints)
 - [KEP-3243: Respect PodTopologySpread after rolling upgrades](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/3243-respect-pod-topology-spread-after-rolling-upgrades)
\ No newline at end of file

From 9c88b40f0555fe58e97997201f9c01739d8f9451 Mon Sep 17 00:00:00 2001
From: Wei Huang <weihuang@apple.com>
Date: Wed, 12 Apr 2023 18:19:24 -0700
Subject: [PATCH 183/272] Update scheduler framework doc to include PreEnqueue

---
 .../scheduling-framework.md                   |   8 ++++++++
 .../docs/scheduling-framework-extensions.png  | Bin 60826 -> 119081 bytes
 2 files changed, 8 insertions(+)

diff --git a/content/en/docs/concepts/scheduling-eviction/scheduling-framework.md b/content/en/docs/concepts/scheduling-eviction/scheduling-framework.md
index d09934aa7d3..507992b445f 100644
--- a/content/en/docs/concepts/scheduling-eviction/scheduling-framework.md
+++ b/content/en/docs/concepts/scheduling-eviction/scheduling-framework.md
@@ -54,6 +54,14 @@ stateful tasks.
 
 {{< figure src="/images/docs/scheduling-framework-extensions.png" title="scheduling framework extension points" class="diagram-large">}}
 
+### PreEnqueue {#pre-enqueue}
+
+These plugins are called prior to adding Pods to the internal active queue, where Pods are marked as
+ready for scheduling.
+
+Only when all PreEnqueue plugins return `Success`, the Pod can enter the aforementioned scheduling
+cycle. Otherwise, it's moved and parked in the internal unschedulable Pods pool.
+
 ### QueueSort {#queue-sort}
 
 These plugins are used to sort Pods in the scheduling queue. A queue sort plugin
diff --git a/static/images/docs/scheduling-framework-extensions.png b/static/images/docs/scheduling-framework-extensions.png
index d27f89abc4963bcf87366aa2b66c09a2eb962712..43fe0f233e133beb68737eb4b8a70a26c7b16554 100644
GIT binary patch
literal 119081
zcmd?RXFyZww=az2APNei6bFHbC{^h-Gz9^X&_gd#igXYNAT^FuK|l>i4MjRglMX@z
z1q3nlmQbXIlF$hyly@_CX2f&;@45GWzWa;7UVE+etomEeezq^PHB~QAvrtn|P+U;E
ze@~Z!;*358#cwHR&j5dMlahr{P&}hhyLT7*)PjJbO1Rq66pF`?YJ-}dX^7?|XwF}O
zh_amzwiFsmcwCpCb2ZsQ>73lThTw6(vt0e!5Z9dGOV|Fqc*yXk8=vNC=)v;+fnjz%
zaycLkAK*mnEY2FZ@0X+{YIPnE_W%5KC$6VEcj#zTfvM1R8yqO<RF;8bIboH&E2QV#
zxew#~zTUj-bYx5pRDe&`wzdfhouG*ggHXvC<f@vL<+2GmqF3-&Byi(vktgj-<nEJ>
z8CWVCB3e;l#*gYp@a%BAeZ|v1x!fUtg?Czc%53GFCZtQ-?z+5{J_C6HbNWd^VJDNQ
z>GM8NtM1^M%+u7n6SOHsM+<8-v?oZMIr}(bDkt;3K@MTJgxVwz9uxg^_TQb9v(yf6
zwIV)kJ&h##N1i`$MgJL43@`CC-=8{3^{pNL#md=-v=UwMIX-DyAz)8pbjD(Z-R%Ss
z#k04s7lPZc8z~bYXVqKiPw1<@+aKE+<}SE#p3v#pTs!=em9y{orWN5$p}=~VMT6hr
zc*AnQbm$2x3Jv6fe;amdzb&TxTS@sB1z(9xe{2Kk^i=Cfs_b_7M=NLYH}0I_*U7iY
z`dt=VqN7U+rlZ$RP^C*HYI+mci)#lSzy`P9BR*ID$>EmC!>KBjTm6YWFwCIz$;S+2
zO`nhN6S4?izlo?zu<pgn-x9FnE(e3YOWQ){{&4wF^5?b#{t#pAKg&7|F=<q(VEb1@
zI_}kiQ`_?N8JU>9kBzDae#LB^%#trf+-m#43T}bj!Ey(*w`W-K9&4?dQ?3|t5Kd5v
z(LlVdhf7XU{R<`08ie=8fFLXmj8?qJ@ohAORJr3_OyJbJvcsB$Yg8`1@KcoO>jk^E
z<=Mx6(TC~*0Vr@czwr9!Fuqw@S_@BkkSpQFoMcF509Xd<GnmEs;P8k4gt4Jf$`7SD
z^{L-f1@XLGx6#7Gnt8wd%W*6f!Y$*aP@P&anY*>+nN~|GwI02LRkID|J4h*<?LSI>
z7vquT!H5h!*U~L!l(g>PiT{-M{>q~~k!p_$kMY)CS&b0BjRZK_<{j~SS%q4RPnHLI
z^hi=5?{zOU@46Tpjv0eEgF6e<w7;)(9CG1d+wwxRsxt{+w^!F?o@~V7a)X#Ip78*N
zPsX@H9@Uh;Qj^(c%(82^$R-Fy9lRU&dA@<TJAz1Qo9U2aPKGBHvZWl^u6r_G4?Yzf
z?OnWqOOMX!->WR=$TM`>E2&Pw%OFH{16JHIO#S>!1w0TRp6W4jvB&pxO+7mkF=Ba*
z2Q5<Gt7!L9pIP4ZO;)j}gfMN&e>9}1lS{;S5*jrVs<u=;w>+tt#rQH=E4ZNa)NqF1
z_j|H3LI+KJTC*m@pEGILh-0(*Od3#RG>mS}2{}GQ$<=^vfyi5*4Pp%8JMugnlWwnl
z;~|MG7JTR2;IZW;zR;+bLX!md6{Ea~Wh&O!y#>`l(WP8Xg6lk`yfh&L>NNZYSYKl=
zg<*5PF)SHg5j7ayGp&EImx0=M6T2|#<083m;1KcQ)tn+@)GM8548^8Ozq+&y?By!S
zf^LOD>hAkUuVy^ZOC2?mnavv|DW!1F9imn5MiDk)ERz{JjMZmwvek+3HBSZ4ctu7w
zy(Z<af7BAGje~!qiW2LYzY?R!MnvnC78&KeJ9tY|bq=(*^ZJfkp8LaP((tHr7lG@7
zze_|_o0D_z!S;nJ=TuzI#+50hI8_Z__K%k#EcXK9_~}kFC^G(Q+j){Tc%Y2z+f6x*
zAPjWt={Xm%NybV5&(NUs)N5R<hzwEMJ=d3D$?(_~SDMJnQ`*WLVauwVTA`|%m^l0X
z@YRe6(BxEN0&Y2tY*C97l%bPYh&5^9VJetkYq29Tv1!Gqe#z*N;|geuOdxnX9nH$L
zOPaDkY6dWA3g^6*r*5yXh(26d%Xq*$;kG<%Bop$h>!UphsRq}y>5EW@-!?>%%iEc}
zjbHs(3+x_|q^^XcUKK7W#ht3fv1^>lA!d41GcMb0M&yjIx9xQMB=NE~0RF5MtReO=
zn1Ndb-K(dyXR}9%IRs?k)y&smYHKl1EY<5Ium;(s&qxMTV26tD`P287$KC__V7`Bi
z)J<%M7h7$YEB+Z_=a}anr8czr%J81eby|H|(S-xMtd99h7-wA*mV&1hgY9oIkq{Q$
zyl9o^rx781Xc`wkl?3<%@>sNTmuef!Sg;(#ZNF^U%i<3o=VHR^R_ynZeBJZ^#V5mM
ze#T9Alq+sR|FG>15PL8)I(k%TasNJRfs;e8@8V8OkL60e48CK`#Xe7jtNM1<c-EgU
z7I*2{S`_27Aa#cizLL1cw7RsuWJEO66}9L(Sz`n+&eKuSaD}AeC3U2L0qmtM#FwD#
zQGM=bF`&TS$w9K!$1u`D?>Q<lQc|19%xKuUBBL+)bY(S#fb6e7P7u4lYG-n*h;2Qe
z*NoqW3CXUm_i*=OR(3`NQ^OG4WX*)nWYm1AVSep}Wky7Frnrf0U5O!t#eZJ<g%ot;
zhBx^PGE|biK_cmlMy7T|*;}>kzWYhKJ6n$`&Nf_wp8D75cBd1gy$I}Hchax>=k=zT
ztSE5`h*96u3$)kq?y^IMQq#>Wh9^Vn(wJUvXX;6aEbMVp+Xx6P@Wj(Wz=~E~W^6sZ
z+BU|>P;P2P2BVbueWhXyeJ%JMkUHc6tDfn8mRl>yV(BBd@|eT;niV99O57vVR7>pE
zd?;0DD7O@g#TMjQUh7eZs8hd%yX>)?aL_Y}*FcZKRtNpYm|<Vtzc7))FB9K&fS9oE
zQlyozPh=`(Hc2?p#l!J|jc=@kk!LPzNyFe4uD!2WIi@vyZz=SCDSzzZCnci%XPXTd
z;-e`9JYW?5Tgnq`Sw2Q7r4Z~Yxsb;aC2uU8$H`DSf7nbfrKpD*d))hJ{v1*>NTMQL
zg*^nqoU|z{7N!tJ9VvGG{?Sma9WQlJMHjW(PZQqp=IEP@u5_k4^D~wyD8!X>`q&%|
zfBRVkD4taz7oN6ZWAFSdx)kXF*5HXU(hcpO{3z@c5^0~lzkLq+ua_t&I+SuQvpcH(
z!fyTbLU<eY)i3NmT7##{_HLeJ#{;nQdGGQIJ3gfxJ@&$1wd;7jkkGdHt9Bo(!T7Sh
zU$n~;^7QnC)go>gRC{`co)msU-T&doI!-^CT!~4u-2zI2?FUaKDtsZ6P`mX~C?=`I
z<P!&%sU-YPqr<7NWT&z2Mu3Rb1|Yh+u1_O12oMbd)K5OP4{jB_zXCQeT9Lw6VbY}i
ze&0GFF`e=j(f^C|m&On32=elm5TYshB?%*vK54FJ{TjZKh&05>y<cG)E*T1Q8|#kD
zEw1(W7(*DU#^(aRE@8}E>z{%~a=l}^rt31iVIq&6KE^oB>mMP2yWB3rmK(s`a@B(&
z;8)4zaTnxMkTDFltzjm)`OVe~rZBELIFOh&Rc8^`vXvdpICNpZT<!Gx)Z@wKpDW4c
zHXe=g>fOnHj7_|ZcEfh7YZ>)v$~<X#6L`2OK)KbxtYOZncg(QOmh>7AlHmh>0SQ9B
z5;(i0eJdej-3WAr>0^-3AbsKE#n8j;xG_=k*FIX)n*bedXuFfZsU`n(7N7%7VEM~q
zWFPfDNc=~m!Q>AU)Lx@pG$WH6v^xeRKIW+1PX{vUkC6Z92mJdifdeCm@=A_k+FK~Z
zdw+*_SP^|EN+hc2%;o27wvVKzLQh02MM%nYMW$h5+u`ctwI2H6+xtN%`6%8`Cm25H
zu5WByURj2bu?@H{D8lfVzwOEkx6>!MJd5qotncmhcq}tqM&2cT`QyLbHAi_>mqpqD
zcV+has+I)BIxAloPlx^lb`;%X##X%o>H(`?^^;psOT!mXzMmonE6@4(k7}RLrB2Rk
z?hE%60C!R~WlDvii7eHZf8KuP5_1#UlyagoQBY_+Jf|<jopC&{{(arKY^2E8sdfT`
zP-rL3V&oq8cg8QXCLg1{U+L}peNy2$ZES?$gBvFbFa^(r3~CAA@v=-OrLH|Kvt%hA
z7anKpKaf>raZ}F?x+TZEDW#ihtv;5WqZL~4G3F6CD}~AOw2Xnf5D0N4NkXGpvzauK
zKc|vAwb!6ciW8%L_eSqy|9pNX%727g!0wbMrX0oGN@@N|5VhTMRlT%yBR54uuG$si
zyZm6cN-bvg4-_s?@dWOs=s24}&4l$-j2q_~+wQGNr|C`7p0&m!P?FL|lLVO2Xt-jW
zZKm^SRAhpfQ*W)0EYDRGPUVC_v^mb|muf4<Rdx4jXNPTcVW?16kiC5pU*79nqr6M&
zAJw+gB)$FM%MvFHdne>reST1Z+0@6+Ssb6#Yu8s&wx#f01IA6ekBSK}3|&g$T!+~0
zVGfMKYzNv~erDgec+{h0<2PjJ`GSoQwHUWI8|Uy5m|P9tmmpM(6tfnoGqcSjdt-&G
zh}#ytP0OG7HjFPhVe<-E#t*3O-+2IiYPDxsknE1Nqr{$C+)39nKG&wCDe}*APu}oA
zhTe>q_VzgBGF(YCLrJ6j=BhNjmls)+`1N=)i9<4o<<ZZ(Z`ER|;l<HUd$O83hcH()
zSS-$aSvd9DS2M)&By=C7;P;z$i_6Ee&I{QmWcr3lOL{Il_L6%KTw@El0dO-qwLd7W
zx=gC&k{kTm%HoqmtuHpE>{u`_OxNLj)%nCsLBZF-WLm7SU*c`?@lllrTRrM%d;fPC
z;<GrFWPjBFKVHTHJKS=UgqxuY`PC@VvJX)di_3X<<KCkeDgm;rPI`Io>XIJw-y=Ja
zdwNJPe3c-wo(Lk-Mv3b}i;1?s<4i6U@Z8tYcK0jQ$aI9i=MQpb9|#zcmetPGWw>F#
zCq(qt*A=yayIei#zU)#_Zh3ld0LVc(-}c{tfS>2HiUFGRY+W47ts?W*0C3G@M((`4
zq8L`0Q&Oz?9uKr9oIzpz%d}ElNG8$uCAQI^R3q}MBQ#u9FQ&-8*B5=hs`>_0`fC=M
zm*JdGQx?ro7n8GL-V`jxa@>KsYjS?n>m+P=@Ce9NTdGh#YI@6P5&N;59@UWmMEvgT
z*m2X{ld<4qDj5+@r~mjxl_QIYGl<QpPt4lajKzFCLJd@n1{DoW*{cD-zjDHpi!E^~
z;C8k7(wAT!sLw=}URsEY^SWbK@JopWw_iLFa$GUkt^mjuneaB4Pja@(o-IzwX%&-N
zSa^(ukCgoLrc^7Q0=PbA+Lh~qq*&4L2xbj4>#=2WxnRfsTgBsVo7WfRD^wy>nx9q_
z^(XPQT=~`6k;fwRFBYUE;&LkQTQZ3*G|G8Y<E|FiK|8g$F5FXug9^NLN{ec>TPAGF
zC>L6yxNgG)hfgMC_dsbdUqU%x4U=#8s!QzNKk8hpb*7e8JR_~(b~rG?UtQFY(Qz5G
zf(i%-VMPnsH^3-yKmhJZ9d${I3Y;DOn$`C4=C3SUjFv~ORKEK!V9F9{y$FF`W!lRA
zll$>%L+r)^)fz{J4SuN0DSpXt^Gi{DBfN&H6_QYC32)Qw@<b1Hq^1JN8;^k0VIp$#
zwOi7Hc-`*aY1ps=HV0}wPR`F1bypT;wZMJT$07`_K}VW*|KvR{BjDCZKT0Av_SQxI
zj;j*4AEQIb;H!9_Neu&O2wI}UC?st*Dl&vJ(10~X77jKetCkuo0tQB%qhh7U04TqV
z=SN0sCU*G*ZRqPs4H!wi<C=MZWcO~Wxu%%$W|8;CC6*C)+r}E>&6-NY#~*V46n_ee
z*mH`EPMaUCR7XNnw~|zr(rYq)-lTwg1C_5^a+{rA^3sVv1C<SE8bAN=?A^tJhZ!fU
z4TUlXQ2kEM3KS8FdCx;G75sdPg25*8_TbgS5frm)0@19^1#j53;=sL9*1uS6z8QJ-
zWRt3H!;CI1)&RvJcUr=Do?HAJ9^)o+qUX+&h7<jWmyYvw0{{*c9_JS~qLP9=Ue};b
zNQC<ls4njfCtg;FmKiDY^H~-y<b}KzY;pem1d%(ysl?V+b6<WL*sqz)9CCVm)pr0<
zlJmn%&;@jY@ZxG~&~z(X{mS~pJ~?|#1hs6G9Jt+@N@7+ma`2PfT>Z17)~)`;1J7=4
z%Qzo3${mS%Wm2M(0QfSYA@f9eDPYALXA7R49k6}r@?Ni#E_WqiMAgD=5t~?-fjIoE
znHVrrqG`epV4`wvZw!G`FtJJ{$7P<m>tz@4i)`Q)0FclM)s6s=IxNc+@l-lmYYy&|
z*X2+Jz}!;2H$c^uA}azsk0@EDU)h+Hi+9;ix7bL*GfPmN(2u7@7o(8i&+SJz0{~W8
zO8~GAVGM8oIEO5{TIT?O*{(zY%rXKP_UQ<KVHbCqr*8wdOdNE!w>7F<=1cttev=m-
zsmo9TNOqFj2QRS20$8{b<2e=ej~KSQ3iv1Z_dQ<EiWRkxRXyxIUKA8vZ!mHwJx*p?
ze#)1U!1FXSg-oT#&!YrkmCqU=0PoRboNWbYgzq%G{SX0&1^WRSA%S~#`DjL3ap19o
z4SkvfCxC`LQ}{QUx}(~SlWw3q#Q0>Z<-Sg^dvJ8Ayu7A+2IS}`^VUz=+kJd?zn9_g
z`sM_t4W*jY%O*Z+sg6WwTD|*F+==Bns;Q3Y=x8zELV%L**?gn4AuHQdK7TIn89na!
z0c|-*#G!BiYRFgFWG{Z(R^0Uyoy~LQc}NgmIp-^YOGLACQS)}GBD-xl+F3>KXZ(k(
z(_DqoUhJ{U2J{SPcgR>yzNL;l(Fp~YgXXGBtPj_>GhoVLFEP&XXr5aIzKam7z|^(u
z*b=FDEz)~-6|k)oa|BJ@73zS^ZyPexKY?SOITqMf5RdoC=j8{#aS!HG5M8*>fJjM$
zfZNCeTx{8#xiUx0{ja$l@zi(nbd#2^6l{vyQw0u_7zkrT*|Ds?PxHI-mj`r`Ery^}
zET?il8N}4{hw)v&3_<p!5TLk!Gw#lX%b|P|sy4!l_sy_bdd?xJD%+4a@C!g@SMt7a
z#hsPsAuUmzb05FVEb;jpXQr$8T!Zpz=w);~L8dtder|qOpv(zf7TU${M{OACfxFEH
zci*%R9o4IKsT<-|kcdumY3Ltz>oLfm`#b4Zdy=$oS|_!yY{xC^ds1S7p3%X9KEmbL
z(4Z|It&>MD$HkpijOzvZbpQ3qje{6_<M7<*qalqzG>$s5{>F(4)tzncnD_4D>=7hz
zqK7h@P0LRy?zBeW(RAhq-Oi=`rY!RQPz5nC`MGws*cdNVhbnN#B3WA-E5@G;zY$03
zLq{?(c}t(@o$2a*gWAdv$=v|&7afXkMHjv@6&<7pEPJOq_U0#w73rvV$C{F5fLUEw
zjPVVafd3j-EeY*0p$$CZ)iKtSUEaU8y<(<g9G;3-!N8K>4#IL&Q7$^q%AaTpW*Oyu
z2<MfJH?f-L!FQYac<`LZjc4`6=ZhM()il+{cwo{kJl@;(+W)9PM`s?Dr1CrRK@-Pn
z9W`NShQb8@F%CdNMg%5gLMub@YkGR8H+IRhZ@Ry>f1_u~{kg{)z;eFKzRA5(jaV|I
zQnFNPwkyJgNXyPya-gpCJ2Hbsb(l1N<}%NnQASoZ>2@xr*!7ABZ_3W-V;WL|HU=U-
z1gWJ>6x8AzY%fEwRd80h(2W#Fe23Mb<icTBQgc<Nvkc{yB^;3pUIF^o`~)(EKRE8X
zgy`;&60wH2N@TY#NmnB+e(z|U>qu(i{9@kse}nqY1-)Wz8+;xluUy)U>Ro~;r0$Nt
zUfyQ|y_YTI4nY8lla=DixX?$CzADU$ZeHeqpo2Li%1ipQ@rw6X`cOW<q>9X=`iG`@
zOq{NK!<WEXpd>=$I3fxDMN_ZSx%cAD@gct`HJPRZq7+o;)7&?Km=4SSb1O^5f5eG1
z791zxnj(O1zQz;ndY`Fv$po_NmP8KHIPmT0;p;E~A4~eh%*jb&o9j6L?p~JWjUuZ`
zrl`E$uMs&3)(_ICcIog<QI+L8uf>>?H^l=Lyz3L_5(v{hRW+&GOX;bq#M1nLneSW|
zdMvBNcEJ-#6&egyGRTtcM77V=yU(3lphiF6KZ!$3fqgb+lYQ*U)si)#(cQB4_`)D#
z^!1_pQ4?VF*^YkR27?cVOq7&?d)M<}i;l4&;2DLl&VBF3(x^PKmkQ1cg><QMgg<{v
zDrOV~@-}F9y1;|v3%p!lqo)tOvG|JioKl<u<<U@*V0F@_e<<4?^(g~&Qs;;Ib}fCb
zt))G66kZBp+dDKKk4nUGt7L{SNbUL_xsT6${IvV39mMHBR_~tou5G!iJ(r8^k$c*P
z>s>ZuK8Vy;hQYr37aKxN9PvR9{jTIyN<bGL^^%C&+njeh)M_MNLA!kt)o^VzI>w_a
za`I50?wJWy2M|kKcBR?WtJ$~kY83`PP05gzX<K(3Lu#;HaE~e%OzY1=i*J1pa6rOy
z16Yo@O#~%BT6h=C!j`$g`fjLQfjerw=RQkDkC`uoC6Q?yU8NSq_itc5W63GXcpzo|
z7R>nh8n9iMO49-I#9WT087l!h2cXbN1O~0WkOsO7{kui5gRo7p1*pQ|mGP=zK1ELE
zW(w5;D<f1hOH;-I!X)T9O9;=Q5q0d;D-{l<D?%ZY&?^P^J@*|uDlSs8A%u3pZnl-(
z(EIWqchl5zc_Vr}$e(6nGGQBS!KjtGuBUaPV_n=itHR#1+RA*Zy_*J)a(zL1!wbb5
z>@fz$y;+&8&|*XzGZVM79%p1T`AyLUeU*g$Mqj%5n%R4Ojl0v1SrIv{5j|B;7$Q|P
zT7n%L@1wS#h(%!1#?gld*@#FDzoF42KHo#?5`WZEN;yOSeOE`UFf4c2PjThDw?-po
z@@}F$x_LV`hdHvxV`G*@?I$7{3my#RQ%`_fKM!mmZYP^)e@<`?5{U|*H#IW5GyH-j
z=2f>d%*!3hbm^$Ku_z;=8?K$S$Rlf!2aXrdP6WR_@D<4J244+S&`^d(xB*VfG?IOk
z_iiYsU(B8+VLv<)ea}WQ^ZveDlF6z?WCA~2r$G|(=#>z<J?5T{cGi|;M8?CLtXsVU
zN{kv4`sXV%p1@yW1H!=@0g3GDyqgy1R!S-}A_h@wWIlg>Zt5L|$BV<%(h@wk1n$@z
z%9RYkn)L1i6Ag8ZZt#kCh_UeZ5I(>RwJJuu6uc^|FK@w&Qqpx48jJYM`h1nA5=JF<
zV|m%F>3<?sxL&iiGFu@?>`|FGvzVu55bwP{-Cg(FCgThynV-C!9I)A?oD*7WnF}!$
zpL}@xb=X2>iRbi#b9Q=of=cxo5`4{=6Q}xUUOcIYR*{HRWc#%EaUeWFDEKU}BJ}|V
z>bp>_l1Dqfb`>!Sk}C;>@W?A6;6r)UGdQ|)RUl?3!BCYmJ9R)m)bWePx!k`pSajKG
z$gfpvA?LO9TE7m5$&WEA{SSZ*n$M$4axD0{lau$$#GMU2?CQWU7)?!Ba7IT2&{-7a
zU?oN}4gyf0{+Vx|NyaZVG#Zz8brNlp+J|(cfTUIRwEunlw<vKMj-MMl^Ets84;=OJ
zK4qn!OY+k(?K{lGmZ!ZlF||+^+;2@1agwT1H?@K8c~Op?lA1bViZ}WrC<z{`8m@xh
z>EQ%1F;ylAL8aySBG1Vre}1K^m$XY{K7&&i?wMHvF*zCjn656l<Rqvfm6Q$u4VLz9
zhTLTTv8W(oW)P9uB1s9g+!zSFT#$1`mnb&6zw?Cbm#Ie$pG$nWzBNrba^R<Q*Q)F_
zTdL64p8fz~;B_YTr~Oz*YS|>3v*IoBiYfzX^l?6$MwMQXXsx4>o7J?7Ef-IE)<jfy
z)*dPFDloQPGi;`Z1$6k7MXu*k#p=fiRkQ%}5+%;0*Dau^eMrzY?@}i01ITfmQ|Tj%
z^2IavSrVtdO@&mMJ^+G?7?}g4ccaS{xCTvCp<bY`XlP`CBSSQP;GtiBK3W#6+UR0P
zs~=HRN&k))??0yToJf6b->c|$KkFpJLm-`*0N_yBs4d;&Hv;m5LJeN7dJZr=<&cN=
z^gq<dc+vryj?IGrxQ3@@)8<Hcq{<Wma&mZp*0sY5qP>vYQ_oq9Pk@m+-Xe3oZ0XSC
z{WTMj=6iM=cIYllt+Q2-^IFMNWX3{(|G|S$K90rCA;FD<1HRwa@{m|pLsd7^vr2I}
zgNpRoigB<rIMYHVGRZ#$my`b`=_*HQdOIi+aFIsQ0mlQt&bs@gRdK<P=F>1V5PB-M
z!H)f%=0>9e%@TTiH!kRWom^5dFzUZjASRiVBbO18LteKj(*M&<udf32c-?cLHH<m-
z@h@=}D+ATZEmKI%8L&TRo4hZN12!MNpFwLh-SOagy0&F{wV>0cH+sh$(zkS%VcHIf
zo_I2bj0+-uj|%5emR5}Ocuwp?8CEqPXr$6Xe9wDoN{Tli&*JX*DaHx$EIr8R$a?4}
zrEJ36Od7*#E8C4-M<ev~bmJ89`xf}goF`4BFvwvISnzvULi-Tn2H#S+_Dxpa%&oV@
zPTASmqUU@?_?ej7$)=yfPax7{-DT};bUSF}An!fHWWTvdg6Vs9C$h7Psh*k5`mxTz
zOR}R3apFLd^n7db(%_w`R$y^*y)b)Lzv4>G1bgU>qFHIAf~H62&E_9j`P#D`dAH_<
zxM0=%A$-$7kQ5~;5r>9c)$`n+x33_~p@WxllJ*ZDU2zX64H$dq$2%ypySGNp;#7=#
z@_TH~^;=Xdo?C#UwgsDxl37CT{oKXu*5LI9-j?&bvuS0roKdxDdHQVz^!c}1XOm>*
zzE!*AL4NyaX2{_cAQqc3CZ4oQDHX9#h_T$yiN5Dew(sK5Lf^F#vpsFZ%#(iOLU;R1
z1Mjb$R&mKR^udZ{mL-XUm1}K(T#jq8qn3n8(&`5?#fnSbHW?lni&Ko7Y$CmdFZ0{2
zZs9H!ycF8qe$M0ovH-wzfJPnW1^Vd4-I3UbWcntOE~^8O*2;4-*P%W4k%-xj&GAKZ
zBeU2!%=VvL2t-WcraT%mHW*+B*A)IG+~dybH`6}Vi0fzIPxK$FQ8MTY+x?J}Gpoxp
zC4;g7>Ic2Rmp~QhAj6}!`Wzo>9os@dQ%*h_9oscLSJ8HMJCzXNkU6nkap^<*-qHfz
z{rQWY7AuTSLlsVkJKv+;){M<8wPrl15oiOw`|wJhYeGk`UN`T$e|YW>?Yla>5@Nen
zU+2KP>KVK<`@%WN@S?c47mM>VpD1%ga+_`A8T;U?xgVG{8V`L#T5M?an|0)9RBfgL
zk%B|;01aVm*4E}o`a+i_L-^rPmM25j4w)v1sR7d>uXQHDA5|57@850lXM9<gGCB&l
z5S{4c{dwdS&(+Yr2W)yqPF@!}#IC0g3-%3+_=U9(AzQ$AldV+so}SlO>K_e{V}pR*
zKc&^T&_vQa56^`xv@xFfo%wg%H~NC`(o7RQ`M5>dA+V7Avz`s=(-a}BfnS2a`KnYl
z97!sC=WBr7zDJ*q+-=qZg6(buD})jpG9oPeU^(^^Qyv1Fqw)Z#%<SKArlkxEj1BGg
z<x!$`V0f1<VCHWgEtvPZDo6;@e?L~2)p~tv++&cLDgHLJwgc!uTQJ$=ME_ds^haP+
zoG-Tw<vkefr~Ulu{@n=GF5+7H`{C(+zma(Ur~gi!&s-F5Dl*a+BiC(_UZJ6=-91l)
z)FoxTXCdf!%!{M@ne9V8Ut^v;xOQ6zq{%#Uo6$n7?R(Cu6pP$D*q-ZxSxZ)o4;xZ5
zF6$Ndd(-#Rm0@bRo9mwJ5(_5$>~fk#9#cVyh=gX%DfbXQu<c|XU5NIiPyf<8`{w4B
zy2z-(b3xpmt1H&)sHHu_yGp}rg1}4qQJeMI#eO=Ou1b~fuI@Gyzi-u<<XvxGXqT6;
zZ~KUSq4JE?xmQQEaTEuPhx6ilO*1js9!0CJ&d91{V-4`0B?#|$S1zCaev7srsjWZn
zDy1+u+Lj4f<qV2lfKhS^&r<7e`tG_{UXBVs*VTY^kTRL&#OK_t)xO$0PY=VhArG8%
z$fQ{oVMeMbPDtRMJSxqS^SjvkxA;Q2Xo-cSyZ`LGP-uUK@<DstKtj7#>YgI}FL!QW
zi(!pnsC|x&M0k@Q%#aQ3nouEnSU)PkCQ10=0u0EolCVeG>T+GyGB$D>G7}OZTU-8&
zJiD64`44X{*9aQsU6&9F+2$TNRScVHLmhc1_u_>JFW+Jfn+%_xj|yEo5(EzL+*@NC
z92bPJ@a^JQCgJy=)boe(fxCdQ5KmudpPNeU(uE?7cvXpv43+V21xgQDtG*4M-{0MS
z12u*6WNsT>apIL7mZ{c))GEd~LrBtJGw!k#?OqNo(j_Xd@D`yNT!xxA)U)fwKUB4c
z-J7g{3A2n%#bn~MpYh(<?_3+#)BZPoC>)}J-lfPX-k)Dg+f}on<G{k>xf6<hDHsaY
zsf-Q-hfiDalxlMyC^uE<{&`3J5362SN!vDKp$^Xyo@7s5WaXaEOQ@k8*t~0E%9WD>
zpxt*kYRD9Md(jizn^j_}XLmaim>dp$1N9(a-A}H-0jBVQl#*nEa2B{tJTB?^HFOcM
ze8sz?lNfJ}Nsn&lD8=4d|69Z3qe&9C@7_gW^<?>Yyz10c-&On`ReVl0x<!7Hb;L+U
zy;hMi1nKLtcF@+P)YoGlQKO5$bLy2!DsSwC9@{9D>K$K=qTQ@(e5|j%JRiA<EZ(AZ
zW1#qV;dd@%YIaUaGxPB9f=njv^zGQqG(quYTn8-&&q{S^y8G2GYxthmXv)6x`RF&;
z-R9MlS;f9c`$fT{n%OlBQ3HpGW6unHQGzeATBzY?>gTaeZ&%2j!^8~^T}ds^*Ewg&
zjx64OM{zGk>28Ng&Q6kewsu1L>Vg!K-O3P|Dwwe)8;XC47z1TKnSF?4SK>Tf!5*W^
zhX3r*8dH?-ae0|J><aa0g*iq?`;E=3_MxcU7`{-~pfxwfr2Nn38G0Ti8jju4#^18~
zqIXHWTiB}X0BTChdI0Ed2KGUXzGrODJwaX&wuG~X;rn-Qhx|q(M_0*DDSSW^d9`Ov
zLM&uOr$IrzsPf%KpQjH!N>qn2*5=w={i$N&3GBH!pG`ALul$=Q6ck<(3-d4LayE2x
z8$kKll_&PgDJbd~15vD$Tr7!t5w{@=3z;V#qi{&&hsfWO7UtWy<=7k28_@97{3P3F
zNw#kIBZ$0^&w$Tc;8>7UlTV4-koMXvb58xgH4fkhS5T2Ta$0Xv6J~tRWA}nt>f|Qv
zyuqf&^4!OftW16RCyn@z6Fw;(hyEu{<(yRLKm9zfc;3@xW^}+OL5+D{>C2#BsoI2U
zW=i=9P4j$xW!j`mybfFJ>C3KTo@jaqIQ(RlUT|efwrw~295|5b{FNOd^|zvZ;-IOM
z>-H#-!tX~TlD_Q1vP2-LzGV)Fy%}#bM-B}Q1wG#$(ZY~XjysZ^KUu*w_P|=6hix-p
zA7+?SzH3aX|GR)6#oWYBLj~0@BILc7S_H=UF{ieuu@Tb3m}*7@oso+N?KiaCPkW^o
zmga28A(y(xo*ZZ(K2Fc6im-hOH<C_6xaY{(9dSCN0}qhfj{*V?(2zP3^_|Mh${+*x
zV%J`Y+uX?nU#0Nli@3&vJo58+>0yJvcA8C13x5ft0XeLc>a~XP-@8X(jgi>x!hhG;
zOB{QcKEOJ)KW@)#ZoRhR+Ax^`u@$`Tm7*oLmo#Q~@csQb@<U_ep=2nXWFC7c*c)y!
zv)}MYL*O285v-RM7sVQOMKLfLZ*Kw1bk=@p!zb)>AHPZW0p}2HElvY8>w$K?UF)2{
zxgNhicp?M><E6H!LdR^of(Xfi0Z9u#l)qrsUg`;yHu!C8$`7-!?Ctj)$T&`#UP)Ki
zcI~C-VV0T@8j1Ws#FdnoyC>cxuw<%^6je`Lcbm$RBm9ZnRyx+?Rx+9Oqv7;K@{)@f
zR$#0Arqj`>1qekMa3m(J7UBA2`3J!^Jv$HSEQ)tU9SMzWH~`B{7=veu6M|6^TC#Ji
zW5kL~?(5ernOAE#Np}1G?B$b-US;$&!|Za4qC;v(0ebgBkE^zz)90w6#ZL<QNNqG-
z4I+IRk>RM73x*TUR2PzN?+SUW=zAJ<8SfaJnHPHtPhH;s@;kG6fIVA7lL;yBG8gWf
zYhAxQsdt6YDQNMR;smiY-)UjL&vJ&iX-zq-%l^g%BC7{&bkMV-Iz)-&f*4QdCG8Yt
zjXk9TbmEWE+aJ33y}Hb+D~4c!9|AUZO$pmDIY%Pe;?BJ<eCxRgdDjV_1urs=U$c@-
ztSmD3Z4a4#rmW6jwrmFW)|judyX%Xq)|vp7G)zT9R0Xbkv4QIF_A*X~lkH(fX!!$%
z_vc@ZcTupl=U{RnPu$EOW>CI?of&^RQAzsVWr6X3q5PNM9pqR0$4EPUF=hNERhFY}
zoB110ki|4-TW{e%j_d}tqcYQO%QdI^^xh!%ByT?k&t0T1lh_A786f)DvOYF6_etCV
z`^0z@wHDr!wB*hu_GIF<3=j4OAyj}$a%q8t3-zB$L*CGpGzO66mk){b4JD`eUZ_aA
z5dC{*1m2aOPik2%U6S&fJ{YoTOuv4786a8A<#u<J2=CNio|TCbs~kw=G8ZkC5$W`a
zY)8e6H(Vvi`@O6zk@v95nZ7_z?}*!mHGE^QSfQ<gO~_By8E+@LRH%$R#~{GO_C8EI
zeDu2I&{hu>tkeS|ePj2BgPmP>g*pXW(|!DTWW60m94_G3sirz?C?CkNVZ%TVTxHk+
zhN{d#6Y=wgVzcc!Ib;Y;j=0{YKiUg>>VQ1*nVV>Nw7#sAs3`%Yg~j1PrYiA8+p-na
zcW`$Y{{&dejYL<>Dc+u`S-;R~`WWm)U$*3Tpzm!Tn>e>W5H?h|c9k{#CGZNOb2qaO
zBRV1Lg*DbAIHq-e^<O*o%DwmED?10@y@G_7LMA)vxy;iW-WreYMzqV}*{Vjq27)*K
zgygbZzwYIFL~7#nidi!q-rH-XT%M3vfWH=RH_Al?R5dBc9rep3VodJ6r=^o$ou4^f
zsFfxUsz;FTt#~|hPhV<b*2EQN#E-3XH~f+K{J7GL^*XwsN287WUkjP_>|HMpMaT}F
zokksbVOvygJ<Of(HqN;W*jsqBwyn7An?QLUTK=%B7SR-!eWrVlW>258FOb8a*0pgn
z-`uI^<^k1UY;!gEPJMUm8Rmph=GK8hR(p`|+;}Im`tcgSEYBpTH8|y_c)es3dh#r7
zc}5AJ_hV(=LFGW1B_q|JDxtJ*j<kf9f4v|DB-pJvNrWGES;5V0XF6yJ0*<rRD2?i)
zg*|*k9{h%AhxcB$^vt*aw3)ixlbIW+CdT87K3x$Kk|HQo`8WpU+gg?=h&*0o_}GZ5
zt*mvt>6&e0-@G5b3{$rnv&ffOvLRsmVP|z99`$PB79h{*MKuiZmQ5->?P#s(Gv*Yf
zVG7^uxm>xmopMoBdAJd(SlFTB$m+0W{(!dIWbjGgYz56NsauH(;KScu{3U21FRp<O
zE1IHuXky#-99>*^`anu>fj`M=^%|M5St!b84UiSB&E~q4DutaVHFa!Yq^XN#^;@6d
zwGQ^SjuztZ3LWrHU|qh%S?`@5zO*{T63qmO;`U<?;EYhaVv6WEf@`DYIAH1NX&UzD
zzB!=}qtIUix}igY?&69!&q0|I5H4iWOPmOs6(G!cO{-)K_>4lf^Jw)>(*tpH5KRK1
z!qlnJIY*C)zHq1-wp(caa9HtB$>H;S0A2SbFVTexO0TxDs%qDRt+>wkziP(4Tg56*
zyM%401>Ms`2i79ZiZb3ncC+uycDatFEnGadT}&GK=*gA$vepIgD8>WJ=EHSnbUVBQ
zSc;52nscA3Kct7uo-WOhcLPSj%~pn(qxmcIuS=|Ob}6Lu!awJ0?lJEVjBVX#${vb^
zz0|&Y@5_UHdVZz3q%jz%@@as62JG5?VR11={$TiOBCYYg_b$f`?*`OuWo>&(QsK^J
zyN(j;;Eve7=yreM<8Zt8<t=$L8BzK<v<sw3IjE0#U0>KoS{aHLhXN&Ss&RAXg4f$W
z4-U56j^>m4vyH#l<CDFOazp{UOjKJOMzRS#Oa~Q-NckR}W>AXk<#x;yQlvaKe3`7n
zmj^<O!{V5_=jdjcv=*R~9!?)t8p6C3bEatkf=lCp2gZ#P>j;buji82kys&0{Yo4bF
zsw~{-ssMVl<M6XRasGhrVtMHXzwL+62m8twj~UbBiU*C(F_kFftZJ=kW;g8?^l1*;
zZ$QGBf#!B|%(cWhU}6@Rv!sPg6zZ|B#yyUQsNT9h7;5TT)^PN&m*o$N?0KSplfC4X
za`wnxPJ>VQ$MW`ca-?g1KV}Z<vVE7qRBJwWfdZy!5!jbq)!1k;(Iqyv>=1%@<ISQf
zO|;}>Duo?wy@1&MCGcQ^Sqo<qZ`{8POJy<7th*5gCbC~9eS?3wZs{!bD8At!thcF$
z47xV+o2|&u#>?%rcK=<aFC@QVH!5=1v`Zo8uD=Dau=->_P(?0UBJc;RH8}oJAhtwx
zr9rH(CnP+4m|lK+So~0xY9ayN{zl;Ynx@~U#xPs3CD3z55ow?IK?J>b+X~NY-}gy~
ziS1|co|_U32sdIEH&I%t9AGx@*BtlXaLG<BPp$t~m}?;EgSksf+U|<IB;&r#_}b`V
zg^W|VPEOFVYdFU|hHf8Ju8q%|49q4tY*Knpv?oRz-Ftsw>u``PyB$aso;bD}0-PM(
zsOe;uzjrH59;)+owZ$ghlYc8^YxJBxup&LgQFD;jr%$H>1LD3nD|E}enoUu-Fh9}t
zSE0r;0q#=WYe@^VwY@49xzc7PTKCwK_pJU!M>9o6yU=ebUX|jij~nMXEPZZ5IiP??
z&dV+LXC8Q0dPC}r{8ck`L`bV@_154jK$gts%Q0hZu&ec(c8rRQUs&R`DU%*%ZM0cj
zXbALOUGNiutzRtrc&XrG!L{qxLmgO3=_3WF&?RiftMR_G#udfI%Wd)jECkyX*@T6D
zMZo#zj}Ch>s}ShMIspeUeD7LIVd0&;=SI_)3hta+Oc71-no#0;-1vjTa`$iLUN-Di
zP3){V9=X$AIJ77cW0oQU?f5&~jss{&IaI{@Ahd)9yLo-x`Cz_qae)l#*oTg}Y~Zd}
zAdB6dkk0t}w_v-fyNv-H1}F!#TXJz$Fdsk|9^Nwgu+#T&1t|(?>n;Rv>hVF=MN!Ge
z;PT^T_ibC$_6-gUs2%)B*Yc-dqK1g?Jy!=5Ek9QDjSgQQCh5(t?huRT%Xs-iNlX0#
z($(sP2M_XqvpwPAMx8iN?Fhn_9Om(MKaId><&kUdm8dMrW(){6Z+gvtn^+QMmFZ{{
z|4f^*to0`J&+9MUu+no$(_usMiLd|Sn^Kd>Qf2}rN8#W%|2D;~SqI1H%?TVA6{6ZO
z;wp;NiR7{YmmLTBb3Do|0WC1jV*a`A_rDFnFsYU+H<!gJ0-G}_jK1s*<ur)=#RS<O
zff~NQU8R-Mu#TvUN9_TK^=RR+64c=1nsfO$Uio)MWa##IKOI`}`I$Ri{+sc=TMHGZ
z&(Q81&c>v6`6oISfel7=qKs}A9JD&uz4<#BBxV6TwK_2-CTEy!)ML+VY<CEuI*v_4
z_l29xq@fo5Oh@BfrN4duWkIw4bMdqYYzq4>n(@D@sv+&Om~mK-yU;YTGCQZ8JLcGI
zkca^Wk}t(GjeaiEC6TK4hCXNlpFjO&&S$<zP40)TzCZRl<7=w&tXkLx!Ux`AT}N~H
zc{8Xpr~x(fG!bi))&-Znzwcv56pn2Dcb~MOaR*i<==~W8p7B`G^=iYEMY7n+3jtdc
zZ3eYvlzQH8r>;s7_h~w}1NJG4ix!`{sft@x=AHEYa0-94SrY<*li!hPblO}VTYXJ#
zYusus`bS;AlF>x7%YG!n8h*!ja0JMl!J1&ci>vB-bDA1#g3Ea-@0kVyrzOnQ&gplM
zcY}t_S;cVIj;dKLm7!N7aco|xZE1lo5zc(Vltv|Wb#)+L65$d0U_BAg+F-n?d?PVB
z&SRBO{us+@DNa5x?7~_!_&PA)V~V4;CCtO~HIMW7tv2Ov<4>?xSI`0*vqk@5A;V0y
zgO=IE`6UhsVvyFvG#YJ>9d|FUK`JlG=%9{v<id>v1{$X%!i<Q~Mo)pz6VL(9Z(09c
zX1)sd@9L$=H=q$4<?*7hacse)`YD656Vd1V+VQplHoB4Baswlbe|W^^^12m0_wDnQ
z+%fAQokUH3!WGZM>FsNlwNP>dj@7cV(D5y{%A@Z&zX|t0K@-h}^7`&+a3pZpJIL<Y
zxkD%Y#X*NC>CzV$s||b&Rd(CGsO15!XGqCuJPOg6aYS3~Hx1jEeMFTzW<SdHA7s>j
zBU$Z>yXF2OBoamXY9D6XSW&6UCVHqu`%6+fMVdL5^?Ge?T}<}wu#Z|QFdN?)^7l!Y
zukc%G^vvm_mQnfDSj**YMhK13`X3R4?SH%e)wE7-!_-@t&Hq-!_FjDnX<{<fVc)S)
zmUXcrObdIn&pw1L6NA`izjrI%0p^yh^xn(!yDrX)-Qc7@*7Ey~<GnM!ij-&7iulU$
zODQ<v4Ee1+_z~N3<X_HM)0EkofAJp-b?gkUWtKskYtXyz-OlNM5{}%+1@<;pCJy%p
zj)mCm=sweb|1;q%O=nCZ<Ek=C!iGi2bn`3dwhIpXg^dR{0`Byk)dy?*YNW-a>?%}!
zsOKMVX!wA<BR<IcEjkY6)uha{@4atR)Ua5y26F!;p-=LU-y6Af=$CT%R*+c@bTQ)r
zK7Rv*rlS9rjWrydyI5$h$as&y0O(wn-&b5U_Z86s8^jhyUp?Xo`=x|cDHm57*~{$t
zhTrxWiyB&+n3iz;TjgLrRPL`P2O4vk9`F@F8%eXiDQ5}6hA?(40lVyn0g-#6Jp9b6
zs?P7#BmIaNT-jR59tpX5ioO7z3O-u%yI5vc5YXaGTZX*}z57M;wKgTIpEPlpt!fYU
z-<EEltrQm)Ef1FVGL>`P-{}<omK|M!*UWo9?E6plR&^4+#|9BG$-_H_0c5qkXMnY}
zezo?cf@_w!_W=_tp}d;MrxD@k_mzfhk|#pF2%hKON-ML|MV6@TXr{4^HWmODj4K|O
zS;I41O6&hsmKyyCl1;G8t!n?;gvA@sg?qo|FVH;0QP(r5rE;W*hhZzo-4BBno}>Rg
zXBQhTBLX?z>Q$E2j6K5peVPe45Z`;MC!Yg8rw{%wmFFMLTM>hX>7sgVQAe+o{wbdP
zYz1ZwD~(=T%FN$uzI@!+TY6^xq_|dOcFWUK?GGTThGPGzK;JeIk~7EQ(!TwhVjM;f
zuMkLg{jGXsNzHc-gL<Ip4f9?qcm_bFTLphb^s(7>E$WXB55W($SR@7X#=FaHbyWbf
zi_iWW<>&Mr^!~G*LxIwi_rFS^IR{kQ4d*O63kWec{Wso_+Sw8VyD<|%;j_9#eix7M
z0RY!r_lgMSdk7TR$p3{ku*Ml3TU4w+N=}n@imEZO<OQ?=oA7l#gTH(uFl6$+f-OMq
z%UiWP-Q>mnww1eI-1A9{)j*8|Kpee{vLd4pAXQoaFN8sSuRU9(M7uV0s=jM)i8=PW
zEIy_6gE%uxw%oP$2K25|{Xccilq=(bbHRVkDEMpbS!_M19NoBZ_|78mTM((tPyslm
zTT<)jtIIt;erW|U7iB%6`uJl!?~<J$dMl%IgJj{^#z}f1DgT|Ir<oS8@@=Nk#s5b>
z#F%%hh9o_c@CDgL*3bEf{Z~($y;xqr@c65;!;Of;-6)&B)@bKjIHwRs5%ODgpt)7y
zk{oYani7ECRRvLu!$SYFKNqfNbgYJ`?o=7|>Z=qvuOu8=HU(~6xSAT<u+xJUX>-CH
z(8>smYzM>4k^pVVo5XmZ#*D44Ew9bcWb8!4s>|aE_q=Cn+vU9uj*mMcq_;XFso5uz
zmRw@<^@xi;EdUnsGRRx+p=2Izyl^3^WcInocN=c!k7Z+)*>Nnnhi|ByKd1pb)PTV8
z+8TeMfWG+6UKK`HW^<{aKj%N!0thpWe$|*wS8EU5IEpkpfstD&&GL_~4aF*aB;i{R
z46fAHp==u;iC-=tRIP9%;?ZNpmx+WRJfwr!0)CD>N=9@MCM<y0@#kT{2Q7ygdYYAz
z3j3;lcq>7hMQFWm;4wr-F&2E48#Hc%(L`X&8^`6PolPF2|F89Q37k)aB>L|WyNKa8
z-)b%r6n1wYKBk0-j0ab)gd84bD~xb>bS3voFN}T@nI%?MW^~*tr~Pn1b-vT7<ff<m
z6aax_M4>%)aXOJXca7hx6s9z6U=jm500?J^bN*h*RCfEg^Zri}302Fx9-}bboQ27&
z9C95cb$f^s1GLbu^ZC<!mrB~f9Jz<<?tTXih*DAcecQV}`P#}$k@E>3vNILoFvC$&
zsT}b+KS6nD)MdqIy%K`TaT0*OzDy_2mtQ_WTmQHtHF4MHLu-3G{s3zc(6)laUmQ9&
z;32aTkxaCa9Cu6$*mk{5tIzH?n`u1}ctFODoayR$nhJLTAr6qO9;A77(69%>BeP-a
zHD09c>5oK7;;!MiW!LVOt7u=X_;^<#D7Wq42dLe-A<)*`x2R#Vv5jVN!QcGJKv8>u
z-1-zbak@ek6;q>O*o!%@KLZn}{gT@FnYR7;<^~<Rlj?akhqj`+f`Iw?Oi|BoxBoBf
zrjzGRvKiv`G%)jwYISZIg!&w6!A92nK-Oduzge#J;UvvX8XVad_-<OEaU;asr{AQV
zR3@|h_MD|9<9(;{4fZPAE(^--n}$X<u>q?i)uLpE@|zhQ^xP?l{Uh)tA}}ubfZPe~
zz#wZ(y==;<7A-wH+9?d*zaTNzF-YlX!^67fm?g$sFrV_JOHY2SHMbpVvv-sjZwBmp
z%GZ=ZCSQ;Oc6Pl9*d^CDBi@OO236Gxdx}j5gpc@BYKe+vH{V(mr#I&K`>lWPB9!H#
zT>Z8ea5W8vC1+%2H)%v-YKs;V{t9-s0(cHk37rjBP&*qmWhwvLn9|An@LjW>+p{%l
zqR`E>OxvcsOoj``1alb43WBk1klB5mF8TBLuijN<E#SHKN3BX-)fdubl1mTxHnkKK
zQM4sd#cUB^>JGDo`J&9dT3)x4JSE3v%e90}FBQBmTUJp+si~s6Yn)?F(`r>M$l93*
zjUDxu3sfoL69q>CyL-6B2M0EE?502^D*a|~BAZu(Mxe`*-{$=)N#+7OhRzpwGY8;5
zE>Xi|9||&B?`qp%I6Syx@Oa#^b-dBz-5XDOHdv~DG^_2lnmQ$quGpX(+LlXkjliDF
zI0kGd;kTk!A~_yIr_Zo+t9<_fX=WoZE?Cr8qcWg2&Oif`sIoF|R8RD_TW4i>FDo+L
z&^hfAS(o-#44&1ukefa)Gu^L8?DW92$9e+e_W!wM;cMEn-hv+;U42*W>%Uo0ab@!N
zyA|UaWoh+~d%{eWO12%_+f^g^dp(w`lg_}|E2vmeg3F4Co9^5iqaJFT`gaB<9_ZO`
z3^($EV4Nyb2NA}6P#ub_9&yu`IBDLY`KwVo+9P8zXiL9MLgFn;5Y@RPOUEC#%CVuL
z<LwOgSg$otZ>~1&Czql>_0*dB1qnyltXc6tK00-p@IyL`!D%C-quU3srSc}&hFT6<
zwH19?qz$~2fJBOf$OI<S=`&ftUp(g>-o!fA_d^{g-CCV0%|DoD82E#nb=o3;QJ$Em
zt$eEE%hq6d5EZSHY`ptx4kd!xbnA$gV53yIRyF|ooa%j7zNEpzXDj}K%m4pCA_w^H
zOCz6RvZfDVTnb|?*zr`Qm0OPO46sAd7JbVQQmhWhduN}u&+|%-E+u88BzBR2w%U97
zX6bpSI6T!F4*A%SAP=>FFwleL2n0nb_K+I5*j`JgLN8{ob85-T)HaM2FMzIssociC
zxd!m?@~h^3=wm0_E_PLadah<%w$Ke{7uQwBcThc&hn`c#-VeD;JtRgPqCxDTpMN+V
zosdMxtn{8D+eHE!1UdZns=<7MDee&{SJH^6Ge0~#gz3Xd8Y1xV1h8-NPYZmIzf~^w
zu8bG7Gi{o9Q0n*B_?8&VSDF8x0e2rzfU@733oi`Qjm_h6!>40X420xjfrD3rpmG~`
zQ$6(-Ppg2uOT|Yzx1QK(-p&aelZ(08=fWFn?ApoX^>uWEtF7;AQca+6K;DP_jzXK%
zqa4$fhjeMazK_K^=5T~qLMA1Cdb(Xypb^YF;T123#03^5$bkHK^$cmo3g5G4bo6ki
z>6IRgY&Sxxx`c<iJKa7OzBG}^pH}7A)t=pqEbizZn7^js%H%qP6~X43Efvfg9Ty%p
z`hxd0-HK7p4ZPJBKC_*Tz}QMzM*Ir^$LZ=lYF*j3bhusk1j^&(I>0sM6^0W0AD~y6
z_RZA8Lg{I3n=MZXh)WnvZ+veUpKhP7{f(D{t4}wx=|nu$ea2@cZ*uDHyJe+*Gms%9
zLC^!(zn<e2H-Ag&5saJ`@oCbp=9;C3!A+Nv=d03aZyEH(#c@J=SokMN3xbH@|Bth`
zj*7b7`iDh9U{L82>2zpOkd~GbK~hRUO1eRY21!AXMnFc8p&7b6BuBctq&o%}_<iws
z-$$QQ>wW(eUCWs(_WsnqaMhb%aFwyCFjra07NnB3K6}1IT3<!`LL;qna{o@3C9|se
zIA(;Lj9tgr>2di=IQ2|LZ0EXZva!;nv-U)J8twfNv(Ki_gt#5T<o=0#<W?nO9*s=F
z>=bjK>yn}lU3cy|jJ4}uGC14<CJ_HelOF`$rch?D%4_Xfs8X@WJh?o3Zam^~N6y+J
zk9ca>EY7vwaQgI{gDhTJ7VJn65^~i=KjKr@L59an3d~?dOU~5{XP-RA4ig?^wN9z!
zx6V4bmzEC8ThHuOoANlJ%&rEAn3I8*MVuA4GiW5~eSsw?-KjYm;vcdC9zU@=t>8$L
zn-FqTsIm^PIooOGS=x&dJ~GR7=yaYi?qp@W>bpbk%ope23|zI6UNxQNA*cSpox6<W
zalrE^|M8ZqeiQRE*=Ht!ul<w(D;ZVMUKpi?=xZ2VcC?$WT_GsO`UdLCHi3>!+qAb+
z>M~Iz$s@dq$;8{#Ii(7!E<pc4L<=8v%E+$NZ*g+4nrMs1&?`M=9m^cO%cSzfSanO{
zrtq_=@R5v20PEPQs0Tlndei6@V}3iaVk4{k;?3F7dYu0YkW0z?=Zq9WB_meS;R@lR
z2+LyQ&YDzR`{2!?FET1NGlwIHXbrh5=$&)?>>R1q2~5n|@0IXGy-oCd!0{1R^fDZ^
zq*gx8!&&*2`xfWY4Ma_X|7CU#HMN;lZbi6;g|V*tvC&nZNmf``9T@`+T^tLer0tW3
zO7#yps+Nz^^UFxJt8;eY=ev37&uVnNsC8TqtvaGV=Ai^za@zMMFjEwyHB&t2VmkJ}
zM}X$v4w?N&Af5H$?fGsX)-PUe4`_N{+r(qsQ(PaBQ$p`oKHOB*)L2i3<qO0(3f@s$
zw6XT2!4`j*EuPG_iwZc6WcN&$|G_J`xizEBzNTs}58L||x;^o3+5<4dP@9_(b<dwW
zH=~poj6tmDjwWj-Dl};hN258^e8WSDTsirb*7lb%AhnX&n$BT8uaAotO%L9uE02BE
zwwbB;waA<5+U)#wUoTGAGvZ7-Ge}?sE}Qy?cgT5|Ug+Kbn|Ev6*S?#*;q*OHR``9;
zt#VQ1vZ?b&_IAb**%<dYEzgYZx4MY}3aLl~;jBk+BHxzdEG|O;29OR8J=&Nxdd2};
z$&4N>Nv5z8DTC(^-%bKZL&waudiS}h?%gY_yJ*LWEGE8NZtl1mI}xFj&pL<Vs9Jn*
zv>bRD&o6zS7}^q{`$n!W_WbFWoSYSca={JAzw1=0PlYc|B+!3}W`7;wgJkJ7R}IrJ
zaYCn2i=?fU4!+B%t0%6WQU{s!M4eoSms*Dk7~Z}6mbtxZqs{%JG7X67;hH#3@%m#$
z)SKan*ymDI?&HV~&zJR5X_3n<8lzvnOC-y@K-9oKU-*0AK3iL_p>#es@3`p7fBXPD
zQng+MNM?U#D{ktPMfP{)#j}|d>@*kn@HkE*aReH%)QTD<+>?tAhdXwSv$ATBCSLiq
z36O5rxqq!u0Yru}-CCD<M1e{f0{|upEPU6@9fJX-E4A*;`Mr@tWqQE_33LpuM9_;7
z{~ZU&6&iGEe?QZ8vDS9Bu~aT(#!TttyE#^@Vc+Bay3PH)6Qb^*YO&bksL^5E=ovpB
ze|{O#{F~$ZLnokL<4GI?3X=Ai6Yn@1dF^U}L{(iYqDz0@3Dsxy-nH+Wn$<w*Q+gZ6
z`n#*y?R;IiejBw)wJH41HW)`{Vsu0UyM=A+Q3LyfGdHR?oL()=VD+G`cF2L~|HBUX
zrG*GxgyDR=b0<a?Wv@obd3S1VJsOB#%Inl`o0IB9RwAA&DnnZ#D3lretaNzd@oKb6
zW=vUYqcr!#-R!5RDi=Vjvw+-Eq10d730YqgG7mrB;a;EAcR?5t-&RZiYBFYbjEeF=
zd91swYcv_GBr>RW+{E2HM80@t{%Ks^8s0B=<cm$XK^aJC;sxLDbxzKReZxjEni=7-
zGU>q64vYR9SLQ^EsFK4^RE_|68*LY(Y{8rsxMt=7-x<#?l$a=W)`IBh%Bb-Iw({Nb
z`x_&$=!&hAT3k7iX3pBVEdWwFtjS=3sIAXX`xs7-qF(z1kjPRENFaI?%8<{cQtU5m
zKx;FX-4q><41+V`x+V+09uHzY^GY776KK2Q`bY}#ks%etBj>>%55v@H2;-2E4_9<O
zUwq9?9CQc*<oddQ2VTJGR9@$_zP|*=NkCo#<OsQp!SmI`sFsLlS<#7KP~oeb>gS$`
zDvd3=UatHJrXn1y%K&tZ>UN^GDJTJ+iR+Eqs%L!h#VPh5Vp7Z<wbvDz9xqa=P)7+K
zS4PKAmOLB?&QSec+w^T{v!s}_BiEy-3H&8WfKOycb-5yO*bd-d8@a_j(`3)P1uw75
zHrNfy)<12Ebfw;I9hpkF=Tgh9{kk(<x*Rqc!L<wABLB6w1S7{^l$y-B3o7^fUMGp)
zsaF*B{$6Hi5H$D@S{1RJ|Kb$hHso?HQmlJg+Wic*w3JZvMg>7@?J|n|chbhctH=^S
zGx?=+;R7>GDr2UoL)40=bY7;tB*u3A&+RXNH1d)<+p@YVMYe+dk+@@jA2ZXsgE{(q
zWql=gaq8eV!c9SwoXrRHI_Y1#R4P-iD|~r~G7XhZ%Pl(n@mlU#o(BolNW=r3*KkIj
z_Gs4pDruEEKrZ=sDx#`o)-s>a&O-bOrt`w^)M{K~qN!Bp;Y;a>har#Zl(MqEspeBF
zv>Yod2y-gNInPE8M3tId5x}-m(}&rQ^7R$h_**vb2<rbk`H5I1Li7Sp?3Yk!4Jgro
z5kR8$)3_+17bo8Klc6+rA$!!xA@n*Z*=y&Opy7|_)m@1e<Et;ezFu?o_XnR`Zq&L(
z6G@GiPtCt$J)=v)@}>FA5)_0328U39z)(vt80K9;!$KDl1f`=1sh+QcLg(**gJ7@)
zf&7IH0UiVoLTE*B#=XvK`lP})IB`R;IBAWkxGMW(iGO6ZH|X0pSgs&Fc%Rg626{C3
zIyaBwYo`aIX4xoumZKOv68ePeWQ~Rf@_0GFJ+4wBLV$N={=xUlZ(>`u1s5A#p9EJy
zscm3VZ4IJHaTSpu@YK;3u?0P3XKJSAS_^k>qQN5^ZbRGkj*!IXckr?Lnp4_~xXaTE
zybh9Gl1NYx2#LsoC+g1b8G)K4$y3$)N);DJR77;_g`5@+;?V*GY7cymCZ0(Ksi2*e
z@+R{VsFkQaRmG>n-xwKpj3rW0z0b>#jiv1V=E1N!b9O^Z)(8@!<2FXKiACIUTi(91
zlzZ6o(uKOlV-QK`!20AFmB{#tV%^%?deMviRro^GXgut?1VU&c&TY1m4<bZ(A-e7>
z501fRRr9TQp&eu(Eqo)Kzp=pI?QCFXX%9<XX*zdeE1Xh8j_9or5t3FpLul@F!u@$r
zNkd(354Q5!Q`HWvaT`H=S~-lXPdNTmwNIT^St>}fP~T!eONB*wX<@y<W#yi8{F&44
zyv}$k3A=q4M|F2C1i5tK<*qOce7T>yFcl9IzZX;c_HfrYNRgmt-J_vVgwn2s>UdY_
z(viM5c~;jAe%GH&zePMj#MB^{ja3xJT(M2}O86{yt<V@v`Spf>*HklS{=peC2ppYp
z%Ze@>#HtchK*HV(y4#5tJxzrGk>=xD_u=_ldU}t(8tf}_n$Wy;_f;tfIWk@KIQIYV
zSHx0YYL(}75*#krM(lTNjEQW%Hy_aHdPiYM`y{FD{gk$bF0ml5{9n6ft)S{-I&=E1
z8tuzuxAq17O}v_v65-?Vk-UrLIJtKJ3KsNYQ|dWC0nM1Ay?s$tu=~tF!D$iZy$223
z^xyo|=p9H!b+R_JQ!f@@mc3cnf6Ou1<LLwi;eEk4)@=z{9jmrsyIgLKIC+cbGL70(
zirLFgEN)nFS{oO3)``ww9Y)&syxbtrZgkjw(S_=y+RH*vY0K@9=S~Gz$w1}Ynhwj4
zUlHUoNfwrNYaM*9Ug^+)=$l9QjEI~M$7%01g=p&Cojr;?wW?2Sfd<C4jpMc)&GU?s
z>1Z_^f}Kd;KSDbz;$@c1qE}|5H>=;2^k*TyItu3W%2L_^lEkzGjh=amrn1A(P6Q4~
z1<7q*^u%|W%!>A2wfoP?wfC1ROP(Y#DT1mDrJx~rrI}1dRw7W4<iaN!%MWdGVV;3h
zs{<38!+kjSb0zsrcCti<0UlzrouXMMpn=K#oMocS1G9eKkJR`Rbs7eowrW0L2pq(f
zPRKyTz0%ZWy4VuC@a`5Orbk0HLCC{7Un$9M0IDg1m!1M?AyprK9=<;iZdI1IJry`+
z1TBPSyoj@|3-`mN{-KXP?b<G3J^Ew+e8s$Y-CBfGf5fB}l-f9+40C75j%L>Ja>r%j
zUOB?F_s}6Y=sG}bLw4Kc+NUnQ7mHk$D6h1wDfmg;ytldTwcLYi<Q9wPk}dGVC{F0o
zd1JK1tiPmkqU^#Me!vjxwew!k@cXRXZl&Dq{H#)bS~<#KFuB;76*HY=mN)8U(ld%+
z@HiMaPmx$h7FGiCMI>rlLhce_Xg`M1{M>EYZXLJyV^@}JmQM{+)^FEUq8Jz2+t<E<
zg2Cd0DT!gFafq4@9ITdSa5v@QiyhqhD!-yH?TVcl#dmLL=mfE+6<pKtlfodL%@`OB
zeqm@_?YzCZ1vv;9<##hL+rGe52g`dScjI)_RxwC8vCK*HOD!pt@%+Y1EVi9D3#+vc
z5A}_ZPilksYE(m0NJ-6*buI2lRDt29^$ff?;!BZZD|205&1gw`3;~46!Ueh&2~$b2
zMQsYlOX8^sIB%`>*1NuBeD|Jzrr<Mu{dQxZhCnzm&4K&@qOA8J>^%(7Rhtb{=QeOS
zosy3?=JxS7<MK}FoFR7yB~=YD7&aqebdq+o|LgRD>{Ma(9>pe=YAj#wAQ873al!>U
zGdBn7Jicx|75{nk^4ngvpnqfjezx~W|E$PhNZyGi@%d5ABmLIBB8HN_-nHJin0jQb
zXo~9t-h#pV2d*r85`SMHF;)JxijPKa-s`Pjd$dm<&@!pf0w3O&f-4C#h%`t%n*8nZ
z82tPpEEwkd>Y4Ucb<p|mwKS>}W^cGXU3bBQE5H&rOgn$Nj+E!vH8&{jbh~l0<<|yN
zy)UJ+00~otoPYRhSzFp9iOGa4(>V#>M;tb~c<o=eeK<{g`H`f>S0*;^fP(^Ga2RrC
zkvn~Dw{**O(T&f&(PJyXMP%RHJOqq488dgYd)eb;!OM;BeaT_jS&E~L*J-t80*ejg
zytaDtA`^0+PvgBppI!L&<2s>^K+&7!q0;*IG0nncPWpV?9LGQ8w_VE<$`o`Z&hmb1
z8IcS-ffT-mR=M;h4WB<L&gd9?o_#xMe{2L7f}6jpAO1QZ4Gk#^c|fAJEV@&&oq9rR
zxnJbJZ>QI5v%j~LH8Ol6&~yVdiE8N*$tx>1lj>>stFU|!0Y+cNRFU>ulix3^Pql55
zwQKvUB`{N+`x<=U0!6>JxBaE^#UEXbD;Odfb0KqYp=<JNa8Ku@iURRuKxA97bY}jP
zLp?4UX}B!n;S1BLHD~MZg(_NxDgmR~=D}cGc8{*O#u%fAl)H4fE!cRt>(TftEh#9x
z&}Y;<z3o*X<MQ!07JSI;^?d?0TTF6c+*v*LMS8j0LY_erhN0}>7}~F7Tf>$fPS~4&
zl+LJ=lT5E=fjYGIPk3DsMGMaa&pzw(dN^Rrbn5U4ehXF%Tz_LFV8xJamcwGC96(c6
z;`6zTms5W4HdLGP#5FVA%yz2zCe_M73gi%_=@u!XV*&JJ;2ilr6-S|`UD{nh_>RMP
z?CU-5Z1uOIid^B<7bOGsxc-Y1|80@hB#G7I6cYGHh9>Ogsi{L{TWAXelrxk+ezi_T
z-Ld7Hs%*ibWKMbeRcVECv|9h-zD7!LTRJ@(p6D7pZpLXKKQ+!>Lt5`86a?32;d%8v
zxUz&|+x1&2rt(V2y0u+I?Ouw$Pm^f|8+SQ06&Y5{xwG1GU?_#N$!LNz68M&vDVu9I
zG1yA1rE+;$(1YTeL<2VBQ*OUj$s+#@Rmu{Kls0haVHpr1b$*#d2px=sMd6psIMc~W
zN)cBW%%R{9(1O7+z)vZ4H2&^OF@qg)s^kwKVYqC_$qDNA&d`IoQ|+YQs9dR-Or~eu
zsNOMy39G5tOV1wxTA3+pQpEjZ%r;XSWB>Iy(PZPbB(L~2@J?8suw#0h9v<(eK-<-r
zvv)QO7Xl9Wcb=yPlHvDXl}?QSp~F+mn9k|L7Wqnt5lPiXUG<;=Vpj+f%n7ljVmdDj
zd1r*jjmP)29BycfS+=4_F**9~s1Df?;i(3?{^30uufbYr-A0>a%oE_;N>cV~5)%>I
z&knm&9lN<ZPOz$L=!&`j4%s3Zd|?EtPO*>sk>mC>${7y`)QbH6K2RTEQ36`QU}&K&
z>Q}oi2qmpXxy%S3Ao=g+dXZgPPYdar)Q3}gjHerg2UDgp5~%sZgq?(kL-sPiFQk3L
z4F*EqBQw)}vZ{>P*UT4br3=SjZytLgC^eE{_Q>ue!xjD&=<RJBaUGHtf+KuOORXnQ
zXzH1ua!xy2R`Y}F_U$zJAHtKkwW()G!p_B*lb4Up`Ob{mbnmgsE09UT6!F#GQri|P
zH7h2t<F@$HdaZ^i8M-;4S;2qDA5mCPP#0x{Fw*hza!!VtniX>>7<^J`n#I7`oL{$l
zBv-fNW9)aL3h`XZgc~U%J3={f(8r}u+a_ygy)NrA^$#z<Z0Nf+LuT&8s*I1_RK^-^
z^@d!u4xD=zZ`2};jG?ni_MN4C?$n8#b!SO$q=>J(+EK!ijMI+ZE;d_Gd#-;)X#Ehy
zDZU+_;62;=NS2_^HKD_W3xMMn6#yJ-?TiNfeGsMagTZWSrX3HvauUY&Pi1CWJ0;VU
zDv|jzsEx0gGny1#5g}l7<6BO}=+#x8kwq@Tb(Rv}o6l11bLuWEautY99Zx9@<+*Qw
zWmV^j`}mk!C9oTDzsxH|!S;qTMUnR1O(64vTx4hFzNizT`WSm=i#fI+Jee7kqx&Py
zZ3he9^26q%FNbyhU)v6XxUc7JeWMZ<uiw6#@AboT(HF-aIg(-@qW$=-<3>g9RlD8H
zTGeEgRQx|JaH#U~x{i+1YFRla&p}wR{VK5VvUc{I6&r6-NmFF4_0EH4s6B^IG_}Ye
z<5;QsgvtSrIf4j%>M*Id7K&-U?)2V&duu!Gu?c|ejSkTe(u*#e@Q4{11p}{PtK*i=
z>(KVEL14wi(w%v=10<VV1(nd3v6?FHGR^;c?e*l~4?lQ7q{fTXg26##f*Tb^Cv?J&
z`F?@#yPXQLNYb~bEG|cP*|ke|-PowZz6LTz)3@mn2{M6hAb2N+U3iwK=i>OJC;HqF
zR9hKC`s!drzoZGJq@UB$cun0xM6by;y(4Z4+Lt8M(Q~c(s;X&QFJ!{=RC#T?XI~ik
zG-n&`9gM+`N+<G+tjk&s_qX#@FXmZIk!XD>`$1xUe5WcUWNDj!bv!zJwUe}z!N3Py
zSdsKENg9WbWWMKYi*5Bdi7s|xC<jpYq0@%NGTP1-+jtOJV2apNJhW8JVk@r2dTrMA
zKo2jF^`&zlrOVy|+NF#XF_p?w3cD?TP2pqV{X~SI^|u|Jmr<}Nq89;UYM7KF-*x%V
zctvkYPWURlu3k)i5`sxxM_VTCEfAj|Em|kP?hHS&%D1)31t2@EWK4sG!%9_oK~*Pe
z_h`b%&B+G<^lxyF!#C^wpMDgN2&5DJ8w$g@l`-N^q{yeUYAz@AJzhFNJAE-zgNF=K
zWnI+`FLQA?f@1=B5S8CofMS=$@ihb^Ex-txqXG5ru)?C*AgoA1F*IVi>WvdA2dqe@
zWLS<htQxf;jiRR6hcQZ8$3Nj^giFSReMXfL%F=<e3q>z|GEsFdH%Q#XFlC{jV&D4_
zHnQq3xIV^fHO(1QfZbUp;0_wwm)uo!0YgO5H^PI5-^Yu;)eKM}4g#0pr1`};cgN}h
z;MKnK+`4*OSys4RlyQ|(z{$=<Xs^bGC+E5Aec98<_7v5ui=FEZv)B@-(5L8hChWE%
z{a=9pFI9G-m9n@!i^40ev3`kBV+PNno)KNtVyr5UdNRu|Bc*y9Zpsm44IGYV{hC{y
z-S(Y4g7h^)>8N$j3ylq-)?1rpzxY0p56l;#bIR!nD-sVNm&F;GITk*eLX6<+<}1#~
z);|$|9-<I+TW4{ForUfQJ$|n;G1W9{s>iND0GVyXku^P1FQLrMrKdFT8R9%}I={vY
zqg_2}ci-Vw@Hps`*VCMnTAh_EdJdIqZc{vO?*C!;adN(0&(VQI_{W)ZXNuz~Oh+rf
ztIp#T>9_{%(Wy=|P1zhEOJc}A$IK5dU1htU4pSkXK_sncWH)3wEVt|x|AbV5?(IkV
z;_0$!?GlmH1Ztgx`SrD!AHT_{`pkmZTp7kxl>=PZH)J&GCFhV~=ed$GIm>K2?O_65
zhHSV^)sIr>$8deNa_qCZ!3jWZf4R{=o;fGi9gE3C{1M?){;!q25DMC{4=n*CnlcqF
z*6hMHU-IvcE!`>Mu}h31oqTlHwkn@W^kwSBD!#Mt#$$R<8i2*$7k3#%T#_T8@yHt{
zPTA=4n#dn-&sx*9ex|(@hjTW{uzkl3&y$7P|K7PoQN2ci2z*xC;6q3V*dUmmlkAHz
z`K;!<U@}5QC12wEHM7M$9p>A;x9^^w`oVm?TW%enPFPW2-Wk^CQ@@F{@ErL9-zVZJ
z8T+M+D5FE=PT*9huxr*?iRG3{;Uc@yI^!qu`Fq9*PDJeTGenT_qNa!vn(Ungk(VUp
z0dtsK9C)%uk0?-r9vuJ+(EuYNUZZQDB4@$t)0wen3+_i-6oi(|C(10!0T0#NCD+qA
z8IpJJrw0UnzHx^fZ@sIT4IB)<^jS9mcw&f{s+&vO&1%0ZKKQ@3%m8}Vc;|K0upDtp
zvMY6)AiXw;_^n7_&#ov#`@v|Y3mdL)yZ6Vyh@&%uCPzo8gZJ^%q`NNyt{tlB3Z~%u
z$s{gOLkPPHaLht~=de+dQ7{6h8zhJIW>UoGTQA<l>6YnX$q8_ajLMk3^7^*JUHKsJ
z*5h%PGJ`{`;xbugy=!MdL}hyNcxv%ZmixXqaGDDLvC(GfR8m%)ib&ejjHHc)f+!Ee
z=+UAUAsS9__9vHJ)zmAZdKwo%LFmtB;4G%rh^TO0#8eJQ*xZoOuaU-X?2PZQ-VY%k
zxBLq~Usn#O3n;?+oOYQ5^4IEQ!Z<TBzPB6eTU}3+T?j(NN^voBeu{`^+0Yo8dFS~d
zCU}EByfAe!m9)>VMm!jtOLhxaPMK`LH3)Pjw(~6Ue!%Fn6v>#&hQmVMWX1qIwS01c
zK_{Du;Zm!9hDhDJ*6}6R6kWzUG7q=DH=@k@pqjeobbxF&-dt;RR*(%?+Aimh+bWFq
zp<F2{;qei?oVUr`vu2*Xlfx0Zt&qsurIh_@vbDXA{RNAw`h2lEaZ3de%byICf>6y>
z9h7tNMeixEnySyv7PiK#zM?e64>7Q&7Ot8&+fPnet>}}peKcVXo&=7?Bo_(TN=$uw
zjjRfFP&vFXDE9-2ums_%O=9i52LQGdi3s*8%dhf1`m?<<1cN^~+!!uYw&pD+R>K;9
zMs6Z3<7a^(-cF$x%Z>FtE09#9JAT?TkaBWY0<q(VZS1#wG20(9)>_sR%T>sT@eR7U
z7{K_Uk&$dZgdL~Gn}K>L*`oz?l=Jpl^Pz&ODy^A)lCBGm^rq1*t`GZ9eB>Xv*D!W}
z4Zm}s{I&bj`o14boQ?R1S%;fPouuj3ZT0cd8pC(I+P`FykSD5X`dB<(-WLZgFAxVg
zU6v5$?Q-XdQ+N!CEV?q|{aImLnnmu3V3Y&1?%c5*cAEl|yyh;6P9(;NuPoXeeiS|r
zh%tK<&f4&pkg}l36b2^qSYYa5$d;Uasr3(naE1`%bcq;>CYN~EvL;V>rL$0NQBHWN
zVQi_eAT;mlG&0~rhWEw4EoX>nu39h9e?^10G__P*BOJ1<WNSciafp4XSGFxyps+19
z?}`JJ%={rL;iKO=bx<Fand1|7^A0`zVRQLVl9;J+tHj}kC_Hq9VS4|2`|dg6yrv0&
zvk8Ndlb=$9i(81P_>giVC2sQi)TzubQ)qUhmue{x_7D=L(K&LAZFXb`7?a95x*&CB
z7!cJG<Z)9Bg2p;3I{X{)K;ACKI-G!RDVFpnVaO&>y9W0Y@}w!Yk&5{&LQkhD#t6d2
zog<5-v%gi0>5D@?{~;H7q_G_v`nfr}SzpvI;CBBfpz1kF+Y?c7JjPt(KQs8AyC(K7
z&VTU*^O=FHkt@>7U^YAi+@N6BLaVdjU%}ci+to>+EkmSpO_{{yAun!IRPT4so6nCp
ztC!m}wO(a0B6&T<;Sx!Cika^viLHpGXtJ+0f%0p8&l<0ZI%-LYlk2I>KEo&VJ~{yy
zj(CH3lBrY-o@yj@-BBY0h*h11+VCUZwf^DT2TlP5YOZdt*U?$C{VgbT;<e((7?qbq
zZS$_s4j@pjqIgFwtwysvJ&u<qE8zkI|Lk&V_>#o0q$-{C$ytn*8C|hyo-I1qcx~vL
zs2%bTyd#VKqzw&WLI1l4zM{+acotlADHez%b~nKA@>WA#BrxrHf|TgfF-SX=^DDMU
zQf0c^%mkp=P1iRu&~Z}q<6+WBNQ))Ywo0svA+L>5VN{X+C4CJS!T1w}j%>qBnn}m$
zVwrq4gp$JS0uqc~IzyK0I9E&Bz8^-M!kzHE-IZLD@)f}>oEdlDusSc3Bh6}f*`LLU
zA^SD@W_j{c0sxMqOI<`z6jmES<!rS-9zb)!O&~JEtR3I*IDZ4CN4VEc4rH*zUcr6V
zbLeta8#&W^j2h@UVXG_pLOt6W#9S#)dKbS`6f1o;I{IkBac!g}1gz|;b@wLQS{fuO
zC-DhhVmR5u$FZ14Vqrch9+R14Mcz3#_K*e!f0SMVWkygwEPj{B<VGK9lr)tg#`OoN
zGU0GF_MicSD?a#xlrx!|S)DhS>x`wNluR_&+yQ7JlVE9V59?tlh=Z74q$3%}$|N@S
zs^XRw0Tov(6fALiuzP4zI?Y5SbO|Xxh>|yCBP%ti3Cv<n(Y(JMnq(a^ltA*6vrY<@
zU1o;>U3a5VKSj#&YD+QVx(0QJLeAN+IVTvhgTw)T{L}a-j29~rd;HCm&X!~+KX||3
z{2Uiv!{CaLMkZFl5Tu3<r>8g!%OgY^U4H;nsDLsC9^p4r=Z7H<2aLobJ{?9kZKDM5
zo^KL%y*7~i@T$Q81GHs?^%{};^#iFdSE}6+#s#N%cpgtMO*R8Ib)(dn)QkMxvyuQ*
zAzd2*ME)ISRzf-3(OLRLQOzfMpzCo7&h31OP`U@J0_57Rg`BZv4A=W1h5i$zKX6oL
z?-tMd3pDwWb%~B`PZw+Ca?Cn>6y2){hX0>Z*+|Xdv-0J_{6@<sXv*wO{J8{F`iXK{
zf%u14z(#<&n#MBq%Zz;(k7~j|E4Ooq>_pAFZqo9Bv;93uFSp8s#P7HPD^EK;w76Pq
zWSmec{m&i<{QP71SmByupjEjOAollaim*Jd#mm6FVh`DLLEx5ALq<2$X4$c|y;bFV
zpru~Sk_TYpg}L#Hg7SkCPzqz1DeldgSLz8}2sTc%=|&G96^J9oEs{7TO|!9Agm4kM
z<htATnsaTX^1eBgROEy|w&RV$XvJ=L;Q8Z}MHBv)bxsqys7j=0#RMD*V$~@~a)~Q&
zF!BjaSnYWP&7%nAk7Ep=!j<y;kG>p3F!0H|3!Zj90k+Yf)MZXe&pYtieCCJa*?vCO
zrCs~(_M4+76LM$^*oIHtO!$kVx%FFxgTQR&VH~@Q?E+nRS)4-AJ8oJg9c-nu>dXx|
z5+<w?u4J<Y=wiW`1wU}#Qt36heSvm*i!q-*oOG00Uk<oG;#b8-qHTOoAzODR*8iOr
zZqP%cHl<z<+&)Y=O^HIar(VWe%_Hh_kL87t;`rHp&42d3#!OCQD;);CTmZ3^BXGp8
z^C*qU5QT%vYrfM238P;A$b3VWZ7bx#h&r=67S_sQ^I*1agb9}TJv>!AEh!9XD|hoq
zYEn6Y!S*(^sgWhIdE=^Yef(JS@%+FR$^jzDc9?N*`i8*hPPfpg8L#+3AixhgUaD#d
zJA6&DZ^E{o`_Z?xf`Ma*+(Fg2iBO9q^DxJz692q+$na7;N#ZsV^|5`?Ew;_D@oeBv
zb+b1_K_9z-Sb6Oz5|7;yLOAcv9qD_S2W#3_(cHv;wP6e?A<Sc|P%GQK&g34sol4)P
zyV2fbCIYA43`u6>%-wNQkREj?@Nh83|FYpmD^xE<D{{|GOm&XumXPPuj0cdibXkkA
zu8LB)(_S?lb)0~Cb7kId?$>8La~}__KQx3z`fM7uhc;uKam7#&XP4`oG!?7T$!@PD
zgFjaPyVOS_>NAh{X2|Of<hZ5Ha74FcSJGOkG>F9}Uj<-twz`_l*5n@1B+qX3?R671
zZ!?N6WA_KFQ_Q#TMB$<Nk}LP^1#za+2i+nUX-jtKGrm9zv5<BLNF~5I?PR7}plR0X
z!Tw{~Y+dD><vX)2rRhSP*MjAno3X9Ee7&1Cj-IEG`bX2Fyd`d)ILw#bq75p^)=4Jj
zDVg{u@c{7%_*qD)AI;$=i?CMYh$~<jyWJPBx!><r*$|3HV?t!!_c`<tzM6N#`vY#Q
z@tX4|4PxJJH&SheM(p%s8w9Am%LPfILph7K>S+#i50YzOa{(lc_uMzCQ<V@eRnbnJ
zPff-H-5*KXp6(n`3L>lUC#{5&Saop!p*X8_|MYnm1&75|0hdPl$64Nb7lU#D{NZ`5
z=@6s%bvrUQrdN}T<o+EBX+m`?<S&3fDwsNTO}65mJ*f**93&)GgN3f#@~kGr^j^U>
z3=g>0pz!tS9tiIh0Z9%=v*cqPwqok@vHf##0mAQ^Sxq7MLLe^ns9t^vT`^UI^A)%7
z6#+wq`TT(t(s;JE%J|2PcISvgTFxLa#DvL4A=xPh(H`LF`mEY*m%g$}-D_W-gBJ(!
zAa~qga%Jq@dPn>vAfUC5e_#Z(hu<teP$bD{+#du7opaSS(%%A{L>gc`6Kye&@4*(4
zpxvzp5)JnuHB-arG<1G|%k(NPW1p+R?F4QWkpr}z$-|Qem*0J^T}KazsG<sOYVHA)
zhQ(Im@Fh;p&5i8DYq-~fD9%4;3ZZeNzO{PqMQesZV-m6;%{+L!Vx@B=nY@tTo$LMX
z)3zmCpE}nkIA|Hc%6RMu3Bso5cp0uN3!|+OwPZQfM6*1<6$doEuju%U-e#dN1CN6}
zx}XCyudYyBz3Wn@6Lf3+aZHuO5)j%55w^r$dA!rgohD3IS;K(UYaH!O@=Q;-8i_$(
z{9Yw&tS_J9pb_IslJSw@n#rq{$bvu}IJEsx&OE#le0$4k?+a1$8aiuY4`C-eA&)f*
zYOn2yXq(S%J!pT`3OB1YRecw$N~^_hn#ty3D6K;Y@o2$E<QBjcI16)YyshboaYY-$
z-#^pCDpdJY1GAXp!f&|AXEOBqB#(+%jm%xPnKCmk^>OGTV<mr?Kbd)7hej^cKpbtM
zRF^&C(w)h9c0PfaE*((MjChx)+2owK)nGIE53qA=zOcUHxKboZ4qxLn;9PT)B|Iwf
zcX(M%=oBFtv**8Vvn@v3fBjESyE6vp%19{=Dc8okPDUh4@r{|Mh|U`kJ*><pVZX_E
z*K<`QXr|&*?VdbIv#h%qwz%#&m_-3^TxM*{?SoMiu3<UZbjQe!qtEQ{Qo44u9=FP~
zCzV$={UnV*!{kfxeEVbDLMk<!(#YxSm3#gVu`Rm^0L*Xf`|;+RTl^W6F(Ok+(&6DT
zM+(+YK8uw!WH7O+#@{p04Mn57?u4O?!F>bGPmQgNjY}+K5AbD7*bq?+*@cPkO41*j
z;Z1&cH+v+e8r)Xf9SAr(DMOZSOwJ!j->(d3$@8U>sE<m{RnhfwjWsVDV{gKpnb)ZP
z()GpDF^-I_o&~7@u>tAto)f{*tV>MUvm%&$*LhtTI3FiWwSmY4-D@Xj&r1GMwh~};
zMSeq^5N27QwPu`$dKF_eJ;XoH0bs}|iZV!6{(}HNB~XJ}H~3cTux8_ZrtG`n5?9vy
zBnYi3d(U{=W9!m1qmmu7qKiQ^2%KADN<E^UJ6eA0@iKZUV$D@Mj!{+>dzWh4bACzF
z?bXnIWW~~J;2&0;7a8Y#5dbJ3m3+{R=FYcA_@D8<Rt)FXm5-qLl3ttiA3H7b-Pigb
zJ8w^@_KcE$*o$gDySoyFw*5AYal88!y>My;TgIK#fxja##>GByIxQ+<@pbk`R$B>t
zq6eJyL72sj)ECc!d5ripe&%BUFK+L9h22&|Z!)3zfUAVUgHiVpUDl<c2}7Jz4nPl>
zPX_`JQLyVRn^<td;75j1#FJ)4`a^OAkI#SHKIXQ2ZhNEqvSq7iX|~GE1$hn_PWn+E
zOsaE<Mc^oPcg-lt7@8Bw1(+1AGXpX+>~Z@xAcDAZlvz5dGH2t(wZ@i1K_5FtO%=*g
zr&PXGfJ-|5Yi(1>k4}O$?Kx9f2Jttnfbb+}&10STn^yiAR2s{z*sNnlDHzoyu~a;E
zJ84~vQv|vI>8~z8NqXmAd~v`?reaQXc~8C3HCZ72^Ej(RQ#%HBz47+wbnTG~sbXc@
zCAB2+q&scZMu~&ps2v)UxZN$ZWj}e@`TOJcuQal`+(J-S!7TN%uYmkOJBr%G6{cXt
zMUP;<1Y!Y)XHJaSw)fzy_;FCD!AB*1|Mff3$>E$o5Un^+yeyRZAnQ9a@n8vb6|4AZ
ztA2nLjfshND$HBh=x&%yIY(@3TahcD!~w^%Xf@EE#pNF{EKA!P!(%IfC-?i}!MatO
zn?DWLQTVwY^QbVZZai54&3D7NVUY{W-5N{em65d$0^p~?+EC8QU0&-bva?XTkP7Bp
zy>ho$24&;^5-ky{?ut;OrMYiLN_)t(iz))O&lA(NkZ}q5nUEM}l8Fy<Mm0Z-0XzIi
z^S>U~e;>XHmW;7HrKRmm2Erf!3B;T94!EEJX9Je5i-f-IY??@$+(AW}>8GXrpc@4J
zZDFY!1HSTk*Q}YF<ql}FpV(46FY}YCgCo8*t&#6(&Jpy;)5)s3Z8qDW__fgX0Q*z}
z>@`Bji9{#}wc}-`mq9zX+&5MuBp5*EkBHTpvdQP$M@OT8%*mdcdG3!a>`w!~?+}w%
zeH(ff;0UwCk{Y*~ik{iKh@6VEao(QRIrb|^4KCzWBBK7Y=l+La48U{;aIuxQfQ%oI
zE+b&Sp{$HS`U(r2PEVy!VfeLrBavdN?u`1!!1zX$cE)3Bz(dPf|DF|!XjbGlMDv-&
z=S}3bSseh-_#STEuFsn6HV{gyvsQnNo(47DuH)ur4hD*E5To=p*ZII?5tC2Vr)?8c
z9nCUlnno>LwE6NZ+S<w(cK!>RaDw@cK~+_)<Lb+fN++gwJrx}qrxtyeK}L|fIc`Cb
zChMI9y%w9#28I8Y3^Yp?D|b-UTIExeUAVK;aSvKzi`>j@j|n-?PBC#Q$h!zzF=t|a
zM;`xs6{ON>z9BzJ;kNBv&%Gtq@cEv&<U?F#BfwwN1tcwdkDGStSGk+K^PX)ZCvJ&E
zQY!;vke60v6V8*h2oQNg_qvgi$dpw%>L_N7n)?Vk366U2b4_e&f6Id|)@1^vRGB~J
zzP#49L^dDjRC?I5H&k~=BrflZ0F{0nn3;ig*j91N{ZvhVgr8KGgtgvsh*X5LstL2A
zcjZ|X9kU1;TwOCw#Y_z2aeb+v^6_6JOaZWWHYPu(xi2hi8yP==h6FXa{Ly!?l)-=J
zMXpj#48A~0s+S-bJa%veB%B@%7Zs&v$GOHjiC%Wqo?mE)Fa`C<`>JtAdl~m=z-u0A
zB9YV()Tj1kVhSw9l1KN471I8Xm<m8h3@R^Na$CpTTL6+(KFR-G8T*xfd@hsS3j8w4
zYqFAJs{fLNjDvRad}KoIH?8nZYu;A^5=O1>+g?UK`h#yO06Z9zTI74_Xh!K}>L^p$
zB;e<3j9d&C=q-+7;EE82F1>CPrZctyywkJU>Ut|xRW~3`=HW(T9oIt|5U}0(yX=s4
z2Qn&sjQu)DUk@@jUX*c1egSF8t4oACT2Q)L5($ImT?tyjS8G?C&LI`E_IUrZ-(;aD
zYO<u!&&bXED#tng1+M;D@lQtw3);!;r*wE(Y>43!3<O(sGwiQ?Rc0*O!?MW-qmh|n
z&C*+mN!ww`Hme~{`SRtptTC-pa~N^Do0mYt$=L{sAZEv{c=gkAKb10=6)gPSvCp2b
zGu3kdVzp}bH)E@*_nq)m`(inrUY1XlN{`48QPolZ9ozUjP6!VH2LLAnuT;h;?_1)Z
zP9#3D+NjLntJE0QzN^m}P46*-!ac}Q)O(4_AbpYe&|+@jOH*fd!R6Y^GVAq$V7tRB
zs;kCaaSvy!9SXhroB8pw?b!h(pzjMK*Umhf9$de*`!%t2w6*qdRSAw@C<@$e`D5il
zu?p7OUe$8uK+0FQ>DcJ+enKZnceVO#f5Dx9v%H1SPIrCOSgGYuTV_wqlBjh<6wnPJ
zk;A3!B3oZlFRE2)E7r$NlB`f6F|(jsoXpWOG{Ld016_KxrzbTqnEiC?3y+um?j@`?
z@!R{okI#HHQ@&B<*Zy8BQ~(Ap32*#29}M8`Zf28@U0$v9mM(8J-wFLoCA(`OHT-8>
z3Y#_iq$DtIdD45%GqeQgTs!9Uka57?em{gGL**WYs0Y$v=NA{4l*`AdZ&7}lT5DGZ
z%|_W7mB@Qn_A=lX++1!+CF#B_4_yl0m~;Olx4{PFCuLj^9}6m^6%$W;lP}3#zlDZ?
zVLP{UT4*azI<<nu%Jj7MV?;d<`RXg$;|lhSZK@n(84oWPQZH85$-O$%L{hKmThzVB
zywQwcaOx9DYVTLri;7jSpUmJ{KB=;)S)eUH3iLWbi`irK+CS5&gu%o;=He+xrnlo<
z#@|ZK&7HyjiCcZ^r-53$i7n!@+6=w$!45guJJYX>Nxh_XJ`WVVh(ovoiRsoo@1-?b
zO*(68D>nAe1?hJ@4<>|8U++cvKDOVgrqW+t|BAXwiD;553;eux3>L~uZ39ZUD3847
zpWo7k5MKEP*pW=5@qbo8S-?ZRxzW%ZzIP@Il|xK>c--Zvw5;X2@?}zw^)`yHe+6Db
z3PvdATBcdzsj*0CwNM&nGc>yMh0i7Q4l@@8tXuyM)iqtwq$^pfokyou08Zo+k`Y-p
z2?)gwspl774o>frAQ?)j_M1JGKG*Tozj<xM9NX71etBr!-+h&5jTwIg<T)VI$q{vU
z7W<>vac4DSI9tH1%G*f>QE#br>vC-wzVqDMq7_XFH-Pxfjb(LhE8SJH>*2z1h|@+5
zv~WlFZyG8Iyt4DdYw@$32fm0)0T5L_PD-wF?25^#XZS~K*6sC}T&l~U9kYg<*ZxOp
z-5EdJ0##ARAA_yJhvSKI#!3Pn(TM8x;5fs>RHsHp5u08pCTqrvSaOZBi!Vw-jLP2l
zt++F(zumbjior?Sk4{niJDs_TDd8a)D$wXT<f33jGUWi?0zB9DwSfCPE2ofY8+g5g
z-@6M`EIVeG=t*1LZ768P)T=A6%sy|tBqx?Q6?HF1={3&G``_=Gp#jr_;&6O|vazzd
zOHsC%TTl?!PT{Ah^8j3tg|3fO9&i%L7)s~KzQfg#8O2X;lLbA0kYC)(H8lSYgXfel
z#af?d3`|{dW_`M6sm0%~dhf-Of#adPqEyW6N|Dh@{?=7SX{F{kYw04u;N%vNeeeaL
zHS4*q@QC`Ijeg{-aa;u?-=C{4{M)Ky`(o0ed*FL)0=;<oOyP7Hu-r9oKb?7c3IG`Q
zzIYKEAhVKx;XL7<+9-tQzXu?<*qXwo<2fKb^RarqN*gj2^aE=<deh}cWDL5i^4*=O
zUv}8Y*Jp=LBe4_G;bB1S7)({WqIEAm!qtPupa0l>z8Lt6S2r>Me$s5XOv*8<l=Gyy
zsms1@gtaSGa1i+HP_QL)x5h9c08W^B0%;*WN^tBJq0+J(12RzS`}VAAo)>YXs*lT4
zyh3p6Sbra!NC#(!W;NmPt(%y%DTYF(zw;n^Gk_x==i+R>2*75D-t)6Bg;4=D9%lz#
z8AFn)b2_=sb4#BOwS%9O0FR=a?8!nq7jyCpRH-zKZ&UE?`W2dJjIcvQ|EBeLYE(L>
zUpcE?3Q$I(b%4w}4Wy7he(l*a@4FE2?vmJpdU{)cvkyjHL{r;tgt1dY2ng}|mxJfu
zZTA2p9Ix54iFp2!Kg9=Q|Lj%D$*}8lZcMr9K+cOEk@RCA{*_6DpU074!wQdV9Exi<
zwxhLdV~B5hYafbGY3!1Z>VoL>5Do+cw;fd~y~dsS!)#X}2H<@SQSnl9XtkLho?2U2
z^<(uqtx(+>3l7%aYkt@($H>cYcNIeArL+tiBnr*%Sy)WK6+zkmC>ir(W8>O<I3mZ8
zAI5SEg8AD5Tv389I`s)5b!24ueW+Y{tvmAJeCg<3P=79$0i(f*0TAZGpiS~n#~3g2
z{x0r$ASMxg6Ji743`wXQFX{u{(z7}vb}m-_7UJUWs!giP>tU{8M->k%&w}Gn$f$Yg
zmss9HK$hNc)x3Ehk5$p_LSQbMr)K@Ni3=fXPi#-rS*pjBK7~%~cuiIMpJ78w1=U^a
zhL`2Hc~xXp4V<vIQ{v;hiq#J)@LZ{my9}T^K+@&F+|?#HUwv*$-PVTMV>nHe@qMtV
zvy;57qF2l3#+ZHpl8kHrE&!_m`(l3@ZwKE)hceqVa5FFV`@-y(HYUI^jMqq4KQ#{%
zHVEG`rt(;&tiQ^!d4JnT^_a_m7kRsL?g2{~;dN@73(>qIcg;PC8H73G^9z4Lu_R*(
z6a9!;d2#WCc%@Vgh^fubw!B`kJ*V?OFBd^|#1#PfaP6l@T772g7&`Z(5Mi9!aV*v+
z)4wdrwFI82roJy0Jqx6|L^(X{Kc`IgC@pBi42IwXy|*U^waVMV6+^FLz=-|DobC2K
zwhC1fj9Nt{96f;t%M00UdYG@?xx{DbV&OSHwxLBN;QlEBFkJ<?fY^Gc6cC@?*&`Q8
zcD-+!;*eIoxJEJAK=|%09OL)^SLj$e<4Rll%Bj>n4Gae?^;WxPM}+p*7_+7V0v(>w
zoyV`em23v`YpLC_-ct7`KD44DbdWTd1wyvJWpuCB`N8}oHhd2_xZPYKu~Lo9l*BW`
zgpUtkMji=Vu7LZ4XX;%;ldS_JGV3Eo4ZE(xb-yVQs99<OdG~uelz&&aC#w8Ag<l|J
z+2^Nwezj##kf+BOGjHhaa5HSttsFvth9=Tvck7-P&aAXX<Z*(UD)Z!t_#g$q83mfM
zl+RiKi&BM)<)s?2n5x)lA*-4#cK0Z`UW1eo-&a{h$r!&o)IU-qE#KayfjI&ZM;rOG
z@MP2@&8m4q>Vfww@Y$_*v)!&3h3%$5MoyXV?^v9eXd}-}R#8hmqP_brlON{bLMf&K
z+hg>{+7TDlv%3-yh`csQ8aiMH`4@!|AN1wgreE|eFsXqfwB4p7c2n2~frrZ4$WOJj
z>w!y&`-h{e_WFJ{*EM`RDpDRb<ojF22}o{)NZsX_=}lkuu1@m3rsm#r%#@?EbG&k6
z17MN`QYRVH@4Mabn@b?NcfTteHwm-*vmAk1lwtbh{vs>D(NqHJ;zZ)9kINtgVydzP
zrGWrT1c1X5Fd>IT{m`W8yio^askP{o8IwGp2HF1%f&mtJ%syudNf(a)SXWC>iJSRz
zLS;tzCYy+>fM+de6oS>5=rZ9Ep;^<-_5nus#`mwjkSq4O4DOcWH-u`DhOer@=ZjNo
zKSV7uN)eI#>8oai0DjbKrtF5F$d}=m_oQd)?Yh-uxZvg|3Nvxr<#a8>io)RKxsR?%
zR_oQkAV%9c%{~D)77Kxz98TShUpztzA5aI$)7UuOEva}iu25z!4ejO+LZ#psTqoez
zPufPtGDPK~F1Ga~4Knmy4FH$Cvl!GGyX^poC4hs_(rB0f`NE{=p<8wyMXG*siZe&3
zmyR=2{0}e8?Pxx93ZPYQdaiiYFCkY6D1d;iv}4bns}ASvA!Bx%qgF3RFK<<ABy-!J
zmw}Ao6;=SA>n`P&U23=9xz>ADuTurYwNu>B7Dji~8X0&+=sB#jL-m^+h`6!iYf(F)
ztVYO|H}oWmW;g6WmI*9f>K=1f$u`bVZ7RVrdT{nml3}AC;-rXgdiVJj53>(Ti$7s!
zKUJ?$mnG;A8u~Bei0R-fiG=L~BoW%_w7<3IrdxfSOB5eTJ<xbaTE`~w)|ESGMs{+<
z-%+odk-ZDII8!T|%0zp2*2hM^UkoZ|-stk`x1^Ow<PZbiZ6-ul($%!ZdT<E1<~i+c
zTKe(SJwpa``LGZ$?UpJqbYbLU7c3=3#qmvi959qU?!xt;#%^d$kHvsqHoNnMuLiHI
zYkTH$vmoCh!UHl5v_-x9N<^YR8x3%YGva@SlRI2;10X<R#&zz&NBchRk2GsSoRL%k
z!A7!(TNTuIxVx?k?fXBD0>%b;|1k&}Vf^T}Sh$ro9wQW?sKyN>wd;g-Z&;=TAWWDQ
zcLZN=>z%dt;?|y0Ew-kcA<IQkx?9HzL^{i}We=lqpq=UF#So!5Gp&5711%2Q2@j<z
zrk<Co;I3l2U0lm*3mm8aZZ2f|Ht0q(k8)i&$;!V_^)XVSTHfE42%fmB{>4A=Bh}f~
zihe^t5nCj~V;;8}tVNlltDGi^rb$vNW@zR-O8a(mXh%xz*=Y=CcLV6cH(`^gQ(pDH
z=gFPie+Fh66kRxWIqiOw|DXVZQv*&D)p6U+FlKP}6HU0xjs)Z+<-z>D%lUvf@^m0V
zJjro~%n_>8KC}SaXFfgMy`gZ|V-sf^63dFn9o?Y|y7&;M)Sb)t!3rh{1aWmlPH?_%
z*P3-cnl{GrxhHGn6dGF{M+I@YQW?l3W42d%x-h<8I`)3j^i=<A`m;wy^(y7=L9VwJ
z_%Owtj8sbtae_SWR6=Ek0a5BhW3638u{?|Der&4<WuJH4MG&4)`OYmOra-F@;NhO$
z+mJJp?%L*pwOP)kZ$@-UdF}nc#BSY2$@)s`9`DTsx4>t*=esSH5I`+Ktu!0+d|Y|D
z;-bKUK##ndz09OXhtCJZJkXKxJmwN(2;u_V;=8++ooj@Wq@F7udTr8wgb=IGs$ixj
zTQn3?Ecwm8W)2)ASu6UTK>UjzqKbiwc`~@v?gg}l$wV8kL(xe)ijN0=XRR(?3;V8i
zB>i|Vp5}l#u5lj4=P8^MnF#K`y5b$@xj%5d&I>f%JZ*VyBnFao9s}lm^<hdoN`bq#
z_ykVM8e=+yBew4LoF+9cti%DJ-RGr2H+9>r?ig?I`w;Ui)>du>YNoK<gP8t}+5l@;
zggvOi8`jiCZ~>?=oHm*XffLeutIVtWu47L`t^G##Rs3jbg1FK=!==ddkEU1PWq8rN
zSVIjsUsfGRPUDycmDqC3kbEK+)741v!8`3-4$(1O<~>BjfbjJFYC72uwzm~_8&349
z;{<rlBo`>^z-T~+CWR!i-YGr0<eae(>l3^OEDoz-{FMtwqCdD&-)S1I-{J_B39Ds^
zYg=SzqLb7}z3wZ17YefL&kfC?SzIhWWeB?G%!a^J&$DOy_{fs#I*yw{ERMNC6V2`I
z8@y#E70z)w9)2^pP`Ol3l#wxiicl{?1ljU-j=ZmmiJnt|Y_XC%QG){3{=3NhFSe~p
zcwslCXsdIU+qH6D9URHKNz5Unbv%D}h+weKaowpy?-Ewd4y-){jCNYDF$^J=FSxUY
z;M1gAX}1bgEVzSCQn(5&Y1sOO&NzXQnb4be95)krZ=*c*N~{OJp*-iBG(G;2^#nK(
zZxEQm2nfCM^S#{mL^9Xk^;Kh%Z5&VV4|q<XUWRUfX3!9efsVPy2Vld}Z1%Ikb?OtL
z$<Q$&`S=FAk%cZpH{_EK%jq*W(_e7v-4q}H{PEeo`IQ{2o-zZvAm5tV%JhRpG3a5q
zWV9$4h(h!xKa3SUxks}1QHW!ZXzhRadGtaDTnhsCpFd!=)x=+*_TSs#W(&dmd(K<g
zA1W6O<YB~LV>p}s8bp1(p8I`fBwjv3kV9QR@#pon-5$Nj0sF$5<lOXTwSo7t{qjVQ
z_Np())a6D`ulHz|?HLEHkWDh<Qh4a)-n%7iB%xn&AMi)EthCfuJ_fF!C7Gt(GRCK}
z)T^WUe1+JmXNz*C>?Gcu4RNBEWKK^VkMd}6<c7$;B(}hYh8#*?8}4~%$2(>-nVxXW
z^$I)x+np=jHa}5Zcz8>4ivB;%ut(Ylyz+<W&F6Plm`7@#%<_nQGbkphJ~;ql>OqwB
zAry6de+Z9%?Q)jK*}IFnw!xXV7RSK+_n$ezNF@d0F5p$hwFug>_#T`RtC_|)1GO$-
zsQ&1Zu)aIiFLFik0GUJwyi+?`1mrJlofO94gd7n|T6i&d{I<6#`+Jie16;&NPM;bU
z+v!b;7gH0fournGh@Nt&mooyuMWobCU3Jba!ec&nHns!|<z9Y+v+_SSmNoY|?Yk#I
zoOm>MuHo{P)v$P;T>RA@0B-sey}I~Ui0*i1W~9DHUAt1FprR=+Nm#J$1tDL}hQGE<
z7%cjD;2ina*S(t5wgM&t^KBIXdCJJ`$@v|<4f+SORAHk=(WXst>^RK0)SLV3DyrC4
z-7Do7@DUcli>RFQ3qUVCJgX2i%8(ztJ(`qy{$n4|Tt&_(X9qSwG!3B*zz9{+1VDrA
z0Z?=<0_U+BE147e9~&8{rHY<d1B|W{No2HK4V?dqigIM{6umoPMt1KI(JB7r!205F
zuFY5{Sxu&HSJ21eg8m<8Zyguqy0wpEAP5o)h{6U$1!O3LkVZljlrBjHk?xWlkp=;g
zmKf>o7<xoXTDlp!yM|#H_}!!KefD|x`M#g?{^n0*=DBOFd#!6->v~kUB$pM#i^_RH
z@YPa|d_^E?6BP5B_p~Q^a@*lbhPS)E(3RA>&iv}8_jwW;m5R~HM6iGZMUlokPiKnM
zCwF1^_5R44sdO&=MJE-vhh7Om!=&-hA9>9?&?4(Av{s>!P~&AS5w7#KU{*W5D_mHS
z89Aj~TD75g(0S3Q!O7#Z``?%Kq{4y#-<awrsEp%XxlTA(Zd^C2kmjl>Z2P(^%B3+C
zrE43oIHqM4Ja6=qLm>aWd34ktV!iUc=;WaqOcK0Ps1BoL$<#dmz^W~67V@D~Hoq=O
zN%;Ir7P=KB70<B^Xj?S$&DhaK8|^}MsK?Q!44RD7{lVg6{*^ZNT<uDL20<eAK<|uB
zsJjcMhIf5*vG;O9`LI6mkR?2%^4;E72o>88(4Xxof<3};kB3OL*X=ej=zx3Cot{n8
zT!+WU<?s3f|72i^M-csoq6LWYn23_w8mP6W(n;voy7^Z7l_!FtbyrSo7ZZw#e^ms2
z9!x1JwM_f9@d1XhS|cu~kb{o~1bf6Vtq%3x!L`Hjn2e4uGK$|Iyd<#9tzMujy!kn1
zuj;DmRPS{=?OG1_UJH-KWbeMH?MG_fs)ON{jQX#$ekxbAEh{niU|lP8jh7@zPm1-u
zuQ8L*@a{PKGf&5Wqz!FwxON=MR)mY$`bb6GUdm-=XJvjfVpb4dKA(|s2`O9Atc^(>
z5a;o!`u{WiRE6X=9tq!ygq0yOcPP^+w~3MhTn}`&{_69`VNzTtKWWpG&0-qYJqF)$
z+0Gq(&~dU0&*%=x+rb+*WPIZNZlmUSv4)VSbh;8Q3Wz3;zAul~8d)+>xBMZfza~{w
zOvpb+=ekp<q3giz{L04(A*CI&RY?vd7k<N4!KFq|c!j~6*tj>>hg!Dcv4n5v_WGB+
z$dFi9Y0G^=Yq}P>ig8@?_<Y+3A**E3DBcmf;w%0_)jO}zp9>~%9RX)mGOG<&%Qt{J
zgUXdEUi_8P|23%k&&9q^;sApS;b-1MtG<u>EM?H#7}5y}fM6l2u9>O39h5j>4f}Ft
zKnq=CZ{X$k&9^Q{`Gl;zUG0NGD)-v_K;S$xd3cD?aG|LI9kn9q!OxK@|JFr+M^f{p
z-ruurfAX}mf8z=KS=YgpPfkb8CZhINd_<5AlZMoA=^V9_(}~Y~P9O~EoG<z$bx+m%
z4hi>QVD7&)O#buGt9n{ZWyb&*ej|}Z@2U1^A~WcnrWSNky-U$b&(%i!*G2p<!4;fH
z!2DEw62fU$I(Wwf*QbeG<ie;Y*em6C)P&tKaCrUG1%&>i^!OigzB|?TwrGzJcT|fE
z`jUYXMv<MGlt?|Dlt}~X&%PO4i1(|Y1txxdumDzou*#6D<YvppX`i@{`kW(Z{(mYH
z{9{d@s483qQWN+H2$MAkZpQcciFHtkwQe5Z8m>^)JLLf?59bwqru=$%Z*QMiL4)bQ
zDwx;*#ku)Yb_T4%{R$^5z0)4o%>-H5E2^4&rgMFq^xSvUq<^Ix#<^54l>ZJ!|C8jE
z{l2&ml!qF3UV^4&C(sDEZ3vW9ZbZQ@fIcdH^omB}@bTBH|8{HQ6nk*g^Vv|L-XX*U
z?^wmWa{3`yjPbWe%aurppl*Ja|Jw)@051j<$G=7M8#eNLKqod&S_)`hROu(UZsv$q
zxAqxTUsUg~@2=ZdOq<npL-C1(YTThn*VRfRE*cGl;GDGjqH;l=4USX;3!>rzL1u=A
z^WhxoboDBSa~H1AW7JB_=5_>>bL>OewPM*&UDVJ$*fu&6*1V#D?c@^K1l*+$^X|ue
zq7$Hjv$g46taJNJW4QvCgEf5|3S3|AlR%7yvR!L?r2Ayo=V%j1NSwx+S1Mi50=-ZF
zL%;~2-|V$>pT@1|-tGso*@BCHeXQEjVsvij^IB;*#^&T$gYL!uqwehUg!q5JKSXWf
zK>3DilhtlC(+(?Q`E^(nNWxea=(^iF?5#}<Ef!$VdX|lq6gVH=F^?a@;NpwfYB|kT
zfm%pKf~@>-H#EVz@}~$xLIw~pC^}@r)pi^vOZ>VsjzQ}$>NHdUnrwzF3LgXfXj?-Y
zzsI1Y&=r_~!rk=FKr1Op>8O_qHm9~Pi7VMuW0Q>7BI$s(hX|Qs<6!q9qt(HC3?!|)
zYTXjv5F*&LvRUrLg~D}qudu2fKKq@X{fo5#1P7=drW<vS$DjwsEBO_f+JGmi#C7cb
zc4+?;`1p@z1WGF+hZ|P>N$;YM0PWGRdL8Z*9LH@(k)gZDS>xu5qq&NR`ky7FCnQhB
zaUwQABeJ`|d-1(LaKY$@8{9aA6-ufWdc#pcZ}S{!SEL~i!OXd3K-;l3tHTZyRJ>wp
z9n`X##s7k<9NF|1tJ3Oq<7)isTZN{EleO{{%+KR6j>VsuBMQK+xANI#e+50vo9hkO
z%wKQ34Vz3Go5Yo~1=ZA9zZt>*aa1V9RnQIVaLl{?V5jk(O)bT=#r*0j!)TqWf}CbQ
zaqj=dg+6*w=($2IdXQZ0w(y+4KE(n<%0CUl=IIJ!_ljI`F|jQT5Vt_)i{7W1p%Qi9
zYLu@8X}dgZX?_R_4v>Ks{wIio!KTRG%kRtc5DB7W-!7Us32%Sm8Y?)x9NBg@zxDeV
zrQ&=|P{t7upsV3lJK12-J#hA8aChU(OHU>m@*m()q&D<?WzdD1H=1yiXD^_fF8LFr
z{+EUi5o7lGx{77yQ&g>4z74T-s3TcCv<|a$v}!O<^ndc$Z<9jJa;%@(r^%3WoXvg1
z$W=j9LhkBwoK<4k2?}9`-L(h%IkMSjw{K~xldFE3`E=vsM`^7Q2IomhgcbfZ4RjpR
zwO(HtMDl?jAOCS(i(Vt|+rGZfMGQzz{EKD~egKv;oIWwqL!r;fU!!SflR9Mo=P4Es
zgf#i$_^SWiMMGTkovgn5Ty$5=tXKV*!TZc&GrtJ~=SSqjm5(HbvY%I9!<FLDjoKGm
z%mXo8+D;?(!zp9BbzS7QPjDPL46Xo?%RZ%M1_pkfqSw)c?zBTpuoddCZsm^t3<SYm
z!3Oxsb&ZQ;&0xq{qXG?`G(uR@f4Vq!Ku%)`ggu;hF+Rlqx9gHvwMpeEVDLO;V<DIQ
zeru~*$K;A3sG?RHfYQz*<HF^aQb1mYbO!@kurGt|RlasD6=$>#jG9W-nx}kTO{+;H
z!w^k?Jj7K$7PU*KeW2v3{_WpHU_*n{O;yrts)xD%Txy_DLMtySyoYjD{Qh$PXJzpp
zRE>Y=wS{GWVNYesK9ABppAUCdRV2jm)UaBc&O&Ne9Y-r4C1=|9E~n@l2JlPhs;HQN
zOq%T4DelINl%E0WHirV1(4`R#UH`Bvl95xBImjgG=C-I?ZfgIQAmj9S{^T0c{X>`N
zKf0~nE2`oO2OwakZubgMF0cbFiYjSTG@yZ&aHh*+rY#&=y$hPLAANslJ_V|AIOL}r
z;PtPVI&ieMwt}N0uKaFKzba6}j0(!S58~H4p?k*W=${o-K!r{Mw3%{;vCTpW{o@!Z
z*+e@a%HpJ)U&|k*9=J8~XP)>o1^#)NH{Hy}<@Go=%tl%}SLi_4uhy0SdWGF~FsBZ5
zf=>JBTuo4jaLEA`b<E*SF2t!SXDxYh8;$~F5NcjFFu0M=qT3cJQMfcxUBE?4r8;@E
z$AZ{7&*&w#&FBuKO|<(KINZ^hnZ--fX(GXP?5>-;+5$rcIL^(aVoO52EW)(wEX;Q-
z-vNPvX&-fHU0tjTzmfeFSM(kQ$|riu)yWC#j;l+%3*#qZoV5}E$qxZ7vFusU8)pkb
zm6kHo{_pVVh&oVe-K=?_#>w`7@VZZARXj6vwPtB}Ojg?Mfo=yi75O=GZd^{tw|?Xt
z*+!tq#PB#l^q!OUbI?k;fAQwUZF!9s;?+1&I~^xQUP$&=P+dIQ!;vHC?im+4A$)E~
z{%}1Xotb&IG<c^pV5gtqeEOh;lLOG9a?fXHlLIxyja{6UP6+M&aoiP-5CLs90KZnN
zwqKv@%Yd6t47SMgAI!b7T)aTyPLuO;jpvT)q0m1~s)|zeEGofC_Zr3cv0{oo`oE7z
z0?Fr&ad%pjIu!#5$Do&zJv)hO4yNHa<v4AS@7DVFe0g=t>BscB37t@`pvW|OTKif^
ze!RQZ#zV<q4{WIa070X8((#IwM^;3geUkv!TW<65#umj#H=H-tNxUkkR5d2<Tkb^W
zOJs1KJlLW}8CGnK79bfd*BV)icCV;-oO+SA2gvjX<P_k@NotNG*<66y1KW_I^Ns_g
zhh3n62sOrlDtNAnM<*O{G$2a&c+3J(tGDkJR|bIID!`ItQ-fxGa{w67{|Mi32ruBP
zzj|g3h}_rOyMJoR{TC65e<qFO&HPv@Rmq93PC$#`C%O8&f{MwZmAbgk`B#pBtD%ol
zz9%kdQh>db{Lpwf^Hs;MashtI<I1ZfG>4Ate+Ucw**P{Y=;(GCAUOB_t{?XghXS4&
z0BOQU`uwi8-;_{H<J71-k{U`IOPq9{0xUazM?I=@r9lVlJ$Zhvh68Lx-8XpUflz{{
z-c>Hg?q{FpPOLHOMK!;m?CHs(*$?C<?}PvM9s$V#z+B}#<oq)=Fa!lkYN+Po;}3Mx
znq?-7Q8>-N$!u9;vUP#kwUR;jZn(x+(}HY~Kjbe#6*@ETClux#|0`sDGy8F}j7|Mt
z>v=~)k*V-7Oe)`G_YKIV3-Wj0%Eq69w7Md_^K-QzLmk_o8Y3t~8v#DfAOL0WN&9ox
zH~;s*L-GeHs<)fFaBZa5QI!Y*{fzGEQuVOA8sS4LfV@utn%~kS_IO=`)&~!?h>Ve4
z3}XWOH2z=g)8A9+J9dirb?AA%jTsXPY<47?Oo*;}2<W~Q2^jYFx7N{>TZo?rlW+o)
zPy>@F`ae!W{{gw`S$R%qf0^ajD2eE*5RL-axKYWSbkf)I!7gvK+(Eu>$2gZmT;q1O
zIX$4Nm;kz1%Z-1~#r{$4`8zNX*!e`oGZd;Z8^Uk%WwkdiPOC~^XRS{5+{#3X7MauD
z#g?Pp5njSDZ^_8c42CN=pI11oJ-jXX`K7`C3T*zH%4$(8s7b6YcG?HW@!C9C;QTP*
z8u#r(+||4Scvc+GX4NpiPi6?)8_T88>QdABx=Qpy%$7pF8^2TjYQHJ<=?GV)snS{%
zA!ByNs}$d9c>H&N-{80kKsM&(T^M2l8h?Utpg7ku`WgRUWJDTX(?6;Sq^h_zpuu_`
zr#Tu3&FEav1C77jN6TYMS@JKjN+YJfi&gR}E8<5Lc=R}|Pd1SVok*f4)uAC1UOb+&
zp#mqbapqX3>&nT<+w6zTw@s*8+rZ3qN@<|YyZ#tTk_sY$RgTeHuERH*@`K35`+2Cf
z1-bwtl~q)P;N*AerP?SBOVPKWiX+1XKXl3kpBG34++ODD<;il!+0@cHAK4U@6EX7s
zmJ2G8@nQnZRG>2X`Inrjnzr@GfaQ+rP)n~A8b=-fC9uhB01o0|p8%ij+Vy;gG2T_o
z9-jf~mB?LYazVq!;mdU*uB41RhMjzymb~BEszyq5s^2`v8m&*3#8F4C?URf9>ra)y
zMC~~oO_u3BYz)`<#B>T5#`JJh`*AZf-Ow^sa}ivD#PJvgb*nf*9VA+A%=j5#&2+X}
zH&2Hg#%oiwu+7-NkG(<0OV+4k+d)2-pD!w!YRp^<34qD_QJihmz*+p_oEOCgK|Gs6
z$Ls1sEmk-`+ooxub`kn0gDVl$TRS;J3_~3ZR;!fByym3e+6abp7BzV$rzZ7bldfzB
zAIX!KDz^_-bpV2|kHB9!oA@YH=-^O;wrSyK4$^Jb&fo;*v##cjjn-h$GT!i*F&s+K
zS_C#v4#a_fD!vx>e&Lji1i~<m4c#;hvefg$yl?)ZKYyC7?MB+VlT9Mmp$ej?X6XTp
z92A?fsSP_v=IBngvKm_AaIuIrqNK2R<+GV~kT1!x(b(oY-HkqEUa-3dqxT(N56tRf
zK4x-aB7Tg)AIp5_HpA(j{7}_;{zmJ3cjM?CUM>)(6q&?}%sk@*kb99w`HxEiuL`y7
z+aokE-v2&Ksv@*!@Qc3`RaIu<^gL!c6M5?kG+!J}85Ciz0PV>Ly#(9s(tx^}JPCj9
zJJPQV=l7QLm%C`+TOSCf7GTy;3{4_%a&bzwP!8Ac)fjCI7HNPWA;M3V18MVzvghWY
zo&2(X-{DyIX4RWcttx3f7nZ@HtARLv7msQGSL|vxV2`tS;}r97I<Fa#=jleu;GB-~
zh@wFP+C)dJkQ2Z+CV(32_^tMtIy*op1MQqkt51j=-A+piFg1Ll=zCF4IK&J{In{`J
zbapyb0Z2b?v!4|KG=%5cIswPdX_k&`{s0M@Xt;Jkk4`lxF>~RhK5_Vnn+|*&8>0o<
zQvwo#Y~ho;6<l_pI$#M}kv6vHbM)sWZQlKDoo?^U?MUmamgh}eH-gO%o)k{cw~jKL
zO#8wd66INt^tU8OBf<-JnoCXcdqM<{x^0)j{3^On4{g?Vi5Mk|?Dj57yAHt)oLrNZ
zMr$*)j=$FyIR<os>5H2S1W_YrFaxP5BcGQuR6`Xd(g~Di(d0Lwzhx`buK3eONEyH6
zcL0!%Jz(DMLZ3>%WPGb~2X;IA5BozgnD6&jtD=_Qtzk~c2L<!J<np-c-{Fki+UP4M
zzO6&XlT#ph*A)rBr@B@BBo@@#oD!-WLkCK_JqQk|-z5p%eAd#XV=zCJ+9%yK%DzHh
zNBdV&6A5ALYPiQjYOhn}<Uq{eHtw)IXn{TH2|T?)B*Rb0)}HaqhNK)h3H7~2Kw_<T
zvK&6VNGa~GG?f>s=MYT8chIeN0Cyd{d)*2pT;-zvx?D$pR|0e`EL%_2`yD#Dm3Md2
z%-EG%40X95Z!{F~US!<)-CJqH1lUv@<-^}{`nmE>dNUBk3vBR3UCdEUyU}C>8_YNJ
z{_DeQFvqD^(v?7WX|@k|oHPJiDc|+2k&MiPPd4uZJdDHn#DXi?I)t}+V_`SFtBOb6
z<0oYwkZZ7kRJ|IpeRT##Fb|AGck?L6%GEm1w)b1NIWpK5TN9iABIwOYK_^8r`Hfs|
zlfg#RP#SY?&D-TP%a)^k_b~zzkx}3ny7gi5gp4u)MbrtkCnGBz!&azV{;7{=EDw(3
z4Aw8lvEb4xzXH)03!wRJMpsA6{aI%zPQ7!;47O2pK*(t7`%BnuRt6-~V}nS}!7xs}
z-7;!U(4P?}JEo#Izb+45EFU*zg9Cv&k0zPYHNZw$*u4V_%`C=&Y}z5y%pYnzSuS;^
zIjr<{7St4pyxRo0vR(+O@Mli2r4oNljEYg_y&X$D-O=i&%W8?Whx%}A`PdOJnaKWm
z)V>~-*Aqg;Be$JC0x<Q3$i#u-g;sSW&IQib9ff<F6yb_3sV(!$%#{tHA|ivRH?8kd
z2r6BzVDx4|<jHTI{8C5H2SPOWr(!7doeOaiFvmFk?@g=hOk3=+EA|ACYMR@`K?vpU
z0i>?kbk??ymzc>=`i$#1NR9?(IPKM4!Gk=Z5tO5(cGLS?x)O1oqM+jL-cX`GwHiHQ
z>83g~&caPgp6*`1`)<&ADn?1P^#sQQx36z87-6;x3HG0>?T;dh9Q`|~e-8T;70Q#}
zu#qrsffA)!g_cZ}ks-h_<*_~O=Gtr;z3H8K{g)hl7aNcvA&;3{sQ>YRuY;6?vlu8!
zU575)BcKEE_(jFmZT@y{VDN3Ap5sp^Py0RPIb$%@U9e1ampX_1zS=f9z$<=cBYv5#
zhlzg%#^4;>xtN=Iwh59e#BCWrc7)8a>=we<qfe>DBj^a5T-QdLCUAnl$So5uSyS!4
zT+FtYhG64D5I~lC=gSOH=;5}_Q(nx)??91eAeh!wGnYi%|MPF@@fslg*#-bfy7qHt
zhr=0ERzC+qS`vjia2*d*J8SAp+1|VJx3bCEn&^S=_=;-)%CC7<w>or6s1B_rIb-lD
zBZ0QU6{bm_Bi+y8#`kXv4`}w3afP<s!$p=kF8gj{T{NPQ1AcGvWbL<GBd$8t2i5a4
zs&AUE8|h7T)rlecBn@$3pGZa`Z)30!*GS4U&0NgHX+>1^+DzTyRO>L>hn(lPt$X5Z
z9RP-*^YyRJh3=wpg1AUPaV0&0XNqq*xw@U+B0vKQ>@!%2bwj%^PDn9$FtR-JiVwpn
z4x3zsHr}gazo%|~T@k)j`!}pn@d{{h5Gx{N3u^vgqjjRCa9tE#Gi(GR72DY@Pd`vj
zC<w)d$Ok#q9j2H8FxwTy$7Zm2HI5HwurLI6FUqVpH`Xc33Nu?8<FrYUZ-vw?vLj|R
z1&n^25aT&nV6On{aKLquu+3j~eGT$#KK9C!iPJ;S9>mnh{%Fmg9<i|qtpvQyLokIJ
z06gb|#uZEW1nT?1bq!ELs8qcTG?mX6OAB4UyVR)hqDy|_<*ww!Hz(u2f{2@vPZa=9
z-hm@`TtMGD2i|nGjw3u>m(mPDE*^2KAkP_GtG$h)4I{`MlXomW;l3n63F?I4$iHq#
zATF?TU9W~gqm3|g+z*!uZ%urvF2Mb_qTsI^hE4-eTs=Wmr6cXu!yB3(K~qbrw#%nX
zaUnq0Qh$F}f<@@f@tpR=Bb77nNj~wu9ex5oiqmr&U1e}zblDfaqb|ash%aEjG6SHF
zAdRU!*F?9b==CCxABFq=RX)J1>__Jqv$=J<`vXbPKwftuPUSVih7*jAk{?L6eaZKZ
zr1d4)McgxPh%n;}F4G}oY>QP~46)A$c_?_G<)Qon#246IWP6ToV1n|mS)F2sq%BX+
z9XR3YgR9YeRLmNDCcTYV7^0Rzuz)<-@wXo;0)D7B^#$>%5}xO@w{n;Dx}f9Evg`iJ
zta`3DXnY__m<80?wZ1XX?WXQaK1XzKE^}7yU|CUdeuC?Cu4;XvJ)`8lPqCI|S>#xn
z19%l^&>jGJ!r2g6$!!46u+y@t4c24q%g}?KqQSLWDvuMj-vGS@O)Hljh>=Mk5pR`H
zsZ7?FsLP}k(UETmG>2bb#j!NQ!b3C9`dn4R>Eywpk@9_3F;~q%R23n};0|}e+Pzjr
zb;L0=dvse7H6qubbBaZ~7term`8|Y7#I2dfvbX;y=M7oIN`Cg`H~d=$ixfbG?YD4#
z6i}8A0SdrQtHPnKifPX6YWV={-}sbcWo-sMlup|L?^IaBX$e;Y4kB9`m(F&8ASfj1
zUYkAyZhaD?pZdo<u7OQvUi4%cwlS(j?fPmC@PoH=URw{8;avK`PdIJ_h%PF$x`RMW
z9WB5jSDUYtQ0Ue<Bw_`+x!KZ0i_OzS$&%$kU0$bpLf|O!K3C1|i(FDg)XQ_gw=k0_
zHlfZX9E=Q*2;?B{+~^$RK_j#=`?)W=Ln0ATDsU3_THyBrKf6g$-H9l?zu!oKMaLB0
zTOBmhx40_q--$0d?|~%?#U>VTycHTQYuMNbqoxl|kR`+wY0I^F(L#J%-bqC#mE~@G
zeNe!Lj;pp3b>?*BWRwJ=`9DRnU*klw<D&5iS>U33xvrq4+rarNQLKxW<ub0C1eDp)
z@1BDMDGrQ5cZW-xM~Cv`YLuL9u#?F(?@0KNGGa$Pe6&2NAR0VUQ5iIW6kk<iCZn0_
z_WEMmmkcy;i5MFf8i%0h4u_@EY8=U`2)S1_4ca{ITv01@f}!NN8})VjDQ49aZidmB
zpbHgZSWPi&0EAT=0tPp+H6d~T=Rjs3CpZztq-d<@Bj#Jt`tsnisROrF{Sm`Vsnk8W
z^NzpR#*}<RLhfN^!{!-VbhV|4d2CSOEOXi;7o4&2fQF_UY_AND!=#Un;D;z@O}NE;
zvz~3DEA|{3OD%3*H;x^q11MY9B&{b_M^D*Ww07!5P=As9<_*vnyY`~aKFq9o)iUeZ
z+l{_Wa#W)PUvn3u_b~TwH}c|&58#g!dbXhLHYUuV3~`1F96=K%DP8;9&&z=xywj#~
zyFrV8C-GXt&%}+@Bj3e7eynKvVA|EiR#;2zB#_s6?8lHS$PhELf-}#W5V0XRb=SH?
z%)Nqo!DZZAGIR>^w0F{qd8g-)d*ZT;Vuaq4VRB2g)XTL_SxRZQ=p@gW1p43fPxe>2
zOm+GEBT5B@%d536O)f$6QKwj}2fPM4S<+D)8!q-q*zV06lwkL+v$*4EtP@#W!tO*u
z)+3bYUDzag?}Pm%JiPjRlbm#JqY=$zcX!Jz_lL5P9MZ7kL(fuoymR7Ic)~8I6>)>~
zah6)O#pWbFE@hc8$|D4#=9UEm-dQh&rkmp)yFoA15`|qf$M1N2k7?}{%GnCuBnbZe
z1iiD^&3#R=+T+%!^Okq1kT?AX*@8$OjX0H4%x=F%U^|1Ekh-8HVf!&RKDV>p>g8;_
zhnl()ROvT0(Az~V#>ORY^j)V%&O=U;lT$JsTGUFHTOIa#;G0id&f$@N2&r@U_(@r5
zX-|464RydjkZi%Cx${HDWDM_wJR5ImyMekuQOWlHI&?O9&m}=wqD3w#wr~5C=qnMS
zD*Lx}K12+ECkA@RR(pKV@@>QnDZ9&PZ*$6nG8rJxu4w77NV&tzIr_GaH!d+ljCs>c
z7%YY~@okk?p65ZE$Ak=)hL>`z_30OVwL*n6D}1G7!mh8Q?X|&zzM1kr!~M2Ha=F%B
z?vIDg0YucSG7Q?%*GS-g3ix8M&ea9wi3`sg4-?Q17`aL8jC@3dc1&HBi{vOL-g(lb
zK&cAs0yQ@teCot(qc59L#U`4S)=x>rK6N`j@4m3Qb3#qQKA|e!9~?gveCC-n&>pL5
zD~bh)8lqgDf!8+>XYuMoxS%mH@$8%^eGe#<Mfiv;&2_QkQ~AZ0;5F`Iu+w7~Pasht
z6~y48;xbVePDNX;yvoawW^wi%&F`i8a;5?wrDq3IBS{Lxe1KZxNlE(Bc8|IB?M6no
zVl+b)@W1w`cthCv>f7L<LgEQ#LswU&yfL~?5%pMgyc-&wFYX6vmapEfMIaJpsYNry
z1D@JX@50m8&%`jQocXcZRw=CVkjY0*2d(LXt)r`JJUtPnO<h0p9|s^9tUVa_t-&33
z4W{qXWh?mmsC>=_)4#1zS!YOGR=vtuR72$%C^`<s$9vy7V1>-syPsw}X2<n(bGzh$
z?KgWG0msr(j(52?z~ilsBBuNEx^FD+3kqU%q0xb9>AeVO<qZpByneAv{mYgJv=qr#
zj*8RIm{L<h)p4_}nrc?|XF^V=wXaf_o!dL--1DR}&rTUbB&Zy#U(S=o@hR^@R2yx>
zE?@4gQv3FE3Cu?-Jt1mYGMnz$xIGc%ht0g$j}gyUkghtTq+)8g6N*AHAd^2a$^JN~
zZAl&4&fQ}W30dfhy=g&!*Z=503?r|*G-L)%Obp&s)7<TmzQ~yojw(ChO={cl5^QwC
z1A_VK*PB<%?!Uli)3X?r42GzX?>Z1b-c+0t;Z^87p1n}I<k{JaaVuFSR#O<#6;9hf
zQ{1pgVtG=ly{5>wT@J=H-W*oDnq`hAvY&Q>hUvCrYq87n5g%hDheVyFMlaxH{<e5x
z+IL#kKW$~4GW(h9>xToDs*yX?fhdxSCh89<E6*X|*u+G`M|ZsXj0a>Nq_#LzyK1v3
z1{H1<LXn3fOnoKMCEy@I^$wB(kxyyy&R;)$Ip0n~o2ffeJhOc#?i|$v+*Xb+{b+TM
zP)fa%P<!CDr;D`SMu{r-^q11M(?<*vd?y7qiLqZD^=0me=c-M_XdO@8>Mv3zFww!&
zCY9sxhFqOKh|?R!8-I@}sFcrHh*C%!s$CD3)iKObMO^50Q5&{46`63CHwz31N`Da=
z8nrN%g#E#sd|`U})v430k=bl(`}D8PCNF-d;p{qcKU+0B;!s%NzLI7$tMw@ro^{-$
zmrD>PEe5$t8<hwBKm#{s%p<TC1O~chhYdG~h=`Ds?sB_Pn@*cOkSpt_Hx9`oF4XUl
zG@VEmSsyKrIN9!dVIndIrV?b0>EtrUv#iGsjc2IZNn{q=BPoeOD;&b-Y<Xmq#_EH!
zI=?<vN!GuIoL!?QL26_Tw7J60EJP^y@NDYnl`cQdJ8_;hl9;{NQU80;y&vLwS{^=B
zxYq#A<X4g|9bu_}r%&zo##NWGCphO9S)dY`IEsoWrT@APOrvn<Xy8GXV#(FsRe`bH
zo$HXWM7dKm74iw*$c_(%+u{TC%&hU@m;AkES*>LRLMI~1M^GYDKg`?v_VW30)9r1v
zaaVEK3`sHCXW(gt`*_!(8#>hh&*;gMClN=brj~@NF3(LibDr+%?%(em+Z()TgXS{u
z=)4-4wy&Bq`X$~9Do3OWULIB5e`P(;|I#TY7*^)iJ+scT{l_hpGw)(D?=0Vgf5pwE
zHN6`qvtD)Zv8$DL(=9A}TvbAoeo79U;o%^zX_cHes+yJC7njRw7r#!IT2Hf^(BUmG
zWFN|MDSo&*&KD?xa1+xcDE3oe^8Z8hh;$%Z6-L8t^0Xix!CYG*a0bpc`xs+7m=8^<
z-IQsWx}eO`9jW`Sn1X^rf^N(y#X>7F$t)TXUQX3EPM&RlZL%MwUA`8_*a@q1I6q*l
z7C>X4|CCOeJAA=PsP>&N$I7EJO|_)Gwk(w-M^@9`Jkri_UKvftlZ|bCLGziaN8HoC
zL=G~<wHc1&p)9GCTV)w8vqUpROqld1W5o^44~VnmR<n~W!W1tfCJtYWY*uzyUg^FE
z4nN^loN+(w^c&(*)NH*{YH+&!Y|(I^h9{+Lj6N!gpn}31f_G5;_Q(XHR7#j|vQ)L{
zfL$xw%u*1)>3%wY(Zm@qN+)xsK=Cn&i+O|F(fkpsiTn3UNirWR9p_y?^UQk4JcB%w
z9TH~tp>do!u&#d7S)*6lH|_}k{v3SG+LkEz58g!5O+i+R2b7hJD%We1<<l1nO&fM@
z-hSaQ*Tom0=loV6GB*aYe@-H(?t1BRhd6R4obS?hXHH)_4Rp2vB?u*MuBm%9=(y-+
zVAv2xoT)iWl&qsz6b7x_F8Q!{&^JR1HdXA$G^Sv0X(*V}W4nB>>H^-Eu_FsIr81f_
zH+Ak|_qpdXvho>bNWHKq{GW5~x{FRc)9<uJh>RJlp<2x{Ls|CP;`zpVLwtvajaSA>
zIOrzeo`9oX-CK^AB=f_?<TOqt&6LD+B>zFe+fyf{uSpb}h^AmiYgb)?t@M61c&izh
zu+01l_hy};{YJm42`1?qNfHqhldKXs)4SUe7%7+J=tbN2-l$o2)kZ_9%Jj3<$k_n&
zofHWY8~F(TOhV*r!ebs(-Yi3QVd2(Y$fv|-Jw=M#8=faKTAbVXvu?YxYC9gghCPV^
zy(jCXCv!sE>ok@I&$RpH`8?8{i(!p+9~8jtCZ(;-?yx=(OYiPNVfls(FGQ)@gHH2g
zi`T|uu-uMJvv9`4<odgKF>pa$LbyA9?hT|)Ng$B-A37jX&F*XWgMErRcXy6iWm~=U
z$(7C+p_u&mv0D}oA{bRJ>N6ltIi6P-U7(U<l_3)@*CG<MpTh2(w1mP~M-41fXtM}a
zFI~PI)}JjUI9lN-=x)DURa)?J!B@d2&&A|%x@+v~v=`kjGfH~R0;t^O&A4c#n*nMJ
z3CnSOvqfQU&g}O>q4^KFp9@)%sy64Yu+i&bcb*~nG~-?5sY=QUx|4bbYLb++>td{|
zj-MU87UrlslLYQAO?!LpvW?-uLE&=W{Nw55J%I~&Q|B?d6B1I&L4A|z$n?~2KHDz%
z&LF(`%6}kS>kCoOdM019MHI=ZPS5v;-&h-N^VEU^OFi~49c{PI_8v%(h)0rd&Da$v
z#uig$8ldW8^Wnx!lVqC(&ng2;H_=0>yp^$S3Qc<T?=Nx}BCSU;9rsLN_1`&?0zD-@
zs9|Xpih6z07DLcTyEG5KYPV3b_&(K9wOYr4H1tW5j8c(!uRsS!5|P&4xFnF$elRLH
z7`}fy(E!-v6z}EB)BP3B5}IW;{9xzt@_X{+`DA3|k}f{jh+H@`M+q$3Xt}?Rm5G@;
zJ+1w!%r4$BZso(mF87xiJaBn6bZ$=+>Y_EOen%|x%1x1)LlP1OUeCbv^qwdkOd7c)
z)1=6z(eTzqeZ)d}MS^NlAfh*|t*4ZAcd2tWIt@!e4EKSY9D1-yEI6f<+Df^1zj!P8
zP<U&H{T|}k{*}6xO;`O7r5>RH7Vf)aBqlfMcga*C18leQ8o*0mxA^Ro+Eb5FZ?r_K
z7z1EG*qML&W;}T2P$4OYZppjJI!8^H+Ov4pRekDm3a!0qOUGsKRA)SXAFw+wK%DE{
z7V$KL0U>a!^W0X(eU<I#7=@3`p&QQ^k%W2e-QXDBtA+_knlQ;I7CgGOv{uHDDt4Q^
zMtIUvvsJ0ob@7!6vR+&|Q=gESIK}t+bCb@tPW$<9LrPlX9m`2XNZQo>cfK=PERhe|
z0x>zS%bwMz9@j0dPIfjl&NinN40p6hKV5a8MUL_z8n)id+&fiBQ)`ES%_2#Xx#}rH
zBpN&NY=-}F=2<*BwY)c~RaV=VTy}R>d(9~E@We77fq$QpQv=HfiIUHt3S#c%8`6zB
zU@#}o_WpwEJ`FiKpo4rPtJ_HC|D%<7lGLg|9`Q;av*3P#A^~heMaA2dkv!3L7kyFp
zqxw*#>hWeU=2_YfJKEvl0c<MTtsvYx;%uGa2Rt7u87rYdBTZ?O+RvSAm<2Kf!tZT|
zs7lsYc~vQ?olEAYb}=7tFCsZrM%=CaV#x3gOoq7|P@@!(HdS_6R9B*83)20Ci_Td*
zJVL|c$*BcodlS6_g%vR{sdqm1-jE9?AK$KC-8UI3PumNHb;(#<yg;ZbK0K?1Qs~id
zG6A{V-Uc=F)B8{HQ~Ph-C%ek?x}RbQA3K7{2WF)Aco+389ro-hVa9<UlmR!o8_%Lu
z>a&R%EHjaolRhWU>Wd*hQC__d6^{hFX={_a^Y%aO_F=o_ck=jv)1!3U)xBkdHZbmF
zLj|;8C8+8a11mXlf%gZqw`zJQMSqqmvC*!B<;_Ak51w^MmK_U5*Y*7i&DI(F?*4oB
zhy6iHBzSmuUw_U=aQTwz@qAEd%CuKiFD;iv+Ubd-qG_}iI88Rx-5!s1s`jq%ML-wQ
z_|ksNIle{r@(r$zm+|Qcp<+wdU(S02Ltp>AZ@irBXDLJgleKWT&*u$cBYmE7_}(UV
zB>|xz#FWOYAo==jdW&F)@q$(;qF(7B|5Kf_;=M4HvRCM5D9u;rHdev8V@Z;E+@ghi
z_mo}JUq+Qxu8;mYCr5@B{W+?{tH^i21g78ftFS8N5(4I<ccSRQ2m5g_iyIO@4;F51
zdu1uXD?fviySW%XjxO>Ns)`L)Y&?a;D@8O<3dV7soEWi+ZMW<?^XqyvGzg|z;0tE>
zKzw6juB{B$(OQh{T+*pNPUyGHu#w38cKCR=HS3~MEf#EseAOZmvb4??TijdBeiQQE
zMb0wX1PyM)lqghGxuLd52j`jd5TTzw_gw?NR_3RVF=ANXgQN^Hp{F=Rz`h0y^rJBF
zV0asIxD`wJK(jaOi{5MBS60%Rz)K=Jj2Co>)GXV05}7lQN*#i@<-_`cVG*4-3SJ{(
z<-u-oi}E24xOX1%`#dJ4mG?s>M2v1yf|m&oH)JgIeK)Mla^5^rseLMytx!!lV4)RU
z^}*!nF04*ka}o*i@k|i?&MfRU3k2!KuyeG8ZWk5bW5dYok_Z*(VyZJAm&o+Hh)HMy
zhih_O=j<hwx4&W}BVu0#CJ{ZMeGom+BX{q(A5R!AUpoWV+z12~copG&;#3mm=G^=1
zBT*q6V`8UAXq~JHIpD2s=ct<}H>Q5$c9^tv+04<CiuoprcJgo=XzT11NNNPRF#-~q
z(^rFu3i#3C#_njVoO$*>z9*6VPyaDxZb_o5Z(xwwFtKjZ7rwgGuo|5@3#{?o_^-{D
zBT+r3;`k)_fSD|vZSmmAx)Y5z<YSt0L9ILqZP^zZhX=;1C4Noa7lO5ZWX*2Mw)@fm
zzwPVq|HO14na)DHIzgn$UPpj)0^k+V$v>R|2$HRN`FtQ@ieddV&y_Vx44HIJR&<s%
za7XMe$Vu?VTXDnI<bm{pNPnq?D^#{+<~*V54K0|*)-4XrLd|hO!}@OojhhRG;$d16
zR8V|k<{w`@8ca4Hw4~1V;U@(Ovi@snfg8F)PcL`<`AXl8L(uX>_vEKhGVrVwkW1iM
zv*3pN{X5~xXwmiB!qqcJFwt5Lx@aA+>~l(Yy&)$u(Gcmr^o|t1P`#*-0U3~LOWS<;
z7XCH_2L;6`OGIiqnEg1OFImnbLw+0uU=`jV2y1`?1}l5a#7vpGo#NVu=1cq(A`i?J
zuaeR{DUgw!{R7P#?lc}YzP?CeJ=vC@fK$;8h3Th4Eno%WJD-A=mS<C$938tZ&$$*n
zT|W<gcNM@Ac-9#&3003(*<o^QSD&X^<=3*)<&c7}*s^MXg|M;N?k~}Tj_x;lv~yy7
z6`F+EiT*lcC4wrfs>}(@oiy?-UGz~PRmQ_}`Td*3s+W!#w+A^^`tmJgml;G8B16U?
zgg_yw3s(1-MXxrspSD0dbwZwA#d39FV()9<^R~|TDzQE3X5_-u$#uxzoh_2^Jb=#%
z@BV8xAqq@9dDnsyAHF|efa;p!R)3fP=i&wNLD0jc=k^B)Lx1GtTN5@c3JzSRimiQS
z?-vgWq}V~i))%XSjdMWDI{TJkzg4cbOKWe0T1~2wPq=bw*ZD6>zg^<eOl5c4$J=o7
z?1!+XpU1mSC$ktcMS70`Z>_J;#CH$%mB@x~5)Y|bEwE2NtZaG?jN+k$7xR8FVj@Fm
z615A7ukzI7&0)Kc1#Z#W!Oqpoh(X`Ly(>+|_3kN4yX^$2Vv_jz%bo5V2M>*Bnx6o@
zMI--!fTWQ1>Yj3r?jL3C$fur9<!-3h@RIx-!9w^0yO>W+EYsjgzdp8Uf6HQ6|7c|c
zCxV>(#JB(ZtJ&qPx^N|HTacB<%PRkQ!hV16U8KH2N|sf3xxGE|!qHIorp%+Kmbmk4
zn5~j8x4WVBcu`I#Qk=3R-WNh;8hxdnXeovD&-MTP8)DJPQlE^Q=j!d}$LU$`wq69!
z{-P}@dArQCCxkbDLXJVFiW48ge@S)0rFfXv*ude-w_l0PpM&5q9mssLs^0yD0U^Zc
z!!m*kG@>9ck}21r8)Y@#kf(edyKfi0bRP&!9%%`0*Wp~(ug|-@o40Odnzg*y`<73z
z1U=a+r%c5SUzYVKohW?@c326psz3iYBn$*wgY4DnM9Sb7-q{9jX1!-UWbxPl7We1x
ztsm;LDQ_&xTfv4I@maz77mNMY%F1m!{8pf5GnF!a9AFjC=yBJ;ug}Yrv*=k994auH
z#Id)j$NA)p3=ZHD%WrCIRA@PvFdmCCS{j|-O#OPBg*^M^4sLY6Kb`ve$ytjNd5u`*
z6LiZMQk01eJn%+~=}@k;EVZyCb+<dG&+SU!jKgt<`uE3}95|gkt^N!ahDw-6rH2fW
zjP1E3qSpaj%RkTWGLx+GV{EgCgPD;+Z0~%d{Ar6_&hwm*{u~V6JoASH<_jmCz(+)`
zP;~&~3efyR)J2!*@mbG*e~Lz?M?&_`jA5fhJ=OYl!5?(l+?hy8njZ&zb}MIHUN$k$
zms?IguZ9U_j^j)?yg*lJ<#^ew_hlKabv0W=0lR>nPw%q*#+-ETeK{V79qnaNqr!lo
zpp3+cqrQBWgT4%g<2wUl_}-8hA$~$tM}~361uutYIeMw*TD(_9J9ou|`)O^@VWqhG
zwHW#}3yPE<E9V?=G|BG@DR2#AoNxxVTcON{?9Q=XxnMeyn}03!{f~P_qt?LX#vYm^
z5>&Q0)KpWfWPQtZ^;77HI6pI#e$$5n=iSHC9d=!2-ik{#?JUn!hypx>NK$3W0y#dU
zAL_+y`Qe&94|w?|22B9DJpF3MDE5<y{n37VZ?PO@Zjy|KM$F;WuFsKi%WXadX|n((
zCSnfV{t4$1X{;Wz7-fpj@64R)&znXreKRsjGZdry*F^F;hGNV*c@{_GqR%)SV;r+~
zn3l%}lzZ=gk-M{J<+0h-;<Q^^ll?TFdJ8Yo`3KSaAu{l8FI7n7Rcrus2Mqnj;>jUq
zD9dHQHaYP)9LmRajvoiLsU&G%RBZPr+^jJ4v1MwST`-(@jsAAAdDZEM44ba^n`iXT
zsO3dD=nw$Y6=ORUOEb;7T~+LGcYsw-@;EV3^O+l_xhACVyjG@Cl?wl7UPJm?XKky@
zUuQ2c@0j4lLzQ{hfSGEFtX^Vtl+V|s$&a*4TrNqIN7m0P%TLNk2R)5gwl>G6`9wR^
zlI>{{>TJa|ub!obU}=+xGN<TDIa!aC?viMZHHj+R)7`wBJJ+eM9;y(ll$GqepPli8
zx`n_Wb}T5`wcEK`Ayw!Lx#&amW9ikz@?1~L5)N(qd2fi(+I`vS+)&&*4SAN#0Ar9P
zflyO~QgeMuKAxn@#+S%cDtvjCWQ{NWK*a8ufC#v4aTZq;e0oFHbmS(t)6heRW^v(R
ztz+$HdvuOdn!}CF;#{XHR51Sv$(tAZ(fZ4iWM94@GNV;%l@+aItvM>wwY4_-k_QcI
z%Sf9&jjCfY2g$+|thL2XAMcdCz9)d5H0u@k=yZaOJ8dSgI|Zqe=MJeRH8u7LeJSV0
z$|Ezu*GIlGO}CE@=j&!N4(aM;^0y3=WzwDXs%Zx}We~bFkM>3$Zihn`Tb%1uqr;0e
z@A^P&Z0_|Js0#{I7;#{`VUtlIss!GUFH(-4fzzQ}A5zi>YM?4Xw^@3MB#hE59{OlW
zME<9^=;zFRoIe`w_r#W>*KTThyo6A3Zn*Cz^i<I6pc|x2biUV)4G5;ay}v>dJD!iA
zd@2D|TtC=9xX_sir_q+kXBvtyYv)<ewCnV8m>Q8A*<UBnOL%UW?aF1ObeqQ~1YxJ5
zNp0JWfbJp>UTz{mBt<^?$ZT`U{=jQcN=MK*FOFXUJ&S$?PAWyc%!YP#MW|Ac3(|_O
z044*i7E<c({fgL~6%sAeDAt&)A<3|F&Af8``Xjng?qr>@s9vPU!&`JPfSZ1`bs|!^
z1f6suE6ZQT9vMwHo)_4eVKvc`n<`gG`x`E`tg+_((~ku@j*t{zi`s}2e=1eWH*40L
zeA)di_ERazcYa`tw^*=Dl^QpXf^PEXz@6@%-6y>?6k_(hY)+)3Y`?&vkW^@FUe4Wh
zebp}0Ezf>)SMhd0NP;lC#W~w9++6n*mT+?|X#C=EZ`1GUhLEw&aHQ9ufFX6}HS*lK
zaRMt*X(^?e&5|)*xfH1O^~kKK3m)-{yS6n#1xAxm;gvj~`RL093thoDkE02j<rv(c
z*(3YJnznX>X0r@xmGse#;`qy7cU#gdMms@*IXy>7!*4D`H|eBgicr3xQa|@7GkGB4
z!i!5NQPBV*D$YAmW+VChI@kku6D@0_$}Fd|D|9=yLwZC>i1T;&_T?mN&wb;W9kn5;
z+_Zh(>F}oh;g-2y{K2{d%Yssxi(#W}K<h>OxlU|v`Bc|^)aHA}KE%Y;Y{1uR*gICv
zS?bxhTOMB(OhvDiNoY0JmF#x4CiDud4WB&kEj}r(R@?!VlQctY?df1iuYe^r#A~o>
zoK@jb;U~N3uC?^J+nZ>O=&0qrZZc_EhrOTan+Si_M-61n^9+zTDCNn#&@3`ePT?Z>
zUNFQrRy{oXC4d%GTjp(PGp~6F-%YIIfv^p-#fT#EP}uK*AU6JI#`h@meXEy(R9rl1
z@wKZ$4?KyO7pU9etK+`;?og>w=GR>E`*Py75}*S~_RL<iP@8Nmanhvox3ZbfHtQAL
zwj7=N`_$&=x~t~PtqMf>L$i7Er`$cR5chfxp=8Fq*9<q1Xo+lSHKPi8VYHpwshLoQ
zZ6mL8x}GV;|77pe>xIU|*r*3%6{hi}q;W#&Ii<OXmO;5sgRczy96v_w!wvdWHjAOo
z!AnDMx0d~0VzR!GS$Ub3RePMl_))%h|Dov@e*tpgJllxiX|r;K!gp8t!4e%4Kp!(m
zJu>u(o}G6V)`h_hCd(=Kg;kycD1YG@gPeNTdf4cOBruUH&LqG@gdchyaqrf(b~7+Y
zcW(%>uQzbY5v%?^peP$?{pA#UZo<9TFVxkWo``Sj*LDdD^p-J*d@Ls^{<@MtwoiHw
zICp%d&9fIXoh+?`E7Y`0&hi~WhJI)d<(}{RS|aDXK1M6onen-^cF`P7ypU2`AjD=t
z`x-bxy&#D^s35-z8dS<9f~?GMK_I=xx2QPcVJ>A{65$urQ%brW!Y@dVn8`b)GbyjU
zSxumJd9qq)Fedo4{iwPEkx@!2SX|}>mJmgD&{oq$tsGGILV5t=>gDU{F7N{ht)VJ^
z80++76f^CuaILgl)AAhEx%X5fvFdPT&*RD6iIar(9z_0pt`*H&XWh`D#r3U&4vaMo
zi!a0{oWl5cX%a97Tha~$=)|cMIDY`MgG*4DSg*?H3vL$`mD*u~dh6DvycN>kn$kSK
zCKw#TAk0<P&GGv#(bgq+aj69Mhr~AiOyiO8kwc2SN2A!x`j=l9VpgV8-PuVBtA5Nu
z1+Vt4eAPNy_Xsni{KfV2?O#hcJrCA{GpH33cn2Dfw$U?7Be$wk-M@0+md#6|2)Atf
zTWb=@762vXE|sRL+R`6P@}<RMMm01=%IK*&7;c3WS>{3ZW}~~R5bs{xA=T7kE$|FH
zQ{TqH5+Wpno-vT(@ZHb6a{`TBjijidFX$edUf*`?#MlCn7YMF`WsQ)-1^btM<HnY+
zf?$AE6<jNuek{G;NmZK;^bPclF)6O8?kjK9Gp|rn%L`ZUXXwbUWyp&j0!(S_m+#Tf
z5(A6y03Mt?{C2Zd3z6i$)CUuZIKa>3n+s_>xdMcv#r;n{34_Qj|KgCZStBsB*wq+{
z`ny}XUfFfE+a2O<OBxd9EW9F7jvG+%QR>$l$YZ#G3I-l7L3Ol#Q@G*_ZGvlEHTU6l
zb`K|gJXOeSE#K3=$7M@;q6oI3`ZG0NgOg;?Oxn^AyW=lqs%OFBCseCJi3bMlCt3xs
ztH++~KAk*D_x!o}Z>wwEcSRDubty0j2n1F+nm_IqseF$sK4w{10^b{<NSAr-#OCdl
z;7!};VNPf;DvU%h&3!fXfy%{y0IiomxJM>V)t*W7`W~+O+ter(v`%teSYcEzQ=*oU
z?}y%Aar)#Wg-yR!GtcxW&UO}#=6%Nq67$lltgHk|KGHbl%(|cGr<h>uw9?#ttF*9!
z0;w2yibUipne4g5`X%|zODRewld`6rFdmtFug=CV`<)2TU6?l;FKldq4>pW3!Yk6t
zbuh5rUF4uuBD)7F8o3%yT|+lXZxs#i#@yQ+ySPTEs>z)v5o!@54?Q^|$r82%42+0E
zh{85snKVZc_Pamf=+=)}C0hHQ%h?f}sv+smW2LR=5$x-t8ozh>;(!;sZ!4{zg8c^+
z$<k85tyHWp<gZwkD<6Nz+pK}-{tyS(xX_k4Q_j&rI{d2Q?&N-xW0T*Aqea94UG@)z
zm5q7k&a9=$mj^N1?z-O^8X8$<5vRwhmGrz9_aB)Js1QJW6)veAY-m3RApcB^QAjr9
zfF%ATrxgs<fO!C~x2zJ6#DO-S4N*T4=TY)!<k@0h?axDeE3vBqSV?ccJ})--6N{eu
zY=yL!_2+4ZtsbtsFT|8~zx*8z*s6hWfH{}$Nmx&qK8C_*{MNc?Kh9zWj$|p1g2-0#
zsE6K})r0+tS*0R`lL~1yt<-gDk{RDAXQ*d*GghZ&Dv^2bi0}0I<5NfD%$>0@Nxf%b
z7an>|yyKkDeA^?ww^H9}``rB9BeSwx5UV6n<_cjC@7okGi46KstUf7I2msqMjotR>
zv?vOXOp=LJYBHH#>)G4(p-#nK0O>k8d4gx)tL={$^r6RDAE;ypWi5(7w<$2)y!lD9
z%vhRs$TB08Qz!a>s^ga*Qj}@AK}=g+#UM2<^a8xnBd|Y2!P7;;@(W_g$7QvtrHf}u
z)B1UbgHnC)xo))|1MnAq)18eT-)?<du9sGOYH^Wj33;Ez2XcyCPe#32M+$S2nESrh
z;|l%)-A*g>;O7{4%y&sM$I#)6KB3P`L(GB?CH=;F99#N8wCPKHP%8>WwPX0;t(@5s
zk+}T7O&GhpP9d1;?sFCZc}9+4a|TjA`(t;6rLT5sF_m@7K*S?|BZfVd%IazBenhy`
zk5DzDhyVMx$DFI{t_A`|t?XIC^`!g0<6_Vr;{Cy((AZF*PFQw#NSX;wB9xO}ZB>$Q
zpf%y<(O}$k#H1AWp6<wLFrG5o%>(_;ST-YSKJ`)O$DLWuEM9?EKQuXXfT_fIMRuAQ
z1=&c5l$Y7j$h258O)_joqq^7c!aGU9p#En9k0E3N(VhI-C6!C7n<gH!O|2N1OIHVz
z5^dh6A%(Pmulq9oip9L?yx7f`k~b)?Zn%57oSxfFbHr!+m!*iPiM$bU%=fJ1RI>(`
zr;Ovi#h{(7;O1@z!yB#O6ALEzo)y>&H#CcGfl+mD@4Gio&@PoKv^sZ<^P)Dyn#e!Y
zw~a>jSssv)S?Kml3cR6vi)gN3g13x6p4g$uZfulP?ylDAA+DzX0zKKbFsV)=N+O#3
zOmUW~AthW(@vu{L%FV#ZPAl(YoB|Uwv#&t;=Hsz)A&DVQD2oLfsD9!C$}4vT30@3;
z<=1I?dWqOazA*XE49{iz9!*Poi)FrF<oNxq+`tL<xc!95?Log0@hRFDOGx-)s)FIH
z*Q6E2b2>F0nvP4Xh`3t=kNvc~247t(Rr{I`Ch)AjEl_H5i1j3W{(!18&0rt^Y`_#K
zs&`lnu=0UYGI6d$(9z!9EmR-Zko?mz+#!;c1C}KJ%u4n$pWYYdkT}k=7i9plFEblV
zNeiM+4q6n69wgxUb%@T+ct5&2==7MS=YmHcRmYIF^e<N|Ub{bI@PKpoTZ?(V7pdj7
zw`%pQ?r{NATMPW^caai=SWFi<J?vU{bxY?@o(@hnG;G(!+#F~&1p{x#t^B2WA|!jl
z7{leukL5*&Wdt4zS_@VPk8@hWDm$y@ZmVSJWkB-uguUu8Yg9k!14MH%6z8ZKHb&^~
z>?}O*c}xPkQKpl&CLTGHWy1Yxja$HDucnmr`!6eQeZWFee0R3@hTDTNlCdF~bq7Ik
zY8tYzK2{4fAF%j13uvvle2*aqedu6&^wsW5{2=_g-i7vS74Z*e>9aa5{Z0}d0N%)l
zGkGAClJSa3n#l=2x7@!$zc(;&OUXUg*6fGCA6|n*51AD1Rq$)X@*Daa^M#UaO#Dz2
z;1#rS{a_<&nNhhe@R~YXg&oGJD~}dYU2wSJ3QRyc{*TOS2VI+zJz<xVgC#D6q~n4B
z0aB`CiO7Ey^ALs@Vl_h5yUyg<a{&|tFJf#SjD631;<C5=T&a43=x?U%6B-a29NObH
z?r6R9)$T_8DEvCIFhRoIax62TA+5Zc>d2`JF#fKJ9Mtr47Pxs0hJj6}H}MRtx2SJ}
zLaU#Ix9n4_2ZscH@%sNLd+)HQukCv{iUOiwL8J+Y3dkT$r8fZq0V%=^y(7{YIx;lr
z(nUn1cNm7=I|xz~r1v%mNEb#JdVSBJNzBc?zvuhr$sc*537>P$-fOS5_CCk3lBm$n
z=PI<vg{_#%qsA<Sud(d<Lrj~4x`RJ^FHSFJrqAL!93N;Z=@mJzYm7%ur_{pz_BUz8
z618?k`4b+l)oT83lw;|^@5Tw{&s<Cwiwa0S#yU@al9cM(nlF=Caiab$lktVG2{Q_F
zW7kGMXW?}@&u-LpwB)TyUFIS1^$VtboOra6Y=7O#>nI-Qw@RoYy+qA7<EW4n<5zMH
z=7-KdaD1fD(^)b6n7^zx!v3y&<I0SqtxM$um?Y&?H^PpNJV2;9@jGvDN*zyHpZ9@S
zYg&OMU}wk3?;4~&igg*E2+Pyn)#1;3h(zlk#ZE*IgX%cPr^e9>7Pm(!NU6mIwngY^
z{55ga&1#vwkPX9*EY}%#6h8TKtPQ^>DM13Zk<~3$PEFu-ib0LH7_QN!;C}FspO)w0
zaVKbUb*9{ceik&L@f9^c8%K+zh@;Ip*pE8@z(S9_r_R;psl9<Q`65N!tFdTyw1Cy;
zmH8PCI%-}zF|tqZs6p&6XS*nQ@?tVW_?^DX<1mJXZWweb0d0!BZr69?yg9nM&cs~H
z_4>)!sGz+6-*wA!t_;ihqwsxLmvkKWk2p=M<uQx(7W%7}uJ3bod8)R&tG&oJFf}$x
z$eRZxs#FCR7*zZr(fGMDshlRcFEvk-dGn}AZ<P&+Hni2dyGQM9Td|MAZs<OUcP@+V
zcVwE`vaPN>biM8>IA?gq7__3)ZS9f_USN}j!Ckv;WvP`>`;2Ui8w(8+u8(l?!8S8D
z+HtgI#>(MQEOs_56Q^`&qLeG^(YsnOc)9q`LN(U*_oti2J@^qvZS{T3&ot~p=I~A|
z-Sg$1aGVh37iJPW?i2t!Y+!_Z<J`@U4^p#&RgsgIRc&`tBr!9=$pxbyrO4seiCLj9
z9U-omICs{t+2+UE51Z&PvN*7dkG()h$7xQ6y&-y`o20=Fm!i`-kmT1XAo%G_JAIoI
zeJ5vpO-ZtqDrMy?(X}MJd`x6$m#HHBQ%KSxyYG09u2(wxthN%|>ee=~)&27Lum)Ex
z`PsLg^KrIzliXj%xdW%yUAihq9jwGv>)mwu<(Wi}NiK+y85crM!XgNS#W;xRI1tm=
zFt~CQiJXMM8`9~8UQZp+4D}gHj9WMyyiG?=m$>`BA^H;P%-4Q%OrKO#o@`jPI>%Xv
z-}zX4MHza`dFYH^hmD=H|HG3&o-Omze{D1q?F-G6<FdJMF2Hx;Q|x~Fj6D%Zz*{?e
zvR<kC=K)nK4;lMpIm>M~*3mj+FHiBJGeB=)%x^>?G})D>t5T!PT%Jy+{x(fM>5F|Q
z`VGt<H=vYKBD&Y*Gaa4M>vbs^I<QU)JzE=1ZF9Xd5cSKbXH+Hf!L3Q9r=#&ApADUb
z;8%M`dK}ol8!c<Qw9o$Lx&qzx#apF4Av?T*w_WOmKDV~EnhHBwgEqja_xz?L42-vX
ze$dY>EO_?yx|W}70fO@AmN!!E&GuQ8`-G(ZZv3Qd>qXEJ!&TWgxq4L3MqVIJ4Opxm
zj=h2MhU2Uyn*0f`a<p`4PWjkba}Q}p6Aw{PxVUY`DniCptcrJe#~W8Y=LODX)LFi-
zHos2xxW-vJcaC_mjgC#G)shJ(o-Q8>fF@^4&l*j<1hKH|;uc;NnG9LVo2=dRR@mt7
zLtud32yqlHdz2?f`;4}vGYlM}7bptDWH|>b{`dQ90=D0vvLx1fN(~Rw$|@=86wJa8
zrgwIDcVBdH{b3CF!5<{Big>>mr-9_zprK0J55n(3uKR}(XI$~EWmm+NWm&if{lKY>
zpI!`uYy<D7qN#pY)L?}dZ^qjc-^HD3cG*@-@}F>;|25w!Fm<WJa!UAv<qWs2W(Po8
z0fGcL6UBa+e#3oIq+-!_T()~^)rnO*Q;xS+&Yw(yI+%|r+}QBWee|;7dB~PduT68w
zUR~>#cXGK>;g_eNSx>x5gl2^kZx1nCymwK9`~x`GhHFR)djghv_kBjLwjW3JEYTV-
zg+<W1X3892XCToUir1Ow*y+kEuYJ8v2s^Du0=r;SXwzRke*<x}nA*!Pf0YPm<On9e
zr;90Qa^%v0S&whIaKzFn#807g^BhRIO{V#$vwKF(g=8!`Z{_Q@W9$#Aa3*<jpKc&u
zO1+OvtuhTrIXsc=aYifZ@}6<4@*?xEd;$&Q<-|A_?@G{%u1d3^Z0V>vLG}SrCipR1
z;8E_Y2r)9lhe7O~MznEI%jqOki_LsnV}L`NC37aIRu4?HYcApEk`WF*Y))cP+ij<l
zSE?OFAA1<dTuaH9CwV)1<;l)Y+uIEtzsRuIut_aaYkUy3pV+`8LY~FhnEQ4Cglu1y
z1y1=BC0{{O)D3gSwUKYvJ%r^!L(oFlEGT&a?N3;V_G!G)UPWq`<(jKBP0`mI)VIjO
zl*Yes1+gh#T#B|LH#<!C={R95+Z~o)%dBH7Ea$eW;%V@@)X(|WS*lgRi5M~wU6rUI
zlq9*Z0Ly?l!3KO&j0?IuJ55+f$6ZprP3=#Lud*rhyi8xzkiRN7wS-3Y3<U}Vt9%pg
z5J4fzAyGLx*rbMH^8(RB<-Gy+hZ}lX#0{^)ip3UVqq1vk4zvjDEI+t|Q+yqv*nEkM
zOoC?AF?}U$HCZ9=;D%*8o1HN$*~<AykfQ^6;n3Zd*t5c0(aPkH9ZrEZI4(h_NoBn6
zn(HQt8=;~uwZ`aV+>WnC$e{cO#7fcWZ5d-qILHq-H(==3%nOKokyr!HwA^>>nU!%t
zx6luZmSi#HhULd~JZ0weG$%!*ZK=%0sxe&Jq43IHxfUrISn!(D+=vyFKlcx}J(M_G
z7}-PQ8`JKpC;AsOSS~>T+iBA?+I;ibpc>Z3)OT^-@9{p#bJrSJn+v<<X9tcU{O@3J
z_m9eRu!Hn#Eb^q7Xwgg^H-*s*tCkO2UY?XnKQ4XWc|XzJ<wf@M;Kc5b6bbGuS;*wa
zK|(9Fn(t{4s4HTMG?rH!fyK8kiyW$UZMM}|?%1E6e}8gx@5jKy3wT}p^+KFZS=+U6
z+<Mw>^<}A<Vv@SQ`1Yk$shvF>t2zo%Z1y}&2(u#AAa6)=xVHJ3^=MG`4uDU)f|R8(
zk>n$fxG(|s{E#F9vB*EZaX~qKe0`txwXm9g6c0No24h2~k^`~(>IFY}j0E9;=sT{~
z=T9~GFq<8f_;cXrY=YPLa3yw3R}t>A)UiLu{eBDp7D0l;;26cLRY8<*e}-ObYtFt9
z-CnuFp}<w~$cws5x2%Lc))(`pw=rm{n-lMa1zO9T-jrot(QRA$iy7OBsS?M_Y$k11
z!TOrF#F!O1cL-Q;(X)Q~P}%bMOerW^H@d;3kAc_~V!C^wp|rfLE3IHoBX07qy*-Vu
zzOi+xAKVa}AUTwP1JHg7*H(nrg1>X}obLERE`C`LrP;7h)i`i>l`>Ancj`}*=QMSJ
zoaJ9YW&6pKnH+vmROnY`7}z}dc@K@isOFrugURl+!%5lLhk}Wf-*)JObUj-5C1N?Z
zd@Q+sVTB#Zvy_Xgh)cOq1DhnxinF;w6HUSi9u*-whwVcIuO{uLKf_qlR<f=xBxUDO
z@xzif?~4mPRfvQRk@kxLNY4iIKUx;oH&^*yC3x&1OW-gt=un?{7B~_(ZGI+hV|fJ+
zS&l|j)9eMIkGv46=&B?%X!{}5wK0kpU~zZ5MTZpg_5bz%1w$jVZ7NB8_oKRZ`-ajS
z&z%0hFU0W|yL)wk!IPxQpqsy7FFH8^nJI%>K4%7|+Fo}4JGD!haU&Z4$1jKbKy;2P
z?gi3n_r8_fK)ujp$sCFrgfVxEs$S3_P!YM`Pr3<}b`TN;*C<XE+yY~o8acdjHOBby
z;5KZQC79-H-aWjl_7gB}eofPb(><)+92{E#=HC`5Z<~W4aDjc%zJ$01xW}=J!-awD
z1cUymGV4@?@%a+>=SZfdtT#&tFAZG1ar!yXnGvGd>*r5<;`59;<MhLCktV;l`9C9#
zM=a82+HZ3lZANxwu{(8Tv26;yG4R<_eQ#>~lBrwdX&U?HBnQ3!IC|g*A6+4RW3uzw
z#(v|2X;!T|0KWtGYdJra&}Hl1{PK(7tbYN;`K1uVvKL|*xJyP3wU<%jR11RpT0Eu+
zRswV;(yY{JJ)N!ZK9znx1zaPV63IV<?AOE%=Z_^Q@%<R8X1las1fplw$(^0pB$lA;
zGU`+5DRWA<u9*UIx+fZ7AcIw4%I^ICEA+qt&X}|x$~_{k;}w1wV;t1Q^x5Gv{l9+n
zX|ty0mZz8m?}gpWu;&5=A&L^T8wBS6mxB{vh8CKC*sL!1Q*_n3otqF%-%)&4EK*Qe
z$Rq@jk^srdV*>4QhNibHnx1oCw8Z8WblV^N|M>wRtPuK!nr-Cd(#5U)Y0A~rGTTZ$
z4hm$al4TOIX#d_qkf$l&FQoWbUVpAE-C8wGavR1eByFF7Cy8+&P}#s!tta%p`F{5#
ziCkJkE=!NpnBU`NB$!gv`KikZc^8Mq2mmN;Itpx%*McG~S?d4@CNM{es?db68XZIq
zXwY0Y?!T!iw{$gP5JvK^PdMH9@?B(FcY{n<=i=kDGpXs0*2wjS!G`I{UBlFc+1ZJ7
z2N<}x#r}W54cy@^Y{M_4Eg-E6F>OYqNF&KL3prXPISpMtABb}XqMK^-kq}HtTS4)B
zvJ4?hq>dj||2A4rZk`8*R_hD8d8-Eg@Cz^0*<FWe5_3TO4xUKEYAFszNw$7fl7Hc3
zxxn(_kF4DX#;s~G1&%l5&>W8h%Z@^vdu`>X=MdGGPXJUBc`uZk&E)P@wVB`HHgrlh
zIDT}(8+SVqr64~H6VFuqkF&qcz}WZoRH_M>54=Zgv3vnW1(V(^%~U?@oz`R_>%G#1
zxsIwSLoub3Gk?{5-m#F;%MAsW?EdE_RcE8yw<cvNY0MO%Ptq`ME(7?pO*LEMv5J*3
zi}uIZh_ubP4<Vb5_xm;3vzJ2@jjppMYAAe<!Xw5CPJk>g1vTaJKWmE5%i;HGOZ~|L
zmJ>Cx!tTdocL~ZId?5$95kCqz3cC{I+IDI4wS^@FTat;6kHBa}-G0svd*&4}GME3A
zC1XOH37b16fgR+AHBneju}IvNw@EB{U}iJ>lXrvVv13asj=*zJ8KO>Z<K+jfykSg0
zymp#%6)1aVpz7Z2{teIh_`yaiuYJf?=K5k{cD2i<v9S>;DoLtQYJpd~y%p8_vdmde
zQx$3JE-s==y-N*gnVD1cEzMI`5*(b)dtfR60RtXUJ==mLE^7^G4%74KB2wY<{}KR8
zwX029GIx}^U(hi<YLyH~lte03yhwqgwdGi3#tLF%muN1W6mA@xZseOAB6T*eqLgzv
z4%ZGiOzY%9DH;VaK=?a)hmyeJgolM3datLx2z{EY#Sp{iaH`h%pr{|6vp@o4v!q=x
zUtW4D=Nc9(9$8Nt_mDxkChCu6G%}}zhU^mRmn%Ycis=xs|Hl$|(gyf>DdqJ^=vCzQ
zS7#?`%oI|_+qMMUg`+xty)9IC8TA9>OXM=y?(gs46QjBsQD(@*Gax_#U|L-pXCXH#
zxTJeN&UV`#yoC5shkuovT6%Z-W|n!jJylP(!8;ZCeD>UYr6lh>iV~8Xf0m)IZxtCB
z((i;&344;%{_yK>5$K^o9UM%*Xmi3wShzZ~*Le_$tkR(l7JY3V)L4>DuCY?6>5hgH
z5yHOzniF~%;a=<Z$M2lYslQr3O2a^??qFzi#;(Z_99@XkX#0zNsr$6l%$BY4RwyS9
zP&-d>=tR7_<-?tNaV+V7)h&Ua?xT&9$Y|lp*}ZRV7nR0rWt@<WE%vB{MYTZ27Ud^U
zpB<;!Hvx6sz7mo?efwb--jpSu{(pru&E{OY^BSUACUb|j9RiK6bMRTy3CpmeWc$}Q
zc9Hw{Wld<?eLM87P1}SK*>{t94|)!CUHA>N{;>Cl;O+|LNSkX^?>()uoifi7a@LnZ
zt{*0F-W24d(^bjYdq)JW5B_f~NJSI#4_#dbw~za#YtgaY#$>3H@5^ra9oJT(@BHhl
zCi8<+HnCJa+s6KnvG(Wx`$zdg22g`(yTws`l@WB(mV|F<l8N@WMtb_QrJae+M}$R@
z1&3ug%*049XZ`o;k+~6-&W>hbODx%&jRv>fhkJD6l;8ptS!i)`$L(5U1sS<Z_1kgd
z@&`I~D$Fs5-zdxmixV(z?hW4#N)}n21;Ctmt@o+F(AH77Td7~~8Ahg8aH4|s-y~uJ
zra<zzW0I{sx36oQ)l!x07g7GucG8^>p}QX$O2f~xqRLP$M)q-_)xSIA9IJ`rWYvQb
zIisFX<9Yiu5lpp|h6>kztqmh1y3d7$1I<cv#CqJLBxtIu65p$)h;dSJR0oxW$~bP2
z3oKjm@C>+o%-Vgcbo28NJ0@++hr5^i`&<Ts0Ph5aSJD(`qn0xlvSl?FqJnOvH9Tfn
z>zJ>sHJ^X*c5Y-EE3IT{+Xe=~GEay@Rdxa}lMHJTX4UPX6(!oRKZ*E2vP{EiUnD%g
zp~R(C)KpicPykv;`d>r#`x1NYs-*(Br`ziyK?2(ugS22Q@wwj&!kR;m3{-35KUi++
z?0i21fmXcim+Ii982>SM+SIMOG8e$h344pbic%B$8WZ28v#j7t^hmjOiFqT8B{gk#
zlpgx|{($!&GP8OqK=CY?3T5~Mw8)UiJ7!=`+EQct%*nO4i`l@ZcNh87_y3(=2<)|g
z3lT4>6@>UhwykL2Ef$)Fg}yFJ_M$m#4n+v~QZLu;Ej%&n;qjh6-z4K!YLeABJqC^K
zy!&?0?ljNfSjR62Cc}g*(P@qbzaeT?>}j-lu&}zGLagp=3p;P>HVaw}(O^sa`?NPN
zJb+5e1!NMX6G@N3Bz{qLLeQ7d&K71>ukgdU7$w^Apc_uqG*J~SA%B;0RB_brzk^nB
zYCROGJi1N$sy?7-p)$Z;wJ&hmi3IkJE>6;6Ol6z3uRxa7lo|rU{yVZ<xuO;=yCrwo
zbFxIrFQ}kdaME;K2VM?{)o*C#;g3m^jyLGtYx`|$cRlFBl5zIT-552g?>vQi!4+R7
zXT@vXuq4902^!DR0(Xhc$&z*1)tz=le}(*w@?@E;jeFDY<*!%cjEsNC11}n;!;ct@
z=n6hhMrC!2G}gXoFHMBSv44yieCXKXD!XfR+N)32g$g9V=>!*!W(t*HK|!rD(7TM5
zQfCGBf>sd%0kKPm-R8xni*?K;8_h21&PO|Qn>8z)sdnXVG~-Z=9_1YWU2uit59vpu
zP#{82WI%8#PGehLN+iW;>_OGPnB#<QmxAsJ6We0*<n?+m)bk+maCwx%OeO!l$=HH$
zWcn@&`IABa!FLY!=1PR=kC#tNwxbPu_vByxLtYKr^y*e=#9+7_7aCW4UA1$B7rO#!
zHXVrs0L`e{Z*Tk9=XT7q|73Z=MKD`2U35NXy71=W=Uzu>L2CU%UU>vSCvdy?$7Wy4
z#8P)lpZer|2Kr`~u1IhZ)ihxOx3E7K!+YMt%Y8nE+kW>uZI&?K<s~jCj`3C1ClpH#
zUE0sl5Pljn58n@*GvFi9+j;YHZWr?BB1U{6g`9=`S>jHkRn9za2S??-2zdi3WRany
z0K!!x_O1|rC7IlUhWC22WWW!j;}o`y8LVNtB@!(5Pnzx+x51RjxO4P8SMZ*8On%S+
z)1i7{Dq3D&s&+!&$wS@AAP?gXDc{d%19yh@kLaSZpDKa+3t(zu)A0(=z?cYBA4c^y
zwX}8qaXSdNyZM_W_`ir);CJlI;bK!K+s0@_d^6@i?%lELJr#{kB0y{S)BPOJ;b=|f
z{_;pEtZLYJ?dICXq{8g3AHj3y)~h4CwL)osFBM$zR8yni`eY)O{mwFJ8-1jtF_;As
z%yxP>a5Y6cJ?L7RNF9fKO#W{b7aU^Ow%%8_qD9Tz%Fhn+YHq!WWZ(d=f)HK#zQAre
z8?<-iQAXMS>YA{C=miZdV9sCMZ7;w&@3@#pdxoT0BK4#^aGNoefru3+d#93zte6Zt
zwk3q!Yd8P9q}aAk<<cN+M>OeF%!bl@Uc|w*bPMh2+wnCHapcp9c;(s&Ki(d)(;Hf^
zJMPOie*PFcf|0*)DLJTcTuN&HaXT`pDk13_@T{znO21LM2b08cRHy<}`kO~%+`(}A
z4rSn8)&3I8-+323ehiF2E9;yT%N{BTFFC+nI2Bp)!aY9vDPz+ea`ZN(JydX@G5i!>
z4shm&P}qw^zRQ=%=*7sf+_+E$zmRFITw6>8qwv3Dmq4|w33BPVbMBw~2y}V5bE2iw
zWiz_{&W5BnJkA!XY|}KZ+fc~HZ)VO?3}%N?j@Ej;j}j3M6n0KeEXk9>QC3cqmD`?!
zfSuTT2$i#%Kd)&yC%1epb)RYA^7dm5J6$|L3{!UMEx)ioy_;w>`9%4r>iQ$EW<PS{
z{a6J(bg`!*?t#K@>Z)KStsY!7eGAQbjS2Z0|2F3>1gNiUg}q_}soMC)P(*dS_95;v
zbnmhF{kkV=_0jQZ4zNP7L>Qb2Eb&l05=9Jmi-~A%lIm-6@NTj_CqabRhlr8U{}r)g
z(#e58`gBZh^qP4Hiafc1S}%WkWNr5PMUG13GhJjOt@=2$-}GUWZSNk=O)~@Sn}{<S
zz`5x=+&q}~Pt6j`ic4e>Iku)YrT!CXn)o=OyVyFHh2%ms&y5_*czaXI-&lA<Xv7hI
zd<{=UC$kTvp#isy_(P*l2UbvC)~9>NpJbqSBuTAEv@~&L*0^>BaDaV(2)NLnT-PU{
z^y0;POd)_+s=_p;^tV6U9}*=8s_HENt||JL-lgEX(vi(@+94Y?c<#zGOBep<=ildD
z+MQj-L&{WYMs2mrJh4Axsoe|JQ2k{Q`tS;fk=30N!raefL~D!xqmb#fN{fh*0g-=#
zi~tqt)N7A1uFm-`gBzLj=c{@u2=@A>$r)vr)f&JGa7QJ#xpfi7m`it;c4q(ZQ7ak|
z)+H)~lb(}vmct!#f5S&xu4iYxHtnLz-E2jpmQPgEvFYX2BMwP8(P`d2%6vLEk#dPr
zaPuHBOtNpLJyyAVFdg|M;576$U#LtbSrR^1Q1`e^DNgpk9egVHvrf}@E+)&^KRcs6
zF8J_YE4kQ<u69-nT{~3yGN#zD6mgV;OOS$8w3V@x2Q#dcHxj89jCf)uYaZJ1W^UQw
zFLVHB(vn^`oYN{5v~N#|y#V};bqzS#U_ED;AKQ0%@V-V0QK@VIyn$7K1LjjP!Bi67
zs5Ky#i*_u=nISDbd(I(`h(UX3a$8L$Sq4L5bSGJ_q@?a7oA^vt&YWb^-~PlaJ6q%%
z=#6&?u|v`tx@7;AXo3Q49@cd^(PY+5Qc|KD74`ga`vUmn9w6Fma0x+%HClN0JyuLY
zmTarT_~er@59QFjK47@}^&+4CK`zfx_nG7B$Dg0AjYki`7~U?eocSrRtL&4akf$bJ
zqhEXhZUa{AVqoBfOg7d&@T>^`hKUPE?|U=|t9Y&0>!1}j3Ru(M-X?u#sG?D8u;a!~
z3HJ!X?70AcZP~>`Ao)zSBmY*X4a`i3EMZSF`4mD198Kw;<B$x;`f*6sH=+9o{3(X$
ztG+=@GFXSAzbbCDSY#<)`mVW7Wmww~WL6XZXEwZw4hu^`E<B#Jn+iKdW6M>8C;QsS
z(?g7}$&4w|LqS1M83L)_28MuoRHMqe*~z6Idxxtmk3zKjlMRdC*#8LMg4RJr%{0m>
zYCQ_bCq%MBE5d~);Y%G8PO{68?cLj1+<ZoxNn9d4toOm6>zR+4tm==EK@sHU=4JMs
zRTlE#<?+!O9)1VBU+8xcf%eQn;CKBZj=243X8vvEoe@Vs@5pu_2GbADt+gCWnen6r
zyjRWFc38vsD|AE+DmR}*raHWO<QJ~bI=@I1yd>n%4m<-koPq#rvO;Z(=XYeJ?`IIY
zsxxC<TRa4I;E%mKxg-*~yUKCS!>itbURRIF-6Iq2*0K~=-{~gIO{jXmkn+O4=P+GB
zIYIw0zHteGb0zIQM1J&AAr9O>I)1-a4yDx`eWKBIg@gp=j&MOjV{3NWeW!ZMV8E=h
zbP$SXQ(LOE5j6}9C5qb9S9!sQ-TMm;>7k+`#pi#viM+I#4slR6?8@02D|QPywVaE^
zL@vEcCWf=U9#s9AfB?RKCE!#+F?g26p#I?85Q@0%ssEH*v)-M_9JIw;*;8P0{VHcb
z*c168utLhg^($O4uoO9-dfzu{C9hw6*?A6`JkKQ9C}7>60`~)Eh*&aO-r&SnUQbkL
z34~__FTlb96IL2n59lwmiKz%EJw8;q3wmE&(2E+H+6tNH{SfQr9Xmo5l^35AB+D#_
zAyayoRNa#{-lQ*j%MPVGI~LxD?rsF=Kd6Rlqm=6in<ox@`lCzT7U2GjO8Jbli?vet
zGXL;N0RhVw6chrF3)mnVd2+beM4P}(ai;$)ZZwDKYKvdCQ!7Z1%A%eBk^{V@=!<py
zW8_~$bkI_QWnZJ$lq#H<=2k{KvNlyr+gdd7q9bT&zq^cIM-_mVCz=hfFT|9mirwiS
zlg`QG5hEk8wMI5ZtxR`+&QaaJS2u)g3@Gf+6jzTCOrruL&FZdrcWySiu=OGxpW^!Y
zCszY3vy%|rqe}>WZH|7s(I3^WZV_NeTrRzj=vlT{mKZpSrziD1P!f}{3%%;nRot2e
zHiiW{wU7E16bV=BN^XnH^=_``GvO<#$S%o){O#u8>Inf;je;Xi1xc2I2VBVOv4VAR
zvitgSZi(H}tPwZ=y))pFG#bb}<>ii3fjvWS0?Dp~?M^B)Fj*^*<;V4FG8{>w)~*NZ
zOc6J|=Y!(rAjlrKG0_$;DOn~f!kG%I(8;u@n(BN4OU=RHvV0SH49x;VN4c-Jcx2AO
zcAw2OwNT9@ZodC`U+-<n7Xqn0pbpXPWVW>(SlCk#@lrzZw<(rJ($lxyr7f1<Wc0em
z|CHD%J!`4+5`~!9YOxq&asjbORn@JeR~B_Lt;uZ(l{9Yk<iPuYJBIz!DZ+^lRN(er
zmqc$wvmTL%<93D0H0R8^ZVtGvKg~&dsdyR<QAyk|J`uM-l?Vvz$$}d-cbK{8Tlp`*
z8Nm(#b%m2FnS<2Hf&6?~<ub0j`2`#pyVn|Jgt`3p#07z=_Jg4TOdBt_<W<R;+_IGN
zRYaCYsDTa}G3@At`}+!geoPmgKb~s<3wFIqOSnJQG0#*ys%tfTDT0*W+=REPLtyS>
zl-%A*?d4uqyo)AS+jD1Ai!bOvaUk$>OZb3-Hb_))$79I+b3@R^p#cWvm~ru+8xkyo
z&X2lZ_hl&Pe6^x)$(c0)e+WEhQDRo97QQut3J>|0TA{{+YzmCe;z&XI<d@F6A%nUz
z!OjAn{}7))8<pkQCD43{2O&@js_$-s|HAMch%Srv!MDj>VV3J(sIa?ZSwRW0cPzzy
z6|>5fe=c5wX9FLyW)t3@YH7MOl$AsAeZF<a9WpoTaL&FPW=u@1><=T~e<B?iIkzhS
zCh9O;OCj3Y>AMgd6%<%nyxpMK#iZ)2E8Z74M>>hR*ERI3t4Aet^r;w{VR2T5RR<Rj
z6JP{&xoM{fT0ckT8aBk1c$0QU(bwbHy^BHya*2iZUzRN(i|%!C<QS~{By{Q&xjXJv
z3GP}3IFsT(qT#Q0%ehEI*Q8Lw^t!RzMXq9QJZkCX>?;ru7TL=*fyr&H?Av7f%+WE4
zb<TFLF>7>P#Oe1Kh+a99Z*RXH?4t*bNo}r;)@`{dx1#by3|j|JFrC^!`FMlWs4NzS
zv!osS`=q^+6OOSxCRN!6Z-z0XEU~g!ho3!^K*@`F<6=%u7^#5IzKdTzUrgV1?5080
z99oM^(n-{PiCU}RgX-s+zq=Y%n)6ibAD%8i0S_?y=9=GpJ?_g0=b%#}*-<612eO>=
z5p_m85xH|fn*BrERM+1X;gxe`Ndi*5KS^26Y&4ZEM6EYsFfopaH9H0vL92+dbDM)K
zZ<mBzS}7n(_eQpPChp$6r!_9s5qMF7LM#g{ujfz;Tq+B-`w=oxPm+nxQ^|UVLsm5U
zl&)j(itnX4FV7*^lZ_pyi%3Cdo5p+4e15#@`;AGS*~(4J1$dOy-kgVfP5lmc(3+>#
z)`<CG`U>(AP=4Q$nGt8ih4^?U4i#BI>y3F&Z~oe%!SR8I>pUJS18&53)DQBr&)j3u
z5J&dFzUhn^I^&k*c!_choM0lk%|#P`@90h*MbD>guxq<3U(Y}izSrvCtjoF*_qQ6H
zZ?F7ug9yXJ^y1P`4Kdk2Obf?Na@z54I41b`m`**p@vKSXsAn$%G6HNRR5>Xy^L;gH
zc@oqg&(JO?u<kuqENvlcGHO@?iVm>V%XDcR?D-nVfibHSuJltTDU|~EH^9*SXo|bH
zW=4QN$l0!C@Xg%frJvg~nLv4$EwyF8<6Ip)#F-lPcYY`wce69?pdW%`OgYiLWFd^`
z``(NSu?i8Z)rpd!m8w72&A#8Nd=xvh#`>1skA%Ha69-!dKgKDjx{FdUXU(Q=n2&;o
zA^!3*;x{fPIF(np^JDfMcSzUgfB-zPqz1s%6kth>4Cuz#*Kb-DegAPhiF?Wfun9on
zv(fTj`w`fe0vA6Jq{*9_Ry*36)xxH&9VY@RduJR8eSuANGU?!3pWL|OVxufziXNG-
z3UH3_herIh+F+3>%(2|t?{DQ<9u6s7d^f1d09sBXFojG)Kg3O_XB>_z;2L)gy`?29
zl~G75Nkh{*8erO6hz(Ii>%81SGjsBY1gNK2y9b8WY-W8yzOvraTh;?a40M~we^I7*
zrbFfO3#q-ZzI(Nd)K`M8rq$i&pR&Cn+Jw`NG>5(-a;wK4;c$p{2I3qiuQqtS(54S=
zsPn}2L9Q^rGLSsK_@R7m`Eke+mWT(n-6mZNL+tdsg6^6)pq*q<yAQgCn6ECa+*TP9
zcq<-x7<(Co+*pc;&w4(a!>&L<N+X(zP)!l37kHwfkp6Jl__?uA{0)kw-JSKhn_t?q
zPK;5-U;LKJVR6`-c6{eHcv4bmwmm9QxNbeZB-qN)2O=UY@(vZ%xpy&hq*tF9XougL
zxlC~zST}0M9O_5n*X&cnWnFs4<7Z6zqJ4X9QR+A&hpB&z?U#{rJ>iG2dhM1|k9U4&
z=Y!*;d8VfUM9r@4_LO}}zb_c@9S2(_cqA`$&4ad=CA0VCh_(s1ahqn8dyNRVS-AEl
z16I%n;<-P)^T%j)axR9JEMH{6_h|1Z*Cj`d85}5Ia)P6n(7>M<Cr4G9)apo=(mr_r
z-v7*#B-pB@XHAU-J&qYYBgJf)tCZoJT!*`3K+Bjh<o@2`1XaHN$H+N*%$)voEM(64
z2t3dxE5ua(Q3&ScgDdJ2hq&kYT(<?l%XN2Gz4dhbSSNUzopyz@*>a!#l5u9Ws@G!}
z+3+Y|`DvR;kCnzMFXz7DgK{=CNhn8HIV{vMwLD%{WB7TL)X6e)&W`>Ne_Bh0TL@T&
zcvo(Oc?2F9co+D6yg(w=3})VomFjw>n11q@<C=Hxy{Zv16ov34XB=(fpyYQC`Fcdj
zi^q8U)*h-h7&2@Tcs2L02nDt<G5^5T{hGc^f0jX3)^{_p2C?&5|G;Y?;Z$g&tqv^H
zGK7|7u!m%<Ftxj_-~om|{ZkwsiPi3|$GaYvte5t><+D6zV98KAR*yGbu`#c&z4G(C
z{@n<P3|35kY#V34nArdJ1!unAk%=koa$j=J&-u&&#!L>AT*u#g{ehCE&9c3PcB&G{
zqMZh*g;m<abR&E4zRd5P5O7!?nTke-pPfryV4lga==Se;$ShC3XJRG4^A8Vd^{8lW
z`0nI!B~=GR8cPi31aP{_Ha$CC8Vmd74gbX2D4@Inz0FMPKQn0_EK=vBJX38RH2Y;4
zb;)eAEOuZMOeCe4e;6Qyt*7A3{H?ck`p9)`^V9<)69<%9)oW;R&cSS>HGl^sZAn>n
zg8Wn&;%K$$53}f}S`_w9&TAC9ft@ezGL3S}N0em;{v7;y(3V*L2kvoKLYR)Aji*c`
zGdpW4wOHiWWn-(K&v67M&7>s~7(3H>ssZn}Wa8mTwt;|z;Jk0gjVSP5nn9u~WdWt8
zlnhpV`<$igF;8w)$(vuz7R}|_rF6<^TYL3r@aQyfrpO1(U=kW#R#v&?M6SCE?h_nd
z>K?9LWY~3xk8LfSsajSLzikQOZ-881PQQ$sA#z^-SV@mtusU)bV{Vvrq|MxG-VNSM
zwIL`Uz<S?ub9Do6=ZLNikMa?xA2|v1Je}%wg#8j7jJP)yB_t$*9{Sd9Z^EHTdi03x
zT!nNahoW0h=1b%ZwS*I$Z;}Vcb7=pzQtjh5*xmK-Nr38@pU>CK)65N5J~0<lfct9%
ztnk(2VkgEQPoX16aP`yYZd*t{CiHx$CN@0uaQMoVtv~23&Rr_I{k;eibVJ}1+bZ%7
z@=o9@>b#2N)QV-~eQZm#Ge6cI{e`zZ_Sgc`vFl=`IWXYBpBzzFZl!9wgxz(&;joNe
zI@oh`SUOlrNHwf`rqIqI;^J^?=~W{6^*dKRyDJ44MZ<FB-4nZ-{WBsspCuXAEp!WL
zf#+~p;IVi%tg(9?&FgpIur&GcjB*QWuBD2zA8!=tyVY+8%0;5QS%}BBEm-fM9!k}`
z;|U16oNqa`J>=+8eF3_xO)3{z&}x*?mfGsSukGUHDM#k?m0M^8sxJoq(Z6DSo#_%a
zH9Q9LxFyM=VkWfsn;Mh8ayp{pK2Jji5uBDAc1C_;BkT_C<GlQaOA{rYgb5?95uQu2
zM-O?^op@8k;pJdK-zzJKsJH`fCN@9RTgsndbL-{1#J@p8KAyIX&Qv83lDf<dtAWDc
z>U!NCOG}*7Rr(%bm$Yb9t6Yc{nY?3?%1arq9d#JNd4^q|hhr+#y&vPgy(2@0V)~x4
z(MS&4+<cPTvZS@W9b=r(8@wom`N;NqVHSp&PY)fzJ@<qupRtXDIhjHVYQC*Q!6rA=
zPI->)vmZNW-9A+mz0PI2Ma~VoKE2qg>)+oW>YgDpQshuz5`dlzmy2BD>KZ>23#oA)
zhF<1%=nGq{{;~KtO<5Af%Y<JQ?B+Rae|-As!l3ZGyU@uEf=1@rkC$n{?4mZ-Xfqz0
zq(2krJ*bxCKEFGgmVej&3%NGJAJ3}SWqm#TneaP;81|3G@96XfePcIBd{gr+{C4*<
z0?4dpbJd#pSt`uV%AIoYP=`v@!g;G71zWyWe(<6HL8%K%J@>Pn;3uCb`X;*isd$sg
zDOK@No6nV-&*Sf6CSuPPGdbSix|VY{ek6J$@-qQBV?)*<-;W0Bi&xydME(7+na-*c
zgIU_=>ktn3rcPHzM9pasexx~>TF;h0fAR&V{^DytX?L}ghluj*PL>qC-471ioQMSu
zn9jKBA5o6;q_pS<RI6Iyc;<}TUhk2FCW`fJaTB~$b$ptVEw4|-LJ<1OzC0IWA*Tm;
z4m~OAt>5!VNaSDbox6>K@8KnjW2{B}(N<FPt|R;XW@}fApBgsb5U!;B7HPzsW%o>?
z)wL(9+-f|H2j4Gbmv`UKHCzT#q%X9F?M=NeAw+iJTWYeG=K+_~yVsodGmN#_L{yO3
z=;Bhdp(~q%*J$o4?fvi(bpRuga*qQTMpgVc8O(HI&1y%WYxmsM%-0j}#T=6N6utBK
z9|#tGHW%YI*GeqmlSA%}^duYeHXzz0$`XRLhM_jEG{YtcKH5s|M?<1S4j7sqm|f6y
z-5};eGuyw1G`wtScNlWM!N(RO7imWHD?X5Qix-V?Vc@mtr~)r1Wy8*X#V$)E?R`DJ
zEFBB6{}N^0qe)=ZTP^$Cr6*tAz|f8kf59fP^j%X<?ydoya5S7woCo|e>Uw33bX*tF
z;5vn7%-L$ToExp#X;n)hT)E$=2xKP^4ozm{`|s~5=JLcsuv4W3EkW3_S7BcJTgDC5
z^XDIXA~J~v{Hg2*lIhK^^l^yAZGU8940mKY2NMzC-?+ep%1$`mSEm$o#9FIyR<q==
ztdLx!>+r32(-I4f2(b{NtSrcyzT{#hc$$={>&JcAYZXhSsjMK?Piyj*^D>Bf8PcO)
zSo+UhWVF1er!2v4f%-A0uMAe1;n5Y5{a7Qvt!Q;s>0aIi+)jWQ_Nic!+KJHBUE7Uy
z#-fWIk%swJjQd6a6&40HnZRn>Kaiy8ipj)PvU}L%4G%dzQ?;91Wpd?Wv~snlq?E$_
z78FH>Os>XIz_vw$r<f7f`#cGUL6=Wybq1U8*gV#bU38lBtzwhf_)xde58w@R{Rttn
zqcSn*GL3vjThC!OJp-S7|F;5yTd*Q{2+up~slm%>9j0Q$RZBz~hKf{u9{M&vj1@xt
z>RmaauFsrFUNV-7N|^G}+&rl7YX90_clZ5+BI0jG<yRb(+>bjgdbV1f=07B%&&_e6
zlPqm7)VQ%F1~ZV3Anw`fD>u^*=8odq$>uX<v<-WS4cG4Tf{<w(flA9--P9TLIb|sw
zdtn&bbN=s`NvyR@nWXc8(N`MY#HBJWNi;CllDH%pa%~`E9#Ou3Bg0huO-!bC*r362
z|3Ip=Nc6&c_NomM0sx^eYZ6j)SE@>VKl|@@zif4TZ?*J8mbzJZS^1z{;mggLg(f+K
zD%lf-fecyMr*s|Yxd&XL7`^iY0-k2IA3sAcyY6$GdxU!41%cl^rJ6E47RT71l&vgk
z&cZ$}pwb^3V5u~DFs^m})(6&D#m(YW@h<De5X8|;pArQZZ}gYSK~}29F5SCV9U{J4
z;>#H<G3TDYt*Ic%W`W{uI(TCQ{_GZR1C+(EGhxQnPR3RN3Emh;y?fFb$1m$-d+jR&
zf!A;0al<wme^nE(dXTD8e}+xyu9u&Tt^Xq|w*1gPsr1xf7RP8&#>TBfqhwqS93vVm
zWFFyD@8^4HSuR-c_`9xKtDtR;1wfCCoqKb7_7V66N9cR{X%xQQn&}Kghc~JByo?};
zZTUpFu=*-PpA+wek=>>@ZCmDmJ(BCDR=q~W;<_?qnfdf*cJ)pe`rvnsbH(65LR6K>
zYtXUt`t|4TB4@w}u6_tXpbOH-qv7~&RZRh8u&qNCm9AyUmbbotrjasJhmU1-*k$F}
zhD=@W(D<s?Gx1{nSyyP(qqKY=(|hM8K2!Wh8YRk+d4SmM1j}0ir@Z4+yovQcTOU#;
zM6Md%H6N(?{7(u%&1Y>&^DK0kSw%;!wE62D{FMA`2bwhFw8kUj!Pj*~))8nPp>h&~
z7_J8nqpr`Bhr>Kw_75I)zi5DwZrO<GWBRfs!Z)L1TZ6Vg4;zc*367^Z!PF7<8N0M4
zD=|+-<I@-yXylQDv2tW^)Qu+u{X)5v2V1%7X%o^Qd-yMxlzq&Q*=!C$7+BsmOlaoH
zy?DO`yrWVU^7(p=skX<C2VIAEzHaO(L%*_n+uJKtQon7?Ej#Sj?%Zus<=LeukC#Y%
z;;-K2^|#&PZj8%C?p-dOI@H85oevp-I>XSZj*l6E4>#pR@Xv4x$=><em$zkO1OP|m
z5^9sg*nVNf5nyY}8s~JJ8UcO&UFt2N6}nH8Ys2>z!UsMdXr5E%9BF;+8M+JTNZ~zX
zD%|Kb*@eM;A$7B(U{6yR7xQ=qPo8{$WzVA=FAlQ<3*lnIB_8B_COwssU75n|!|b*_
zm$n<ZaLtNU{z*Q>^UR<!(cRi+2<69bS%l?_+GJ(I6~q0^wH^Y!tG5T9!fUpu9F(j(
zlNZhM6Kz>9h%0jA%CnL1!QN)HwS`^AoibW7b%K`XrCxkzX-*fp80q%vGA83|#}jId
zHN2Hkt53P77s$BJdynuJVvlDq#iZ~G_i~`}IG$J^18U=YBsASo=2?5?U~kH%#p!O$
zJ+LG6ztZkeeO<Km`uDyjs3>BK=8w!(x3~=(FKcetm6%5jyVUECJ=6=bQUK?9fi1|o
zsp!^6*NH1#XO>rT&{nOByS887>`oBY+6hEB;ysWJ`O1}l`+UgMeK!_wv!SfB%<&O7
zs!Z|L?&AygT;doFujIM*n)BIL$y&~dp3T<4!>tKx#{do<4!v=6wW@v%$oVY=QcU>f
z;lm5c45iiESv~k6H}j+2KZhVxeUp`IwgpUjJBN8YAAE?*;9rXG&#UAkP@NDS%FmD~
z_%g;95X^!%fGEzoN0(4<e8E|y{UdE~WQVV&)Q32)2NgfM=}~f*kR%%Z0!7|~IhoZP
z2cPZwzH}`W9I+mZhFYvgGN|24y}uZg0V&hhCUc3s`zOa)7^bJ`6xzOJfV|O+jcN#l
zX-d;Eb?c+Xi_Lh)D{p3Mv8{Ca^MpO|6%na>wGnylpR8so7{_o6(49aP#U-$V63tOZ
zEunqUr8;sh7hIoR``qz3_5$F0nVT&zCO=QF#hhR&$O__xH?~Fj8^umj(u39I`!(k&
zrSJh3D}F%mgcG}E>ve0H4)e+!Ome_dQrx(-thu7xF0g>#U^v+Y7gQAs+}7|+@-t}~
zReeH{WMf1pg%5&_8`gv==(q*{SO}rvJy^|d{}JS*@WDxS{<U73%#pPNx0Y}``BjXF
z&ci*~`ApeY+zl!GCN!&`NHmHQR(r7#nT)YR-_G$dyIXG4ec~SDX8kU`*TNHY)spz;
z@@sDOPlFNR0O?421cfgrxXd#(DT-QE9X@zAAI#_$_YeRX+do4o?CiVyE%xM3bU0<c
zvuGq5ub#(;<;!i#dEEFD(s+e*N$P8!rpY$i83f*PsXmqQ$H&wCFSKIWSf#6f?it#~
zy>hLb@QD`x_&A&g_Byn7tN=~*SvStSPIaf&$HCfq;L?%Bdq{gIdF&##+dd1);Ud?)
z|7lh(<9UNph1FfKuLDmprsgfL3d7?kb!9mslh*7CEco44py1X3C@#-XNRo;wKMro#
z(Uwg>bmMvRtgpiI$1pdW*aSN5jcCZ(TcbOrLN7k4?h^!!jO}xWZN@-0mj@Uv|I!O7
z?zMYAwz`gDDIlNH%j;i0FI-CtBQ3~Ms-26D)%%+P4~lJ0;5%L2zbEO$vwapXlbk3-
z-}f-t?zzjF4)p3b<q#Y_3f(ox#c;kbfQQR}HWAo4K&ZV)>c)J=emA9jc7YO90r}++
z7Uc^xL3bOzz08oI%LgxsW_+Ld^uZEgIJNt^T}mtplW(~-K;omroaSM)D12M4W>B)Q
z=XsAyb(WXj6k<kb;>G0Yd!e3V8+k;aG-o^UCToD;snKg#q7!;^aeHMO|1h!AyreE=
zQ{MvRy8pb;IfOG|VP0%=fV_OslncffvcUtR<&QHgv(%L7g1?7cb}$eBJ3xL+3Do=S
zZQcrqHb{3ixB~t_Q^;aA6-`E4Nbz0}*0-@sp@V)#<=XX3{tocO&VN>WPm`GLPyM!^
zrzq1Vn12C!bgZlBl(}a%EGHxA$w@BNEmk@_*I>^{_YyV11%}EbUzZkT(_(#%9}yM9
z)~*_D#a^4Rq>-qdWR1e2^jzJ;jJC$uz%N)UUarJo!>>5CFsM+NFIaociZzawFmscH
z325LxxyY`>cp_gz<>tP{7ghpz2yTBYljLi686b7rK&E65-X8~nVS(aE1_cSPX8nNR
z_3PJ<g0Hgh88Uv5<C&1&LrH>Mut?qud~w))^`4axV8p*O<HernxxU6*#uu;cx3FKA
zOuU`<(sRZo{O>B}6TW?1wJbPCI>_IhTt3#rsT*2f2fLcpid8w&nVFT{`ueD-n^V_*
zVItWnFw0a-=6Z0<eTr#KE>e+;iQ(tOiS`~oa+{pYYu04Kp)q4^ZnmhGs9%;>%ehck
zrj_OJ)+ePx_Sabk*ZqMS5B#|qcwBPu2PSYqr$er%r3hFlnhOk+Il<o%CQb8&_p5Ne
z9?17iQi$TMFH5O${Lw`h^@j89hYXp>aGDa8T;qxvZlT-^8Lhs(xp_)y_)wFDtaRX(
zxp;7wKrDm{C#k;%*s+UiXpkGEsi{{wlYe<%`f>wC919sRPN*dQRerji`|_!ALa{q}
z8*ujy47*O&G#fbXGv|?p!~uRGHGXk47mnC@6(8??egwo}@^(zM%%dc9p3MzKCs+$I
zc4L(X6)O>;_9-ETzU5BTo3;=-!Y5tN<4Bh?^g;@H?EGIP_8hc!;pMfI)TwT9=2S>y
zmLAIWP%A&!q8r0ABXE|R65DjA4uvg#NM3rG9htdG!Jxu3nCC_VBs8VFvok**{<8mg
zsrf6y&go@H{2R&8@Q#1V>IP}zkC%av9_-UbXaLKlF+-*UC~1NU%s0c=JsupKN;%`$
zVQhD)6kV?>7ylEoC&yeFx`EE8WaKQ)I8$2c^(HxX7i(Yduj-8TJN5aAf)BlR1R))o
z+dEiO{WrC+P_cNC{6tszqbYo71PjB|)D?MBNG^O@J}0q^)$3`v8E)1rFTrdscA~Lc
zT?=utOU+?StMJ|*(WP9v>iUKP{BuEUwe4H-zI((=(H<W7DbCAk6>B|4z@ivWD}Oq9
z8&XwAcynwF_EO=fwbVie9ku?UD+rV#t6oj~ikk*4EjBmZw6jYdnZyiJIL7I+ZOum-
z1>IcU626zkjBuhH_WaTusHfcgvnD}lthsjfnHXNj4J*EfgwfK;kFFfdv-CBu?TqHd
z#XlT1x?<Knz)bux5~z!hh$>kHZrFQ8@SmRwrQ<($OG@sBWMCxS;YRr-O0u(wHTz_X
z`Bwm}1nm>uxR(<8HN3;{@jjE&7oSzjnWkk3#c*gzyO$hUZ9!IJtiK!?u%g`W_6Hf>
zk_}zZWVlR-i!{YtryDs63IyV<Xv<F&_kQJD<5?Q4L?#;4@|Ty3@kQH7&ONWnM?Afp
zQrGr2GW83B1qJBz`<ul3$)EM%%AW@b$i*Y(>Zo9|;aus7k5i2?@MbxLf7`TpAALp^
zPlfr}K4h+tI^>8hw*O3-(094)46m4^?RNy%E{EiwjfMOja1A53(4$1>i3GyS);~0E
z4ja$yY^BMa5W-##H4g1z9@W6l?l2!zV!U-<pXqqUJdj(rO=}^tR?n|cs$MJFeD<vo
zz|wfdCgXbzUVjQ^$KL8qui}e>;(OUmrpmMV3U@t8q(hqdhMufSj1s%sZr?>>#YMaA
zG?8mJ|3iG``Yzc8;_sBM)K&Cq(G(tzZ>Hs&{ZjIt;81EoE%M|Avg6AnkDQ=e*eNBL
z^G+`Km;4(#1s+u6){f^!Fb{ym)oR$Dr1Q*Yp?YKZNpBu7<pvvHO?!4fXqeQ>+B|f_
z%Q&S;@k~RIXOV^|+bU7h3L)?Sma}PdWvnG=dTWdGnIh>1+sLfTC}oG*fyJ;na`>qO
zt7@(jZ!|<|JKyi^H(uT<zKAoojJ%!`)zxixlD{rn-`OU|(q}p2dDfon9t@0NB{5>$
z^QTxcTN~)|_J$riFV+bzjH6XQrbxJ6{jP>4I9fAhrj%j?lD}12=;P%<Wwt+eGe@KB
zT-&u=M#jK+)8hG$dm+`*9+AA3sIQQ#f^@b+fm*#*4C&6nym@!BZ<$8?hwDWa4S7%0
zWJ1m7atRc{KVuHKO6>9-QEm$Pmp!Mykpw7K83*c8UrQ~&CL@(%aFgCcnhksl$WCPh
z_17g*tq`wyi;1kW-(6kL^0few;<UKRtXM728s5ucr=@U5i)ZkOGC85kaa+;$;=oNp
z%L#wqg^;fsQ&Bu`gvqA3YqMpRH?GY&;2n$DELxj%-%&aU&S?8iy`F4U%Rk3ya$&gj
zwJ4Ch#2VtQI6KXe>FLS-dco-!Js*z*cbGA_&$r?4tetawa=cfc7zwJq50$+G#3aPD
zd$fFua{B!}(}8g-u~^lv;QMr_(unvTu{7P{Fs2}o$un;grex&$u*Yr>F1lk|o)qc+
z6{ufgYYA20;}TD<3RH)p&!)D>-#&y*mt@(_{(xfJ3wfDBN~jMG`mZDRKSr53Zof;@
z#<xH%06awtTA&C)FcxP`hXL<`66drs&9(dO&xzaj;m;WtTCb=TcWA^3Trz1IZjJB_
z-JSM9t62L6CNm7aFDMrX7~4oFc1x+$nAOlyUFPqtFA9!Zk>eXIGcQsrHG=2gwd$*e
zd=0!gBeWp=fH<_iOyWC_5;8f<OC-O#8k)1w;3m$r4P50U#)aDBk<!LzO?GTGS+7b2
z0?ca7Q?iseQbKm(j}MNtdQ~pJry@K*HbX=VG{;Y^eDpm!tDB?k_|#=@vf^qnOlRS<
z`bcr=y$DXD%P4opxbFLLStJN_r5$0~ZHe>ldj}7CtvKLswi_xXdoF|GtJ-NzeC?OX
zbc%@aYGY`u6$6OQpnSJ8tQuuEPquJ<nLsAVkrhsla5XSg*4N#cvxuJLRE4wopjT!(
z*t-M2L;-01otpgaHXsw&ckF9xcN`lwZ#|;MUkHX>o%L*3>M*{BV=9Jq$iXp^YxCSH
zr}(t#nnGhYbUfhEls*^nDKlg=>dWR{*g5&=_%{N#DRMcCEH;K!Xi2v3IpFVU{c{Go
z`TC2`u2c4(sSU3wx@*(f#BHO|i=sjfRx`#xD0W(h{FzbTEoayAyJV83p9np+BoiNf
zhN}z#Ne)xPP%PqE=HSIO`rCYk^cEV!q=Rqmy)#0VqWAY5Lv9(i-Gm-~M-GzqWlRkx
zr<iSC4P9Xr!n3h<^RQcW+v~sDYgM4{ei2)tkN{i_qZ_|;@`r+)aO;h{;-*LE9?fKQ
zd~It_e8UNyD#`NtX7nO)o#UZhx`S&;lKK<3dhTzF@uZ+u{MWs^@E(<6fq{l!F`jWd
z-z5CR(ojU6n}5Sm05yL;1I;Py{n*v^elg>jYf|N9MhfjOY38GXDoIDWx4{EA0}zn!
zX0>=vON6^FEPQ)H_s4#sx_GF~X`V$P`@n7Zf?l{jYJ(Epd>uY(Y4_O0$R+{}J8O=h
zh>85Zk-k|J3sI9|s0wf@9S1hxul=3Lhx_Jv^S{ETtPK~5dm%TKY1R5Vh5df^d&p83
z4tDf&r8S-7#)Tejr~`d$8X^7D+v=d&Ke7__ULt2FZwSh45yPs%`NeJ*xzp@)sb<8w
zxo^C}z|)YQ_@6yd2jz%n0AZl-AReWNw18CW0fPKVyV?)vauP<9X-fXt`HY=X%CATG
z;pl;YPs<lWnP%D^{xa8J>Im&OWVI$R;mh2>zes(K$*L|aIGG5Pb#f+SQL%_SwoflM
zP1{WT%c<zf2oynW<`F(o_daz^-0s;y%Jm+<%GJUxqQSv}?Fe6-mRj0<!&z0$N6um5
z`rUs+kZ^F2b2O%@b%*SA%T;|z&3zr_XIeN(1-zp(02cDR9u^QH+P6Htli$DT0K0_a
zKukm(R}Mn?5YD80lHBhZ*^835vu5QfvkVxb4&S%oghX2>w!QhI`HN1Ux4gp+4Vw2q
znW4UNF|`}Kk=vOPkmlwRg{Qq}_xb-Qdkd(lwl-{3rKC$5L`eyyyF^kYl<t)7k_M$g
zN)SOB#0_k^k?uyiTS^+F`_2t`KF|Ms_x|IK;n6dOj>TH<ntRUYed66Oa(>2^vF#};
z!%&AbyW+*xF6*!H`pUvRh{K4C*#2<iF~t<#FnZ=A_i(f)le~A9?xofH`eVGd@OtXd
zdtyZ%9b+e$YvNw3U_6X>Tg9_wy3D|fNq|20te~tDrf!vhwxkV7`O7Ee0b0WC%7ZLr
zqi~ylmiSZCiG%H<#lwL2I04OOrO%#^*|Pf40|ldP85CM3?2Ro8tEBn(ElbT<>63P!
zf8!=j#WQdsI0vgU2fK|tG=|Pb=7?L|k*c@-)r_82iw0}c6ndgLHPvG6bUWc{*tPt%
z$BmbkB>bd)=h?lhm-{NMI8F~hRmt@G0F&Wxw<io<%7_-epz#Ux=vHry;8Zl{=FoPN
z9m-W#k0%i#x2Pz+XZWTiX49u0_cZ(psK3gOEy^GoPGiY^oPbn}>zC6PYItjys4(my
zkOdFlzg+9G_o@frXU0!ok=OcYN;!ItU@P(6R_>37^^#*%t~GUTtnSZbf>ca)gvfvF
z@*$e}>#WkV%Ws!c#vz8=eA*tM7LC(+O;&ty&R5jUGn4+olbA^#0ZWcQMPOy(TQ!r|
zs<wq%=d-IqtK1_q+aD#Gq^)P~|A@cyT2H%YPo)+QPrpblaHM6W_N*Syz)w8Npudgt
z4gWvPNpH3ZW7S@LbkkGhrVUIjpBf_XHbQ8x0hG|qX#%a>+2%91P@$^~jmCHarl*S=
zHjfhLzfU`L>8P%qYSC3X@3ZFbh7;jlf*ux1Z-ojXVAR+RoK*sh*%l3w_mdXf5o4&%
zw8K|)A}*o0;D>OqGjeDbVRw^c>$FeVjp22+i7S@WvB8Fa$<ts?w4m|UC>S%Uw)GTH
z7tYlMf=CCAYlOt_4&LGgKkla35);!2;y)!+0@U!MWK|M8=>Y~LJs>~!YvY3@E;VIr
ztO_8B<kn1RjQiW+NyTR^AFp)<8~Rz(?QyvIhb&Jzwu*3P80GF2x9lml2(l|;SlPF|
z5^fj;W;XRADNV#Z^UV=I4%6V$emavhtHWYL!&CAZMg918SnFNH-vNOH?i$*M5iBK^
zY-}Zcs@r+|MUMlKn9(Y!llI(TPD!BeERHWzzjviJym???4k$J$dG7zbfuQ4`U#*g5
z5-PSgqi3+;sIjcv4oHl9nTZ8Yx4GUh;{D=Ov<FM*FP^z}NFkHHoea0VoE657-W_s5
zN_EWLYNus?&FmCfLK2+Bl7kCDV@b4b9-;?WH5n#zyVR%*)T^2~qcQA#Ypio2KTwcR
zCufIK3lC2<EO~cbVx1Eve(n6^IRkPLM1VDB+ALG8wkDsv7{Dh6)pxLt!h~EFn!S0K
z<tg4n^6aD?@b4j6GHB8}d{fh#RAA$4hoE@*HXLTJB2Dq0D7_}samhmPP56|4M&VPC
z`FkU-86pVhN_|wKDY(I=xFowKdUEh<flcw1BT)O_Amu2o5d|psI2B<gfAMEfUEe^=
zT6V6jWQj_smc}0v?zs|$u9b__7{{42B2kG}tlcyUIX-)@)}Csq7CC@(hx8M_1HJwa
zcYM7ggPqi<&JJRf7JHfv2`cD$bP;^}$?0`(^;$qXc>G@5BnfI$O(T=lp1Q#M6_@q%
z;A3z5c5~VBYhb|_4-U4htr#T0k@&g1o-Xz+$H_C%(=Yhlq2(?9AY~I1F|)lK&pM|E
zh~=N_cScI<QoY5(1s=n>ym7=Ko_i7KWk9L3JU^|*K%a^1VkKDAR`n#WHa++noK<A%
zAq<4-_U(r~k@3^6)$(9g=i#VRsE>j_cuRE6@L-J)IASkL!Ei@*Jl|%gTyh6v1_l_&
zCa|?ke7qd?@_A+C4I3Kdyz|BJ0nc|178!a9Pc;_viMQdw-|lEaI$X={)fb-K51(Ko
z^0SwQhF2;tMqK=F)Nq$_n;Q^*cG?f*o1Jh-cE|M-@J_i?t}GKSH9AiRj^f3*Ol}>&
zw0)S9=h?SMmn9z8N?u-!FWy5&f#O55QQqGmm<uCJhg|&GK*!bp`=f{5p4zNiNmvRA
z*NP@t2AvDZ$QBFrj|4U#lmG>yhWQoqMo)>7>|~ix=NERJCoGEj;wZ#)h$?n1#+{v(
ziz9x;W*b?jO^_GIQe+#|2eU8m1}CO1^G$SR<$IPl?~9BZydvAnzMH+V+p%I}z2bVV
z@GY%~;u=pqS}O2Q^nRl0iZh=^QMy@4L?gvWp`Qsz;@|6=ZUGtdk6DS(CO(}0m#lMH
zD)G6Yt9xEV56HX!5su#nNSjjpAeu-GRP~v*gwC$|G?nh?Y0sM~P&RG=s2aoBo{@)p
zSEE3$>&qgoVIcqc@Z0rD&<g!I-gEC}%d>gRF-w|`Ob!yDzt)hpKQGX;t%AvearBB`
zp)Of^jqbZCZ<gPT0&=vUCN4IWEBB;+%S~z`AWN2jEEdB|_H%@q17gd*=8cBK@7Y6W
zGaZ%`FEyTBY&CT^0+%G>ob`CNfr`6C2uaXsUN}{jIb*oj6zX#)j()MoG?y!ffHlpE
z!fk&Qt@gmvbB^O^RqW`e^+5$gAy{4%mxs<@m_@ms{L<ZY-EzB4)g=CfSkFDy^#G09
z-Qb_fZcg+x)Co5R*vMgr@n2FJM~=S-3yuu(B3+67&{zy?9s++%7i3)Lb6zlc;#aTh
ztdG``qZ-gpV@fz?vWvVdVh%DLTu^rjvlVr~76iknGF=3W&#bs!hP!;k&Od81-{qE~
z)wgI(o|+_!Y;%Hfj`6*GSSnv>at)e2lYYKnlS+BB#emAS60%a8FWW2WVM^}ZM;V0l
ztnz-2=y<{B4csP&B38^>fMt7CulI}Wv>2OVYI_+-81tJV)d(Tzyas6=Gc}=mQDV})
zu3Pe1&2Hwsk0LaLI^fpwM_XZs2WX|d=-$1}TW9#;eNWby=|^S8qp3+FqvrM8pOqEz
zruwXjQlO`T4u?zQ?N>R!^-5Aw39nIJR%u%uxr2E4{2e6ZjC{79^OW$a!oUxMwY-ry
zEOi##qOg20jkK7pgEE-DMJjgE`Rp2yzV1pnFKZmNi3|h<-a7v+o2qg?#O3j<B{F0H
z(gC2-vF5uI2Xl-Mtq!=$Oko5EGF0<z@BTtd1EA<WH$^}FzSd2#H*!bbGpANr`pH|^
z37o!!D#$Wz<V1iyYV~=P@FZjvkt<&Fr(@UV2ZnBEoEaz)qW~15Qvr_RpPxX>T7rf6
zYy;S(&=}TbPdY(MrEh&-S$O=A?>3~du|odfu;tbO)10g6mQgDpo$e49Ie7G<Dp$@4
z4)*4fc(nvo*D{)VO%I#d=L0WC*_=ug1}QI*wWj<}b@W$62Vj11O9Tw^4-pq;{zUsG
zf7bo`cYx(9f@#mHcYD!d4!yfU&1nsvOfQd$?`f4gGWPW+mwk|;hl%=+4A)u&UMXmZ
z2S=LqG1)zubZAv&O*D_^RLmt!G}Uqnvg?<ujQmR!vOa;#bQCCaiL~do>kWwl=9)by
z#BYubDTp(BpiWrbSqBB{Yv~K;*@0j-&QMBsgA~|lYE}b(C+P`Oxd(i9l?8^0{Iz<^
zIBDU5Xf}f5r!-elK(YUDxV%1APMi-?FmCVikO-Wq{d~Yg@+-QZ=lO~$9pAuk@WYYr
zr^TCtcQ9&;Kkk+Nq^TB3G4O|%j|P%Skh^imI0xG+2X}B_6lLQ4zQT}B_LruT&qKYx
z#<4wTmgDq1*2&HI>P3jynTzM%?f%|rK4s?(=@{Ta6v>KP6a^2|=oII)lcFLD46r~K
zudt?iA7-w}W?Gwz{@IC<TTy3kb5O$yI{Va6KSQ&Zm5nn(bnmIzs#FofyAr#b-PjN2
zOrtI@`WRV5(Qd@aW=8cY4E)CvPo*NwUKiS<Ginuv2Gf$HOGjxZB+@?NcKU%d97eGr
z^A~8TTZ!}VhV_+oxQP=%x=^ZbE^8>kiCjK=QNCBpvY%w^U|X(@bObjwb?ww7G)sjU
zud|}^<#X~cS3ZMyrV5}r#1Eeyt*Jk(cn)VHBUN9z?!+RnRPs2SXF9sU3Sd6lV9*>n
zhONs$?gO@2vJwTL(0;3CZ4lsPuG=mF-zBbOBDjm%&d^DruL5gS4VDjQcKz-H))c+|
zF(%{h0pvCJSr2`V&R^e6Yj(}Nrj6Yu%pe-5xmSx+5tY>A%8RnJs*fvX`i)7Op29)~
z*R)qrqL()wCWcq+H$@2_Zg%51C@tNye;3hilJ9AOSap%?;*AMPEJHjd9$#csVTJI*
zg-?4m4`BQNcjH$?r_;{%6hITa;r8?lyB~R@PhemTEU1xIFJlvObNgS_7mq4Sy_5XM
zSadPZ--2(t)yYT7Xs*C0IwvhY&<3I4Q`UJgjtYeUczvy0I6mkdWc8w_Ut?G4gQ+(H
z+6NjM2t`(H1n<v+S*Cy?NoyWm{v;!j3v~MfF6!Pts_iPn-+FuZ<Z<N%#%Og+KY`;~
zvB<&o&Dvhypl4QUeX!wD%(>>R^5wfpm5Q`aD|_e%nhh8TS5$pl#I#XZaK~WPRC|?)
zF~gGd!@h~NwgYr!v3T0Jf9W3jJ8B8TyWY)Lh|y4<y6P^+FDRuknGCFDA09Y&2_;<!
zQN<6H#uNJb+JK)lw90ilPH@AhhaeVw>F?7J6Y87u+;DRAdH!;nW)u5&d?xqpe>`wR
z@-)0sQHNGvFj!t=W09#6Jh3E~7*F_{bqD+5UC6C^I|^xB;y@j|VY|AdK81R{5{n9_
z%NSAScQ62a;|AoJKy5mvVeEKlp(Nf-gyt@8?`yML1YA<rG9UrG_fa`-gI3-B5943I
z$dzf487EBNc`I1s1(r70EsLk)dKlSDnj4l6-ZHRs69>(2j~iP>zK`3RKIzpn9(}ax
zzvZtaJj9HQ_cfmvk)t=bv}__w1ZFNX;R1}lqQTs4?R=yU8S^z-js4y3#)HJI0LKQo
z3lt5sbF*e3yW~~4=Vn>}3Wxio!_YQZ{+hBP7vfP(+jTj<;NRKJ(@uIW=N{F{<`_aV
z-%bVWQ=!QvQM6X%2=d}3zMs;JcX)$O?k$Hd2aW7q3dTyDv{3=R>esM57XaOXjq*)A
z5}42Ng=PRMtE%A&%%qjenY)k(J-&Z*^y}xFzcvOmqEB#Tla7foH1)lO4kS)Xfede?
zz5r{cW&9BNZ`P{LmGC9$RGnAL_{?c$a!)t4qF(;nkqKMM7}eFDk2sC*(Ixt{x)Zjw
zx{IGMp-sNM-z&4;NL#GP?~n;|*6{9aa+ZJPriEk`l&P9baHx{{ixq8H{839_68<2x
zZg*T*9szZfM2NOD5SO86UBB&VtDBA5mVj(7Ye{w+e@p6m3vQ4=A@9exMCH$|*uUn>
zP6hC$3VBE*kNGU|Bd%`jkxzIBzgFEoueZ}Z5p|7=D)?4Y*9r_bl9k{c=F-Rf_|bbO
zkE9$0uhu`<y;+?mVBT6NcfH=-cxk-#BaFXZLnRvj35RoV#a{!8<sfIL1%r7sNJt1^
zwcYa?e9#ev@4&c3u#XT67rmKe-YS^_n<Qh>qWf$X&^M0;T<rkW1p9nwx?IdG8-O#*
zJccDVK~mcBak;qkG4Mz}`9TCsJNGM{%O&9qyLx~i`je1dMZIKO(AwL<9JmOO|Jq<G
z99EFinQES)Md}bH2;m*9*L(@4!zF{D<i4u6L+m{Gc>z@Yf1i=$CZ9)D;&D+2Nlw=x
zD69@8TYfCBpi!@0UpJuoCzw**J|@a&Xhmrr-Yy=eIgH$|eko7fZY>BSqrWB_Up~mk
z_u2X0_`SElk;E8>oYF&F-e4zX#gNZy#qIjl^rbjzbV4AXowQulII<T%Mr^Wur+Gpq
z(-IDfo%lv|gAgqyq7z8yE3En6Jj1!Di+Q~b?3OLg3~KF*F!}uA!VllrTsMS$epzj1
zEdWAsKaypfg#Q^$9-&yv_3MD7<T}YHn%waQ#19Af)VtgxoaA?<k~ljfXSx@Z<UO}3
zAkyx{`rUf%Zj5|5BEfxL(Gui4WWr|f@(gp%8^G)N<JOGh*5q@t=boydH(Tp3((&1<
zU(`8jP5%b!rhp_c<7CX=*EzewCxI*i%{AcQ$t?zy5b8BMF2<6hR`Q-!`!a@*rau3o
zB~C}JPlFXAHL8$#f43{-k1z<fr~quyrsBsfz$Wlw_}-QSj<-sc9JLcOtw7>e=-`Lo
z2l^dPfeEuU@K}$w)VB<a2BO@6ce^}q?Sa)(B5AxcqNJx>O2|6n_hF4LOq&m(3EbZu
z0cO-+Q3I;k`G6GpF-TO8M`T<Gq!v)%VO=QU$pcN+iN?8T&ItYdi)ie@7JG}g-i*CY
zmc4xU)V@(i9KzK{WsC~$`ENO=9UShGtf2w#ny_@AD^OjZN$_vg?NsY*w9AzPE5ri#
zP{uG{yj0XyO$A!5(;>W@qvF&HMCEHzs}H-_W6SNm^M(m2?n9K!nNs)gqcLX1(kGh+
zh`Bp6Gqr4S!IW@U?r%ZYeq|;G6;L2T_TTHVA%ufC7w5iZ)$-88hs{8JNG*i{%0K9&
zsfpcBS?D+jRM&c`UHQS|YLcrH0f^eZ%c!4W;8_1(;5anyVpGJ82mD<K)_dB@OgW%?
zsm2g}7@q)DfuR%b6fQxrkd}ZH8-taPn(qCm-+`?20WbTTUKgAjbaE6}J+QuVKHD8G
z01WrF8AfNy`*(lN7*VY?;R+MzMl=h}Sc|vDc%59ng|pCqP(gS#aj5Vpce*1n_BLpt
zn~lB!&%QSH7_i>7Uz1tcHTw5O2M;}y(LJZFXWaTMH9tasI}E{B9|{$TcRA`C=rUjV
z&nSWa%s(<Sm0?zm=;C+1MxiY46E?-SPqy?uFs$*gHeF9OYG8#8=W{$!8m+e8Qh{yQ
zNI4F_zP}MSl21qc=%BOut2DnR+usR&QFjpGqqIXWuCTl1G%uFlzSV7*+l1uv-tVlf
z$fUSCCKe=dVrz;wR=!6IMVOv&4y%K{ho1XJdNJ^gLrj;qUZWG&`CDCj1wTdw9boxi
z9!VGsd^0C4wnRRCcUZ~fOa$vzQhzC=QJ9(RqdOWA%;o0;#6=oKgSw{#g6}mG5`7%`
zWV#8wrwEi|cOL@m{9OomMD8ufys(e~MBdf;iiq?iXO}H*Lx-62Olsm3kWwp}isD_r
z1)JR-Ge@PqX3FL_jhHr0)(OExJJNS4-akAs?Iz5cZh1@yq1s3TTl9p>IR-vplQ~JV
z`rnIa-d0{n5_*D{S&fhXtr5rtK0lE+QnbsQUe`8EE5nN00dc9dn~xm^ekoQ(YlK^y
zBKeQX-AQ3Y&04SBIH47N$#_YgH)c|dDDbHA{vtxtuI3dPEGXEDzVWZ8hLcwx@UWZo
z2gguHrAQ=QSf5OzzA*>B$DbF@OG-DEQdqg*y7EGotMLi*(LWiA{lO%F2+M-`uYnoT
z3*l=>dWQ`{&_~V|OQ_CmOMPl0Vw(dSSO|wZr;H3ua9N7{!CuQPcKmOxLv(!izKIsf
z;qK=$mP2urlU0<{M(dH_ho|IUoQ&&MSChKfct^yVyammfIn<}>sxezdD_=4wqu4Te
zkU#8OooBCM2qk1-V9puYnoguX02TN_*2Cej5Czx-NK>2(H#Hs1jO@@mfRU@_yxbRP
zeQcjNTW00FoQ-?KPoaFb-$5xh83-i=4`06SqEd2#$Xd#%5J$h2@W|_B<u1ZZ{A0?E
z#hsQpy7-H%*v3Cmo|!!oosfI{Mj&Gl+(U6YX|ly0|DdMuiUcKdk<}8E8#E%6>-8_@
z3A}NwrR_hnUL-_3p1*P;b!<J(hwK77%@ADKYRC$P1ORk^0eBAy3`sFKg)gALBQH4~
z7S#+!ROtf${!fjN`P63T0%mSVQPVw_gL$|)rD_p`kW7*uO(s)!QV-Q`INbLDg3ZG{
zV&e+SyLY5@%@B+!d|{Hin01~g34M=*iSF%>u^f<8#<+<<U`0aLudbWpI|rv8QS-w3
zOQx-D8B-3yaOP1r30okLnAhPYgFoP$=4%bZY!%$B;bg_bDYS@ZJMX<+uuGzb5|KZz
zCa2fW2tL6sagS{pWLwS>{_&2A#c0F*4do3mURYmAPm$>HXnK^1hGbbuZfn~L`oENM
zh4!AkCnBO+g3RrC7MpGMkA6J&7IU7Gtc@cu`f^_W%6%UwELS3Se9cN(5umDGRT+3W
zoe;oXmU|(<$*bR25e<zBxoX%zI0AO6^DcD``{Rq8BknCd#wvI&{Ru(bp^JbF7zA)n
zQ8DjDoU7Q~k*69v>}&~f(SKD=p<kmJrZghe_zjh7l?(;7CTYT$Ul+<We?A5bU^^F7
zr6K;`S`8zBQ^&+*O}qrG!Y+UPIJRczoGe=As3ETgnWY|bjTkDgNu#iZ@C(-Z-T3h&
zIP$8U2Ys}J_Qppb`f#^;y9yDxKno6mgYCkK*+r6-NCY3)Z+Z7bKX<QE{P<8Jcww!W
zR3N9h*TfUFa+<x{i;-K*YX^2}hMSax*u%0JH$*?fFe>rq22KYONg^6<cZk&Sd12n~
z>0-Qs5Q^tQoQhDPKjD&jh-U}1uYte*0g7OWsg)zjweWEWTsV=muNgWc8rj;)udpd#
zn>+N61IJ)twBxc@4}M0*1tw=y-=wef6X>!VUo+8r4MqXSp=1>VSWEBXj!!G&TMoD$
zaBj&L95|b#i<!FhW=VJ%fIN#R8R?oJ<D1&ECPrIx=W^*SsMoGDpw$-Kg||=Mdm_zV
z?$B+IaV<n%6au;xNe@P71>K{)oR+)F59orgZ%E$l**XpCH8LuGC#d=JEVNOL!26U6
z)D{`^WiK0n-3-CObcAArhHs~vLd*gWWWHcXl*~oT-8}VCnkAtkFrNBtnskc_B>g@b
zG5Q7$L4bj<+0)nUSg?Q#GcfAe!Nnh6>b*j%5u2D-uSA0*I&hMD?>y0V2@7TdE}u!E
zp2<H+CEz2oiu!D<rT?K!=D~(c%C(igC4C&-A`1o4Y6B>>u=L5kTjpJ<YX5!yZ4=LI
z-1m8Km(A=iV}7pzqitFk%#uk4nj?$cN1|447p3a`JIO>k92j!Ew1I<xKotQh>7h_1
zKCm*&63%x(r@tpObC<8OPz$tg#eU|aj0}E_7g|%O8mwJuX(9LFj<U+n?`m%)--R4L
ze&D_VqYs(wk>O+MV-ow1z5^!_b2fmm$&g<b`Rhxny$tDW?B=8fs~?i$NPawd{{wEk
zeu)hguo<wlLe#Ofj)fmLlVG>yIzvJPBCs+a;pI(N7cz;u*Y-?bne81+0;&$`oFsv7
z@hpC{e)du}DM|dK{i-qR-8~>d!rjPi77~06vwQIVI$jz>hR7WC*8f~tY2ZF??iAYw
zV737c$zND)qGgHY`<Lf$(Edn%C}ZVsk?!@VOG!m^M6kK=lL|T!fbUQ<hn9OLe#iUc
zd$buKpJ;I0O{IT_gLa+y0d`y{0d)E017>N=VZQt=M`9qJ`cJEbPamxhWvY`XP4c#y
zH{RJdPE!#|va@1*px;&}?Lv@CX13Z_A&<I4RdXH#qN0IM;qQARb^*#QQlI{1&$|6?
zl}c;#_-CHn^fABX#@UkUT08)l6nk$q;i<GtCYIZmGou$M;ckk^gRfLJ=!KZQl&@@O
z5dUZcGhuPI#r~{rE%pYf$mz_VmnsCP%2ea09k5{68z|{iEwNn0{OqqKDV$)1_Q<j@
z9Ab@f2cPdf%xZ$priI@zQ3FPRk@D;mmDdmEgIR?|93C8`pr1FJJ%u44L03b19vK8!
z=E@(YWE*IjILfCBWSx9`3ooBtV%qnL)H}&Wk#6J$efl!etKWX9Z1s@lxq)hp4Q*F!
zb@=~U-sHUB^PEF8ZAGP_nL0NjUe9<eQxJ{+9en4~Foqjpv>5}kYBJh(`i2d1*l<FB
zpdbGX*1%e2f7OG(VCg1^eRQCYr9t#YgY7hAU3}aCEb4-b&nd0Ia}@b@x4f@r-b+<L
z4*O-8%YXurJ$b~^$h1*8S9H~w;9%_(u*l@n8^;j3%tE>Jfv8xYv}31}&EGJX4DbV}
zt$1&F;SUi8V<^Zz#tCtSe!y?u*Z?i`Rc-IqxW~X#DDDE?8aMNE{yPrhTb`F`qW6?q
zXC5+D;=%L;r^P*P<Kc2aAVdW0MZ*YP&_xYGtwy-H3r*fVlC!dMjJS$y$x2-s5X#m6
zu1z{tQfLQ=iO0q%h@18zBp}HFIPmccTIaFcFxNL&Z^E$m<k%fB%*PyjVyL1PH|?U6
zU3+TYfY|rH(9_daX(9Yl&O5JSN)4K_h4X*uU}x9ZCAOVf7#-p=fLPNFZ16|D(iwUP
zG<f`$MVKvuBYBQs!6sm7=Lkou-t8!qth^no>6FtnKmJylW`h;5GMb2QvCd70a>d58
zr3%wNL#3)CpQ0s>wvsZqs`)YBS#Qk-q)f&K?^c~4=Cj-)@+)t5N2<uc<C9Y*u~BKf
zG#K2#lvf(N;s{QEElOjJ^_t1dosr11D#QfFD4`z$Ul(R!6V0&_YNf*>NgTb_{aOQ`
zjP!RV6qhp+({&8PiuE&%9djXYlG<MY-#dg|tYxN(%<L#90b)Ma3wBP_q1UdfR|y1<
z0%}sn*~){OV_KoB&_6hgNWk_EDYs1!tc*EHZm6$cqt6Z;*3c~91>3;i8#1^1K$wn<
ziw3qXe~SC#2tJw!pekR}Fc<_dA`GNVVkp|%>cdQ26^6F%B9iSkn^d!ieX>a)seR;M
zOp^Q^4?G`K2TBE$Uf^JHP?QwQ%FIUS=Sor)9cK_xn<>>J)o54jTh?o%nt9O`w5kNQ
zSZLwzQXUBY@dvx^^SAN_%kvDPF3gi$X~~#?%mBd?ys|FN{T4ii7LUeoF?j?}@#;SN
zdUqZ%xHj(V_^Dw2yOWC&qNSc0%>=kz8i#w$LjaRu3oA!u)`r7UwqC=iANsp{P>0ij
z|L*xs%=R_eUh$6}iO|J}xA4j*dz++Y_Yb?H^Z>p5=TrXXfc%alzthJUD#aA}==<Ak
za6J)rKH&J;Ofs_k;{*gCN+O$16@=EKR>25)Sc<}n=WtDY5PP{<fuFDQ`SWjJ2L*Mq
zDe-=tCisy0$?Pgpnz4JLvp|#AIuL$A1-#ZIVqA34GrXCyX<Icsvq#Yezdm$W_)TLg
zWnetRAQp@_Qb=b~<W-^+JW_g*$l7lSGykCcSgzQw8o@bp1gJ!BF;f?soEgBNqL$VY
z7psf%5=6HEXzdx((pfc@b~FOrt6M(8Vakp%i0l9nKM>OK#k)}l$XVO#?S0!LDE+rr
z9$b-z`@nP+geT}UEhe@C3)v0zgqjN2EW+bUNnGqkt?11p%_Ny^qT-*H7h1<9zUTIA
zICPY;_pY#>xnQg%X4kG!fIt2|UHcM?T^Ssff5a_Gm-O82-Xbe3?=*TTx+lINB#x2)
zvzVg_uhY2@n+mo$^!SejZ4VyUX*18hpg8>pS>0htb$U=Nb0|yhm8HylH~Q0fd=~+l
zHLQ=nO4qR?pe3;A2$iy<8d~0GiYc`Hl+mpV?-Bm<G0Z#%KG&5`j+8hbgy?-0v)KfK
zy=Vue6sDmjGS7oNTB5IogjxFA)uYz*)?@@yhrUZOHq$|J$`t?!)NSF4gqdLv6h9<&
zOC)}CRoxk`?m^pw(!eDTkZ>u9V|KW|*|=5>y2NXK_H_8D|7`F>209O1L{kms6Df*T
z-v1*v_Uo=1Wx7=d{%te<!;JcN>&{Z)?Jmu)bH7)r-YI<Yqq}$Im^j`gK<)lM%Fijc
zKL2drw*LF);bAimlG$ZJYC2*Zy{`eE9XE)dwS?b9K2yW-A4klMl?hTJK35!dUcew^
zD}5JFsSwYu2nFkR2>0gv2NWau*y*0B9M?ArdK4+&E6Fxv*cHq_SUM!Yw`*|+sUfNv
z3%vKjT7SKOkKsRGQe&Zc(;m=VajktRTo6eVPCPxm2`3mo%?kW$5H5VdvNhbh*(^5m
zUppl)J6PSltxB*UEsZXZfuJ3<mEmys2?aM>Q7zRO%_DRjXf<)bR2TwzE1(v6*o=|;
zrXJW=0H8&7`8sAym~ZR@(ie~9c-5rw*x}XRZV%@Pzi^a&IDd0co&6m6V12w}@gk{8
z!o$Itmvkzg4n;+O$Js3hk#IDTr$%7X^8v}lS`Z|4O-S=uF)}_lr8JK9hnNXraq4Tf
zL~*Sh62z9QJI+nx^~=y`GJkm6Gb#Gxe_*Yb!>e4k3v?DqXoIh^;JdVi;RVtZpn#n&
ze^LJ<eFJv85&60^00RFI>d-DV7A)(;#cDU;RMaBu%x*=7I?<ykd(r_S%=7eBL1=XB
zLcPU>hgm2v?;0cr#m_9~k?mJlHR}3y{hlgFQS~9O^zw-j${%>JX41JFcFEA55ED9l
zK_hMzi;lBpR=A3p2j#w7OP7^?uU>}f)liVxOCi{?RlNbi$*^=i$Wi0N2;!A2c!2PN
z*ON<3!GsN)&?J5?ba6D(=fxrvYa{RX4FqPBgp|I1eShP?36PyWN1>pg2;h-ZoW2}N
zN_ia#v0nV0zMuh1AyqDaiTmrhcQO_A5l{q$O{^SoZh9jSlW7{g3%S$i9%D2$N`N+k
zf~bUdZ3m;qQaP*>q@~xJ1BMGfn1=*(lsXUhyKDr`?;OUYraPqLr~WF2&ZfUt-=7BB
z>KobacR<?r3G^~q4c_w~CdOf{s}sV9a!n`wCglA_zGBvz19WJQWtdSq4bl)La75;t
z#jxI*2@rerVdfB4(qwSgb3PR=GeAhE)iT1ycc37k4$o8@J?csvy**wW%sI0Ltfl$(
zhDNqk_JE6I1wAEnU-at_$-uXuZ7<jw$?Kt7>CbJhtxeYN1j#o<IAT?p7?`KKwd%1w
z+TA!OyVd=$HS@-0`nrjP$sNtcraO=a2L-N3qV93)7VR<$!Vsim#euSUG-bPCIuLk8
zW=Ac-q2l+aGp|^gfn}xi8Xk27iw@>7*iLPE8iKhG$gmW|KLb7znST6;w(jQ}Y*>x@
z23aFx<m+Mb2R6N~PcM|@`Xjw$(wki5Ij3rGDNVA*tw#$>_n+2%E7ALA>YO!`FEa(5
zSdQ>uy~>y`dLuLz+&vxd-^7||ilZ^t$%6+Yi~tFA*5kh`Ik#t)Lf;$#)(nO~Bl3Up
z2^5LEm-NL}Gl7JZDfz}jhL0H3Wq#nHK&7Ls!IS)xe!=BBKccen7JonB@c^&~Iz7#b
zX-QXkjt1oF#;er;dlG`-xP6Szz&DJ?@FaSQ|K(sNEaJffp@3FSA0^Z*Y@?~z8&~wU
zPg^3$XQ3zYyyCZi4Puri(ZUWRd{{?yD7lCY#mV#dXx^X|ZUl{3yAA!-cnU%0eN4gq
zS{q@^Uo({VO-ByCi8hThh&gY}o&{p3CBYuk2lpzv>$=}G#AhWCkC}d8fSg$A8f-^*
z)**aj&uIGM%JekJ11^vS2c<0W`>pd6Od9Ye0frLjnMC_Dp2cQh1~~b5oEf4$C@VjD
zKyRcIZO?2K{*)k?U|YN<dfnHu)D6lZbc#P+?m7tnG)^j4S%y<0*Nas`zIN{_e?dw3
zsg-tjgJIv=_r=_JL9e@Htfc;sl>!$wVe>qI=u{f}EiR<u9c}cKDX*%{8x*%*eFuzu
zuj3o#@*hfT5HQptfBE^zHasy?Hx5Z$YXLCmzzo1#iuuOp34H!fJuFc~xiZW=JXVJ@
z5kyX@8-TrFE<u7e!UOtL-sp7yeD?Q%BbK{Yy$SjyAf26d*Wq_6UcYp$8~`LJUk)vf
zF&<{_<`=$9N|+029AGZQ88gga+Sc}#9G4pRC*-`PJMQGfO(2sWM%qc;%J=7Z3c!`v
z^o_@MZX!hX9T7YyCgu$G>k&Ld=h0T|Gl7DkQhMB;BKH}IM#yYks2am_pKo709uS*&
z-!HsfX@@FF{^c*(3IP1DdPdTjTf0*r0oE83k<!a8*fOaN@`l_;4KDrK)HjW-S&GZx
z*tp+{;C59TbYc*4ao6YCsqHmu#9pH~OL}&+a8%5pF9|Z(FvAfEof;RuUM%OmWmZ%2
zhlKVm#PkP;w}tJ-E$gmIPrJ6Erht#OJ<*!O_}+AU)-;%oK>``hR&?j7?i+GX3sjyb
zSaVRvN3&bgxe^SiwYMP&tfrYMiEyol6s<6yYi~e83CHEB^QZ*>E0#BM+A)>-5zJH@
zt-QWh_M_ipZ1TGMRhGSULqflT>Q`Z|(!dFEl%l%n9%NXY<J%k{XAzol$3;XnwdwWJ
z%={tSz!A6Lln%2g$gCXio3X)I|Awx{-ThTkRM~047sYdK%~5hn2_M&T<u5BHGnQLr
zW&D6T5TK<rbzd;{<q6L}JO9)~SY29XQ2+}Ly~RX&J#LsL&2kofg;W$dSpuR-yL4Og
zYKeE`T>4=b{-sr1?_I$P3&a%$)PK*>0Jt$UOq4SlvocA=q;$i{{7XibUa|gdbyv@*
zD<#0Rnt@djC6`>cbdjl@+FkMMwT*Rl)nCaZaH;ApJYrgOQj9dnwzj%~t%|jjy;D}3
zaonQV;eK!EFDq&=5rH+4u|d%)0fK^G(VDue5-%t~Ih2QPmJU<TmY;d!47?v}EyT@r
z@o#8=^A*M9Q%SzBTvRNRzN8CIR+s_<2A+TrJG>A%m|}(V_~U0X9G%neLGpQ-fM5XP
z;aFJ<315H-;cZ<1^g4?Pq`;p;2lMt=AQpm*etEP>swb&hUu*(c-{&Vh!l1jbdDb&i
z#e%Cw!~TGG_~hdBAf=HfJV7{bM=4Q&CpMT4u%bMM#>bdcgurN552JV775}ihdK(=%
z%#IhfdO<!NKACKDEgSxA$Iu`Q`Nc>+!)KAktFe^EP>s>gMi-NUnJjLHqp+j%uW%-)
zDbo~Na~0%(__NIT!0D-1K#c3ubneZ0e1k|3x^eVn9;l2GdM5yH#PLRJvCcsa6nJkG
z)~b)YD6p;bO+REQ<#%6b>D1jH@Z>NjT`coF4papPl~2|*SOV3uIS1<Xz6{L4r6sg4
zo9UmNI-~Xaj5+8c5DmO22c&N!%4r<24p~WNmPBI&C0p|4=>4S&OK(1u^;lgO<~0$5
z!pu;YuRKFdg+IBlfDgZ+uQN_k`$kHXFSGK`?y`S<S$9A9Q=l$XRBZUY?zwv1^w9aN
zH)>>?4KHw$tcv!!SeQ8eKF%ND=ft@<nd1kkR#=7(S>R=Q8umFFv6w_a6yA}i2A&V%
z%Ua7FkJe!FVOaUgR*pfy=Uhp4f0Gn7dh<TqRwC0o=g6~KChZ!bus!8J@=ZYh_m{fO
zek6f(IP~fVWd4B&1MOGu!r<&(>5>>7M*(&=<1geu>FOtZvGhh<p?+XyNVmSFHfJy}
z<^20|usp4zqb2Jvv-xs7ryieO2N-N_PKF{7)_*0SP4k%C<OedEmtHUV;XDey*}Gz(
zu!Gp+m9=*HM;kkb*Z}+oi7mHD61N`GkpXj&d4qES13jVK&vm?9;_3&*Xu!2Pnac%<
z>d=mVsT8K8Lu=>8WP4WfD`BG9id0I|pjfy2p_#gZy?cPUN{<ye1imQDq<I6_$|c^?
z?j9!9JnYHq&d5>9Dy=2*Wl*u%4{~Q51B1T`Fg`23Y!bZun7V(l<%@fz_Ttr-VMabp
zGxs<@kt%mydrBxkrAo+fq=xP0;;!U@#0_}%s~IgxxYs5%aTv7XFdNTEWX{~2ilg3R
zKcFPABojV?(f|_*cS<@($w-^<<GDTQv3v&`rVRb>E%TRof=gK&cAz0LRJYX=VTCY)
z5hNa^=$gG6$9W8F=i^BGGRzZOqbxChy)rrkHl2wJ+@^cTQ4)!+sB#nEKJF^w0oU4$
zAS*e=suOx-a54PRIru_XI)RDiKzHDz0;PyU++TGGW9V9a+Vb)LNKwX&BeqH~OPX1=
z)<yPd0fE;<IS{6eTv5EMzN^Qqwg)<PGH6LWy?Gnkog^uiK1|k)9AVE|iGw8?$Hs>r
z4HIk^<e@bv$cwAPvcBc4)<x3{mI-iy7UxM`V%9Sq6HDRqc?iQV3J@=GCz|SmL*_*%
z(2b&FWM_%D@N(gw<|q0VkSk{;^O%rN)OEW=BSF&HJT3u6y=~UWZhCN-4pe0mdMKD&
zGR4L>HON{jhC6U?=44hcK=vS~uwi~3?5b*8vBpr9<B3-4?K1&=9gvs|A08I^rZ|&p
zlkfam)@i?sdk4O%Iu8ZrX~j^}$99m~GBDojcXu|NsI85`6gfTaPu|oTi{4X)%_)1G
zvkazt#JHq<|9vR?qKh+oOTQSMe6&ArM#xjcl-TPi&s{^cT)Kzpi8Ket+5mNEv6cF2
zrLs6%?{qHljY9&v(XOQ~g^!#HBAHQj_(ABIw_l(2eur#3PnH)jybi^=fA`qZ6u6$g
zk)j#dRFiG_7>H&6j=#;ALKp6#KiE)F88SAKr-os6E#S)@9s*)rUwU)Sd!DFF=R06f
z6Ii#L?dm<4%BeawCi+5%BIpU&QgLrK{2j1^OVi$VgPeu+*J;-zt;b4yYSI|+W)30R
zpX3*xO$`@EJ(ipItv4=K&HEZK#Ls=!FJ55UY+PC3<$`ZHc&esT!8`BRT31tIv0y%f
z+i|x>=-`4LY;XE6ctv_55-vQ2x&coB1{26qT)zoR=;-m{;>u6tx7j5)Q+3K&SeId^
z3IydCK#SouK3_guj*SJNNp?KU;vk1YlP8_Q<WJQ-YgnfS%_L_;YfFLV$Tk6DDIaTc
z)Y$J?7~76byqV(^5CW8UrYcYi`z;fapjskgH#}g_uMt|@O+m-N7z);3aXj#wHRrmv
zKcKV4nZJi$C!xBn^_$yyK9K(=Us(2QCdPvf2t5BrSymj1<MtMGKlHyj&}u&v$^Ncq
zC4u6Z!Smp1a>5nTzUp>eP5pRi*BNNB812oAx43KLi?hJUgx5J`1;hy67sKcBN};R{
z;-&nv?ms7ITO^{tSeQed1_pFrP%@fZ4xz6^jMY42qa@5WiDLd1Q-ZDxA+(UjC5fyl
zk7zT_%lK6hw}<ihtpFpWL*xR|@yl7HtMs<Bz;o>(uvMvlJ5J1<0Up!ZQnIk)Tq0z;
z0$6e!Hl^`+*7O}$kIXyZa=_tuw(Uqf%J80)HWJW-Q19VdSJ%(S&UJeG2M0wGwp|A>
z=1UWHm`Ic)0zT`_s)2Th*UCU}DPB>gaMXB*G7^e1*4Tsrm{KWJ@rzB7IV!gLe0ZbA
zAIEwqs9KZb#^XsbUMA~p$5bVahE3F^S%vcXiKgriRXku*24e~hmz>Q<Qd!)bXEX|C
zETN>2_BG2tFCISlx2GFS4#>)sQ_TLpZjgE{kd?;LPx(UvHTDsQiEmfi@}8Ecs@ggs
z0t|Cw!1_#0-BXniDaq$?5d0Rce{4cA^=kD$Y(71t$;}=;+#|ND<-iK_P2V`rW}qEE
zeDM&_-5;h&WV-!fIXV|Y_6sd8sYpYi8hW4!e3{3$`l7ShTJcy#yUiH&4MuXNezEc=
zm#)Vy%6>soc=Ly19S1T1!pM{DTaHZ|xop+^s*TvLquv!n`l-eVgLJSNFOP(rEr}<K
zj51WndIfU6eAz^)waQ-#I(Pa4W&<Hj<ZU5EC)IeH;=+U1p<)L1+zJQt7vnui+eEiv
zQwiP<T?J%zmzhoqYe%KueJDFN-Pd*Db=A(w^g>Lo)&x<eNNGHpdw@O^)zGkWnwv_(
z77<01kV*8d7qPwGQ&1wJ=PGS1z^KUJwHf@_i+lx7@Fk<ahB=4LCA7x1pZ?pX2p9}=
z=n=Si*b9KlcOzcKtE8hq2Id3pS&q&s<yZG13%lohdK^e^u1Z`f@i{NNtRTW1jNP2A
zP^;0{I=Hi}(%Dj>cXx&j@Mm`&t1$&@?-!;Ugg;w8V#_UWc<Y)3)zci}0@--G%l@x5
zdWCKA8@SK4(R4^Q;x-TS81$$o_j6I|W9d6B6U9zodwfXNFq-tCV99tMx)7!~$*_9C
zp<>9@5WVB(bb`6x^AocmIr~v3jh>nC{NTGAca_aM$t}E@F3%yY%3+oUQf^0n0@zHZ
zl{}xMClANrKddJ2ms#P*jVI5&vGP0v9vONOF-S*b*{RaBR;R*oYq~k~fs*_;ldmqY
zSuEsaa>QRY=$`kbk+pZHnKZunV-o@_(Vgjwuo+m{nQAWWj3>+K+;;l77OJAeK>TJU
zflV5BQB8_yGI1{&%%1prK<9Oxua(CSu-w~Q+^6_gnPeO4m=qF0fndYuzz%Y@r{P+t
zK>9&8QC5qkgGn-skxxsiB}$lkEhH<0xYb!cUA2Di<J#uVDs?2nsr&vTYsKK#)-@Be
zp-UIz4yM>5eHE#9Cvr+u)_sbm6`M_=I%JsH1$yr?`-3^-4~ID!GOFD*h`>HFrhr{L
z!x>hE-U_v!edSO$G}|gGi;eJ$<(=uhQ_ecxhcNPBVe?^VET2btlR|y+K5!6upsj7a
z6q_uN*6+9627(!-{(rKu;AbgB1yq#$XVmMx?fS49pNtH|CbW;w<!sHIHru({zcYNm
zkVkMn9cBMD+ON)7%x}2()=MZ+Tk@piZ(}pSAJ*d6<E+5Ww*PG34a|HbA95kDu6jPm
zm2YPJ&g3{)Kj*d!oYc7i{E-3ZeLxm1;McoZ6g<X33(O9rv<SKZ3=K6T2TC{L&Oyue
z-hwczZ+u>eA8gJ*4k~D-ew-H8Smj1p5Aog0hP+UmBQ~wq=TL;cNG=WostYVd3@onh
z+FSwIa9<H=8|(Ma=U@{)^-E@P<f-p@T!zLf3SDt$#j*4-st}Cgfelm<yB(e6O0HHc
zNh2O0B_5iDc6t#1U^$nuLJDu8CydDpi7VJE;&p<q<Oo&$wpNbL#=>-ieE~TW$-m)r
zBhd}RDwtp@+oPZgobF;RQCIrQ>M<Z>K|WiY`Bu{CaI{i)@>(*6HAo9D*{Cc`jwgN^
z*BCRxMOLl`qLgGYlrcuDTX3_aPC@^`2CcWZAUE7(^ijv9+laF$l=(D93C5~`kt3kG
zMVS;H{ucM0{~6MA8}fU+qMV@0)+N4B$6gY&^afXCJs^=aUdg)h=5;iz)SANLDziHh
zT0Sx>Qvui%ktGv{BD#J2wwoQPjS6E5qXe6p0;C>}mbXppaQ@dr>QpBTO~9gNAge>M
zO5$@TRF@p=^{~MH)pUq79%3-zBbbf|rBk+-7?(@1LaOTX(Sl)kEw^&EZ2>uDr1g+`
zbf#BkWj~u-yGqI0@BxEXn2H(Z!=uFU)*@J6d?&W}P1GyuxjpTAFyruutkikIf?Meu
zoIeyUH}_#M0MFF|F9%caMhVsM`3FCS`89`J3Nz)3{wTH9tGN;>o=dOveA*T+XrG9r
z|CoZUWq{(CwvreU?*pVKDpogw`6*mK{(mlH6)Ph!aGqZ~K7na2jf<G+G-)SqEG5Ev
zh{Q}x$5j$u*Y=YHkp9D2Abj>6lD_e&xAPa@i!BgJ?fcdu4Wl3r->VzJ3w2RehJKv}
zftwV&>IidQAj&hqk*a@#nFQ8H*Eu|_RQf-_Q<|YL%_JdBL>ttZMQ>7^z{4TsEFywb
z>al-T5g=rNJ{|S3z~G&J<?|kEi5u>(t}kxW=c7Ii4y7o~*4f!%s%5AD)>%Y+Ei0JD
zQsrO|WtmIXZe0R$*}r@7zen*l?lzAdH@JYEM;AC8C>&DVJ;lKEz6KXQ@G8L!R301a
zghR*2o6o#Ha`=8@<3mM%g<2_CUngw#9Sn7f-2W7K!^ywfP{*hnB%*G*`%$_~>wLDW
znxO5N!FvFL0y#6q(bSGFl75B;Bhf%k;4cU_8|PuPeCukyqW|)TqFvv8!|DVuB^ZBr
zLiKt~Ev^yfhY?mcotHSl*>qB*i4^Qk3pMVdNjkI1C6mb<Ywa!_qJIh!w8r&pEP|s6
z{$qD=1a-dQ5c<MdRJ{q<y$na-2UO}C_GC9mF@-9PIC*3^{>qXcL1xBy>RkA;$|mNH
zf3CafR;ya2gEj68Zsf}2`g?*&``vJRV7^V?E!cgqhlSkRYV~xpfBy>?jkNePNwJ}T
zs_d6P>UNBL)vaOksh3h%W9yZR_ZC9iD3|llKs4l|yPAlaEw27g&B%>r;J5v|Z>Zxs
z|MBBCc<$;cj2;4`Wz@B97e0iw4aV%UqU-)Pa%NHtyodK?J&PX>DR}4-O>wCH#}DWB
zAYSLT=VK9mv)iRE<ae|b2&y1_HClBf#$LD{?9PAOcK??L|CaeXz3i4pX)ruh79W^k
zio4a^GGv!YBi!)c?>{@Gac;DFIRH7;YxD@-Y4I4d&Fn5Xw<q~}CNXY^XhJT?hHEK4
zS3L*vSwcc09O)YyFb?{kH7HZ>!iNeT7|fq|DUWcxbQ>o;`-cV(-)+;88Vm}G)rJvm
zev$pVI2dZ3=wL`=cDmG!Dvq$X-bb+MdPc4HF5`jgoBO1E_5{x8^<Xb^w$Z)~<_D0o
z3w?LR2RXREUb>Q%s;(QpDPzWaO#;RIz~-dy9d*Jy|5bN$X}pCseX2*Qnq#%4wNB)v
z7V)wU8SwvIcjL%@jQh1`f-FxJ^3CTlV%UsWuI~Yv;IGeL)ovu0&d}20GymAT7n?Uf
zdoeq3@vU`esv+s8uj3i-{`DEKFkbuUO75@!{4S}Mue0yD?#`Y)Y-$+QQ&o$jvHe?@
z?%0Xku7nrIr{oB|51qJ;A9ERZyFmNcvb0fI-b%xPNi<jUm&I;N$Flo&l3zp+KA`75
zZY%07Qbq(f2o5IK<u4OAidit?Xp`-5lPzBckyg5s0q&4ELU!5x>YcNLWOD~3Pa{p2
z-7^Td#pN>IYIF<FBXzA|noZPa=%h85CvaFqs<KrzrR^cJAjmM62hhfQZROog&08~?
zG_|gZb5|eOIC@*@sOpJm;*mIF^i`b^zdkS!J>s891k+3xl4w|XRmaU`Sa?IXJkBmg
z7E0i~<zc-ys&2>ZK`&KB4YzjViG!~32$hp<tCMZ^UmHpTvs6qYLtMP(SQGd-b0Hlk
zoRj!0bM;uIzY?fz98(Y$tor@Heq-`Syd&@qzW?YQnPP5AjGRF^Q==+%r?D-N1TjKC
z=j<Y3EDh7v+>VB4xPyEqLFD9tKNrS>Rtg3~N8g4jj9c1dh(}Wc3y0`<7;3H`@rn&2
zU*taDKh>^Ab1i+0JwK$deJDY;KF)knf4J;#*2XDIXmO;cL9||T(jxnS2ExK3q!2Ou
zosa)y)(-Y`xR4Hg_10(A6(#M_pX*D%5M9m7{4<F5zn=;H_wL!!@di6|iK`|_C|*BK
zV%kqX@K%(7u_E5Zd3x6Nc4jqmzNce`Vita1O9yRU!mXn%TI2*?sz~r~dmDU`<WwBg
zA4$y?qqk<HPaZs0Zvs#4wll52aQNx=)zLGS_M4(JO)th8F^^oR>)0ZZd3?LMoOSfP
zVZcfxYuF-SCncht?WN9civa8iOyw8BfTagC^j;b|8&&y^6kxj7e}Ds_pDv*|3F(3(
zXIl?9YLAt}E=g-^?cAT`!~E0$Q_U9zv9sWyO_R&&VZHsrM3Ru~$pc!9T*_88I;Ojx
z>vhDo*-=6s=O`=Qq|=o_q#tIT2*?G|Jdg86B*|&cbYL%_nRyQFhvV7i$s8Y}Ij2=}
zw{QKX9j2C7?vxAeya+Yd{R*<*ziA>zfUQtE3g$d+LGI5L(~n7*KrXB-+nWf>tOv9d
zKpQs`FHjnp(O|#IQOds1!~XB<9Zp3myWge$I=#IbdTtpDJDpp?wppCl6)<Qo--Ouo
zr;FGfZ5H?%PPCY~ca;t{iGyzcKO2B9tQO#xGMMxUyEd3JoZ#(h<y(LY!2$QUb-CJu
zHITtlb=(owzV;m-+$d2aZ){6@0)y?@_{Ca^ToF3z$iyl1FD>)>f_^r5U<@bhF5~F?
z#|m}1q>_rl3CW@Dq_J>iQ*N<UiDtlu{e?Xv!6cr)$n1^@*J{pS#U^h*<nI?Ht>L!F
z@@uS&ZxE_!GuICdj~FNZoT~|+<Z&*@V`Xskvy8kxa6sZLC<}v}3vK#*)uDb`-D;0-
zs|^`UVA;f-I2&)d7mRf}b9#c#ZF8v`qpAjP<@TGEhZgp*%v~j5{wwVHM-@K)=od57
z+3ApO+I!XQ6-A<ZafY|BuYn3g=%)9XhOd^tog<_P<i1WDyBMK0_Kf-uXlO8=U7##`
z7CG9IZ@NWMzFmL5-L-7=&32+WPUn@SCn2jjmfOxo>%!T{PhZEx_l_64cut#_Wrz2z
z<?bDyUNXM?AxyO#kMJq}UOUB|EF3EDH{lN?v9Q9?BJ99_@c6nPtL{d42h4%6$JSn|
z<IJhw<<@4lrx1s{zU)xfdKW7jU*#!(-pDD!gres8m&DbTSP#hR?hw+?wkfioqsx^c
z`urGtPqOiVPX+%NWdV;b%$y@s_U=O;te=>%^gdY6?n+06@2VZ%{+aXT1KI%PWcK*m
zSA$l)T>-Ro4FI|g{!*4-?DEPLcTRB|n_9f&=kI!iNz1M%haXG-$s2+a$Q*~6jq8lM
zfQ{<d#oXoh3dhqbIzy#8UZvPD7u#DXG*ReLcW4Om%MebH?#ahiA1InpKUCIMS~dw^
z-301CH!)D)PQc=LY}mMWmup$*G@<PaTlCS-1M=XQGwkQ`i#f_kpPd!gGZt&>#$Wdk
zEzYj~wiK^S0dsacp2_>#_9{HYUg%xHTtJIDo`4V`ig3pizbQ5zO-;o17m5`ekqk~0
z7&T_lAg$V|DL+KI{;9~M|M}@@J4Jd!2O@qe*vK89vL1!r=Qe6u2$PJZZ#NLnL;OE}
zQkv!YxL!lUN52BBC#CUf4}(5Edebx)M#@w4!Cje)#KJdHmYk&w1yuRj9e>ExpYqfT
zgBe=t>%l@+g!ext>uboe*tO_U(s=eNJWn`heEjt0A*kdbQa{^__|WAaYLHf!$v3sM
z5ZfH-*TqbW^UWDHZ~BUp!rt1$n&eFIyHBqIG7t5OPdE}x9){q$Ivw%fQeQ?Vic4K2
zXGZXzs;a$%pe%xaN^$oj*7A`L38{QoBY7YuZZKzqbUq6XxCE8Eh`cYjVoD~Ct?gpR
zV;rH&dS-r#`o#I9fZurZBrM02laLOpvO@xG^YwF;vvQ;GKFdeo>V>@uDWvR*lJLUX
z1L(fi-ukOH@@8Ctw{E@adM+xga0FHdtN^KG{}kEwau}0BzeVcj(pOJHKMAVxoo%Bp
z*%vL}tb#|~ur1}OV^jX;WskmIl2rfCJC=KraH_Gu^s1MckD`45JvQj^+96TFu@~gU
z>Y9-W!p$0e@XM?s1<TS}N&v$%O*FWKWRU&m16UPz5Tx;7RfN2d<ncI4eWae7s%tMA
z;UUr*@S1XlRc{wTI%;sFryqq~@ez_V9*%JDh`q?e$=Mhe(hJEzLR|8A=Ks3TSoMBJ
zhGtm}>_XHeZ$B(ORwMbp-4VMY?8AVAcKv58{X>K9-xjIOyBla<DI?-5c0$^s^WI^{
zF&RVCYCJwGf%nN{3=O~QRRbYGnL}(HoZpssv7n$@WA+{!30Cs}@GoJDgkAAj$E0ef
zXnOg5zdme}Abch|nHEpere*Y4`pmqfZ+OPgR~WJMR9?w>D}K+)>sj`>&psY8*Bet#
z!jn+KuGG)<pL_aQPLz6>{L!x++hp8+ogTkS)8ha0O2Sv`>R}(oKSd^DwJs*)(XG(6
z6^-2)SPr}|fJnIG3~cNFuWzgAw|0GtB&bgK9{N9*Svjz^Vlmj1Yg`CmSI11iAA*i>
z{@nF*$)Cy=XE9+-quq{`*B5%p@ZSsch>}__dny_7UuAkRG0YU?YgR@=Ba!y~cXyIl
z>H1i6f>~HFp+ieZVk+;`3WVjSLQGU=|NEL!Zq^L}-msE45&ToIZ^Gvgy{SZ}#sx`a
zQ~v$p(UScD?5{tDn(~@PUq>!}mkFCKnJ4|V?CV1w@2RnzyO!`GDHVKF5&!zA(qU6x
zKQ=tvKaZcO@x5Zy^=E{xbsGHCDLNi*OE<F~6_wimpJnl4uA#YUN4Az3E%cMlW>9yk
z!&<0#u#YI}|61v8F*?QAmR=zrVGp=M^3Ufvg2Rl{<~S<}&6|=s;Bq1HkwSR}Hs!;<
zJJNU^;N^>A?Qu-Ky8Hhy_SIoguU)$;0@8{!0-|&e-5>(eg0wW_(2aBn2oghg3kU+z
z-61eYhje!hAvrYX2kyP!cYk|-=bXQ|F2R{6R@`f?d##6uH=F#E$Zvt9noR%GY!N#Z
zU8=q7OdMh3c@uf>wIF?;mwR_WOt{IvSuFaJ3-y1PD|VLTTIN(Hl{Pl+H<7Calff&&
zJR~K!xLE&wNB?^7utB6X@%F9}Oz?ARVm@2{^)aXTM~sw%cm8DyZ=S*0P-&sOH@Yh3
z{#&{MtI1wz%}<q@J9oQ`Be&2%eg{&b|9u%>ZVw<_|1bMZ+#P3u+h64|c(aYyjVDU)
z`cq%Jdmgww*A;t1@~<XLA!enHfXMddIzFEG{OMrc^&~cGyx$(}06r*DMl~<k*G++B
z4>xk?-_B#tz-Lgh8jV}><}<!n|79;=)q~37*XdwP<>y%&lbLDp+%AQWSSjfN?fd_@
zQ>1fjLU48uw_HfH5iEmiu|1TP^nY7H?n+ard!_Or*-!cCJVh})CT&rbLe&@0c#vY-
z+!SOOSy>$#1v(^~nxRwvr!~qnUn4g>`#$2I8!_}m&|W8+L3K1BE<D=*U;N#bq2TeU
zl~R$5<x$PXi{7)5w$yG?sK-5!su@p?=|7Oj;C@ZzVnc}A%@Nd`u2Vd7O08e~iJ?aX
zdK?+~-)D*3-uNx4Jyw}9vi<nL9D0m*E9n>QC#yb>N}r%~Wq*X&P5F><h{sIguN)8I
z%aXuko@UD|`ab@L6DM|nb3aTvrX|Xj<Qyp8us59PB9rX-_=W1f_3_2vT8P!=0i8*g
z3WI6+SJ4_kuP)lht5t;}m|t=4wZzDiPle4+(Z6-DVnMXq=~K*3uCiqQmN&(}ygYkX
z%r`3R<VGVRlEG%Ubv?B|Ho1A5oRrL;IO@KKJP#h8z~iwXSLV%}ek!E~D~M8=?#Ks|
znIp|iA>_%SrC*<#k{MRM#YS}etnvjToPv!7xFb4zPkpk!7YjX9hMX26|8tA41^2%2
zIxLa44g{d6SqVKQ;kK~)$M<eMov34{SwyKfiKay@&+1qRYx{&INgBlPS``o9Jes4D
zF}#gj)^}nFr%mOb(kq!Qm(X5;>cxc_VlqFS^6HuTj^JYOlo#6~4OQ0P>?8lDT?@jM
zZ!!49h8zJa=W9eOEj|E(IcZJH9omVBea6kLmd{r@K&QNQ`970Qtu{b#rx~qiP~}GV
zrGETn#n5<Iy%_CQdm!<|gW|dDD-sv!7?N8bzu^7%y|s`s;`9=Nhz-TJCApxb`nP^|
zkfpF<(BE*Pk&nIb0{I|Fi32q-gf^DMp?Ni`8$$M^PQ?#*U+)i~ivO2WS?CFbXPA^k
z`bRvHuOG-taz>;epyO!L^#AS3eOQh16Q08Q$QYuU;gFUOHyeANON9D*^SSZh=UI+k
zGt!lyBMRn6ezJnO!r;q9hJVFGywwP>QpK6_&3DNqHi);iHyE`kNXY=E?-p?13d(n^
z&|Kh_L=Ck)oW0kFc9B6Q8M|MO^{*?K7qe!!C1Ue6FA^C7aTNYxuc$0^5#A=_%bKk}
z0%#mPqUjh^^3DFY&$np{5CokUT5(qbtynjPkBaCooAo^s87@8*s)P0Xd1Cd|y!EqJ
zp~;IksPY6&8trfAvN(P@L+-^oE2KP{R_dPL;ke9TI@=gg(!@I84=582D~WaaLa;)^
zWRP3}hl@p0l|!Q7YPqU4$&p8i``Eqb*f-Ylp&k%z0AgU0_wnO~@@k+}gB}kQYLaQy
z09(AoIuH5Bw`SOWbIo|)9+?68YQ%2cIgoq#rcFiq#;e{Hu5ZwJ*PW`W@=Z&VWrNG}
z%4YD3{AD=sdfh)z50Q|2hO@`8cxzh#_ZcQJ^DGfxXFytb^xym?-E6#&#;}#j%jKSw
zmmVzALD5W9H|9V-7Lf6PdStt=0l9XEvkHTaT8v7KX2cO7aK1oed_0lT<px8B{T#O8
zP~@OtPjb4Qz;C?q@jnsTz*@yvdlJVgDUD=#iOGz@V1|VGb5F51_x{^Q&4&QNo<x(a
z(7Q{+tl)qxzOvkY1~h2Qagi{qWFv=Ez98po5^`74PA;a&_6qLFffu28M1pMIhU{$t
zr7^OBm?gx5hWQ$q$pNIlGLlUXt~O#MNy8rhPcWLU+!5Ell?BIo{CtwvW!pT0_4={o
z#m6uA|E70@t_m>~d%??*S`&8fqTcn!N_cn%_Gq#P3dQjdSyFWrKcJCxQ;2z4RT<P?
zXB4E+FxAPuPw-<Y6o=Efu&|^l!_hbKA9f6_H&KXHt-fiF4U`e_Od>c~nL>w47l|_B
zZ?1=~GDT+_v?R`>ipTI39e1ioxLy>RBA}8;dR}A+n!IoF5(vZ^ZyggDCjBOG6KC34
zk7*qAvR*j1iimfCD^p(L-y8)R(3ikm>ER4xW6Ow8BjXR2I2a`=@(z~*?E8O|5-%jx
zOR|qQSFs^~eY`9rfOJ4<6amRwKR>@`xegdPb*Pj|Sn0HjeV}pT2*Hg1``B);Qx4Tb
z?mu7+WeX6G0$K*Z8(f(f21e|(CQBmVar5!2wSX~KY|ejf*T_1VDXuSXUqvE<8eSyp
zws0L|t{Pq@2J0oIkq@y+WQZaR;hDU%hj0vRi8>1a{KX^cZhWT>)bOROt1<_P{sr5`
ziU`(j%NF3tASdR3##KL(c$#>f)*=k_#h>p|@Kc)&=Y#7}#Gd^PnEXPColGn?`I3LF
z;=9SdAz)N8Z~eiYK^3lo%X(zRO2hPoew0khusmJV1BeBwgyn!#BFr1EB_50&B4J^X
zZ!%h#eq-zfgg+2-VZ9Y*b`5crs4uh1=uc+t4E%5WD@DSos&At|ClyI+Eo{3~*F=gU
z$!WL3<AqyuundTUw9Ec#xAoy#Ip%)@r(b@lKs7;4jXaUoI1i6OO)<JiP3>Jz^x)-b
z1ANgnGh~^Fz&nvav_H3Wchd;;-b}=$M~16A_!%`u&5|$Qm))WVe@ASl11c?^wGpCH
zW_LW)cl%9=|E7x=Gb&2s_P|q>buXDj*witTM)jW5*Nm7TeZ~T|Umk33S-t@L&0RoE
za0)GO%edumqvAqA$LjyUTOY--*6Uoo6uSS0fAqGl-Zc;jIORBBAIgMnN5w)34yxoi
zHqY<f#-wbZ#ww>uA`!3Zj>?okbI7z-e<Azk`M+ruC6$@z+{n58+rKH%ANdOUN8o=^
zh5yHY`JZtUI;9fQS>bHjPxk*d5q|{p@%1M40380e2>L-F$$-<*RdOug^ZyZbFSg##
z46%7^0R`N_1L?Ux{lY_BuFt!hmwe2BQ_A0-@{hDzpyQwJ>;L)%b=9Miqzg3TL}-A=
ziER86cl<y04&FxL3i%&#ikQ^!hsJM+|0$3iqh;U3e^z3NA16-?8^@^MK+COfx6slj
z#1=LgnDM4}|Jh3ml;<o09vzN6$EsAqyas>6%u@W^sw^I-QSmkJ3gVAu`E8G;nuu0{
z;5b(_aAx4G2Rhjz_x<*;{p9>f&mVNM{mIq)S%R!n*lAo{_wN3S)CNCK+s32rB2Z0J
z%1|uv5zd_|k1c7scYXt6;)#IK;Tzn_rAFO`Z4l#=^1HAr^glon%I(ja)d<&K)SMf1
zeja=rVuy@*f0$moyjm$%m(Q`&Whd2ixQ8y-sBiX4q5jZ})%IfFBa;a)-`T54khSR8
zWrhyp{?<Q_sXhNF>fPlH2(4o&<mo~}zA>ZV{fs?H(ngbs+yslJwE$jQz_DfuD#q@<
z)&JW8J&?zjhCvhB3d3+i_&;O^Nt<!0l2n*bFTvc3;`{*j+446;<-T|JWw!JxnOQlc
zR9}?zCf9U>6&5g<&SQ21>u=M#rTYKF5OAtatK?|+!rApXRps6Ql&q%CGIpy(hQYgk
zvp?<Y6TXnkm`|(304(G_<h^(V&D{rVWrlc-A?#THABbA~R7O?e=<8<JH4X_^OHN!g
zKvWv@!h<_f#ME%cHZ|#uR>kSnU%Q!#QF&hZmh5(#>vgj)Tb5Wi9nTlpohNAFgm@fY
zJ}&g6zV<pBMJh4b#s;}<pzJNwXi4e-O#>UNILR(bm1NPUkVAe)?34z|)uLI3*{SMR
zjly2pz!O+A3KPehWE3Q8&mZ=A9SfAaYqgqyq0)-POxax7Ofxo}Mk!r?Z`fUdi(c||
z^VA@erkzj9rmK!QumE#|?a6dKI@MwuXEn(<HF45nTSSwTqSL_=;1p+xXYNQI>tLF9
zA4u%|C$jz3e*RUx%bohN1HsnibNAMa-RfZDx=7<!sBL#HzN9AGKg?ssn~KE6<_+^_
z_Nz?KxWSUApQm;E({kB8S{Nb(Uh6vCqn@x|ez^3t-+rtG$;rZc?o>6*!ytM2M}lnZ
zf<b+QMN6Wk-T99|4k&n%UMsznPB#w<McSKMG8suPGccJx+1WK*AE$q2Ub#i?V87f$
z4{H?aFrmm+__;ReJlqaX;dBeUXqr)ZF*S3B^@!LIEVOCdnaJEZW`Me;5Qfw3ctpxC
zdF9nQ8#WCTD;tIjs@&(cj$W*oRkTH5IK3013LopfYZzN1a-mt7Mz3rXw(sK?6adjW
zCI)?fm-n_T^wms8yKK;-$JyQ2KUL5$0WXtP#oYF5?<JJg{NqQGn?%pAS7|)8o%eq&
zt>F-Uva;mrLi&AtY#>i(x4Ikv($VQvK%K33EdU+44ZI_CtIzA;hJB@)8S)*Y8HO?F
z85)5ZqvLr{laa=(__FueCtK&FFyT&v@$r@n*(!y_^;2I-O)9>t&PT)@;XEjS5SQ8<
zX-|yq%LmU)_07tKPr2f3nhu9?E9eNYNY?YIaGJc;Yux?(wjj^2xwvsrWAT&ZrBpF|
zUCrf+riaKl`jMCvr+0|}jH$51J?G=@$J;pT3yDdd$~XFJ@}p6Ked`|Wl77WskUY7B
zIytM3*24+ev0x7hy$B9Y2DJjpD#oaLmMc9mT0j<BaoYV52XU2zldM9kdq^%gnYm3^
zdmKK6NUJq#vqa67S!L3c@W&(;54&n@OE2STpM4xBey}#xd8t*tGq2P%_Bq1NZNm<K
zrRQ<adUH>xA+=2Bb}LNYVN4>wVskWZ%3$EBZqF|h#1P}Y^SBj{>TF_#hLtZG(h`y+
z{-i(1dpo{8v!jT^@=69#1H%l*!DR`qS}S<yazJQ9O6#aBkwRPF=is&|aY2h{>ncE<
z?sn(07=1HZcQNwX?pV4eNHux4ci3rVE-$4}=&W;_Yg6#K@zQ)la-&U!^J3@sAu6${
zJQkxKJcc)NqaA#&Sjc;RxYQabBU}KSNCdc5SunHsTuZ}sftTiUV8SMlRQ6#Vg|Xst
z!Bu0j(T|aUIuU_i5I$$l9~OP%)}nus+hCN($JdjSgFZ?!yfx`Tw~4kPBsSilxc9UD
z9^U({#t71L6bww#@+#Bax0y_l79!=EFr~&fe3?udx}*a-m0Zq;qKHc0ufpL|sdO66
zITXyzbiNyplLil7i8>mBIev^Ct-N*$xoqv6UMXAIODZ>ccYFPVUK$if34y@<bI#o4
z(sH4%5KHY%*N!9O3R13sx$ahJu|TfC9RKiWY38Utfx)>rRFh`@<g1=@d2m(*Iw2#a
zu~u^3xmHbqd`Dqv$V>-oEgXwPNJ;o(zxq6yQr4OB&UU<zw<UFV^nuA3DVyp5i`?CF
zM<!aeEJ;hv%B6L_8mux#8$lxEwH?9zoG?h+{&F`fyHU@wrx4qVVlUt9ewX+cpCRW8
zr9D=8oSu~x)Bc*2$F&+pm}`Agazp~W*T|{PZ~82hIOOo0vCL4Q?5b?RC{sakOw7iY
z<M3AT&RC&3i|)o5Erpnry|oqY<>A3Nf>yp(K5yd8z82D`6g}rU1nH&{;i{$|!w7^}
zKBgH+mS~bJHydjp`mVqI*L4!?rsfK#MShXXiUd4wH2n4k1&++j+ZKZx!F8nPj6<2Z
zKEw<X!2(`~N`;1+CHf;z_=1;uLhe6GbC&9PE2z__E$Y%DhTJ|<#6n_u|D`KPRl$>l
zb(70evhQ#Z{t5}v*hFuf{d5PKz#f!(Sr;tSQQ3_^topugPYrVnh|_f$^q4s$p6)hz
zo_qtiz7XhclYJFt1jXXSWNQKc(rGl|vzPI{GXn)8gOAUgIEqg;$@!=(8ymmr`s`x~
zE75dQaDJ1+jDVyj-Rbrvc%N65G45!5w#xWbjYoehA53_#4WZ{rHA^z3uJY~8=+Ze#
z-vMc>>km7RG%3aFjm`awnVRw`y605d11h!&4D<5|aJyAhBZ+wffl3$PNr!^zXH^ax
zgJULyhoszUvEWMND;N~(B4mOs58FsWKQON{MK{*y6T5yTIX^QTc%zHYt(~+>g)h;0
zjIK3OpHA7uu=qaV6*;?6sS@G5GhN!RzI&%m+WlAiyX|l%Vh0cy8RDp%^^$Nc4j!kw
z4Iz^EE;jY@nQl75(1Egl#(Z=xhfl=ICVW`?S*j$mwDIj?_pJYnN(&REMQhLV2CO^E
zXe*n%4x3z&UT)o591gQ~nv%-YY(S<YwpKGhjV$&0>lGvf7!C5D`clWT#8L?N_uhRS
z3@Gmqzs5esE*3NfKBvvy)k2$=7RAA$h|?{;vC<N*D;HyeD(gnMYB5n7MD}Tprwe~6
zyD=R`Yv^>rohb+$+3l6B59xX+7&1{XEC^7_<40N;DcG{guEl8sCDbL<IMQ>coppEJ
za=XF%nM~2{Zet10p1wM^AfKA5uoE_)tlqZ-r<oWWMOKMBnm@_vgIu}SWJM@F^&&@9
zPS@B4oOsBFc(lq7K0^lHs!E+QihhL4Vv;v5htFmfc`%k6pJKC;B;v-UiW2%>7!zg@
zPN=tIs#s<vq#5d(6DGbHzxP@00hM?MQ?PDP7_RavQ;b8&`}hV+B0|?5em2$p<z8b8
z)TyxKsBQfXmWzVeuKfy3!dRr2r`-)GT}>s)_*cTftSu$N8aYMaWv${ZqWw<&I({!U
zv+!R!X&Z}J5GhR3>q;e*=nXKB>K&s1ebW8<d3VDNj-Ep$Tm8|{Jb16li$(&A);9)c
z=MQ9Jn0NQCK3gsq?Hwl$=MyF}cmr^;bhyPEUSxXdwXQe%02osCp9<$~RQrIZ1r|@R
z&NaYCvpKp3$?WMXw)KTH@E@6xLLB>M&NTY$S}af-FxP?CoJ3|Lj_zI+jUixP^>o9J
z9`B}dce&pMKRBQEd@p}R#+==CDRLii7G>Y~zHd&L+W70!RVM-kj;?L}iK5Nds!<MU
z)`(=KRP6zgUnB#1hwKjna`#Vhs;1Y(8j66brfI6>jJ8KutA?=3cPBBR+BiX{oaH)V
zx42c}fMPzIw4ACFLF=Tj7x&6o@K~?$mpq@=@^Hk6<WzcFTyCjzACb$&LB|;Bxi}Jr
zQOKLIhIN9mx6=*v9hnzre%l!a4T+_KvavmjKRI?uEk8a6KA-w?ZbkxwhJT*q_E(7J
z^}<qpB7@YAP)q0L&}4>2B0-}_w=~y~#BT9*6YIfAGCQy3>kp>h*G_N&jnS8a8Ytbu
zt=|dRRBfJk2#7Y~l}|0#aPRNNZYOsWuV;TW^fRw13bhqlnbU~G^a7i*HLw&XiKF+#
zyJR7rI+5c`B<#n$^Tcbw5&&oOHc1(}FgIY<U%|8_FJ!s5Vr$HXZS_?Q&{&dXA^B90
zJi(*)NHyD?-z7p2{n)b{!=KV48J)<V3xA%K{o|Ssp)Wlpqfc2cyGbb1QEoEx?zSg=
zjwLI@K_A9FJwr;o?689MfsWHOD^A0`n}S5hWfUp+t^R=2n#J^62eY%@B-^tyv=a9N
z+>+fkmdveVCw0ho#J$(cPGK*@$Fgk?{3XR)A$j?86>s}|ig%*~tgS#c&LRo$mm(+{
z6%Gk<p9?pA-#}!7CS;9>9JbG!d6kYp97tuH+*`WOuSex$5*^Hbtn?jL<Hvkcja)&C
zTbh{yyrc#{){(x{IHKtCJ#!6NcOe$3fW~qs0$xOXu+mQ}DNn=_LU38_<msjZOW{yg
zaPna4I6j{4G+a5Cg(R80p6e$yJC?q>clrgC9tXFWXnH|Td-a|26fufKy0T}(vU3e+
z7{z>jrb0*IwooNlP41HB=-stq5mMP_m;&+kUhQQ9LtIn!(^`Z}`;zv%-b9J_>(dG(
zOs*bc571~;&3Wx(fOnEl6-{da5<sLybnZ~~3+7C@y{fqs{MUFt7~#w*B7JmW_ZtCw
zwko-ZonVh`+r;5gtW<b1C!&k%kY?v8JY1+MeX)-)mrSt%RPrYI$f=Ax9(Px(X)Qh<
z7%5czg`iU2-8j9Zh_yJM;8?Q~k`~}*`GHg8CR}EEiA_L6rNND%SMAQsnC<J~E;O%h
zd+RJpwNJDXkocvhL-$jW{JWb-xx93*u<Rv^;Fj4zeOJor5OVw&<1g=Pf+WcV%4W4_
z;YTE#Lv%<C3H9u%zsMJ!JhMi}B#!5HM3NvDICf{8mBWu$7(c#BSB8Nays3`X3F9d<
z<7~5KY=CqQ(@NzDwf$<(^*%yBDqL~Cd98_1xrLNIMmbAI+dLCX?<2!knPN~ja`Bfa
zex7YTGe%*-vi_W<Fw!|)M-jy?BM(Zeb3^mJeRCZ^__J0jxA;ok%5&xLRdw?$=v}ny
zG>5XZXqR}|NLBdkV(Nz&75b8kg*jHZtvM`>nB1otUT+(xMs5rL97y0O7SCPW*PBuC
zR`T9PRoDSdBC&ZY7Gk2z_p0mx{qRyH-|gIzLi;Y<cqugaB~x(jWOg^=?57PE=)H<<
z5p3q$xiF(uDzD}k3*rAdbKYpy2FHrm$q92jEEN?MWcx6H(gSLEQf@LL7dwT;N<^)(
zN;oxWJn%Z)Ua~iF<IwI^SnYUr5`(cdO||{S{Pg$o7kYF$h0)U}nLn;(fw~WGOFS7u
z7=Exu_{kn{UGh}`N{W<!nvL#UQ+A*^HsEbbKIL_G{KeUMH{hgWm$ka;a*TrIhb0^M
z7vlPIBeL4Y(AU{(8`E}gnP%_$^0aiYG3EMn<FW1H0D6h#rJU_{{eeLftMW>Rb#g}s
zXoS1X$5O=0OW_LZ=i>A$_{tt@$|Td(oSraOsOeghS1nyw*je0bYg^jr>ls3dPRHv5
zdwsN3flB*OTN|q=b{QL8MPQ&?ovPLO&OzqBGcSd!hhNoLQS;S#Wp7*&lI0b=NFB;A
zoxs3L7?1psTY+4c`s%9HB@>&nMNGLpIQO39YrDd#5b^bsF<`7NJ)MR5Y+geNg(!AR
z<I6dlHOSo#7QV1gns`~=s^K+!Dw<!_b)$^XBgZnajY8HfU0<%K?8U0T0|M7l%x<%V
z-6|tyNAjk*hnXy*m~?4CP;sHv&VD+BfY!2cD`v~#_vE#lZt}c`DiL<hfeuiPO12Vo
z3vY-8f~af;hwSBg^(w>@{_Lv$AxR9^Fqcs{Es%5I6jltSo*s6z&h7#L`U-b4YXcdZ
z;rI70EVwsW2Q>~)?ri~s;db12beX@SlsM1ghsM^aoQ>s=aAgMi-@j}jG+!bNOgzeS
z%>t@4&tylLN*nf7y90J!))Af4jsaBy7^U(VNeMkV{<#Bz@zUr~JGA0)$R+-5)l3TK
zkYcpMBlHgW+tv>^L2Gh)##oi_{k3saoQjhC=*duGOlPT3_VY-Ct~<@G4j%rU(Gz`p
z1fG|lK5m!^7)k1D-$#OMhsKbfyT9Kno_e5JZq(=|5F7KxzZ;6IEOe|{Y!>R4EiRM5
z5MbF`xk3&>dc|vu)e=zJKT6CoQPXx`E;_8pb9olqJ`=2sia008$<64A=b;JV?7EkQ
zfcKTKV^TJ34P73Lj&rE>q5Ew3TUHlAIu|eU<JrK;uP%Klc2#kx+s{YcLM$8Q@F6T*
z9)*F`N56vH1dM79iMK8WRs3XDq8d0!C_mmu5}wjdYawd=^yVj1+k3#<Cfqm6D>vP^
zNN=zE>F;8Jh*gGkCvMnHE$>~n@ATTg!+vy8(3~HKQ`yH6dRL7(m2Q8vb47`wj7OM%
zUi(a!N40)Mr6m$F?mt#}1IgX|QhQj1ryIt3xtrylFxeXwg<a6H`N<GCh4x;ZY4uYN
z)O+(27l5!gcgK0V=@765Az4A((Iuglt1~|JW~vtR7b*S1Gw|7~qXOTIk+LHpT_ifS
zLunUGH&S48<sk@GbG0=h%?NsBNsyTok7@MA-a}lvYU7$Syd49j%nbs1vpm3rBRMJ~
zb8r=J;Wa*i^U3IAFL%c2#cq@d>J#D7X-IkIR?tFUiMc&_u64Zi>{VYfx#R~Cz=f20
z(1xvi57ldA-Ct#WIwfEaPoMVpDl_V48H`(;JYFE?gClhaJ0Ys<NTDQ5U;RGrezg{|
z8EePHim`4NR?adUA=!7Z6t)@4+_rZj@6=|DSBe^rG-AsgV1Z&*VAaU#kLDm=0Qw5>
zl~+ELjD^8BE_|?AX0IFS^7qR6^rR-|2#@&f*E-EFud`oi!H?Uz5s!AiCaQj<?ii5V
zHYSm2l^SVxVO0Bm8vNon!m!(b`i<9HH|%8rh~LK(V3c(tcl$bQAbdF0V|UZQ(Tume
zxsU9UOy{bNZ#9*2ja+P(cd#?HBTkx|yu)K%tS`mPnN}_a{jn>TUhu|#F5UHoG!3`f
zSa<dnxyR74L;9$UGqtZ_r#3nX3}>Z^cW_`arX@fQ2H_~E(NUQW*5x_Ai=o~hv!a@(
z?r5zntG$7<g5L#|qE|*fU$<<f`an!M_4=a11LBiE(fEBFwL1Wx<*igKD$v?)C!`|9
zkQOAucK*P!nYSc~RDYjojma??Tp_=*Y&u@vI7sk;(x)2MBqVvY-K(NhmRGzrR#7AZ
zn*0#q)3^%P1`<FyfK^Z9!(Jm2jwUgugoSNF1k0aMJp||>xWd}>SoerX;tLE|4~+AM
zb5%8kNqy*jP!E-7w^$jX8R@%!wGs(6{fMjqLx_(zMhY4@WoSa+wELQ11}eK(nrzwV
zvBTdFD!-bm$8<<yLSzY}AZ)0O^|sBK1vMO!)nNEcgYS5`S>iM*+KR3Ahka2%|L%EH
zH1b<Tqki|t@1u}VFVG&PLz1#6()~Jl+?#?kBU@q6B(V!jqxj^S_G|K&XWkj$-h1*k
zhFcPl&{2L?M-+7?Fsw7S2lIJdVEvTrou{PIu<5tcp{V{O5t6O-B`5dZuV%9D59z5u
z<wpaC;UaM-c093BKW3fBB4426)ox2>$nkKgL9><c4fXJR%(uVFt8=`cuuJ7dDo&4k
ziyT@!7K1;%eVog1T8T->h2p2q!OUy6nq@+}&-!T0L>O#NTSp@n`1OuNWRHzmB5Tz2
zF%9ZwR9vi=$WKZ1dvYpY$tTjsU5d?=D9>>%j<xI?YoKEtb*txXD&U3L=VM|(^0v-T
zf~G^OZD${yNAt--fEw|u0OF&FHSvlt$Vf33-y3~Qo%(Ck8nPm+Df`tf<~WKZZm%p(
z^JSNkK0+h%iKUN$erNa$>W{7a;#rM1o(enYn&jO_0aCqLBLs$v&^=fjx0o2(S%MXv
zAPa;sj({sQ*UUowmf88h0UB@X>vj-8j1<By;mWOw_o;s;&R;yrn6#Vtu`>nU3PbEs
zy!0nc<nhpYI#&U7p*6rMtuiG6oTZpN{tg*4P5Pd3MUE%#%<}%ITXY@g!BofN{+|%z
z{?yHfXLoRBlv3YhqwjxSw?v8oORg01#h#>JknZ{wO%R%mN`1}_>RQ_8%|`za=;ydv
z<UR(jdyCz7g><(^Z6D#ee%Y3k%kEx(aQ9Ix=1+wBA<6j5(G8)TuS${+fB*sP=)TIE
z3_elZbU@u<ysRU_DR_W(9|$xw*_z}|fSE?7YeR?e+qM?h>|igiY;+>-bx7DsX>qd3
zQC{B@M@No_-5QYY)h8Vr90J9M>MgX%-GM0JybqvOH)o~>KS(J<tP_cVGA*W!wby$Q
z-FJP-(xH!VcC^=RF^Qz9g9OsFya5qT#u@e_{t}0b9y{5U+Iwn&f2w)7uU=ao31PHY
zyYj2-qp$}XMKt!1K&hig@^xDpdXoT`^`ytgTN-S=#2VHYV5ZvDwZDQf$7u*?;*Ipa
z{w=*9fdRdC3eMGqxHad77l$sTy1lhW&{Aep5dw!z9><~>Onr3yT;>LrafdA*3k*qL
zp)u5)v1&git!l@*k~G%n+)}f1%9=0nLFwA<48rzb^QT=!RdN?DBERO0<<#`wKW1YH
ze<eQRhgN}Tqb4?=Qebr(me}eNSBj?7QA@;gt!r$Ck}NyCuyZ@Q(x;J63e|zQoiydu
zz5l7p7bQuCfiiAyDbPhs`(w@La$9n6FnBa>HnEQy?+%n$mD{P^$Ypk`1biG)l{Nlr
zw#DZA7J+J&L0Rnnlf`(tp9r-3<(Yp}=(5NOGB(OWuG6mmvddxJ!9^9fe5Fi;BMIcr
zO>yFPUWPnw`qVCPb(@rU3jelvF4aH(g2(9d`|YbpHxy*tf^Ykp!6|x$5k=y2V}KqH
z#_heyLEVQt7Djr3YZx!E^riGo*{yRZmgzXedo@HO9WIIHmt(-Cf?0rRsU4WAjN27z
zR0cv2G%xiW?b)1f@xpU8J(i!d(RDdC!%}&_(_#42?>16Ty$B_!*aounJBTi;d$|XB
zu?QJ->uhu*9s{k=WIiZDFMT#`ZL*wglIml)V&?uUz8hK1tMgkwl@VA<$EWoEEEn^|
zWcEv_z}P1;KtAPg-3syB^K)N9PJ_3TYN`r!Hnml=q+7p2&+c^Fr3(@%Q>*uF=^jMT
z+276nI9aJ5YmcVdGcW-6O-V{#!U9qe?7Jxur7W@7Kf8VIaySlP_fVcYE`Mto(q{9y
zx|lJo*+%H4h4*WMMn`%d-g${u=D(<Gw&AG<M6hf+#aO$6vnb6&rgTLr>CsA(Qcveo
zS87vjaDqwXs~&vI#g$>1KG$89Yk@v)U`nP_M(&PSux2{<Td6#Bo#k~q7a%U1<e~pH
zsi1p4IlhC%<VW4#(Q6&TuBTta)%L|&J;$BSM4k1e_PFOM;~K6`7*Z_%OD!|v@-NMN
z>azJlEY2Q(l-#u$EcRqa^EI!suFc}Y6%CI#S{0qONy^>dVjq`0iPuHB_0hMPALl2>
zIx|#pye89msY=-oxMAgY_U*>)(@zXfY1Rmt@3h{TnoWgYWK1`AL@LZGW_M*bn1`@`
zPGX4X^KBZeIz(NcRW!QagSl08@S~_ZVB&OnR#OwOS3yC_uUPeJ4I(b48p{(x*{kjW
z^G=$E)kdv<f{MkDepvhRvUn{dBY$bmf6BD$Pfg3>=_qMM%3Ggi;r4^nS8y|L0(1<S
zxmf5`aVadYzX(Q%dd)f1uebu-ZbhFGemUJw9MVFtU+F4t7^nK0UM3P!Pj61t&LEIh
zK!YD$Rz$T><Lzk63DK&L2VlB_JTw^u%xJ{nYb4cGN6r&`tIo#z`kBJNVsd8Fau>~|
zIeNB4Yi5R(_`vSOXz^Sbo<!t8Vro`!?Tyh7a7G+*>qe&eI{^uFk%f}!(OO7fi9;MA
zFtL5A$-{e^06LKloJe4X=ZBB?k8pO$K-CVmaZIQp9&SS>QQ=<{#|m0qZlyqqD_cee
z_}kos8|tp-yn*9`{fzPMVkV+k-k0Cq8km^95pVt=X2_>$1qe}Wvo+Q~!etof09pxZ
zw&b)KQR+_<13Di*zbU={iMF~_0-LI2^8wP(uvcXvG<|n`N0Lkeh{7FzeIP9&mi}o_
zxW2;AP}LFX&_^sJbrRb2Z6x1t_(-A{m|IMWwt2PQ*NyuC(j`EFmp>ZW!idY#(QT)f
z-F5YG1}1!mPh63lUKw(p-rMJx>i#|Fo9K6!VYFeD1R#3J$FaZ1r+H|X;=-7Wf@;L5
zbKXlGR?5xF8<!K$?v`<~|Fw?22?JJ4%R+XPqh9~TKD(-jScZRAE(XZVD_Oxs^23zU
z9s;}^*yf3x9dE}@x*7y^M+qW(>xw>#+U4n=vM?e0yYkt;bLxlQxsr>CW!@yVyi3GQ
z_evMLqCi4<?ZoY1(^S#}-&dPo<bg7>tii_ic=vX8(A!8%7n#E|^kuadDWY;Q9#gB`
zwLfNjzU;cXeAeG!?{R#gb*xPnKj>@u>i8<rS+{q!ByH@=fP9QVT=Ho+5;98gEDfc!
zw_EHtoCR_Mu0*RB%G78>k-7JZF^P3w1JUbapq(K0RPm+;eUPUw5PLX;kd~e2`h&_*
zYFdMoc502y@z({m5C%I5P&CsZH$Ift<%f-n)c8yMQ7#_tK4q-_@<WfUXx!e#7f92A
z<+kVV*1R2+C8ll^#XWUDO@ZrLU)uyvXG4*Quo}tx#&UFYqM3BQTjJgahJ>Th$7txR
zXb#p~t|#`4cysT0S(uOIhD^Uo1Eni+h`v{rAb!Qhap=J^BeJ_A8^Nw><?g2WuDr1t
zJk|MnDdg-945<r=OI2T?##4uxrq}%^U6rq%p?aa3^k_Rfk1L-XZuE%xVR`b5@AXt%
zfU@A!Bwr!fWh{caW7I;61t2dm>O$RK+<;~m``UxC^w%Q=rdvhL`-Zy(dUV3I&f|2?
zZxy!|p8BE0EhnavME#PK<H6wt+Q<81KuV+;6NO8;HT9q^E!QwD(69sW@OD)eI*3pu
zJ@2eSACT%+b|9Jc3PXR;%$ET)m`cmORt`q}%F8{JzJ;?D<u<1@ilcF1k0E#|8545$
zBn&~n+)_fy9lQpOIGPluIO*X6DjH2Eq-DWJ7yPp)z1uG(lRlmxAsD91Y<5e}-qO6n
zyGiZEP)V6*cXf<;Jx?`V*3BG|ziI5qshS0Ce&zc0_77gq#Bi5bG@WX)i>lPPD8)}K
zWW9V|-q!#>Yk-!z3qMNMtO1~al@yWPc2BjmjoXVSKZ;91AL$MvbS)>)QYc_Mu28P?
z-u+ZziqCY{&pxF|R2WgJJ4*zF=QLcnxpSulKSjL<eX?SUXS9Y6PTF4XcT?i_g3;(L
zFh*7Gn)!>(oH;Cmjy#529ovq9-1%}Pgfyi)#=!rRaNRu)2K{@VwRu$a?->Y84u^4A
zZIW*4l7W<w->+|Jr&VtU7eKa-&)6Ofw}y+#10{~{HZ?f2q<Tj9n9SvYt|z!xEodA@
z@hrR@bm|TbN5~c82@ci=X3e>tye99wPOEs7k+UOR3uf(Bnwi9y=+gL&Bb5{YEcxX<
zpYaaMC;KgOJ4k2bX~a?3$>N#k(gHrE^dlgK*sqD@uArsEiOC%*NjXRuy-3IeeDbNN
zA~}olO3iBj56f?H^^jrI>kAMF=-T`6mK%#t`;eV%*|RgP-^J6oNvJ1ttHt=$GA}Wo
z;nnWzxVE~V$&v-B#u6#&dfkQIbF(6=5o?k>s>AH&^J}~P#OIIqtLJt7u44G?vv;2;
zWp5C0sz!>g;7Xgz8d45k)W>MG^-!C)=WTyl9@2MBDSz-6+bfA(!`*t}Af1#l4C5^B
zuQs?pX=SD<WjwECULvoNmZ|-^<8{^Lv?7Pa=GKWhSZwNnAS_7;&UV`>ioMgF$Q2x4
zW)bT~3}Q;lBIi9K8=BG);mbyk?E02~|KpqY^3ixGm{OB}-}SS_WPRt3hyH`%JY{98
zjwZ9!?=eNV5^L%LHF{xIdG*3(AErYmKpOm8WxLh^ZFOH)SR-vcfAK4kO9STabM6Gc
ze5xhWsD&QoT++hQrvQtIvYN3U*f16EQ<WxZp&ANun)32KMqO4YTRdT~TK{7%_^?eH
zEfXlaDqYb<ML)m!%b+~do#$EF?WKKV0~rzLLiLw3s-XAKgSbRK`xQLGo#fc52B3C1
zGHbhoKn3Mp`6DuqIr^wMiihJ9OT-^gF5F2QEbM;;od7xF)a3UcKOYs5EW{AIN2#bR
zAvFF<=iDMxF@b?06x%Y9=%}T$_1im_YPlHV!ilGi$9&cH>9w)Ih{xC-hpTv6>s0N<
zb5;@duI-$*V+|I$wA_2c`z9U7toHqzHJ5>FLt17VEL6o+07pS4hVB_WS*TLssvwC$
z!%8keK;ygI9L2>I{ITJW4~0W_&Vl4Rdl%Xs>W*rm`9|^cuG^x$wEACsyCKegvG=<N
zL3`Ap;ff!wvPjX>^#PJSj2rour*6}Bvar2v*c;&obChu9RK0_VN+s68hd?HeJwH3T
zUJrae-L&88do(>7Cs#p1K00+!LDivhcM97ovioJOV@&7gVp1OTcuIT*fjIdQ1TkBF
z(S<sXYPkE%F&vDepUP=IA$}zi3E02MOP~hc#5U!<Fp`z@lWG%)(FRjR^i6U+JiN1J
z+#7a-z=2IHes`4>Sk;@QO4770FU$Ld_aJ%A$)?vsMctR_bM&oP^A{~dLt*lOKHdkv
zA6vtQZ7mFGV1RP0jelz*0BOE{`YH}Q>+nv9$=gp8KaWWTNIH~%j}#@M&=sud%oN5g
z7n$nev**<YaJWq~^n>l;!cIH+(e=qZSSdZ(-i7U9POi_v7rR%(IcmCn_Xgn~bdu&`
zjL<hj$R}s$P&Ej!R(?G81@$U(F_Jjw2dI2oyf8qQd)Dy8h^VXBBK|FlB9Cfwz*tI}
z7Eniz;rMvyh;rx{inf<{$SxLn55X{2@zG6P<#(N>@Gq8UR&E}$XT>?|)nx2Pq(fGK
zKLkTn=MKE#VXvUBl0Y28^Bbj;&M4(oL|g`)GqJ2KWHe}2EmLR!Vzp)T#EX;+YK-%n
zUoP-I4?VnR<fu<fCm3%%P~MoMQjyV<<t<2}ag2`Q*BF-ad<|R5K3#Xoco}+knNzdT
zB~Zy4=96nTifWX$4!I-yD*Z{|@=>X|p4T&)J|fmckvWys?dFnS`m#JvxAe2o<nC@M
zf7P{2(C|2DJYrWz3+3>*!UI#pWAS2>uY)^5TbXj?J)zB>KZ-Iot;ZWAty<q`n@zR%
z_x-SZYy>?pA?1@RzP#90hS^3jbd;KZt7M5<(f<Z_-drFza$i5c|9$WPb*0g{sN_Pk
z;;kwKJ9^JL>`~gZfcY>&GPhKr?A=l-mt+E2J;e_%-{Zm8`sfSeuGeS3dW26&2n$oq
z%kS!!8jJ>QS*z(aV`kHr(FP^q2y<=Xib>J6j0?UNHpWI7ix<+)GjDl!M5PH}YMjX<
zcVg!cb2*;!5zI;U$IO_hZo>Ev8I+OboHMJYQ-Nx%sk^>o&&p3N@$=D;tc`~j8E5)(
z_@9kpo5weRNUa8Myba_bz95Dyer%yRQo(d}TvsNU)Yxo+TVX+>+sdf(w$tA4AOJEv
zTnhfIxx_DQ?5TeWV!F=Sd`91(i|X#~T*0YhQ#eaB`qKS)L)TPeforXA<-)eJ77{gc
z1lXk;pxw}LQzdQ=MP6KJc)mE4+q+nyKGnU=i(-Vc(LqZ^Zy~*DyBqYo3NwWN7d^Rt
zJ;N_v(A;Ma5*prt>><m8xAmlYuhC>A%kKh0yy=sXg&vGJ?&IDJO%>8u?%96Q^J(aJ
zH--VK<m*$jK0QnN#7fJj*xGZ8N;ojZq{2Q{|K_w@T!7^(elK2GLjmhl_K^J!$9)fV
zy+r0W&3C^027Q;naOrh<`GC?C4ce;%Mu(2H=3<T-!{-XT+B47hU`R}27wJG~+noQg
z)vbqWC!JIE>fk^XWcTaa4g`kB_ME#QaW&b2L{b?!zgQPlj_iEzn+n5oAOX2?MT+tX
z7_HIR=rADkvxC&x!+GZV@}~q?PvFvx&mJ{H*r<PfB?!o`+mrG+{_?;&)!1?XPVf#0
z%nhAI`M}q@f+B6#EQIdyqc+yd@uR79Psbo92FP&TdFh448-0;W11`$kyN5arB3~gk
z9!p$xg-$^}lUh$VcAECObuTf<D8rD>Vy)=LO~;2$;SBDl^xBKkRi-{(AVy?|U)I}_
zO{>~;s*Tke^={dNYIax{UfErt80He#V@0K<kbVZR3X0;A+R^mU><p*GGV2K(_a(Cc
z*JC#pYqm*QE8t9h*jHq`8v`{NTqpKkhXz0kv#5W0H3;H9tq}|jOQ3co1_&e6Y&5JY
z%hFth%^E_}lVD1Mp8eG2q=$O?G{|z;*7}+Z%d^cx8fTtC9DC*v9jY|7DNp<J@aa`^
z8efJ_O6hTT+c+J*-{I3*P3iP)UsD$epDGCxRz~6AC?=!%FnPQZf@C)Z#DmaEB>E1E
zM@%m&5tlWKlP+H;J_yoQ!`O}csNyDu5NIFk;t&Cd)e!t51pJxa6j1Op+#c#=e-)@Z
zMw+DlItuiDb6}e8=V^B)$B>DSrZ1Q|S!fcz4|WdWCDd4yXKjVIx$$lnyeP$5R+=a_
z%(Kuck_D0q<bJ|iwE*y0ew&DNhRs3VMuU9(lS1urB*|}ci898cTLyRiN|!}SV3&(`
zDSLY-F;;YRH`52Y?N>VKZ(0hf$QsLZ$~|hbre{4&2unZ)xpW%KXs0}p9}y%+LA?7D
z3Yi5Rpx=Eriu#pklivUyo|_T+B8%E&g1w>6h2b7-tL53te2#upxi}}D*PzM48%FT6
zmf{j$$Xt)!)3oFepJYmnQuEQp4S*2X_sNZ{u9D{%gSMNSC6-3!Yn(urUi`B#?ES&@
zBcMf#*&D<sY_9`8l*-BU%TaCZDHDAlO%l%`MNqV6uk=KuT3h#L3}Y;J*E3|J(WfZZ
z9R3favHm&@6wLtjC0Ak`!>D`b8#v$4q_KWGd0#kb(S$>Ta`YQQRPqOe%!k(bSw&tY
z&#7uY>j8{I!_6Su(t3c79kvZLK+=@1_0TYkFtK*2Ij+8LzBbTbw{%82I^w-pV3lM#
z@Y~1gm^&C3hD;FEkjcii!(c)2n4k>hUB|_Nf&xj>Srfvst^nWg=+#*S4}jkqXrntU
zN(*Q7B2U#0FTZ!jckbwY2^@!(480qK0~O-8_tMHFf(cdAJcu%1i6yYV`|*nqu6Jtg
zeEEWavQ0#T9b*g!cj$RbeFG+kItfn>b+-p~Bo5CQt3_Pdwk!aCt}d&-N%8?r^E>j@
z{`tF9UNE8VC2Rs}Gh@m`PBR0+0QsPLmjhD0M&P8Dd*kNTfu0ZTxx%qfcuGdJ;giA%
zhE91=xd5JlukT;J0GX{m)fDzPN|My9sEwIP`>Au*@HBMxKt!M&`*`rCi<8KFw1_6|
za;VB$sIH5QB9<Yk!XQ$q0~ir;)31litnb1~1*YK5Xu5wb;<6I2#EMI$9U6zox&fs(
zl*|>ND`B+RIMp2LUBU-jj~GJ7r~&A$Y{3r~DVC+_HS3G(9V2A#OT$Z;2x5ERG!?P}
zwYa?{9$J8()t=TQz-$kDZ!sqKt~*u&_F<acRY>d&QZ-LHPTh{GQm!3AhRNU}%vVE9
zYVyt)Poe$Tk%E%rNY%;f?4ATqKHH6)J>;<P<@sM=4a}s~p0Ih#ntWI0<W3@i_tubT
zYCwl>w`j1l+?h5t9-7r$OrcQ>_E$;;x-)P3_%eJ!&Z|8MpvIFha|?25RcK(~>Fd$_
z1f;$}(Fdpa%dUGdijCU`A@6kYJ<@D^l4&$cfAl}@Y!+rEcDNDL)Q@gaBVpGeZZYSD
z_>iEA6XKuek6+J$$YHo*Z+NN;Z9SIwopg5bvdmNbOa{uYSkK}F#Uhc;q5#FcNMOK9
z{l?gR2&uYv_Z%R?{%$5f2XZtmNm?tmUFwYH(a7JI{g!?=oJTg^RI^;~1c6*+Op5%7
zMDpVH6oVh)5=pIxt~9eLugv%PEe>8fXDWOV4JB-|T^q8>goY2_+mWv3so7CdD##=-
z9IWSpA!&+9ZK8~E6<UuuC@9TF&n<=#7y@7jMkplagX|#<bpCqBGn^OkMYW<L-5lVn
zn;sV|i8t9Y4XYI)rJ{fK9ayp*!%m*k(5${L1eUZ;AFOA$`h&&uWV3otKN#qS38bnf
zT(~(QI63|Z354>k$Xtu_Q`ra7GxN2uqwU&0`mVUzxB462de|vf%_rYqNwIxq1=RQ1
zLm=sAu>q0xz69D6_B66(g83yipZ-a?XCbmT?p*9~nI{SU`sG+FV8_-H`bq1iDVM6H
z;Q@kbtbu-0b$n4TfgN(TVz#IbdwH|r`(tJ19<yFGh4w-Fv<W$-?>2CorcaJb_u9k4
zMPG;vVIljmtHSyzZl<{`yx8{VdN+}n84P6yU>iwh!!ilM_TpPoOFI3$<-VkD-mBV^
z_I=(85*3avyqlKPTQ_#o0F<PkuahSyeKbHvg8M7>Mx3nSdbTv41$!TEkK}$e>Voca
zEp5y&Al~1cF+i?uS}@<=3*;y?A3Ks)lBN%Ccfc6T^N<DB<^*L0@{jk<!U2Ja&W(I>
z+xH!(-TGY*%BFe<MwOW>nF%?@0~SYoI}Cuz!yCj6n<V0CYipaf;q90o{9MH(o`s&(
zCgLT>N&fy3(7w8GA3;9tYr|?c6ZIw}Q8NIrCYN>x`&F>kn|0h9vu&(D9r^UA&^icR
ze1+-CjMDWGZsd+eMfGsN3ot3(#0&s~TaLgXX_S3Z`L<s6ix3>eeG~#l?fPYk1a!gw
z)$99vIh4fg?@lJTjzb9`mDTX(FmYE$PIAZpEJYjfY&z;qOrK_eXTv8V91}FkTnz1w
z>QtREE(zpJ8iH#uCBPQ5a(_fcML*#5-}6^YZySL(NTCHFl+JL<*6SMB^k8<E8F6s|
zd=^CReES`D5KpGvn63idBGwA%9dcsZn*c8ORjHS{&t7=!!$|(-qa+ZR#+`^V4!zJk
z2wjbgtncdiY^uP-iI`M?$bj`<U-(ClSVFx`^6&8>L#RZ`;CkH0j}NTJGz8v`bcns{
zk3EWGG_E4SX$0&Gkk)p?+Tp84RPVgVRl{Hw4_wS@JCbbzk&ohvWsquDReRc!)fE~C
z$rPSx{vaha&JWiYO&k1Umd?rZzmI6Z8pgyQ8z%v8nT+vc?1_8VFLslnLQ(Z^M4zr%
zC|mSOuuHL}fmRj6JXWXVAr_nmKTYR4Wp5z%A#TdNYr8`*e9VFDYc1D<+?>aahn>WX
z8rKP(aOtO?o7VrF{Q{8K05PUqKmi-aylm%sNzFyXpqSrofT5Hp{%Eg`RhXUp<ISOl
zA?+|%cg*W9)vnFYMs2EgExKV0o}FSZ&W7xUe5(2wzJ70vzEEAeYV^Y;>X?I^Qu@PK
z+HgL#w-wg(K$>#m<hxV=*&+U4!$EF4fo~|Qx07CmF<?DJ0!vrBUFo>JvYsx=+`;0X
zx-}M{H?w-u?;-G#(r*veRFcck(D2IWl96QC{CigOgFr(Yk466Wqs>|?bCWR+38BJp
zse>YH_gn_$H&6I4z4zK99wMIw{&xbXu3GJPgRiukem)e$0VDk_t+5IrU2q%Vj8gsh
z)PTDbWT}oDkG=RVgn~%q{JIGOftsqW@Y{o9@K7B&T!bhGQ3_>&T%1C|-E#_?8M85v
zgr5wAxlk(r=p(;m2g1cA3@XYy9^yQBfAq^o2Y~ik(0(_Re_>{m>`Ue=J8PN38YAN8
z!e}ComG!2K_%-UVON8^|MwCRGh1z1H$q})fTrVZmrGvi_022x_*T>ufs$EXCmReXS
zsY>Vh+l~U@xMN?r^qW>|b?F(B#Zpu8vDdH^IW6Am0e+jOQ7-aO-U6m^!{2CCc|iDT
zce`8|0~`WO{h{Rc<pqXhWER-i?JY?Eu`Vn&8rZl-NR$qEwLEeO7e3v+eDvA6KXfro
zgoXsC`^JY_&!>93eX0$s-k~>r_DSYV*SnH|7!CR5?j$`Z`Ce>w;z`Wj=eUQsx;8Tl
zXRQta@IeP1miIbe@$l&#Do!$yjS2z`z^Fi?q`}I)hH4|qkUA(R>wJ|cTdaEA&diVQ
zO-3;=!Hd8$`T64RHv1$x;Z%RoBSuFi?%TmjfGY#*L;XO&GI?M6V|qD;#Qe-~)w+oD
z%K-{@ylxgLd-G60q)U9=kaviyovL>ztK+^1jFj^3+SJIz4+XW22d@@93j7M3vlkj=
z`rR?YLJn<fGX}nZkdXFC-)a_m2I}bkg$sukFDCK9MTvH(pLKA5W0QgV1l2~cE|Ob-
z`k50q)XxTFx#B!{GJzub<mzPc>(sM_?n_Cng^Ve<PMbMW9qDiL?BD}pg*6f(ftj8>
ze(bv<$HomK;$!|++D`TfE?|nN=3e|%6iSLS2psGeYa8okA+Z@&Z3Oo8%b|)yO(cJ?
z*=kURNrYjBbf&RHoWe|7xOZmzk92EXvB<lH6xy$<Q*Cr6ia4~LN=iy77Wm6`qVQrO
z^Q^s(G9VNlrN5#K_w&(`Ya&ByY}U$u#EBHemn~SfYCqtLw|sN3VP-g(cq;is+7^D^
z4TJ)?nZ1e}yO*XJqAeGTi^j%KqMO@}tZgPD1nWRuMoz}gLLGl{(I~KfXF#*oy!a`$
z{3CTcZZFd{P~?K9#W@F{BLMc_?d}d*HP1ZxLaq9IY74%j1%m~M9SrN~00Tz2s`Ypt
z5Dk8y)#Xq`v-F*G@s-HXLj4XM!z3Pfu>GDM9i*u@g{NwLb`8H|Et3ourxbZS;qvYq
zr<(50lxDtgHQO?uTBz5a_xO7YKa;`QT$9n#z?%w{B&M|OMbz`5EoaO1Z-zhjR$w6V
zxW{@skI~Y|@FarpW7l4a2m|{OdxJyt)6gOqR7kQ51AL}kh&PBpAxuo6-vfK>^hYFh
z84>&EZ`E!tVSC{rfT5j4NxQ5@o!9-mgHh;q|3C!wGdjUG^O=TRdAz~{X@Y9cGv4H}
z$AyeRGV+`Hdx5P+n6V66GEjH>_;GuSy6WrmDOj9JBzFrmW(?&$A+>Cr4Z=_HO|3RP
zXt6ha5eP8=FDkRBV+_seijMX;%&p}T3cX=%JI#<(d~=H?yKpY5%Qp*QAcp{y6sI`b
zQG%OGIctu`2dhJI*kVUultggD9$CJl=yp_soe?=RwW6m4JtWlRGhsaB^?>b`CY|RX
zPdhs4QBS)r{Czu$coIr@_+Rqg_LQB>8l2-MJ~zf5%uwan8x^n)l6M;mvab^6Zfv_5
z76;JzrP*lO$ML`_P*spoMVJBD(9qK+#1aI{s{fYJjvg$+XR%i3K7nhfpBC5FCtucn
zX@1_;bmiLa%=QY9h}sro9^uwK&Cve$?v+y_aGl@hDXIjlVHnKd+kSw()_Y|CX-!@|
zlG%;>RQ8&NnIw>9hF|*sEKc6k;h)h2Q2hj~SsM+PN#!TK=`_?hw&>T7E3C)XNgPhn
z={D3Aov|VBAGg?U-MX@j=ca0EZXr7HK_wZNUB0}%8E8~lQ*W4j=`}Fo7ctbRtv;V#
z6ZY6xdj8#C&v(9t1WWokk*-A=U0jPNh_7frs?~j2tiE7|c^cU7PD-4|mPpJ_>gn33
zRUFyocEUXPc+#AsiQVgULOvw{m8@j1DSK=zGymxipX2G(RcAHbK>i9`ct_0Ndd_~P
zH;*6rw$IG(fcW7!WAYh0J%evYBt((}wTez<1Rh;9_wn`bO_i0LiYiqBJLfUlt^PQ(
l_k146L8E8@LLeyMzr8}i=GKktKie_@fv2mV%Q~loCIEN&Oql=x

literal 60826
zcmdqJX*iT^{69>JB$1LNsVrqJB0EV4iDbqYTaAPfvW$JHq(Ugmh-}%-LL*}tTMJ2J
zXNbYv$Tngy#xl0&;=b#?f5-ECUOcb<$MN?<W6tY3&+q#AF6Vg`X?D|q`@o3<EG#VC
zhS#r|v#{&~v#{)O+|LetBmb}{lZE9Gi{UjL3;%&%wcLpo<LM>UZmFi$*G?N9b!a+$
z=CBFJ8NONnfjeTKcr0Grx#%L%;KOe5^5B`!Yl@)~4ZM1K2BJ4r^t}z`tl|&G-n*yg
zpdpu_$CrMlYEZCEc;cDr81ze;aogSdZz?@DQ7iTSGqbgRv#4TfadBV<K9mau5Ay@f
z4z!0-wuSZrB>ms|W2Sskec?^L`u)K-;rE;;E028LA~tCu<}`*o|FF#VD0lE#W{9|$
zt~zlJdOTJw@TZ7Vi>d=B4gUL?M<>D|ZfU_IGtplhV%1Mn?dWy)$IO)%9g`$<$|^M(
zecP!nXdlh}_t2vgk0EY1s?_fPn$pf#{<J(3@SN@USPx4B++m`(U|aE|`ny?eie|_n
ze0co#C<}-kH}Jy?<j6W4K;>MSzsd1?r10zu($_X&>tZg7e89%tpHjaEuJG$%E{D#A
z&P4}Qsm(ogsBcw2^?NMqz-jPXgW{W7vro5=`)&NF|I3!=_gIH1FS<3s;}_&ed1h!=
zy~w3HH{&@|%J*uK-%n&+1)h+!Y<ek74}N5`@Aub*2OHq@@yD6Nd>Ngp3^OrHg9XXo
zV=U*7G{C)yq{BG|8)sK8JEKReF_)4}1QoDP9OJmCx(6>rFMoO?qL~4K)kSvt&|Tk~
zptBv@4O8yhex|@2<fOe*65rPnS110l%t!egxPd`0#Im07Hu|d<UOoAuF5$aPaXux}
zI7m47<z>C~JD8YL$phuf&ICMY_!Q@)Zq>=QaZ=*+GII5;vmo7}-0uh_?H~F&mQI74
z4T|5aJwGh^oOXy=ZiZo(09T`H1~H3Xr_Ef+#Rtl<nuReC+rzRe3saP7&h8XQjP6ws
zjB(}RH3E70ESUA5sd&-X)}}^3Y+roP@V=f4b-|Lu7;`hqj%Y6RG2gBAqKWlBa&N{%
z8*;c0Zs3%KM65keVBYjk=QSa|eB&c%9mPz$Oq$yT82@j{;f!SH$@cTwqE%{nQ64z2
zMk>;oDLzamhYuIeqWTG!&d-(Bb*J1cp&f{-{(v6Om%dh=-M8UbgqSe$s7>{)xD-=<
z*V;_RD8Y!;S!8f-nTn+K#=G&1HlnCGb>l4+^)JWz4!3%HEUk{)9AaO%TA2v3o!Ojy
z5Of&*n}!#lQ6dR>S2jMd8?|&y+7g4(nySmPlo|NTR655I6M3q=)zNin5H*E+BfJ#V
zuIy#?irC_OO0(jNm4W5MYY?pjqF$BEcSqBQ*D4P*-!^Pc&Ox-iEN`^8i-(YWR`kgv
zVXQ~}2m4tadt9K?(%_{|UthiLK5r}bm{M?lcg+~($R#&P9K0)lP*M8=^qZ^(sRi$m
z0(GA9Sm({RQnihx2kr3PZ=G%~)j&&7`|=}iRG>p`Bw0Ak@M`H(vK}DCS-sA&;;Dtp
z9)z~3HS6pqdhOc5+PeOLG%;}BxnIeVJ-)PspMPDChGYtN*5xH#?r`PnntKF-7fGqs
zNZ$`Ug0{6oUL*6eH}2^#7r_1Y_(u?NcX$7LE-D1Ko_Du$^f!|MT5e#B0^N<irM_9~
zHK1F~fa>*&E`Xc%89)P>Hx5R*#`x}Az^ahLVV$b7fikQ`NR**CUwi|6Fzc3wUej6k
z5aTDKsrho6ovz;Iv5Y6qsr;N|WpdE4>}}p;?67CWtR801KVmoyHssDj75dCe;p+wk
z#QYwwG@?kyOo&M5f#Roba2}>_YjUo}l#H%|SBTl5`DH`Q*9EV#mz4}`>w6xTCeI+n
z81|BZ=>~WM^QvM|BT7O3{@N_-9|O!1Xpky;XThHoMXLIAIHl127j}5Y5C-Zhkv=2b
zS!S!_i<9a}w^M>Bvm4yYh37$C+r)4KCqCGhaO5?@O}}g1FjBDt>)-L?rAR@@=*KlS
zccG}S@K+CmdH-Wy=DI~vQisv;VSJCP)7Sa}y2X<Ayg-{u$)n~Nm$PnLzB0j3afH4&
zBS=MSCjRInq<2TZepraHd2CX7h<jP4=OCY0@?l=rC!*mYf`2UJk&zDOEXegdNKYIF
z!fTS4UGOLF(Wm@WyWiCK%w)L7<<Bf3C(HM8Kluei=q>p_R!-;a0Bl4IN9DSn@Ya~G
z_uM-SIFIkUTU#)EjR`OFNH`LkBIYvi7uY=-?02f+H`rbgKMj73Qc6U9Za}fS4ZP)Z
zeNB*=B3}iW&tFkY$Nx~AE>d8f$(a<hB6TtDDAptKswxWpNJJ~`Kxrfh>uO(C!{}UE
z(T@{9ZvvBu1hrPn4jg)W-}*cADYrTP+!Q}<pxrWO(%n$yYq@q@@~Sn2ySJ*-;otT1
zcGnM$HXNO8;WfO5?@IKyhz8Y<k7qlpxgt<5;(X$#{ZzW~>g~o~>kcnP8CUFcHYmeX
z4Xa7$wO4;elzz}Sf)aW%3e9uPUVAw=g}X*uc2@T_Aa_DxA-*k&nPRx7Wx4b5i4HYV
z(6*MBVbMyRV@@@*a*bjhq5l}-qltaED2qSg;E}?P@PET1OV$lu^z}ckyAuzj%>RHK
z%lEziM_$c!gb=q5i&{7Hw!iO1hUuYxJJoN9`TzVkF;_HsF45=U!kU_Ki*nwl3F~-c
zbr09y&p+DgP9i=C;+<O?{P}Q2U?3^M)Y-bEAU?a#4XUi`Shvs=I~aeNvQ#u?sWcT_
z{lu>MH=3}p@V`Hk{P4S^!?xDO(4^l_uhYpLrQY<$k=efVq~o=7H??~v)<;AI^4ltA
zo^zeJUnfLp-(Rie1N(9L{_4nIFYf3S|KTFBnPBtzwdk|j%^0N*4vi;WYECj+OXusf
z*UkK=4NTYi!d7SIR_5h@lg;w2E!*bvEz#!@7s6J|pE}U*o5~$oQ~5J|&%sn~B*!m!
zZ`Jk7^PYdcK5t?vcX!>e>FM+BW$zbyUgtO7j=KfR{2A}EN-$oHKo7@Rh}HIowAyGL
z`!h7{gRsBMV5GmjpnpEzj26zNe$Jz{_QL(ef0ME6XEtoxC34T+a<8Amn0Z9n5Z3Pf
zc|R9G-#`A&vSV|6f4qX_N<dlI%9bj5rQS;k_WJan7|o(kdO3N%Xq~_tz4s4{v%EUo
zAf@vMR#_4`VM#qu4BRT6drOrnLw|#~*4^IrzNK;se@mV&^Wu+?mDq7c2l}hlM(01b
zHCu<<Em+Em!IeQOC3{E9&&;b19G!In+r{Qn((k4i_Gc1LdSukz`b~e<*VEw0On5Tu
zR2*bT@F4dsNGv4%m`U{|W(B%IK|rs&(kg*CVsmIhp*e-)52+WgoCb5k@Y{)^U|LLm
zdIs^GO?e{Ze$eL`KmC%DhZ(wmxH!oB0;JFZL%4TH-ynNgWfC*8EZLdj`xRRsXIW}d
zx95Bfjoc5#zPOgeH9u47Ye08NseUr-zCz4y3arzdN=m5Cas0J^)H=@BproHrCWAlj
zhRAQ00xPv|ISXDj2g#bAYrJ7?glUVkv!Bs;4*Bi<$4?UqOoi*W*F4&F&&NOJLl1R&
zqb^B(Dm<1J$5H!a0c-PBuiNF6;kWS4?MZ`nKmGPuuE54Al(XvdbeDz!XU(9r>lk0X
z_WDzr1q_cDNXba`MyqFdxuH|C9&TlFniXv+a%f2H`BeA36@QbKvb+ZB2@k71|4PX0
zY5h$9(;H&pr@^EHJ#Gw_?1!)EHb6GeY-R|mNGd>z-a;QMcI)((0B3sU3-O;kjP_9J
zX73ENZI=8bZ8gJ_K{|n@2>VN+A^2mcBejmR^w@~%7GGMxY{lM%PmfOg30~nGuq24D
zd!0(nd+$<;cs<1fciIjkx0pW@m0>@wF&Rxt=~S#}z%(@!;-N}7wR3khrE4e2;iJV2
zzI1r4TL0Ud?e$bQ%VRjH6saNtDQFnlX!ldogLoq<m%7K}-yrkx%43K)l3b!r%(Ydr
z#!5tz<U9z)Sstxs_Lza1>YTnoh(L&|Cme>?ysNpTRo;ZLZ;3?~r55v{IC7@H^P|z(
zF6H|Sz8}CKCK%RV2k0}k(@El=UV}^I{&>)%$9r%_&$1vxN0*Xfj#;}aHBc{gdUIsE
z-I4_xwi-b(sHKnZ{(7<D<9+eIwJ`}2!}cGM135G=ADW)y0&c(<Fm4Z}7H#sQxw4y1
zK!_z_1nKjpn6_9u%A0v+=@cW#0oiZ&6{r6nOP!_EhP5qkme|BV#B_BqMrkNgK|}rp
z^*)Y9ywSQe*lnw7*auY|r~*vn{?d+i!+&VmHLOGW#gJopvM1)>bd~Lz-6>6ky#VZW
zPYz^=Z^@_y@#*m0Kx4(BSm%uCPK{Leg6-i$QUd79Lqr|g9lJnVwtI#)r=noFk)TL(
z1cP#WRHa|xSU?<^sM7ndXjlQ!P^~c3Dz;9#b^4?dZ;y2+Jt`MPeHTlokaf1<80z-(
zG{!Gt-nl8^7Na;P{qDR-(%k7#GtB9`)xLqm2N%X5qJKb$eLs*`;UQS|S;=;3Hzgat
zw;%r0XOA>qfXu(OwF*2J@VyBpb{x_=@f$H%ns*Sx{l5^p0|tLW=}w&e52%?*40RX8
zQnoiLCeIxG&ts>hM`&90tSQ(3&B9n5dAG`)1QlMNU)k(`{#me~evG54qES&x@Xy+k
zPq+J&gs<y)O(_#Um&<?Atrg$%AGlQ;X(L;Ip)hKqY;y7N4r!46<n2ERz^ljeewmre
z>zN@;%J6FERWXMn6XP_y6R{`df6ZoDVtf}O|E%-vYobH!DI9I86YHTJ*ktf3#w7kr
z*m{*&813*E>#gHUMkGe?(Laxub|Z<sS(e2SG&S68T=a!N)71{Q$!DfReMugj$IneH
z*SuHR4m5wp46Y8XJdMz*)p|Oqz7a{ksdXoe&QkOz^qL*URxSNp1V6l1K7MKI$7}1)
zL-x)qmqMtkpslhPMN0FzGOX!a(-NNkwPiWsq#!p(xoWSf7ZuvSDY>%!>P~t>^u3=0
z=jliCXCLNA63sG8&<(-1y1{j~YKC@&!TxNSPkUg~$3Q@V@%6j&IvDH{Kv*5*U5d@F
z?rTQtcvKKn+1{JZ?E|gz2AWn05QM`YK2TGz@wvRmwlin}MAKw?$*oK%q?aiFv+kpT
zPX1h<OU99V+v3#*;%eJ`861XHeV0zLAwImd`Vs=2!Ju9D*A@`cXXj2mbr>rSb7Kp=
zKdDcvm7#UYR^2!OTQ8U$I(abWEhphq>Fe(Of6sfxyNlmK0xUa2y{C;j0~R;r30yBo
z^?|ciUSh61T4BD+vh*SCX@EO6<=<*V5f<EEtR0+dcC?mz>(zglerhO_Sazl~E;?=2
zqlE4@bkc3|=1tLmC~h?b>cWqO#-2e&ir8F|kPfag#hPQi(;g?~f+zQ%GwjLjErjPy
zlpjwFPKShtT*ZKWA1s9q3g%Tm)<VYxWvWN^xNy=O@e&k~qZJoLl=m)sCVXg}Mbu%-
z(|^0{BZ)le^Y*-D`x=MFXLMwiEHQ0<%LePcsUycLz3|6mMGvE6{2rh@Z}4!`%BmZm
znWlaxz3Xrk{sU>c&x*4YbS_>x@2;u*13SW$1`o;gS~>nTm{mCp#{=z^VO-JPn7LmE
zy1dw(t$B}f^#_(zMEwqekIv{?npK^C=&G8}J*udhoRQ_X*E{kE$ua4nbisPf&#nz;
zJ6YYFjCM~uS_uRZ(WWOjc?;dE+o{2!aHHhd(|DLr4r53VD_w+mkfzZiZ+&bj>MxT{
zMepx}eQh?qduwfp%6i*08E?Vc*&zWM1DX7v4!a~vfSdHzv&)=R>@Lq19&GyhCb9I8
z-{x3a{g_^7(D&g?_~8NY*Y%H?VUGcENv^++$jGY9fV-y9t%=m|PTwS^);vYXTLII(
z+%9W!Q9U&*fqp6_?P8dL;<m4oy?`pw1O{6=Wo`M@k9fnWs@wRN<?{-UoV2DnlcdVc
zf4WkS*bAf!Z7_4*6ER1;<AvgdpNFqLE)f$Kw>IXK;UsNx63t{SBFna-NI~JF14&jX
zX?IgyI&mf^SZ*}Q-<)7BJ_J3y_LJGqpNLdT*I_y@2D<r1I$qb;N?2S;+<W5)dTt$S
zvG%mAH#+H%9cjF^Z@k8D<2v$!Bre9gw*B$8U;3DvE6{i|S*i6l-bZhLxmE1qWkIXg
zl%&OI>M*%ERzBpkkHtP6pQ^s2+ftqzqV@R=1FuIBer`S-y(008e!z(kE}1!!(&m?p
z>^r=<*;Vd+`?rsq09s9fq#r-ZwXZ%JCzg33%~x;c2ha*L=lYP5McY3KeMZenUFujI
zKEON&b_$y5=d~yxm))EAlm%I>IWZd^6kK*8)b*<6x7w3OiCLOD_Wd>5<0^9dqxP*l
z{_7iy>ALZQ=kjtB9xH(@3WIJ~Cmf+yRpNQh%FVQUCVWxRe6iE$PlreRRL&!x%{tbF
z4T3w347lsq!0aIrrM1e3{7b}>&b;rd2%x>*?38EhE3~KKPvQn9YMTaW$iDD8WxG-L
z!3Xqm)fZMx8E-b-dHzHI-p(C&A3By1RMXdE>swJVC^@Wnsn*4}0i!$QW4n-tyzkDX
zC`%`0K_2{?ZNmLHx#VVBFl+8NVJ^Eh`s!ye(JF&rS&etbYgob!VO0u#*a}T3xS~Rs
zxn5;XZ+kQQW?Hxjq~n?FBWt>c{4;qg9Xz^PGq-8tCKx*NGw>MtdCs8VQ7)I+KH_j4
z^9E;>;|P@YhDxiHosu3NAO`c8@I>VW;}=}tGifomI@c+i)n6m;hiO*?(auDEM+_4r
zlGl`#2gjK37Qg82l^~5TPTgUdT5~n!N_W)@f4g<ZPoI6`oO?L=D)Q`Yq%T_@GYS^t
zG_2sNSD*xKreygTtGdNWJFkm^@#%Fo2=9w(`g|r<&_jg90PpWUb04kTEj=tx8KJ~U
z;b{Q&bkIGm+2oA-WA$`OZ=@bO>gQ>C0)tUMt_A~Hy?#IEspDxp7AZ;gHU7Tt64arM
z8vy04_;xK<VHLW+pQ>z9EN(+r$EllZ0S&#S$E`+@ps<gX<%zU?6~FWbCmGqNxAMPk
zyrdz1N7*Y0-TX)W$U}**WOY1<n)SvWX(|Z4$ripDKkJq%ESQ{znC0rSjwTQbp9RN1
zlq4xx1&B^1y*7kcZky-eOk?vq7i|ttegC2;k9P3Bcz4_O3_<!!9nI*+eLrjPeH;DS
zXcC+Fu%-2p;imB#<$}GNN6_@zcBoRykzB3-kqZ7o?K`Q}aV~7{7>TRv$$aQJ$~|{M
zitNmh{QjvMAH<n5b>qS8UCaCaEA6~}Fmti1A$O;G?S|6tZWbTaIC}E6Me&j(sN$i;
z!)rdE51>r3XsADG{MT0E*!+zS%i^l5v*QQ)Xy3nN@O2Yp!)yn8zgV$rc~!es<H5E?
zm-AlE76XofeaWbvd1!6o-tzE<-#(HHj!^wQb2EtOAGS{ichq*Wb|Umt*ERZJRv3&_
zCw+)L&)B<cU!I55s_Zc3{22YoZ>V<mB0TwZ7PM$Ss>9$&fJP(O8$Zi)xu^FmPpSI-
zoC66W?=HeUxZ{$bVMcO>-`4QgLe^${FAYORm^J|_1r23}Fj5JBRr$5SV~>kh2So0b
z(5L5uG^0r-ju?t<6DrF`k~O(iXB<Y_)R;vtt_MVa_|-3%@5kX!&-3X$HkP-w<q}43
z*70;5!wbUBE<gN!x%K6mMnTf0`4z!GlFaqlN8;b>-ZzdBy;mLH3F#x3f#W<OeVesx
zK7&2xeI-rQ??sAL$w`U<Qwd_=3ihOm>%)J^6r`DR+3Gk%le{QzSJ;!HNs+^pdlvkZ
zFY3g>;^jnI)MH-shxG-!L&gvK)I0`U1Y<dVr;}OD(+5z}`v(cn;+)c&ggd^%tqzqz
zK&~p>hm?w1)@&qy`NkCs;0U7U=ML3=c!}{uhC^cP{g5jY%q%Y)b=$34>W%$O;vh(x
zeoH<x<=t8EPyj`WUYoW&l<zQ#WckJ%iukV%s0a4=1-!k~cEs|)M=W=0-q9;z4JhgF
zy@{$N<k=83y+-<tvW344`V83imQsO8n59t1q*)5>@zx8H(-Y=V^mv_e_p&ILyXx~G
z={J-iJ3khgmHdw_2Z<@^^L9K>9v?=N3aw8*m#!Q7w011<4bLCZ0+0ZRHsQ(W<2y$0
z)ShuXsSCHP3Lm^DDS2nKgbzo^5^4G<e2<8gB#&s+Yku((YZ3DYtF?o4F$5xn6jzT{
z_Xh<<x(w;Wb~R9$p&0Lrjc`jdJK>Qbo$UtH`l;Jka=F5U8>5#ttnx5owDcemid?J^
z+K)pa^T1q;D@k?R6M^L6X^bvKGU4{bpYE=rs;v%V-(%@DBa)O)<1_LBlf`e)I75j%
zZm~<3&X=GGaa0H)yw4{|zQkI)I|)2sC!{iI_Db%HzG^ptY|o9O8UcCWul5ONtH29B
zYV8!kdje(dwtb2?g6f!jkunZdkBtm=8>@UtYc*;_{ouFg-7_G(_a;rZq9=kp5NQ3(
zu}aoPAfSZ%DTMn8tY535fzb1ramDA?Dbv+KTJ)MwH4R(#_UykY7ZCaDPFIRwpHujC
zHelj_XxLMP-^0Q(IcD*EQQ23Nw2zqA2cNfniW2u29@Q&MeWw(^e3_<M)NHQ{_8BB;
z@8FSpt|=-*WRVK|@X<*n;mllUnXnEncexQBWTx>wB>tj3e=b+^r=#dCW&%<)Wh>B3
z7&kC3>*Qt@*u&Htroh}<COyJlVJ)6YPx0&x;pjv~Kw_#T$D&4UfzTf<t3!BsGthRu
zTzx#KnKEgcrvFc1PfaM!V!}YOtAofpZ=cj*nPL-zI%tc_9|iQ{1A5`0CxuNxwtE_q
zk~a^d;kD%yYh>>HlPt(txOR`ZySJGPb`)-3&S3zxg%2djcia5D;oV_vsnmdi{H!_V
zce3$@hoI+KxUShC6F(FLv{dDP$>FeZ9F6fex9!J-$$>}FZo{Du;+84PI<(ieI+WMb
z<n@IrLbo*%SuZvvE#Sn_s4V{LgYY@nP$@S@&Wgi8kfNa?*cjtJuXTH@#$m$P6n`iE
zB)#_iCvr)%B<*!AXH&;;IP*~IsSj9p&IHxY@|!;s|7luvX!z{IPj^Ylk9<GAX)oI#
zhVJ>?BP^z`AXjwnQA56T|ME4Wzl6%!g+uHHP{+C1rpvBEHfPe529Uik$tAPole6LE
z)P;u~e(%%ZkszGblysJxx^G~KA-EC0_W@T_HB2OG3km%i3#2?i4SdQYWNtr=Bdxwj
zx)rFYFSDHi>lr-E6}w_C#!A_b5(PKba?bP%jo)c;RS#c6rf&s}#W+)x1IQU*feI)L
zVfA^-WJ#-Fy|%q=`3-GfkXv0vtS?PPJfyrgfabD&Y0Im{*M01NFo)(Z1lyIcPmdaw
zBFrPl3mXTwp00_PtA&etJ@nA7u)?;9#U0w07lA65BxY&DTgwX?yhfo1z_&36I9u7o
zmknjFcZ;Rjk<%2mC$cKZ{(hgmEaXNXepXo43j?+zfQG{Zb|VaXr>|Q~fAW`3+)06>
z(KGN@JtunOwtA(CI#TbZNE_EEAKJShn;rwm2!A=|2+~%*Da0UhlX7H9)}w<OaxRaA
zW>_~B)9qF~PJzbOfA8r&<Bd-px;4@3EF6Ci?s6_tsyP?zNS)KfzI43qbsYxfGL|(~
z_-1slC1&}qPEvW5EVP&49OS1qL#n&}qYR1DFhL`|`Bcd{jzxMC@mU_VMmb;B$cgdo
zTxl-GvweIX>SDU$e+>|SWX4XZ6h;ikItQf7(~2Y|iEmEU^85<HNiv1V3vWhc3a~F7
z#@hN`FNV@u=IdGmH=0ywpQ4|Pb_qyK9<p5XCLP`!!ZgmeP0?^#fh93g-T`CTWA*aT
z;n;(;TRG}ulOE>ZDPK1+&Z>U;G_;Z=O;mR5*yJVZT$pPlqp7weIA66}F4AfucPhv^
zWGMjhN%D99kma->DOWhz6Y9!Ic>87Ngv8%JtuGO*VO0%2?p9BoR37~PmZhVm5^*KL
z$hq)srFD+C)^qMZBdLNU76u2Z%iC7RBL>9X^7Bw-dAjbu6Lv_Oii5uJ^`A&QCC2&Z
ztt^+0!X-GCaN#_%$YZ=z{JPwcKVvK`s!(s2cE_X7|8#)=Gxq=cW7etTNyb5Pw!r>q
z-do<Q`_DXmrSm;|%5VCY&DVw7Ay=Ho10V5TrK)**O}9Am705jLq$~2#vFgEhM<=;z
zZ`D`E*MV1fuU=2TAGSnB=*rPwV>jK+<h9k1WbXjc<O=_|!&kq(`u=WeJ;-=x8(nbd
zG~1&S7sZpUy#iFHbydB7ew)utFg>X4Gl!YaCTbs+v#wLDac6k#kivVFU1mr#^H2#y
zL%YUjq;ZXs*R6h&r|G1o#N5ivh>cyVqnlj9T9ti#c_BY_!sgIdTb{D=LtJDE0``OP
z`orf&t_ugZe=$v;S5TG$fEmNz2qD9yYzRN&gXL7Vbw_?#IXyjc?xk@&mKjPptd#%u
zTM<uI*pz!?ZPl-ZebjxKtIqyS1oG!r>&$}{^@}#E%#6(E_3M+$yTt7;B5o{MYID|a
z)*5^fawo`LuwlIIt$x!J@iV?qN#dkS3aU8AItOVIF{VThr}5C3-xufCutJ}ex5z7>
zE0(v!4sO@m140)(t6I68_pq<MPDqO}H9Im%xWH9l;ucrUTI4;p2U@x(v8imT>GlX4
zVsLfrv#DL}>ENI0JkRR;SGYpcj_fM!OuB85Juw=Le}E8oH8v)0zaU(@Tzv;L(^Kp2
z+SA74_msjMKs}_))n79L)WxQ++??S*CB25ketCwkne~5H+gbHmL5)SS(3d*aX&X8J
z2IuC1mL~aCZ0fC6)Nk`^f8^X%^cSPv>ORWhIuE9z{rh6)&tSC=IeeUJV;!CoJsWzL
zWz9Ly<gSU$=u%eA{Re`E8JV$nNULh-%C-GwFXvPSU50|5;SUk}@&m_P(>FRK03Gi?
zW5Unq@Y?6<>PqxD+y7(A`9_4(gZgvn7tc^Mk5*mTf99uwbsc|(-`q=WwI>Kui?b|Q
z)3<a+Kkv^t;X{q+3vG#m?^;XO(i0Hd2deVoEd$}aUNxccVb-)0uklqO8_KgYg||c(
z!_!YPCo@Hl0NOh`ey&}UuWqI6_SVp0jFf2eY0HkpGX0?~x(GY}{PriV_C?Xuzy0C-
z3F|v+F`8?qY}YbuzdSFBXj@_@NH|B!MbVWklweC+nqd(dr=Rl1zxlGg2wk13a6i=a
z@|5EfguR@1$AgXscnd!&+r_|^sS1(c#kU&||K?fj4B0-Q*zD9D$jrs0cB=a;*C%~=
zQ@|Lx{I*u*pRxju*wT6BnNxe(7DoYt3iT0EWFvgZ5E=6BiahsJJJ^#;8@a2I{mmCY
zlK7)1MFa;?`0>YQLQS%c>5r5Z&5q332a6a2;>*qMMXz9LmmgXvoO>ClUy(hWbt@&4
zs8ieDt`@`|e*5sQ^vv(iksn&VQ@k?sqE}XTevg;?+#VIm=R*1y;k8?tuh{@iG1V(c
z^CQ^pW6dNtZkvRYsc({e{cQaPwwG7xN1w~@*vI}e{6DM7TW3#tFC9-nlb?6&`?<#z
z<ip4gSVQXXX9dPd-_T*Tk|%>&-e{|MB_Yur7iGTpg`enMTuvo#zZChhJIT|fOD9$l
zqYFpqUWkTohue7`bA5|NB9Ys9v$dP~?V_xJ3N19HWXHadnmRo@_WM9qw#jqVDI%Z#
ze%->;OgaI5%j!{}BW%YTa%MMdRvc|M0B0$3A%Y5ISlFPSUg?X5Ohk8uEmHSwtcvfx
zn9D9}iIusMe#kiwS*BhV^1&%xXC(}vTB*H!d(3)!`k=EChbD*a;mt>ZAdgX=boJ;|
z)Za_?yq`dEJ0}_YrP~S&qGwZmK0kf9ol!sfB$M~*w?{wc$l#42A3KZi`bcNB<M0Pv
zLaPnU=jt{oq3e9w{(oz-=<bdR>@bI1g?-Pj(3aGyBp|OY-0o15p(rJAg#cu*@iShj
ztYfA*M5_q=CLFqvNr7Xrr!FyPMQY2EL<oOVa_~wqM5EsCBKojsX!3f6+k4`Z{yQL3
zjU|4$MPQ+W{>!sl#D_~$ufZM&R>GlYMz$ojz;3POr7s&F{}#i&N2RVb*OB#n(+}}1
zLezI0<k1KLFHh6`XYO?@0tQ}AAI&IyAb!O*N95rMfRg96-8lsx`J^H4`!6ogoCkt~
zhxgU+?11Dsz{=(9J@9#X<8f7#@edr+sdu8-xo>ek(ySl&9-+AtZ)7<yj`t*N`-xdv
zzMIX;NQozo-2DO_?&VPn{lRCxp60U{Iijt-4C$W8Z9ccC1-RPPn&2&_<6RH8ZY1TP
z`Ak|XbXx!^`&V`bAnL410AevDR3Icym!ea<_;R=~vnG&L+nEzM5C8`F2LhbO^5)rX
zp)-URHu4|)_6kF306Ki$4BCp~3Iv3Vc<t>J_7^3GK5Dci+#`A^=jxhA{o=&U&<?&Q
z5IqbZ@JRR@gF5;hJ4|_5*+$%8eGWS{I}4Ba;SHs66SW&7G=NnI&2i<yM0b_Byk4mu
zQFR7;EfCd0zx|m4!RvGy{TQC!UBrk{Uw$+Hu`b=_+m3yrZ>TbUZog=Yrg!?AnYJ`<
zKT>laB$v?ERJCD$c$j#APrbnHyKa&>xd-6-`q210kKkrtwJYN~nm9?y&}9A$YLRWe
zMex#>Bj@U)U!6&gv-OdL@#BmDwe+~6N#gk8Jr^H9j6-|IL#nsqx%_uHPu_`2J&$Hi
z_-iIdPH7Z!SR{|i0=7Pa7qJ{~%G^sT4pX`Q?N#(}^$Spg6rf*o(<+A{H#U;mIZ8Bk
ztfk1NW`_lG%QUlt+!^30Xv9N(94wr7+ce0J6uNO{XR8Po1=+DOR00sOxC~-Xx_BYH
zxJ$TtU4<(`T?7T@fHCUj9cxuT=WZ~qqxou^6~FNn*ofTG-(fT`d|h~=D?)&*_fr;6
zIDcFowi?!_X16(GVpF-Z_>31zr|QC;9xkCfX8k$JKY<Xo50-QqEM$hMt8%wpB?iqE
zsRZ?w82qitG><Uat?C!Sc>TV;-DMkw=WhI!oxUScCu*YKro7sPwrew=?kL!LG(^(g
z%=;>Zt?qDv4{e}U-7Xl2faqC;Gy`V<0O{q1erI)lAM2@9DF?}+Zvjz!?8)v-29xNi
zRD?L3hy4gb{D5`<;|VXIhTppI(DIp+QP*xSVLF#%u@~U|+QAc{az6k|?Fq>UT=E6P
zpfmgFPWEfPFHISt$N%%Dr+ekJn!2_}VQ2`cH>{_0rEcw{z^@(oX;p_V+p3?ddpr=X
zQ&PhG?5eGg;p@7m1ip|WpL5!@0&8cxG>~cU%?(R>rPj{TM*SA%bl4ni<KNu0h9P;R
zlhR3b=T)eMIa{}hS{oNiJU?meU;E4Il2<(^Men+a0&O&UHSP5?;-}3E{i+MRJDkO2
zAxrw7Ld0|B8{y{1GQDr=WEkZWO5AMm2XIE$(<gx}Z#3v_k78ilf)%<1NSq>Wy;`wc
zOTA+gIvBw@RtXWw1w6eunD**KXl7>1<V(eS5-+uvXQygZIBPk=b>0p?0ygDtGekmO
zfOgyv@a5gp7Db^;WKA^#OK%pm3v>dAdp3olfP#`<ok{5b(DvRNb}ovCJzO%7En{)c
z4^W-URa_v#$w?=}-Tp)V6rLty9}5xRi!<Uy2lrAh0{LZy_tGyZI{_b;6k8G1XfB}l
z39O@V&+F5gNU8Ve$)h3%+1EtOPS_p=*rG>*IBzEu%pheX182Vm(E03jF@T2y_MqV3
z>9I0(atPEo^Tb`&dph2@(hRUTz-e?P)I9Vi8{Bs$GG1ceNo)c0Nj1Y1Z?`xdSo8_D
zwysM;8ST+n>~DW&5O>nbf3`UTF#j_<e2XLaHhtsTI-^nkw(s?c8;dc<RsYQU0`%x5
zrb}p^-gf~YqU$M)VYxCSP+nekbT8aS|B%S3t>vwCz<+l3Ym<5mcVfgbf!D717LO1&
zegW$4?DxL?d^VnW74tbOew!6Rv;__mKUI7O0lBAYYlARU2GoNMmc+Xwk@#QJb89}W
z4b<Cl!)+02I}XMvs8F>NoWXbJ8>t~eb5{W>a$%q<8Vdc{q3NY0A1W}oFUj)IH|B3D
z?zJP($)Y<>4ZIB;e%YBDuK5DwNYUkqxG)&(U5Ox}HtGX4%w_=l-IeP<s^6vJH1OtL
zoSIl8^$u_dX8$e?f8z@vP+s(-9k6bI+eVWLN@_3L_-?I@04_V>y@s(Gd6s9)Q5GTf
z4>N#Tc5Mj|@s%CJf+4QIASw4@x!TnjJq<dj;gF4mH9nTzSpiaaRt4+@_{6&V+k0*E
zYs|>fU|f+{5nMG8C~5HOv}?Nr0|(1?tN|b$*cAs33+=@b+?(T{Xt=q#H2ZDW&wQ7r
zx1(h~;vBvnwcEaC037B3qzjPoFF`E3f0N9WiU@!(ekia??Yq<c%c}m=F2}&rf3v;w
z9t&Xg6UWfKXO*x@RME`M2k%JKauWKtcy}1vQ4=6&;J1rA4*uC^EkZ!zCO!N@DDI-I
z4I2F0%62K<Wfx$&t6gKItK>^l{YvuMuMJX|0j9SKq8ae{=|=PYfyi?c9Hmij^PSq#
zo<KqtdaeJL)p|ZalHPEc>q~0i|AiarPoI3w<1u_fogz@@@7=g~gU++eIfteMm;Kzz
zRGu6gNznFxcb}Z)P>67`F1@jxl98lGeuL0zp#BA%XP~!9pGczumTl?pMhoY8W?wZL
z73>D84c+*GJ7}i|7{UJ#$w#xpXucPhv^QRB2`YzP)!9F^`SA$1H27T2*wda(k=}t5
zTB|)P9JUzu{sn00fV_c-a4{srdUaf##uK(duh-e(HDtC;{mbhw&jmOaj>M_UQQ}EY
zQRBtZCI5?xFIqI9#9)#O=hm1585N7|)ApRT$-^5>&v?<vp<af+X6jeh*+xe5G}l~i
zx@#jk8mY{48Lg((^Hj$ki11YyD4?{UAnqE&yZNPHWZs@#^ZHwBzg2fo9!HHbGs$H9
zTu89rqC}432Vjh(p>2y>#8z_{=_e|;G(U)GpdFL0zn+5cEkaJZyQ;!S<;vK+_sGn0
z+4lNn@{`l;fe#Xp1&%HuFGvqMvn;y3wNb(E)atOZH6bIPbzY-(b-!!ne@q<*)y1Lu
zY}Z!OMe5$zH&My;y#}9Ut;)|*@WZ*Up@9U)z3~mGYrh09-5<AK|C+On|5<Llyf$O5
zr84tn#G(BGIu!yM4x4zX1+%)k@YR|o_bWQPixu@4HO6}`b<&P-@ua+$#k+m)33Pk!
z&141OWNMSq5obHiUcyr9vK6s6^zGi>%Wszwztv7fHLmgPDaX<@H(P#;Js<}9u1l{m
z33HUr?`NFrhZHykTB>DyGY_K|0>)$2KLZ$lN^1vA$$c0>#dm;5{>vHg35dkJXr-g*
zc<*yH^xW)YZ#|X3;=KcuOZd~XK#6{DEoR?>q+qfbSX|i6&c0UypItWHKFx%LsvqT6
zbSyQ6y*~j1Vbx8pyAQ1qKg+9z%{A^DDctPYg4Z(!6Ibf$uPYkuA<LJ|)^4EYHhfdF
zWW>SvnD`9eV21x}pNQN^Q_TWLLkzSPQk(BqUjH~Yt{1z=E^%kGw*-n@HeAOz!YN`m
zm9V+*zw=JnW9?ymNL!<uqF@msSC9R$cYBtR#sAxHA3=m!a45MsJ{JjI?7n+x5Iiy&
zE;#MWW9jE<sL`yF5K|11wM0p!$`$n%LUB|jJo{`3B#Bq4=zOztyKBdJ&4Od)#aBq7
zu2z92<Pnbq{6&0WL=k@ftf?f6dIn!XZ!6{dMTo1l<pVOMF}DzUdY!nq9UJ(-i<Hz0
zjopj8CIeHdO`^IaNJKc9rkMNRjAtxbeOL^Kq$8+BYigMP1x%m4f+Vdb+8{*xCGXys
zy)rb%@Pv_|_ly#mGp}D*5Dg4fEQeDpNQ)nQwktH&!UaChcrf921KfLTZHZuX3nse@
z>Q8umy?irS(Psvoig}5yl6oh(Rv2)@3ngA8jU0kVli@Ew_3U#<;Szpm$5&YzGDzfG
zeR1!Htx^o4xZWMu&Q(<dlTaz-7cfS}3Pt3Uw(o;?8K?~MhtLrJQO_nuQ3Y!8e+vZ9
zUO-HukU7XGJ|9nd%3lemNe+fxn8lX-3PRzgV5JecVk^>#j<p~~DZ2LgBt#f?E*q*5
z;%{M9uo>_!FD$VR>Wiu?!n>QehFAj|C(+hP2j;EY2?29?_A4$iZx!Fa!CK2EB*5p-
zg2%kaY62owdOAf7o&|{nU#tPb$e6ZwlkjsO{bFrIG45ZFc7HOxUYo|s{y)J3hHv92
zF-mRUo7wyYLzE9FIQFi0Kt3Ac<4yTu$`6f&mT6e~s>1MT%&hVfm!=<t))|!~wXfye
zBwqB^QmUMLpz>B-A|Kk5comcH6gc-hG1jz6vf!sRimIBl_x%c1Y^E24J`iUQtv&{%
zN8wSRA^+~}&C1D3jC+5bP5d9BGxY|B`uY7y9BOVG&JDMn#HY#7tz&K{T{KGvAzUoe
z&G0{D43OZnU=pc55kg`CfvbB6V?56w_}=%P*c(I0ukqv;q=86dyg6xMjqX}3naJww
z<|29hXwrcW`Z6RQsCBM8M3Ks9fl0}@Pkcj*>i@d^PV7Db!JvX_eimLUQ2*=o_#8*Z
zH=;h8l}c21wMs##V=`QAVs4{_pwc+hk1W#@gQ%VvYF81m%rKA5BB&e;V~n&~-?r9n
ztc`_WLxb-!m+*bZGH$!}=1%V<P00|Dg@{e}^x!Ms@C(x$N0j$F*v!()>;ye07jn%t
zJn>(MG0O#MZa1Qkhb@DIck+q<AZ;IvB>Ys;omUDS1jj=|0t%v4NNYXb@E9n3QzC0a
z%?BDw0stKXlJ3vtvQIicZ%xb4UK!o+4s5MIuf%E1g+q;r_RHdC`kE2ey@aNdIOyh&
zk09z|NmF0g##qG4!}c`Qkb5&+%9NLY%@{VKh91ye9cDK2)kc?vu~QN`8FanEQ!~{A
z?pL8aJfwqhN8X?~is_HtUqP*eHGAoEKJiFseV}gPxu^NJ%WOzueE}LbzYhd&nP?5|
z$9r7?S8rU>lqSaG2lUe&uz4lfn;lo8QKCSq{cmakKolPgB%n<A*wq-rZeorWXx6BH
z<71Ezm*7Xe>_JbK;=Gd$7Vz$c8(=LFX9^vslt`-BBnU|_Th8317?t)|?l1Qm#@xoT
zs}SJ5*<*Lc5BZ!a+U(wfYd;8bJp-I2so|@PABI-MCT*R%42hC11a@HC4NSE)!-B;i
zO0P((<>gOUUYQM*2O?CwR_8YyHmhmxp6{sd9VE%DjCN;5KkZ&#h?DU(YK<t)MOloI
zDy=v>k=Z8CYy<zQDWV1Y4V(*`zdBN*w9*x^=7Mm?dn4^uTwjt)ee61`%)I)_FBCuh
z#83`V+D>hIy`0v2*AY>s4J{cuPO7(JpD*p=901Fj5+BAzH!PZo>_7P5Y_UTOMj{}s
zxo#-K^G3_B7{>d-i{c%F#1w{*D#vVpO`q*xZ$u?QlwM<wscl_$uJ$=ON*F>b#cI3B
z8nag7!C3Klp-AU?1|JO1yyZqZeSh!6$X<%a;PE=ICgF%lq`m*hBcq)vo=qCeNcUh9
zlHz;K3{46yquDe3AC4E0`1}0Ir4QJSz$ba7wR7kRl)$B5ZFDX+>47pe9+yD-7gRtJ
zLIV=kv5_D>1yZ@r<O)Y7Gj!C%q}c}hrA>Jz)4%+EX6TGX!e^IoIV6>PboohVD3E&o
zo3Wk-yPgGu`fdn7LjCG7^hUf4DI!%a)#r6#^ruS4nX651ozvyLxad}MTUPuj{KuZg
z^xiQ$jUxVN<SkTQl-#0X`ZYK4bJuNaTtWdLXn3t*VqLIoNXBsKZ=zk?gi3poKe%j;
zW%y`pss;Jh^h7BYD_$8Wjqi1fuj*mGwZce6x2qNahu`1(xOB2uTKf4;=t%=v^jChg
z%j<7FK59(_y3v)1nF~#6=$`P;?lJ=bU!e(1hCX9+);CUB5QRi}k{@7=X79g?Bvl4d
z17!@+$8zTa%qBVNkrher44J}ru2%HOCz&aInlZ>bT6Snw^dIj3sd(@bz;c1cIZ>c-
zbz<`5xXVhwWQ6wWs6e#cIw@p@yV49OVie|Kpi*<JF-W0lcB>eiZm2AcohzD%j=q*_
zw_@!@4KTbhv=N<9+Usx?Yd40J9-)@sRKlU$ZlZb6tkNN$iiC=n(~`P6P3kHcP+Ba8
z&8NRrcgP~?0f;6rLyFH+{-<{Or#jf_Oz@%+a^M*yAWE}Wd_^@IASf$A7b=Hn#*Kl2
zQ}&3W72}W2Yw;=LW!WGxsUbH*sXoyFS8*;3KN{L*lt_@Z`7mc%6gU&#7T-Ph$Sw-n
zioA4D?0>SpyNWIZGmIEd8fiWv@iQENqN)Z|ZVm|rb~UrSYE%X_agY33wmL)?KSheM
z9|a?tOf*t$@PYYKjtS*9uBuQYjMP9VK7*tIt;p|V4!K~I+^W_SEF3`V5^LyQl$2)H
zTIs=K&;BRu?39I6US9Nt;Xqe^3dk}7eW6P1^5jiT1>RK63Is_Ca0-*tU=t`RFE8@u
ziV`AS*-B8kWN$vH73>NkeUC-wU>Dh-b?ms($J}EL1>`*-wyV(AJ{cIP_uatciEl>R
zE3R1dug4jFGqr@yD^Q8+-R!tBXsM@C|E5muKS=*O^V|VM;U_RqxP{{^ld6xkT+v+O
z1&l(17aeskmz>%ya?MET#%6%x`FD2RES7;7)^~$*t6NvX=Uk!BpJE%Z_D`;u(`ySd
ztrS@-fMfj4k~$b9n%P%QjDaRYYx^r%k76U-2NudU%XF$YJ{`lx0v7(;3wMg{-+IWn
z>|(A5BwQsxq3Ci5xDOzCYpPs|Vg13#2!+qjxIJSQWQWyo3nZD7yrYwse_9vAp?D3v
zV|BQ(%ZZtrCCHLgaQKyUpo9xyM}0pF-W<TjH+r&}SaDl4gUI@b@rubIx0lh-&Vejj
zDYvXrjwrGB%X;mus%rYXL4kA>?dxz(l6eTc=@fFVk<=o`5Qe&xwPBPK9}MIcUM>$5
zZr~1vU?H4o=8UqT;e+_WzuO{z*X;P4ji}A*nn3yeaHQYq`Ho|o=1+z`==YhU4^5^E
zY=w^L|E*YlL;Zv&b7k@A?&%iM(EChcPeeg8NEte()E8D1*8-Acu`Un-cG9d%?<eh%
z5Ej!)_%7fqL`o&u7fg6^{4k1!&M?`0B;#56J{V$QyWIfbfHGq<ho-A6g@92C=D14(
z`O(awSz0(l<^3lXSMf{4!)R$R1(^wM+AZAqS%BmuA(FJ<=C+m)lMC-sgr~sGAALga
zchSJ1xNh6>GHvI^vgOuOdrM5DI8l=zAqMkpU8+E|Cqr+@g#@z@=zw#lmd{Pvue*hw
zFp<Vhmyp@NM3IZd7ETM=z}4`%q|4N7tMvpiSVDG4{Iw3>8T;xh6`PhWth?<S=nGQr
zjBE%`QCg(6QDa^55)?`QcqJ0F`PQPhF;H%b^641b*PCy*I@+Q2NEFG`$LHy}Q+_u7
zK>G|X4CcNAT>Ik$$lYyaMnT*T;ZRc($w?lPE8ZnSwuZ{B8$!;-iI{u{NbzG9!}t1$
z8)oq;Gu-mC3Cmb845YkWhADf@v)eCV-3@%CGv~oGK>G*i-R$N<FG$o#5JP6ZF)ufJ
zA|+`0b9TH$;7#m|xC4mX6L_&m&esMVBs=*eAerCjU7^@Z=q9?ySg8>OBaa@qMXCfE
zQhwHWo`Fe~q9VIPQqgz1QA#D>@%I3TDo>Iy6L#11tuP4VNxJZmI9!-$f*j`GUHTCO
zYm9?yU-ohG%<8jkOCKmps6fh_F<$-MvHiQj09=VY4xH9e0Zl@mv|~+A_?f(OJtlPC
ztlOAi^lIQvIA4_eG>hN7cC)VSdLgoG0zZis2ZQM3@=p}yBlW4<rbr5;kX3GEMow4!
zu3~+;DWgPbbItpLoQ!fbgrt-wYrl?Z>NNuAxnhQ~vEj%PheC$Snv^mCkw7D9r#}R^
zty%+c?tO(rQnUmaMcwh*-6j^$n*$nbe13#sPtk>fNq)S(tdf5caJNLKUJlRsO~|9R
zdVcUTI(a;k&T%&QSBhH%B?d_ErP%Ix^$G9oApCSy-*Df$Tw5LLnuI!r^33C7-ac@J
zK3zEtG2XKtE(D!{B<;Vl)7{z!P=VlWgk!l{f%}yIwyt0Z=SWgnA*1kVAz4Yw1Vb2S
z-RQH4gm+!OdCZ841k#OaYqG;FqLq+8(XOKRU3`Ir0_f03`}~IY69L;Pm!g(e060qt
zYy}lTlvL5jK6ug#84tFg>mvob4G~tH+C>=XoJob92@*E#d5)oiLpeIhJ}5qds3PAo
z#zAksTdNciG$h-UM34@n0j>V&4W`P0#ZNQd4#yBO&_M)SQyIH~1mH?C{v;k;=xdT!
zx(9suw0pIf7m*+B`C23CU{VL7gknL%TU^j01%Z@<D@cVD0_kkZpa>2w8z?edqvV@$
zff5jg@&|&-jzr+32GoHVax;a1pE{IDc+@}|=rnAJ$|E-q%@RhVK#2ACsVY%hnLd4H
z+E)i%5U}3ssh&A76r=Fw*K*;3`{^5FQRS{`_1~)Wh!sy33}H&xj+!k}-0=$k>bb73
zF_3AG52QU^aT3z2ZF={B@<za;R%ws`2R(=tQNO$$+EG78_p=QU-_?c=X3<I)6Msg<
zKM8T$k0Vsd62puE{ql_eQRWEpo=15Fi4*#6xvb~^Kv?I&NZ${xiXYt=lRsX2eh1VJ
zbX<dhM6W{yxYGxHM%6vqnz;P#+7?N!IX5<m?^nXkU4eQ&R4?i`?7M(*ACf;>|Eh9t
z&gPX)TRjtx9CfOFg(GGz4JyEIU0$xMZ71fC0AFuNFB`krWd+9!L=GJ2cBS}iJa~)H
zu#v~Q`9>GJzD00YclUcrO+M#_;XT<))B>)SB=!Le#qa2F2Nb?LaRV2`G9Vz##1zmt
z!$v{y#mnKcVA3}UmlM^+o)re%R-^g0r4RJ#8&FAFFI+oDi|uCsx7bxpYXj<LDBNw@
zZ@RBACiI<Wb6=&JQs9Hn9VP0C7KMYdPqzNLO}S9Ev}9diq{TcJqRzQ~&IM~3?|r%v
z)jMeno9WFCVXS<i+~2%XTHU|vgn!z#0@Ro@;MvsA#g~A48i@2<S03B?MyzR{ApR&C
zem=gOLQQvy@wPb}>^r%J>wbG2Yk?V1dKakqwbh}|UW#+KHGJR&DHS-YHJ|u{ZeZRM
z+3Dt4)Q86s=&3$Uo%)zE5!Tzo>swmgR&J+PI3m(5#;9YE*FNex(tMu+<%+L8A`J+h
z$Dw*_w-m4$uQvCa%aY2j(mfZC1K7H2oWfC^s-~JYKHZ?n-ax?^!JQ=U9>ChY%%sa7
zT#;K*pvJ&sOm5q<L$0zrRd3;$mlNHL*zMFnVWtv@<Y21sqrSIC>7CMxA`1-4Guqah
z>0mhp1^2y#8X(7kO&6D79FtloFG@Mf_Ex^><*?uP#3N3M1c*{mK|(A6hgQ5|lb&jB
zt2!FGw;{$|a3%aRHG%4$-8<G4DmJyZ=!D*!bAl%W#$k>j<oHNz?pKgZ?{PC23g-pX
z4@B-5S@3Ldj!>dYxWItVrr=ZDV01TJPhc6$*Q8)3P^Ok2id{5kZ0-gRrYM-?e3eoZ
zdP9qel>|=gB5dEWOF%1-Zfy6b2l@KEO9o)1!2R$|g70nJlZNK5vgn!1el}dL53?r`
ztvRzGhZBA_F*1{!uIW;^n&lZD0rrEJJ24KZu{%V|s`5Z7ww;^5q)$$?-T$bC?X9Dq
z>_LOrQ=a}Ckz?Au-+;RItlD8h_ysG0LkP!;=z6c4buJODW1(jEgawB}RT8bO3z0yd
z1yE3Se~9qkD(YH=fpDiz#YlkN_TIPcpl-9Np3h02*-bEj<9_*i;yoMSJOHbs8s3G?
z=2O}|!&kx97^tAK>*}cfRjYWVVn(t0JkG>*%;Vl+^yS{?tsa`f2;Fw0A61=9AB`^e
zd%Hm*p7onRU7gCwOTJ6>eP+dn2oS_R^vz*4Rx4T1$~{*BV>~aKFyk_$*p=<}Qd-=M
z24nQkmgKsBAideycLO4};&TXTpZ#Ftq?rJ^H~U*MCmUi82nh{Rg20*L-gxGrm}qDs
z>X^%5uvAR8i;vr1zE*wSo_&(#8I|;ir`gbORK>e3QmLC2v!X}KImB?Ll@IWhi-cQ+
zGuOgeA}g8b6G6J%eu|m4eMz?!^obpHQd?T6aZDW@q2Y7Lh$*yNJ;m#M<BpSQC6XMP
zDrDh`I8?$L!sg7OtnJjfJy7(K72KT6S6O4cj|HVClm)o03=%MC7q`8qwcJv^;Y;0%
zaqHbzMCETBdR#W3<q1=AU%L!-l5K<+xs_KFUyvq_q74D$=&H<P=`z{_$di!O;x+PM
z^7P7QRUk$$^|qD{bb%E<x+Cuk%ZL;8{J=od1&N@P&0(4ZcNKa$Znx761RsmjmIf6u
z8*#WM;o98S4XC+a;`|%sw?y1nq-^*1U$Jx_I;j^o#F`IWla)9|iV-a)KUXK@!iMyH
z`nu~O-9B6UiU@x-nUuKUpw|FEnQP3a$aWn-?`)lg3+|Ng=fFb)9-iW?KnK3fQ_Y?*
zbb%3;u0Gn3)3$KpWLKNFS|1?g#oLo!wG+O03m#-8tI=p1iTVE!_MKr(He0*ceP2Y1
z0@ASnzEl+hO0|I^O@RamO@p-11dMdB(*y*hHw!fh!2qEbl_p(EK)TWi0%8a~aOMfP
z_dee_`}+K$*JbiNnOU>ez3x?JX0FhaWajlVg<3Ey8l6KXIDJ`@S9UZ;<~rgsw8c~J
zboTpEwy;!6Dvr!a_B;74bhP-gEY16dR0?oiKMP)dn$lx{3!_{GmFDEGIr*;XRu{Th
zZqCM8)=S!_=`q>3r&zp7Ky!)*WrZB&^SLqzb3mGP6?30NP`i*x3B{7&M3?bEvyZld
znDF)ol)AgzuLwuUYH`v-c-vA(H@)_UE%w}A$P8&YT9P-rkv-tYh<<JX`<C3%Y<i(1
z#Qq_btTZBDyfP`7oI7%JcTEu7{nqIQoxc#ZtyNwv(KrR?-iz1exiNn2CH4FH7uvk%
z7I_a|>%?uADrdSm_Ep*m6%5K93wlNnw130len(^Q4f#zxvT|^-YpGb-<|jXzqq{X~
zv*ot`V4=lY6-$BLBziVr$xPmw<iz*0MkpIO(&aQnDGCcCW)wNLJ7+wOVPMvus$vcL
zY6Coa-!b3CDH&L>5j;erXkU;TH(%+>f{buiaJ7sIp`P$a$`If8JVNnFMwx^AdF_yA
z1dH=#+!ikBOa-hiYAu+Bd!0Q<e4ol%J+l9n4joxT`FfNQ!&ch+ciX0bdZmQY=D6}Q
z#L9(<*m}7qc@`YPI{3bln^H=Hb~OK}XLA>?b*{=^=NvRGpoV)7MI8*azl<9`*v)%h
zQ=qcA`-8%=ogZm!Q6$eX{26{WR`K-91_O;zy>VaxyH1Nsj8$d~U+^-o?@sBw(JA_Z
zKCD{koPJ6cP|+P11G0NH;u;Omc~D~IZUb9{NYk9ePq;4RHSVK`U;XoQ^A@&tyouep
zsxb&#WrA&4l>kR}=`jQOj|HDckue!WJ55f<9tF(hv@8t4q<Ao=D8uo-%-=X;+o1`v
zg2OOg<bKj6b-dgQBV~6=SLFNp(sm`j80qvn@#8F#2#iyZ#9wS;h@5*`10~v%_C@!?
zkVQA|QCv)CZdMf*4=TMLc-ik%wwmeYCxRlU-S61wcB`w&41(hp%tJrn3c`xlW;eBO
zm3^8iMA5?YGZ?G)ht_t456}m=K|k8cmmkAuQ2a;pk^FAYbQOn~&Kx!lVNZaFCNM?X
zKM2mjF{<Y76%_dyNKAx>{DllMq)mP3&T;8PY8v++9*ir9$wy{_Ed~xE>$X5~Y}bg1
zA>F0jz;;8)95{3`66+q++P0L;=gxmLn(yl{Gvuln6bR(4H8{s8Y3@~{-+x6^3thoS
z>YeqZ9QJ$bpCj_BpM`_i=YfI>EuW*rw7&4SQ19vL{#Y<GG!NP?4ZNd1G2!^gjYBK*
z7+$FlHSav%&3rPOKfFw(|8P;653-{>wJ?0Hu(oA1w)-CvJvxvqY2}R{cZ#VY@vAco
zZHI}0BAV3%pJMm3DBZ+G)qwD0n+9|9UEqH;+V>@zEoRq-DBh1LwHJ+Mxr9IG!THpX
zz2h4Seh$7z&sc-W0-x|J%0nAj*fJjsCv(YM$D8}X-TgMx?nMOIp<vTWlRZ2_l0@up
zrH48?iiaC74IN}Od@%ABm+^<+fjW`C_N{&FNRtu;Jmy>X-(%t^QqVguFRUdl#L(=^
zw1u)XOc-n=0*Wb;<^ql+Vk(McLhJ$Lyp`R{Tz+(<m3yf)GX24$DglIoaJCvYCete|
zIvAcjGw?WTV<ne0#t0t9<L$6nlD0O-szRgJ@GdY2A4rxkf(gEBc$HtBCZG37Oui6H
zI!Dav@A$=@^TXSwQqk0JD|5f8iuw9SGK-WUra804tIZ_BRNy(}4H(781USA_N@GwV
zbt!?8C>nah8Fmw1-!Jrr0!j+&hf-{Re=WS4BLmf_H{5uQ+AS)Pl}k3i#2aoDbv>4G
zBq>LJ7L`4qk53qbn;H9i;nbSG!=X2mhW2WR=xj`P?B6%1yO^9ny1t7+eL*{?MoJ8p
zMPxyN?elFZtG3ebiyI1j731j3gu{GG)Pc=H&=_+Wk5KT47TTYCB5k1-%g_>RK6;Os
z-77H+&hXSBT9Ub2S)aYYQhCgKW@nND=`vws_Llu^WwD0rl%omeGhJ_VyOlT7<+q3<
zz6HDR=U=@?enGE-EU=t~#XxK!kS^&f*@ri&Da@<{1@E^SF<vKFzL|WWh4%>$W28md
zaZ6^{MCtSl92pZI9o(R|Cz0XktzUbmuKli6lQL*48GHI;yvI*6sh`e{F_bCqK8F`6
zUsY6w#fHwuDOG-GwLZ-(T;kQ8G`-&RYTITQ8mlI<%Lh<eSa#42dBB#_vun~du7r$@
zf<U;|DPZiaYDG&F>99wKN@d=9>fcW<l-|~aSBW@)s0cYHuJD3`JPtCn(?axu8<$KT
zIBZmHH?pbW!}wH>6Mc5#OU%Jw^7Ld9VkNR_Vn|~BMwNStm(LGOLpL&{ZegCk#{flk
zT@q9IwIzt@x?R;eyL<`&1_Lz$;SCxM<$6-8B8D(C(;l6ME2KCB4JNhDbe6O<Og1b!
z?S1K(Nl|;+>?@||SLDT_f%Qw+y@Y#0sov8)o)@zbMSX+|Ja0WoFK_P07%=OTD&c?a
zC8v<jcIAzf&cq<Y%{$M2C4N2IPUJ~qc7cL*(3C;bBm(h5Mio$Oq&)jH^JwLFvKQIk
zx7UohI)BnvSO)I9fQ4YMI^4|HsS<+&b>5`b1aEbZ>XVx5TDVn`<T!L@VA68$R%ELA
zZ^Tv)_2l*N(+=U<{gSREYF_@505nsH<A#ujer)9HHdy*Ac6mVGWeINq*wMYf5Gb$%
zB0yV$$Y;thgj^8GlwN~%+O6@*TA&#r|MKSqoQsIH%kO#uoD2Bw?NeHVWj5$fUNouL
z3H#)j1jFB5oNxU$xCoJ%b6x{>B9>7xomx_cstdi;P3cISK1dmyVE_=L2?ugiz<or2
zEqFW|d2{!vAb9ls+jKjLt#>~6y917R|D6^4gksiTfGk2ziUpC^1^uwMypgw)ZKG8*
zBup+b@(*q$%k{X=#L<4#^9<yh6#wyFA_+dfp=!vbL0;<AZ4A*T+rpK*ixD3PM(_f2
zQXJTwq-EYA=N$sqC2Z=?9n)fTiD?IyuJ<o*N9qhM$o3~<w{S-<>1jN=KosYZc#Bo&
zjI|&q%Y?u4rx~^3HUbstsghO1Gq2uk=9ac&_c=bLtfFWMGgYts{XQ$|d|{o+98Xm(
za+l<42{2{Ed{PnpDP|Ge@9k)7U4z5PljZyJgOQ1)x%37B!=nxQWHhZ7yBFJdaB9`L
z(nG(q$B0Iakg%p-HE;t!cOxp8JZs<m4C=8dzZ4o`5<pJrFGX|i<Q4$k&$c9r-;Otc
zJPIWt_tURaw^BDgF{^b_h+|muqPb11fMe5rduQAnb-gXA{W>12<36xBC+t6d_%Jy7
z<JtLSBNE>0Xa0{QoJvw|EU%cMOx2R*bGv#0)xuxpl=QVG*8>%KUO0l$?1e4gL*~&4
z)ZOMl)v>V4Vo<BoQ5<Nz%eMWB9jy;zSyovQ{*Qs_6VW-hMsETyi~&6sa}``wSjC4W
z%(><<{$^%dgWZ`p=PhKa9W3r`m4IB;{@)=cmB@;lLx;N``2@mMY(QICS`F6X#GCcP
zrq4%o;*E;$#A=axG|89X+<xBR032T;rN=@IZykxn0K(zn)pxL(9u%r>ioP~>^S#i)
z@uU7?fn;#<(7ej#N^lL<6;$kZJSTAFX<?v8lHmqd3|P8~$FYYVNtm}KQWrKxGyNAk
zzuC+CD-L<D#jj2x@Rd><6nUZ9BhkCR&R`cB-6f$(V!6pWaCtxSMdg_%otBxm-F=sz
z&}Z6m=T0JWa8-O#ZRUn{z{^s$0?B#l=)piTlqS9a)hNqi`vmDYFC|LYyYXT(<oV>3
zPNhxP^Wo-H-LA;wwa0gx3?Fp(|H_`PzX{`X(&cb+$(?qZ<&h10oqwx`m&}gZt5t)p
z2!wk(3o5(bD_%)*L&+*HTQ+65rOvC&m){4SdkkN~XsL@-;KG5R1OTtoikGzAD{<xd
zhdn(Cix;L#)iDNxvtLW|28wl&s!*8Kg`$N?^>9|6hJAmH&WYi`4Syqw5^+^(?_dN2
zCKPE{k0f1#^<(;WFe);mG%EYul=us$lNywZi7K;Wg3DL$&a_%g=&ls{U@RjZk%R;&
zhoh{<n$vplilJzBDUjx~*i<u=Y;A()ESJRkwFL1K6{b)a&}?}*4)7CTe>*rd3JQ6V
zOkhW~&>OH_XCj9P&hA5uX7s>Jl8oTYhGw}U&jtM$-~P+9r@);{x|uxdPdkz-Q7(FX
zEk!oGAh4rgsjs#t$-=`N22wTR8f0p&QrQ$NG1C<2q-6w_CW45SG>O<+&+-emP%?AP
zt3r`8mS;Ay;!4RYF3eCzBrKKFBlctH`t2jjPXmMz2atGarS+da7nw*Z+6mUx9qFsP
z@JAWGgE8uJi$GU7K34hN=Jr)yel9b_ub5jw0GPpYJrbRPJpgnZp>RogZ6qdll3d2N
zLqg8oiALf|bMykjZCmP{H~nY#7;;ZUEj|#L`qF;#H%GT)HrA^6om_|!=0I!Ylz?KT
zl*K$}Hc}M@ch`^lI}Z2U4s4GOMP)l}xy)2<X5?~l+Q@(iW@D+kI=pfJ6b6}d0&&0u
z-|Y=7y~`ZLczUL|<NjR}NcEXUq^4PCZ8SYwtw5U85qaTj=-{Vg2DO_iG*Ldt9Y7NT
z45Z4BICGMQr&i4@esgp|hng)K^}sgWi@bQ&`dykTSdXSqGYzjEHCsOG!2l(65aUGL
zLd*J7-TFL(a@aFW(R|T|@0*mDMzB@*Roet-w1G|Fc9QmTW={=rju6rA7l%Pd+P9wB
z8q;i$(ukz91xln4BAJ{FV_m@!rCF4Vq|#86N=JJ=7Y|UTvn8&L<P=Sq<Ra~u#=o7l
z{LI{@B<r)*XAilz4@M-ndwLJp33_rQJgYetVbR^8L=N^7GwMAqUpm!O0vzgwCRrJ@
z4FU%Y!x>?`+iHDd(Rakl_IGNF_=@2~vIW<B)SV;@=n_A$>L)3VwiV34N?MNdeZ1MJ
z*^FKlSHADMo}C@42M7m1fhY*H{a*cp8CCTjI`F%FOT<7E(_pCCebLbOf~xMMmCbXA
zH?5AZc51vrd)`ctoUNSA`<0}r5@#_4SQP%a=5B-2aM1p!Qbv#N656-)^o<_q8k05-
z&Mcb&w7jqIb#NISfT0nJ1{xj@nV2B;hH;UEs^MaG;2-vcz(c>_sj+;6j|`HP>}w4q
zN{}+37cT2mgyTmIOe{R~0a?38+Yr}6u%vY)ZUq{R=Yv}8RULe($gYifJ>LV^kgA~D
z?o8&&^F`;$+M-doxq`K!m;HxnIv2{Q8!A<@uyBjb(Cuu`TS;i7l+TUG*L4-r$9q8v
zUd)?*>4rp#xm_r{pKI{3wuy?F85<5Hgh7XU^0erq-_a5TkeBNC2!aah)V(86Z(`<c
z`wURrB1!JM1KTU2GrIqtOZfA>09M<00V_&0BD+85%}&#PKYva;Ga*Bx;s7~cr$-AU
zs@w_PnS#%QqZKs!5BpY8lHUKeLvCJ*Ndedar9L7bzrsG1MquO(r0$(x(KoGt*}L$H
zA?Tmp9W6VU7sA0u)^j)NL}N=-Pk=0qU))Nr@mY6zaiB?MY2_hAj@%O?4Ah#u&!rTA
z>hE_nyuNptC4Cjv^Q=h5^caM;Z_j_M3=o9cs_&uT?X^W2?VcC4J+OWjF&N6gbc!XY
zF&e+KvKi#^|E@twy2(3^j5z=G{LPLf^wuJ>8<B&!4hu1YyZ7PcZD@Shq}lDv$yJM;
zPUV~XEwJ6S-{B9B|7g-E@+kFYx7~wWJ*iK5^0_p>m|LXuLKoG=9kd~YD0)O+%gtDp
z(K#O~gU}wp)`s~1cpoB`Q<lK}YA+FK7beuN$o5@C*7|6QB8byB+^WhaQ#LIBLPX_)
z7EB23pMmUa<mt+nAfYM!u{B_BwbNO{inR87PhcfA&Bs37wFVml&H%mbDXg67PcCgN
zo$2>n`IK2{0TtjiWMDadiCKohif>+T=JHi7@uhbyyjtv{B1~?zyBIX=S}uA@_bu>W
zs~XG2B$Es4NQ)gVUGparyZ8U>I>(@!e>%TUAT%7)(Pn{gv!ihv<qO?qRH<uSjh)EU
zHSWi9!qL)M4<a(UMX^B{A#!Ek-OAdhVSKNzZuP944>$Wbb)~-IP9E|avI^r!9QoO&
z<6ouKO4+TaHcTIx2TY@G+sBYqG(n0&`zR>MXKb^lSE8WOUHw(LXS&>)gPKGLA8#Y`
z{?%9WZWwOf^!1{Cp6=u&ja!O_eW%IMT}GtempB3t-0&y*{r7gC%h`wZAL@2~a<i2k
zA%Cmt$SFG!ZMedxu?&BooEY4aTD^At)z3z4cE+2-*Q=}^l*2q?{QSRtNA@{aspZhk
zPMMQTi&Px+oOuBRF{0xg$Crl2q(O2}d#_nX+W63&J*O6o^s5PVz%z53fhv|*XYF&6
zAm-$%9qsV|^9}!Jcg!U1c+hsE^RdXpZ)#COX12A_7lZ-l;lfdda+k+KsS_f>WHE2A
zzvl-*jfz1hgW!WV44QPcPwuj9ODtZz?t*ALtZ0FSXDT~O$<p13$?w5Idm^{!Rwj0W
zLA82K+I^LH7)y>^xxZgei+R<?EA4sKC+VI!Gy<sr<GfNj&N3jV<TTHhILw`e?!`{i
z`qOz~XebfG*ek&BjcMrQ5O~>_ueHym*}9&$l=g|3?Zwt%k%^}tzJ1FKGpnf~AM1P`
zB)!p<cdbcNe8j2$9U`-ji}Z>#=Z@6v@Zl&(=$^<XKjH(5t<mZ|y#6~iy*no6KIok1
z3L?*&`TG`wj{Ym5@MxA5unho+lNVG+$XS(>1I2?B5zU;C(pLZOXw^COx1{^gJ{bFg
zQmM0p(u?D-zi5C)%J+BrAKD7#`_$X_N#>Z0w$j!F*q2Q{Hl8l-x2YeHvABo%Ci2A5
zSR*~c)WyMUgCrp8Fj}ae6HF`J|8jdn6k`Dyi3L&w79)ZfjTD7~dF!^$9&?jdqGGyn
zw@xAGH}Vdr8Gw-B+y@j)nj?kMC(S<DP48mStsn@Va%p-k2{X1=zP4zTqu*KjV;L}Y
z`5Stg9iXEHIgaQ+k%!$Ij0X$IF8MJPAf{RNRi0c9YdGft@0&kvFMx~5_i7DC^3PzR
zHMcS4Ut?0kcB^Bdei9BMcCk4=YD>w?V<H}KsvP4%y<OmI3AuGxp{RJf&m96k8(aG|
zo+5kY7O&&c0^pnrQTKfQfMUTj$XN0Xj3oz|6W6U!m{g_9MMUo|GZ;ZGLy2D~d}d@h
zK!yko+^{f0!l9&eQ#Q3>YYS>P&M{QfxhP^Gc<0RwG!PJDp`}i0f?(4FQ}(95LDyY4
z6P)IOHsh6_LYQ_bAl9wxwPtRI8mi4ielOs-2C}bOc%;T#aEO8;7calojP}hK+W+&r
zd|=5lvZV#{9=tsXyyXL^lS!o(+ggoqhuQtoaIf*gVG;}!J|Z!PK|2J?gP?Z3r;2t=
z*<imxvIT*Bnbb{i!Q7fPDgjI|JSrW_nfseLvK^!x`iF~=g@}2$KlA?FE8B@~C}ang
zYmk#{kmJ4Gd~x$259k`PeeKnfd08L|`3Bm;@OCb1|L4ep#qn$w2iP~Tj_=T3K`q6I
zWUQ?HAYJ78tfxk2n&sQ>_k~*CIwI_m$a<te7rDqk$AO5h?~Sf>GBAn$gxdy7hKI`$
zS_(bZTbg>v;RUI1!#*?}VCXARb{rHP-e0&ldG9cTlc+w5MmiJdYt^gfr_jlEO`Yx;
zCLvvWv!3CR+Be@}(;i)WgADF|YJ{oHE?x7_u(9%E6L-u#Ma2B*xnxN2AU}|^eZ8O1
z;kIV@u6wCv(E6`iq$QHmdIF+e_p^Ry>aW(Qzv~J7M2a9Q3%|8Lx0LGi{Pvz8s7%&4
z`SQ=E9Em{HTkvcKb66vRqW|dr>%lWl(k@vDz%eL=1dd%a(Beh78MxMOcN?c$1;b4c
z5jdw)5hNDT+k>l%Tg9IUrySvj-$e4_xc(v+S2ckU_I828AKYYgsBCwF12w+!90h-;
z-9hNs7236?mt!bGJ+*?bwbm;T{L5I|KJRPc<tA~!-6tQq_55BmO?nM)(yBlNX?2yO
zbFfb99H09p^hg>cX@LW3TU)imLZ|yw$u^<5>p081_0<y#TPmR8nbfA?uh?MjSVcD*
zxw!{wrQXRLf!a2s9V6!q@G~ri7Ool&U9_zgqNTS<fPlN{$~|3Huu}VvLbmZA_OkPk
z>ypaKoeQ%yN2p?_=<DmDd<+``00N9<C*KNf7Xm$H!N^?XKaU)7hM?5DV{wcq4=S!R
z1|SukpQ-gvAe1v;JOMrch_hp!f4<T)S1w!bGF1Kxudkbal<804^#`!GB})6(em7{2
ze})0no{<M<1U`%h{yYV3^@`j|t#A*G#40RT<Uc=n;(Sqt-JI0d;75V3oR=?Oy2Tb@
zaw+J|n-lNeU8>=W2wdRc2;vPBWz#6%8-DCU@MVs|ii+>!wR_D+yUS&G5?@yPjb8kb
zbf)#!Q=yGB7F*0VXT33S4BR~jKJz=#a^uA<_zfz)1d+39(&hsO3x)=^cY%f&pngz)
z4%oHz^f4qBa5V!s;f^s2@Rk4i0pr<!J;4Nh^WV?z2M1z-m<=4uwDa~$P}d$4v61nW
z|NaSNykH<qU~r9Bz`2tD_16R8t+F6Ze~j@3@aFBka}dgbk%KpYV|F14Gv>k=DKy=k
zPr!kb|KI8FA@*G>eVDuCR98Lra+BU%mzf$;%iTZ7Cn#IdHg&}7<r|k)0lA}K^gv2r
zV(ehQ9(WVj!}jTPxRKNWnOV<Ii#fCQge3Xla(aWm`fujhP}VJ!bjtaLB*mYm`8HcP
z$-|Ibpy#12Jb#{lY$T<6Al%26OWOEO>BAXoIn^RrJqv49pOMK7%gnH$mS36vsx_a%
zEE!Yyw@if*Jb`4}g@INJuaL+4LShr>sr2wXzaX-}T4KqAz6Wkg-*;K}B+BFq1DQYz
zz*r^5Zv#2)N5M+@FKnd5!~8RrMSeFKF2#&9J9NfyYg@s&^Y5*qs0;1kMu(u)_@An>
zhsevC;`zhITsB9o2@%K2D#Sb<q6ssH&ybdRDk}PNC3pY-CmJdsv@z}|J07gr!b4wA
zob_Hhu$E41b~cBZmBGD9=5T8CJ|;-EV0{0U5?E?B9C0GZVzb6xnDn!iH1U4xf_aCG
z1liT>{-B=zU_~Epp)pkT=uNfthZBP=e0u-DEzG=Qr}aBSJee3`hTduF4kYl%$VwRT
zzSSgPDSjbJMsCl37CFV4O`}K|ti}9VPi__7E5VqWyNE7x?PRU}dy7KBb~V5?$kNft
zEg`w|U{9v6d$DEiv>NWc^^ZR7Y3Wbp5A7Q97#7+>w@z8`HCAm6+?{kK97i0NB(Bk5
z74GwbY{GjEu>R&{zCN3v^8Kgmo~@#Aen06+9<X}g3K%=jsRf$(5+!-r(bjbdi!PKd
zwR@fo4vt2bxaPBdfv1TxoeC&nwn<EvKwLw!`^{<>CE7cehmAgk?CWR)wx0m&v}p<H
zg89<utO>O}rk@seF$A_S)}lHGJ6Zqo{A4J<mAU`?aL5|RK;@*FzT$Vu+=n=HvFrPt
z9|)nRc6qYuT6j<1ImPuI9oG9+-^O{FrTze<t*66ewiZ%iD^_a?1tQpSdn(O!EA!o%
z>klvtx-QXMe!xoMA?04TN-?orM%Ail$Y;{byl`ezb&Fko<&i14Cg9Q&W8W>X34S{E
zI%=2Sq%UiH{BV4=3xwIb5^fC6w8c@J2Fo{(jaOz=eOQ<3%yo7SV+NM>*hqW7_fi#w
z%u#lK;~KRtz`tQ_JTn3Rv{kuBt9TKWr^ZwQ?ofDi^cPUoa<BI$TQl}nW{+?ix2$5t
z^JiKF_`!7?D9$%Lrv9^%`F9pVt+;W_xh5#NfvP0S-3(QTss_e&4>9DM7+bOSG*!t=
zMw8aMF0`0u(6ePLK-@hB-MgUo>|xfSW9L8MnePwAzDz!oG76~RBWu?U+vMq?ioT8C
z(ZjK{yT<EFoD)+vRikl0g@I*`5ocOrTONI~No?q}_AoiGZhEHfCBN)vT*FNtVTY16
zXI38}aGLTh>ldL4!%8bF`c@{-mR0TFcsfny^D_hWfBk4s#`&D@dXLwWeEy!rdcP%n
z{5iWr^}x6Ql!_{P)7HjAv=ck~<H`h$w6)$ixRQL;6!YhYyd$toOjcvj!_M;2aI;3e
z*!cyi{+36VpI$f&tl{+Wd_s}~*Wd#a;~L6}W?kZJ+vclLU?;#bb_v@`SGfjXBw00m
zYhWl}C@_cf@<Wy97Wb|EVy=r9D|8w;20-D>Gk(RqHUl{3Z2$64R$2nVPcT{0{k+BI
zsB+jI#@g+B^nvS^OC;_Foax31w5f4>W%BBvcj~i3rY#ylUVA=)*IA6E9>5w?`gm_<
zPh$Q7mL)IrGmM!9rcEK=p}}E<b!SXt`wS!*3lZt3oucB6ux0-BmwrZKnf!qEPvE}T
z*kZLyz76;-uYD!VkVy3A^{q8Y;sJ&gFtHUHg_bguuw!*)>Uu`0w;^?AYboF(_i%0{
z-9NDrD?UGeY6-~Y;EVUE^wtNIuJ)h!b<6KPG#iUv`&I?&p%EZ8NH%XwQ8274Cs;GP
zyQ34=n@g%&nSFMt*!<wgN44bC@PnD`qK?&(CI+Yh2mH*oT46nLp{zNlCKzbT$<+7{
z;=QOLSesXJ`&k9<`K{D+K9;InrZ41Xn5lVFKUoZk4ngC1%&ea3Jm+`c@=gy8V5{tG
zzhPV(>%7R&pZ7>1-k)H+NBuzyZVoXk_4=vNqv8Ag%gvx8Jl1Fric|QM%DQd9bXRti
zC%wX-b*yyrOO&cSINSVW_s&b+oj^26F<xSwVTOq>p%KdVG@vP8v-4N!0l7zPfc`!E
zQa$4g<JL{!2sEm=(`=hRT2db<yR){ZgUGH74M|Iu-zx5T@Dqq_ee_49bY+jyudI>>
zYgRSKfIyB@$*QX7ueS2s@%t6k5#x26%VDxrpgDHSBm4p&h0yIYfeA(|CWJX;ew_j0
z;T3=u6l1?hZR?40PZ1Lz|3#sC?d6n;7J|Gxn+0SPkDtz0PDSs{Qd}&GH0yUZqbcW)
z)Opr$GmK*QC4*YDkt=OHTB4=Mq~Oe~cwhX!kcs%%rSgw1yB~GAe*fj2k%#RlFJ2$M
znYZFMm1)u(c=mme6j<KIFUxbqt)>dIjgdj*p$c!0&oSSCqh}29gAogofXt?BDXw>?
z+y!uf^PKsr62`-n78W3AG2if2PqMO&_d%HF+Vhqg;M<w3u9+;^+pj0o7dbdDVSHya
za}(cQZ9PHQk^YD<;%OwVBn_K-mOE6APhJ&uSa9{#=mDne@10db=WJL7@Az#{EnxNw
zbl@Fjftxy!0aPQ9Y5wOR3R{Meb@u<A+EQBBMsHQhpKgcO9Nn3|X$?Ai9Q{_0oZd3+
z*o<E_OqhJQ89928Dd>7n>5$FhSs_7{?y=hCESJ%ile!zPJOCXKJ|S7<@;IJ!=XO-?
z%)08j(8OZyd{DSR?{y_W1`h#}Q=@^8xk->y!>(n|4Uz4C{a$Can2g(f2^D{Ty4D)>
z@W|UORQR^}b&^cvW!9sOpqKLcEUfltxaX!!aLdpM8a+z~{1>0aU-VTX?%lD>>%>0O
z66D|66q|2Z)Rr}&94c?+eV<*z8dE=R*Xsyq557IACR3T&8fQ7zdtcsVZ;kk+ns4;q
zqMh#zWn|V1rjif7f8p()a^cS+Wg9tSO<AsBOAFBCMy)c+IchVr>dC9jOdQpb;~_2O
z^X4X9pVw*2n}a}GgAV9G0zExkv34_mDx*KRw6JPv>A3zNsl$iX#u{{dN6#;WkWu64
zuX<!%D|out$%hrI=j!>HP@!X41Utp03X5MO>j@%7aePh{5i8&xDB*Wm>S#Een>u6W
z%;n=)Wi>8fO>-O;@dFF5o=}TD6)<$*(eJa<zcp`)o?(u_-PMGvQt-a>FUpz^_<JVq
zJI_=Ti3uODls+b3_~v<0sdf?0)_KWa@A^+bUfAxM`^}vN{@a1t?$7VM*hgr4FmLX-
zx$#M}22jh!8~H|3@C<&YYXLs4qyeA<YE4|`C*#EYR*x{qoYtO84!1m`DoHkRnS~Wy
zQzPEJ0?Tn1dzwX@AX)4()Jj~TVb<r=b7yr`w}N^6hAyG@Gq4XZGP?-e?MSR&*CFdq
z?>r~cm1RC;fzLkB(la40H{Rl~_UqSK{oeG(pS@e+XZL``I&@*JcU~(~C%L)Ff8|WB
zQHAToA?jj=cOXyKXaub&Vbx8V#+z{4n;UXxfFz8eU#DY*tRCl-uOq14Z+#^{>=N#H
zS#}R!;$8jzBKOd;%7(t|LS947-@w4mj&SP|WG7Qpl_sCcMtj%|S0-QdD+u$rEd7@)
zw(Q{&`j?>3vKs2?wpVL)rM;c^5tGv+x5b61Cx#{poduNp3yP2FM8LV*(Jr}a4-414
zE9_g($W$&#p!Nax9(UI1=Rr3>R;)O2svZyC$41{s5>7S3@F<LFK_+J&b$;a8_S>yD
znyNN5e{Qij>Ns0kw^Vf~6;Wd)OLqzDWxZ^8GDC3w@XODq>7m=^mmf6;p|OvB5zF-w
z*#(g@KGWd<Rw4Azx7AZFPoC6b)2*7gtk=3+tn1yv;{o#$JbM+Qzf4R&IwxNaG3flt
z{zo@{0dKLChp_Nozg6*k`Q!1)_?9ZaC&wTS%-EQEtJoaKT-RMzSd};L+nMieNU^yR
zRfE;EnmlaX8`(QS_xFwYcANoikG}JG{x~@ArEbi`6v*qY{GrcO$y3kz2R$U#&&I2#
zi;WMgP0g`}PWI|H*s%XkoA{aaP<a_y`*~9>pEtcIven0Um~}P1sba#ehMlpJOs~%?
z!b9;x8>8l2{Y-4eD)jZ^o$E6*WZ9}!=b_KupI=W~SC6U+%Rx$a(SP&1NbaeRd_tSG
zxa2_+wu4`#AnMyCu*bJ4?XQz9R1?AT7CxJDXVtdFP^%AkM10wOITi~*vuykQXCKM7
zEGe%;Q46Hxfy@BPIX;$_#l~x9Xvrq}(;|7iKixv@ejE(f><3&4P~^K5bN?4{C${Im
zQDEEq8PYP(jY-uj>P(j$ZZ|~ERd^-Bmj^YJfYrTv6Ujs(`L^%?^fXB+O^v&B8bwaG
z2^V)8UXDpSXTrNZ>9MyDFZt)n{n*r{7y(23dE2srGH2HExO$$Q6^QWELD(@$?|X^<
z{I?)Wsb<`%>kRfet0Du8tj@d>Mx^$yYR*rvFg4a^F<(!+nSu3QdY4!^^VdPHui%hO
z;3dI@mo5cPzSwxxNxl5_acy%13<^D?jP^acA@zns6NkuYek~zQL$hHUnCk_=L*TgP
zM@Eh+WHZG?a*=NjKQM<sQNC!<+v*o_5YDKqH1+dC7jXfUXF|cg(0X3Uwq#s4jJLeL
z1QY}Ue-tb%tMYqjk<?kh#TysEp`&0rK=xNN{->&f0fCP|d{s&IuS=S??w2sRknykK
zU(5PA@JZ6-T)+M27huvrrvu3c&;I_*J_MWi9>IDs=3n1@#&h2~wD<m&tJ`A!@SjnT
z_!lp}FEaLA&Y1v#&G-tq9R#d2ldvdI!H#DU6RT3J2{J1Fe8k2(;Q!fhm-V(4rO<PM
zWZ}{bUJh9in;Q{r=k3Lpzmg!K1tJed6b9x<GWbt5I42}T53~d`1sclq=vfdvHboiR
z>^p3NIxN%|^k?uHw-n!0mCQUQTW^VB_@N6wAt9z+!<W9SxRd4S)u}wO(yjodBO0|K
zF$xJNV$O#+tr2=@6HWZk8L5o#o8pnkA{BCTs#|t1@NN)cy2jA;M@F1ENYXidLUEVF
zChf=sU<M;b;3;U@OvHpJ3L&|L(qCzRxN`jj6fAKz>U6F%-BJ-X^V7((cu`^R6)!Pq
zes|7)MQ{XMSjt9Pf6^q{H~-VZC;ye?K1JG=X{l|7nBgv_H;c_lDk=*=kW>HH>Q94R
zMN{gB!A~;&w7>s<7aSyw{(OA;MI&H#c_R5O5dVe-^zV;icG+~tu`J8TUsqih_#Yo>
z98pi0EK;(qT-k7B<Zk}F@YW$mU1v)!3%BRl-gMA5{_oq9m~KhZ*O$&681~&koSjF`
z*R8lzHy36Koz9Zn_TM`nJTkD!#72-Kbj?BU?SH)IRmkDl{`m9|>jd{Dr+;o{Y-7UC
zLpM03ObXBFi-n%;Po=+I{Vg;PGtT<IzoGQ>z>+MV5YkRXwY;eJ97tRRMjQD$P0A?m
zTyZ;Y)Aju1&l9eb^2^lpH#%Ew@tyVFAqGs3PT!}y+r$kiD<mp9rNjpMhbNp%*T_IT
zoV$aNuIdBES{vC2&Ph3m0Erv$C!rps9~zS`W>xjl=X6GPwbb?AF3jqh*^Rk-7`?#U
zevQNukkUEqv($cgWLHFDA{j2wyr<}}yfRLr+2%lD{pRr4jgK`QrL=78*5)AV9%ny?
z%C*UWyLCq)^vb}z#cakMpGcQ4Vh?{cqP+2$+U&eFD_^tcZza_>t4cQK5tf!P%%pU3
zbAiYatxSTzD_pa4jrcV!Q_OkR0fmmmpWVAkkniGjc;&zPEcq+zDkXdZT7aMay7?e~
zeKMAZx;0??Q0eSNc2`&f3bPpK)~wH0WfLaQYe--KG5P$^qC58I9qFn~ROeglXNN)B
zQJ23IhRhTanqo~I6c8l&DlZy$&Az`CRO4l85<RZ!d)l=zgTToo-)9sy(cnHWuPN7j
znQ*R(9mjUuh1~sfb9FIl<nNL`pWB1!pOx;<oaxLjP4?Vk)jbj``sU)dd~cil(T0Yh
zfr3+)38LEgrJuL0x`#@N@jWb%swMnR+>B1-w&6l%k{liVDn~PG#4crf)%#!MnU|YI
zCR%JRRj~=3p4zy_kWOtL$nRxfO}O2vS*u2C`<|Fu`JF@@=N-X@^e%K2ynqHGnZ4E;
zB72Vb^HzIfdH$qLP3B%b(k6ejsV@%^S(mfPT;*2MyG)tLs@+}`TE=kRPvUCEJ2#Ut
z^hZ6CUwQxWBX0t!QL9(VgXGWaVow;x4+p{nu?A{{7#%F~p{guxrbqWWA?60QJN5mn
z<v)g_k_fVg<}f?(pbrf!gCV-o>C@@lKJ$hAJsnN=IC<nv+<$%FqJk^Q1pwYO4C}Ra
zVDxuuOK}sqIEcLI>mARqWff1@;cdTcS2exdL>8itTpr<iV?dKB^vk2&9;sV3{=VAa
zb9|_VFOLdBhGkxGVEhoLr)4ORPNoJP8__TqEAP4G?DA`nJKs+yx4-S)NpXMap%HA9
z=h`RDU^c@q<cS;bD$_yQ=js|M=2W2}`~6)@XA<WG^uG?g%r^~vYBc+`GT9ganS7Nc
zm;N@``qLBr$)>(zGl>c#+(`zQ(Hvd})wNaDAfZVy>T{1H&Le}T0H?M=uhHb(49yX@
z@DaG?`BNeApvd*gqMF6|{`^nx=#QgELs$Ek`QG$UrIwnOCO6ls>oz9aUane{RrvQC
zZf%^&7{SK&J{Ydm-WjJM0Xsnnvv3sl6M2PoiN@XL#QjeMsf95ggDlRq(;^jS5|eNk
z&iRG>C>_h^jA2z5z3+F<B2a!obm*=Id`z6G7=(f|yTRle?y16)(4wK!ce&aWI`QV`
zYPytxWec~@P%=_NZfulP5za|Cmp30_yFJ8f@^^NysZ_E7iQi*f9H_j2E9sgZEX);#
zMqz$^^s^qlDp6s{-s8#Ot|ilLO};V%FHKo4gDa{2a{xCP1F%EUzFGL&iz}vBPiRdi
z>Z9wTb5+dHSc!g*1!wOyyNF@&e$$=b^C`3ubfqP79FN4>JM$tV-DIU*VSl4YdDNca
z)TUe=trD>77V?GupIk95Pm9=ln9{NSMAE}*@sY+=<6k}{%MtVJJ#3>bs~Y9+KZ9_n
zKMJc~sYoy;sspn=auTt%Y;L(ZY|^r@C*+8TfmxXE{hWA}w?*!UkVOjQaw4_iU<l6K
zdN%Ke$Wg=T7+gy<)~{r(D}3&T6+ap7_cLpk_4tSzxM{fVG9gA2kLLcA6n~_JFuZXg
zW*poD2e^(ry+vJq3vG*;Ty{QQx$7o*ZNbR~k!zvhb8#DWj?Clvm43gy=w5SiB68mJ
zR;1BMV1q<%T>bFbiCp(nh^#f^lBp!ECBv@9-5w+8#XI@GOR2lr45we?(j&11Q}|V!
zHtX;U1MLV?7888f=9<cQcIYrwu;3I%he61l)|jp7O+^V5m1syYfQ`Ce{<mJd-PVh4
z6kIz+?*v>*R*dXXkJ>1{8x)JRi@~MGU}H`?OP|@ZhS3Q%WdT<QUnaabj__W}ItTcA
zQi2-;Sb**wWv%c!;0oId+T(`4>}}PZU<OK8qo@Ry(#o%18;@StByVk)QPQxt8unnk
z41WT~EV`fv3w4E^&PK2LY<)KP0>>o88YHXc_@AD%HW)|WLcvYw+<ud;`SawK>?YCc
z5QiC9ls6_wBP$<y95@Z9hvdvStx8jqwh_m@ag+`SyHd7-Pshc_b-X2w8)2Z|Cr8Ec
zdF;oPk?)x7*Erprvak3GOu|JFNjAz5)LG@InW;SQif<M|vs)Xd^gWU(0u<8`u5s<M
zK{WFbp6g~}6Q*bTn&bO=?3uW`OL){ukZ2;-!PBgWc1t9O6wbc0(2+Q5Y_mG{1=qav
z1SNg=Zl&9{@#)x=tAc>Vtzn!ykt%xVysGca(5;c=htTjUjg)_N=T@XzT^bI{evReX
zEUerZLD#8Sw|4cN3&h=PB!5W5S`Y~3o`QO?Pp+h+D3brMITRf=ZJs&6V5XMdoz9*=
zLtz=iB^CN&hSf1xr}FjG{sSeA+eoSSd_g+aKsz5=hpTv%ifO@l8)K!J<_96<>Y{WV
ztf(>Jg%o_SgTpdlS?i^#RFOgGJ5xvOHViJ&N-f-u#4~WdWLoAp-`0IY>=+v4nfRQ?
z#J9n3{y}Zo0JM_Ps{)`Ujk^H&Z^=Ovd?R&Fb`)0QHEui-%N5;qBiJ<BKtK^+ig%Mm
zyONF(`|_-q!R3Az^69-oUg;{YvY--DbmHctampA^tVf7y8u~&=&Oe4aHy@P$%UX`y
zz*4*mlk{NP(9h`-OQ(m<29ifHKSFRk-0{Tfvg<cYYfT6-CeT`L7#~sg6s$KQl-nhU
z!QUHrU;NvZ#0J_EzQjYQ)iN2dd_sq@d>x_=CD>XE4(_7c5!lVz?lik2uW(7J*{KjS
z5W6_k$Np~KkgoWiZ9c6DKH=_DODViwcM@@x3n$^6GOIzJ3c`6blCvPslI%9V@~we<
z`X)K+3)vLd6_epM|5Cg64@6Ye`d%|zb=W4NI>yjlK#ucN8J?G>;~QEu$ge3jEQGx?
z(9UCc`_X1XOKd`|p)O0#=G~*|=%jJz3AOkyZqkYp2v=C69_(*d&=rznl8T;aPO^PS
zpQtCcXsJV$OmfY@q8OZ@4hK$sM|xt4L$|?A=dXclS_vj=hZD}hDzHkoBdm#7-hAyK
zi;grj|2Wzp9sEt9m=MnGS$p^^;l3I@Nh;PfdN0572tT!}Zk`dysqaXw(UmrkEAtJc
zJ^~F`?1-=jV<p5e`9Dt4_ldnzk_~p<z-#cwd;a;fFF<tVwb*)MkDkSTVM$`CSFMul
z8;km5K{(qcau(QdVk)5M6}UP=Ejr25q|G{LyMJ-kR%N*AjNGK-#W8X1EC#4{h>pn9
z=UTRYX-w822z6?}(FmUPJm?xtmF0xI@%*X!_15{}5e;&HdBsVtg|IS)G}&=#fjA-Q
z<uvq04gCB#+B6L-VK}L)su<}C3)6$$WXWNqJWn{DXcieR5q{_jbJ8PQjclC#0&i`*
z*2X=eT^_|hf8i$i0#E^YP{mAe$mX>w;g!#(<oz!F5fO=ViNSsW<$6%Y9?z({Q-V$0
z+7mE*75k$2TkzF?tMG~@`9dS~2AEdmhKB~e7M+xiJ~|Hm29_?UiZtvt0=FRK<y!XE
z@q4;m{wWkD40ewkV%Ubd^QQgU^4WFO?5kJ~=RYvpe;0Va_~2H@mbF;tP~Y-VVTi|(
z_3kg`*lTHrKb)Y)T2IgilK%14o<T^VBoL`yKf9j=;eI#5b+HIiILQDrPI=U)GC{5O
zZsKSXXd80$LKMMLXX9hzn%%}g{{aZYT{}}_vwO_>dutsdfufAGY{N^UN9y;8OrbLZ
zSn+1y_><y1t{VgA8YPB^KI=ZFYjSn|mP~tAYSCQDw5Pou_G*a=_jO|FsNt|~R<U@v
zsdl6R32!D>D(MOf(&H=vKm+3Vfkp0`a>WcaCzr%)*}UT(J3uNr)DVrm9Rt+&UNF4u
z&EV3Pm5<Ns)6OdYtSUQw%JAuC@8P)w$3jPQdnl+j2z_I!{my{oQ0kA$0ztxmz8yo|
znh;t(0oUjHmkbqG^<cpOQ$mfT_HkV7+m!J_q|VVR$kC4Ha;+>EzhZyg>swGrL+>3&
zM=};_b&Pz;vSg-YT`M3MG4WBtP^9v>fGY^tK(?S{+IexJ$}P6lx@{AbME(i-50ij6
ztsAnx+qxwtJt*A$D4=D0L?l6v>8<{5V(HAPP@0zMJ_*B4VYpcd(v1Ai2an49^|QG{
z&b+7~u%`uTQUES}B%zFO9@My_ty~gCvw5HYTSj6lt6`~Lq1cY2^RC-!b{eQzkQh8%
z$SCO;ajkV;F5SR%-$}#HQ{et+=i;u#pF<+AJP;3+q~OE{lT+V!Rj|bYC<grt$7U4~
zX_Sm%*UoCg#7!HTlx8`2s7c^oLR;VKsF;+}=%GpI?pi|miQNMs%E_Cuwdm4X_<Tpm
zM;*sbp0?DM^H1C6On!TGFXC^^mY8+on0Fsxh>7pL=CV$9*>ur^+4koiVoF0UnRzDH
zx2Z!S#Hy1~MDf*(gluXijq2wQwE1^80>h(-SKvZ%x;#I4Dg~<QGa6c*HiG0)(a$fQ
zcm_SE4Z;}|DQ#*ix5{SY%Nz}j=K{&#uOn7H6Phg}xJ<A9Hg?0nOCuUeyCCj-0#ULc
zHU#yk{Kw-knM6S|E3_BflPBFyde5(qIn`SFBLT%%_HyV#Z7!gU1Nhx$4ag6D=4Xcj
zC<fzsjv|kKv(L`W1^p`En<IZgUJYnPsOkc=f0PkwGDgUbBZA&B-_kDr0a!mozs2UO
z&L1HLgIU#pe;9@ks8S;i9^2vYz!gCo-U|tKR`uNxS>QYW+b=|L<5IznV`LHfNA2B}
z@6y%_cv-hRuLf{L@QGI*&^#EXePWFb2h9U=Kn%Huf?fcXss#?2{r1lMH$&kyoC}bw
zp|1l62Br}t|KZH_XCR7)B)t$8YozQ~(8|BsiJ;bgnz_O$&@ad{Uwa8=0NSl2fRwkp
zuJ%A9#&bB|xf^!y&o2o`K#YMS`EKxG7`|f|*GxVg$W2%3m&=6(u+CmHJ-$0gYylK%
zpl8SHQW*jWWZV8((IL>S5)3EaSI_B*qx_nmyngi~f9}=){h1K5jH)?mZ8`gllt~gw
zoi*p&==FzfjT?60><orhK;s1l5IhC;se!D-c8JGNDo&y}6gG{%;<h4z{-DP-Q65m6
z5I|?nc5wPAP@;dUZw;DKi%mdG&%^5|VPc|*ZA;Cv*N04BMZb481Kk#ob_4-|Ko)&X
z2o(+H#?X!)oAHU-iFdsxwOZZ?X6P3kwjO!HT;9Vyq*y($G)AgPT-7dT#|43Y>h;Ct
zxjrAe2YU~pIN5I~1&RHqRsvZ+W1F9<_Z}6RJNLA{OYYlm1<G%?isb`glu5eZ@6XIZ
z@>EEpjsU1m$5y!y7urRz$#9g1<ffp9ddv1P46Nn|!{wr)`TR#9tvGQd(A{8^-dQvU
zBTdp8keXkE$-z2~vbknOeq0OIen*^Z(84H8=X;!%cCNVYgBSlOgb5irC>SK6W2BB9
z`)lF%|7J&5Ulv`<j?Mr{l3B+sA-7sj9^zV*{Jfm9Jx(^YJ$Gl&;7k<3dUFYr7~3YU
z%(!&7199?&=H}hJVBxL_17+PQG7YSN0RgQA2@XrP`QxLlznz4ue9@Y2!_4wFXlyAD
z4)rbVGEd3cH$MBo9dVpQh-lh-705dF`zYEkRfebp{P(p=bn?ZO^L@#Gks9GCm1ty^
zcUMPU67Ro?7-`vn)Uzg#+_o%p9;la0;A-dE@&B$dVzt<^TGd3O3Uuu~pmB_aG5Py@
zQ+Vt(^>WZ{1Zf&LA09G4*HK-d01QnFyIejfwdporE{QX$0C%`)^)ES=_aKuWitnt&
zyBaJy6MN`mquL~RiQ$gAZetSIiao?edS0TCJN)aHlI-1~)3WysRCAfvujUT@AY)An
zoHCYGPCTRL^Dme$ecSM&?I~OQd9QRSyLqE@_?7v@Yp%?DLxz?TJ98DTp)9<|OngZ#
zOprNj&W)Y=w)DkAW<P)p&V`r$N^rvauN{IV7mDrW03I?T3TP4|EVqs0hJju~n$E&|
z$5xSswIM9~NqLI22Os>gA$h(0y4J<a_7_s`-sziAzdJjN4K+IhU1Yh2@7tGi%_eTd
z7HIC!FrPZT>&mOH-a^lui$1nuC%_dGN+EPl?*fUb6j32eoAz~pTMXI?e*R|p@xPhf
zg7oG4+hh<VTHof7qu?{}Ylmcq8sjQ$mjaXA$lZ4;=AS42+em7Co7&{1sw(#rK)z(d
zb2;gEkEybGz(KH`>3=wc1Shb2b=--VQv7{4<m!2d6uG?|jZSLM?)$|^3?)R#I;Bim
zeZZR5em_exUkx5ttyFmJ%GvBZArH_#<|<y$cZOHDuE2@>?)Hy&Z49lEEnVoUj;PIV
z#n*r4Aq_n}l3cCOmZ>}C7}F|n2O-IS&sqoDkhBi?N^?wr^f>_gfsnZZH$^@l1cz}3
zH9p~H;BU%UipB72<3NpDz0|IleIJs^gS@f&T%lLN;5h!c&O;~?TiszC@L0QpY??>1
z*BVL-UkW0vK!(Ke>9U9(Ek)(zkDF9*P$Z<1+7TeiR&*Tvc?<r-ijzLpQpS#xED%1y
zOr7a&YdokAPDajMuf=}7xFMCvtOztp7Vm+}PM83PA&uiw(UW--GCS%Dj@h_&7<#Ek
z%rlU8_;L?dxz*8}l-lXNWF9a9hg=ZIq@EyBtV_v<D3|NRnWX~1e)joMA^SH6uJIme
z9Mox&Qt#HU|DKT{^dzAH#{zZ&NflaqfbH>t9uzOs{M}Q=ZoWG4_$9Y+ydVU^3_%qH
z!lfR~a)11w0pJBp;0m+b@&^9}tcB?N0U1Q*@R{S(i)2&ADr(|`5t+#p<pNMltpa2N
z=7^%<bYl}{!*$OCwj%q~UeT(Mt_pl;K8R4?!V3CGt9tn>l<bM*3KO=+K<|6C9?bQ5
z$7S|}H?3Ywo?LPRVKa38Eu$=HhXqmU=id0*4~d+hp!as)xJ4Z9ZnQ+&>j<nHysD?$
z-YTI?PZMLzemp64{3z~<i1oyfCl3HR$Tz(GS9I45{7!&$c;y9;WFFN#?{0N?6W5_d
zKbdxH+dg{!4a#{Dzrag?V>o=_Gm&Xa>I9hA5B8vW`fPke&BH2eRJq5h1)%i+0f73g
zMYD>BrPF<x=csC5bDX2aOhoSI5nZXM8n6sC=o?vyYyS*)VbF(y5Z4Y)+FS&u^KQlj
zF-w0rZ}vw@wnU1{Pg35OlbHQIZFmQA>12jC*kWTur_NpEnZ}A<V8HiFU8QKdq5QSQ
z{mX;V0w#&wImmmyW_b{5s4bjj!~Mg7dw!6Qo9ufHpZE0&{zX8-o?c$;Y8sZ)D3GnS
z%{2(Fd=MO>?e0XmoIC-}mt_b=gA*6v@Bhx`(}=N+wRzMH5{ex2*D<e$HZnLC2J2b~
zo>Y`+&5DgkVD?o{4K?}04Iz}OL62}xfD~7Np(^HA98#v*)D;UL&|LkyS=-Pf030u$
z8NmmK5BPg~SD3NATPjzHZ?@lo@hEVdm1FImT+?WMd~m3Hs8hkN!wi4@o<}!%SbQ?V
zJ{0e^`JK>9e7WPm(X#DNijKXG02$S{&y83D8o)Jv1snSzDDFbRa~(IT&4!lM3ZEZ9
z!4#+_tX8kta}Q)FSTB8JcP4;c*BKa=Er+)9auiwa6KIJ97VI;cO*O<MVTPFL3R7;p
z5c+~JYlmIR?fMH|w6vf*RL-|hv&zFv6fdA#U`p6=?FqxBVN-D=$Ki}2mv*8)RWVxN
z_AF+kg$A|)UBG5zQw>MXry7y%u?<;yprp)jypV~409bADI3S5A*rnHM*6H<-LFp!?
z5;<_aL)Y;!?tT({aFJ_yRva_mq<YVYQP+9obx#eM>Y~ID;X*mG*Eb7D=Jj)DUY(A<
z2KTKUY}0ZSMvynGYd>FRp?t`I;{hmW>8i^I6vGZ|({YA^W?WkQr_8oim)i@*7w}TC
zslP6}G_29dxWLK!d#DT4?OcQQo%8-N@p9~zBfRFwq|MRMoSd;nEl$>|O7Y37yV3X<
ze?MG9vV?wgG8!C7jg|OBE2WHc0I9lg;2vJa&6eD43iIvHh>sag(go>}GXml|v}-fX
z8Zh(N`xWM9AY%8ON%-i`MfM!n_Cq$OYNMaI5tRiuZV*oFX2;!CQS!V;`=Yg{G_6H<
zJ9Z&+e6ViP>rA)F#PdjEKV?|-9HRUP0#}hhM&(g&JC_`5RTCiSWs8#@38Kn|Ep#sj
zI6A47SEmk#R}e+rq_U^Fy1idvdqheH>nt0?ik6x3ol~!rm!t?ILL8iAy=>u#_7k6Y
ztp(KG%BAy0{szkrv^%y{;MLUXPI!WRGQpXnqX?Vq{s=+#hPlZ>2*TNLKlp{Lw*Fzh
zMT65PGxi2O3lwr3hX4?GirMR-VzacX!!t`5u<LnHqHq&SPzCH1M9_j(={NC8RSS_H
zi*hox@!}@8{LRPr0@x#;xv;Um8pOS|!_Qi3W(V;5y4CWpd-U&_y<)$aU`MMwU2x$l
z!?5><w^pH?#|p-I**~xH7?c|-yZNe*^p{pOqMJom-PjlRC``DI!V+nhV6jFRaP^R@
z@@0Ho+`$mCLpgQikZuAt=`-ZC{fCt6anZQ7f;CznUx3&AwCtKB;0L_jZB^rML(UDS
ziqE{|tt+h?8>P~j8Riao87^?o2;X0be#}7C*N&LW>m`3t)sG{LZGk(+1-?2OT-l#e
zUO42gUN~V8dO4K*+Xk;wb@z%65!-QT$xU2!djY6TAE%Fa*-)~>1Q3p(UI_|wry?_z
zak|T4gZeYl&8rv5#a%Xw#&n)*!YJ4wxj{uyYDE^Z@qF&??Vu+o0JIfobvf`zRvdVs
zd2c^6iqn{v3`m=Y=4-C%(%B;6D;HGRK~4nU6Xl%RcTWH2JwWX%Mzg(eUfRoh`re}a
zWxC>Cdbk16SlfX3SGEPaak`8HSa4*!+{1d6V!6plgZJHjPV1vb*ue_j^01s4kN4z8
zCj%bJu&cVOi+1e>Sw`BFZs05OUNfR>ZZ2oon>>zTKO0*U&$GW(zbJfcp5M5U!6p8&
zY$<z@k^@;yAo-`jXPks?*9mi_87*gADdmh)x%~t6LJG+>h+AVAq&8uo0g;2*g>-j3
zu$eRoP|!2+X>XgIq8zk9`xS=Qm$MI=PC;=mh_PT9?{o#~nE%;#pBx;e8<{D|3pvN<
zMp8!_70LivQ;tuU9u5?1)dc|}v)a1{Q_u4GqOpxgGUkPcY}KeJLSDJFv1<|gw~t~a
zr;mO;4gD*H@|2>i(G3l!KBFerbc8ZZ8$H(}RBJ$j(^K2+#YuNmx$pU~<7zs?6VkH>
z0tB<BKB*O6WNiBYS~4;LZ@lSJ^nWOO?`XKYH+ochBT9lGk)jhM7$Sloh!%CmFiLcW
zA$kjv5YZzTf*?el(FS95i5g`Pj9wC=6A``NGxEOg`rhBVYu$VOVW~5p&-t8lp6A)m
z-uqbdvXMj!wAlC{%#Mr(NTXMOw{FHH_Y;citEImyW<DvqlwGSK$7@hyi*f4Wr^fex
z5lZea=?G7UthW2tRwsdLG~<CuMpQEl^{w0KMZ+q1qk++GN&Z5VE+1pk<i12hclik+
zrn=Z0!mr3zBp;sL^mZ{h=ft8`&nH6|JMdx-f?mFUlp<l6ZL@x6(@rVI3n(GLq<xp6
zY5cykdbLQQQ&W=WoYSztt&`ulVmR`a!=`C|){9TOJ3iRk;VlO7e7Vf}j7nEO4fz44
z2SL%yU7cB~Z3eCnXH@4x;rz#2dSq45v&A5DK*FVK5yJ$H`Q*fif3ql%ZX#?+mO0bW
zn4!S1zvHlcrJQP-xqfLaoSbA=ctW*PJ)xe{g!##iGS9S4<G(S58J7Swyy!cv&*X9$
zI^wPi-UX=?-(w7Bngh&+qY($8CH%vzHfIzv=OU}NZN=K+PkvuK(POdQ#7IF!i%~xa
zYHkz5I1Q@Bg>yU>1w-x9Xo_bluGy3Bk=-Y0UwO#pHo5y^Eh{Dp7TqPeU0Gm9^Atn|
zokt%7Vp_Q=B`cjR5$nId7`7LkI&osuC>+j_T&^JroUs}|{sA=o2HudjAmvSkt1Z;U
zda$W{s<@-OdWG-PS|OWm(^e4AjJXuo3b}FtoSRzbVCW%EgTeL+1WMkH$&crMqoi8;
zELO7M?HdN&a;Z-jf9k)Oy8==yaG2O@22;q%SiASyk$0e|N4w&XWErsOo~B<;sq!Rn
z%_hi+v$L-5KH_-++P!)fgd#W|VKHd7Du*p@1;Lp);9oqZ@3Vv(0vO@X9jHQFvHjj4
zW_?X)$!ya7KdvKk);V$fr|mNn>8x%L$r*q<_IEvx<*;_oEaMrzNzJdGVc?F~$L1mk
z={fVFd~Jpqaz#q8mj1Sa+I!EAb?hnRo(A@>uS5}?HZ-Pq9&20gu8AqInk|Q?@zcLk
zlW=sp&D6Iy8dd|*Y!AdgP+Od41JO|CW7H*HrJFjtx&z~kA=5(S!f?Xu2J8|q49%Z@
zDmt|Kn>N4Vq4xwpL)!J~J0ItkfrN%U<n9E+8Hr_vyu|qJkr??&8nCS1MG%w?XqNwU
zI-nW8UA#<qQY;PZ8Tf<6`Y!?d!7)$AK;1JXJfPXlel^v#N&t52cX(c0;zjx_&Qft2
zQ-~C(uc#$D*?-#@0k$R?vm3gBkf+K?(7vvoMi!7=z%fT`Ju7a_9KZ8rIAqCJfyx>b
z+D<pq>_o`v?!Zc4RZMzM#A(TsUjs`Mu<4W#*e9{tepGE^WzC1aQrGI`-RJRt8Y)+u
z>qMD*<(8gPSGoS0m2r!tz6MfSb_G)?(@T);a_Ji!MVP;Nlv?C0qTJIFNMeQHIu2lX
zzyJi+2Y7y(Px7a`-g-yd(A=;35u{A^funEWH3!MUHuU=ARg86~!!-#K6lz1Uc?@_7
zmk{gN)h^_`<1Z&;IGLKc$lY4+C7a>t;p7pm6NLuZBgg({f$=BKCYF7FrP{;0drIS5
z4r&^2$9+jjOVs890&M>xt+yWOVGVb67}mPXNW%SW$@iq?-V%zILiFrT?o+(j9=+%F
z5c5WKXROmLY>h&3`HY?wJ<cmF_5E=Ao&1bg8tl6GP9MZ5=Y;{D5n4-&OQ;@<C9GQh
zxUovgQUMVN`Y$R*GKUl>|EXiZh1?FWIIFo@mU^k9gAY?OdKu)YdJ!JfOztpC0bXa)
zel`CIazV1`y{}7sA;{gcG}9PwTBNHkX{DVcBUyDD>eoU$VF+J(D)}AxBq!sp?uR$<
za2y<cXK6g^799~g!3j&zcQ@gbBA3l)9~~jQe?y<j+92~&O>6GI65Hj@N(+}J;w9lC
zBss{Us)jm3Jtp>U>sFyg?a%p2FrxCF>{h4sFI@~ScQ;a~YWpBF*ZBmx<YH(X<i6^D
z0-~79yUT)ORtFuoRFDKnf1})3IPCbKqun<RtrRszG8jves*2rJZa0vAjCXc^I0Jex
z0AV=U#F>156P*!3RtSRK-3gbl@tS`{Ar>IF>J621D=?ytk013_Qh^M^!XBhYs2~TI
zV5E(DI$`LGW43fd>QC$ggo}(0C9p$X4^D1J-sb-gr7N(sdY@*tDXgvD+mh5(xi~y9
znz!EARPbQ}IX7~Q3n|f=4TP$u5TO+vA1M0wZ!4_@lh3`5)v9d{ZoDqp_ei-0E)n7z
zU-0D3@dyv7fJ2ET&w&q{jNw<X=dm;(w;;5Pd5MGHT`lr43fIY%%m@>f&UFI<`SHyb
z8S=Bkgzw#}+|ic34q#^eQF*<)-%d}t>cs7H9}OS&=cPak*aJte#ZZy-!=0->u^+|A
zihEjtxxQln_hUWxj$RDs1!~q}hhY)nkITVlTtNZu8Kry}Ver`FCV8g;Uh>f*o5uz~
z6O71sreJjpo8Nvwqvm{X)`{VtnuWg@?1E5WHRpN`-~}q5Ztui=Nk4Pz{w90j9$t6J
zGshWGs~B+7nUX!Dj<=kK;6a@z!YxdVPQ~1tJNCi%a7i2CMW-JB+<pn#7`<Rpwu)$e
z2(brAO59Mlv`G`9s8=fT;-8vxIA$swvT}$GmKZ2>ycYdCe<6sp)u8=HM7P?!rO)ER
z>FK0I5cuT&2d@f&zs?SlO5C>MK-WqY`SJ1GN*BrXn)VVL)*9|JWXe`mIahb5LC0Vs
zPZjCTnm_CtN~ktig$%m~8431ptcr9x@KwHU6^q%u5_#+`TrCQY4*CXrin98PiLFG;
zuwfOalf2z_{f0%yMfn&m3IX7M9+KfauDe8jsPv7^Kp>`*TM_P%(Ar82{aYN|{P=5b
zsKVBvHwHCrnSr!j2XNN9{RaC<+M7f<wJ$}Zk5zIpdhdPnCh30S?>t#?W6|aj*l<OO
zAHvQib-Jpq9qJIg&&fe(x))lLN%d!@H_z=MdT0kT1p7@18+;P*iTmRlhlMJD0qn0x
z^@-fZ2#(z}PMAYMI~A^k+k<6GFBqI-+La=6@)kIH1FyZbnK93K=(%~-`8yh0MMwW@
zKP)jdf9cSx%ye9v3e;48@1(mbWE$GQ(t2BVBuocI5Maly1HecjK*WELpxzRndIRT0
z3TcTS=Szfq&8@xHh;V|gY7AEW@;_#wS$VhDpQ73blh?N&xQ2Z8Ay-6)sJm~J_F>y6
z&E=~N3Xw9aZ-lt!WfPj-JUmL9ZcC`ugGafaya`k9HH%r)K8-MI)=L2o7u4l0lXJ1h
zo?Q<B)k;|V0@(b;wwwV2r$O`+^IzDV{+r?v)_+sqe3(VVRi{%|;%=B~NqQ)klGgCI
zU4X!P#J{CuFTMKWQE;g?A76Kq1VZlagkg%euTL~%vsSEn<mH&F?VS9J;!io!xYNHN
zm|3r8kL4xRhK!F$2(ISyi<)UUk7Vf3T?P3Sl}aw?KU+oY*<c9}X;sH`I|#|>cEHC4
zK{9&QP#iB^P@FgJW5_hK0bG_2QxG7j|F0DWFgv-JM?r{6t>GkqtwH!{u^Bm7<Yaac
z&xR{snq55yNe{m+Czv4l$|LR=YL(EeEMyQrR4N|ZaZJex;@xH*L^c0z$0JJ#KnFd1
zAenF*W}DRJ!!>*{EGCu`ZHYhRB#y#^-Ypzv5lRTACySl|$%=>-!p~S6(F0?SX`Qao
zVOnep&COPU;+dq5QM=&|ba@u1%3#2aTj_I5b@px<#<>**H;Wdm_K+Q-FvX(Ft}jq1
z6Os$b|5P<+`MfkItTd#lNDypWr0Lkq!uXo|j4r4RD+)0M1K|K#EbWwsp?M>^$PIP6
zpvZ^g)dk`fezx-l*kVjVpn#$Lw`!Bmjn&H?YL`U`!<N2?xLGLVGQ1f^8wokoRcR(a
zq}#z)@*7$YL%=0bOWIu}&2q)TN&d7#Fc!<m3dHhis)wkU=*D}>q-Sm*_?nW?Q~6iO
zOLZ{y6`Y@A=vMBN38ahgM~5@&?POFIK)~N2_?`Klj3Cn031wV#0Pn`mWidx^IP>2<
zgq+QU!1<41I;|%?`hE+41;1b*wN&0!9z{tKCvpI?4)Xqq)27fes_1+p3CZ;pw*p&}
zV3L5OgoRK!IOUgsLzrFbkCv+KiIE}WrGXr<TF_P2!##_%8Jviz>X#&$QEHVOrMRT;
z(^;WDhSX2?mWlD*jAWHKDBY-lgO-)USG#7NdX{0&sw>Qh54T{eVvgIfJ=a*sS9cQf
zUOeNS{4fBEjxYa7I!$Xzc#nvAZDY1<Nev{St|G)0Sf4d;^4OO^^Czn1Vt&3*J~ePZ
zx7`8xJdSN_DCgFf0?)xK8zvV`A*`lQy==2LN!DpxINqEhP~|^Jy#?s3Bs;ix9cBJf
z%r+SrWrNjP_EeiyokmP-y=+X5DXJB`{I?Ld#trEl0Y)I&0+>5N_f*jR@L?wky5ll!
zcN&mFkAfIxhIR^`j72@7QvkV;*E$q^H|Q)66;d_Bj^t#u+{`nU@FwI<E8EEL-&GGS
zisk*@df$%uf)oy2HzqiuuShswS(Rw6mx46)7?cj?n4q(j<f<U*EZ*D-s~Et}!HZp7
zKM+9elYu-1`LqTk*q1k$zo#3L_YJP2$9V+dfx;zP6Ndizet!aeW1)}GI^3NQej@`Q
z!IZ*}9=ny#i%R}s3+6JBty0$z&Q|nCZJT_&y(G&ZMmP0Zgi^I_FZLd3GgA5l0&z$x
zQHvjtkrsI@SH*$3kS7ra4^M$hg0P<Hie<<wGP5n%*1GAZ0D-R;=eRuVx~1X@%(;)!
zl?xzwRDM7<FaUI5u<VV3coP*Lv)-_;W5n7N*o1=l(!?>=O4qk-mH66_oS9wZ$i2N<
z)-c?67dnl6->ldyL#+Q}aZ-6_{+>{+daD#cp%5%nsu7)60o$W4uss(O|MKi>r(=$v
zh2`3NxuA3Ap!8d@-l*;VPQpt5H+l5M$e_G@yGvzXyJ6dz4T8v9zmpiP-lIc1RuYc$
z^u1QL16w~{yb3fERF&RlrqMC}SIEh%^7_3oM+ukeMalGO{#`JyE!32qwi25k)7c=3
zi$1Kscr=5Zete}!kc!DN%D;jEBgJ*AvaD>*i{l%UdHp8?wPwq4sm4p%$n)7}f}$CX
z-rID2-IEGt9w{Fe9J*`LSTbR~&^y$9QAX;8npc&p;YAfKHki*<Z~kYR>ABkb&(F9M
z1?D>kr$uEh)RhH6NvTlPUK7JVz2P&U-e(@U#HX^A<H|_J4;wDM{3{pvb{V@pCYKu<
zA<GPBzv+JpH{?=2WAEtJDNj5#9M=4{WBlW5Shsu-f}lOT-==qX&wd4#_k?eD%@{Ew
zg7CaVT-JJw)w=LIz0-kIgT9TQqP2@>LL|canSaE7i7d4A6$=M+V#|r_rqm#kc`#Jz
zvx861-3MXPagT6F+un+S)5g40k%Dti|ACFVd=Eg^Z-%J!ZrLOR$&WP|1?96@zX8=h
zfefdthG;<EVwk4$JU~@oJgqZ=5@1sZ>lj&hhF*XH!579ETUz`8oO_~E+uK?$+hvu=
z!h-0B8i0CuwUUBe3)N1p_B==Fu^aczZT)%c(F;mFxb@y65J>GkoV4Mx|9nWupgko~
zJf~^b8S^c{61UUT*XHc2nEgffP>SBOR<ZXEC2bI#YGEdh9q+6@1FPw#-*8qhxDHyp
zM=hYETnBgFM6exi*jwvSI2>;^@&Grsz<cV(_RR8AV{1vJM~^qcq*&A&<HAUF??IWA
z)|wb2o6GyDtan`3W+>s8rN&MpW>-Iw`bzf=7`g@3#-AO~R@6N0jUx<x@qIPo`U1|+
zFZxMKFYfgL6UiV(M91tyNk1IVLA$td0D8pn0525Vs?i86n8@5IDcz3a`08|C1flHy
z05Zd_&7XgVBuBp~$w)dT@aXfu)C2PNncDD8R0UP3<0Ct)p?ZPOf-vjTfUIc1B<5jM
zxh&r2_!GvWXPpT-!>7vTZ&nVzvKvLQw$hZY%dQ)rLs=9lKeJ-{>ecHQOdz%vQ+a_S
zBSiOF6?mqz+0pwFB=(?fLxUy^Gj56wOXmmRO~U8(^f~Ut;c9|1Qf*x%1RBhEPA0g!
zzBa{JC)PHyjza*HvsrFq*bdC$OlchyQ8+3sR<`j|4lg@NMv53hOLqzFJy(ip{@rHD
zov%QRwr}?Mz1RZ2;=H!LRLrens;jt!i#X)Mb>7Mr6!Ry~A03xmP23MZum}67*PWy7
zUgLah;~>x<<AInHq`d}<EnvM($*S#bI&8fwIwt<n3tKL9?1D{QOyIQLFNgy5?=_!K
z%gl+_3X0C#GgQ@J%aTQsUVhrinDC<G00o3~lK7vjJgNW#ngL2>6hiuUD^y&1bE;WI
zNDFVZKKIh?!du`5D*v%oA;ZVeas5!-qVx#Vk2(Ie??K*`4OC*_|4bwZcZr82N3*s@
z<LGEUQ%N>xq1l?)zpYF-_&HR^w@2k2gJV=cX@H#xqAMrWIFb9qD!?sQ$M<8et6|TL
zoftI(>-Jan-(%N2u#^w=^SLySdJuU#GHog-b$3F^+iS2T^yxx1dmS@PH9J6|H%Go<
zKt$ukncV;3&xE1juC{s+*9Rr7Rs|nD^|7lLWDNF8bQSlqMi06yUs-krMd$p!*X&?Y
z^`?k4L~xzrg-7xu*GLJS5Bh7a2JwB^ILcr{qW(Xf3eFG`sKN95ea47dE46Vy1=dYM
zq3$Y#h&S`dq0C2g5<oGN6Gz0Lz6Oz8f}zAvy9s4$`>n$d^FaGYi=7G~oQz^+$cZ(-
z8K0W*S(1we+X(rpy&c~)k+GcqQDTrwatujhIhi9Q=#`zo_bGuHyK))JK!Vz-epY4f
zVe86U&=WUe+@@4fl59ZU;r0!Q77}!pyaK=XNtDgV#)w2iTH()Z!e|&w4p375-FWc9
zruZCoHTD1=7#=^~<k%47?9^A*GqV^=Oh+w&qZGh_Sdc|q3=Y{?8F{%S?zP*uMcN>m
zgtphL4od7TP!ykT&Uwijt<bo>6vuFQwX{n)=8Tv9i94Y`x8C!0T#%0h7yau*fmXX`
z1Jb1tqcQiA+ye$B)SrYqN=TkW*ZNl4>CVcTm@F1=$_7mBJ4REyNZBooDS9WL4*qHy
zLf(Q&llCAs!CRK8)<Qgmj1iK#M_?j}jub748npDG_0*n5y?+@5Cptf<u}S!uY=s0}
zd_T;~*-i!*;SVhzALRn<2a?W<|9Si8O{jq5uugnp({|ppt*An)1{GGpULQF$WLwPq
z<|Ztf9~R1glk8@6I=FO)vHPdWawC3FYk=vq=5g?*<fOua!Ka>+>JI~+C=>q}WWk|O
zu?SxrrZJD7_yVr>7QWsuU7}_&B1GYa&1MfO(neVpcNNTO84pE_-B(A6c`Gg5Sx^Uv
z{osRpLGD#n<5E)r514!FA8a%+Hy~d%&VM81udth#L3BvZl^|DWu}ebh+#DMGLs7})
zXE68hW8QUrSg=C~z*b4Sz1~5jiQg%ct!sF_dEUxMK{@hqPUNdRx2%;i{TlXu#m)8}
zuf#Wd0vP=Cd4P;LxxG-#<<!kp{#lNX*tg!bmx|}O8+w+92(xMIM)wJLJ<KqB?GX|I
zN0)T_^I6#0UU1W9y_2q#yCdwe?oERA=Q9wO@08|e-86%)e(Qtk#-AeT6QQ+I9gsy@
zESE6<YKxQw=3@R*??)5ugvNQotm$<R9*Uc(1^kO=jLKU>6BFP{rz=uCK_8`|_?^>r
z3_3UPY3a8()4}fk$a`U&uK(Z-0Ew&dL?a?(CKN94^F2EqG2eefMH68}iv=eryM-3l
zZlof0cTQC@EdH|6DHfYWRoU45V*AoN@ahS*!mIX+oc=|>^A_o}vbGpR$(zSz(hDA{
zmDoj=2h)#==_LG6t9K6}Gl6er?$+7_zJU|{nGYY+gd~%)tP<`H_U~~^2oG;;-iUmJ
zc)qT)+A+o-M2ZP{D7H(uYi&fjhl#hFbbZ#pSatUoz{t9yuK#n<;bm~>r>hp=q(h?t
zRI|*5008&%o1)9LzJ^B#=|(dE{+Ef9x}JMf&X8|%-n%g5h7GGy)NHZcC_hz5`Qd}!
z`imBNJ5$jO*H&uA`Qkp>k`nk;<RoEUXWt3d4@*_?mONKuo+dDB4-O101Ts%pgeD=p
z0v65z*T(+<D?v6v>u+h9I*mclyU(973MSr}O;H=JNTjPRY(NWf?+@>VHn#FVdiv|n
zWxD6#hVFnx{uHptX>j@v6)H3WF-6{^J0-H~e&}z^{gzMv$yzyDP2)j0KV7GO;Y4bq
zO(debhaL9%WWaFt*S9AlO8YtQo}k6)-``eNYv`7SBZm*n_eCvaE3^>(N+ea6Q?`+a
z%t<<jbCxXBja<2A=w;>|e&eiN*I@?}+nxT^{-nw%58l-8HJL&b_D!P1-wC=y9OI>a
z%EwN!9idrXqm8o4#{!gk8<EV3C(vxk04^8Z<d>GV4J=Gw0H}Et|E~sN>EY|rgO4}1
z!{a;(B&&T5rXh*1^F4;!*A!uIAN_+DArl%f3<%HwDHeFl0mWat(*n8LhQ4W6OoyJ!
z2)l_s+vR2-9BjuF0-h*_4{axD1YDyQo($P03B6>oeayB-!M?QOcFOAJ@#4$v#=?2Y
z_mUh}8&n4`8%hHRFFwZ*rDBop<Et`cF~8(<O*#>^Xqi2qFd?c=>D2#7Us*6cwU^Fx
zU7=t)EgjQv9+WD~jUKGK-}RS|y*TTg+$5O{G&py9?1;n)w_@nNg}_ALe|vQR;>2qP
z9Z`SzKMEIMn?5KD#oR!)PIjJGi|n8pc?+*zYO$3R|JnB)&oo81D$_Ti7JAlkp$~IX
zu0~Zv3=09*ow$_qQs+u@Yu`CnLdovCr|8=yf6&`LPQHjAGprJ%t&RTUR=#3_X3$EX
zm~VLt!8JVqE}+M1vi$-_atuH_Wc2)C8a%~9v-}H64A`Lg%wkYqa4E|{KO}gnSx7H#
zW`QI6Vo!lK1PExrZwq+aGw7B&Mg?H<-p#n>#0{`WIKxeaOX?T^M}<kuxnt=h0Nk?R
z(D(=grl}}p*ws_z;UZMGepaj(Gn=nX(YXbYcE;ICpJXZX7=Y4f(=ZLRx;Ls(zcZKf
zo~QKGpY_gV-qq`7hk;YMmf(VGG$h|rOAYF2cVWlkm-OmFuxJh#$9_zFW-f&9_$uj$
z9}OC5S?P6vmO%B(eQoTQRi+n{Kae>3pS>-l4K<ucYbL$DQ4F7CRYx5XoHb`E=GiM(
zwF~B)Lq7Sa>E-`d8U@2$38#?@={_LoKIo4s?FvbQt2rrLHO1d!&v7C}^ls196xj9M
zC{BwKknNQjYbx4&VK1)2UzUbgQTMKbGJhF$8^5w+=WJ$nD22ZHbyIvZ_2aHjEC@|@
zrUcQ#qLI-_(}h#Ex*?-@A&YPK^10L+q}I;wc!T5GS#cOj$o_L=+D`}jo-3uSY^HcA
z0EX)dUg#2pp{o;GDr#*-O!2faqYI+i$gmp=Cz>Ub?LYC7GVyvjrXZma*2^O^I9DqY
zhRL}Hw-mr2z^O;X>@L{kb8t|x2?#L}4B10ka}%)!ziX{<gK&_vghG|HD$#mra*zlP
zX*+R>q?9(l=dO}DQ&Kl%0xrKrAZ7F{qu5$q$lI7nMVi2DLK;Y!-R?fe26fD2&|vNB
zZ&&u*LU88g(PNUBY*NO-B@vz7^B4Me!b)?8ZJ%^yT<h+l?6f>-%PO@te=Uea^B-+8
zusiaN7Da{yAZo|kz7^6|q|U>DbIlTBy^Q1E2Ys#seG!yYIXj;JMB%fh7CQNjmw*iL
zw_&CYT;2I+?4!@u!d->S1rj8W<MdBr5W4N*;nyvi0iMPK8x3=EPs~5ui`gpXkc@Kk
z4djQ7E_H{e{+f$10)~UGwtg!5IW1|4CbtKXgyP+WH<_Nk3o?eKW~K##_M)ZfPa~=R
zM6o(FJ^@JRa;ZURKGS_;ax1K|Z!37gKY=?KNHSb)Su<%Zy85a&%C`4@kHLfZP*6fY
zD_Xe_uVaYA<jt$hT(s^=x<)%d<F0bw6z{_Hx%G*w8D~6loWMkCwIpr-TZoY^2Sdf!
zo@Bp63zgW#zC~U{VzKkngPqpLKm+<Jicq2_+nDwm-YqmigH?-uZtsi{LC<q5sv!ue
z>H;OFBxfm0${G->8WODM8|}p%>^CxYtIdnGTv^M;Z3f-U)2mgg6PNe`)tF;wvo{hx
zdB6C`GQlA^c3&`Lze9JA7Q4bo=H`p^_>6V}`0+$uHT><QD{i4e;4<581s|*tG^bmt
z7zoo3LGI>ijrtI?&1aKf`$YdTVq$QsJP$s<Gci72(61}VL}$$j0gs6+3t=-@6*i`7
zwiCK(!*tuE0TKR;y=uhnCTf#Vu&vpb8le)Y1$N7VX)dp??^JS?f4{@&>+5LA^jF$Z
zORyVpY)n+SiXm6*kyLH6torl`>nWKYD)uT9Hew;Q9fkQfP3#b4kPz_A(5`cx)_l6*
zKwJ$)R6Hy*Z54!Zl!9zK7^<ri7s?Jf5qkXJc>WPiBuI8~<S^aVv@=2nB-jR#x&_)@
z4+e83Kn_*2$<oaSSdWh%1;mI>8o1iME?qyp{gj7i1qMrRg+G3RRj`VTdeYp`cewGX
zon)F2db23{aQ~8J6*Nu0f8MmKUZer}pb-<0k}x#8oWD45U;Dbt!|{u(r8(hJt7|)s
z0I?)~4oH70fWr*<@MRkI*N0^d<Bh`OXs{WQ{q7I$4)Up_>SJVU#}2k0Eld7|n@N{L
zp{e`_bRq|oH_lzNu+H&Rp<~oHX+{XC2GFWEAot|If>s2T`8!EPRLjN9>Knp5wCbDS
zyuFXM39MHJ7i}0((wkO_u@#!%$td`|Zbywz2v;3+K5#p!Hn13p9ZI6R?;ADIdeYLD
zt%w$@c1aIeXg;O<CPbSU^4ebrG0;DDueW4xXIJ8@{SQZatm1e@Q)swp_Mt$stEJ>%
zh3#sF<>0HA@tr66DWh*3hhqB>hyp+~<)<Z!s>JvVsWt2F0b_xqRG(SqTUKK}--VJZ
z_&@4Qj7p3?Q*?ti#4ED73@PhB8MDhZ0s(j};>yi2TZD#c7^*`)IxY;;E$>#h+axL_
zU67<XE5!D8+i=Uh29^CYO+1hC>ApU-iwi4_L(MWRw$Z{sxp1gIQ+;+x>B^>at3AL+
zPU8|zDb32ZSw4QscAUkbl>HkQQ?=7KaZAtztiJ!TT*LX!M7;5Vu5PJ~i#@M|;c?J}
z1tkNJ+5qlll&JoqG6Odset`0N1Jbwma{55t3#CEkAUOZEA!SMP5j}B-37rC6Ca<8Z
z?uMa07|G8WZK;t5wb-LwzNA-GUOKs}DQe53(mMNowz5sI0!k-0qk6ZQn`#viU!71n
z7!htdE7~3nRC{q3C7*XyeJHXv;FN=J8pv2WvBByYvG!umT5c=xZ#oaP=J&s{yKL^4
zykhnyLCj5xiN!HP)%aXbQ;i~fR_#5HYo-wDgg1?S9<c_1#_{b0t(Xz$4933}MpiG*
z|M0Ku^;XY#_%8$jh{YIwzj)Iff3I{QGw!b*{mK1Vvn+|}BE=7LPirg4uF4F?xV1Uo
z9POaJ`TCQc&gPzT@y5tP#;gXEcD6nn>^Sk=_AtzJ=E>w%E$fbXAF)K}T>+@G7~eT)
zYm<+|VtaJB#@gzgS{7d}o=Zm5hjx^%xnL7b9lNR<&6m$bthEPCTtV#DSRGP9vw@@0
zcMFB?TmQ0_{vdAz@)(vtM^kV}mb2vu|Kf84Hxgy&S!%g^3w3UD0bL4ck-ZZ)X8**2
zWzVe7HUo#=B@6IM{IE>t-4#Qu-Y4mnrZ^V>dczS%Q>_e+A3g|RfRn#}WMv|dlVzu4
z@$*#DwcxYj@ABr)%UZ;OgUZr0n5^t=0s${j*{5pMZr)&u`!a$=QK|>@@Q+&$oNdc@
zrgB&>SM-0Aoe$*n@#VAp<*y?_7`629)y#K(v7oe?j?C8**hux?ul@;8*zF^QRBGEp
zRAua5&xT)Oc!k4o$!X$y9WI@MxmA!3RpHkEobJ{cF5oy<k31g$ZemcwjF*Kg2~jRZ
z09gJLsrTgIPwr`u{U>zHNS4+%@0cw&5X=pjQY)1((KGykpo+STZLM=A?7kVi#}j_5
zf%q7zonnxpo#nkNuC!dzT!|RJG+F@F;vAnDx!pb8mz@OCf3Ns@-!FN#S%~C^;Y>YJ
zwWABcyN1h*SlPQI+o7Tk0D6_hV=9`v>tSMY@QERM7MWOJzkB-aXcOQoy9m~+y@EoR
z(4IL(6hlIGEF&lPiyPE(_0Q#nNjHXAst^USH_G)XWn!~}ydRJ#a%qk&S(Z*;D*X3>
ze1t<!$L8@^FP!H+(c*S~<C6LGRU+2f=rvq27;I*O{+F)?MMet=Bzm;QDqU@I3|6UH
z+I(YfkSbIHoYO^(qtdlR?ed2Tez_yeELgflYJoUpumM9XGWQiL2&@h#Ok<Iloyk1$
z`B>ww0ubfsv6$U*mtPcu&g%nb`YlWGl}U>ndg%CIIFUa;h7<}{V{m+%l^DFU*QCPi
z^YE_;GLRHp4k48|kQEhVE>3@+GvB=!`o~R34<?`0epSF{SJK@Tw=l^BaE?<iT<r;>
zuP#>4+8(9PmlbpD{jxJ7kyW#>U2SL2P33U*{oq2daW3*#v*DWjlGlVNqiWjMC!gRX
z*nt66%-$#o-N@;fo%dzO^~x=7dsAppYqB6{PKN;9g#vFf2FM4j0Jf{A;yLT}T@=>}
zdvi1`06+i+6?v(vR7&Z}O(n|=)w@4in`Cn{KY60>XAkE}1oH%6Bu%NbJwGQrMt9BL
zEX8hc`+nBw?XS;|i}J6)E<wcX>6CxTQ4oKS#XZ|$zN3o+&z&jPKBsETVJYiCNB!C*
z!dR9vhpLf>N#;hLP{^pqxfVEB!<{s4lR<E`KsfXguSFW*eJ&}f2FGy+=Yn92GSt0|
z5`W>;ENp*E!}Ymq`|F09!dk(Y8!Q+O86B1EA=?V&=iHW<YK(#>3oIgg(-(vsGhO|^
zwuz?rlT@)GUx-x?a~Z~}TJ8BWJ?R12DorqNHRFR}Pabzkzm(r4=5sui)ndezJ~=j$
zuB+K6uPD052mKdN>`-gev%8xeZBDV>_ofp0%kIP4mv@O#RL<vXVzb$4n0~7%4h|10
z2X2AW5C3rF6YJ90|D|I?tVC^cG(;0B{3~a|%tPjLk;Bg-qj-Ux2-Ay@#Q9E3)&rds
zd%#7s&x}}@A_2MPV6tb>!`;;l>$u>=ym;kROn1ua>n5SEO-CXQK;yHpy??ZV<#QGE
zALQtLKne6*!KjCO+#k$V7sBJ-qj}jn(VC^AWJ;aKq2GQ#kyoI^Tn=CZqx0ZsEUjrw
ztJs~|#E4eIGHNpy>5q%{yM;e6^wC6s%C&v<qwQzj_zReZb>Atvjn>Pt`w}0Ge1Mxz
zR*VWD!*fW?X@0L_*VhH!OOC7CKdNywx=~(aPGheM-vj)wIxk3cG0v+c5^kw;;$Ph(
zIbxGLN$DI9Mk4<Bva9SF&IWG=Gbfi%WQKhMEcV+rNlyt?52akH&bQot(zaJhO`~)A
zp&Gi^MV0!J4$>T`%{W@Pr@guhuRb)R1bcny$`dS{*aVVH$#3_ql#LxK3x`XT2jeh!
zOlQEK)vE=e;bpS9qSO}3w!Y^q4$trI%ARvF;>@vJN^$R85z2%X)e&L+_4JT}5Zj#d
z|KhZL`r6kXkaV;I-ySR!guVfF1IC?4oYStDf&BkMwr6q7*J-2r&Rm}gBNR2WpKuMo
zOs6@dJUY^(qV$%~P$INS_DvGxQy<KgF=$>pT<br%{;3^G^04p~+c$c-J^H|f^+WgL
z!040ik?TOmIwdzuN->h|xcxyhkv6YY;8Ct<n0D#X!S=_?6hv(6{<0RQS0tV+2PI>h
z%qBQY;--O~Jo2R0>@8q{&JFY-WS<%VF}m-Uro;aT!BLV1C|vAGK?O>><!J7DUFu6;
zUkDm9R4MBW>|kW|>JqRaj#sGhwAde}Z6~?qpz(GX#`)N@K+8)OjFO=cvKh9je2P#W
zyZWldli4Qe*&(D&JDlHL^o}XS=z?<+c1S;uj&8>Rt``*)xj6eW`lL}L5d&0!64|K3
zA+%{mv2W7yG0dZsyb~bK0A+Ki?dSAb-QlABbr>kkga9}*K3pR(2NI)`v3&JfYVVWB
zJ(N5+cucRVqjrt&yT4!}t4n%DlA8g`n&F=|IMEbJgq_bpq%S3cM7s};zxD!*3aP1d
z3?p1p`%;Sr!b^LT3!F2$P%*EvLzu)&R@D|)3$fLIU3_a=wZ2@ML7NcLz-kKlu$`AX
zY8Q?vffz1t+upAn*8@<k^i}6J3IOsBRw<{sEQQNSu1q9Lv}%yt)&VGeJ0&3aC18d=
z#r4xX#%WnDgAQHw``4T)mpG5ptD}=WzW13JT^&WugQmdH!!6q}-r@ug(MK!5nn8IT
zI_~KRXar<X9jV`lDOIeXl7s<1z9nwaP4i+!@NrWJb2q47s$ZA?93#liVj|9pmxqtg
zXZ<SY{*ttC@9}fK=zFLY*lAZBl>#6OT6YLgxZ-uyp7~Wn(I*NG2RJV7Qq4_~+|?HL
zV3|nK9OO6e4VhOHbAIpr;i!ssz;F|bfcSffye|$Sd4!Sx?aO|sbla_ZS_kmBg;<uE
zmn_QB62h8?2mhvmdX5}-r$j0KT#&Y)V1r#yjL-IU<o!~hUlNs7&Yn8G@=`bdR&tFh
zDK@;f31-Iu^86zxP@5YzD$v?$M8rRZxjzM~oxaZSJ(k7&rm6A_So$Iv_hZg2HuZr+
zgwz_Em^-q8Zz2SoJ`#rFJ3o4cG79s{Uq-rB;mPD4tS8+obOs1A#TPnkB_BloZWHZC
z>s>W3wV-RnNKgBUyrIQ@`M*iE&IkygrW1-zw0--`d3`57fedJp-ia~xUg{|at}8;i
zlbpw?4}E<*JdhW5x89AeHhC=;A}8iPw%gP`f>Q2NACI{f_76u;7B}DeAo#?g+klq&
z<s(KZDf6z|bfFi*HE*rU&u}HR-MIm|`tIJJI7DH;{3bjI$c#kzd@BlN6dWU?Bz|R3
z1cpiQVGC_r{Uus7HxE-MBT-xm0x|I)O1C9}IBk8xqAkce0wI%^uyF9^!p;Hp<PWv(
ziM%pVQEFGIt>tP^!O@ddx)%)WwuE75p6nqET|TIkPUD8o0y?|)@`#4p$CDoqKb+H#
z<dQ#`55JfF1?K9vfkA!9e2+YMlG0T<<}G7s+{B+uM-&wZiKgGfXi7YP7T500Yw{1(
zhD?Q2n<n3$M$PMT39h4L+8g6-H{LTtgXP%Tyr&mImt*gij9~qI-2tt9j_m}0$BGe<
z1X&_#LQQoS*Pk%u_-<#7GM0K*SB@Hj<D(u~95cw_Ye_8KPFj}1@EIBcIOSH!G+HT?
zF#W+VpU)ra+<Dy$6qz7Qnn8(n27|Xw_qz#!PTAevQZ+smQQKZ1`=%%luU;(mLm}Kx
zVFPZO;>$ej;o`T1rJ;nrq_|c)*O>wq+s*2d=AQ7-+LAX&($Hp1<3E}La;0?(@bziw
zZ*K1GWS)+HW%EGVKa7x=Gp`Kwn~txw3z>fssJSW%q(Bc`RXWUz%7OWY>w*<z?l318
zMJUZXkQUwT9*_Kn`pRCuz&a@s3O#fWo6bAj;$}+(U316lWm^RoT0PYN_~S}KpwdzP
zt$;d(skDH{=V59woN9D$Ko&mHYCPT(t5-Pq3bbG*a&nb-cR-X{Kv``bmWyleSdR6}
z9iJGylYDT7?LL^v|G?-+@ez^+T*ii5AY9%07&b~Arfg=|?UyuzeUfIwe9OhzgD85p
zg<_#K5kD18f|j3RzNJGe3||L9Oyf|!0r0%*+GtDb+oA^QA)$mklHE7|B6ed?EDvhd
z-#GWAg%Lt<5*7iSm_~GM1ZE=kkt03q!9Lz@X`vOfaVSm(jTu<g{Z#+EB%{C(``?Bm
zjfIDjp^3BsN29Cq#{1%*?`&Y*UK}e=*s}=5=L79a^zFkH()x5hi*D^x<axjqI}q5E
zB#gX3xZ@+=&<Bw&E%TfJ16a5M^E}mn+-bn%wQ!qcEDgf?W^02;Yr$A2AU(nX;=lAi
zz7mO^ljAzC3<5axa{GX)Ykv%Y-D|Zo6O2H2Mb0Bc28KTD6y)*cv{yGVzYc%z^rSiy
zW)r>%)F9O|`;RLPjrD2|7Qbl)K?ylgwdVDJ+snMC2eFdPoo2+Eh+vextD=4PBclG}
z`+E(i)(f2Z$Q*|3NN?|r?br-%Juz?^(EY)?L0DIGC=CG-UZHx?`EWP(hArPex*FhR
zqYpIE04oTBLgH53_1qhw`A-&KyGSbrh&+%+EuMaxljnX=?#jh+o^++f#}8-?v>6>5
zWr)2Z)cgH>M8vs%t)?&N7dzg?q`b=urQ=%5o!cCqW@_<K4{D)tu;Zi&BX#yKqnie=
zZqpt$ACJ@ml%6&V{Pv!+x70OqCM&$vx;OktFdy^v#|3>B?@cvKvwq>5k6fC-`VJyl
zHWcSH@c%3Am%pKuC69Fe?augD+?&COZIAmtxg?s}s?a$!-)_Z`sUy|sV?5k7nyG6O
z1au3Dr{-hdl6yQKUUg&){GqU4<xOIXg6*(66(5Y6SrCjWi2*>}u8N<X^rEw`TBmr3
zb9S^nwmV+Db^RhRq2+^(4|tW&X=on)h$_-Xe{mcCvnrWGXWpbQL$;mB&^U?wg%BMB
zn#_uZ+TG+U61fQ;|ILJGh3<x<?xg*S;AQ1wfG2hH%bs_PXMCQ2HSxSrv4zcaF&&5R
zyDR3UNF8t&zmU9*mWxV8m2?o6Qpy(*ISCf!c-_V|7EWL<lS~8JY%PUJ3mjPBsxXT>
zl=gk<XpXD|J&FJE2_V~a5V2ZZFp@QwZcmx4lD>2KjY(8Sk`VtWYKe~hpnXq%!LqOI
z-UWSdGT4Ii`p}&Cq2GOn5wHAT8;5}IvtEM}qWDK8%1}>k+Xlrv2741=t}1yPX2csk
zNRW%9)+d)*|F~t4n<DLTUmFpoPY~_bz0K76HaYZ3CCaY~Xq4W-`Saj-CsIoJeY@_D
zr<?1Ed$8aavIJc&l&@_EgI2=L>%CxYHbHZxK=y5|(isy<QrnDJVYY*uAyLZ%hHuZ=
ze}Gh4pQ8y)wsi=0j}{IinX7gSBK&XM1=tg7tB{+p-jQrSOEFiuD#IxEAmv05-~WRx
z1pR-uEiAa9dplLS?w<O!Ix3{?o=y?rthZwSpBzZ`$QG%<<-NFkIaV_VEns}Ls-wit
zv$enEPV?KooB1^V^F;o2Zg_N->=i?{T4_MOyt=Q1%m|&2<8?C=yb^NcFY|x8#?apU
z>&rqGcgz2--OLn4;4>9pyFVzE-j!>hKk{<<Un3k)0{`c*0_2!chX>a4fP@6nJ+r%e
zRWGNpe!fBf?{DO^cg^g;OL1PAg6tE$y?RFQfA2<35IS1%-d+-`-4bcy|F<yuAEOk!
zr|EiP6otwRl@O5F$6J4M0`&Zz)HHN|Ard%||L-fwk39@B#aDDAo~6J0GDBs4@qfK#
zo}|M^H|H(YMduG8Yl|J0K*1QzgE%NXSnyj=SK)*LAD_?J&Ba!(652g%Nnxyg*Z(2N
zQP7y-hVaoj^G5N?r<2@8SDtuP(W<9*<1p28y?JuHOwa83f%6jc^QL(*C%n}r@2+q{
zYeXKAED#`zM#)ZrcHZXC0}V{S?yHK{?Kltp5)?|=Utl&nm~lA%?gZH>CXnM_SKt@7
zW=HU!bXhsVDX)4lIKS8??mhVkr#A-2mypffGc(-@VNZ#H!2h#2YPmCDe+EExHtmOm
z!S{!F2@UbCV($z<YD6n5P+!;C@o=+sKzg}7=J@m`CHNVzz6bU4k@xY7dm+#`a9)LV
z=>ykV!q$4UL+XdOg@+@IDYfCB$v)agXIPQ_eSviN$msX4mpJ(+|9lJj5Wwx3Y+g+^
z0sr6s0GTfN$7C-X@*jXN!6&e^|9^e^j~6m|k3SCH^T@!P{9<HcDB1q{2t+>g^PV|w
z3w51#{8jCddiJ~%_GIHN|DQuz^+D9n@A%8+Qs36e`TpX|Ptm6ux7iqYw?2QomRmw&
z+^F1$)I679OQRw)e+`%Yh~<4>3@71S^c`(WWTuD-v*kp9<V@}0c#CQAhWKt(XZhx)
zx^H=5r<8Zz{=MDBb?NaPDe}cod?pX)XSn<o@-2eP0@mi>Q^=jaLqlOk9so1?n_*yt
zz(*LA`~~>)vq!%m|BC#@9T;uhKbF)-e;5W0AioayIC|MDSn{8LWG`JBqr2_rV$+5D
z9`W=^GwMs)F5~G=)N{@);urPSA|KSuR0pFhvbtdTz{`7pddWFw*lTr^_@mU#ZwPIe
z>1P{nWE<do*ou&*ip?(*d@pgh@q2IKezwJUo2M`NDvo{ZzA9eAcklOHEKS6jr@5xN
zx4`wx$}bMAx;>ji#|^}NSE3X*d;Gf#V_|W(%`S0Wh^EG~uOy0K(cDq(w=k}s*+0KM
zQsC<b{hhJeq4r>NzBd1@f|NA*M!JT#e#f!AdN*@X-Mo&&nCjPJ8OPREbzIf5@$S~d
zv+CVn<<%2D)$@NGO%P``534wr;_80*8-DpjEpT?IIqboY?Hs?uzV8)0x+e`Cq;;cx
z=gQ``=I;IR1fxnGE)5x}o&EfeOYNn<FZ?d)IrCbf&xiWJ?DyA8)UV%#&Jf;qNU`(2
zqBp}^UBTAwPS$*15YDvheABV|%6sO`zONmT?TgsV2%QnNo1xt(DHyyWc$ieLD67-2
zt4)5rqAH~L>%EV5<1X(B4OIENWRhJiywu)^rG)C*2g!(?%|^f7sV?)SVFE{G6~lC4
zMB-4N<Ih!a-$&2x)z=54YDLY^Upj8%_xa=BJc|Ex1-l(isy?$3u$$<jY8$SqBatPf
z<+D&laIm^FzqeYqzD6+Mxk;W#<Vk|D${kvBk^7eGP_yIzv}vtn&~@S++RJcyWGCx-
zZZJ-txDon;F-hHm*rRl*Ipy;9?%>O$)YOEwswVg;FhIQKxv^#y{1gxM+wb+n{5JR&
zZuR!wK^OMHhokH8Qs3{QqdNV^XNJ2uClAYQNuGy?Z{J?QY7{gf^ViMKBd^8h;^(oQ
z@Vw2rLx!CDKJ)3{SEZMg3^pq_S!<=g2INg2nB*RB;+@aa$6V0ReDomw_(S}idXYFB
zZw%{0&i;h!(m#Cm2jh|{?f072f5bSY`eA=V1<arYeoL9Qa?b9HWd#ARqn+d%koPP4
zn8Xh13db)Ml=Ck3H;-QbDRSB&(cAXfmw}B!;~hene2Qb%l6CoS6yKa{3Jz1JuHR{B
zxlFLQZ>gPM%NfS-r1-G3=30U0rb|H1Rh^$o!)gdS<)!S}`+-8l)w}|;bTib<L8DmT
zo297=OC3s;g$LVp)auHTsWEi-Es@4ETDz&U10_wEo!rtT_-qw#-pidvD`pBzcr?ty
zvOJuWr7LLi@ghA0rYl{_ZJ?+<FgcwX_E6qvNQfy&-!0qQd+YF%-_DJ&kzQ(w0@T*n
zIdLtYvW41%Kb!TY>Pk(R0-x$ygC$#^;nD+SrI#cT2VKkAk=R<3F_B)yi!bJ;Hm6*=
zu6IR1`;cUmzqzw9-sL;LHR!mO7u^Ym*1FkyijD+sEh#2$jXWIuvum20rjHc(CQhM&
zGJm1Z`@%HjvQ6tQy`R{R09oC-1Hnt3R=Ek~j8>m>PE?&vy~W4xRAgN1t0y-=DQmp$
z5%0CZx{o&~Ldq$a>?J1(risq2mx#lb_Vr_J4=1-(E!c-Vi#}xO3%1Xo2f4iYQ4P8B
zJZ)XKrxV`2v-KfuchWa5BoqiC_#LoGViM9ru}0wSFp`8W{XMUq9h-JjiWg2lMxr^<
zjs}GW!_S{8ojKu}osC1%qE~{T#u3^~KBDV}r!$xW1Ji^U`M2IQJWpR)w@^j4`VC#h
zma0!7jZbBoyCs~9FYSt<$5eQa<>g!m-ri8#eYeIcU)SVk@NN)OQ?ZRe)sh&+oJ8Yr
z753n0_JQUU8H@bo!=J8F(i(KdmIjF6>nya&c}hOaA76=3tlc)Bh*z@OydnP*pg(uf
zGE>aOLL(!y%ES5bw)uB$nv$n(_?R`@>eZ`fT8-R*IJ<0rQYkK%qTkQHrDEA#&Y7~&
zrYb=^S=e7PGL(bH@tVPXqCK;H3b{3eL+OL(?2T!YEz{=9Dw-Q5-EG34*CY_qtZMpa
z?~g0J>j;s86!&(ZWA%((JM3!d8?oG`!_o-p7C1!CU`C@q+jb+tv7?=uBD=BuEhSsq
zwP%{0uf0F6ghS<dhGN{9&^F;D=ME`h5e~(-%(MxILWlW@PV%MI9_jeRw=VOpm+Gr>
z^sN@-4ml0-QS_#{)3(ydaU_&+U<O|LSKVDbf3Z9quXE4PJ064fa@-{MbIsC_hopmZ
zp$gD|oORvPxHL<88%*tqPcwY|vuZ-HrLuVs>uV@Eg@qWbAXS_#Vs!WZHl@rrxYs+O
z!+{_TB!2kmyEi%%*_=Yz?cC1qj&ZZ8ltX-amgqT<fmwp4I-J=?*Zl_NxtO9`l^Bf=
zxf1&<sKir(x$67-{ZP^e6_n!qJ(r1FJ3`K2W->HkerK@UIics{%qEgoa9>KP`F0*|
ze&Y+I?m}bxSlPK>HJm3P$-bWnHI&aKnoFsr%t#y1X13(}pSuMITy2}cCYSL|lB=R%
zLvXU}snZrfl;ean-b95%nXCnzEyrk7%YI^0%Q>I(a5*tyEhC$pLlfe&P?d8h%wO!>
zDzsoQa@{Vw6k?Zg7ZyF#?>h%U_4NBzy@)aDaf>?dv90lr7f~BC`$Rb9w&aV@4#fu{
z1Krfz75!Q_%V=?K0!vqR!bsJ%UL2K1Baa!~-A1Csq8M(VI)45gDyj(T>|+#|*X{gM
z57120Pm0~MQkqw>m`JpdHt&n{59uL=B0VI?`b5tt|8a=DL4~DWcZsv`U35WDY&=uE
zIjerUZC)63{9w1VU@~r5QEci;UMUW#nIlBvpTB1xP^rDUl%O0Eg)T2Rc>i))7{*^j
zg4j*YGFzw1no@KP%qG*1YE#E~8r*>m1GB&ruG}Oz@pUHt&~Cr=6&RtgmCdiY!mEN~
z)bdR`PVXxeEN(VoRO>{R_}*sAm+yqAwxpL>_lY!NhTmv~X!2-@%n1va-G2@nsS>Sh
zZ#Nk)ryEa@kQ6bsDB@(oDo1~`NWd%&2Re=EukmSO!Pyu)cvkG^x8Y~$(?3<5Me(vz
zJj{zc#^tQ6y`N<L;ZkNALdSZ@ASpj5&Lt(3B{TtP-;_@u5n{HlA<cgavim*hX%p{x
zLTnR8kod}BmtlV{v?`qOiIN#-#k6ZqWAbf6{;g<3|6VP*GEG9CW&VW0c8G4g4aO}x
z{}ersN=VRY3T`n`XSVtSp||IT>{<nn?jL_#ULfR!OIByIbM&+@%m>B$O4#0x_f}8l
zcdm7kQ%WWTW)ZMc%2o^+tC@;Kue|TAaSA2>&>*%Rj&8Bz%(SIz>niE2Vfvzc<|%6D
zJaqdv6E;@);mjkSO_K#~Ns1IU?#na!`;@lSB&{>&nLLhD=$w$}O30Z~c#?pdPV6%Z
zx*OjH$7c_eq@$WChxM7THiVQI0RM$em1rg~5V5bG+VrUleWCwyRRIyUtL!%TA!0a!
zy6czm?5LozaxjQgf>HO+otHWO5K?IB%T&R8N8l^M<Lt-Y324ZRlJ&9i8Ywhxo;j{&
zB=y&VXtjY~^v=^cif(4?>yi{~kapF;6J|3gZGO!plv2pMUI(^0l5Cjia?bJ7Fy*A|
zuQN6KrOzvDzPeUXI8C7<@>9o6mjIQ9kLN8b#lv#VwH*1wjFx&NH6pgQ`@Al+8;<{~
zrRLsGA$r~BmYm^av1S;_fEN3j8EafQw?!d4BS_p4dTP<s)F1Z)$(ff{x^{Teit^my
z^7KPjwjh;YI6loRB(lT(+LqJ7af%q0-H6u0)DizzzWe%z)xFvGKEu__nr!ZSjkNQ{
z;gF||AKdDTb0~o|VKTe2Ah6N1!}zy?Pw+LFYuNoVTI^wS&*j<i6>gZAa_MC=k`^ns
zmUyze*c06A@{jIjIbuRp{`fb@9CQT@^r!zDC`Go2P<!2+LVc&Q$PJ&&6ecVzlDlQC
zM-)x1{Vg=%qEQ$QQ&q72N4>4f8IT0?GXymvVB_98vltCCsJI*!m8&nq$JC~@TM+b3
zHVhgnLb@9=qquI;vyf%rM^q}%8|yi>+0i-ezdki`jYiGgc{RU+oBw4#mkQ*EFsz_v
zV|g_*`7sOa1qzLeF2-TMhObSrUM?w3{`0Oh?<MaEx9oHrvMJNnG#1R4G!^@sne1i+
zx+YA<@yD%v`qsP@V%@#`-RKK^kyCsMR^{63;)MMkm*?(D{=0t3l5uaS-8g<#dhb1N
z!r<3;+Qw&ukJFp1n}sgw@6-0NVlp^qWqVx|SwSVh?5TrDGcK?Ynbz;m{8?EpOkC56
zNpq+uYZvma9teUm6<J1c(n|?l>VT~2_>5838puZ&Om+~Z=dt%4mUMdHuA9c1^(&iI
zxJmq?H<)Qc$$6h++FK1WE10^J8uM>Q=`|J5pVUrxz2&v7su}8Ax;h20{Wek!n@@jY
z?406p!=4&YW5rw=b^dVmXFZtF9`NBB5dA3!QcasMPCi4I9s2{wGvHK4REQ!E*C%-`
zSRH7~tzfo#pA$ao)O^UTsnfQ6(3VTGlH{T5>v$JoB~YxZ;1q>JzAG>PL&Q)I1!lUe
ziocS@m9R2pnt(aI@HC&B59BMR;&=J~i1;qQ`@&t^Mmf;j_rU3uj8#vu1*ZIT(ycT6
zQQcanE}P|6_}EDlFQp%}EEd1a%QSCV9m^SCxuuq`ccrtD$LvWPeK3<)F#mi}LKCKI
zg|P2VRFn5Z>ZLYemfj}yti&0*MA`5~>z(>&H+;WVX}HMt;pvKqcb#iGAuOR$;VdN~
zT2SML2uTMnW^6^~ZPJTwriM>3{9dqc#7FsHrFYLg+Wfl7C&F2FFE03`1_sBgO`;V4
zkzg|=1hUkj-ffVjiqA>53eNMLCMViUh;++6#q-sfY5IM>`er0z8|Ju<l4TYpeArz+
zbtlYF{!{A!dIjq{KVEYjYFWWsaj)iDe7*mtUR5Ed=rE|-a(~gmK0^I5<Y`su5AVT=
zr|CCd$~yj`#@_Juvy;@ZmAo#vcZ@=V$NaHg$;X?{s+uqJZTh)VyDM&S5});Yn+LRf
z#Ba8iX!lz1G-1XHmfmY(W)<<DYAr9eT8Anc@!sz)%{mLKZsxB8Q(@FpPyhew?mYjR
z$htT_$Rj9qSq+FZQBeey8oHqwKu{@3Xz~D|g{oL+iS!~%UEBl+E&@RUA#|xhKtzxQ
zTuO)_7KjQ+Ab=Wr$urUa;+YroVm@>3`Q3ZYz4JNW7js@kXE&q!f}oiwb{>4DpgZuD
z(_Z~oI=HWFv}P{fNG6wUQz_hVw+m81Qx$LA;H7S*j-$P<6Cc!C@*N#UFG@FtcPt$H
z>Pk0ooV4C^JPj=h0r$6LSrIy_OyFSo-(wrbpHieuz<><3>ZP5R`MT>FoRc-H<Csi-
z{0NO1{Zn(js*aG+X$>CdgX1KJrs;y3Dz@su_}m*i$;YUcV(bC(Z*^>yF-~uoYC>30
zUUDC`>D=8WoCoGpGycbT^Qlr@$`p;*Xnn4@GcYzR__ba*{le+l+@|Jx%M6b~;d)k1
z^4rfdlJo;sgJ2=oxY&BcMx2p&X5$Z(ivUpJsHi&OuT^S2co)L>OHtXI9$h=6CLQ2c
z>B^ys)VVEOf9URXk2IvCr6aoM;pbm-5_J<AwPs`N_78IWPLa#`#Nm)v>+q2NnamB_
zzS7(_ics**&F=F1J4K6OP1Vt(Z6k{X*jm`RhH=ai87@Ie<1|{?NwKN3Mz52<Hx@`N
z+DOfi&TabzwhM$Cy-p<Woh>Y?Za3(8ma@F&H$hSR?*YI>DRlW!sj6IP$-)bf_a)BW
zP^mOL2mUaZ?hK{(W*ACAnks$1spu-jN&op41ODJP#r|*CE<10=5DLD#9u||4b?Owt
zp3>IrokL<)F=XMT>#^UlBQU=wEppNgEL)g2YH^4dl^7v2C0;1*;d8+R=Cf%zF&2FO
z5>nh@l9Tg9HWmOF{T+du<gobxUChd$lL+;w&lgIjc5<E@y<udpegk>OW9;(L`5TsJ
zsGVA$&WWd8s(Ar@NzZ?pJSUi^SQTFNn``}+X!?R0U_#OB6=_#By4X5OVjgQXFQMOo
zTv{-<czpGxn>{{FnL)d$gd^T@%|-4iPcO3mBAxcNP*E9cuBLFXML{ClQ!UXd&C%b!
z;nb3AgW9c=i+%m7Xd#e<3`7$(`e6xW4}lDxvbw94M6iSwQ799H2~<v3piLj;8aLZ=
zq0+YV9M>!wp}=s0i!DxH<v#El#i(sFzx)shamH4-b1HAvq)jrJAPw3$dDm$)zu@tT
zmJ2&98iV(8$W177>vsY~f#P!Yh!`EUFUBZ?8B$x@RxBe|ZRI5J#lrrvrjhTNv(jdg
zw_T~j`6vgB5KLP|Wk@pmY-b|j0qcqu*t5$RvsrIO0&!OHJUZa8_MZ`5M~+eg+AxH)
zl7i@|W}MCBK3K|2kgZ1=cg;?w@&U&o9~K1)byl6VQ~$PGFf~OW=x<<$2`~6g#A;J!
zZ?9eZr{$B&K%Q&*z8q|lkeN?7Jfxo}V9OsW<tSgN%T@{m2^cctACiNwmx^Eur0RF;
zgLWYZg#Psp&)f#?4z?YLbC;}ktv(>9>k6}aL=yoPh}aJ=mykPxx%ZL~UkFZbg!IpO
zHBD**y`)c$tUSn*F|NMTNUCydeGQXLCU^Pli}m%Hhq=78?n;e)zsD!u0014w;Hj1U
z_^U|O&@vKAr4f}*6fIb<g;lH`C941&Nj$<}yTm5y%M=x=tT&7AT-gyC1x#qW*#nj=
zRZS>ZMxk_3$wb;4L5FCQQqrO>Emz8$S%M|pK_+c2M&|#7tQB&)F`uzACNPg#jqcM;
zy!xIwju!X<^j>RkF>_JzL=93lRF0NC!?SEV6Hvff8qCJNk)=R7xpat8*0*355)yKW
zd_c))1SFu~A{FU|Kl3BAMn!rmFDd&61WeVeLkUE_O8_wbdl|WY_qnv6_lFYf#30T2
z)?;Yq16Q6^-0@<L>L_r>_X7V#WYWCdM!3K_0N80c8aMZM9@+4ETVgTdzo+?eZ0vq8
zy*blp@|UlivmTozq9=^0w{MF<hJ=<MN2v1S0HEUV_HA2A0BNQ7igS2{{S%MA#AY=y
zB_*CGz=RM9^2Tl{f%{Bn?YO0iu;*|v8MqX+8@jc=abTlA6kI?4>^0e2WR^~q!MGJm
z=D&^I2fg1Vf*5SISeQ42ohb+_AtEv{j@3erN(&d)Ff$bXK-c?%0Dx5hON$Rej(ayQ
ze9t_EtQ7E@tW9@@T#1_ewb&v&s^_`uD@CMCK@J*>r|VRBu)Qq=z*E|*4s;H|us^5w
zth}6?o9nWO>XHbwYQpGMrAIL%Bv(g%Ip;&_>1d+F$I-}tpU=&aW9_+QcikL5kY6J4
z9`|4n4*Q+gbUM9m&aO1*PRekYscH^PypyLJnDt&r+X=4x9E;h{s-|mn_k(V@4#rOJ
zjkDu<_Wvm>wBIK7gT0}Y9$?cttJ7Wo;Ansy4#8`n$DEpb@IvMhg4WwKmyXt(2L-^V
zc*1gYA$p4V)$kjtN^hLrc!t(`<)=)*&g(kk*1v7N0@<cV`$rDZ2Df*gKNQOVjg*BA
zTa0*2GFVG52Ey1gt+2GHNeSRXjs&j6Uotwz&+~Wmxn<Wh#0@*Ew9MfWMRm@6t?OsF
zXw`^j?Jw|O1tlpLfS<B9eUzaF%Klb=+i}T8nrAR>^<!tD(TSfUJn>wt`FCbXq9<fE
zvd;FiqrqcY;)`xnUbe7U*e$RLF%XxqxjT$YFf_cL-%<bjpy--p6K1kjxQm@`o*gpP
zoFnMV6A~wD)bfp3=Vz)NxvSn&XQ6OJ8w%Z{u46bA66kJ;3@{U|dN6|F0)L&!5*KCg
z0;e;xB${NMYxcBd!F&Wv*`+xbdaC=+1W2t9*~s-ASes~-(3jEVuob-%&^cFRIV;o0
zt6F2_Dd5CTVDOdXeR0E}3SuRfxP{Y@lwnn~WRe3F7=omxrnSjuID>@jcH<ev<2-#>
zXuC06NEq34IqGvkLBal5`Rz0$gtVXIBD-8JFsN2@BR(E{?d<9t)tJYqhxSMEx7>H<
z<<)WgB@O=fQu5e68ebdZU*#Ipw0V#|vVs@cIQQfP5y=>g=}4`Iv5ZmW<|3lQb2X9x
zuT8rxm35f*F-A-aY<-#cgQ=$LQ@&@J!cx$TEk~Cr-fO_$=gRHWi5O!d{p%i{<Y@%3
z28Qd;<j&J#(du6^6qg&hPNgT3K0bLXEjFo<4-0dsyF2)l$*~m?0OCGs&3bIaL<>%C
zm};|QW5lf=B--_A>-V_N$7{BN5#B7`nrnX)wfa+}e7EYYJ#FXEmE9Se`NG8l3W=IG
zpMk)}l}U@e(+H3;(975QkrJw+9OcXhVC88oi}JO&j^(ZENi43<KJ5K`WVL*f9Uo0;
zo3Nj{QyjIP%Ito>)goy8w((-*#>BfT(m&;g4S(dvy{H(U*MS|GyB=cr^ukSYjO6U`
z!Xfn&RP?Clc2aSAe7V>mzpF*EyC9_S<ese+1h@1HJOKEsizzG#tuSeMs+uUci1&0l
zZKHO{TppD)@IAdrUcG2IRDIo4Sf9-??XLJSEPS!!`@<P9VGcmLvHpw(PX;3U*I_4G
z*1&QOwOn13M)Y71@KQ0oFq0Wv%IlFr^fkN(o|4%HHAwS{o{l*0+ngm2Jvr19@oMQ&
z!pcXS<tm4zgjPHco{Vxq3LdiWBZk@N)0NAkG$-6ur1{2XZ-=_5m>G(Z^wmlDT8_hh
zS?OT~E8fiGuuLnTCza&q-$lHms?=QPeKx~WS~QokheP>+xRjaDd*Txv&l3BQNrBXE
z=_#$N1M0fl&>i$o+vCOlkKT?xrI2p+3p+)LW@JG>^8s<&T=%8n2}!d<ib=oyAK&aO
axZ)PIn~d|v(*EGB#ufPW%Qa@63I7A9V5Fn~


From b0094b63c4b7e508fb702b771bd9bee75227c606 Mon Sep 17 00:00:00 2001
From: Guangwen Feng <fenggw-fnst@fujitsu.com>
Date: Thu, 13 Apr 2023 11:45:14 +0800
Subject: [PATCH 184/272] [zh-cn] Sync user-namespaces.md

Signed-off-by: Guangwen Feng <fenggw-fnst@fujitsu.com>
---
 .../workloads/pods/user-namespaces.md         | 67 ++++++++++++-------
 1 file changed, 42 insertions(+), 25 deletions(-)

diff --git a/content/zh-cn/docs/concepts/workloads/pods/user-namespaces.md b/content/zh-cn/docs/concepts/workloads/pods/user-namespaces.md
index f201a088748..f3f5738ced5 100644
--- a/content/zh-cn/docs/concepts/workloads/pods/user-namespaces.md
+++ b/content/zh-cn/docs/concepts/workloads/pods/user-namespaces.md
@@ -50,34 +50,63 @@ mitigate some future vulnerabilities too.
 
 {{% thirdparty-content %}}
 
+<!--
+This is a Linux-only feature and support is needed in Linux for idmap mounts on
+the filesystems used. This means:
+
+* On the node, the filesystem you use for `/var/lib/kubelet/pods/`, or the
+  custom directory you configure for this, needs idmap mount support.
+* All the filesystems used in the pod's volumes must support idmap mounts.
+
+In practice this means you need at least Linux 6.3, as tmpfs started supporting
+idmap mounts in that version. This is usually needed as several Kubernetes
+features use tmpfs (the service account token that is mounted by default uses a
+tmpfs, Secrets use a tmpfs, etc.)
+
+Some popular filesystems that support idmap mounts in Linux 6.3 are: btrfs,
+ext4, xfs, fat, tmpfs, overlayfs.
+-->
+这是一个只对 Linux 有效的功能特性，且需要 Linux 支持在所用文件系统上挂载 idmap。
+这意味着：
+
+* 在节点上，你用于 `/var/lib/kubelet/pods/` 的文件系统，或你为此配置的自定义目录，
+  需要支持 idmap 挂载。
+* Pod 卷中使用的所有文件系统都必须支持 idmap 挂载。
+
+在实践中，这意味着你最低需要 Linux 6.3，因为 tmpfs 在该版本中开始支持 idmap 挂载。
+这通常是需要的，因为有几个 Kubernetes 功能特性使用 tmpfs
+（默认情况下挂载的服务账号令牌使用 tmpfs、Secret 使用 tmpfs 等等）。
+
+Linux 6.3 中支持 idmap 挂载的一些比较流行的文件系统是：btrfs、ext4、xfs、fat、
+tmpfs、overlayfs。
+
 <!-- When merging this with the dev-1.27 branch conflicts will arise. The text
 as it is in the dev-1.27 branch should be used. -->
 <!--
-This is a Linux only feature. In addition, support is needed in the
+In addition, support is needed in the
 {{< glossary_tooltip text="container runtime" term_id="container-runtime" >}}
 to use this feature with Kubernetes stateless pods:
 
 * CRI-O: version 1.25 (and later) supports user namespaces for containers.
 
-* containerd: version 1.7 supports user namespaces for containers, compatible
-  with Kubernetes v1.25 and v1.26, but not with later releases. If you are
-  running a different version of Kubernetes, check the documentation for that
-  Kubernetes release.
+Please note that containerd v1.7 supports user namespaces for containers,
+compatible with Kubernetes {{< skew currentVersion >}}. It should not be used
+with Kubernetes 1.27 (and later).
 
 Support for this in [cri-dockerd is not planned][CRI-dockerd-issue] yet.
 -->
 
-这是一个只对 Linux 有效的功能特性。此外，需要在{{< glossary_tooltip text="容器运行时" term_id="container-runtime" >}}提供支持，
+此外，需要在{{< glossary_tooltip text="容器运行时" term_id="container-runtime" >}}提供支持，
 才能在 Kubernetes 无状态 Pod 中使用这一功能：
 
 * CRI-O：1.25（及更高）版本支持配置容器的用户命名空间。
-* containerd：1.7 版本支持配置容器的用户命名空间，兼容 Kubernetes v1.25 和 v1.26，但不兼容更高版本。
-  如果你运行的是不同版本的 Kubernetes，请查看该 Kubernetes 版本的文档。
+
+请注意，containerd v1.7 支持配置容器的用户命名空间，与 Kubernetes {{< skew currentVersion >}}
+兼容。它不应与 Kubernetes 1.27（及更高）版本一起使用。
 
 目前 [cri-dockerd 没有计划][CRI-dockerd-issue]支持此功能。
 
 [CRI-dockerd-issue]: https://github.com/Mirantis/cri-dockerd/issues/74
-[containerd-userns-issue]: https://github.com/containerd/containerd/issues/7063
 
 <!--
 ## Introduction
@@ -283,21 +312,9 @@ Pod 完全不使用卷是被允许的；如果使用卷，只允许使用以下
 * downwardAPI
 * emptyDir
 
+## {{% heading "whatsnext" %}}
+
 <!--
-To guarantee that the pod can read the files of such volumes, volumes are
-created as if you specified `.spec.securityContext.fsGroup` as `0` for the Pod.
-If it is specified to a different value, this other value will of course be
-honored instead.
-
-As a by-product of this, folders and files for these volumes will have
-permissions for the group, even if `defaultMode` or `mode` to specific items of
-the volumes were specified without permissions to groups. For example, it is not
-possible to mount these volumes in a way that its files have permissions only
-for the owner.
+* Take a look at [Use a User Namespace With a Pod](/docs/tasks/configure-pod-container/user-namespaces/)
 -->
-为了保证 Pod 可以读取这些卷中的文件，卷的创建操作就像你为 Pod 指定了 `.spec.securityContext.fsGroup` 为 `0` 一样。
-如果该属性被设定为不同值，那么这个不同值当然也会被使用。
-
-作为一个副产品，这些卷的文件夹和文件将具有所给组的权限，
-即使 `defaultMode` 或 volumes 的特定项目的 `mode` 被指定为没有组的权限。
-例如，不可以在挂载这些卷时使其文件只允许所有者访问。
+* 查阅[为 Pod 配置用户命名空间](/zh-cn/docs/tasks/configure-pod-container/user-namespaces/)

From e18d5b725f3a28b1deef42cb5bed3d6c59ceeabd Mon Sep 17 00:00:00 2001
From: Guangwen Feng <fenggw-fnst@fujitsu.com>
Date: Thu, 13 Apr 2023 12:01:14 +0800
Subject: [PATCH 185/272] [zh-cn] Sync downward-api.md

Signed-off-by: Guangwen Feng <fenggw-fnst@fujitsu.com>
---
 .../zh-cn/docs/concepts/workloads/pods/downward-api.md | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/content/zh-cn/docs/concepts/workloads/pods/downward-api.md b/content/zh-cn/docs/concepts/workloads/pods/downward-api.md
index 825b67caa06..42ed777570c 100644
--- a/content/zh-cn/docs/concepts/workloads/pods/downward-api.md
+++ b/content/zh-cn/docs/concepts/workloads/pods/downward-api.md
@@ -218,19 +218,17 @@ for resources such as CPU and memory.
 
 <!--
 `resource: limits.hugepages-*`
-: A container's hugepages limit (provided that the `DownwardAPIHugePages` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled)
+: A container's hugepages limit
 -->
 `resource: limits.hugepages-*`
-: 容器的巨页限制值（前提是启用了 `DownwardAPIHugePages`
-[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)）
+: 容器的巨页限制值
 
 <!--
 `resource: requests.hugepages-*`
-: A container's hugepages request (provided that the `DownwardAPIHugePages` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled)
+: A container's hugepages request
 -->
 `resource: requests.hugepages-*`
-: 容器的巨页请求值（前提是启用了 `DownwardAPIHugePages`
-[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)）
+: 容器的巨页请求值
 
 <!--
 `resource: limits.ephemeral-storage`

From 8e89830e92b36a7b2cfbce7c73de45189eff2ac3 Mon Sep 17 00:00:00 2001
From: windsonsea <haifeng.yao@daocloud.io>
Date: Thu, 13 Apr 2023 10:12:06 +0800
Subject: [PATCH 186/272] [zh] sync pod-scheduling-readiness.md

---
 .../pod-scheduling-readiness.md               | 65 +++++++++++++++++--
 .../taint-and-toleration.md                   | 36 ++++++----
 2 files changed, 81 insertions(+), 20 deletions(-)

diff --git a/content/zh-cn/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md b/content/zh-cn/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md
index 637f1a299df..c36d9d1c504 100644
--- a/content/zh-cn/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md
+++ b/content/zh-cn/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md
@@ -3,7 +3,6 @@ title: Pod 调度就绪态
 content_type: concept
 weight: 40
 ---
-
 <!--
 title: Pod Scheduling Readiness
 content_type: concept
@@ -27,7 +26,7 @@ to be considered for scheduling.
 Pod 一旦创建就被认为准备好进行调度。
 Kubernetes 调度程序尽职尽责地寻找节点来放置所有待处理的 Pod。
 然而，在实际环境中，会有一些 Pod 可能会长时间处于"缺少必要资源"状态。
-这些 Pod 实际上以一种不必要的方式扰乱了调度器（以及下游的集成方，如 Cluster AutoScaler）。
+这些 Pod 实际上以一种不必要的方式扰乱了调度器（以及 Cluster AutoScaler 这类下游的集成方）。
 
 通过指定或删除 Pod 的 `.spec.schedulingGates`，可以控制 Pod 何时准备好被纳入考量进行调度。
 
@@ -47,7 +46,8 @@ each schedulingGate can be removed in arbitrary order, but addition of a new sch
 该字段只能在创建 Pod 时初始化（由客户端创建，或在准入期间更改）。
 创建后，每个 schedulingGate 可以按任意顺序删除，但不允许添加新的调度门控。
 
-{{< figure src="/docs/images/podSchedulingGates.svg" alt="pod-scheduling-gates-diagram" caption="<!--Figure. Pod SchedulingGates-->数字。Pod SchedulingGates" class="diagram-large" link="https://mermaid.live/edit#pako:eNplkktTwyAUhf8KgzuHWpukaYszutGlK3caFxQuCVMCGSDVTKf_XfKyPlhxz4HDB9wT5lYAptgHFuBRsdKxenFMClMYFIdfUdRYgbiD6ItJTEbR8wpEq5UpUfnDTf-5cbPoJjcbXdcaE61RVJIiqJvQ_Y30D-OCt-t3tFjcR5wZayiVnIGmkv4NiEfX9jijKTmmRH5jf0sRugOP0HyHUc1m6KGMFP27cM28fwSJDluPpNKaXqVJzmFNfHD2APRKSjnNFx9KhIpmzSfhVls3eHdTRrwG8QnxKfEZUUNeYTDBNbiaKRF_5dSfX-BQQQ0FpnEqQLJWhwIX5hyXsjbYl85wTINrgeC2EZd_xFQy7b_VJ6GCdd-itkxALE84dE3fAqXyIUZya6Qqe711OspVCI2ny2Vv35QqVO3-htt66ZWomAvVcZcv8yTfsiSFfJOydZoKvl_ttjLJVlJsblcJw-czwQ0zr9ZeqGDgeR77b2jD8xdtjtDn" >}}
+{{< figure src="/docs/images/podSchedulingGates.svg" alt="pod-scheduling-gates-diagram" caption="<!--Figure. Pod SchedulingGates-->图：Pod SchedulingGates" class="diagram-large" link="https://mermaid.live/edit#pako:eNplkktTwyAUhf8KgzuHWpukaYszutGlK3caFxQuCVMCGSDVTKf_XfKyPlhxz4HDB9wT5lYAptgHFuBRsdKxenFMClMYFIdfUdRYgbiD6ItJTEbR8wpEq5UpUfnDTf-5cbPoJjcbXdcaE61RVJIiqJvQ_Y30D-OCt-t3tFjcR5wZayiVnIGmkv4NiEfX9jijKTmmRH5jf0sRugOP0HyHUc1m6KGMFP27cM28fwSJDluPpNKaXqVJzmFNfHD2APRKSjnNFx9KhIpmzSfhVls3eHdTRrwG8QnxKfEZUUNeYTDBNbiaKRF_5dSfX-BQQQ0FpnEqQLJWhwIX5hyXsjbYl85wTINrgeC2EZd_xFQy7b_VJ6GCdd-itkxALE84dE3fAqXyIUZya6Qqe711OspVCI2ny2Vv35QqVO3-htt66ZWomAvVcZcv8yTfsiSFfJOydZoKvl_ttjLJVlJsblcJw-czwQ0zr9ZeqGDgeR77b2jD8xdtjtDn" >}}
+
 <!--
 ## Usage example
 
@@ -93,7 +93,7 @@ The output is:
 输出是：
 
 ```none
-[{"name":"foo"},{"name":"bar"}]
+[{"name":"example.com/foo"},{"name":"example.com/bar"}]
 ```
 
 <!--
@@ -126,7 +126,8 @@ kubectl get pod test-pod -o wide
 Given the test-pod doesn't request any CPU/memory resources, it's expected that this Pod's state get
 transited from previous `SchedulingGated` to `Running`:
 -->
-鉴于 test-pod 不请求任何 CPU/内存资源，预计此 Pod 的状态会从之前的 `SchedulingGated` 转变为 `Running`：
+鉴于 test-pod 不请求任何 CPU/内存资源，预计此 Pod 的状态会从之前的
+`SchedulingGated` 转变为 `Running`：
 
 ```none
 NAME       READY   STATUS    RESTARTS   AGE   IP         NODE  
@@ -146,9 +147,61 @@ scheduling. You can use `scheduler_pending_pods{queue="gated"}` to check the met
 以区分 Pod 是否已尝试调度但被宣称不可调度，或明确标记为未准备好调度。
 你可以使用 `scheduler_pending_pods{queue="gated"}` 来检查指标结果。
 
+<!--
+## Mutable Pod Scheduling Directives
+-->
+## 可变 Pod 调度指令    {#mutable-pod-scheduling-directives}
+
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
+
+<!--
+You can mutate scheduling directives of Pods while they have scheduling gates, with certain constraints.
+At a high level, you can only tighten the scheduling directives of a Pod. In other words, the updated 
+directives would cause the Pods to only be able to be scheduled on a subset of the nodes that it would 
+previously match. More concretely, the rules for updating a Pod's scheduling directives are as follows:
+-->
+当 Pod 具有调度门控时，你可以在某些约束条件下改变 Pod 的调度指令。
+在高层次上，你只能收紧 Pod 的调度指令。换句话说，更新后的指令将导致
+Pod 只能被调度到它之前匹配的节点子集上。
+更具体地说，更新 Pod 的调度指令的规则如下：
+
+<!--
+1. For `.spec.nodeSelector`, only additions are allowed. If absent, it will be allowed to be set.
+
+2. For `spec.affinity.nodeAffinity`, if nil, then setting anything is allowed.
+-->
+1. 对于 `.spec.nodeSelector`，只允许增加。如果原来未设置，则允许设置此字段。
+
+2. 对于 `spec.affinity.nodeAffinity`，如果当前值为 nil，则允许设置为任意值。
+
+<!--
+3. If `NodeSelectorTerms` was empty, it will be allowed to be set.
+   If not empty, then only additions of `NodeSelectorRequirements` to `matchExpressions`
+   or `fieldExpressions` are allowed, and no changes to existing `matchExpressions`
+   and `fieldExpressions` will be allowed. This is because the terms in
+   `.requiredDuringSchedulingIgnoredDuringExecution.NodeSelectorTerms`, are ORed
+   while the expressions in `nodeSelectorTerms[].matchExpressions` and 
+   `nodeSelectorTerms[].fieldExpressions` are ANDed.
+-->
+3. 如果 `NodeSelectorTerms` 之前为空，则允许设置该字段。
+   如果之前不为空，则仅允许增加 `NodeSelectorRequirements` 到 `matchExpressions`
+   或 `fieldExpressions`，且不允许更改当前的 `matchExpressions` 和 `fieldExpressions`。
+   这是因为 `.requiredDuringSchedulingIgnoredDuringExecution.NodeSelectorTerms`
+   中的条目被执行逻辑或运算，而 `nodeSelectorTerms[].matchExpressions` 和
+   `nodeSelectorTerms[].fieldExpressions` 中的表达式被执行逻辑与运算。
+
+<!--
+4. For `.preferredDuringSchedulingIgnoredDuringExecution`, all updates are allowed.
+   This is because preferred terms are not authoritative, and so policy controllers
+   don't validate those terms.
+-->
+4. 对于 `.preferredDuringSchedulingIgnoredDuringExecution`，所有更新都被允许。
+   这是因为首选条目不具有权威性，因此策略控制器不会验证这些条目。
+
 ## {{% heading "whatsnext" %}}
 
 <!--
 * Read the [PodSchedulingReadiness KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/3521-pod-scheduling-readiness) for more details
 -->
-* 阅读 [PodSchedulingReadiness KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/3521-pod-scheduling-readiness) 了解更多详情
+* 阅读 [PodSchedulingReadiness KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/3521-pod-scheduling-readiness)
+  了解更多详情
diff --git a/content/zh-cn/docs/concepts/scheduling-eviction/taint-and-toleration.md b/content/zh-cn/docs/concepts/scheduling-eviction/taint-and-toleration.md
index affbe62d888..8cdc03ae42c 100644
--- a/content/zh-cn/docs/concepts/scheduling-eviction/taint-and-toleration.md
+++ b/content/zh-cn/docs/concepts/scheduling-eviction/taint-and-toleration.md
@@ -54,7 +54,8 @@ For example,
 -->
 ## 概念  {#concepts}
 
-你可以使用命令 [kubectl taint](/docs/reference/generated/kubectl/kubectl-commands#taint) 给节点增加一个污点。比如，
+你可以使用命令 [kubectl taint](/docs/reference/generated/kubectl/kubectl-commands#taint)
+给节点增加一个污点。比如：
 
 ```shell
 kubectl taint nodes node1 key1=value1:NoSchedule
@@ -82,7 +83,7 @@ to schedule onto `node1`:
 -->
 你可以在 Pod 规约中为 Pod 设置容忍度。
 下面两个容忍度均与上面例子中使用 `kubectl taint` 命令创建的污点相匹配，
-因此如果一个 Pod 拥有其中的任何一个容忍度，都能够被调度到 `node1` ：
+因此如果一个 Pod 拥有其中的任何一个容忍度，都能够被调度到 `node1`：
 
 ```yaml
 tolerations:
@@ -119,11 +120,10 @@ A toleration "matches" a taint if the keys are the same and the effects are the
 -->
 一个容忍度和一个污点相“匹配”是指它们有一样的键名和效果，并且：
 
-* 如果 `operator` 是 `Exists` （此时容忍度不能指定 `value`），或者
-* 如果 `operator` 是 `Equal` ，则它们的 `value` 应该相等
+* 如果 `operator` 是 `Exists`（此时容忍度不能指定 `value`），或者
+* 如果 `operator` 是 `Equal`，则它们的 `value` 应该相等。
 
 {{< note >}}
-
 <!--
 There are two special cases:
 
@@ -182,7 +182,7 @@ scheduled onto the node (if it is not yet running on the node).
 <!--
 For example, imagine you taint a node like this
 -->
-例如，假设你给一个节点添加了如下污点
+例如，假设你给一个节点添加了如下污点：
 
 ```shell
 kubectl taint nodes node1 key1=value1:NoSchedule
@@ -279,7 +279,7 @@ onto nodes labeled with `dedicated=groupName`.
   很容易就能做到）。
   拥有上述容忍度的 Pod 就能够被调度到上述专用节点，同时也能够被调度到集群中的其它节点。
   如果你希望这些 Pod 只能被调度到上述专用节点，
-  那么你还需要给这些专用节点另外添加一个和上述污点类似的 label （例如：`dedicated=groupName`），
+  那么你还需要给这些专用节点另外添加一个和上述污点类似的 label（例如：`dedicated=groupName`），
   同时还要在上述准入控制器中给 Pod 增加节点亲和性要求，要求上述 Pod 只能被调度到添加了
   `dedicated=groupName` 标签的节点上。
 
@@ -310,7 +310,7 @@ manually add tolerations to your pods.
   我们希望不需要这类硬件的 Pod 不要被调度到这些特殊节点，以便为后继需要这类硬件的 Pod 保留资源。
   要达到这个目的，可以先给配备了特殊硬件的节点添加污点
   （例如 `kubectl taint nodes nodename special=true:NoSchedule` 或
-  `kubectl taint nodes nodename special=true:PreferNoSchedule`)，
+  `kubectl taint nodes nodename special=true:PreferNoSchedule`），
   然后给使用了这类特殊硬件的 Pod 添加一个相匹配的容忍度。
   和专用节点的例子类似，添加这个容忍度的最简单的方法是使用自定义
   [准入控制器](/zh-cn/docs/reference/access-authn-authz/admission-controllers/)。
@@ -333,7 +333,7 @@ when there are node problems, which is described in the next section.
 <!--
 ## Taint based Evictions
 -->
-## 基于污点的驱逐  {#taint-based-evictions}
+## 基于污点的驱逐   {#taint-based-evictions}
 
 {{< feature-state for_k8s_version="v1.18" state="stable" >}}
 
@@ -347,7 +347,7 @@ running on the node as follows
  * pods that tolerate the taint with a specified `tolerationSeconds` remain
    bound for the specified amount of time
 -->
-前文提到过污点的效果值 `NoExecute` 会影响已经在节点上运行的 Pod，如下
+前文提到过污点的效果值 `NoExecute` 会影响已经在节点上运行的如下 Pod：
 
 * 如果 Pod 不能忍受这类污点，Pod 会马上被驱逐。
 * 如果 Pod 能够忍受这类污点，但是在容忍度定义中没有指定 `tolerationSeconds`，
@@ -384,8 +384,8 @@ are true. The following taints are built in:
 * `node.kubernetes.io/network-unavailable`：节点网络不可用。
 * `node.kubernetes.io/unschedulable`: 节点不可调度。
 * `node.cloudprovider.kubernetes.io/uninitialized`：如果 kubelet 启动时指定了一个“外部”云平台驱动，
-   它将给当前节点添加一个污点将其标志为不可用。在 cloud-controller-manager
-   的一个控制器初始化这个节点后，kubelet 将删除这个污点。
+  它将给当前节点添加一个污点将其标志为不可用。在 cloud-controller-manager
+  的一个控制器初始化这个节点后，kubelet 将删除这个污点。
 
 <!--
 In case a node is to be evicted, the node controller or the kubelet adds relevant taints
@@ -395,6 +395,16 @@ controller can remove the relevant taint(s).
 在节点被驱逐时，节点控制器或者 kubelet 会添加带有 `NoExecute` 效果的相关污点。
 如果异常状态恢复正常，kubelet 或节点控制器能够移除相关的污点。
 
+<!--
+In some cases when the node is unreachable, the API server is unable to communicate
+with the kubelet on the node. The decision to delete the pods cannot be communicated to
+the kubelet until communication with the API server is re-established. In the meantime,
+the pods that are scheduled for deletion may continue to run on the partitioned node.
+-->
+在某些情况下，当节点不可达时，API 服务器无法与节点上的 kubelet 进行通信。
+在与 API 服务器的通信被重新建立之前，删除 Pod 的决定无法传递到 kubelet。
+同时，被调度进行删除的那些 Pod 可能会继续运行在分区后的节点上。
+
 {{< note >}}
 <!--
 The control plane limits the rate of adding node new taints to nodes. This rate limiting
@@ -518,7 +528,6 @@ tolerations to all daemons, to prevent DaemonSets from breaking.
   * `node.kubernetes.io/unschedulable` (1.10 or later)
   * `node.kubernetes.io/network-unavailable` (*host network only*)
 -->
-
 DaemonSet 控制器自动为所有守护进程添加如下 `NoSchedule` 容忍度，以防 DaemonSet 崩溃：
 
 * `node.kubernetes.io/memory-pressure`
@@ -531,7 +540,6 @@ DaemonSet 控制器自动为所有守护进程添加如下 `NoSchedule` 容忍
 Adding these tolerations ensures backward compatibility. You can also add
 arbitrary tolerations to DaemonSets.
 -->
-
 添加上述容忍度确保了向后兼容，你也可以选择自由向 DaemonSet 添加容忍度。
 
 ## {{% heading "whatsnext" %}}

From ff72402fb5f0441e969e90adfeec2d81e3dbad38 Mon Sep 17 00:00:00 2001
From: Zhuzhenghao <zhenghao.zhu@daocloud.io>
Date: Thu, 13 Apr 2023 10:48:10 +0800
Subject: [PATCH 187/272] [zh] sync 1.27 images

---
 .../zh-cn/docs/concepts/containers/images.md  | 112 ++++++++++++++++--
 1 file changed, 101 insertions(+), 11 deletions(-)

diff --git a/content/zh-cn/docs/concepts/containers/images.md b/content/zh-cn/docs/concepts/containers/images.md
index 2c7292201f9..cb30af9d8f3 100644
--- a/content/zh-cn/docs/concepts/containers/images.md
+++ b/content/zh-cn/docs/concepts/containers/images.md
@@ -38,7 +38,7 @@ This page provides an outline of the container image concept.
 <!-- 
 If you are looking for the container images for a Kubernetes
 release (such as v{{< skew latestVersion >}}, the latest minor release),
-visit [Download Kubernetes](https://kubernetes.io/releases/download/). 
+visit [Download Kubernetes](https://kubernetes.io/releases/download/).
 -->
 如果你正在寻找 Kubernetes 某个发行版本（如最新次要版本 v{{< skew latestVersion >}}）
 的容器镜像，请访问[下载 Kubernetes](/zh-cn/releases/download/)。
@@ -55,8 +55,8 @@ and possibly a port number as well; for example: `fictional.registry.example:104
 
 If you don't specify a registry hostname, Kubernetes assumes that you mean the Docker public registry.
 
-After the image name part you can add a _tag_ (in the same way you would when using with commands like `docker` or `podman`).
-Tags let you identify different versions of the same series of images.
+After the image name part you can add a _tag_ (in the same way you would when using with commands
+like `docker` or `podman`).  Tags let you identify different versions of the same series of images.
 -->
 ## 镜像名称    {#image-names}
 
@@ -71,9 +71,9 @@ Tags let you identify different versions of the same series of images.
 
 <!--
 Image tags consist of lowercase and uppercase letters, digits, underscores (`_`),
-periods (`.`), and dashes (`-`).  
+periods (`.`), and dashes (`-`).
 There are additional rules about where you can place the separator
-characters (`_`, `-`, and `.`) inside an image tag.  
+characters (`_`, `-`, and `.`) inside an image tag.
 If you don't specify a tag, Kubernetes assumes you mean the tag `latest`.
 -->
 镜像标签可以包含小写字母、大写字母、数字、下划线（`_`）、句点（`.`）和连字符（`-`）。
@@ -199,7 +199,7 @@ running the same code no matter what tag changes happen at the registry.
 在创建 Pod（和 Pod 模板）时产生变更，这样运行的工作负载就是根据镜像摘要，而不是标签来定义的。
 无论镜像仓库上的标签发生什么变化，你都想确保你所有的工作负载都运行相同的代码，那么指定镜像摘要会很有用。
 
-<!-- 
+<!--
 #### Default image pull policy {#imagepullpolicy-defaulting}
 
 When you (or a controller) submit a new Pod to the API server, your cluster sets the
@@ -293,6 +293,91 @@ which is 300 seconds (5 minutes).
 
 Kubernetes 会增加每次尝试之间的延迟，直到达到编译限制，即 300 秒（5 分钟）。
 
+<!--
+## Serial and parallel image pulls
+-->
+## 串行和并行镜像拉取  {#serial-and-parallel-image-pulls}
+
+<!--
+By default, kubelet pulls images serially. In other words, kubelet sends only
+one image pull request to the image service at a time. Other image pull requests
+have to wait until the one being processed is complete.
+-->
+默认情况下，kubelet 以串行方式拉取镜像。
+也就是说，kubelet 一次只向镜像服务发送一个镜像拉取请求。
+其他镜像拉取请求必须等待，直到正在处理的那个请求完成。
+
+<!--
+Nodes make image pull decisions in isolation. Even when you use serialized image
+pulls, two different nodes can pull the same image in parallel.
+-->
+节点独立地做出镜像拉取的决策。即使你使用串行的镜像拉取，两个不同的节点也可以并行拉取相同的镜像。
+
+<!--
+If you would like to enable parallel image pulls, you can set the field
+`serializeImagePulls` to false in the [kubelet configuration](/docs/reference/config-api/kubelet-config.v1beta1/).
+With `serializeImagePulls` set to false, image pull requests will be sent to the image service immediately,
+and multiple images will be pulled at the same time.
+-->
+如果你想启用并行镜像拉取，可以在 [kubelet 配置](/zh-cn/docs/reference/config-api/kubelet-config.v1beta1/)
+中将字段 `serializeImagePulls` 设置为 false。
+
+当`serializeImagePulls` 设置为 false 时，kubelet 会立即向镜像服务发送镜像拉取请求，多个镜像将同时被拉动。
+
+<!--
+When enabling parallel image pulls, please make sure the image service of your
+container runtime can handle parallel image pulls.
+-->
+启用并行镜像拉取时，请确保你的容器运行时的镜像服务可以处理并行镜像拉取。
+
+<!--
+The kubelet never pulls multiple images in parallel on behalf of one Pod. For example,
+if you have a Pod that has an init container and an application container, the image
+pulls for the two containers will not be parallelized. However, if you have two
+Pods that use different images, the kubelet pulls the images in parallel on
+behalf of the two different Pods, when parallel image pulls is enabled.
+-->
+kubelet 从不代表一个 Pod 并行地拉取多个镜像。
+
+例如，如果你有一个 Pod，它有一个初始容器和一个应用容器，那么这两个容器的镜像拉取将不会并行。
+但是，如果你有两个使用不同镜像的 Pod，当启用并行镜像拉取时，kubelet 会代表两个不同的 Pod 并行拉取镜像。
+
+<!--
+### Maximum parallel image pulls
+-->
+### 最大并行镜像拉取数量  {#maximum-parallel-image-pulls}
+
+{{< feature-state for_k8s_version="v1.27" state="alpha" >}}
+
+<!--
+When `serializeImagePulls` is set to false, the kubelet defaults to no limit on the
+maximum number of images being pulled at the same time. If you would like to
+limit the number of parallel image pulls, you can set the field `maxParallelImagePulls`
+in kubelet configuration. With `maxParallelImagePulls` set to _n_, only _n_ images
+can be pulled at the same time, and any image pull beyond _n_ will have to wait
+until at least one ongoing image pull is complete.
+-->
+当 `serializeImagePulls` 被设置为 false 时，kubelet 默认对同时拉取的最大镜像数量没有限制。
+如果你想限制并行镜像拉取的数量，可以在 kubelet 配置中设置字段 `maxParallelImagePulls`。
+当 `maxParallelImagePulls` 设置为 _n_ 时，只能同时拉取 _n_ 个镜像，
+超过 _n_ 的任何镜像都必须等到至少一个正在进行拉取的镜像拉取完成后，才能拉取。
+
+<!--
+Limiting the number parallel image pulls would prevent image pulling from consuming
+too much network bandwidth or disk I/O, when parallel image pulling is enabled.
+-->
+当启用并行镜像拉取时，限制并行镜像拉取的数量可以防止镜像拉取消耗过多的网络带宽或磁盘 I/O。
+
+<!--
+You can set `maxParallelImagePulls` to a positive number that is greater than or
+equal to 1. If you set `maxParallelImagePulls` to be greater than or equal to 2, you
+must set the `serializeImagePulls` to false. The kubelet will fail to start with invalid
+`maxParallelImagePulls` settings.
+-->
+你可以将 `maxParallelImagePulls` 设置为大于或等于 1 的正数。
+如果将 `maxParallelImagePulls` 设置为大于等于 2，则必须将 `serializeImagePulls` 设置为 false。
+kubelet 在无效的 `maxParallelImagePulls` 设置下会启动失败。
+
 <!--
 ## Multi-architecture images with image indexes
 
@@ -327,7 +412,7 @@ YAML 文件也能兼容。
 <!--
 ## Using a private registry
 
-Private registries may require keys to read images from them.  
+Private registries may require keys to read images from them.
 Credentials can be provided in several ways:
 -->
 ## 使用私有仓库   {#using-a-private-registry}
@@ -340,7 +425,7 @@ Credentials can be provided in several ways:
   - all pods can read any configured private registries
   - requires node configuration by cluster administrator
 - Kubelet Credential Provider to dynamically fetch credentials for private registries
-  - kubelet can be configured to use credential provider exec plugin 
+  - kubelet can be configured to use credential provider exec plugin
     for the respective private registry.
 - Pre-pulled Images
   - all pods can use any images cached on a node
@@ -376,7 +461,7 @@ These options are explained in more detail below.
 Specific instructions for setting credentials depends on the container runtime and registry you
 chose to use. You should refer to your solution's documentation for the most accurate information.
 -->
-### 配置 Node 对私有仓库认证 {#configuring-nodes-to-authenticate-to-a-private-registry}
+### 配置 Node 对私有仓库认证  {#configuring-nodes-to-authenticate-to-a-private-registry}
 
 设置凭据的具体说明取决于你选择使用的容器运行时和仓库。
 你应该参考解决方案的文档来获取最准确的信息。
@@ -390,6 +475,11 @@ task. That example uses a private registry in Docker Hub.
 请参阅任务[从私有镜像库中拉取镜像](/zh-cn/docs/tasks/configure-pod-container/pull-image-private-registry)。
 该示例使用 Docker Hub 中的私有镜像仓库。
 
+<!--
+### Kubelet credential provider for authenticated image pulls {#kubelet-credential-provider}
+-->
+### 用于认证镜像拉取的 kubelet 凭据提供程序  {#kubelet-credential-provider}
+
 {{< note >}}
 <!--
 This approach is especially suitable when kubelet needs to fetch registry credentials dynamically.
@@ -470,7 +560,7 @@ term:
     c           匹配字符 c （c 不为 '*', '?', '\\', '['）
     '\\' c      匹配字符 c
 
-字符范围: 
+字符范围:
     c           匹配字符 c （c 不为 '\\', '?', '-', ']'）
     '\\' c      匹配字符 c
     lo '-' hi   匹配字符范围在 lo 到 hi 之间字符
@@ -600,7 +690,7 @@ kubectl create secret docker-registry <name> \
 <!--
 If you already have a Docker credentials file then, rather than using the above
 command, you can import the credentials file as a Kubernetes
-{{< glossary_tooltip text="Secrets" term_id="secret" >}}.  
+{{< glossary_tooltip text="Secrets" term_id="secret" >}}.
 [Create a Secret based on existing Docker credentials](/docs/tasks/configure-pod-container/pull-image-private-registry/#registry-secret-existing-credentials)
 explains how to set this up.
 -->

From 7ea1729a85a8e34d595af1910409f325fdc07ce2 Mon Sep 17 00:00:00 2001
From: tianlj <116049443+uos-ljtian@users.noreply.github.com>
Date: Thu, 13 Apr 2023 03:30:25 +0000
Subject: [PATCH 188/272] [zh-cn]sync readme.md

Sync latest content

Update README-zh.md

easier to understand

Co-authored-by: Michael <haifeng.yao@daocloud.io>
---
 README-zh.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/README-zh.md b/README-zh.md
index ee45a6aa285..9ddf8a646be 100644
--- a/README-zh.md
+++ b/README-zh.md
@@ -22,11 +22,11 @@ This repository contains the assets required to build the [Kubernetes website an
 <!--
 ## Using this repository
 
-You can run the website locally using Hugo (Extended version), or you can run it in a container runtime. We strongly recommend using the container runtime, as it gives deployment consistency with the live website.
+You can run the website locally using [Hugo (Extended version)](https://gohugo.io/), or you can run it in a container runtime. We strongly recommend using the container runtime, as it gives deployment consistency with the live website.
 -->
 ## 使用这个仓库
 
-可以使用 Hugo（扩展版）在本地运行网站，也可以在容器中运行它。强烈建议使用容器，因为这样可以和在线网站的部署保持一致。
+可以使用 [Hugo（扩展版）](https://gohugo.io/)在本地运行网站，也可以在容器中运行它。强烈建议使用容器，因为这样可以和在线网站的部署保持一致。
 
 <!--
 ## Prerequisites
@@ -150,11 +150,11 @@ This will start the local Hugo server on port 1313. Open up your browser to <htt
 ## 构建 API 参考页面
 
 <!--
-The API reference pages located in `content/en/docs/reference/kubernetes-api` are built from the Swagger specification, using <https://github.com/kubernetes-sigs/reference-docs/tree/master/gen-resourcesdocs>.
+The API reference pages located in `content/en/docs/reference/kubernetes-api` are built from the Swagger specification, also known as OpenAPI specification, using <https://github.com/kubernetes-sigs/reference-docs/tree/master/gen-resourcesdocs>.
 
 To update the reference pages for a new Kubernetes release follow these steps:
 -->
-位于 `content/en/docs/reference/kubernetes-api` 的 API 参考页面是根据 Swagger 规范构建的，使用 <https://github.com/kubernetes-sigs/reference-docs/tree/master/gen-resourcesdocs>。
+位于 `content/en/docs/reference/kubernetes-api` 的 API 参考页面是使用 <https://github.com/kubernetes-sigs/reference-docs/tree/master/gen-resourcesdocs> 根据 Swagger 规范（也称为 OpenAPI 规范）构建的。
 
 要更新 Kubernetes 新版本的参考页面，请执行以下步骤：
 

From 85adfe93bc31df6fe6171bf3c40a3f520145213a Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Wed, 12 Apr 2023 17:21:45 +0800
Subject: [PATCH 189/272] sync 1.27 kubectl.md

sync 1.27 kubectl.md
---
 content/zh-cn/docs/reference/kubectl/kubectl.md | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/content/zh-cn/docs/reference/kubectl/kubectl.md b/content/zh-cn/docs/reference/kubectl/kubectl.md
index f0e608fdc7e..bf2cce0d371 100644
--- a/content/zh-cn/docs/reference/kubectl/kubectl.md
+++ b/content/zh-cn/docs/reference/kubectl/kubectl.md
@@ -528,6 +528,19 @@ Toggles whether calls to `kubectl explain` use the new OpenAPIv3 data source ava
 </td>
 </tr>
 
+<tr>
+<td colspan="2">KUBECTL_ENABLE_CMD_SHADOW</td>
+</tr>
+<tr>
+<td></td><td style="line-height: 130%; word-wrap: break-word;">
+<!--
+When set to true, external plugins can be used as subcommands for builtin commands if subcommand does not exist. In alpha stage, this feature can only be used for create command(e.g. kubectl create networkpolicy).
+-->
+当设置为 true 时，如果子命令不存在，外部插件可以用作内置命令的子命令。
+此功能处于 alpha 阶段，只能用于 create 命令（例如 kubectl create networkpolicy）。
+</td>
+</tr>
+
 </tbody>
 </table>
 

From 440fc5ccc35a4f0d8be99d9a368101645dc0bcd8 Mon Sep 17 00:00:00 2001
From: Michael <cloudyonspring@126.com>
Date: Thu, 13 Apr 2023 20:32:02 +0800
Subject: [PATCH 190/272] [zh] sync cluster-cidr-v1alpha1.md

---
 .../cluster-cidr-v1alpha1.md                  | 100 ++++++++++++++++--
 1 file changed, 94 insertions(+), 6 deletions(-)

diff --git a/content/zh-cn/docs/reference/kubernetes-api/cluster-resources/cluster-cidr-v1alpha1.md b/content/zh-cn/docs/reference/kubernetes-api/cluster-resources/cluster-cidr-v1alpha1.md
index a4fd99af85b..bdf887eb0cd 100644
--- a/content/zh-cn/docs/reference/kubernetes-api/cluster-resources/cluster-cidr-v1alpha1.md
+++ b/content/zh-cn/docs/reference/kubernetes-api/cluster-resources/cluster-cidr-v1alpha1.md
@@ -53,7 +53,7 @@ ClusterCIDR 表示启用 MultiCIDRRangeAllocator 时针对每个节点 Pod CIDR
 - **spec** (<a href="{{< ref "../cluster-resources/cluster-cidr-v1alpha1#ClusterCIDRSpec" >}}">ClusterCIDRSpec</a>)
   
   <!--
-  Spec is the desired state of the ClusterCIDR. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
+  spec is the desired state of the ClusterCIDR. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
   -->
   spec 是 ClusterCIDR 的预期状态。更多信息：
   https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
@@ -70,7 +70,7 @@ ClusterCIDRSpec 定义 ClusterCIDR 的预期状态。
 <!--
 - **perNodeHostBits** (int32), required
 
-  PerNodeHostBits defines the number of host bits to be configured per node. A subnet mask determines how much of the address is used for network bits and host bits. For example an IPv4 address of 192.168.0.0/24, splits the address into 24 bits for the network portion and 8 bits for the host portion. To allocate 256 IPs, set this field to 8 (a /24 mask for IPv4 or a /120 for IPv6). Minimum value is 4 (16 IPs). This field is immutable.
+  perNodeHostBits defines the number of host bits to be configured per node. A subnet mask determines how much of the address is used for network bits and host bits. For example an IPv4 address of 192.168.0.0/24, splits the address into 24 bits for the network portion and 8 bits for the host portion. To allocate 256 IPs, set this field to 8 (a /24 mask for IPv4 or a /120 for IPv6). Minimum value is 4 (16 IPs). This field is immutable.
 -->
 - **perNodeHostBits** (int32)，必需
 
@@ -83,7 +83,7 @@ ClusterCIDRSpec 定义 ClusterCIDR 的预期状态。
 - **ipv4** (string)
 
   <!--
-  IPv4 defines an IPv4 IP block in CIDR notation(e.g. "10.0.0.0/8"). At least one of IPv4 and IPv6 must be specified. This field is immutable.
+  ipv4 defines an IPv4 IP block in CIDR notation(e.g. "10.0.0.0/8"). At least one of ipv4 and ipv6 must be specified. This field is immutable.
   -->
 
   ipv4 以 CIDR 表示法定义 IPv4 IP 块（例如 “10.0.0.0/8”）。
@@ -92,7 +92,7 @@ ClusterCIDRSpec 定义 ClusterCIDR 的预期状态。
 - **ipv6** (string)
 
   <!--
-  IPv6 defines an IPv6 IP block in CIDR notation(e.g. "2001:db8::/64"). At least one of IPv4 and IPv6 must be specified. This field is immutable.
+  ipv6 defines an IPv6 IP block in CIDR notation(e.g. "2001:db8::/64"). At least one of ipv4 and ipv6 must be specified. This field is immutable.
   -->
 
   ipv6 以 CIDR 表示法定义 IPv6 IP 块（例如 “2001:db8::/64”）。
@@ -101,7 +101,7 @@ ClusterCIDRSpec 定义 ClusterCIDR 的预期状态。
 - **nodeSelector** (NodeSelector)
 
   <!--
-  NodeSelector defines which nodes the config is applicable to. An empty or nil NodeSelector selects all nodes. This field is immutable.
+  nodeSelector defines which nodes the config is applicable to. An empty or nil nodeSelector selects all nodes. This field is immutable.
 
   <a name="NodeSelector"></a>
   *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.*
@@ -171,7 +171,7 @@ ClusterCIDRList 包含 ClusterCIDR 的列表。
 <!--
 - **items** ([]<a href="{{< ref "../cluster-resources/cluster-cidr-v1alpha1#ClusterCIDR" >}}">ClusterCIDR</a>), required
 
-  Items is the list of ClusterCIDRs.
+  items is the list of ClusterCIDRs.
 -->
 - **items** ([]<a href="{{< ref "../cluster-resources/cluster-cidr-v1alpha1#ClusterCIDR" >}}">ClusterCIDR</a>)，必需
 
@@ -179,7 +179,11 @@ ClusterCIDRList 包含 ClusterCIDR 的列表。
 
 <!--
 ## Operations {#Operations}
+
+<hr>
+
 ### `get` read the specified ClusterCIDR
+
 #### HTTP Request
 -->
 ## 操作 {#Operations}
@@ -233,16 +237,50 @@ GET /apis/networking.k8s.io/v1alpha1/clustercidrs
 
 <!--
 #### Parameters
+
 - **allowWatchBookmarks** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#allowWatchBookmarks" >}}">allowWatchBookmarks</a>
+
 - **continue** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#continue" >}}">continue</a>
+
 - **fieldSelector** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldSelector" >}}">fieldSelector</a>
+
 - **labelSelector** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#labelSelector" >}}">labelSelector</a>
+
 - **limit** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#limit" >}}">limit</a>
+
 - **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
 - **resourceVersion** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#resourceVersion" >}}">resourceVersion</a>
+
 - **resourceVersionMatch** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
+
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
 - **timeoutSeconds** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
+
 - **watch** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#watch" >}}">watch</a>
 -->
 #### 参数
 
@@ -278,6 +316,10 @@ GET /apis/networking.k8s.io/v1alpha1/clustercidrs
 
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
+- **sendInitialEvents** (**查询参数**)：boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
 - **timeoutSeconds** (**查询参数**)：integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -308,6 +350,7 @@ POST /apis/networking.k8s.io/v1alpha1/clustercidrs
 
 <!--
 #### Parameters
+
 - **body**: <a href="{{< ref "../cluster-resources/cluster-cidr-v1alpha1#ClusterCIDR" >}}">ClusterCIDR</a>, required
 - **dryRun** (*in query*): string
 - **fieldManager** (*in query*): string
@@ -360,6 +403,7 @@ PUT /apis/networking.k8s.io/v1alpha1/clustercidrs/{name}
 
 <!--
 #### Parameters
+
 - **name** (*in path*): string, required
   name of the ClusterCIDR
 - **body**: <a href="{{< ref "../cluster-resources/cluster-cidr-v1alpha1#ClusterCIDR" >}}">ClusterCIDR</a>, required
@@ -416,6 +460,7 @@ PATCH /apis/networking.k8s.io/v1alpha1/clustercidrs/{name}
 
 <!-- 
 #### Parameters
+
 - **name** (*in path*): string, required
   name of the ClusterCIDR
 - **body**: <a href="{{< ref "../common-definitions/patch#Patch" >}}">Patch</a>, required
@@ -476,6 +521,7 @@ DELETE /apis/networking.k8s.io/v1alpha1/clustercidrs/{name}
 
 <!--
 #### Parameters
+
 - **name** (*in path*): string, required
   name of the ClusterCIDR
 - **body**: <a href="{{< ref "../common-definitions/delete-options#DeleteOptions" >}}">DeleteOptions</a>
@@ -532,18 +578,56 @@ DELETE /apis/networking.k8s.io/v1alpha1/clustercidrs
 
 <!--
 #### Parameters
+
 - **body**: <a href="{{< ref "../common-definitions/delete-options#DeleteOptions" >}}">DeleteOptions</a>
+
 - **continue** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#continue" >}}">continue</a>
+
 - **dryRun** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
+
 - **fieldSelector** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldSelector" >}}">fieldSelector</a>
+
 - **gracePeriodSeconds** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#gracePeriodSeconds" >}}">gracePeriodSeconds</a>
+
 - **labelSelector** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#labelSelector" >}}">labelSelector</a>
+
 - **limit** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#limit" >}}">limit</a>
+
 - **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
 - **propagationPolicy** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#propagationPolicy" >}}">propagationPolicy</a>
+
 - **resourceVersion** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#resourceVersion" >}}">resourceVersion</a>
+
 - **resourceVersionMatch** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
+
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
 - **timeoutSeconds** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
 -->
 #### 参数
 
@@ -589,6 +673,10 @@ DELETE /apis/networking.k8s.io/v1alpha1/clustercidrs
 
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
+- **sendInitialEvents** (**查询参数**)：boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
 - **timeoutSeconds** (**查询参数**)：integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>

From f86545ddcf76263cda660668c3825bc79f807980 Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Thu, 13 Apr 2023 21:19:36 +0800
Subject: [PATCH 191/272] sync 1.27 _index.md

sync 1.27 _index.md
---
 content/zh-cn/docs/reference/_index.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/content/zh-cn/docs/reference/_index.md b/content/zh-cn/docs/reference/_index.md
index 61b2b4776dc..7a788e469ae 100644
--- a/content/zh-cn/docs/reference/_index.md
+++ b/content/zh-cn/docs/reference/_index.md
@@ -193,12 +193,10 @@ operator to use or manage a cluster.
 <!--
 ## Config API for kubeadm
 
-* [v1beta2](/docs/reference/config-api/kubeadm-config.v1beta2/)
 * [v1beta3](/docs/reference/config-api/kubeadm-config.v1beta3/)
 -->
 ## kubeadm 的配置 API   {#config-api-for-kubeadm}
 
-* [v1beta2](/zh-cn/docs/reference/config-api/kubeadm-config.v1beta2/)
 * [v1beta3](/zh-cn/docs/reference/config-api/kubeadm-config.v1beta3/)
 
 <!--

From b953396a7795152d97edca7ba3d691e57a5df776 Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Thu, 13 Apr 2023 21:30:54 +0800
Subject: [PATCH 192/272] sync 1.27 client-authentication.v1.md

sync 1.27 client-authentication.v1.md
---
 .../zh-cn/docs/reference/config-api/client-authentication.v1.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/zh-cn/docs/reference/config-api/client-authentication.v1.md b/content/zh-cn/docs/reference/config-api/client-authentication.v1.md
index 3e338d18b21..af0eb45a16d 100644
--- a/content/zh-cn/docs/reference/config-api/client-authentication.v1.md
+++ b/content/zh-cn/docs/reference/config-api/client-authentication.v1.md
@@ -259,7 +259,7 @@ itself should at least be protected via file permissions.
 <thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
 <tbody>
 <tr><td><code>expirationTimestamp</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta"><code>meta/v1.Time</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#time-v1-meta"><code>meta/v1.Time</code></a>
 </td>
 <td>
    <!--ExpirationTimestamp indicates a time when the provided credentials expire.-->

From 7a314004d3ad0506b29e1dd98a8952a91e23002a Mon Sep 17 00:00:00 2001
From: Jefftree <jeffrey.ying86@live.com>
Date: Tue, 4 Apr 2023 19:54:05 +0000
Subject: [PATCH 193/272] Blog post for OpenAPI and Field Validation

---
 ...23-04-24-openapi-v3-field-validation-ga.md | 133 ++++++++++++++++++
 1 file changed, 133 insertions(+)
 create mode 100644 content/en/blog/_posts/2023-04-24-openapi-v3-field-validation-ga.md

diff --git a/content/en/blog/_posts/2023-04-24-openapi-v3-field-validation-ga.md b/content/en/blog/_posts/2023-04-24-openapi-v3-field-validation-ga.md
new file mode 100644
index 00000000000..1bd1295f975
--- /dev/null
+++ b/content/en/blog/_posts/2023-04-24-openapi-v3-field-validation-ga.md
@@ -0,0 +1,133 @@
+---
+layout: blog
+title: "Server Side Field Validation and OpenAPI V3 move to GA"
+date: 2023-04-24
+slug: openapi-v3-field-validation-ga
+---
+
+**Author**: Jeffrey Ying (Google), Antoine Pelisse (Google)
+
+Before Kubernetes v1.8 (!), typos, mis-indentations or minor errors in
+YAMLs could have catastrophic consequences (e.g. a typo like
+forgetting the trailing s in `replica: 1000` could cause an outage,
+because the value would be ignored and missing, forcing a reset of
+replicas back to 1). This was solved back then by fetching the OpenAPI
+v2 in kubectl and using it to verify that fields were correct and
+present before applying. Unfortunately, at that time, Custom Resource
+Definitions didn’t exist, and the code was written under that
+assumption. When CRDs were later introduced, the lack of flexibility
+in the validation code forced some hard decisions in the way CRDs
+exposed their schema, leaving us in a cycle of bad validation causing
+bad OpenAPI and vice-versa. With the new OpenAPI v3 and Server Field
+Validation being GA in 1.27, we’ve now solved both of these problems.
+
+Server Side Field Validation offers resource validation on create,
+update and patch requests to the apiserver and was added to Kubernetes
+in v1.25, beta in v1.26 and is now GA in v1.27. It provides all the
+functionality of kubectl validate on the server side.
+
+[OpenAPI](https://swagger.io/specification/) is a standard, language
+agnostic interface for discovering the set of operations and types
+that a Kubernetes cluster supports. OpenAPI V3 is the latest standard
+of the OpenAPI and is an improvement upon [OpenAPI
+V2](https://kubernetes.io/blog/2016/12/kubernetes-supports-openapi/)
+which has been supported since Kubernetes 1.5. OpenAPI V3 support was
+added in Kubernetes in v1.23, moved to beta in v1.24 and is now GA in
+v1.27.
+
+## OpenAPI V3
+
+### What does OpenAPI V3 offer over V2
+
+#### Built-in types
+
+Kubernetes offers certain annotations on fields that are not
+representable in OpenAPI V2, or sometimes not represented in the
+OpenAPI v2 that Kubernetes generate. Most notably, the "default" field
+is published in OpenAPI V3 while omitted in OpenAPI V2. A single type
+that can represent multiple types is also expressed correctly in
+OpenAPI V3 with the oneOf field. This includes proper representations
+for IntOrString and Quantity.
+
+#### Custom Resource Definitions
+
+In Kubernetes, Custom Resource Definitions use a structural OpenAPI V3
+schema that cannot be represented as OpenAPI V2 without a loss of
+certain fields. Some of these include nullable, default, anyOf, oneOf,
+not, etc. OpenAPI V3 is a completely lossless representation of the
+CustomResourceDefinition structural schema.
+
+### How do I use it?
+
+The OpenAPI V3 root discovery can be found at the `/openapi/v3`
+endpoint of a Kubernetes API server. OpenAPI V3 documents are grouped
+by group-version to reduce the size of the data transported, the
+separate documents can be accessed at
+`/openapi/v3/apis/<group>/<version>` and `/openapi/v3/api/v1`
+representing the legacy group version. Please refer to the [Kubernetes
+API Documentation](/docs/concepts/overview/kubernetes-api/) for more
+information around this endpoint.
+
+Various consumers of the OpenAPI have already been updated to consume
+v3, including the entirety of kubectl, and server side apply. An
+OpenAPI V3 Golang client is available in
+[client-go](https://github.com/kubernetes/client-go/blob/release-1.27/openapi3/root.go).
+
+## Server Side Field Validation
+
+The query parameter `fieldValidation` may be used to indicate the
+level of field validation the server should perform. If the parameter
+is not passed, server side field validation is in `Warn` mode by
+default.
+
+- Strict: Strict field validation, errors on validation failure
+- Warn: Field validation is performed, but errors are exposed as
+  warnings rather than failing the request
+- Ignore: No server side field validation is performed
+
+kubectl will skip client side validation and will automatically use
+server side field validation in `Strict` mode. Controllers by default
+use server side field validation in `Warn` mode.
+
+With client side validation, we had to be extra lenient because some
+fields were missing from OpenAPI V2 and we didn’t want to reject
+possibly valid objects. This is all fixed in server side validation.
+Additional documentation may be found
+[here](/docs/reference/using-api/api-concepts/#field-validation)
+
+## What's next?
+
+With Server Side Field Validation and OpenAPI V3 released as GA, we
+introduce more accurate representations of Kubernetes resources. It is
+recommended to use server side field validation over client side, but
+with OpenAPI V3, clients are free to implement their own validation if
+necessary (to “shift things left”) and we guarantee a full lossless
+schema published by OpenAPI.
+
+Some existing efforts will further improve the information available
+through OpenAPI including [CEL validation and
+admission](/docs/reference/using-api/cel/), along with OpenAPI
+annotations on built-in types.
+
+Many other tools can be built for authoring and transforming resources
+using the type information found in the OpenAPI v3.
+
+## How to get involved?
+
+These two features are driven by the SIG API Machinery community,
+available on the slack channel \#sig-api-machinery, through the
+[mailing
+list](https://groups.google.com/g/kubernetes-sig-api-machinery) and we
+meet every other Wednesday at 11:00 AM PT on Zoom.
+
+We offer a huge thanks to all the contributors who helped design,
+implement, and review these two features.
+
+- Alexander Zielenski
+- Antoine Pelisse
+- Daniel Smith
+- David Eads
+- Jeffrey Ying
+- Jordan Liggitt
+- Kevin Delgado
+- Sean Sullivan

From 5f71626646335617593151a93ddaa9f644bd6a8f Mon Sep 17 00:00:00 2001
From: Dan Winship <danwinship@redhat.com>
Date: Thu, 13 Apr 2023 12:45:10 -0400
Subject: [PATCH 194/272] Drop kube-proxy/kubelet skew requirement

KEP-3178 has removed the interdependence between kubelet and
kube-proxy as of 1.25 so there should be no skew problems in the
future.
---
 content/en/releases/version-skew-policy.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/content/en/releases/version-skew-policy.md b/content/en/releases/version-skew-policy.md
index c0a1528af2c..0cc10a37d89 100644
--- a/content/en/releases/version-skew-policy.md
+++ b/content/en/releases/version-skew-policy.md
@@ -170,7 +170,6 @@ Running a cluster with `kubelet` instances that are persistently two minor versi
 
 ### kube-proxy
 
-* `kube-proxy` must be the same minor version as `kubelet` on the node.
 * `kube-proxy` must not be newer than `kube-apiserver`.
 * `kube-proxy` must be at most two minor versions older than `kube-apiserver.`
 

From 936ac5574fed896adc6a489f9fb4652913910a5a Mon Sep 17 00:00:00 2001
From: Wei Huang <weihuang@apple.com>
Date: Thu, 13 Apr 2023 11:36:02 -0700
Subject: [PATCH 195/272] fixup: address comments

---
 .../scheduling-eviction/scheduling-framework.md     | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/content/en/docs/concepts/scheduling-eviction/scheduling-framework.md b/content/en/docs/concepts/scheduling-eviction/scheduling-framework.md
index 507992b445f..8ce367db654 100644
--- a/content/en/docs/concepts/scheduling-eviction/scheduling-framework.md
+++ b/content/en/docs/concepts/scheduling-eviction/scheduling-framework.md
@@ -59,8 +59,17 @@ stateful tasks.
 These plugins are called prior to adding Pods to the internal active queue, where Pods are marked as
 ready for scheduling.
 
-Only when all PreEnqueue plugins return `Success`, the Pod can enter the aforementioned scheduling
-cycle. Otherwise, it's moved and parked in the internal unschedulable Pods pool.
+Only when all PreEnqueue plugins return `Success`, the Pod is allowed to enter the active queue.
+Otherwise, it's placed in the internal unschedulable Pods list.
+
+{{< note >}}
+
+More details about how internal scheduler queues work, please check this
+[document](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-scheduling/scheduler_queues.md).
+
+{{< /note >}}
+
+> Check more details
 
 ### QueueSort {#queue-sort}
 

From 184185755a90f027ae11537f5c5930d809fc2621 Mon Sep 17 00:00:00 2001
From: Tim Bannister <tim@scalefactory.com>
Date: Thu, 13 Apr 2023 20:42:37 +0100
Subject: [PATCH 196/272] Fix typography

---
 content/en/blog/_posts/2023-04-17-topology-spread-features.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/blog/_posts/2023-04-17-topology-spread-features.md b/content/en/blog/_posts/2023-04-17-topology-spread-features.md
index 170496742c8..9edaada138d 100644
--- a/content/en/blog/_posts/2023-04-17-topology-spread-features.md
+++ b/content/en/blog/_posts/2023-04-17-topology-spread-features.md
@@ -5,7 +5,7 @@ date: 2023-04-17
 slug: fine-grained-pod-topology-spread-features-beta
 ---
 
-**Authors:** [Alex Wang](https://github.com/denkensk)(Shopee), [Kante Yin](https://github.com/kerthcet)(DaoCloud), [Kensei Nakada](https://github.com/sanposhiho)(Mercari)
+**Authors:** [Alex Wang](https://github.com/denkensk) (Shopee), [Kante Yin](https://github.com/kerthcet) (DaoCloud), [Kensei Nakada](https://github.com/sanposhiho) (Mercari)
 
 In Kubernetes v1.19, [Pod topology spread constraints](/docs/concepts/scheduling-eviction/topology-spread-constraints/)
 went to general availability (GA).

From 625b03134442db11e06b8a54814047e0739afc99 Mon Sep 17 00:00:00 2001
From: Wei Huang <weihuang@apple.com>
Date: Thu, 13 Apr 2023 14:37:57 -0700
Subject: [PATCH 197/272] fixup: address comments

---
 .../scheduling-eviction/scheduling-framework.md    | 14 ++++----------
 1 file changed, 4 insertions(+), 10 deletions(-)

diff --git a/content/en/docs/concepts/scheduling-eviction/scheduling-framework.md b/content/en/docs/concepts/scheduling-eviction/scheduling-framework.md
index 8ce367db654..ea0d981055b 100644
--- a/content/en/docs/concepts/scheduling-eviction/scheduling-framework.md
+++ b/content/en/docs/concepts/scheduling-eviction/scheduling-framework.md
@@ -52,7 +52,7 @@ equivalent to "Predicate" and "Scoring" is equivalent to "Priority function".
 One plugin may register at multiple extension points to perform more complex or
 stateful tasks.
 
-{{< figure src="/images/docs/scheduling-framework-extensions.png" title="scheduling framework extension points" class="diagram-large">}}
+{{< figure src="/images/docs/scheduling-framework-extensions.png" title="Scheduling framework extension points" class="diagram-large">}}
 
 ### PreEnqueue {#pre-enqueue}
 
@@ -60,16 +60,10 @@ These plugins are called prior to adding Pods to the internal active queue, wher
 ready for scheduling.
 
 Only when all PreEnqueue plugins return `Success`, the Pod is allowed to enter the active queue.
-Otherwise, it's placed in the internal unschedulable Pods list.
+Otherwise, it's placed in the internal unschedulable Pods list, and doesn't get an `Unschedulable` condition.
 
-{{< note >}}
-
-More details about how internal scheduler queues work, please check this
-[document](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-scheduling/scheduler_queues.md).
-
-{{< /note >}}
-
-> Check more details
+For more details about how internal scheduler queues work, read
+[Scheduling queue in kube-scheduler](https://github.com/kubernetes/community/blob/f03b6d5692bd979f07dd472e7b6836b2dad0fd9b/contributors/devel/sig-scheduling/scheduler_queues.md).
 
 ### QueueSort {#queue-sort}
 

From 9a6e46cce53b4e4e1c14a15d3c98a96a98f8dc28 Mon Sep 17 00:00:00 2001
From: Guangwen Feng <fenggw-fnst@fujitsu.com>
Date: Fri, 14 Apr 2023 08:41:16 +0800
Subject: [PATCH 198/272] [zh-cn] Sync disruptions.md (#40662)

Signed-off-by: Guangwen Feng <fenggw-fnst@fujitsu.com>
---
 .../concepts/workloads/pods/disruptions.md    | 34 +++++++++++--------
 1 file changed, 19 insertions(+), 15 deletions(-)

diff --git a/content/zh-cn/docs/concepts/workloads/pods/disruptions.md b/content/zh-cn/docs/concepts/workloads/pods/disruptions.md
index be0a46dc197..1af0d70bf35 100644
--- a/content/zh-cn/docs/concepts/workloads/pods/disruptions.md
+++ b/content/zh-cn/docs/concepts/workloads/pods/disruptions.md
@@ -130,15 +130,15 @@ deleting deployments or pods bypasses Pod Disruption Budgets.
 
 Here are some ways to mitigate involuntary disruptions:
 -->
-## 处理干扰
+## 处理干扰   {#dealing-with-disruptions}
 
 以下是减轻非自愿干扰的一些方法：
 
 <!--
 - Ensure your pod [requests the resources](/docs/tasks/configure-pod-container/assign-memory-resource) it needs.
 - Replicate your application if you need higher availability.  (Learn about running replicated
-[stateless](/docs/tasks/run-application/run-stateless-application-deployment/)
-and [stateful](/docs/tasks/run-application/run-replicated-stateful-application/) applications.)
+  [stateless](/docs/tasks/run-application/run-stateless-application-deployment/)
+  and [stateful](/docs/tasks/run-application/run-replicated-stateful-application/) applications.)
 - For even higher availability when running replicated applications,
   spread applications across racks (using
   [anti-affinity](/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity))
@@ -266,6 +266,18 @@ during application updates is configured in the spec for the specific workload r
 在进行滚动升级时不受 PDB 的限制。
 应用更新期间的故障处理方式是在对应的工作负载资源的 `spec` 中配置的。
 
+<!--
+It is recommended to set `AlwaysAllow` [Unhealthy Pod Eviction Policy](/docs/tasks/run-application/configure-pdb/#unhealthy-pod-eviction-policy)
+to your PodDisruptionBudgets to support eviction of misbehaving applications during a node drain.
+The default behavior is to wait for the application pods to become [healthy](/docs/tasks/run-application/configure-pdb/#healthiness-of-a-pod)
+before the drain can proceed.
+-->
+建议在你的 PodDisruptionBudget 中将
+[不健康 Pod 驱逐策略](/zh-cn/docs/tasks/run-application/configure-pdb/#unhealthy-pod-eviction-policy)
+设置为 `AlwaysAllow` 以支持在节点腾空期间驱逐行为不当的应用程序。
+默认行为是等待应用程序 Pod 变得
+[健康](/zh-cn/docs/tasks/run-application/configure-pdb/#healthiness-of-a-pod)，然后才能继续执行腾空。
+
 <!--
 When a pod is evicted using the eviction API, it is gracefully
 [terminated](/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination), honoring the
@@ -434,14 +446,6 @@ can happen, according to:
 
 {{< feature-state for_k8s_version="v1.26" state="beta" >}}
 
-{{< note >}}
-<!--
-If you are using an older version of Kubernetes than {{< skew currentVersion >}}
-please refer to the corresponding version of the documentation.
--->
-如果你正使用的 Kubernetes 版本早于 {{< skew currentVersion >}}，请参阅对应版本的文档。
-{{< /note >}}
-
 {{< note >}}
 <!-- 
 In order to use this behavior, you must have the `PodDisruptionConditions`
@@ -464,10 +468,10 @@ indicates one of the following reasons for the Pod termination:
 状况中的 `reason` 字段进一步给出 Pod 终止的原因，如下：
 
 <!--
-`PreemptionByKubeScheduler`
+`PreemptionByScheduler`
 : Pod is due to be {{<glossary_tooltip term_id="preemption" text="preempted">}} by a scheduler in order to accommodate a new Pod with a higher priority. For more information, see [Pod priority preemption](/docs/concepts/scheduling-eviction/pod-priority-preemption/).
 -->
-`PreemptionByKubeScheduler`
+`PreemptionByScheduler`
 : Pod 将被调度器{{<glossary_tooltip term_id="preemption" text="抢占">}}，
 目的是接受优先级更高的新 Pod。
 要了解更多的相关信息，请参阅 [Pod 优先级和抢占](/zh-cn/docs/concepts/scheduling-eviction/pod-priority-preemption/)。
@@ -543,7 +547,7 @@ and Application Owner as separate roles with limited knowledge
 of each other.   This separation of responsibilities
 may make sense in these scenarios:
 -->
-## 分离集群所有者和应用所有者角色
+## 分离集群所有者和应用所有者角色   {#separating-cluster-owner-and-application-owner-roles}
 
 通常，将集群管理者和应用所有者视为彼此了解有限的独立角色是很有用的。这种责任分离在下面这些场景下是有意义的：
 
@@ -573,7 +577,7 @@ you may not need to use Pod Disruption Budgets.
 If you are a Cluster Administrator, and you need to perform a disruptive action on all
 the nodes in your cluster, such as a node or system software upgrade, here are some options:
 -->
-## 如何在集群上执行干扰性操作
+## 如何在集群上执行干扰性操作   {#how-to-perform-disruptive-actions-on-your-cluster}
 
 如果你是集群管理员，并且需要对集群中的所有节点执行干扰操作，例如节点或系统软件升级，则可以使用以下选项
 

From 22b6bc99291701f338126a93bf981243e29bbbee Mon Sep 17 00:00:00 2001
From: Michael <cloudyonspring@126.com>
Date: Fri, 14 Apr 2023 09:15:46 +0800
Subject: [PATCH 199/272] [zh] sync self-subject-review-v1beta1.md (#40665)

---
 .../self-subject-review-v1beta1.md            | 181 ++++++++++++++++++
 1 file changed, 181 insertions(+)
 create mode 100644 content/zh-cn/docs/reference/kubernetes-api/authentication-resources/self-subject-review-v1beta1.md

diff --git a/content/zh-cn/docs/reference/kubernetes-api/authentication-resources/self-subject-review-v1beta1.md b/content/zh-cn/docs/reference/kubernetes-api/authentication-resources/self-subject-review-v1beta1.md
new file mode 100644
index 00000000000..fd3ce719886
--- /dev/null
+++ b/content/zh-cn/docs/reference/kubernetes-api/authentication-resources/self-subject-review-v1beta1.md
@@ -0,0 +1,181 @@
+---
+api_metadata:
+  apiVersion: "authentication.k8s.io/v1beta1"
+  import: "k8s.io/api/authentication/v1beta1"
+  kind: "SelfSubjectReview"
+content_type: "api_reference"
+description: "SelfSubjectReview 包含 kube-apiserver 所拥有的与发出此请求的用户有关的用户信息。"
+title: "SelfSubjectReview v1beta1"
+weight: 6
+---
+<!--
+api_metadata:
+  apiVersion: "authentication.k8s.io/v1beta1"
+  import: "k8s.io/api/authentication/v1beta1"
+  kind: "SelfSubjectReview"
+content_type: "api_reference"
+description: "SelfSubjectReview contains the user information that the kube-apiserver has about the user making this request."
+title: "SelfSubjectReview v1beta1"
+weight: 6
+auto_generated: true
+-->
+
+`apiVersion: authentication.k8s.io/v1beta1`
+
+`import "k8s.io/api/authentication/v1beta1"`
+
+## SelfSubjectReview {#SelfSubjectReview}
+
+<!--
+SelfSubjectReview contains the user information that the kube-apiserver has about the user making this request. When using impersonation, users will receive the user info of the user being impersonated.  If impersonation or request header authentication is used, any extra keys will have their case ignored and returned as lowercase.
+-->
+SelfSubjectReview 包含 kube-apiserver 所拥有的与发出此请求的用户有关的用户信息。
+使用伪装时，用户将收到被伪装用户的用户信息。
+如果使用伪装或请求头部进行身份验证，则所有额外的键都将被忽略大小写并以小写形式返回结果。
+
+<hr>
+
+- **apiVersion**: authentication.k8s.io/v1beta1
+
+- **kind**: SelfSubjectReview
+
+- **metadata** (<a href="{{< ref "../common-definitions/object-meta#ObjectMeta" >}}">ObjectMeta</a>)
+
+  <!--
+  Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
+  -->
+  标准的对象元数据。更多信息：
+  https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
+
+- **status** (<a href="{{< ref "../authentication-resources/self-subject-review-v1beta1#SelfSubjectReviewStatus" >}}">SelfSubjectReviewStatus</a>)
+
+  <!--
+  Status is filled in by the server with the user attributes.
+  -->
+  status 由服务器以用户属性进行填充。
+
+## SelfSubjectReviewStatus {#SelfSubjectReviewStatus}
+
+<!--
+SelfSubjectReviewStatus is filled by the kube-apiserver and sent back to a user.
+-->
+SelfSubjectReviewStatus 由 kube-apiserver 进行填充并发送回用户。
+
+<hr>
+
+- **userInfo** (UserInfo)
+
+  <!--
+  User attributes of the user making this request.
+  -->
+  发出此请求的用户的用户属性。
+
+  <a name="UserInfo"></a>
+  <!--
+  *UserInfo holds the information about the user needed to implement the user.Info interface.*
+  -->
+  **userInfo 包含实现 user.Info 接口所需的用户相关信息。**
+
+  - **userInfo.extra** (map[string][]string)
+
+    <!--
+    Any additional information provided by the authenticator.
+    -->
+
+    由身份认证组件提供的所有附加信息。
+
+  - **userInfo.groups** ([]string)
+
+    <!--
+    The names of groups this user is a part of.
+    -->
+
+    此用户所属的用户组的名称。
+
+  - **userInfo.uid** (string)
+
+    <!--
+    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.
+    -->
+
+    跨时间标识此用户的唯一值。如果此用户被删除且另一个同名用户被添加，他们将具有不同的 UID。
+
+  - **userInfo.username** (string)
+
+    <!--
+    The name that uniquely identifies this user among all active users.
+    -->
+
+    在所有活跃用户中标识此用户的名称。
+
+<!--
+## Operations {#Operations}
+-->
+## 操作 {#Operations}
+
+<hr>
+
+<!--
+### `create` create a SelfSubjectReview
+
+#### HTTP Request
+-->
+### `create` 创建 SelfSubjectReview
+
+#### HTTP 请求
+
+POST /apis/authentication.k8s.io/v1beta1/selfsubjectreviews
+
+<!--
+#### Parameters
+
+- **body**: <a href="{{< ref "../authentication-resources/self-subject-review-v1beta1#SelfSubjectReview" >}}">SelfSubjectReview</a>, required
+
+- **dryRun** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
+
+- **fieldManager** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
+
+- **fieldValidation** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
+
+- **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+-->
+#### 参数
+
+- **body**: <a href="{{< ref "../authentication-resources/self-subject-review-v1beta1#SelfSubjectReview" >}}">SelfSubjectReview</a>, 必需
+
+- **dryRun** (**查询参数**): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
+
+- **fieldManager** (**查询参数**): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
+
+- **fieldValidation** (**查询参数**): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
+
+- **pretty** (**查询参数**): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
+<!--
+#### Response
+-->
+#### 响应
+
+200 (<a href="{{< ref "../authentication-resources/self-subject-review-v1beta1#SelfSubjectReview" >}}">SelfSubjectReview</a>): OK
+
+201 (<a href="{{< ref "../authentication-resources/self-subject-review-v1beta1#SelfSubjectReview" >}}">SelfSubjectReview</a>): Created
+
+202 (<a href="{{< ref "../authentication-resources/self-subject-review-v1beta1#SelfSubjectReview" >}}">SelfSubjectReview</a>): Accepted
+
+401: Unauthorized

From 6cbc3aaf2ed5aea0ab497ccca7c6a45fb451575a Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Fri, 14 Apr 2023 09:24:13 +0800
Subject: [PATCH 200/272] sync 1.27 apiserver-audit.v1.md (#40669)

sync 1.27 apiserver-audit.v1.md
---
 .../reference/config-api/apiserver-audit.v1.md   | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/content/zh-cn/docs/reference/config-api/apiserver-audit.v1.md b/content/zh-cn/docs/reference/config-api/apiserver-audit.v1.md
index 6d2fba5492f..f3a580defc7 100644
--- a/content/zh-cn/docs/reference/config-api/apiserver-audit.v1.md
+++ b/content/zh-cn/docs/reference/config-api/apiserver-audit.v1.md
@@ -101,7 +101,7 @@ Event 结构包含可出现在 API 审计日志中的所有信息。
 </tr>
     
 <tr><td><code>user</code> <B><!--[Required]-->[必需]</B><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#userinfo-v1-authentication"><code>authentication/v1.UserInfo</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#userinfo-v1-authentication"><code>authentication/v1.UserInfo</code></a>
 </td>
 <td>
    <!--Authenticated user information.-->
@@ -112,7 +112,7 @@ Event 结构包含可出现在 API 审计日志中的所有信息。
 </tr>
 
 <tr><td><code>impersonatedUser</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#userinfo-v1-authentication"><code>authentication/v1.UserInfo</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#userinfo-v1-authentication"><code>authentication/v1.UserInfo</code></a>
 </td>
 <td>
    <!--Impersonated user information.-->
@@ -187,7 +187,7 @@ Note: All but the last IP can be arbitrarily set by the client.
 </tr>
 
 <tr><td><code>responseStatus</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#status-v1-meta"><code>meta/v1.Status</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#status-v1-meta"><code>meta/v1.Status</code></a>
 </td>
 <td>
    <!--The response status, populated even when the ResponseObject is not a Status type.
@@ -237,7 +237,7 @@ at Response Level.-->
 </tr>
 
 <tr><td><code>requestReceivedTimestamp</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#microtime-v1-meta"><code>meta/v1.MicroTime</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#microtime-v1-meta"><code>meta/v1.MicroTime</code></a>
 </td>
 <td>
    <!--Time the request reached the apiserver.-->
@@ -248,7 +248,7 @@ at Response Level.-->
 </tr>
 
 <tr><td><code>stageTimestamp</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#microtime-v1-meta"><code>meta/v1.MicroTime</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#microtime-v1-meta"><code>meta/v1.MicroTime</code></a>
 </td>
 <td>
    <!--Time the request reached current audit stage.-->
@@ -301,7 +301,7 @@ EventList 是审计事件（Event）的列表。
 <tr><td><code>kind</code><br/>string</td><td><code>EventList</code></td></tr>
 
 <tr><td><code>metadata</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta"><code>meta/v1.ListMeta</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#listmeta-v1-meta"><code>meta/v1.ListMeta</code></a>
 </td>
 <td>
    <span class="text-muted"><!--No description provided.-->列表结构元数据</span>
@@ -343,7 +343,7 @@ Policy 定义的是审计日志的配置以及不同类型请求的日志记录
 <tr><td><code>kind</code><br/>string</td><td><code>Policy</code></td></tr>
   
 <tr><td><code>metadata</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#objectmeta-v1-meta"><code>meta/v1.ObjectMeta</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#objectmeta-v1-meta"><code>meta/v1.ObjectMeta</code></a>
 </td>
 <td>
    <!--ObjectMeta is included for interoperability with API infrastructure.Refer to the Kubernetes API documentation for the fields of the <code>metadata</code> field.-->
@@ -428,7 +428,7 @@ PolicyList 是由审计策略（Policy）组成的列表。
 <tr><td><code>kind</code><br/>string</td><td><code>PolicyList</code></td></tr>
 
 <tr><td><code>metadata</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#listmeta-v1-meta"><code>meta/v1.ListMeta</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#listmeta-v1-meta"><code>meta/v1.ListMeta</code></a>
 </td>
 <td>
    <span class="text-muted"><!--No description provided.-->列表结构元数据。</span>

From e0b8ec7658f5abd830afaa4ef52efa21873501de Mon Sep 17 00:00:00 2001
From: windsonsea <haifeng.yao@daocloud.io>
Date: Thu, 13 Apr 2023 14:08:34 +0800
Subject: [PATCH 201/272] [zh] sync /controllers/cron-jobs.md

---
 .../workloads/controllers/cron-jobs.md        | 126 +++++++++---------
 1 file changed, 64 insertions(+), 62 deletions(-)

diff --git a/content/zh-cn/docs/concepts/workloads/controllers/cron-jobs.md b/content/zh-cn/docs/concepts/workloads/controllers/cron-jobs.md
index b15ebb56b50..1f4295dae81 100644
--- a/content/zh-cn/docs/concepts/workloads/controllers/cron-jobs.md
+++ b/content/zh-cn/docs/concepts/workloads/controllers/cron-jobs.md
@@ -3,7 +3,6 @@ title: CronJob
 content_type: concept
 weight: 80
 ---
-
 <!--
 reviewers:
 - erictune
@@ -21,9 +20,9 @@ weight: 80
 <!--
 A _CronJob_ creates {{< glossary_tooltip term_id="job" text="Jobs" >}} on a repeating schedule.
 
-CronJob is meant for performing regular scheduled actions such as backups, report generation, 
-and so on. One CronJob object is like one line of a _crontab_ (cron table) file on a 
-Unix system. It runs a job periodically on a given schedule, written in 
+CronJob is meant for performing regular scheduled actions such as backups, report generation,
+and so on. One CronJob object is like one line of a _crontab_ (cron table) file on a
+Unix system. It runs a job periodically on a given schedule, written in
 [Cron](https://en.wikipedia.org/wiki/Cron) format.
 -->
 **CronJob** 创建基于时隔重复调度的 {{< glossary_tooltip term_id="job" text="Job" >}}。
@@ -155,21 +154,21 @@ Other than the standard syntax, some macros like `@monthly` can also be used:
 除了标准语法，还可以使用一些类似 `@monthly` 的宏：
 
 <!-- 
-| Entry 	| Description   | Equivalent to |
-| ------------- | ------------- |-------------  |
-| @yearly (or @annually) | Run once a year at midnight of 1 January | 0 0 1 1 * |
-| @monthly               | Run once a month at midnight of the first day of the month | 0 0 1 * * |
-| @weekly                | Run once a week at midnight on Sunday morning | 0 0 * * 0 |
-| @daily (or @midnight)  | Run once a day at midnight | 0 0 * * * |
-| @hourly                | Run once an hour at the beginning of the hour | 0 * * * * |
+| Entry 										| Description																									| Equivalent to |
+| ------------- 						| ------------- 																							|-------------  |
+| @yearly (or @annually)		| Run once a year at midnight of 1 January										| 0 0 1 1 * 		|
+| @monthly 									| Run once a month at midnight of the first day of the month	| 0 0 1 * * 		|
+| @weekly 									| Run once a week at midnight on Sunday morning								| 0 0 * * 0 		|
+| @daily (or @midnight)			| Run once a day at midnight																	| 0 0 * * * 		|
+| @hourly 									| Run once an hour at the beginning of the hour								| 0 * * * * 		|
 -->
-| 输入                      | 描述                          | 相当于         |
-| -------------             | -------------                 |-------------   |
-| @yearly (或 @annually)    | 每年 1 月 1 日的午夜运行一次  | 0 0 1 1 *      |
-| @monthly                  | 每月第一天的午夜运行一次      | 0 0 1 * *      |
-| @weekly                   | 每周的周日午夜运行一次        | 0 0 * * 0      |
-| @daily (或 @midnight)     | 每天午夜运行一次              | 0 0 * * *      |
-| @hourly                   | 每小时的开始一次              | 0 * * * *      |
+| 输入                   | 描述                      | 相当于        |
+| ---------------------- | ------------------------ | ------------ |
+| @yearly (或 @annually) | 每年 1 月 1 日的午夜运行一次 | 0 0 1 1 *    |
+| @monthly               | 每月第一天的午夜运行一次     | 0 0 1 * *    |
+| @weekly                | 每周的周日午夜运行一次       | 0 0 * * 0    |
+| @daily (或 @midnight)  | 每天午夜运行一次            | 0 0 * * *    |
+| @hourly                | 每小时的开始一次            | 0 * * * *    |
 
 <!--
 To generate CronJob schedule expressions, you can also use web tools like [crontab.guru](https://crontab.guru/).
@@ -318,55 +317,29 @@ For another way to clean up jobs automatically, see [Clean up finished jobs auto
 
 <!-- 
 ### Time zones
-
-For CronJobs with no time zone specified, the {{< glossary_tooltip term_id="kube-controller-manager" text="kube-controller-manager" >}} interprets schedules relative to its local time zone.
 -->
 ## 时区    {#time-zones}
 
+{{< feature-state for_k8s_version="v1.27" state="stable" >}}
+
+<!--
+For CronJobs with no time zone specified, the {{< glossary_tooltip term_id="kube-controller-manager" text="kube-controller-manager" >}}
+interprets schedules relative to its local time zone.
+-->
 对于没有指定时区的 CronJob，
 {{< glossary_tooltip term_id="kube-controller-manager" text="kube-controller-manager" >}}
 基于本地时区解释排期表（Schedule）。
 
-{{< feature-state for_k8s_version="v1.25" state="beta" >}}
-
 <!--
-If you enable the  `CronJobTimeZone` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/),
-you can specify a time zone for a CronJob (if you don't enable that feature gate, or if you are using a version of
-Kubernetes that does not have experimental time zone support, all CronJobs in your cluster have an unspecified
-timezone).
-
-When you have the feature enabled, you can set `.spec.timeZone` to the name of a valid [time zone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). For example, setting
-`.spec.timeZone: "Etc/UTC"` instructs Kubernetes to interpret the schedule relative to Coordinated Universal Time.
+You can specify a time zone for a CronJob by setting `.spec.timeZone` to the name
+of a valid [time zone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
+For example, setting `.spec.timeZone: "Etc/UTC"` instructs Kubernetes to interpret
+the schedule relative to Coordinated Universal Time.
 -->
-如果启用了 `CronJobTimeZone` [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)，
-你可以为 CronJob 指定一个时区（如果你没有启用该特性门控，或者你使用的是不支持试验性时区功能的
-Kubernetes 版本，集群中所有 CronJob 的时区都是未指定的）。
-
-启用该特性后，你可以将 `spec.timeZone`
-设置为有效[时区](https://zh.wikipedia.org/wiki/%E6%97%B6%E5%8C%BA%E4%BF%A1%E6%81%AF%E6%95%B0%E6%8D%AE%E5%BA%93)名称。
-例如，设置 `spec.timeZone: "Etc/UTC"` 指示 Kubernetes 采用 UTC 来解释排期表。
-
-{{< caution >}}
-<!--
-The implementation of the CronJob API in Kubernetes {{< skew currentVersion >}} lets you set
-the `.spec.schedule` field to include a timezone; for example: `CRON_TZ=UTC * * * * *`
-or `TZ=UTC * * * * *`.
-
-Specifying a timezone that way is **not officially supported** (and never has been).
-
-If you try to set a schedule that includes `TZ` or `CRON_TZ` timezone specification,
-Kubernetes reports a [warning](/blog/2020/09/03/warnings/) to the client.
-Future versions of Kubernetes might not implement that unofficial timezone mechanism at all.
--->
-Kubernetes {{< skew currentVersion >}} 中 CronJob API 的实现允许你设置
-`.spec.schedule` 字段以包含时区；例如：`CRON_TZ=UTC * * * * *` 或 `TZ=UTC * * * * *`。
-
-以这种方式指定时区是**未正式支持**（而且从来没有）。
-
-如果你尝试设置包含 `TZ` 或 `CRON_TZ` 时区规范的排期表，
-Kubernetes 会向客户端报告[警告](/zh-cn/blog/2020/09/03/warnings/)。
-Kubernetes 的未来版本可能根本不会实现这种非正式的时区机制。
-{{< /caution >}}
+你可以通过将 `.spec.timeZone`
+设置为一个有效[时区](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)的名称，
+为 CronJob 指定一个时区。例如设置 `.spec.timeZone: "Etc/UTC"` 将告诉
+Kubernetes 基于世界标准时间解读排期表。
 
 <!--
 A time zone database from the Go standard library is included in the binaries and used as a fallback in case an external database is not available on the system.
@@ -376,16 +349,44 @@ Go 标准库中的时区数据库包含在二进制文件中，并用作备用
 <!--
 ## CronJob limitations {#cron-job-limitations}
 
+### Unsupported TimeZone specification
+-->
+## CronJob 的限制    {#cronjob-limitations}
+
+### 不支持的时区规范   {#unsupported-timezone-spec}
+
+<!--
+The implementation of the CronJob API in Kubernetes {{< skew currentVersion >}} lets you set
+the `.spec.schedule` field to include a timezone; for example: `CRON_TZ=UTC * * * * *`
+or `TZ=UTC * * * * *`.
+-->
+Kubernetes {{< skew currentVersion >}} 中的 CronJob API 实现允许你设置
+`.spec.schedule` 字段，在其中包括时区信息；
+例如 `CRON_TZ=UTC * * * * *` 或 `TZ=UTC * * * * *`。
+
+<!--
+Specifying a timezone that way is **not officially supported** (and never has been).
+
+If you try to set a schedule that includes `TZ` or `CRON_TZ` timezone specification,
+Kubernetes reports a [warning](/blog/2020/09/03/warnings/) to the client.
+Future versions of Kubernetes will prevent setting the unofficial timezone mechanism entirely.
+-->
+以这种方式指定时区是 **未正式支持的**（而且也从未正式支持过）。
+
+如果你尝试设置包含 `TZ` 或 `CRON_TZ` 时区规范的排期表，
+Kubernetes 会向客户端报告一条[警告](/blog/2020/09/03/warnings/)。
+后续的 Kubernetes 版本将完全阻止设置非正式的时区机制。
+
+<!--
 ### Modifying a CronJob
+
 By design, a CronJob contains a template for _new_ Jobs.
 If you modify an existing CronJob, the changes you make will apply to new Jobs that
 start to run after your modification is complete. Jobs (and their Pods) that have already
 started continue to run without changes.
 That is, the CronJob does _not_ update existing Jobs, even if those remain running.
 -->
-## CronJob 限制    {#cronjob-limitations}
-
-### 修改 CronJob  {#modifying-a-cronjob}
+### 修改 CronJob   {#modifying-a-cronjob}
 
 按照设计，CronJob 包含一个用于**新** Job 的模板。
 如果你修改现有的 CronJob，你所做的更改将应用于修改完成后开始运行的新任务。
@@ -491,7 +492,8 @@ CronJob 仅负责创建与其调度时间相匹配的 Job，而 Job 又负责管
   Read the {{< api-reference page="workload-resources/cron-job-v1" >}}
   API reference for more details.
 -->
-* 了解 CronJob 所依赖的 [Pod](/zh-cn/docs/concepts/workloads/pods/) 与 [Job](/zh-cn/docs/concepts/workloads/controllers/job/) 的概念。
+* 了解 CronJob 所依赖的 [Pod](/zh-cn/docs/concepts/workloads/pods/) 与
+  [Job](/zh-cn/docs/concepts/workloads/controllers/job/) 的概念。
 * 阅读 CronJob `.spec.schedule` 字段的详细[格式](https://pkg.go.dev/github.com/robfig/cron/v3#hdr-CRON_Expression_Format)。
 * 有关创建和使用 CronJob 的说明及 CronJob 清单的示例，
   请参见[使用 CronJob 运行自动化任务](/zh-cn/docs/tasks/job/automated-tasks-with-cron-jobs/)。

From 0162b83b5af9c32f7a0dcee91a2cbd6e15417b7b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E6=9C=B1=E6=AD=A3=E6=B5=A9=2CZhu=20Zhenghao?=
 <zhenghao.zhu@daocloud.io>
Date: Wed, 12 Apr 2023 22:19:35 +0800
Subject: [PATCH 202/272] [zh] sync 1.27 virtual-ips

---
 .../docs/reference/networking/virtual-ips.md  | 169 ++++++++++++------
 1 file changed, 112 insertions(+), 57 deletions(-)

diff --git a/content/zh-cn/docs/reference/networking/virtual-ips.md b/content/zh-cn/docs/reference/networking/virtual-ips.md
index 6a3b47c44fe..14d8ddf2e6e 100644
--- a/content/zh-cn/docs/reference/networking/virtual-ips.md
+++ b/content/zh-cn/docs/reference/networking/virtual-ips.md
@@ -252,6 +252,44 @@ iptables:
 ...
 ```
 
+<!--
+##### Performance optimization for `iptables` mode {#minimize-iptables-restore}
+-->
+##### 对 `iptables` 模式的性能优化 {#minimize-iptables-restore}
+
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
+
+<!--
+In Kubernetes {{< skew currentVersion >}} the kube-proxy defaults to a minimal approach
+to `iptables-restore` operations, only making updates where Services or EndpointSlices have
+actually changed. This is a performance optimization.
+The original implementation updated all the rules for all Services on every sync; this
+sometimes led to performance issues (update lag) in large clusters.
+-->
+在 Kubernetes {{< skew currentVersion >}} 中，kube-proxy 默认采用最小方式进行 `iptables-restore` 操作，
+仅在 Service 或 EndpointSlice 实际发生变化的地方进行更新。这是一个性能优化。
+最初的实现在每次同步时都会更新所有服务的所有规则；这有时会导致大型集群出现性能问题（更新延迟）。
+
+<!--
+If you are not running kube-proxy from Kubernetes {{< skew currentVersion >}}, check
+the behavior and associated advice for the version that you are actually running.
+-->
+如果你运行的不是 Kubernetes {{< skew currentVersion >}} 版本的 kube-proxy，
+请检查你实际运行的版本的行为和相关建议。
+
+<!--
+If you were previously overriding `minSyncPeriod`, you should try
+removing that override and letting kube-proxy use the default value
+(`1s`) or at least a smaller value than you were using before upgrading.
+You can select the legacy behavior by disabling the `MinimizeIPTablesRestore`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+(you should not need to).
+-->
+如果你之前覆盖了 `minSyncPeriod`，你应该尝试删除该覆盖并让 kube-proxy 使用默认值（`1s`）或至少比升级前使用的值小。
+你可以通过禁用 `MinimizeIPTablesRestore`
+[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)来选择执行旧的行为
+（你应该不需要）。
+
 ##### `minSyncPeriod`
 
 <!--
@@ -264,7 +302,7 @@ things change in a small time period. For example, if you have a
 Service backed by a {{< glossary_tooltip term_id="deployment" text="Deployment" >}}
 with 100 pods, and you delete the
 Deployment, then with `minSyncPeriod: 0s`, kube-proxy would end up
-removing the Service's Endpoints from the iptables rules one by one,
+removing the Service's endpoints from the iptables rules one by one,
 for a total of 100 updates. With a larger `minSyncPeriod`, multiple
 Pod deletion events would get aggregated
 together, so kube-proxy might
@@ -287,21 +325,20 @@ The larger the value of `minSyncPeriod`, the more work that can be
 aggregated, but the downside is that each individual change may end up
 waiting up to the full `minSyncPeriod` before being processed, meaning
 that the iptables rules spend more time being out-of-sync with the
-current apiserver state.
+current API server state.
 -->
 `minSyncPeriod` 的值越大，可以聚合的工作越多，
 但缺点是每个独立的变更可能最终要等待整个 `minSyncPeriod` 周期后才能被处理，
-这意味着 iptables 规则要用更多时间才能与当前的 apiserver 状态同步。
+这意味着 iptables 规则要用更多时间才能与当前的 API 服务器状态同步。
 
 <!--
-The default value of `1s` is a good compromise for small and medium
-clusters. In large clusters, it may be necessary to set it to a larger
-value. (Especially, if kube-proxy's
-`sync_proxy_rules_duration_seconds` metric indicates an average
-time much larger than 1 second, then bumping up `minSyncPeriod` may
-make updates more efficient.)
+The default value of `1s` should work well in most clusters, but in very
+large clusters it may be necessary to set it to a larger value.
+Especially, if kube-proxy's `sync_proxy_rules_duration_seconds` metric
+indicates an average time much larger than 1 second, then bumping up
+`minSyncPeriod` may make updates more efficient.
 -->
-默认值 `1s` 对于中小型集群是一个很好的折衷方案。
+默认值 `1s` 适用于大多数集群，
 在大型集群中，可能需要将其设置为更大的值。
 （特别是，如果 kube-proxy 的 `sync_proxy_rules_duration_seconds` 指标表明平均时间远大于 1 秒，
 那么提高 `minSyncPeriod` 可能会使更新更有效率。）
@@ -311,13 +348,13 @@ make updates more efficient.)
 <!--
 The `syncPeriod` parameter controls a handful of synchronization
 operations that are not directly related to changes in individual
-Services and Endpoints. In particular, it controls how quickly
+Services and EndpointSlices. In particular, it controls how quickly
 kube-proxy notices if an external component has interfered with
 kube-proxy's iptables rules. In large clusters, kube-proxy also only
 performs certain cleanup operations once every `syncPeriod` to avoid
 unnecessary work.
 -->
-`syncPeriod` 参数控制与单次 Service 和 Endpoint 的变更没有直接关系的少数同步操作。
+`syncPeriod` 参数控制与单次 Service 和 EndpointSlice 的变更没有直接关系的少数同步操作。
 特别是，它控制 kube-proxy 在外部组件已干涉 kube-proxy 的 iptables 规则时通知的速度。
 在大型集群中，kube-proxy 也仅在每隔 `syncPeriod` 时长执行某些清理操作，以避免不必要的工作。
 
@@ -331,47 +368,6 @@ and is likely to hurt functionality more than it improves performance.
 但在过去，有时将其设置为非常大的值（例如 `1h`）很有用。
 现在不再推荐这种做法，因为它对功能的破坏可能会超过对性能的改进。
 
-<!--
-##### Experimental performance improvements {#minimize-iptables-restore}
--->
-##### 实验性的性能改进 {#minimize-iptables-restore}
-
-{{< feature-state for_k8s_version="v1.26" state="alpha" >}}
-
-<!--
-In Kubernetes 1.26, some new performance improvements were made to the
-iptables proxy mode, but they are not enabled by default (and should
-probably not be enabled in production clusters yet). To try them out,
-enable the `MinimizeIPTablesRestore` [feature
-gate](/docs/reference/command-line-tools-reference/feature-gates/) for
-kube-proxy with `--feature-gates=MinimizeIPTablesRestore=true,…`.
--->
-在 Kubernetes 1.26 中，社区对 iptables 代理模式进行了一些新的性能改进，
-但默认未启用（并且可能还不应该在生产集群中启用）。要试用它们，
-请使用 `--feature-gates=MinimizeIPTablesRestore=true,…` 为 kube-proxy 启用 `MinimizeIPTablesRestore`
-[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)。
-
-<!--
-If you enable that feature gate and
-you were previously overriding
-`minSyncPeriod`, you should try removing that override and letting
-kube-proxy use the default value (`1s`) or at least a smaller value
-than you were using before.
--->
-如果你启用该特性门控并且之前覆盖了 `minSyncPeriod`，
-你应该尝试移除该覆盖并让 kube-proxy 使用默认值 (`1s`) 或至少使用比之前更小的值。
-
-<!--
-If you notice kube-proxy's
-`sync_proxy_rules_iptables_restore_failures_total` or
-`sync_proxy_rules_iptables_partial_restore_failures_total` metrics
-increasing after enabling this feature, that likely indicates you are
-encountering bugs in the feature and you should file a bug report.
--->
-如果你注意到 kube-proxy 的 `sync_proxy_rules_iptables_restore_failures_total` 或
-`sync_proxy_rules_iptables_partial_restore_failures_total` 指标在启用此特性后升高，
-这可能表明你发现了该特性的错误，你应该提交错误报告。
-
 <!--
 ### IPVS proxy mode {#proxy-mode-ipvs}
 -->
@@ -521,31 +517,35 @@ populated in terms of the Service's virtual IP address (and port).
 One of the primary philosophies of Kubernetes is that you should not be
 exposed to situations that could cause your actions to fail through no fault
 of your own. For the design of the Service resource, this means not making
-you choose your own port number if that choice might collide with
+you choose your own IP address if that choice might collide with
 someone else's choice.  That is an isolation failure.
 -->
 Kubernetes 的主要哲学之一是，
 你不应需要在完全不是你的问题的情况下面对可能导致你的操作失败的情形。
 对于 Service 资源的设计，也就是如果你选择的端口号可能与其他人的选择冲突，
-就不应该让你自己选择端口号。这是一种失败隔离。
+就不应该让你自己选择 IP 地址。这是一种失败隔离。
 
 <!--
-In order to allow you to choose a port number for your Services, we must
+In order to allow you to choose an IP address for your Services, we must
 ensure that no two Services can collide. Kubernetes does that by allocating each
 Service its own IP address from within the `service-cluster-ip-range`
 CIDR range that is configured for the {{< glossary_tooltip term_id="kube-apiserver" text="API Server" >}}.
 -->
-为了允许你为 Service 选择端口号，我们必须确保没有任何两个 Service 会发生冲突。
+为了允许你为 Service 选择 IP 地址，我们必须确保没有任何两个 Service 会发生冲突。
 Kubernetes 通过从为 {{< glossary_tooltip text="API 服务器" term_id="kube-apiserver" >}}
 配置的 `service-cluster-ip-range` CIDR 范围内为每个 Service 分配自己的 IP 地址来实现这一点。
 
 <!--
+#### IP address allocation tracking
+
 To ensure each Service receives a unique IP, an internal allocator atomically
 updates a global allocation map in {{< glossary_tooltip term_id="etcd" >}}
 prior to creating each Service. The map object must exist in the registry for
 Services to get IP address assignments, otherwise creations will
 fail with a message indicating an IP address could not be allocated.
 -->
+#### IP 地址分配追踪
+
 为了确保每个 Service 都获得唯一的 IP，内部分配器在创建每个 Service
 之前更新 {{< glossary_tooltip term_id="etcd" >}} 中的全局分配映射，这种更新操作具有原子性。
 映射对象必须存在于数据库中，这样 Service 才能获得 IP 地址分配，
@@ -562,6 +562,61 @@ IP addresses that are no longer used by any Services.
 Kubernetes 还使用控制器来检查无效的分配（例如，因管理员干预而导致无效分配）
 以及清理已分配但没有 Service 使用的 IP 地址。
 
+{{< feature-state for_k8s_version="v1.27" state="alpha" >}}
+<!--
+If you enable the `MultiCIDRServiceAllocator`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) and the
+[`networking.k8s.io/v1alpha1` API group](/docs/tasks/administer-cluster/enable-disable-api/),
+the control plane replaces the existing etcd allocator with a new one, using IPAddress
+objects instead of an internal global allocation map.  The ClusterIP address
+associated to each Service will have a referenced IPAddress object.
+-->
+如果你启用 `MultiCIDRServiceAllocator` [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gate/)
+和 [`networking.k8s.io/v1alpha1` API 组](/zh-cn/docs/tasks/administer-cluster/enable-disable-api/)，
+控制平面将用一个新的分配器替换现有的 etcd 分配器，使用 IPAddress 对象而不是内部的全局分配映射。
+与每个 Service 关联的 ClusterIP 地址将有一个对应的 IPAddress 对象。
+
+<!--
+The background controller is also replaced by a new one to handle the new IPAddress
+objects and the migration from the old allocator model.
+-->
+后台控制器也被一个新的控制器取代，来处理新的 IPAddress 对象和从旧的分配器模型的迁移。
+
+<!--
+One of the main benefits of the new allocator is that it removes the size limitations
+for the `service-cluster-ip-range`, there is no limitations for IPv4 and for IPv6
+users can use masks equal or larger than /64 (previously it was /108).
+-->
+新分配器的主要好处之一是它取消了对 `service-cluster-ip-range` 的大小限制，对 IPv4 没有大小限制，
+对于 IPv6 用户可以使用等于或大于 /64 的掩码（以前是 /108）。
+
+<!--
+Users now will be able to inspect the IP addresses assigned to their Services, and
+Kubernetes extensions such as the [Gateway](https://gateway-api.sigs.k8s.io/) API, can use this new
+IPAddress object kind to enhance the Kubernetes networking capabilities, going beyond the limitations of
+the built-in Service API.
+-->
+用户现在能够检查分配给他们的 Service 的 IP 地址，Kubernetes 扩展，
+如 [Gateway](https://gateway-api.sigs.k8s.io/) API
+可以使用这个新的 IPAddress 对象类别来增强 Kubernetes 的网络能力，解除内置 Service API 的限制。
+
+```shell
+kubectl get services
+```
+```
+NAME         TYPE        CLUSTER-IP        EXTERNAL-IP   PORT(S)   AGE
+kubernetes   ClusterIP   2001:db8:1:2::1   <none>        443/TCP   3d1h
+```
+
+```shell
+kubectl get ipaddresses
+```
+```
+NAME              PARENTREF
+2001:db8:1:2::1   services/default/kubernetes
+2001:db8:1:2::a   services/kube-system/kube-dns
+```
+
 <!--
 #### IP address ranges for Service virtual IP addresses {#service-ip-static-sub-range}
 -->

From f86e6e3f8357d22ca1c5715724310c21ce26a297 Mon Sep 17 00:00:00 2001
From: Guangwen Feng <fenggw-fnst@fujitsu.com>
Date: Fri, 14 Apr 2023 17:37:42 +0800
Subject: [PATCH 203/272] [zh-cn] Sync statefulset.md

Signed-off-by: Guangwen Feng <fenggw-fnst@fujitsu.com>
---
 .../zh-cn/docs/concepts/workloads/controllers/statefulset.md  | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/zh-cn/docs/concepts/workloads/controllers/statefulset.md b/content/zh-cn/docs/concepts/workloads/controllers/statefulset.md
index 136837d9504..3973d78160d 100644
--- a/content/zh-cn/docs/concepts/workloads/controllers/statefulset.md
+++ b/content/zh-cn/docs/concepts/workloads/controllers/statefulset.md
@@ -258,7 +258,7 @@ pods will be assigned ordinals from 0 up through N-1.
 -->
 ### 起始序号   {#start-ordinal}
 
-{{< feature-state for_k8s_version="v1.26" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
 
 <!--
 `.spec.ordinals` is an optional field that allows you to configure the integer
@@ -648,7 +648,7 @@ StatefulSet 才会开始使用被还原的模板来重新创建 Pod。
 -->
 ## PersistentVolumeClaim 保留  {#persistentvolumeclaim-retention}
 
-{{< feature-state for_k8s_version="v1.23" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
 
 <!--
 The optional `.spec.persistentVolumeClaimRetentionPolicy` field controls if

From d8c3dc822f6926c11a3b41cd93d114236ba725ca Mon Sep 17 00:00:00 2001
From: AmarNathChary <naduminti.amarnath@india.nec.com>
Date: Fri, 14 Apr 2023 10:23:48 +0530
Subject: [PATCH 204/272] Fixed Broken link in Feature gates

---
 .../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 8441f0bc186..56fb28b56b0 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
@@ -528,7 +528,7 @@ Each feature gate is designed for enabling/disabling a specific feature:
   that is independent of a Pod.
 - `ElasticIndexedJob`: Enables Indexed Jobs to be scaled up or down by mutating both
   `spec.completions` and `spec.parallelism` together such that `spec.completions == spec.parallelism`.
-  See docs on [elastic Indexed Jobs](docs/concepts/workloads/controllers/job#elastic-indexed-jobs)
+  See docs on [elastic Indexed Jobs](/docs/concepts/workloads/controllers/job#elastic-indexed-jobs)
   for more details.
 - `EndpointSliceTerminatingCondition`: Enables EndpointSlice `terminating` and `serving`
    condition fields.

From 357e5a62f0f88f524933f3ff7966dac30fc590b7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20=C5=A0afr=C3=A1nek?= <jsafrane@redhat.com>
Date: Fri, 14 Apr 2023 15:49:42 +0200
Subject: [PATCH 205/272] Update
 content/en/blog/_posts/2023-04-18-efficient-selinux-relabeling-beta.md

Co-authored-by: Tim Bannister <tim@scalefactory.com>
---
 .../blog/_posts/2023-04-18-efficient-selinux-relabeling-beta.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/blog/_posts/2023-04-18-efficient-selinux-relabeling-beta.md b/content/en/blog/_posts/2023-04-18-efficient-selinux-relabeling-beta.md
index d9a3a880640..c9f437a4806 100644
--- a/content/en/blog/_posts/2023-04-18-efficient-selinux-relabeling-beta.md
+++ b/content/en/blog/_posts/2023-04-18-efficient-selinux-relabeling-beta.md
@@ -11,7 +11,7 @@ slug: kubernetes-1-27-efficient-selinux-relabeling-beta
 
 On Linux with Security-Enhanced Linux (SELinux) enabled, it's traditionally
 the container runtime that applies SELinux labels to a Pod and all its volumes.
-Kubernetes only provides the SELinux label from Pod's Security Context fields
+Kubernetes only passes the SELinux label from a Pod's `securityContext` fields
 to the container runtime.
 
 The container runtime then recursively changes SELinux label on all files that

From be8c17c533a7afdacd899355bec1ad87feb6ff7c Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Fri, 14 Apr 2023 23:21:08 +0800
Subject: [PATCH 206/272] sync 1.27 version-skew-policy.md

sync 1.27 version-skew-policy.md
---
 content/zh-cn/releases/version-skew-policy.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/content/zh-cn/releases/version-skew-policy.md b/content/zh-cn/releases/version-skew-policy.md
index 1c9d2b5b80a..8cbe75c9e29 100644
--- a/content/zh-cn/releases/version-skew-policy.md
+++ b/content/zh-cn/releases/version-skew-policy.md
@@ -368,7 +368,6 @@ Running a cluster with `kubelet` instances that are persistently two minor versi
 <!-- 
 ### kube-proxy
 
-* `kube-proxy` must be the same minor version as `kubelet` on the node.
 * `kube-proxy` must not be newer than `kube-apiserver`.
 * `kube-proxy` must be at most two minor versions older than `kube-apiserver.`
 
@@ -381,7 +380,6 @@ If `kube-proxy` version is **{{< skew currentVersionAddMinor -2 >}}**:
 -->
 ### kube-proxy  {#kube-proxy}
 
-* `kube-proxy` 和节点上的 `kubelet` 必须是相同的次要版本。
 * `kube-proxy` 版本不能比 `kube-apiserver` 版本新。
 * `kube-proxy` 最多只能比 `kube-apiserver` 落后两个次要版本。
 

From 215bceeec49de00cc86c5cfc579c8ba9aeea1186 Mon Sep 17 00:00:00 2001
From: Dipesh Rawat <rawat.dipesh@gmail.com>
Date: Fri, 14 Apr 2023 17:48:44 +0100
Subject: [PATCH 207/272] Adds banner for KubeCon CloudNativeCon EU 2023

---
 data/announcements/scheduled.yaml                   | 13 +++++++++++++
 static/images/announcements/kccnc-eu-2023-white.svg |  1 +
 2 files changed, 14 insertions(+)
 create mode 100644 static/images/announcements/kccnc-eu-2023-white.svg

diff --git a/data/announcements/scheduled.yaml b/data/announcements/scheduled.yaml
index 79e6e2e5b0c..830f5577acb 100644
--- a/data/announcements/scheduled.yaml
+++ b/data/announcements/scheduled.yaml
@@ -152,6 +152,19 @@ announcements:
     All images available in k8s.gcr.io are available at registry.k8s.io.</br>
     Please read our [announcement](/blog/2023/03/10/image-registry-redirect/) for more details.
 
+- name: Kubecon 2023 EU
+  startTime: 2023-04-15T00:00:00  #Added in https://github.com/kubernetes/website/pull/40691
+  endTime: 2023-04-22T18:00:00
+  style: >-
+    background: linear-gradient(90deg, rgba(174,28,40,1) 0%, rgba(50,79,133,1) 65%, rgba(33,70,139,1) 100%);
+    color: #fffff;
+  title: |
+    <img src ="/images/announcements/kccnc-eu-2023-white.svg" style="float: right; height: 80px;" />
+    <a href= "https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/">KubeCon + CloudNativeCon EU 2023</a> <em> Amsterdam, Netherlands + Virtual</em>.
+  message: |
+    4 days of incredible opportunities to collaborate, learn + share with the entire community!<br />
+    April 18 - April 21, 2023.
+    
 - name: Redirecting k8s.gcr.io - After
   startTime: 2023-03-27T00:00:00 # This should run after the redirect begins
   endTime: 2023-05-31T00:00:00
diff --git a/static/images/announcements/kccnc-eu-2023-white.svg b/static/images/announcements/kccnc-eu-2023-white.svg
new file mode 100644
index 00000000000..69c664329bc
--- /dev/null
+++ b/static/images/announcements/kccnc-eu-2023-white.svg
@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" role="img" viewBox="3.38 -1.12 630.24 280.24"><title>kccnc-eu-2023-logos-white.svg</title><defs><clipPath id="c"><path d="M238.203 11.813H239.203V215.313H238.203z" class="f"/></clipPath><clipPath id="d"><path d="M15.63 251.001H189.603V252.001H15.63z" class="f"/></clipPath><clipPath id="e"><path d="M447.545 251.001H621.518V252.001H447.545z" class="f"/></clipPath><style>.f,.g{fill:#fff}.g{fill-rule:evenodd}</style></defs><g><path d="M177.20279,185.71296c1.10001-.3,2.39999-.60001,4.10001-.89999,1.71819-.28603,3.45827-.41988,5.2-.39999,1.56427-.06822,3.12683,.16956,4.60001,.7,1.1317,.43799,2.13077,1.16145,2.89999,2.10001,.73483,.93996,1.24762,2.03389,1.5,3.2,.32605,1.34248,.49387,2.71851,.5,4.10001v12.39999h-6.10001v-11.7c.10239-1.44571-.17332-2.89316-.8-4.2-.50002-.8-1.50002-1.20001-3-1.2-.46883-.01309-.93779,.02042-1.39999,.10001-.5,0-.89999,.10001-1.3,.10001v16.89999h-6.2v-21.20003Zm-11.39999,10.10001c.06738-1.57396-.31412-3.13463-1.10001-4.5-1.43765-1.82254-4.08057-2.13455-5.90311-.6969-.25882,.20416-.49274,.43806-.6969,.6969-.86681,1.33492-1.28702,2.91074-1.2,4.5-.07166,1.61911,.34656,3.22221,1.2,4.60001,1.29948,1.82254,3.8304,2.24655,5.65294,.94707,.36603-.26099,.68608-.58104,.94707-.94707,.78513-1.40205,1.16592-2.99443,1.10001-4.60001m6.3,0c.03511,1.59505-.2016,3.18442-.7,4.7-.47517,1.3696-1.22363,2.6284-2.2,3.7-2.00189,2.16328-4.85562,3.33405-7.8,3.2-1.50322,.00429-2.99449-.26685-4.39999-.8-1.28856-.55368-2.44678-1.37125-3.39999-2.39999-.98329-1.06645-1.73267-2.32677-2.2-3.7-1.06668-3.04254-1.06668-6.35745,0-9.39999,.49159-1.33197,1.23895-2.55493,2.2-3.60001,.95738-.99913,2.11636-1.78314,3.39999-2.3,1.35948-.57161,2.82591-.84442,4.3-.8,1.47075-.00461,2.92932,.26675,4.3,.8,1.26381,.55345,2.41602,1.33289,3.39999,2.3,.96106,1.04507,1.70842,2.26804,2.2,3.60001,.61427,1.48982,.92043,3.08864,.89999,4.7m-33.7,11.60001c-4.7,0-8.3-1.3-10.7-3.89999-2.5-2.60001-3.7-6.3-3.7-11.10001-.01868-2.18192,.35388-4.34952,1.10001-6.39999,1.35368-3.55853,4.2075-6.33919,7.8-7.60001,1.88783-.69559,3.8884-1.03467,5.89999-1,1.10718-.00862,2.21252,.09187,3.3,.3,1,.2,1.89999,.39999,2.60001,.60001,.64493,.20058,1.2791,.43422,1.89999,.7,.39909,.13379,.77145,.3369,1.10001,.60001l-1.89999,5.2c-.97542-.536-2.01793-.93954-3.10001-1.2-1.30731-.33257-2.65105-.50053-4-.5-.98709,.01154-1.96603,.18033-2.89999,.5-.95451,.31487-1.8143,.86513-2.5,1.60001-.75763,.82205-1.36668,1.76947-1.8,2.8-.45958,1.35277-.696,2.7713-.7,4.2-.02635,1.24541,.10809,2.489,.39999,3.7,.28201,1.07622,.7563,2.09258,1.39999,3,.70915,.84964,1.59689,1.5325,2.60001,2,1.20009,.5089,2.49734,.74786,3.8,.7,.83696-.00877,1.67229-.07559,2.5-.2,.67847-.0654,1.34856-.19942,2-.39999,.50963-.13628,1.01054-.30324,1.5-.5,.3811-.20882,.78337-.37643,1.2-.5l1.8,5.2c-1.20401,.72067-2.52338,1.22813-3.89999,1.5-1.85452,.51599-3.77574,.75192-5.7,.7m-24.7-13.7c-.00288-.51462-.10474-1.02386-.3-1.5-.17257-.46341-.40811-.90085-.7-1.3-.33042-.40894-.73819-.74873-1.2-1-.56833-.24898-1.17972-.38484-1.8-.39999-.62529-.03374-1.24786,.1046-1.8,.39999-.47619,.18207-.89188,.49384-1.2,.89999-.3457,.41684-.61639,.89053-.8,1.39999-.19182,.51698-.32597,1.05357-.4,1.60001h8.2v-.09999Zm-14.49999,2.3c-.02849-1.74188,.27702-3.47308,.9-5.10001,.51175-1.36899,1.33315-2.60109,2.4-3.60001,.94285-.94537,2.06472-1.69328,3.3-2.2,1.24523-.47357,2.5678-.71095,3.9-.7,2.75203-.15768,5.44168,.86003,7.4,2.8,1.8,1.90001,2.7,4.7,2.7,8.39999v1.2c0,.39999-.10001,.8-.10001,1.10001h-14.1c.0625,1.2375,.7375,2.3625,1.8,3,1.26546,.76204,2.72346,1.14391,4.2,1.10001,1.10699,.00395,2.21188-.0965,3.3-.3,.92718-.16447,1.83288-.43283,2.7-.8l.8,5c-.41965,.20026-.85432,.36743-1.3,.5-.6198,.19106-1.25578,.32495-1.9,.39999-.7,.10001-1.4,.2-2.2,.3-.76385,.0811-1.53201,.1145-2.3,.10001-1.7433,.04704-3.4781-.25909-5.1-.89999-1.36899-.51175-2.60108-1.33315-3.6-2.39999-.99915-.9985-1.72265-2.23878-2.1-3.60001-.50723-1.37511-.7449-2.83502-.7-4.3m-4.1-.10001c.00336,1.60083-.26722,3.19043-.8,4.7-.49158,1.33197-1.23895,2.55493-2.2,3.60001-1.01358,1.02539-2.24358,1.81123-3.6,2.3-1.54202,.54099-3.16588,.81163-4.8,.8-.80125,.01263-1.60258-.02075-2.4-.10001l-2.4-.3c-.77434-.08467-1.54254-.21826-2.3-.39999-.7-.2-1.4-.3-1.9-.5v-30.60001l6.2-1v10.89999c.71306-.29282,1.44884-.52693,2.2-.7,.78802-.16989,1.59473-.23712,2.4-.2,1.40688-.01532,2.80207,.25691,4.1,.8,1.17862,.50027,2.21088,1.29167,3,2.3,.83425,1.06784,1.44628,2.2919,1.8,3.60001,.49825,1.55003,.73482,3.17223,.7,4.8m-6.3-.2c0-4-1.5-6-4.4-6-.63757,.01712-1.27283,.08398-1.9,.2-.5133,.16501-1.0145,.36549-1.5,.60001v11.3c.39294,.09192,.79726,.12561,1.2,.10001,.5,0,1,.10001,1.5,.10001,1.46991,.09691,2.89259-.53955,3.8-1.7,.90139-1.36073,1.35583-2.96877,1.3-4.60001m-20.2,10.39999c-1.1,.3-2.4,.60001-4.1,.89999-1.71819,.28603-3.45827,.41988-5.2,.39999-1.56428,.06822-3.12682-.16956-4.6-.7-1.1317-.43799-2.13077-1.16145-2.9-2.10001-.71632-.95122-1.22712-2.04092-1.5-3.2-.33225-1.34135-.50015-2.71812-.5-4.10001v-12.2h6.1v11.39999c-.08781,1.47711,.18683,2.95331,.8,4.3,.5,.89999,1.5,1.3,3,1.3,.46883,.01309,.9378-.0204,1.4-.10001,.5,0,.9-.10001,1.3-.10001v-16.89999h6.2v21.10002Zm-28.60001,.7c-.6-.89999-1.3-2-2.1-3.10001-.80426-1.14777-1.67229-2.2495-2.6-3.3-.9-1.10001-1.9-2.10001-2.9-3.2-.94948-.95459-1.95101-1.85597-3-2.7v12.2h-6.50005v-28.8h6.5v10.89999c1.7-1.8,3.4-3.60001,5.1-5.60001,1.7-1.89999,3.3-3.7,4.8-5.3h7.7c-2,2.3-3.9,4.60001-5.9,6.7-2,2.2-4.1,4.3-6.3,6.5,2.42954,2.06461,4.67162,4.34015,6.7,6.8,2.23989,2.77257,4.31032,5.67786,6.2,8.7h-7.7l.00005,.20003Z" class="f"/><path d="M92.00278,79.61296l-3.6,.8c0-.5-.1-1-.1-1.5-.01186-3.80733,1.02616-7.54425,3-10.8l7,6.2c.11396,.12351,.24952,.22518,.4,.3-.42986,1.05391-.69952,2.16624-.8,3.3-.2,.1-.5,.1-.7,.2l-5.2,1.5Zm13.6-21.2v9.8c-.97546,.30392-1.88953,.77789-2.7,1.4-.3-.2-.6-.5-.9-.7l-7.1-5c2.90701-2.90269,6.64767-4.82546,10.7-5.5m-48.7,22.6c3.4-14.9,6.3-27.5,9.7-42.4,1.5-6.7,2.5-8.5,8.6-12,8.4-4.9,14.7-8.4,23.7-13.6,5.6-3.2,6.7-3,6.7,3.9V51.51296c-6.2683,.76625-12.07056,3.70276-16.4,8.3l-3-2.1c-.36954-.21362-.62577-.57966-.7-1-.27878-.9432-.83658-1.7799-1.6-2.4-1.40941-1.13084-3.46868-.90501-4.59952,.5044-1.12931,1.4075-.90582,3.4636,.49952,4.5956,.45412,.40212,1.00584,.67798,1.6,.8,.4,.1,.8,.1,1.2,.2,.32381,.07158,.62988,.20762,.9,.4l2.8,2.5c-3.07482,4.54621-4.71232,9.91161-4.7,15.4,0,1,.1,2,.2,3l-6.1,1.3c-.43565-.01282-.87144,.02071-1.3,.1l-.9,.3c-4,.8-8,1.7-12.1,2.6-5.5,1.3-5.7,.2-4.5-5m55.8-12.8v-9.8c4.01499,.7239,7.7327,2.60013,10.7,5.4l-7.7,5.5c-.1,.1-.2,.2-.3,.2-.83718-.55325-1.74543-.99055-2.7-1.3m17.2,11.5l-9.60001-2.2c-.09978-1.03721-.37009-2.05083-.8-3,.10001-.1,.2-.2,.3-.2l7.10001-6.3c2.01772,3.27839,3.09052,7.05047,3.10001,10.9-.08871,.25678-.12279,.52928-.10001,.8m-12.5-52.9c5.2,2.5,8.89999,4.3,14.10001,6.8,7.2,3.5,14.39999,7,21.7,10.4,1.8,7.8,3.60001,15.6,5.3,23.4,1.10001,4.7,1.60001,7.2,2.7,11.8,1.7,7.3,1.5,7.9-6,6.2l-18.5-4.2c.08322-.79714,.11662-1.5987,.10001-2.4,.03969-5.53848-1.63715-10.95328-4.8-15.5l2.60001-2.4c.31339-.26517,.69415-.43826,1.10001-.5,.97578-.07436,1.91118-.42081,2.7-1,1.40833-1.13219,1.63219-3.19168,.5-4.6s-3.19168-1.63218-4.60001-.5h0c-.5018,.36876-.91232,.84771-1.2,1.4-.2,.4-.3,.7-.5,1.1-.10648,.32545-.31738,.60666-.60001,.8l-3,2.1c-4.34317-4.57886-10.13839-7.51181-16.4-8.3V30.31296c.1-4.9,.5-5.5,4.8-3.5m-6.4,63c-.62639,.12127-1.26209,.18818-1.9,.2-.60174,.01657-1.2038-.01688-1.8-.1l-.3,.6-4.4,8.1c2.12607,.72104,4.355,1.09252,6.6,1.1,2.27698-.01562,4.53755-.38676,6.7-1.1l-4.4-8c-.20193-.24294-.37011-.51204-.5-.8m7.8-5.3l9.60001,2.2c-1.58047,3.88199-4.29991,7.19411-7.8,9.5l-3.8-9.2c.75029-.76285,1.42046-1.60056,2-2.5m-28.9,2.1l9.6-2.2c.58781,.95158,1.29338,1.82515,2.1,2.6l-.3,.6-3.5,8.6c-3.55924-2.30995-6.31828-5.66271-7.9-9.6m78.60001,16.9c-4.60001,5.7-6.7,8.4-11.3,14.1-5.2,6.5-9.39999,11.8-14.60001,18.3-3.7,4.7-6.39999,4.8-12.5,4.8h-42c-8,0-8.6,0-13.5-6.2-4.9-6.10001-8.7-10.9-13.5-17-3.8-4.8-4.8-6-8.6-10.8-5.9-7.4-6.9-10.1,2.3-12.1l28.4-6.4c2.20708,6.0174,6.40622,11.0987,11.9,14.4l-1.3,3c-.15289,.38452-.43606,.70308-.8,.9-.87854,.46224-1.58114,1.19997-2,2.1-.80305,1.62814-.13417,3.59901,1.49397,4.40205,1.62814,.80305,3.59901,.13418,4.40205-1.49397l.00397-.00809c.27113-.56596,.44039-1.17529,.5-1.8,.01646-.4026-.01714-.80568-.1-1.2-.03096-.34563,.03849-.69286,.2-1l1.6-2.9c3.16407,1.19347,6.51833,1.80334,9.9,1.8,3.42474,.0183,6.82062-.62691,10-1.9l1.60001,2.9c.21838,.35944,.29001,.78916,.2,1.2-.17113,.95206-.03087,1.93394,.39999,2.8,.79758,1.63083,2.76617,2.30633,4.39702,1.50875,1.63083-.79757,2.30632-2.76617,1.50874-4.39701l-.00577-.01174c-.24927-.57632-.62526-1.08904-1.10001-1.5-.30896-.26634-.644-.50086-1-.7-.30327-.17081-.52094-.46104-.60001-.8l-1.3-3.2c5.49193-3.27743,9.66586-8.37104,11.8-14.4l31.3,7.1c6.3,1.7,5.89999,3.9,2.3,8.5" class="g"/><path d="M112.70278,68.21296v-9.8c4.01499,.7239,7.7327,2.60012,10.7,5.4l-7.7,5.5c-.1,.1-.2,.2-.3,.2-.83718-.55325-1.74543-.99055-2.7-1.3m17.2,11.5l-9.60001-2.2c-.09978-1.03721-.37009-2.05083-.8-3,.10001-.1,.2-.2,.3-.2l7.10001-6.3c2.01772,3.27839,3.09052,7.05047,3.10001,10.9-.08871,.25678-.12279,.52928-.10001,.8m-12.5-52.9c5.2,2.5,8.89999,4.3,14.10001,6.8,7.2,3.5,14.39999,7,21.7,10.4,1.8,7.8,3.60001,15.6,5.3,23.4,1.10001,4.7,1.60001,7.2,2.7,11.8,1.7,7.3,1.5,7.9-6,6.2l-18.5-4.2c.08322-.79714,.11662-1.5987,.10001-2.4,.03969-5.53848-1.63715-10.95328-4.8-15.5l2.60001-2.4c.31339-.26517,.69415-.43826,1.10001-.5,.97578-.07436,1.91118-.42081,2.7-1,1.40833-1.13219,1.63219-3.19168,.5-4.6s-3.19168-1.63218-4.60001-.5h0c-.5018,.36876-.91232,.84771-1.2,1.4-.2,.4-.3,.7-.5,1.1-.10648,.32545-.31738,.60666-.60001,.8l-3,2.1c-4.34317-4.57886-10.13839-7.51181-16.4-8.3V30.31296c.1-4.9,.5-5.5,4.8-3.5m1.4,57.7l9.60001,2.2c-1.58047,3.882-4.29991,7.19411-7.8,9.5l-3.8-9.2c.75029-.76285,1.42046-1.60056,2-2.5m-9.7,15.1v-9.6c.63757-.01711,1.27283-.08398,1.9-.2,.09468,.2534,.22976,.48978,.4,.7l4.4,8c-2.16245,.71323-4.42302,1.08437-6.7,1.1m59.4,3.9c-4.60001,5.7-6.7,8.4-11.3,14.1-5.2,6.5-9.39999,11.8-14.60001,18.3-3.7,4.7-6.39999,4.8-12.5,4.8h-20.9v-34.3c3.42474,.0183,6.82062-.62691,10-1.9l1.6,2.9c.21838,.35944,.29001,.78916,.2,1.2-.17114,.95206-.03087,1.93394,.39999,2.8,.80406,1.62765,2.77534,2.2953,4.40298,1.49124,1.62306-.8018,2.29234-2.765,1.49701-4.39124-.24925-.57632-.62524-1.08904-1.10001-1.5-.30898-.26633-.644-.50085-1-.7-.30327-.17081-.52094-.46104-.60001-.8l-1.3-3.2c5.49193-3.27743,9.66586-8.37104,11.8-14.4l31.3,7.1c6.10001,1.7,5.7,3.9,2.10001,8.5" class="g"/><path d="M400.50278,102.31296h-16.60001v38.8h38.70001v-16.6h-22.10001v-22.2Zm83.10001,.1v22.1h-22l-.20001-.2v16.8h38.79999v-38.8h-16.70001l.10004,.10001Zm-99.69998-38.9h16.70001l-.10001-.1v-22.1h22l.10001,.2V24.71296h-38.70001V63.51295Zm77.5-38.8v16.6h22.20001v22.2h16.60001V24.71296h-38.80002Z" class="f"/><g opacity=".8"><path d="M459.40277,63.51295l-22.20001-22.2h24.20001V24.71296h-38.79999v16.8l22.10001,22h14.69998Zm-20,38.8h-14.70001l18.39999,18.4,3.79999,3.8h-24.29999v16.6h38.79999v-16.8l-11-11-10.99997-11Zm44.20001-38.8v24.2l-3.79999-3.8-18.39999-18.3v14.7l11.10001,11,11,11h16.70001V63.51295h-16.60004Zm-61,21.99999l-22-22h-16.79999v38.8h16.70001v-24.19999l22.10001,22.1-.00003-14.70001Z" class="f"/></g><path d="M302.70279 183.41296l-4.20001 5c-1.75729-2.21008-4.38004-3.55788-7.20001-3.7-4.43527.01453-8.01901 3.62181-8.00446 8.05708.00024.08099.00174.16197.00446.24292 0 4.8 3.39999 8.39999 8 8.39999 2.75131-.15198 5.33466-1.37189 7.20001-3.39999l4.29999 4.5c-3.12854 3.1714-7.34836 5.03098-11.79999 5.2-8.60001 0-15-6.3-15-14.7 0-8.3 6.60001-14.5 15.29999-14.5 4.2771.15897 8.34149 1.90594 11.39999 4.89999h.00003zm3.5 24v-30.3h7.10001v30.3h-7.10001zm35.20001-11c0 6.8-4.79999 11.3-12 11.3s-12.10001-4.5-12.10001-11.3 4.79999-11.2 12.10001-11.2c7.19998 0 11.99997 4.39999 11.99997 11.2h.00003zm-17 .10001c0 3.39999 2 5.7 4.89999 5.7s4.89999-2.3 4.89999-5.7-2-5.7-4.89999-5.7-4.90002 2.29999-4.90002 5.7h.00003zm42.29999 10.89999h-7.10001v-3.60001c-1.46921 2.55714-4.25555 4.06641-7.20001 3.89999-4.79999 0-7.89999-3.3-7.89999-8.39999v-13.89999h7.10001v11.89999c0 2.60001 1.39999 4.2 3.70001 4.2 2.70001 0 4.29999-2.2 4.29999-5.2v-10.89999h7.10001v22zm27.79999 0h-7.10001v-2.89999c-1.56879 2.05208-4.01727 3.23923-6.60001 3.2-6.20001 0-10.29999-4.60001-10.29999-11.39999 0-6.7 4-11.2 10.10001-11.2 2.65332-.10828 5.1922 1.0865 6.79999 3.2v-11.2h7.10001v30.29999zm-7.10001-10.89999c0-3.39999-2-5.7-4.89999-5.7s-4.89999 2.3-4.89999 5.7 2 5.8 4.89999 5.8c3-.10001 4.89999-2.40001 4.89999-5.8zM420.40277 207.41296l-13.20001-17.60001v17.60001h-6.79999v-28.60001h6.39999l13.20001 17.7v-17.7h6.79999v28.60001h-6.39999zm31.60001-14.39999v14.39999h-6.89999v-2.5c-1.39999 1.89999-3.79999 2.89999-6.70001 2.89999-4.70001 0-7.60001-2.89999-7.60001-6.89999 0-4.2 3-6.60001 8.5-6.7h5.79999v-.3c0-2.2-1.39999-3.5-4.29999-3.5-2.29999.14201-4.54636.75467-6.60001 1.8l-2-4.7c3.16071-1.6115 6.65234-2.46729 10.20001-2.5 6.10001.09999 9.60001 3.09999 9.60001 8zm-6.89999 7v-2h-4.5c-2.10001 0-3.20001.7-3.20001 2.39999 0 1.60001 1.10001 2.60001 3.10001 2.60001 2.03009.13513 3.90515-1.08774 4.60001-3zm26 6.3c-1.81427.97534-3.84021 1.49042-5.89999 1.5-4.29999 0-7.29999-2.39999-7.29999-7v-9.7h-3.10001v-4.60001h3.10001v-6.10001h7v6.10001h5.79999v4.7h-5.79999v8.60001c0 1.7.70001 2.5 2 2.39999.93311-.07903 1.84604-.3157 2.70001-.7l1.49997 4.8zm10.79999-27.2c.08057 2.01669-1.48898 3.71684-3.50568 3.79741-.06473.00259-.12955.00345-.19434.00259-2.07108-.02748-3.72772-1.72868-3.70026-3.79974.02698-2.03232 1.66794-3.67329 3.70026-3.70026 1.93903-.10443 3.59558 1.38278 3.70001 3.32181.00677.12598.00677.25221 0 .37817v.00002zm-7.29999 28.3v-22h7v22h-7zm18 0l-8.29999-22h7.29999l4.70001 15.60001 4.79999-15.60001h7.00003l-8.29999 22h-7.20004zm38.89999-9.10001h-15.5c.50659 2.44879 2.70062 4.1787 5.20001 4.10001 1.98083-.03886 3.8739-.82466 5.29999-2.2l3.70001 3.60001c-2.48407 2.62906-5.98615 4.05179-9.59998 3.89999-7.20001 0-11.70001-4.5-11.70001-11.2 0-6.8 4.70001-11.3 11.5-11.3 7.70001 0 11.5 5.10001 11.09998 13.10001v-.00002zm-6.79999-3.8c.19543-2.28334-1.49719-4.29277-3.78052-4.48819-.17273-.01479-.34625-.01874-.51947-.01181-2.5 0-4.09998 1.8-4.59998 4.5h8.89996zM560.30276 183.41296l-4.20001 5c-1.75726-2.21008-4.38-3.55788-7.20001-3.7-4.4353.01453-8.01898 3.62181-8.00446 8.05708.00024.08099.00177.16197.00446.24292 0 4.8 3.40002 8.39999 8 8.39999 2.75134-.15198 5.33466-1.37187 7.20001-3.39999l4.29999 4.5c-3.12854 3.1714-7.34833 5.03099-11.79999 5.2-8.59998 0-15-6.3-15-14.7 0-8.3 6.59998-14.5 15.29999-14.5 4.27264.1786 8.33032 1.92268 11.40002 4.89999zm24.70001 13c0 6.8-4.79999 11.3-12 11.3s-12.09998-4.5-12.09998-11.3 4.79999-11.2 12.09998-11.2c7.20001 0 12 4.39999 12 11.2zm-16.90002.10001c0 3.39999 2 5.7 4.90002 5.7s4.90002-2.3 4.90002-5.7-2-5.7-4.90002-5.7-4.89996 2.29999-4.89996 5.7h-.00006zm43.20001-3v13.89999h-7v-11.89999c0-2.60001-1.5-4.2-3.90002-4.2-2.59998 0-4.20001 1.8-4.5 4.5v11.7h-7.09998v-22h7.09998v3.60001c1.5553-2.56879 4.40186-4.06897 7.40002-3.89999 4.79999-.10001 8 3.2 8 8.3v-.00002z" class="f"/><g id="b"><path d="M238.20279,11.81296h1V215.31295h-1V11.81296Z" class="f"/></g><path d="M238.203 11.813H239.203V215.313H238.203z" class="f"/><g><path d="M238.203 11.813H239.203V215.313H238.203z" class="f"/><g clip-path="url(#c)"><path d="M238.20279,11.81296h1V215.31295h-1V11.81296Z" class="f"/></g></g></g><g><path d="M15.63 251.001H189.603V252.001H15.63z" class="f"/><g clip-path="url(#d)"><path d="M15.63,251.00136H189.60279v.99998H15.63v-.99998Z" class="f"/></g></g><g><path d="M213.3335 241.46293v4.90234h12.38037v4.75879h-12.38037v5.40332h13.63281v4.75879h-18.92871v-24.58203h18.92871v4.75879h-13.63281zM248.75732 242.78715v18.49902h-5.22461v-2.25391c-1.14502 1.64551-3.18457 2.68359-5.5459 2.68359-4.04346 0-6.87012-2.93457-6.87012-7.15625v-11.77246h5.00928v10.66309c0 2.29004 1.46729 3.86426 3.54248 3.86426 2.18262 0 3.86426-1.57422 3.86426-3.57812v-10.94922h5.22461zM265.32324 242.35746v4.40137c-3.86475 0-6.3335 2.21875-6.3335 5.68945v8.83789h-5.22412v-18.49902h5.22412v3.4707c1.21631-2.39746 3.50635-3.90039 6.3335-3.90039zM267.86328 252.0186c0-5.33105 4.54395-9.66113 10.09033-9.66113 5.5459 0 10.09033 4.33008 10.09033 9.66113 0 5.33203-4.54443 9.69727-10.09033 9.69727-5.54639 0-10.09033-4.36523-10.09033-9.69727zm15.13574 0c0-2.89844-2.25439-5.25977-5.04541-5.25977s-5.08105 2.36133-5.08105 5.25977 2.29004 5.2959 5.08105 5.2959 5.04541-2.39746 5.04541-5.2959zM311.69531 252.0186c0 5.68945-3.57812 9.69727-8.51611 9.69727-2.6123 0-4.75928-1.14551-6.22607-3.07715v8.80176h-5.22412v-24.65332h5.22412v2.64746c1.4668-1.93164 3.61377-3.07715 6.22607-3.07715 4.93799 0 8.51611 4.00781 8.51611 9.66113zm-5.08105 0c0-3.07715-2.03955-5.25977-4.93799-5.25977-2.75537 0-4.72314 2.18262-4.72314 5.25977 0 3.11328 1.96777 5.2959 4.72314 5.2959 2.89844 0 4.93799-2.18262 4.93799-5.2959zM328.79883 255.8477l2.93359 3.00488c-1.64551 1.71777-4.83008 2.86328-7.5498 2.86328-5.51074 0-9.87598-4.04395-9.87598-9.7334 0-5.58203 4.18652-9.625 9.58984-9.625 5.79688 0 9.30371 4.18652 9.30371 11.05664h-13.91992c.46533 2.50488 2.18262 4.25781 4.72363 4.25781 1.71777 0 3.61426-.75098 4.79492-1.82422zm-9.48242-5.54688h8.87402c-.42969-2.29004-1.89648-3.90039-4.22266-3.90039-2.32568 0-4.0791 1.53906-4.65137 3.90039zM345.43555 256.99223l9.05273-7.0127c2.93457-2.32617 3.86426-3.93652 3.86426-5.6543 0-2.03906-1.7168-3.25586-3.7207-3.25586-2.39746 0-4.22266 1.2168-6.01172 3.25586l-3.36328-3.25586c2.43262-3.07715 5.5459-4.79492 9.51758-4.79492 5.22461 0 9.01758 3.2207 9.01758 7.83691 0 3.29102-1.43164 5.83203-5.72559 8.94531l-4.47266 3.4707h10.41211v4.75879h-18.57031v-4.29395zM367.54785 248.97758c0-7.44336 4.58008-12.70312 11.05664-12.70312s11.02051 5.25977 11.02051 12.70312c0 7.47852-4.54395 12.73828-11.02051 12.73828s-11.05664-5.25977-11.05664-12.73828zm16.67383 0c0-4.61621-2.3252-7.9082-5.61719-7.9082s-5.61816 3.29199-5.61816 7.9082c0 4.61523 2.32617 7.94336 5.61816 7.94336s5.61719-3.32812 5.61719-7.94336zM392.80859 256.99223l9.05273-7.0127c2.93457-2.32617 3.86523-3.93652 3.86523-5.6543 0-2.03906-1.71777-3.25586-3.72168-3.25586-2.39746 0-4.22266 1.2168-6.01172 3.25586l-3.36328-3.25586c2.43359-3.07715 5.5459-4.79492 9.51758-4.79492 5.22461 0 9.01758 3.2207 9.01758 7.83691 0 3.29102-1.43164 5.83203-5.72559 8.94531l-4.47266 3.4707h10.41309v4.75879h-18.57129v-4.29395zM414.16992 257.60063l3.11328-3.50684c1.75293 1.86133 4.0791 2.89844 6.54785 2.89844 2.68359 0 4.29395-1.25195 4.29395-3.00586 0-1.89648-1.50293-2.8623-4.79492-2.82617h-2.82617v-4.50879l2.82617.03613c2.68359 0 4.29395-1.00195 4.29395-2.75586 0-1.78906-1.71777-2.93359-4.15039-2.93359-2.29004 0-4.11523 1.14453-5.76074 2.8623l-3.04199-3.2207c2.04004-2.46875 4.97363-4.36523 9.33887-4.36523 5.51074 0 8.98145 2.82715 8.98145 6.72754 0 2.82617-1.89648 4.86621-4.61523 5.65332 2.68359.6084 5.15234 2.50488 5.15234 5.76074 0 4.25781-3.72168 7.33496-9.48242 7.33496-4.40137 0-7.80078-1.75293-9.87598-4.15039z" class="f"/></g><g><path d="M447.545 251.001H621.518V252.001H447.545z" class="f"/><g clip-path="url(#e)"><path d="M447.54499,251.00136h173.97279v.99998h-173.97279v-.99998Z" class="f"/></g></g></svg>
\ No newline at end of file

From 4a5436f42e05390ed00e12e0f7f915789aaa9973 Mon Sep 17 00:00:00 2001
From: Taahir Ahmed <taahm@google.com>
Date: Tue, 11 Apr 2023 15:38:35 -0700
Subject: [PATCH 208/272] ClusterTrustBundles: Document service account
 impersonation

(Change message to retrigger tests)
---
 .../access-authn-authz/certificate-signing-requests.md    | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/content/en/docs/reference/access-authn-authz/certificate-signing-requests.md b/content/en/docs/reference/access-authn-authz/certificate-signing-requests.md
index 4ce299e5fb5..ba41e551618 100644
--- a/content/en/docs/reference/access-authn-authz/certificate-signing-requests.md
+++ b/content/en/docs/reference/access-authn-authz/certificate-signing-requests.md
@@ -405,6 +405,14 @@ If you use your own authorization mechanism and you have enabled
 ClusterTrustBundles in your cluster, you should set up an equivalent rule to
 make these objects public within the cluster, so that they work as intended.
 
+If you do not have permission to list cluster trust bundles by default in your
+cluster, you can impersonate a service account you have access to in order to
+see available ClusterTrustBundles:
+
+```bash
+kubectl get clustertrustbundles --as='system:serviceaccount:mynamespace:default'
+```
+
 ### Signer-linked ClusterTrustBundles {#ctb-signer-linked}
 
 Signer-linked ClusterTrustBundles are associated with a _signer name_, like this:

From 83972ec198dbfbecf3ffbd92e1778d3453e95172 Mon Sep 17 00:00:00 2001
From: Maria Filocha <maritka10@gmail.com>
Date: Fri, 14 Apr 2023 15:23:01 +0200
Subject: [PATCH 209/272] Synchronize Polish localization for ver 1.26, part 1

Synchronize Polish localization with upstream up to 6e6e4ed79a8e219e7db434fb7f6d76433901739b.

Part 1
---
 content/pl/_index.html | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/content/pl/_index.html b/content/pl/_index.html
index 5c9c8ed9618..1fa0f72c4cd 100644
--- a/content/pl/_index.html
+++ b/content/pl/_index.html
@@ -33,6 +33,8 @@ Niezależnie, czy prowadzisz tylko testy, czy globalny koncern, dzięki elastycz
 
 Kubernetes jako projekt open-source daje Ci wolność wyboru ⏤ skorzystaj z prywatnego centrum danych, infrastruktury hybrydowej lub chmury publicznej. Bez wysiłku możesz przenieść swoje aplikacje tam, gdzie są najbardziej potrzebne.
 
+Żeby pobrać Kubernetesa, odwiedź sekcję [pobierania](/releases/download/).
+
 {{% /blocks/feature %}}
 
 {{< /blocks/section >}}
@@ -44,13 +46,12 @@ Kubernetes jako projekt open-source daje Ci wolność wyboru ⏤ skorzystaj z pr
         <button id="desktopShowVideoButton" onclick="kub.showVideo()">Obejrzyj wideo</button>
         <br>
         <br>
-        <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/" button id="desktopKCButton">Weź udział w KubeCon North America 24-28.10.2022</a>
+        <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/" button id="desktopKCButton">Weź udział w KubeCon + CloudNativeCon Europe 18-21.04.2023</a>
         <br>
         <br>
         <br>
         <br>
-        <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/" button id="desktopKCButton">Weź udział w KubeCon Europe 17-21.04.2023</a>
-
+        <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/" button id="desktopKCButton">Weź udział w KubeCon + CloudNativeCon North America 6-9.11.2023</a>
 </div>
 <div id="videoPlayer">
     <iframe data-url="https://www.youtube.com/embed/H06qrNmGqyE?autoplay=1" frameborder="0" allowfullscreen></iframe>

From bd49796a8fbd5b3e8f0eff5d90cbe10654a158cd Mon Sep 17 00:00:00 2001
From: Fabian B <fabian.baumanis@mailbox.org>
Date: Sat, 8 Apr 2023 16:42:26 +0200
Subject: [PATCH 210/272] Add translation for "Automated rollouts and
 rollbacks"

---
 .../docs/concepts/workloads/controllers/deployment.md  | 10 ++++++++++
 1 file changed, 10 insertions(+)
 create mode 100644 content/de/docs/concepts/workloads/controllers/deployment.md

diff --git a/content/de/docs/concepts/workloads/controllers/deployment.md b/content/de/docs/concepts/workloads/controllers/deployment.md
new file mode 100644
index 00000000000..35b21bc8519
--- /dev/null
+++ b/content/de/docs/concepts/workloads/controllers/deployment.md
@@ -0,0 +1,10 @@
+---
+title: Deployments
+feature:
+    title: Automatisierte Rollouts und Rollbacks
+    description: >
+        Kubernetes wendet Änderungen an deinen Anwendungen oder seiner eigenen Konfiguration stufenweise an. Währenddessen achtet es darauf, dass nicht alle Instanzen der Anwendung zur gleichen Zeit beeinträchtigt werden. Falls etwas schief geht, macht Kubernetes die Änderungen rückgängig.
+
+content_type: concept
+weight: 10
+---
\ No newline at end of file

From 14ef8798951fd2eaf1cec64a9844f2b56a2eefb2 Mon Sep 17 00:00:00 2001
From: Fabian B <fabian.baumanis@mailbox.org>
Date: Sat, 8 Apr 2023 16:46:07 +0200
Subject: [PATCH 211/272] Add translation for "Storage orchestration"

---
 content/de/docs/concepts/storage/persistent_volumes.md | 10 ++++++++++
 1 file changed, 10 insertions(+)
 create mode 100644 content/de/docs/concepts/storage/persistent_volumes.md

diff --git a/content/de/docs/concepts/storage/persistent_volumes.md b/content/de/docs/concepts/storage/persistent_volumes.md
new file mode 100644
index 00000000000..d0320d5b977
--- /dev/null
+++ b/content/de/docs/concepts/storage/persistent_volumes.md
@@ -0,0 +1,10 @@
+---
+title: Persistente Volumes
+feature:
+  title: Speicher-Orchestrierung
+  description: >
+    Binde automatisch deinen gewünschten Speicher ein. Egal, ob lokaler Speicher, Speicher eines Cloud Providers (z.B. AWS oder GCP) oder ein Netzwerkspeicher (z.B. NFS, iSCSI, Ceph oder Cinder).
+
+content_type: concept
+weight: 10
+---
\ No newline at end of file

From adf7b99e4ba5bd1bd1e0685eba1c34be5eee833e Mon Sep 17 00:00:00 2001
From: Fabian B <fabian.baumanis@mailbox.org>
Date: Sat, 8 Apr 2023 18:38:04 +0200
Subject: [PATCH 212/272] Add translation for "Secret and configuration
 management"

---
 content/de/docs/concepts/configuration/secret.md | 9 +++++++++
 1 file changed, 9 insertions(+)
 create mode 100644 content/de/docs/concepts/configuration/secret.md

diff --git a/content/de/docs/concepts/configuration/secret.md b/content/de/docs/concepts/configuration/secret.md
new file mode 100644
index 00000000000..25ee70b7c16
--- /dev/null
+++ b/content/de/docs/concepts/configuration/secret.md
@@ -0,0 +1,9 @@
+---
+title: Secrets
+content_type: concept
+feature:
+  title: Verwaltung von Secrets und Konfigurationen
+  description: >
+    Deploye und aktualisiere Secrets sowie Anwendungskonfigurationen, ohne ein Image neu zu bauen oder Secrets preiszugeben.
+weight: 30
+---
\ No newline at end of file

From 544c78cfcd30c70e241cb8761ed9148125bc08fb Mon Sep 17 00:00:00 2001
From: Fabian B <fabian.baumanis@mailbox.org>
Date: Sat, 8 Apr 2023 18:40:26 +0200
Subject: [PATCH 213/272] Add translation for "Batch execution"

---
 content/de/docs/concepts/workloads/controllers/job.md | 9 +++++++++
 1 file changed, 9 insertions(+)
 create mode 100644 content/de/docs/concepts/workloads/controllers/job.md

diff --git a/content/de/docs/concepts/workloads/controllers/job.md b/content/de/docs/concepts/workloads/controllers/job.md
new file mode 100644
index 00000000000..da65fa9dca7
--- /dev/null
+++ b/content/de/docs/concepts/workloads/controllers/job.md
@@ -0,0 +1,9 @@
+---
+title: Jobs
+content_type: concept
+feature:
+  title: Stapelweise Ausführung
+  description: >
+    Neben Diensten kann Kubernetes auch die stapelweise Ausführung von Workloads verwalten. Im Falle eines Fehlers können Container ausgetauscht werden.
+weight: 50
+---
\ No newline at end of file

From 6d82d6c4fa90047f268d4d800b9d130bf4113f21 Mon Sep 17 00:00:00 2001
From: Fabian B <fabian.baumanis@mailbox.org>
Date: Sat, 8 Apr 2023 18:48:07 +0200
Subject: [PATCH 214/272] Add translation for "IPv4/IPv6 dual stack"

---
 .../concepts/services-networking/dual-stack.md | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
 create mode 100644 content/de/docs/concepts/services-networking/dual-stack.md

diff --git a/content/de/docs/concepts/services-networking/dual-stack.md b/content/de/docs/concepts/services-networking/dual-stack.md
new file mode 100644
index 00000000000..4e1f4be1af3
--- /dev/null
+++ b/content/de/docs/concepts/services-networking/dual-stack.md
@@ -0,0 +1,18 @@
+---
+title: IPv4/IPv6 dual-stack
+description: >-
+  Kubernetes erlaubt Netzwerkkonfigurationen mit IPv4 oder IPv6 (Single Stack).
+  Im Dual-Stack-Betrieb kann IPv4 im Verbund mit IPv6 verwendet werden.
+
+feature:
+  title: IPv4/IPv6 Dual-Stack
+  description: >
+    Pods und Dienste können gleichzeitig IPv4- und IPv6-Adressen verwenden.
+content_type: concept
+reviewers:
+  - lachie83
+  - khenidak
+  - aramase
+  - bridgetkromhout
+weight: 90
+---
\ No newline at end of file

From 1d5135574b94edeb2964e9822f3b0478b2bf309b Mon Sep 17 00:00:00 2001
From: Fabian B <fabian.baumanis@mailbox.org>
Date: Sat, 8 Apr 2023 18:51:43 +0200
Subject: [PATCH 215/272] Add translation for "Service discovery and load
 balancing"

---
 .../de/docs/concepts/services-networking/service.md  | 12 ++++++++++++
 1 file changed, 12 insertions(+)
 create mode 100644 content/de/docs/concepts/services-networking/service.md

diff --git a/content/de/docs/concepts/services-networking/service.md b/content/de/docs/concepts/services-networking/service.md
new file mode 100644
index 00000000000..05b9f275a28
--- /dev/null
+++ b/content/de/docs/concepts/services-networking/service.md
@@ -0,0 +1,12 @@
+---
+title: Services
+feature:
+  title: Service-Discovery und Load Balancing
+  description: >
+    Anwendungen müssen keinen komplizierten Mechanismus für Service-Discovery verwenden. Kubernetes verteilt IP-Adressen und DNS-Einträge automatisch an Pods und übernimmt auch das Load Balancing.
+description: >-
+  Veröffentliche deine Applikation über einen einzelnen, nach außen sichtbaren Endpunkt,
+  auch wenn die Workload über mehrere Backends verteilt ist. 
+content_type: concept
+weight: 10
+---
\ No newline at end of file

From 31cc243d275dea2270ce959b10dc1a6861a39b93 Mon Sep 17 00:00:00 2001
From: Fabian B <fabian.baumanis@mailbox.org>
Date: Sat, 8 Apr 2023 18:53:35 +0200
Subject: [PATCH 216/272] Add translation for "Self healing"

---
 .../docs/concepts/workloads/controllers/replicaset.md  | 10 ++++++++++
 1 file changed, 10 insertions(+)
 create mode 100644 content/de/docs/concepts/workloads/controllers/replicaset.md

diff --git a/content/de/docs/concepts/workloads/controllers/replicaset.md b/content/de/docs/concepts/workloads/controllers/replicaset.md
new file mode 100644
index 00000000000..03addcb9ca0
--- /dev/null
+++ b/content/de/docs/concepts/workloads/controllers/replicaset.md
@@ -0,0 +1,10 @@
+---
+title: ReplicaSet
+feature:
+  title: Selbstheilung
+  anchor: Funktionsweise eines ReplicaSets
+  description: >
+    Container werden mithilfe von Health-Checks überwacht und im Falle eines Fehlers neu gestartet. Sie werden erst wieder verwendet, wenn Sie komplett einsatzbereit sind.
+content_type: concept
+weight: 20
+---
\ No newline at end of file

From 791432d7f3a02b003721893b4c61ec29603aacba Mon Sep 17 00:00:00 2001
From: Fabian B <fabian.baumanis@mailbox.org>
Date: Sat, 8 Apr 2023 18:56:23 +0200
Subject: [PATCH 217/272] Add translation for "Automatic bin packing"

---
 .../concepts/configuration/manage-resource-containers.md | 9 +++++++++
 1 file changed, 9 insertions(+)
 create mode 100644 content/de/docs/concepts/configuration/manage-resource-containers.md

diff --git a/content/de/docs/concepts/configuration/manage-resource-containers.md b/content/de/docs/concepts/configuration/manage-resource-containers.md
new file mode 100644
index 00000000000..9ba50de1934
--- /dev/null
+++ b/content/de/docs/concepts/configuration/manage-resource-containers.md
@@ -0,0 +1,9 @@
+---
+title: Resourcen-Verwaltung für Pods und Container
+content_type: concept
+weight: 40
+feature:
+  title: Automatisches Bin Packing
+  description: >
+    Container können je nach Systemanforderungen auf spezifischen Nodes ausgeführt werden. Somit kann eine effiziente Nutzung von Ressourcen erreicht werden.
+---
\ No newline at end of file

From 5e56b19ae29d261fb2b656f49f03cbcca2af12f2 Mon Sep 17 00:00:00 2001
From: Fabian B <fabian.baumanis@mailbox.org>
Date: Sat, 8 Apr 2023 18:58:47 +0200
Subject: [PATCH 218/272] Add translation for "Designed for extensibility"

---
 content/de/docs/concepts/extend-kubernetes/_index.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/content/de/docs/concepts/extend-kubernetes/_index.md b/content/de/docs/concepts/extend-kubernetes/_index.md
index a537b745ada..d23443d3c31 100644
--- a/content/de/docs/concepts/extend-kubernetes/_index.md
+++ b/content/de/docs/concepts/extend-kubernetes/_index.md
@@ -1,4 +1,8 @@
 ---
 title: "Kubernetes erweitern"
 weight: 110
+feature:
+  title: Für Erweiterungen entworfen
+  description: >
+    Kubernetes kann ohne Änderungen am Upstream-Quelltext erweitert werden.
 ---

From 5ed63def8a3306c3fe6cbfdc53c1f953c7547ee8 Mon Sep 17 00:00:00 2001
From: Stanislav Kardashov <stanislav.kardashov@gmail.com>
Date: Sat, 15 Apr 2023 18:38:24 +0300
Subject: [PATCH 219/272] fix minor typo permision -> permission

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

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 f48ad1e7bf3..d8511ac66d7 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
@@ -201,7 +201,7 @@ For each updated PodSecurityPolicy:
 3. Create the new PodSecurityPolicies. If any Roles or ClusterRoles are granting `use` on all PSPs
    this could cause the new PSPs to be used instead of their mutating counter-parts.
 4. Update your authorization to grant access to the new PSPs. In RBAC this means updating any Roles
-   or ClusterRoles that grant the `use` permision on the original PSP to also grant it to the
+   or ClusterRoles that grant the `use` permission on the original PSP to also grant it to the
    updated PSP.
 5. Verify: after some soak time, rerun the command from step 1 to see if any pods are still using
    the original PSPs. Note that pods need to be recreated after the new policies have been rolled

From 0b25549497f9040ffc87e560e496eb4d72fdc11e Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Fri, 14 Apr 2023 22:07:53 +0800
Subject: [PATCH 220/272] sync 1.27 scheduling-framework.md

sync 1.27 scheduling-framework.md
---
 .../scheduling-framework.md                   | 22 +++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/content/zh-cn/docs/concepts/scheduling-eviction/scheduling-framework.md b/content/zh-cn/docs/concepts/scheduling-eviction/scheduling-framework.md
index 2641362e0af..436e2cc5a5c 100644
--- a/content/zh-cn/docs/concepts/scheduling-eviction/scheduling-framework.md
+++ b/content/zh-cn/docs/concepts/scheduling-eviction/scheduling-framework.md
@@ -105,6 +105,28 @@ stateful tasks.
 -->
 {{< figure src="/images/docs/scheduling-framework-extensions.png" title="调度框架扩展点" class="diagram-large">}}
 
+<!--
+### PreEnqueue {#pre-enqueue}
+-->
+### PreEnqueue {#pre-enqueue}
+
+<!--
+These plugins are called prior to adding Pods to the internal active queue, where Pods are marked as
+ready for scheduling.
+
+Only when all PreEnqueue plugins return `Success`, the Pod is allowed to enter the active queue.
+Otherwise, it's placed in the internal unschedulable Pods list, and doesn't get an `Unschedulable` condition.
+
+For more details about how internal scheduler queues work, read
+[Scheduling queue in kube-scheduler](https://github.com/kubernetes/community/blob/f03b6d5692bd979f07dd472e7b6836b2dad0fd9b/contributors/devel/sig-scheduling/scheduler_queues.md).
+-->
+这些插件在将 Pod 被添加到内部活动队列之前被调用，在此队列中 Pod 被标记为准备好进行调度。
+
+只有当所有 PreEnqueue 插件返回 `Success` 时，Pod 才允许进入活动队列。
+否则，它将被放置在内部无法调度的 Pod 列表中，并且不会获得 `Unschedulable` 状态。
+
+要了解有关内部调度器队列如何工作的更多详细信息，请阅读 [kube-scheduler 调度队列](https://github.com/kubernetes/community/blob/f03b6d5692bd979f07dd472e7b6836b2dad0fd9b/contributors/devel/sig-scheduling/scheduler_queues.md)。
+
 <!--
 ### QueueSort {#queue-sort}
 -->

From 210c50f967913724105093c7dd0678321feabc4f Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Sun, 16 Apr 2023 09:17:29 +0800
Subject: [PATCH 221/272] sync patch-releases

sync patch-releases
---
 content/zh-cn/releases/patch-releases.md | 15 +++++++--------
 1 file changed, 7 insertions(+), 8 deletions(-)

diff --git a/content/zh-cn/releases/patch-releases.md b/content/zh-cn/releases/patch-releases.md
index ff755a51489..94e444dc0d0 100644
--- a/content/zh-cn/releases/patch-releases.md
+++ b/content/zh-cn/releases/patch-releases.md
@@ -149,16 +149,15 @@ releases may also occur in between these.
 <!--
 | Monthly Patch Release | Cherry Pick Deadline | Target date |
 | --------------------- | -------------------- | ----------- |
-| February 2023         | 2023-02-10           | 2023-02-15  |
-| March 2023            | 2023-03-10           | 2023-03-15  |
 | April 2023            | 2023-04-07           | 2023-04-12  |
+| May 2023              | 2023-05-12           | 2023-05-17  |
+| June 2023             | 2023-06-09           | 2023-06-14  |
 -->
-
-| 月度补丁发布    | Cherry Pick 截止日期 |   目标日期  |
-| -------------- | -------------------- | ----------- |
-| 2023 年 2 月   | 2023-02-10           | 2023-02-15  |
-| 2023 年 3 月   | 2023-03-10           | 2023-03-15  |
-| 2023 年 4 月   | 2023-04-07           | 2023-04-12  |
+| 月度补丁发布     | Cherry Pick 截止日期 | 目标日期       |
+|------------|------------------|------------|
+| 2023 年 4 月 | 2023-04-07       | 2023-04-12 |
+| 2023 年 5 月 | 2023-05-12       | 2023-05-17 |
+| 2023 年 6 月 | 2023-06-09       | 2023-06-14 |
 
 <!--
 ## Detailed Release History for Active Branches

From 612163fa46c84600b3f807c986b4013d191161d6 Mon Sep 17 00:00:00 2001
From: j4ckstraw <j4ckstraw@foxmail.com>
Date: Sun, 16 Apr 2023 10:58:42 +0800
Subject: [PATCH 222/272] [zh] fix typo in assign-pod-node.md

Signed-off-by: j4ckstraw <j4ckstraw@foxmail.com>
---
 .../zh-cn/docs/concepts/scheduling-eviction/assign-pod-node.md  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/zh-cn/docs/concepts/scheduling-eviction/assign-pod-node.md b/content/zh-cn/docs/concepts/scheduling-eviction/assign-pod-node.md
index 5af2dfc0449..ade103cf432 100644
--- a/content/zh-cn/docs/concepts/scheduling-eviction/assign-pod-node.md
+++ b/content/zh-cn/docs/concepts/scheduling-eviction/assign-pod-node.md
@@ -419,7 +419,7 @@ Pods, the default Kubernetes scheduler places those Pods and honors any
 DaemonSet 控制器[为 DaemonSet 创建 Pod](/zh-cn/docs/concepts/workloads/controllers/daemonset/#how-daemon-pods-are-scheduled)，
 但该控制器不理会调度方案。
 DaemonSet 控制器创建 Pod 时，默认的 Kubernetes 调度器负责放置 Pod，
-并遵从 DaemonSet 控制器中奢侈的 `nodeAffinity` 规则。
+并遵从 DaemonSet 控制器中设置的 `nodeAffinity` 规则。
 {{< /note >}}
 
 <!--

From 4eb68d2db27ba3e6a0773ff32bb42baa59a060b9 Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Sun, 16 Apr 2023 09:12:04 +0800
Subject: [PATCH 223/272] sync kubeadm_upgrade_apply

sync kubeadm_upgrade_apply
---
 .../setup-tools/kubeadm/generated/kubeadm_upgrade_apply.md   | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/content/zh-cn/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_apply.md b/content/zh-cn/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_apply.md
index 026ae9f0098..4847dac894e 100644
--- a/content/zh-cn/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_apply.md
+++ b/content/zh-cn/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_apply.md
@@ -138,11 +138,12 @@ Perform the upgrade of etcd.
 <tr>
 <td></td><td style="line-height: 130%; word-wrap: break-word;">
 <!--
-A set of key=value pairs that describe feature gates for various features. Options are:<br/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)
+A set of key=value pairs that describe feature gates for various features. Options are:<br/>EtcdLearnerMode=true|false (ALPHA - default=false)<br/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)
 -->
 <p>
 一组键值对，用于描述各种功能。选项包括：
-<br/>PublicKeysECDSA=true|false (ALPHA - 默认值=false
+<br/>EtcdLearnerMode=true|false (ALPHA - 默认值=false)
+<br/>PublicKeysECDSA=true|false (ALPHA - 默认值=false)
 <br/>RootlessControlPlane=true|false (ALPHA - 默认值=false)
 </p>
 </td>

From ae4f12001fcdf7ef22c7a1a2d39f603dec47d9eb Mon Sep 17 00:00:00 2001
From: Michael <cloudyonspring@126.com>
Date: Fri, 14 Apr 2023 19:45:25 +0800
Subject: [PATCH 224/272] [zh] sync /services-networking/service.md

---
 .../concepts/services-networking/service.md   | 174 +++++++++++++-----
 1 file changed, 130 insertions(+), 44 deletions(-)

diff --git a/content/zh-cn/docs/concepts/services-networking/service.md b/content/zh-cn/docs/concepts/services-networking/service.md
index 76e931ae4c9..fbd4e5374c0 100644
--- a/content/zh-cn/docs/concepts/services-networking/service.md
+++ b/content/zh-cn/docs/concepts/services-networking/service.md
@@ -1079,6 +1079,22 @@ The cloud provider decides how it is load balanced.
 -->
 来自外部负载均衡器的流量将直接重定向到后端 Pod 上，不过实际它们是如何工作的，这要依赖于云提供商。
 
+<!--
+To implement a Service of `type: LoadBalancer`, Kubernetes typically starts off
+by making the changes that are equivalent to you requesting a Service of
+`type: NodePort`. The cloud-controller-manager component then configures the external load balancer to
+forward traffic to that assigned node port.
+
+You can configure a load balanced Service to
+[omit](#load-balancer-nodeport-allocation) assigning a node port, provided that the
+cloud provider implementation supports this.
+-->
+要实现 `type: LoadBalancer` 的服务，Kubernetes 通常首先进行与请求 `type: NodePort` 服务等效的更改。
+cloud-controller-manager 组件随后配置外部负载均衡器以将流量转发到已分配的节点端口。
+
+你可以将负载均衡服务配置为[忽略](#load-balancer-nodeport-allocation)分配节点端口，
+前提是云提供商实现支持这点。
+
 <!--
 Some cloud providers allow you to specify the `loadBalancerIP`. In those cases, the load-balancer is created
 with the user-specified `loadBalancerIP`. If the `loadBalancerIP` field is not specified,
@@ -1092,50 +1108,41 @@ set is ignored.
 如果设置了 `loadBalancerIP`，但云提供商并不支持这种特性，那么设置的
 `loadBalancerIP` 值将会被忽略掉。
 
-<!--
-To implement a Service of `type: LoadBalancer`, Kubernetes typically starts off
-by making the changes that are equivalent to you requesting a Service of
-`type: NodePort`. The cloud-controller-manager component then configures the external load balancer to
-forward traffic to that assigned node port.
-
-You can configure a load balanced Service to
-[omit](#load-balancer-nodeport-allocation) assigning a node port, provided that the
-cloud provider implementation supports this.
--->
-要实现 `type: LoadBalancer` 的服务，Kubernetes 通常首先进行与请求 `type: NodePort` 服务等效的更改。
-cloud-controller-manager 组件然后配置外部负载均衡器以将流量转发到已分配的节点端口。
-
-你可以将负载均衡服务配置为[忽略](#load-balancer-nodeport-allocation)分配节点端口，
-前提是云提供商实现支持这点。
-
 {{< note >}}
 <!--
-On **Azure**, if you want to use a user-specified public type `loadBalancerIP`, you first need
-to create a static type public IP address resource. This public IP address resource should
-be in the same resource group of the other automatically created resources of the cluster.
-For example, `MC_myResourceGroup_myAKSCluster_eastus`.
+The`.spec.loadBalancerIP` field for a Service was deprecated in Kubernetes v1.24.
 
-Specify the assigned IP address as loadBalancerIP. Ensure that you have updated the
-`securityGroupName` in the cloud provider configuration file.
-For information about troubleshooting `CreatingLoadBalancerFailed` permission issues see,
-[Use a static IP address with the Azure Kubernetes Service (AKS) load balancer](https://docs.microsoft.com/en-us/azure/aks/static-ip)
-or [CreatingLoadBalancerFailed on AKS cluster with advanced networking](https://github.com/Azure/AKS/issues/357).
+This field was under-specified and its meaning varies across implementations. It also cannot support dual-stack networking. This field may be removed in a future API version.
 -->
-在 **Azure** 上，如果要使用用户指定的公共类型 `loadBalancerIP`，
-则首先需要创建静态类型的公共 IP 地址资源。
-此公共 IP 地址资源应与集群中其他自动创建的资源位于同一资源组中。
-例如，`MC_myResourceGroup_myAKSCluster_eastus`。
+针对 Service 的 `.spec.loadBalancerIP` 字段已在 Kubernetes v1.24 中被弃用。
 
-将分配的 IP 地址设置为 loadBalancerIP。确保你已更新云提供程序配置文件中的 securityGroupName。
-有关对 `CreatingLoadBalancerFailed` 权限问题进行故障排除的信息，
-请参阅[与 Azure Kubernetes 服务（AKS）负载均衡器一起使用静态 IP 地址](https://docs.microsoft.com/zh-cn/azure/aks/static-ip)
-或[在 AKS 集群上使用高级联网时出现 CreatingLoadBalancerFailed](https://github.com/Azure/AKS/issues/357)。
+此字段的定义模糊，其含义因实现而异。它也不支持双协议栈联网。
+此字段可能会在未来的 API 版本中被移除。
+
+<!--
+If you're integrating with a provider that supports specifying the load balancer IP address(es)
+for a Service via a (provider specific) annotation, you should switch to doing that.
+
+If you are writing code for a load balancer integration with Kubernetes, avoid using this field.
+You can integrate with [Gateway](https://gateway-api.sigs.k8s.io/) rather than Service, or you
+can define your own (provider specific) annotations on the Service that specify the equivalent detail.
+-->
+如果你正在集成某云平台，该平台通过（特定于提供商的）注解为 Service 指定负载均衡器 IP 地址，
+你应该切换到这样做。
+
+如果你正在为集成到 Kubernetes 的负载均衡器编写代码，请避免使用此字段。
+你可以与 [Gateway](https://gateway-api.sigs.k8s.io/) 而不是 Service 集成，
+或者你可以在 Service 上定义自己的（特定于提供商的）注解，以指定等效的细节。
 {{< /note >}}
+
 <!--
 #### Load balancers with mixed protocol types
+-->
+#### 混合协议类型的负载均衡器
 
 {{< feature-state for_k8s_version="v1.24" state="beta" >}}
 
+<!--
 By default, for LoadBalancer type of Services, when there is more than one port defined, all
 ports must have the same protocol, and the protocol must be one which is supported
 by the cloud provider.
@@ -1143,15 +1150,12 @@ by the cloud provider.
 The feature gate `MixedProtocolLBService` (enabled by default for the kube-apiserver as of v1.24) allows the use of
 different protocols for LoadBalancer type of Services, when there is more than one port defined.
 -->
-#### 混合协议类型的负载均衡器
-
-{{< feature-state for_k8s_version="v1.20" state="alpha" >}}
-
 默认情况下，对于 LoadBalancer 类型的服务，当定义了多个端口时，
 所有端口必须具有相同的协议，并且该协议必须是受云提供商支持的协议。
 
-当服务中定义了多个端口时，特性门控 `MixedProtocolLBService`（在 kube-apiserver 1.24 版本默认为启用）允许
-LoadBalancer 类型的服务使用不同的协议。
+当服务中定义了多个端口时，特性门控 `MixedProtocolLBService`
+（在 kube-apiserver 1.24 版本默认为启用）
+允许 LoadBalancer 类型的服务使用不同的协议。
 
 {{< note >}}
 <!--
@@ -1308,7 +1312,7 @@ metadata:
 ```
 
 {{% /tab %}}
-{{% tab name="Baidu Cloud" %}}
+{{% tab name="<!--Baidu Cloud-->百度云" %}}
 
 ```yaml
 [...]
@@ -1320,7 +1324,7 @@ metadata:
 ```
 
 {{% /tab %}}
-{{% tab name="Tencent Cloud" %}}
+{{% tab name="<!--Tencent Cloud-->腾讯云" %}}
 
 ```yaml
 [...]
@@ -1331,7 +1335,7 @@ metadata:
 ```
 
 {{% /tab %}}
-{{% tab name="Alibaba Cloud" %}}
+{{% tab name="<!--Alibaba Cloud-->阿里云" %}}
 
 ```yaml
 [...]
@@ -1449,7 +1453,7 @@ You can then specify any one of those policies using the
 annotation; for example:
 -->
 然后，你可以使用 "`service.beta.kubernetes.io/aws-load-balancer-ssl-negotiation-policy`"
-注解; 例如：
+注解；例如：
 
 ```yaml
     metadata:
@@ -1483,6 +1487,7 @@ Since version 1.3.0, the use of this annotation applies to all ports proxied by
 and cannot be configured otherwise.
 -->
 从 1.3.0 版开始，此注解的使用适用于 ELB 代理的所有端口，并且不能进行其他配置。
+
 <!--
 #### ELB Access Logs on AWS
 
@@ -1517,6 +1522,24 @@ specifies the logical hierarchy you created for your Amazon S3 bucket.
 注解 `service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-prefix`
 指定为 Amazon S3 存储桶创建的逻辑层次结构。
 
+<!--
+```yaml
+    metadata:
+      name: my-service
+      annotations:
+        # Specifies whether access logs are enabled for the load balancer
+        service.beta.kubernetes.io/aws-load-balancer-access-log-enabled: "true"
+
+        # The interval for publishing the access logs. You can specify an interval of either 5 or 60 (minutes).
+        service.beta.kubernetes.io/aws-load-balancer-access-log-emit-interval: "60"
+
+        # The name of the Amazon S3 bucket where the access logs are stored
+        service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-name: "my-bucket"
+
+        # The logical hierarchy you created for your Amazon S3 bucket, for example `my-bucket-prefix/prod`
+        service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-prefix: "my-bucket-prefix/prod"
+```
+-->
 ```yaml
     metadata:
       name: my-service
@@ -1565,6 +1588,63 @@ There are other annotations to manage Classic Elastic Load Balancers that are de
 
 还有其他一些注解，用于管理经典弹性负载均衡器，如下所述。
 
+<!--
+```yaml
+    metadata:
+      name: my-service
+      annotations:
+        # The time, in seconds, that the connection is allowed to be idle (no data has been sent
+        # over the connection) before it is closed by the load balancer
+        service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout: "60"
+
+        # Specifies whether cross-zone load balancing is enabled for the load balancer
+        service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: "true"
+
+        # A comma-separated list of key-value pairs which will be recorded as
+        # additional tags in the ELB.
+        service.beta.kubernetes.io/aws-load-balancer-additional-resource-tags: "environment=prod,owner=devops"
+
+        # The number of successive successful health checks required for a backend to
+        # be considered healthy for traffic. Defaults to 2, must be between 2 and 10
+        service.beta.kubernetes.io/aws-load-balancer-healthcheck-healthy-threshold: ""
+
+        # The number of unsuccessful health checks required for a backend to be
+        # considered unhealthy for traffic. Defaults to 6, must be between 2 and 10
+        service.beta.kubernetes.io/aws-load-balancer-healthcheck-unhealthy-threshold: "3"
+
+        # The approximate interval, in seconds, between health checks of an
+        # individual instance. Defaults to 10, must be between 5 and 300
+        service.beta.kubernetes.io/aws-load-balancer-healthcheck-interval: "20"
+
+        # The amount of time, in seconds, during which no response means a failed
+        # health check. This value must be less than the service.beta.kubernetes.io/aws-load-balancer-healthcheck-interval
+        # value. Defaults to 5, must be between 2 and 60
+        service.beta.kubernetes.io/aws-load-balancer-healthcheck-timeout: "5"
+
+        # A list of existing security groups to be configured on the ELB created. Unlike the annotation
+        # service.beta.kubernetes.io/aws-load-balancer-extra-security-groups, this replaces all other
+        # security groups previously assigned to the ELB and also overrides the creation
+        # of a uniquely generated security group for this ELB.
+        # The first security group ID on this list is used as a source to permit incoming traffic to
+        # target worker nodes (service traffic and health checks).
+        # If multiple ELBs are configured with the same security group ID, only a single permit line
+        # will be added to the worker node security groups, that means if you delete any
+        # of those ELBs it will remove the single permit line and block access for all ELBs that shared the same security group ID.
+        # This can cause a cross-service outage if not used properly
+        service.beta.kubernetes.io/aws-load-balancer-security-groups: "sg-53fae93f"
+
+        # A list of additional security groups to be added to the created ELB, this leaves the uniquely
+        # generated security group in place, this ensures that every ELB
+        # has a unique security group ID and a matching permit line to allow traffic to the target worker nodes
+        # (service traffic and health checks).
+        # Security groups defined here can be shared between services.
+        service.beta.kubernetes.io/aws-load-balancer-extra-security-groups: "sg-53fae93f,sg-42efd82e"
+
+        # A comma separated list of key-value pairs which are used
+        # to select the target nodes for the load balancer
+        service.beta.kubernetes.io/aws-load-balancer-target-node-labels: "ingress-gw,gw-name=public-api"
+```
+-->
 ```yaml
     metadata:
       name: my-service
@@ -1691,9 +1771,16 @@ groups are modified with the following IP rules:
 
 为了使客户端流量能够到达 NLB 后面的实例，使用以下 IP 规则修改了节点安全组：
 
+<!--
 | Rule | Protocol | Port(s) | IpRange(s) | IpRange Description |
 |------|----------|---------|------------|---------------------|
 | Health Check | TCP | NodePort(s) (`.spec.healthCheckNodePort` for `.spec.externalTrafficPolicy = Local`) | Subnet CIDR | kubernetes.io/rule/nlb/health=\<loadBalancerName\> |
+| Client Traffic | TCP | NodePort(s) | `.spec.loadBalancerSourceRanges` (defaults to `0.0.0.0/0`) | kubernetes.io/rule/nlb/client=\<loadBalancerName\> |
+| MTU Discovery | ICMP | 3,4 | `.spec.loadBalancerSourceRanges` (defaults to `0.0.0.0/0`) | kubernetes.io/rule/nlb/mtu=\<loadBalancerName\> |
+-->
+| 规则 | 协议 | 端口 | IpRange(s) | IpRange 描述 |
+|------|----------|---------|------------|---------------------|
+| Health Check | TCP | NodePort(s) (`.spec.healthCheckNodePort` for `.spec.externalTrafficPolicy = Local`) | Subnet CIDR | kubernetes.io/rule/nlb/health=\<loadBalancerName\> |
 | Client Traffic | TCP | NodePort(s) | `.spec.loadBalancerSourceRanges` (默认值为 `0.0.0.0/0`) | kubernetes.io/rule/nlb/client=\<loadBalancerName\> |
 | MTU Discovery | ICMP | 3,4 | `.spec.loadBalancerSourceRanges` (默认值为 `0.0.0.0/0`) | kubernetes.io/rule/nlb/mtu=\<loadBalancerName\> |
 
@@ -1864,7 +1951,6 @@ to learn more.
 
 Service is a top-level resource in the Kubernetes REST API. You can find more details
 about the [Service API object](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#service-v1-core).
-
 -->
 ## API 对象   {#api-object}
 

From 46e88db8f17e41f06b7a8b441d68bf47a3e47074 Mon Sep 17 00:00:00 2001
From: windsonsea <haifeng.yao@daocloud.io>
Date: Fri, 14 Apr 2023 17:38:54 +0800
Subject: [PATCH 225/272] [zh] sync csi-driver-v1.md

---
 .../csi-driver-v1.md                          | 177 ++++++++++++++----
 1 file changed, 144 insertions(+), 33 deletions(-)

diff --git a/content/zh-cn/docs/reference/kubernetes-api/config-and-storage-resources/csi-driver-v1.md b/content/zh-cn/docs/reference/kubernetes-api/config-and-storage-resources/csi-driver-v1.md
index c6cac3bbdf7..568f0736160 100644
--- a/content/zh-cn/docs/reference/kubernetes-api/config-and-storage-resources/csi-driver-v1.md
+++ b/content/zh-cn/docs/reference/kubernetes-api/config-and-storage-resources/csi-driver-v1.md
@@ -41,10 +41,12 @@ CSIDriver 对象未划分命名空间。
 
 <!--
 - **metadata** (<a href="{{< ref "../common-definitions/object-meta#ObjectMeta" >}}">ObjectMeta</a>)
+
   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
 
 - **spec** (<a href="{{< ref "../config-and-storage-resources/csi-driver-v1#CSIDriverSpec" >}}">CSIDriverSpec</a>), required
-  Specification of the CSI Driver.
+
+  spec represents the specification of the CSI Driver.
 -->
 - **metadata** (<a href="{{< ref "../common-definitions/object-meta#ObjectMeta" >}}">ObjectMeta</a>)
   
@@ -58,7 +60,7 @@ CSIDriver 对象未划分命名空间。
 
 - **spec** (<a href="{{< ref "../config-and-storage-resources/csi-driver-v1#CSIDriverSpec" >}}">CSIDriverSpec</a>)，必需
   
-  CSI 驱动的规约。
+  spec 表示 CSI 驱动的规约。
 
 ## CSIDriverSpec {#CSIDriverSpec}
 
@@ -89,7 +91,8 @@ CSIDriverSpec 是 CSIDriver 的规约。
 
 <!--
 - **fsGroupPolicy** (string)
-  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.
+
+  fsGroupPolicy 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.
   
@@ -97,7 +100,7 @@ CSIDriverSpec 是 CSIDriver 的规约。
 -->
 - **fsGroupPolicy** (string)
   
-  定义底层卷是否支持在挂载之前更改卷的所有权和权限。
+  fsGroupPolicy 定义底层卷是否支持在挂载之前更改卷的所有权和权限。
   有关更多详细信息，请参考特定的 FSGroupPolicy 值。
   
   此字段不可变更。
@@ -107,28 +110,38 @@ CSIDriverSpec 是 CSIDriver 的规约。
 
 <!--
 - **podInfoOnMount** (boolean)
-  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. "csi.storage.k8s.io/pod.name": pod.Name "csi.storage.k8s.io/pod.namespace": pod.Namespace "csi.storage.k8s.io/pod.uid": string(pod.UID) "csi.storage.k8s.io/ephemeral": "true" if the volume is an ephemeral inline volume defined by a CSIVolumeSource, otherwise "false"
-  
-  "csi.storage.k8s.io/ephemeral" is a new feature in Kubernetes 1.16. It is only required for drivers which support both the "Persistent" and "Ephemeral" VolumeLifecycleMode. Other drivers can leave pod info disabled and/or ignore this field. As Kubernetes 1.15 doesn'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.
+
+  podInfoOnMount indicates this CSI volume driver requires additional pod information (like podName, podUID, etc.) during mount operations, if set to true. If set to false, pod information will not be passed on mount. Default is false.
 -->
 - **podInfoOnMount** (boolean)
+
+  如果 podInfoOnMount 设为 true，则表示在挂载操作期间这个 CSI 卷驱动需要更多的
+  Pod 信息（例如 podName 和 podUID 等）。
+  如果设为 false，则挂载时将不传递 Pod 信息。默认为 false。
   
-  如果设为 true，则 podInfoOnMount 表示在挂载操作期间这个 CSI 卷需要更多的 Pod 信息（例如 podName 和 podUID 等）。
-  如果设为 false，则挂载时将不传递 Pod 信息。
-  默认为 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. "csi.storage.k8s.io/pod.name": pod.Name "csi.storage.k8s.io/pod.namespace": pod.Namespace "csi.storage.k8s.io/pod.uid": string(pod.UID) "csi.storage.k8s.io/ephemeral": "true" if the volume is an ephemeral inline volume defined by a CSIVolumeSource, otherwise "false"
+  -->
   CSI 驱动将 podInfoOnMount 指定为驱动部署的一部分。
   如果为 true，Kubelet 将在 CSI NodePublishVolume() 调用中作为 VolumeContext 传递 Pod 信息。
   CSI 驱动负责解析和校验作为 VolumeContext 传递进来的信息。
+
   如果 podInfoOnMount 设为 true，将传递以下 VolumeConext。
   此列表可能变大，但将使用前缀。
+
   - "csi.storage.k8s.io/pod.name": pod.name
   - "csi.storage.k8s.io/pod.namespace": pod.namespace
   - "csi.storage.k8s.io/pod.uid": string(pod.UID)
   - "csi.storage.k8s.io/ephemeral":
     如果此卷是 CSIVolumeSource 定义的一个临时内联卷，则为 “true”，否则为 “false”
+
+  <!--
+  "csi.storage.k8s.io/ephemeral" is a new feature in Kubernetes 1.16. It is only required for drivers which support both the "Persistent" and "Ephemeral" VolumeLifecycleMode. Other drivers can leave pod info disabled and/or ignore this field. As Kubernetes 1.15 doesn'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.
+  -->
   “csi.storage.k8s.io/ephemeral” 是 Kubernetes 1.16 中一个新的功能特性。
   只有同时支持 “Persistent” 和 “Ephemeral” VolumeLifecycleMode 的驱动，此字段才是必需的。
   其他驱动可以保持禁用 Pod 信息或忽略此字段。
@@ -139,7 +152,8 @@ CSIDriverSpec 是 CSIDriver 的规约。
 
 <!--
 - **requiresRepublish** (boolean)
-  RequiresRepublish indicates the CSI driver wants `NodePublishVolume` being periodically called to reflect any possible change in the mounted volume. This field defaults to false.
+
+  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.
 -->
@@ -155,7 +169,7 @@ CSIDriverSpec 是 CSIDriver 的规约。
 <!--
 - **seLinuxMount** (boolean)
 
-  SELinuxMount specifies if the CSI driver supports "-o context" mount option.
+  seLinuxMount specifies if the CSI driver supports "-o context" mount option.
   
   When "true", the CSI driver must ensure that all volumes provided by this CSI driver can be mounted separately with different `-o context` options. This is typical for storage backends that provide volumes as filesystems on block devices or as independent shared volumes. Kubernetes will call NodeStage / NodePublish with "-o context=xyz" mount option when mounting a ReadWriteOncePod volume used in Pod that has explicitly set SELinux context. In the future, it may be expanded to other volume AccessModes. In any case, Kubernetes will ensure that the volume is mounted only with a single SELinux context.
 -->
@@ -178,9 +192,11 @@ CSIDriverSpec 是 CSIDriver 的规约。
   这通常用于代表更大共享文件系统的子目录的卷。
   
   默认为 “false”。
+
 <!--
 - **storageCapacity** (boolean)
-  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.
+
+  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, if set to true.
   
   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.
   
@@ -204,13 +220,16 @@ CSIDriverSpec 是 CSIDriver 的规约。
 
 <!--
 - **tokenRequests** ([]TokenRequest)
+
   *Atomic: will be replaced during a merge*
   
-  TokenRequests indicates the CSI driver needs pods' 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: "csi.storage.k8s.io/
-  
-  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.
-  <a name="TokenRequest"></a>
-  *TokenRequest contains parameters of a service account token.*
+  tokenRequests indicates the CSI driver needs pods' 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: "csi.storage.k8s.io/serviceAccount.tokens": {
+    "\<audience>": {
+      "token": \<token>,
+      "expirationTimestamp": \<expiration timestamp in RFC3339>,
+    },
+    ...
+  }
 -->
 - **tokenRequests** ([]TokenRequest)
   
@@ -230,21 +249,27 @@ CSIDriverSpec 是 CSIDriver 的规约。
   }
   ```
 
+  <!--
+  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.
+
+  <a name="TokenRequest"></a>
+  *TokenRequest contains parameters of a service account token.*
+  -->
   注：每个 tokenRequest 中的受众应该不同，且最多有一个令牌是空字符串。
   要在令牌过期后接收一个新的令牌，requiresRepublish 可用于周期性地触发 NodePublishVolume。
   
   <a name="TokenRequest"></a>
   **tokenRequest 包含一个服务帐户令牌的参数。**
 
-<!--
+  <!--
   - **tokenRequests.audience** (string), required
 
-    Audience is the intended audience of the token in "TokenRequestSpec". It will default to the audiences of kube apiserver.
+    audience is the intended audience of the token in "TokenRequestSpec". It will default to the audiences of kube apiserver.
 
   - **tokenRequests.expirationSeconds** (int64)
 
-    ExpirationSeconds is the duration of validity of the token in "TokenRequestSpec". It has the same default value of "ExpirationSeconds" in "TokenRequestSpec".
--->  
+    expirationSeconds is the duration of validity of the token in "TokenRequestSpec". It has the same default value of "ExpirationSeconds" in "TokenRequestSpec".
+  -->  
   - **tokenRequests.audience** (string)，必需
     
     audience 是 “TokenRequestSpec” 中令牌的目标受众。
@@ -260,9 +285,7 @@ CSIDriverSpec 是 CSIDriver 的规约。
 
   *Set: unique values will be kept during a merge*
   
-  volumeLifecycleModes defines what kind of volumes this CSI volume driver supports. The default if the list is empty is "Persistent", which is the usage defined by the CSI specification and implemented in Kubernetes via the usual PV/PVC mechanism. The other mode is "Ephemeral". 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.
+  volumeLifecycleModes defines what kind of volumes this CSI volume driver supports. The default if the list is empty is "Persistent", which is the usage defined by the CSI specification and implemented in Kubernetes via the usual PV/PVC mechanism.
 -->
 - **volumeLifecycleModes** ([]string)
   
@@ -271,15 +294,23 @@ CSIDriverSpec 是 CSIDriver 的规约。
   volumeLifecycleModes 定义这个 CSI 卷驱动支持哪种类别的卷。
   如果列表为空，则默认值为 “Persistent”，这是 CSI 规范定义的用法，
   并通过常用的 PV/PVC 机制在 Kubernetes 中实现。
+
+  <!--
+  The other mode is "Ephemeral". 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.
+  -->
   另一种模式是 “Ephemeral”。
   在这种模式下，在 Pod 规约中用 CSIVolumeSource 以内联方式定义卷，其生命周期与该 Pod 的生命周期相关联。
   驱动必须感知到这一点，因为只有针对这种卷才会接收到 NodePublishVolume 调用。
+
   有关实现此模式的更多信息，请参阅
   https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html。
   驱动可以支持其中一种或多种模式，将来可能会添加更多模式。
-  此字段处于 Beta 阶段。
   
-  此字段不可变更。
+  此字段处于 Beta 阶段。此字段不可变更。
 
 ## CSIDriverList {#CSIDriverList}
 
@@ -344,7 +375,7 @@ GET /apis/storage.k8s.io/v1/csidrivers/{name}
 
 - **name** (**路径参数**): string，必需
   
-  CSIDriver 的名称
+  CSIDriver 的名称。
 
 - **pretty** (**查询参数**): string
   
@@ -372,16 +403,50 @@ GET /apis/storage.k8s.io/v1/csidrivers
 
 <!--
 #### Parameters
+
 - **allowWatchBookmarks** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#allowWatchBookmarks" >}}">allowWatchBookmarks</a>
+
 - **continue** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#continue" >}}">continue</a>
+
 - **fieldSelector** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldSelector" >}}">fieldSelector</a>
+
 - **labelSelector** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#labelSelector" >}}">labelSelector</a>
+
 - **limit** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#limit" >}}">limit</a>
+
 - **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
 - **resourceVersion** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#resourceVersion" >}}">resourceVersion</a>
+
 - **resourceVersionMatch** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
+
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
 - **timeoutSeconds** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
+
 - **watch** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#watch" >}}">watch</a>
 -->
 #### 参数
 
@@ -417,6 +482,10 @@ GET /apis/storage.k8s.io/v1/csidrivers
   
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
+- **sendInitialEvents** (**查询参数**): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
 - **timeoutSeconds** (**查询参数**): integer
   
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -511,7 +580,7 @@ PUT /apis/storage.k8s.io/v1/csidrivers/{name}
 
 - **name** (**路径参数**): string，必需
   
-  CSIDriver 的名称
+  CSIDriver 的名称。
 
 - **body**: <a href="{{< ref "../config-and-storage-resources/csi-driver-v1#CSIDriver" >}}">CSIDriver</a>，必需
 
@@ -568,7 +637,7 @@ PATCH /apis/storage.k8s.io/v1/csidrivers/{name}
 
 - **name** (**路径参数**): string，必需
   
-  CSIDriver 的名称
+  CSIDriver 的名称。
 
 - **body**: <a href="{{< ref "../common-definitions/patch#Patch" >}}">Patch</a>，必需
 
@@ -628,7 +697,7 @@ DELETE /apis/storage.k8s.io/v1/csidrivers/{name}
 
 - **name** (**路径参数**): string，必需
   
-  CSIDriver 的名称
+  CSIDriver 的名称。
 
 - **body**: <a href="{{< ref "../common-definitions/delete-options#DeleteOptions" >}}">DeleteOptions</a>
 
@@ -672,18 +741,56 @@ DELETE /apis/storage.k8s.io/v1/csidrivers
 
 <!--
 #### Parameters
+
 - **body**: <a href="{{< ref "../common-definitions/delete-options#DeleteOptions" >}}">DeleteOptions</a>
+
 - **continue** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#continue" >}}">continue</a>
+
 - **dryRun** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
+
 - **fieldSelector** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldSelector" >}}">fieldSelector</a>
+
 - **gracePeriodSeconds** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#gracePeriodSeconds" >}}">gracePeriodSeconds</a>
+
 - **labelSelector** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#labelSelector" >}}">labelSelector</a>
+
 - **limit** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#limit" >}}">limit</a>
+
 - **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
 - **propagationPolicy** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#propagationPolicy" >}}">propagationPolicy</a>
+
 - **resourceVersion** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#resourceVersion" >}}">resourceVersion</a>
+
 - **resourceVersionMatch** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
+
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
 - **timeoutSeconds** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
 -->
 #### 参数
 
@@ -729,6 +836,10 @@ DELETE /apis/storage.k8s.io/v1/csidrivers
   
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
+- **sendInitialEvents** (**查询参数**): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
 - **timeoutSeconds** (**查询参数**): integer
   
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>

From ad7c0712c646fe559be6508686516419fd6c502d Mon Sep 17 00:00:00 2001
From: Qiming Teng <tengqm@outlook.com>
Date: Sun, 16 Apr 2023 16:26:38 +0800
Subject: [PATCH 226/272] Fix examples test for 1.27

- Some examples are actually not good "examples", i.e. they are not
  not ready for the users to try out.
- Some examples are failing the validation in their current format.
- Some examples skipped the test case.

These issues are fixed.
---
 .../extensible-admission-controllers.md       |  50 ++++-
 .../validating-admission-policy.md            |  17 +-
 .../admission-webhook-match-conditions.yaml   |  47 ----
 .../audit-event-with-audit-annotation.yaml    |  12 --
 .../access/deployment-replicas-policy.yaml    |   3 +-
 ...ing-admission-policy-audit-annotation.yaml |   3 +-
 content/en/examples/examples_test.go          |  51 +++--
 go.mod                                        | 130 ++++++-----
 go.sum                                        | 203 ++++++++++--------
 9 files changed, 292 insertions(+), 224 deletions(-)
 delete mode 100644 content/en/examples/access/admission-webhook-match-conditions.yaml
 delete mode 100644 content/en/examples/access/audit-event-with-audit-annotation.yaml

diff --git a/content/en/docs/reference/access-authn-authz/extensible-admission-controllers.md b/content/en/docs/reference/access-authn-authz/extensible-admission-controllers.md
index aa1a61b2e38..7c3636e49b1 100644
--- a/content/en/docs/reference/access-authn-authz/extensible-admission-controllers.md
+++ b/content/en/docs/reference/access-authn-authz/extensible-admission-controllers.md
@@ -736,7 +736,55 @@ webhook to be called.
 
 Here is an example illustrating a few different uses for match conditions:
 
-{{< codenew file="access/admission-webhook-match-conditions.yaml" >}}
+```yaml
+apiVersion: admissionregistration.k8s.io/v1
+kind: ValidatingWebhookConfiguration
+webhooks:
+  - name: my-webhook.example.com
+    matchPolicy: Equivalent
+    rules:
+      - operations: ['CREATE','UPDATE']
+        apiGroups: ['*']
+        apiVersions: ['*']
+        resources: ['*']
+    failurePolicy: 'Ignore' # Fail-open (optional)
+    sideEffects: None
+    clientConfig:
+      service:
+        namespace: my-namespace
+        name: my-webhook
+      caBundle: '<omitted>'
+    matchConditions:
+      - name: 'exclude-leases' # Each match condition must have a unique name
+        expression: '!(request.resource.group == "coordination.k8s.io" && request.resource.resource == "leases")' # Match non-lease resources.
+      - name: 'exclude-kubelet-requests'
+        expression: '!("system:nodes" in request.userInfo.groups)' # Match requests made by non-node users.
+      - name: 'rbac' # Skip RBAC requests, which are handled by the second webhook.
+        expression: 'request.resource.group != "rbac.authorization.k8s.io"'
+  
+  # This example illustrates the use of the 'authorizer'. The authorization check is more expensive
+  # than a simple expression, so in this example it is scoped to only RBAC requests by using a second
+  # webhook. Both webhooks can be served by the same endpoint.
+  - name: rbac.my-webhook.example.com
+    matchPolicy: Equivalent
+    rules:
+      - operations: ['CREATE','UPDATE']
+        apiGroups: ['rbac.authorization.k8s.io']
+        apiVersions: ['*']
+        resources: ['*']
+    failurePolicy: 'Fail' # Fail-closed (the default)
+    sideEffects: None
+    clientConfig:
+      service:
+        namespace: my-namespace
+        name: my-webhook
+      caBundle: '<omitted>'
+    matchConditions:
+      - name: 'breakglass'
+        # Skip requests made by users authorized to 'breakglass' on this webhook.
+        # The 'breakglass' API verb does not need to exist outside this check.
+        expression: '!authorizer.group("admissionregistration.k8s.io").resource("validatingwebhookconfigurations").name("my-webhook.example.com").check("breakglass").allowed()'
+```
 
 Match conditions have access to the following CEL variables:
 
diff --git a/content/en/docs/reference/access-authn-authz/validating-admission-policy.md b/content/en/docs/reference/access-authn-authz/validating-admission-policy.md
index ffb7f96965c..a9c802b6058 100644
--- a/content/en/docs/reference/access-authn-authz/validating-admission-policy.md
+++ b/content/en/docs/reference/access-authn-authz/validating-admission-policy.md
@@ -438,7 +438,20 @@ For example, here is an admission policy with an audit annotation:
 
 When an API request is validated with this admission policy, the resulting audit event will look like:
 
-{{< codenew file="access/audit-event-with-audit-annotation.yaml" >}}
+```
+# the audit event recorded
+{
+    "kind": "Event",
+    "apiVersion": "audit.k8s.io/v1",
+    "annotations": {
+        "demo-policy.example.com/high-replica-count": "Deployment spec.replicas set to 128"
+        # other annotations
+        ...
+    }
+    # other fields
+    ...
+}
+```
 
 In this example the annotation will only be included if the `spec.replicas` of the Deployment is more than
 50, otherwise the CEL expression evalutes to null and the annotation will not be included.
@@ -564,4 +577,4 @@ Type Checking has the following limitation:
   to consume excessive computing resources. In the order of ascending group, version, and then resource, 11th combination and beyond are ignored.
 - Type Checking does not affect the policy behavior in any way. Even if the type checking detects errors, the policy will continue
   to evaluate. If errors do occur during evaluate, the failure policy will decide its outcome.
-- Type Checking does not apply to CRDs, including matched CRD types and reference of paramKind. The support for CRDs will come in future release.
\ No newline at end of file
+- Type Checking does not apply to CRDs, including matched CRD types and reference of paramKind. The support for CRDs will come in future release.
diff --git a/content/en/examples/access/admission-webhook-match-conditions.yaml b/content/en/examples/access/admission-webhook-match-conditions.yaml
deleted file mode 100644
index 96705289a95..00000000000
--- a/content/en/examples/access/admission-webhook-match-conditions.yaml
+++ /dev/null
@@ -1,47 +0,0 @@
-apiVersion: admissionregistration.k8s.io/v1
-kind: ValidatingWebhookConfiguration
-webhooks:
-- name: my-webhook.example.com
-  matchPolicy: Equivalent
-  rules:
-  - operations: ['CREATE','UPDATE']
-    apiGroups: ['*']
-    apiVersions: ['*']
-    resources: ['*']
-  failurePolicy: 'Ignore' # Fail-open (optional)
-  sideEffects: None
-  clientConfig:
-    service:
-      namespace: my-namespace
-      name: my-webhook
-    caBundle: '<omitted>'
-  matchConditions:
-  - name: 'exclude-leases' # Each match condition must have a unique name
-    expression: '!(request.resource.group == "coordination.k8s.io" && request.resource.resource == "leases")' # Match non-lease resources.
-  - name: 'exclude-kubelet-requests'
-    expression: '!("system:nodes" in request.userInfo.groups)' # Match requests made by non-node users.
-  - name: 'rbac' # Skip RBAC requests, which are handled by the second webhook.
-    expression: 'request.resource.group != "rbac.authorization.k8s.io"'
-
-# This example illustrates the use of the 'authorizer'. The authorization check is more expensive
-# than a simple expression, so in this example it is scoped to only RBAC requests by using a second
-# webhook. Both webhooks can be served by the same endpoint.
-- name: rbac.my-webhook.example.com
-  matchPolicy: Equivalent
-  rules:
-  - operations: ['CREATE','UPDATE']
-    apiGroups: ['rbac.authorization.k8s.io']
-    apiVersions: ['*']
-    resources: ['*']
-  failurePolicy: 'Fail' # Fail-closed (the default)
-  sideEffects: None
-  clientConfig:
-    service:
-      namespace: my-namespace
-      name: my-webhook
-    caBundle: '<omitted>'
-  matchConditions:
-  - name: 'breakglass'
-    # Skip requests made by users authorized to 'breakglass' on this webhook.
-    # The 'breakglass' API verb does not need to exist outside this check.
-    expression: '!authorizer.group("admissionregistration.k8s.io").resource("validatingwebhookconfigurations").name("my-webhook.example.com").check("breakglass").allowed()'
diff --git a/content/en/examples/access/audit-event-with-audit-annotation.yaml b/content/en/examples/access/audit-event-with-audit-annotation.yaml
deleted file mode 100644
index 6d947745d4b..00000000000
--- a/content/en/examples/access/audit-event-with-audit-annotation.yaml
+++ /dev/null
@@ -1,12 +0,0 @@
-# the audit event recorded
-{
-    "kind": "Event",
-    "apiVersion": "audit.k8s.io/v1",
-    "annotations": {
-        "demo-policy.example.com/high-replica-count": "Deployment spec.replicas set to 128"
-        # other annotations
-        ...
-    }
-    # other fields
-    ...
-}
diff --git a/content/en/examples/access/deployment-replicas-policy.yaml b/content/en/examples/access/deployment-replicas-policy.yaml
index 23c04fff621..e12a8a0961f 100644
--- a/content/en/examples/access/deployment-replicas-policy.yaml
+++ b/content/en/examples/access/deployment-replicas-policy.yaml
@@ -4,9 +4,8 @@ metadata:
   name: "deploy-replica-policy.example.com"
 spec:
   paramKind:
-    group: rules.example.com
+    apiVersion: rules.example.com/v1
     kind: ReplicaLimit
-    version: v1
   matchConstraints:
     resourceRules:
     - apiGroups:   ["apps"]
diff --git a/content/en/examples/access/validating-admission-policy-audit-annotation.yaml b/content/en/examples/access/validating-admission-policy-audit-annotation.yaml
index 378fa97247a..5a7a20ac56a 100644
--- a/content/en/examples/access/validating-admission-policy-audit-annotation.yaml
+++ b/content/en/examples/access/validating-admission-policy-audit-annotation.yaml
@@ -12,4 +12,5 @@ spec:
       resources:   ["deployments"]
   validations:
     - key: "high-replica-count"
-      valueExpression: "object.spec.replicas > 50 ? 'Deployment spec.replicas set to ' + string(object.spec.replicas) : null"
+      expression: "object.spec.replicas > 50"
+      messageExpression: "'Deployment spec.replicas set to ' + string(object.spec.replicas)"
diff --git a/content/en/examples/examples_test.go b/content/en/examples/examples_test.go
index 82c2fdc14aa..4bc95fadcd3 100644
--- a/content/en/examples/examples_test.go
+++ b/content/en/examples/examples_test.go
@@ -34,6 +34,9 @@ import (
 	"k8s.io/apimachinery/pkg/util/yaml"
 	"k8s.io/kubernetes/pkg/api/legacyscheme"
 
+	"k8s.io/kubernetes/pkg/apis/admissionregistration"
+	admreg_validation "k8s.io/kubernetes/pkg/apis/admissionregistration/validation"
+
 	"k8s.io/kubernetes/pkg/apis/apps"
 	apps_validation "k8s.io/kubernetes/pkg/apis/apps/validation"
 
@@ -65,6 +68,7 @@ import (
 	"k8s.io/kubernetes/pkg/registry/batch/job"
 
 	// initialize install packages
+	_ "k8s.io/kubernetes/pkg/apis/admissionregistration/install"
 	_ "k8s.io/kubernetes/pkg/apis/apps/install"
 	_ "k8s.io/kubernetes/pkg/apis/autoscaling/install"
 	_ "k8s.io/kubernetes/pkg/apis/batch/install"
@@ -102,6 +106,7 @@ func (g TestGroup) Codec() runtime.Codec {
 func initGroups() {
 	Groups = make(map[string]TestGroup)
 	groupNames := []string{
+		admissionregistration.GroupName,
 		api.GroupName,
 		apps.GroupName,
 		autoscaling.GroupName,
@@ -152,7 +157,6 @@ func getCodecForObject(obj runtime.Object) (runtime.Codec, error) {
 
 func validateObject(obj runtime.Object) (errors field.ErrorList) {
 	podValidationOptions := validation.PodValidationOptions{
-		AllowDownwardAPIHugePages:       true,
 		AllowInvalidPodDeletionCost:     false,
 		AllowIndivisibleHugePagesValues: true,
 		AllowExpandedDNSConfig:          true,
@@ -170,6 +174,10 @@ func validateObject(obj runtime.Object) (errors field.ErrorList) {
 	// Enable CustomPodDNS for testing
 	// feature.DefaultFeatureGate.Set("CustomPodDNS=true")
 	switch t := obj.(type) {
+	case *admissionregistration.ValidatingWebhookConfiguration:
+		errors = admreg_validation.ValidateValidatingWebhookConfiguration(t)
+	case *admissionregistration.ValidatingAdmissionPolicy:
+		errors = admreg_validation.ValidateValidatingAdmissionPolicy(t)
 	case *api.ConfigMap:
 		if t.Namespace == "" {
 			t.Namespace = api.NamespaceDefault
@@ -390,7 +398,10 @@ func TestExampleObjectSchemas(t *testing.T) {
 	// Please help maintain the alphabeta order in the map
 	cases := map[string]map[string][]runtime.Object{
 		"access": {
-			"endpoints-aggregated": {&rbac.ClusterRole{}},
+			"deployment-replicas-policy":                   {&admissionregistration.ValidatingAdmissionPolicy{}},
+			"endpoints-aggregated":                         {&rbac.ClusterRole{}},
+			"validating-admission-policy-audit-annotation": {&admissionregistration.ValidatingAdmissionPolicy{}},
+			"validating-admission-policy-match-conditions": {&admissionregistration.ValidatingAdmissionPolicy{}},
 		},
 		"access/certificate-signing-request": {
 			"clusterrole-approve": {&rbac.ClusterRole{}},
@@ -544,20 +555,21 @@ func TestExampleObjectSchemas(t *testing.T) {
 			"configure-pod":       {&api.Pod{}},
 		},
 		"controllers": {
-			"daemonset":                      {&apps.DaemonSet{}},
-			"fluentd-daemonset":              {&apps.DaemonSet{}},
-			"fluentd-daemonset-update":       {&apps.DaemonSet{}},
-			"frontend":                       {&apps.ReplicaSet{}},
-			"hpa-rs":                         {&autoscaling.HorizontalPodAutoscaler{}},
-			"job":                            {&batch.Job{}},
-			"job-pod-failure-policy-example": {&batch.Job{}},
-			"job-pod-failure-policy-failjob": {&batch.Job{}},
-			"job-pod-failure-policy-ignore":  {&batch.Job{}},
-			"replicaset":                     {&apps.ReplicaSet{}},
-			"replication":                    {&api.ReplicationController{}},
-			"replication-nginx-1.14.2":       {&api.ReplicationController{}},
-			"replication-nginx-1.16.1":       {&api.ReplicationController{}},
-			"nginx-deployment":               {&apps.Deployment{}},
+			"daemonset":                           {&apps.DaemonSet{}},
+			"fluentd-daemonset":                   {&apps.DaemonSet{}},
+			"fluentd-daemonset-update":            {&apps.DaemonSet{}},
+			"frontend":                            {&apps.ReplicaSet{}},
+			"hpa-rs":                              {&autoscaling.HorizontalPodAutoscaler{}},
+			"job":                                 {&batch.Job{}},
+			"job-pod-failure-policy-config-issue": {&batch.Job{}},
+			"job-pod-failure-policy-example":      {&batch.Job{}},
+			"job-pod-failure-policy-failjob":      {&batch.Job{}},
+			"job-pod-failure-policy-ignore":       {&batch.Job{}},
+			"replicaset":                          {&apps.ReplicaSet{}},
+			"replication":                         {&api.ReplicationController{}},
+			"replication-nginx-1.14.2":            {&api.ReplicationController{}},
+			"replication-nginx-1.16.1":            {&api.ReplicationController{}},
+			"nginx-deployment":                    {&apps.Deployment{}},
 		},
 		"debug": {
 			"counter-pod":                     {&api.Pod{}},
@@ -627,6 +639,7 @@ func TestExampleObjectSchemas(t *testing.T) {
 			"qos-pod-2": {&api.Pod{}},
 			"qos-pod-3": {&api.Pod{}},
 			"qos-pod-4": {&api.Pod{}},
+			"qos-pod-5": {&api.Pod{}},
 		},
 		"pods/resource": {
 			"cpu-request-limit":       {&api.Pod{}},
@@ -678,13 +691,15 @@ func TestExampleObjectSchemas(t *testing.T) {
 			"mysecretname": {&api.Secret{}},
 		},
 		"security": {
+			"example-baseline-pod":   {&api.Pod{}},
 			"podsecurity-baseline":   {&api.Namespace{}},
 			"podsecurity-privileged": {&api.Namespace{}},
 			"podsecurity-restricted": {&api.Namespace{}},
 		},
 		"service": {
-			"nginx-service":         {&api.Service{}},
-			"load-balancer-example": {&apps.Deployment{}},
+			"nginx-service":                 {&api.Service{}},
+			"load-balancer-example":         {&apps.Deployment{}},
+			"pod-with-graceful-termination": {&apps.Deployment{}},
 		},
 		"service/access": {
 			"backend-deployment":  {&apps.Deployment{}},
diff --git a/go.mod b/go.mod
index c84a9c62aa0..23d361595c5 100644
--- a/go.mod
+++ b/go.mod
@@ -1,55 +1,68 @@
 module k8s.io/website
 
-go 1.19
+go 1.20
 
 require (
-	k8s.io/apimachinery v0.26.0
+	k8s.io/apimachinery v0.27.0
 	k8s.io/kubernetes v0.0.0
 )
 
 require (
+	github.com/NYTimes/gziphandler v1.1.1 // indirect
+	github.com/antlr/antlr4/runtime/Go/antlr v1.4.10 // indirect
+	github.com/asaskevich/govalidator v0.0.0-20190424111038-f61b66f89f4a // indirect
 	github.com/beorn7/perks v1.0.1 // indirect
 	github.com/blang/semver/v4 v4.0.0 // indirect
 	github.com/cenkalti/backoff/v4 v4.1.3 // indirect
 	github.com/cespare/xxhash/v2 v2.1.2 // indirect
 	github.com/coreos/go-semver v0.3.0 // indirect
-	github.com/coreos/go-systemd/v22 v22.3.2 // indirect
+	github.com/coreos/go-systemd/v22 v22.4.0 // indirect
 	github.com/davecgh/go-spew v1.1.1 // indirect
 	github.com/docker/distribution v2.8.1+incompatible // indirect
 	github.com/emicklei/go-restful/v3 v3.9.0 // indirect
+	github.com/evanphx/json-patch v4.12.0+incompatible // indirect
 	github.com/felixge/httpsnoop v1.0.3 // indirect
+	github.com/fsnotify/fsnotify v1.6.0 // indirect
 	github.com/go-logr/logr v1.2.3 // indirect
 	github.com/go-logr/stdr v1.2.2 // indirect
-	github.com/go-openapi/jsonpointer v0.19.5 // indirect
-	github.com/go-openapi/jsonreference v0.20.0 // indirect
-	github.com/go-openapi/swag v0.19.14 // indirect
+	github.com/go-openapi/jsonpointer v0.19.6 // indirect
+	github.com/go-openapi/jsonreference v0.20.1 // indirect
+	github.com/go-openapi/swag v0.22.3 // indirect
 	github.com/gogo/protobuf v1.3.2 // indirect
-	github.com/golang/protobuf v1.5.2 // indirect
+	github.com/golang/groupcache v0.0.0-20210331224755-41bb18bfe9da // indirect
+	github.com/golang/protobuf v1.5.3 // indirect
+	github.com/google/cel-go v0.12.6 // indirect
 	github.com/google/gnostic v0.5.7-v3refs // indirect
 	github.com/google/go-cmp v0.5.9 // indirect
 	github.com/google/gofuzz v1.1.0 // indirect
-	github.com/google/uuid v1.1.2 // indirect
+	github.com/google/uuid v1.3.0 // indirect
 	github.com/grpc-ecosystem/go-grpc-prometheus v1.2.0 // indirect
 	github.com/grpc-ecosystem/grpc-gateway/v2 v2.7.0 // indirect
+	github.com/imdario/mergo v0.3.6 // indirect
+	github.com/inconshreveable/mousetrap v1.0.1 // indirect
 	github.com/josharian/intern v1.0.0 // indirect
 	github.com/json-iterator/go v1.1.12 // indirect
-	github.com/mailru/easyjson v0.7.6 // indirect
+	github.com/mailru/easyjson v0.7.7 // indirect
 	github.com/matttproud/golang_protobuf_extensions v1.0.2 // indirect
+	github.com/mitchellh/mapstructure v1.4.1 // indirect
 	github.com/modern-go/concurrent v0.0.0-20180306012644-bacd9c7ef1dd // indirect
 	github.com/modern-go/reflect2 v1.0.2 // indirect
 	github.com/munnerz/goautoneg v0.0.0-20191010083416-a7dc8b61c822 // indirect
 	github.com/opencontainers/go-digest v1.0.0 // indirect
+	github.com/pkg/errors v0.9.1 // indirect
 	github.com/prometheus/client_golang v1.14.0 // indirect
 	github.com/prometheus/client_model v0.3.0 // indirect
 	github.com/prometheus/common v0.37.0 // indirect
 	github.com/prometheus/procfs v0.8.0 // indirect
 	github.com/robfig/cron/v3 v3.0.1 // indirect
+	github.com/spf13/cobra v1.6.0 // indirect
 	github.com/spf13/pflag v1.0.5 // indirect
-	go.etcd.io/etcd/api/v3 v3.5.5 // indirect
-	go.etcd.io/etcd/client/pkg/v3 v3.5.5 // indirect
-	go.etcd.io/etcd/client/v3 v3.5.5 // indirect
+	github.com/stoewer/go-strcase v1.2.0 // indirect
+	go.etcd.io/etcd/api/v3 v3.5.7 // indirect
+	go.etcd.io/etcd/client/pkg/v3 v3.5.7 // indirect
+	go.etcd.io/etcd/client/v3 v3.5.7 // indirect
 	go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.35.0 // indirect
-	go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.35.0 // indirect
+	go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.35.1 // indirect
 	go.opentelemetry.io/otel v1.10.0 // indirect
 	go.opentelemetry.io/otel/exporters/otlp/internal/retry v1.10.0 // indirect
 	go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.10.0 // indirect
@@ -61,60 +74,67 @@ require (
 	go.uber.org/atomic v1.7.0 // indirect
 	go.uber.org/multierr v1.6.0 // indirect
 	go.uber.org/zap v1.19.0 // indirect
-	golang.org/x/net v0.3.1-0.20221206200815-1e63c2f08a10 // indirect
+	golang.org/x/crypto v0.1.0 // indirect
+	golang.org/x/net v0.8.0 // indirect
 	golang.org/x/oauth2 v0.0.0-20220223155221-ee480838109b // indirect
-	golang.org/x/sys v0.3.0 // indirect
-	golang.org/x/term v0.3.0 // indirect
-	golang.org/x/text v0.5.0 // indirect
+	golang.org/x/sync v0.1.0 // indirect
+	golang.org/x/sys v0.6.0 // indirect
+	golang.org/x/term v0.6.0 // indirect
+	golang.org/x/text v0.8.0 // indirect
 	golang.org/x/time v0.0.0-20220210224613-90d013bbcef8 // indirect
 	google.golang.org/appengine v1.6.7 // indirect
 	google.golang.org/genproto v0.0.0-20220502173005-c8bf987b8c21 // indirect
-	google.golang.org/grpc v1.49.0 // indirect
+	google.golang.org/grpc v1.51.0 // indirect
 	google.golang.org/protobuf v1.28.1 // indirect
 	gopkg.in/inf.v0 v0.9.1 // indirect
+	gopkg.in/natefinch/lumberjack.v2 v2.0.0 // indirect
 	gopkg.in/yaml.v2 v2.4.0 // indirect
 	gopkg.in/yaml.v3 v3.0.1 // indirect
-	k8s.io/api v0.26.0 // indirect
-	k8s.io/apiserver v0.0.0 // indirect
-	k8s.io/client-go v0.26.0 // indirect
-	k8s.io/component-base v0.26.0 // indirect
-	k8s.io/component-helpers v0.0.0 // indirect
-	k8s.io/klog/v2 v2.80.1 // indirect
-	k8s.io/kube-openapi v0.0.0-20221012153701-172d655c2280 // indirect
-	k8s.io/utils v0.0.0-20221107191617-1a15be271d1d // indirect
-	sigs.k8s.io/apiserver-network-proxy/konnectivity-client v0.0.33 // indirect
-	sigs.k8s.io/json v0.0.0-20220713155537-f223a00ba0e2 // indirect
+	k8s.io/api v0.27.0 // indirect
+	k8s.io/apiserver v0.27.0 // indirect
+	k8s.io/client-go v0.27.0 // indirect
+	k8s.io/cloud-provider v0.0.0 // indirect
+	k8s.io/component-base v0.27.0 // indirect
+	k8s.io/component-helpers v0.27.0 // indirect
+	k8s.io/controller-manager v0.27.0 // indirect
+	k8s.io/klog/v2 v2.90.1 // indirect
+	k8s.io/kms v0.27.0 // indirect
+	k8s.io/kube-openapi v0.0.0-20230308215209-15aac26d736a // indirect
+	k8s.io/kubelet v0.0.0 // indirect
+	k8s.io/utils v0.0.0-20230209194617-a36077c30491 // indirect
+	sigs.k8s.io/apiserver-network-proxy/konnectivity-client v0.1.1 // indirect
+	sigs.k8s.io/json v0.0.0-20221116044647-bc3834ca7abd // indirect
 	sigs.k8s.io/structured-merge-diff/v4 v4.2.3 // indirect
 	sigs.k8s.io/yaml v1.3.0 // indirect
 )
 
 replace (
-	k8s.io/api => k8s.io/api v0.26.0
-	k8s.io/apiextensions-apiserver => k8s.io/apiextensions-apiserver v0.26.0
-	k8s.io/apimachinery => k8s.io/apimachinery v0.26.0
-	k8s.io/apiserver => k8s.io/apiserver v0.26.0
-	k8s.io/cli-runtime => k8s.io/cli-runtime v0.26.0
-	k8s.io/client-go => k8s.io/client-go v0.26.0
-	k8s.io/cloud-provider => k8s.io/cloud-provider v0.26.0
-	k8s.io/cluster-bootstrap => k8s.io/cluster-bootstrap v0.26.0
-	k8s.io/code-generator => k8s.io/code-generator v0.26.0
-	k8s.io/component-base => k8s.io/component-base v0.26.0
-	k8s.io/component-helpers => k8s.io/component-helpers v0.26.0
-	k8s.io/controller-manager => k8s.io/controller-manager v0.26.0
-	k8s.io/cri-api => k8s.io/cri-api v0.26.0
-	k8s.io/csi-translation-lib => k8s.io/csi-translation-lib v0.26.0
-	k8s.io/kube-aggregator => k8s.io/kube-aggregator v0.26.0
-	k8s.io/kube-controller-manager => k8s.io/kube-controller-manager v0.26.0
-	k8s.io/kube-proxy => k8s.io/kube-proxy v0.26.0
-	k8s.io/kube-scheduler => k8s.io/kube-scheduler v0.26.0
-	k8s.io/kubectl => k8s.io/kubectl v0.26.0
-	k8s.io/kubelet => k8s.io/kubelet v0.26.0
+	k8s.io/api => k8s.io/api v0.27.0
+	k8s.io/apiextensions-apiserver => k8s.io/apiextensions-apiserver v0.27.0
+	k8s.io/apimachinery => k8s.io/apimachinery v0.27.0
+	k8s.io/apiserver => k8s.io/apiserver v0.27.0
+	k8s.io/cli-runtime => k8s.io/cli-runtime v0.27.0
+	k8s.io/client-go => k8s.io/client-go v0.27.0
+	k8s.io/cloud-provider => k8s.io/cloud-provider v0.27.0
+	k8s.io/cluster-bootstrap => k8s.io/cluster-bootstrap v0.27.0
+	k8s.io/code-generator => k8s.io/code-generator v0.27.0
+	k8s.io/component-base => k8s.io/component-base v0.27.0
+	k8s.io/component-helpers => k8s.io/component-helpers v0.27.0
+	k8s.io/controller-manager => k8s.io/controller-manager v0.27.0
+	k8s.io/cri-api => k8s.io/cri-api v0.27.0
+	k8s.io/csi-translation-lib => k8s.io/csi-translation-lib v0.27.0
+	k8s.io/kube-aggregator => k8s.io/kube-aggregator v0.27.0
+	k8s.io/kube-controller-manager => k8s.io/kube-controller-manager v0.27.0
+	k8s.io/kube-proxy => k8s.io/kube-proxy v0.27.0
+	k8s.io/kube-scheduler => k8s.io/kube-scheduler v0.27.0
+	k8s.io/kubectl => k8s.io/kubectl v0.27.0
+	k8s.io/kubelet => k8s.io/kubelet v0.27.0
 	k8s.io/kubernetes => ../kubernetes
-	k8s.io/legacy-cloud-providers => k8s.io/legacy-cloud-providers v0.26.0
-	k8s.io/metrics => k8s.io/metrics v0.26.0
-	k8s.io/mount-utils => k8s.io/mount-utils v0.26.0
-	k8s.io/pod-security-admission => k8s.io/pod-security-admission v0.26.0
-	k8s.io/sample-apiserver => k8s.io/sample-apiserver v0.26.0
-	k8s.io/sample-cli-plugin => k8s.io/sample-cli-plugin v0.26.0
-	k8s.io/sample-controller => k8s.io/sample-controller v0.26.0
+	k8s.io/legacy-cloud-providers => k8s.io/legacy-cloud-providers v0.27.0
+	k8s.io/metrics => k8s.io/metrics v0.27.0
+	k8s.io/mount-utils => k8s.io/mount-utils v0.27.0
+	k8s.io/pod-security-admission => k8s.io/pod-security-admission v0.27.0
+	k8s.io/sample-apiserver => k8s.io/sample-apiserver v0.27.0
+	k8s.io/sample-cli-plugin => k8s.io/sample-cli-plugin v0.27.0
+	k8s.io/sample-controller => k8s.io/sample-controller v0.27.0
 )
diff --git a/go.sum b/go.sum
index 9d1140f1e7e..013dc6455fc 100644
--- a/go.sum
+++ b/go.sum
@@ -32,8 +32,11 @@ cloud.google.com/go/storage v1.6.0/go.mod h1:N7U0C8pVQ/+NIKOBQyamJIeKQKkZ+mxpohl
 cloud.google.com/go/storage v1.8.0/go.mod h1:Wv1Oy7z6Yz3DshWRJFhqM/UCfaWIRTdp0RXyy7KQOVs=
 cloud.google.com/go/storage v1.10.0/go.mod h1:FLPqc6j+Ki4BU591ie1oL6qBQGu2Bl/tZ9ullr3+Kg0=
 dmitri.shuralyov.com/gpu/mtl v0.0.0-20190408044501-666a987793e9/go.mod h1:H6x//7gZCb22OMCxBHrMx7a5I7Hp++hsVxbQ4BYO7hU=
+github.com/BurntSushi/toml v0.3.1 h1:WXkYYl6Yr3qBf1K79EBnL4mak0OimBfB0XUf9Vl28OQ=
 github.com/BurntSushi/toml v0.3.1/go.mod h1:xHWCNGjB5oqiDr8zfno3MHue2Ht5sIBksp03qcyfWMU=
 github.com/BurntSushi/xgb v0.0.0-20160522181843-27f122750802/go.mod h1:IVnqGOEym/WlBOVXweHU+Q+/VP0lqqI8lqeDx9IjBqo=
+github.com/NYTimes/gziphandler v1.1.1 h1:ZUDjpQae29j0ryrS0u/B8HZfJBtBQHjqw2rQ2cqUQ3I=
+github.com/NYTimes/gziphandler v1.1.1/go.mod h1:n/CVRwUEOgIxrgPvAQhUUr9oeUtvrhMomdKFjzJNB0c=
 github.com/OneOfOne/xxhash v1.2.2/go.mod h1:HSdplMjZKSmBqAxg5vPj2TmRDmfkzw+cTzAElWljhcU=
 github.com/alecthomas/template v0.0.0-20160405071501-a0175ee3bccc/go.mod h1:LOuyumcjzFXgccqObfd/Ljyb9UuFJ6TxHnclSeseNhc=
 github.com/alecthomas/template v0.0.0-20190718012654-fb15b899a751/go.mod h1:LOuyumcjzFXgccqObfd/Ljyb9UuFJ6TxHnclSeseNhc=
@@ -41,6 +44,10 @@ github.com/alecthomas/units v0.0.0-20151022065526-2efee857e7cf/go.mod h1:ybxpYRF
 github.com/alecthomas/units v0.0.0-20190717042225-c3de453c63f4/go.mod h1:ybxpYRFXyAe+OPACYpWeL0wqObRcbAqCMya13uyzqw0=
 github.com/alecthomas/units v0.0.0-20190924025748-f65c72e2690d/go.mod h1:rBZYJk541a8SKzHPHnH3zbiI+7dagKZ0cgpgrD7Fyho=
 github.com/antihax/optional v1.0.0/go.mod h1:uupD/76wgC+ih3iEmQUL+0Ugr19nfwCT1kdvxnR2qWY=
+github.com/antlr/antlr4/runtime/Go/antlr v1.4.10 h1:yL7+Jz0jTC6yykIK/Wh74gnTJnrGr5AyrNMXuA0gves=
+github.com/antlr/antlr4/runtime/Go/antlr v1.4.10/go.mod h1:F7bn7fEU90QkQ3tnmaTx3LTKLEDqnwWODIYppRQ5hnY=
+github.com/asaskevich/govalidator v0.0.0-20190424111038-f61b66f89f4a h1:idn718Q4B6AGu/h5Sxe66HYVdqdGu2l9Iebqhi/AEoA=
+github.com/asaskevich/govalidator v0.0.0-20190424111038-f61b66f89f4a/go.mod h1:lB+ZfQJz7igIIfQNfa7Ml4HSf2uFQQRzpGGRXenZAgY=
 github.com/benbjohnson/clock v1.1.0 h1:Q92kusRqC1XV2MjkWETPvjJVqKetz1OzxZB7mHJLju8=
 github.com/benbjohnson/clock v1.1.0/go.mod h1:J11/hYXuz8f4ySSvYwY0FKfm+ezbsZBKZxNJlLklBHA=
 github.com/beorn7/perks v0.0.0-20180321164747-3a771d992973/go.mod h1:Dwedo/Wpr24TaqPxmxbtue+5NUziq4I4S80YR8gNf3Q=
@@ -70,8 +77,9 @@ github.com/cncf/xds/go v0.0.0-20211001041855-01bcc9b48dfe/go.mod h1:eXthEFrGJvWH
 github.com/cncf/xds/go v0.0.0-20211011173535-cb28da3451f1/go.mod h1:eXthEFrGJvWHgFFCl3hGmgk+/aYT6PnTQLykKQRLhEs=
 github.com/coreos/go-semver v0.3.0 h1:wkHLiw0WNATZnSG7epLsujiMCgPAc9xhjJ4tgnAxmfM=
 github.com/coreos/go-semver v0.3.0/go.mod h1:nnelYz7RCh+5ahJtPPxZlU+153eP4D4r3EedlOD2RNk=
-github.com/coreos/go-systemd/v22 v22.3.2 h1:D9/bQk5vlXQFZ6Kwuu6zaiXJ9oTPe68++AzAJc1DzSI=
-github.com/coreos/go-systemd/v22 v22.3.2/go.mod h1:Y58oyj3AT4RCenI/lSvhwexgC+NSVTIJ3seZv2GcEnc=
+github.com/coreos/go-systemd/v22 v22.4.0 h1:y9YHcjnjynCd/DVbg5j9L/33jQM3MxJlbj/zWskzfGU=
+github.com/coreos/go-systemd/v22 v22.4.0/go.mod h1:Y58oyj3AT4RCenI/lSvhwexgC+NSVTIJ3seZv2GcEnc=
+github.com/cpuguy83/go-md2man/v2 v2.0.2/go.mod h1:tgQtvFlXSQOSOSIRvRPT7W67SCa46tRHOmNcaadrF8o=
 github.com/creack/pty v1.1.9/go.mod h1:oKZEueFk5CKHvIhNR5MUki03XCEU+Q6VDXinZuGJ33E=
 github.com/davecgh/go-spew v1.1.0/go.mod h1:J7Y8YcW2NihsgmVo/mv3lAwl/skON4iLHjSsI+c5H38=
 github.com/davecgh/go-spew v1.1.1 h1:vj9j/u1bqnvCEfJOwUhtlOARqs3+rkHYY13jYWTU97c=
@@ -80,22 +88,22 @@ github.com/docker/distribution v2.8.1+incompatible h1:Q50tZOPR6T/hjNsyc9g8/syEs6
 github.com/docker/distribution v2.8.1+incompatible/go.mod h1:J2gT2udsDAN96Uj4KfcMRqY0/ypR+oyYUYmja8H+y+w=
 github.com/docopt/docopt-go v0.0.0-20180111231733-ee0de3bc6815/go.mod h1:WwZ+bS3ebgob9U8Nd0kOddGdZWjyMGR8Wziv+TBNwSE=
 github.com/dustin/go-humanize v1.0.0 h1:VSnTsYCnlFHaM2/igO1h6X3HA71jcobQuxemgkq4zYo=
-github.com/dustin/go-humanize v1.0.0/go.mod h1:HtrtbFcZ19U5GC7JDqmcUSB87Iq5E25KnS6fMYU6eOk=
 github.com/emicklei/go-restful/v3 v3.9.0 h1:XwGDlfxEnQZzuopoqxwSEllNcCOM9DhhFyhFIIGKwxE=
 github.com/emicklei/go-restful/v3 v3.9.0/go.mod h1:6n3XBCmQQb25CM2LCACGz8ukIrRry+4bhvbpWn3mrbc=
 github.com/envoyproxy/go-control-plane v0.9.0/go.mod h1:YTl/9mNaCwkRvm6d1a2C3ymFceY/DCBVvsKhRF0iEA4=
 github.com/envoyproxy/go-control-plane v0.9.1-0.20191026205805-5f8ba28d4473/go.mod h1:YTl/9mNaCwkRvm6d1a2C3ymFceY/DCBVvsKhRF0iEA4=
 github.com/envoyproxy/go-control-plane v0.9.4/go.mod h1:6rpuAdCZL397s3pYoYcLgu1mIlRU8Am5FuJP05cCM98=
 github.com/envoyproxy/go-control-plane v0.9.9-0.20201210154907-fd9021fe5dad/go.mod h1:cXg6YxExXjJnVBQHBLXeUAgxn2UodCpnH306RInaBQk=
-github.com/envoyproxy/go-control-plane v0.9.9-0.20210217033140-668b12f5399d/go.mod h1:cXg6YxExXjJnVBQHBLXeUAgxn2UodCpnH306RInaBQk=
 github.com/envoyproxy/go-control-plane v0.9.9-0.20210512163311-63b5d3c536b0/go.mod h1:hliV/p42l8fGbc6Y9bQ70uLwIvmJyVE5k4iMKlh8wCQ=
 github.com/envoyproxy/go-control-plane v0.9.10-0.20210907150352-cf90f659a021/go.mod h1:AFq3mo9L8Lqqiid3OhADV3RfLJnjiw63cSpi+fDTRC0=
 github.com/envoyproxy/go-control-plane v0.10.2-0.20220325020618-49ff273808a1/go.mod h1:KJwIaB5Mv44NWtYuAOFCVOjcI94vtpEz2JU/D2v6IjE=
 github.com/envoyproxy/protoc-gen-validate v0.1.0/go.mod h1:iSmxcyjqTsJpI2R4NaDN7+kN2VEUnK/pcBlmesArF7c=
 github.com/evanphx/json-patch v4.12.0+incompatible h1:4onqiflcdA9EOZ4RxV643DvftH5pOlLGNtQ5lPWQu84=
+github.com/evanphx/json-patch v4.12.0+incompatible/go.mod h1:50XU6AFN0ol/bzJsmQLiYLvXMP4fmwYFNcr97nuDLSk=
 github.com/felixge/httpsnoop v1.0.3 h1:s/nj+GCswXYzN5v2DpNMuMQYe+0DDwt5WVCU6CWBdXk=
 github.com/felixge/httpsnoop v1.0.3/go.mod h1:m8KPJKqk1gH5J9DgRY2ASl2lWCfGKXixSwevea8zH2U=
-github.com/form3tech-oss/jwt-go v3.2.3+incompatible h1:7ZaBxOI7TMoYBfyA3cQHErNNyAWIKUMIwqxEtgHOs5c=
+github.com/fsnotify/fsnotify v1.6.0 h1:n+5WquG0fcWoWp6xPWfHdbskMCQaFnG6PfBrh1Ky4HY=
+github.com/fsnotify/fsnotify v1.6.0/go.mod h1:sl3t1tCWJFWoRz9R8WJCbQihKKwmorjAbSClcnxKAGw=
 github.com/ghodss/yaml v1.0.0/go.mod h1:4dBDuWmgqj2HViK6kFavaiC9ZROes6MMH2rRYeMEF04=
 github.com/go-gl/glfw v0.0.0-20190409004039-e6da0acd62b1/go.mod h1:vR7hzQXu2zJy9AVAgeJqvqgH9Q5CA+iKCZ2gyEVpxRU=
 github.com/go-gl/glfw/v3.3/glfw v0.0.0-20191125211704-12ad95a8df72/go.mod h1:tQ2UAYgL5IevRw8kRxooKSPJfGvJ9fJQFa0TUsXzTg8=
@@ -114,25 +122,28 @@ github.com/go-logr/logr v1.2.3 h1:2DntVwHkVopvECVRSlL5PSo9eG+cAkDCuckLubN+rq0=
 github.com/go-logr/logr v1.2.3/go.mod h1:jdQByPbusPIv2/zmleS9BjJVeZ6kBagPoEUsqbVz/1A=
 github.com/go-logr/stdr v1.2.2 h1:hSWxHoqTgW2S2qGc0LTAI563KZ5YKYRhT3MFKZMbjag=
 github.com/go-logr/stdr v1.2.2/go.mod h1:mMo/vtBO5dYbehREoey6XUKy/eSumjCCveDpRre4VKE=
-github.com/go-openapi/jsonpointer v0.19.3/go.mod h1:Pl9vOtqEWErmShwVjC8pYs9cog34VGT37dQOVbmoatg=
-github.com/go-openapi/jsonpointer v0.19.5 h1:gZr+CIYByUqjcgeLXnQu2gHYQC9o73G2XUeOFYEICuY=
-github.com/go-openapi/jsonpointer v0.19.5/go.mod h1:Pl9vOtqEWErmShwVjC8pYs9cog34VGT37dQOVbmoatg=
-github.com/go-openapi/jsonreference v0.20.0 h1:MYlu0sBgChmCfJxxUKZ8g1cPWFOB37YSZqewK7OKeyA=
-github.com/go-openapi/jsonreference v0.20.0/go.mod h1:Ag74Ico3lPc+zR+qjn4XBUmXymS4zJbYVCZmcgkasdo=
-github.com/go-openapi/swag v0.19.5/go.mod h1:POnQmlKehdgb5mhVOsnJFsivZCEZ/vjK9gh66Z9tfKk=
-github.com/go-openapi/swag v0.19.14 h1:gm3vOOXfiuw5i9p5N9xJvfjvuofpyvLA9Wr6QfK5Fng=
-github.com/go-openapi/swag v0.19.14/go.mod h1:QYRuS/SOXUCsnplDa677K7+DxSOj6IPNl/eQntq43wQ=
+github.com/go-logr/zapr v1.2.3 h1:a9vnzlIBPQBBkeaR9IuMUfmVOrQlkoC4YfPoFkX3T7A=
+github.com/go-openapi/jsonpointer v0.19.6 h1:eCs3fxoIi3Wh6vtgmLTOjdhSpiqphQ+DaPn38N2ZdrE=
+github.com/go-openapi/jsonpointer v0.19.6/go.mod h1:osyAmYz/mB/C3I+WsTTSgw1ONzaLJoLCyoi6/zppojs=
+github.com/go-openapi/jsonreference v0.20.1 h1:FBLnyygC4/IZZr893oiomc9XaghoveYTrLC1F86HID8=
+github.com/go-openapi/jsonreference v0.20.1/go.mod h1:Bl1zwGIM8/wsvqjsOQLJ/SH+En5Ap4rVB5KVcIDZG2k=
+github.com/go-openapi/swag v0.22.3 h1:yMBqmnQ0gyZvEb/+KzuWZOXgllrXT4SADYbvDaXHv/g=
+github.com/go-openapi/swag v0.22.3/go.mod h1:UzaqsxGiab7freDnrUUra0MwWfN/q7tE4j+VcZ0yl14=
 github.com/go-stack/stack v1.8.0/go.mod h1:v0f6uXyyMGvRgIKkXu+yp6POWl0qKG85gN/melR3HDY=
+github.com/go-task/slim-sprig v0.0.0-20210107165309-348f09dbbbc0 h1:p104kn46Q8WdvHunIJ9dAyjPVtrBPhSr3KT2yUst43I=
 github.com/godbus/dbus/v5 v5.0.4/go.mod h1:xhWf0FNVPg57R7Z0UbKHbJfkEywrmjJnf7w5xrFpKfA=
 github.com/gogo/protobuf v1.1.1/go.mod h1:r8qH/GZQm5c6nD/R0oafs1akxWv10x8SbQlK7atdtwQ=
 github.com/gogo/protobuf v1.3.2 h1:Ov1cvc58UF3b5XjBnZv7+opcTcQFZebYjWzi34vdm4Q=
 github.com/gogo/protobuf v1.3.2/go.mod h1:P1XiOD3dCwIKUDQYPy72D8LYyHL2YPYrpS2s69NZV8Q=
+github.com/golang-jwt/jwt/v4 v4.4.2 h1:rcc4lwaZgFMCZ5jxF9ABolDcIHdBytAFgqFPbSJQAYs=
 github.com/golang/glog v0.0.0-20160126235308-23def4e6c14b/go.mod h1:SBH7ygxi8pfUlaOkMMuAQtPIUF8ecWP5IEl/CR7VP2Q=
 github.com/golang/glog v1.0.0 h1:nfP3RFugxnNRyKgeWd4oI1nYvXpxrx8ck8ZrcizshdQ=
 github.com/golang/glog v1.0.0/go.mod h1:EWib/APOK0SL3dFbYqvxE3UYd8E6s1ouQ7iEp/0LWV4=
 github.com/golang/groupcache v0.0.0-20190702054246-869f871628b6/go.mod h1:cIg4eruTrX1D+g88fzRXU5OdNfaM+9IcxsU14FzY7Hc=
 github.com/golang/groupcache v0.0.0-20191227052852-215e87163ea7/go.mod h1:cIg4eruTrX1D+g88fzRXU5OdNfaM+9IcxsU14FzY7Hc=
 github.com/golang/groupcache v0.0.0-20200121045136-8c9f03a8e57e/go.mod h1:cIg4eruTrX1D+g88fzRXU5OdNfaM+9IcxsU14FzY7Hc=
+github.com/golang/groupcache v0.0.0-20210331224755-41bb18bfe9da h1:oI5xCqsCo564l8iNU+DwB5epxmsaqB+rhGL0m5jtYqE=
+github.com/golang/groupcache v0.0.0-20210331224755-41bb18bfe9da/go.mod h1:cIg4eruTrX1D+g88fzRXU5OdNfaM+9IcxsU14FzY7Hc=
 github.com/golang/mock v1.1.1/go.mod h1:oTYuIxOrZwtPieC+H1uAHpcLFnEyAGVDL/k47Jfbm0A=
 github.com/golang/mock v1.2.0/go.mod h1:oTYuIxOrZwtPieC+H1uAHpcLFnEyAGVDL/k47Jfbm0A=
 github.com/golang/mock v1.3.1/go.mod h1:sBzyDLLjw3U8JLTeZvSv8jJB+tU5PVekmnlKIyFUx0Y=
@@ -155,11 +166,14 @@ github.com/golang/protobuf v1.4.1/go.mod h1:U8fpvMrcmy5pZrNK1lt4xCsGvpyWQ/VVv6QD
 github.com/golang/protobuf v1.4.2/go.mod h1:oDoupMAO8OvCJWAcko0GGGIgR6R6ocIYbsSw735rRwI=
 github.com/golang/protobuf v1.4.3/go.mod h1:oDoupMAO8OvCJWAcko0GGGIgR6R6ocIYbsSw735rRwI=
 github.com/golang/protobuf v1.5.0/go.mod h1:FsONVRAS9T7sI+LIUmWTfcYkHO4aIWwzhcaSAoJOfIk=
-github.com/golang/protobuf v1.5.2 h1:ROPKBNFfQgOUMifHyP+KYbvpjbdoFNs+aK7DXlji0Tw=
 github.com/golang/protobuf v1.5.2/go.mod h1:XVQd3VNwM+JqD3oG2Ue2ip4fOMUkwXdXDdiuN0vRsmY=
+github.com/golang/protobuf v1.5.3 h1:KhyjKVUg7Usr/dYsdSqoFveMYd5ko72D+zANwlG1mmg=
+github.com/golang/protobuf v1.5.3/go.mod h1:XVQd3VNwM+JqD3oG2Ue2ip4fOMUkwXdXDdiuN0vRsmY=
 github.com/google/btree v0.0.0-20180813153112-4030bb1f1f0c/go.mod h1:lNA+9X1NB3Zf8V7Ke586lFgjr2dZNuvo3lPJSGZ5JPQ=
 github.com/google/btree v1.0.0/go.mod h1:lNA+9X1NB3Zf8V7Ke586lFgjr2dZNuvo3lPJSGZ5JPQ=
 github.com/google/btree v1.0.1 h1:gK4Kx5IaGY9CD5sPJ36FHiBJ6ZXl0kilRiiCj+jdYp4=
+github.com/google/cel-go v0.12.6 h1:kjeKudqV0OygrAqA9fX6J55S8gj+Jre2tckIm5RoG4M=
+github.com/google/cel-go v0.12.6/go.mod h1:Jk7ljRzLBhkmiAwBoUxB1sZSCVBAzkqPF25olK/iRDw=
 github.com/google/gnostic v0.5.7-v3refs h1:FhTMOKj2VhjpouxvWJAV1TL304uMlb9zcDqkl6cEI54=
 github.com/google/gnostic v0.5.7-v3refs/go.mod h1:73MKFl6jIHelAJNaBGFzt3SPtZULs9dYrGFt8OiIsHQ=
 github.com/google/go-cmp v0.2.0/go.mod h1:oXzfMopK8JAjlY9xF4vHSVASa0yLyX7SntLO5aqRK0M=
@@ -186,9 +200,11 @@ github.com/google/pprof v0.0.0-20200212024743-f11f1df84d12/go.mod h1:ZgVRPoUq/hf
 github.com/google/pprof v0.0.0-20200229191704-1ebb73c60ed3/go.mod h1:ZgVRPoUq/hfqzAqh7sHMqb3I9Rq5C59dIz2SbBwJ4eM=
 github.com/google/pprof v0.0.0-20200430221834-fc25d7d30c6d/go.mod h1:ZgVRPoUq/hfqzAqh7sHMqb3I9Rq5C59dIz2SbBwJ4eM=
 github.com/google/pprof v0.0.0-20200708004538-1a94d8640e99/go.mod h1:ZgVRPoUq/hfqzAqh7sHMqb3I9Rq5C59dIz2SbBwJ4eM=
+github.com/google/pprof v0.0.0-20210720184732-4bb14d4b1be1 h1:K6RDEckDVWvDI9JAJYCmNdQXq6neHJOYx3V6jnqNEec=
 github.com/google/renameio v0.1.0/go.mod h1:KWCgfxg9yswjAJkECMjeO8J8rahYeXnNhOm40UhjYkI=
-github.com/google/uuid v1.1.2 h1:EVhdT+1Kseyi1/pUmXKaFxYsDNy9RQYkMWRH68J/W7Y=
 github.com/google/uuid v1.1.2/go.mod h1:TIyPZe4MgqvfeYDBFedMoGGpEw/LqOeaOT+nhxU+yHo=
+github.com/google/uuid v1.3.0 h1:t6JiXgmwXMjEs8VusXIJk2BXHsn+wx8BZdTaoZ5fu7I=
+github.com/google/uuid v1.3.0/go.mod h1:TIyPZe4MgqvfeYDBFedMoGGpEw/LqOeaOT+nhxU+yHo=
 github.com/googleapis/gax-go/v2 v2.0.4/go.mod h1:0Wqv26UfaUD9n4G6kQubkQ+KchISgw+vpHVxEJEs9eg=
 github.com/googleapis/gax-go/v2 v2.0.5/go.mod h1:DWXyrwAJ9X0FpwwEdw+IPEYBICEFu5mhpdKc/us6bOk=
 github.com/gorilla/websocket v1.4.2 h1:+/TMaTYc4QFitKJxsQ7Yye35DkWvkdLcvGKqM+x0Ufc=
@@ -202,6 +218,10 @@ github.com/grpc-ecosystem/grpc-gateway/v2 v2.7.0/go.mod h1:hgWBS7lorOAVIJEQMi4Zs
 github.com/hashicorp/golang-lru v0.5.0/go.mod h1:/m3WP610KZHVQ1SGc6re/UDhFvYD7pJ4Ao+sR/qLZy8=
 github.com/hashicorp/golang-lru v0.5.1/go.mod h1:/m3WP610KZHVQ1SGc6re/UDhFvYD7pJ4Ao+sR/qLZy8=
 github.com/ianlancetaylor/demangle v0.0.0-20181102032728-5e5cf60278f6/go.mod h1:aSSvb/t6k1mPoxDqO4vJh6VOCGPwU4O0C2/Eqndh1Sc=
+github.com/imdario/mergo v0.3.6 h1:xTNEAn+kxVO7dTZGu0CegyqKZmoWFI0rF8UxjlB2d28=
+github.com/imdario/mergo v0.3.6/go.mod h1:2EnlNZ0deacrJVfApfmtdGgDfMuh/nq6Ok1EcJh5FfA=
+github.com/inconshreveable/mousetrap v1.0.1 h1:U3uMjPSQEBMNp1lFxmllqCPM6P5u/Xq7Pgzkat/bFNc=
+github.com/inconshreveable/mousetrap v1.0.1/go.mod h1:vpF70FUmC8bwa3OWnCshd2FqLfsEA9PFc4w1p2J65bw=
 github.com/jonboulle/clockwork v0.2.2 h1:UOGuzwb1PwsrDAObMuhUnj0p5ULPj8V/xJ7Kx9qUBdQ=
 github.com/josharian/intern v1.0.0 h1:vlS4z54oSdjm0bgjRigI+G1HpF+tI+9rE5LLzOg8HmY=
 github.com/josharian/intern v1.0.0/go.mod h1:5DoeVV0s6jJacbCEi61lwdGj/aVlrQvzHFFd8Hwg//Y=
@@ -222,17 +242,19 @@ github.com/konsorten/go-windows-terminal-sequences v1.0.3/go.mod h1:T0+1ngSBFLxv
 github.com/kr/logfmt v0.0.0-20140226030751-b84e30acd515/go.mod h1:+0opPa2QZZtGFBFZlji/RkVcI2GknAs/DXo4wKdlNEc=
 github.com/kr/pretty v0.1.0/go.mod h1:dAy3ld7l9f0ibDNOQOHHMYYIIbhfbHSm3C4ZsoJORNo=
 github.com/kr/pretty v0.2.0/go.mod h1:ipq/a2n7PKx3OHsz4KJII5eveXtPO4qwEXGdVfWzfnI=
+github.com/kr/pretty v0.2.1/go.mod h1:ipq/a2n7PKx3OHsz4KJII5eveXtPO4qwEXGdVfWzfnI=
+github.com/kr/pretty v0.3.0 h1:WgNl7dwNpEZ6jJ9k1snq4pZsg7DOEN8hP9Xw0Tsjwk0=
 github.com/kr/pty v1.1.1/go.mod h1:pFQYn66WHrOpPYNljwOMqo10TkYh1fy3cYio2l3bCsQ=
 github.com/kr/text v0.1.0/go.mod h1:4Jbv+DJW3UT/LiOwJeYQe1efqtUx/iVham/4vfdArNI=
 github.com/kr/text v0.2.0 h1:5Nx0Ya0ZqY2ygV366QzturHI13Jq95ApcVaJBhpS+AY=
 github.com/kr/text v0.2.0/go.mod h1:eLer722TekiGuMkidMxC/pM04lWEeraHUUmBw8l2grE=
-github.com/mailru/easyjson v0.0.0-20190614124828-94de47d64c63/go.mod h1:C1wdFJiN94OJF2b5HbByQZoLdCWB1Yqtg26g4irojpc=
-github.com/mailru/easyjson v0.0.0-20190626092158-b2ccc519800e/go.mod h1:C1wdFJiN94OJF2b5HbByQZoLdCWB1Yqtg26g4irojpc=
-github.com/mailru/easyjson v0.7.6 h1:8yTIVnZgCoiM1TgqoeTl+LfU5Jg6/xL3QhGQnimLYnA=
-github.com/mailru/easyjson v0.7.6/go.mod h1:xzfreul335JAWq5oZzymOObrkdz5UnU4kGfJJLY9Nlc=
+github.com/mailru/easyjson v0.7.7 h1:UGYAvKxe3sBsEDzO8ZeWOSlIQfWFlxbzLZe7hwFURr0=
+github.com/mailru/easyjson v0.7.7/go.mod h1:xzfreul335JAWq5oZzymOObrkdz5UnU4kGfJJLY9Nlc=
 github.com/matttproud/golang_protobuf_extensions v1.0.1/go.mod h1:D8He9yQNgCq6Z5Ld7szi9bcBfOoFv/3dc6xSMkL2PC0=
 github.com/matttproud/golang_protobuf_extensions v1.0.2 h1:hAHbPm5IJGijwng3PWk09JkG9WeqChjprR5s9bBZ+OM=
 github.com/matttproud/golang_protobuf_extensions v1.0.2/go.mod h1:BSXmuO+STAnVfrANrmjBb36TMTDstsz7MSK+HVaYKv4=
+github.com/mitchellh/mapstructure v1.4.1 h1:CpVNEelQCZBooIPDn+AR3NpivK/TIKU8bDxdASFVQag=
+github.com/mitchellh/mapstructure v1.4.1/go.mod h1:bFUtVrKA4DC2yAKiSyO/QUcy7e+RRV2QTWOzhPopBRo=
 github.com/modern-go/concurrent v0.0.0-20180228061459-e0a39a4cb421/go.mod h1:6dJC0mAP4ikYIbvyc7fijjWJddQyLn8Ig3JB5CqoB9Q=
 github.com/modern-go/concurrent v0.0.0-20180306012644-bacd9c7ef1dd h1:TRLaZ9cD/w8PVh93nsPXa1VrQ6jlwL5oN8l14QlcNfg=
 github.com/modern-go/concurrent v0.0.0-20180306012644-bacd9c7ef1dd/go.mod h1:6dJC0mAP4ikYIbvyc7fijjWJddQyLn8Ig3JB5CqoB9Q=
@@ -244,10 +266,8 @@ github.com/munnerz/goautoneg v0.0.0-20191010083416-a7dc8b61c822 h1:C3w9PqII01/Oq
 github.com/munnerz/goautoneg v0.0.0-20191010083416-a7dc8b61c822/go.mod h1:+n7T8mK8HuQTcFwEeznm/DIxMOiR9yIdICNftLE1DvQ=
 github.com/mwitkow/go-conntrack v0.0.0-20161129095857-cc309e4a2223/go.mod h1:qRWi+5nqEBWmkhHvq77mSJWrCKwh8bxhgT7d/eI7P4U=
 github.com/mwitkow/go-conntrack v0.0.0-20190716064945-2f068394615f/go.mod h1:qRWi+5nqEBWmkhHvq77mSJWrCKwh8bxhgT7d/eI7P4U=
-github.com/niemeyer/pretty v0.0.0-20200227124842-a10e7caefd8e h1:fD57ERR4JtEqsWbfPhv4DMiApHyliiK5xCTNVSPiaAs=
-github.com/niemeyer/pretty v0.0.0-20200227124842-a10e7caefd8e/go.mod h1:zD1mROLANZcx1PVRCS0qkT7pwLkGfwJo4zjcN/Tysno=
-github.com/onsi/ginkgo/v2 v2.4.0 h1:+Ig9nvqgS5OBSACXNk15PLdp0U9XPYROt9CFzVdFGIs=
-github.com/onsi/gomega v1.23.0 h1:/oxKu9c2HVap+F3PfKort2Hw5DEU+HGlW8n+tguWsys=
+github.com/onsi/ginkgo/v2 v2.9.1 h1:zie5Ly042PD3bsCvsSOPvRnFwyo3rKe64TJlD6nu0mk=
+github.com/onsi/gomega v1.27.4 h1:Z2AnStgsdSayCMDiCU42qIz+HLqEPcgiOCXjAU/w+8E=
 github.com/opencontainers/go-digest v1.0.0 h1:apOUWs51W5PlhuyGyz9FCeeBIOUDA/6nW8Oi/yOhh5U=
 github.com/opencontainers/go-digest v1.0.0/go.mod h1:0JzlMkj0TRzQZfJkVvzbP0HBR3IKzErnv2BNG4W4MAM=
 github.com/pkg/errors v0.8.0/go.mod h1:bwawxfHBFNV+L2hUp1rHADufV3IMtnDRdf1r5NINEl0=
@@ -260,7 +280,6 @@ github.com/prometheus/client_golang v0.9.1/go.mod h1:7SWBe2y4D6OKWSNQJUaRYU/AaXP
 github.com/prometheus/client_golang v1.0.0/go.mod h1:db9x61etRT2tGnBNRi70OPL5FsnadC4Ky3P0J6CfImo=
 github.com/prometheus/client_golang v1.7.1/go.mod h1:PY5Wy2awLA44sXw4AOSfFBetzPP4j5+D6mVACh+pe2M=
 github.com/prometheus/client_golang v1.11.0/go.mod h1:Z6t4BnS23TR94PD6BsDNk8yVqroYurpAkEiz0P2BEV0=
-github.com/prometheus/client_golang v1.11.1/go.mod h1:Z6t4BnS23TR94PD6BsDNk8yVqroYurpAkEiz0P2BEV0=
 github.com/prometheus/client_golang v1.12.1/go.mod h1:3Z9XVyYiZYEO+YQWt3RD2R3jrbd179Rt297l4aS6nDY=
 github.com/prometheus/client_golang v1.14.0 h1:nJdhIvne2eSX/XRAFV9PcvFFRbrjbcTUj0VP62TMhnw=
 github.com/prometheus/client_golang v1.14.0/go.mod h1:8vpkKitgIVNcqrRBWh1C4TIUQgYNtG/XQE4E/Zae36Y=
@@ -287,42 +306,50 @@ github.com/robfig/cron/v3 v3.0.1 h1:WdRxkvbJztn8LMz/QEvLN5sBU+xKpSqwwUO1Pjr4qDs=
 github.com/robfig/cron/v3 v3.0.1/go.mod h1:eQICP3HwyT7UooqI/z+Ov+PtYAWygg1TEWWzGIFLtro=
 github.com/rogpeppe/fastuuid v1.2.0/go.mod h1:jVj6XXZzXRy/MSR5jhDC/2q6DgLz+nrA6LYCDYWNEvQ=
 github.com/rogpeppe/go-internal v1.3.0/go.mod h1:M8bDsm7K2OlrFYOpmOWEs/qY81heoFRclV5y23lUDJ4=
+github.com/rogpeppe/go-internal v1.10.0 h1:TMyTOH3F/DB16zRVcYyreMH6GnZZrwQVAoYjRBZyWFQ=
+github.com/russross/blackfriday/v2 v2.1.0/go.mod h1:+Rmxgy9KzJVeS9/2gXHxylqXiyQDYRxCVz55jmeOWTM=
 github.com/sirupsen/logrus v1.2.0/go.mod h1:LxeOpSwHxABJmUn/MG1IvRgCAasNZTLOkJPxbbu5VWo=
 github.com/sirupsen/logrus v1.4.2/go.mod h1:tLMulIdttU9McNUspp0xgXVQah82FyeX6MwdIuYE2rE=
 github.com/sirupsen/logrus v1.6.0/go.mod h1:7uNnSEd1DgxDLC74fIahvMZmmYsHGZGEOFrfsX/uA88=
-github.com/sirupsen/logrus v1.8.1 h1:dJKuHgqk1NNQlqoA6BTlM1Wf9DOH3NBjQyu0h9+AZZE=
+github.com/sirupsen/logrus v1.9.0 h1:trlNQbNUG3OdDrDil03MCb1H2o9nJ1x4/5LYw7byDE0=
 github.com/soheilhy/cmux v0.1.5 h1:jjzc5WVemNEDTLwv9tlmemhC73tI08BNOIGwBOo10Js=
 github.com/spaolacci/murmur3 v0.0.0-20180118202830-f09979ecbc72/go.mod h1:JwIasOWyU6f++ZhiEuf87xNszmSA2myDM2Kzu9HwQUA=
+github.com/spf13/cobra v1.6.0 h1:42a0n6jwCot1pUmomAp4T7DeMD+20LFv4Q54pxLf2LI=
+github.com/spf13/cobra v1.6.0/go.mod h1:IOw/AERYS7UzyrGinqmz6HLUo219MORXGxhbaJUqzrY=
 github.com/spf13/pflag v1.0.5 h1:iy+VFUOCP1a+8yFto/drg2CJ5u0yRoB7fZw3DKv/JXA=
 github.com/spf13/pflag v1.0.5/go.mod h1:McXfInJRrz4CZXVZOBLb0bTZqETkiAhM9Iw0y3An2Bg=
+github.com/stoewer/go-strcase v1.2.0 h1:Z2iHWqGXH00XYgqDmNgQbIBxf3wrNq0F3feEy0ainaU=
 github.com/stoewer/go-strcase v1.2.0/go.mod h1:IBiWB2sKIp3wVVQ3Y035++gc+knqhUQag1KpM8ahLw8=
 github.com/stretchr/objx v0.1.0/go.mod h1:HFkY916IF+rwdDfMAkV7OtwuqBVzrE8GR6GFx+wExME=
 github.com/stretchr/objx v0.1.1/go.mod h1:HFkY916IF+rwdDfMAkV7OtwuqBVzrE8GR6GFx+wExME=
+github.com/stretchr/objx v0.4.0/go.mod h1:YvHI0jy2hoMjB+UWwv71VJQ9isScKT/TqJzVSSt89Yw=
+github.com/stretchr/objx v0.5.0/go.mod h1:Yh+to48EsGEfYuaHDzXPcE3xhTkx73EhmCGUpEOglKo=
 github.com/stretchr/testify v1.2.2/go.mod h1:a8OnRcib4nhh0OaRAV+Yts87kKdq0PP7pXfy6kDkUVs=
 github.com/stretchr/testify v1.3.0/go.mod h1:M5WIy9Dh21IEIfnGCwXGc5bZfKNJtfHm1UVUgZn+9EI=
 github.com/stretchr/testify v1.4.0/go.mod h1:j7eGeouHqKxXV5pUuKE4zz7dFj8WfuZ+81PSLYec5m4=
 github.com/stretchr/testify v1.5.1/go.mod h1:5W2xD1RspED5o8YsWQXVCued0rvSQ+mT+I5cxcmMvtA=
-github.com/stretchr/testify v1.6.1/go.mod h1:6Fq8oRcR53rry900zMqJjRRixrwX3KX962/h/Wwjteg=
 github.com/stretchr/testify v1.7.0/go.mod h1:6Fq8oRcR53rry900zMqJjRRixrwX3KX962/h/Wwjteg=
-github.com/stretchr/testify v1.8.0 h1:pSgiaMZlXftHpm5L7V1+rVB+AZJydKsMxsQBIJw4PKk=
-github.com/tmc/grpc-websocket-proxy v0.0.0-20201229170055-e5319fda7802 h1:uruHq4dN7GR16kFc5fp3d1RIYzJW5onx8Ybykw2YQFA=
+github.com/stretchr/testify v1.7.1/go.mod h1:6Fq8oRcR53rry900zMqJjRRixrwX3KX962/h/Wwjteg=
+github.com/stretchr/testify v1.8.0/go.mod h1:yNjHg4UonilssWZ8iaSj1OCr/vHnekPRkoO+kdMU+MU=
+github.com/stretchr/testify v1.8.1 h1:w7B6lhMri9wdJUVmEZPGGhZzrYTPvgJArz7wNPgYKsk=
+github.com/stretchr/testify v1.8.1/go.mod h1:w2LPCIKwWwSfY2zedu0+kehJoqGctiVI29o6fzry7u4=
+github.com/tmc/grpc-websocket-proxy v0.0.0-20220101234140-673ab2c3ae75 h1:6fotK7otjonDflCTK0BCfls4SPy3NcCVb5dqqmbRknE=
 github.com/xiang90/probing v0.0.0-20190116061207-43a291ad63a2 h1:eY9dn8+vbi4tKz5Qo6v2eYzo7kUS51QINcR5jNpbZS8=
 github.com/yuin/goldmark v1.1.25/go.mod h1:3hX8gzYuyVAZsxl0MRgGTJEmQBFcNTphYh9decYSb74=
 github.com/yuin/goldmark v1.1.27/go.mod h1:3hX8gzYuyVAZsxl0MRgGTJEmQBFcNTphYh9decYSb74=
 github.com/yuin/goldmark v1.1.32/go.mod h1:3hX8gzYuyVAZsxl0MRgGTJEmQBFcNTphYh9decYSb74=
 github.com/yuin/goldmark v1.2.1/go.mod h1:3hX8gzYuyVAZsxl0MRgGTJEmQBFcNTphYh9decYSb74=
-github.com/yuin/goldmark v1.3.5/go.mod h1:mwnBkeHKe2W/ZEtQ+71ViKU8L12m81fl3OWwC1Zlc8k=
 go.etcd.io/bbolt v1.3.6 h1:/ecaJf0sk1l4l6V4awd65v2C3ILy7MSj+s/x1ADCIMU=
-go.etcd.io/etcd/api/v3 v3.5.5 h1:BX4JIbQ7hl7+jL+g+2j5UAr0o1bctCm6/Ct+ArBGkf0=
-go.etcd.io/etcd/api/v3 v3.5.5/go.mod h1:KFtNaxGDw4Yx/BA4iPPwevUTAuqcsPxzyX8PHydchN8=
-go.etcd.io/etcd/client/pkg/v3 v3.5.5 h1:9S0JUVvmrVl7wCF39iTQthdaaNIiAaQbmK75ogO6GU8=
-go.etcd.io/etcd/client/pkg/v3 v3.5.5/go.mod h1:ggrwbk069qxpKPq8/FKkQ3Xq9y39kbFR4LnKszpRXeQ=
-go.etcd.io/etcd/client/v2 v2.305.5 h1:DktRP60//JJpnPC0VBymAN/7V71GHMdjDCBt4ZPXDjI=
-go.etcd.io/etcd/client/v3 v3.5.5 h1:q++2WTJbUgpQu4B6hCuT7VkdwaTP7Qz6Daak3WzbrlI=
-go.etcd.io/etcd/client/v3 v3.5.5/go.mod h1:aApjR4WGlSumpnJ2kloS75h6aHUmAyaPLjHMxpc7E7c=
-go.etcd.io/etcd/pkg/v3 v3.5.5 h1:Ablg7T7OkR+AeeeU32kdVhw/AGDsitkKPl7aW73ssjU=
-go.etcd.io/etcd/raft/v3 v3.5.5 h1:Ibz6XyZ60OYyRopu73lLM/P+qco3YtlZMOhnXNS051I=
-go.etcd.io/etcd/server/v3 v3.5.5 h1:jNjYm/9s+f9A9r6+SC4RvNaz6AqixpOvhrFdT0PvIj0=
+go.etcd.io/etcd/api/v3 v3.5.7 h1:sbcmosSVesNrWOJ58ZQFitHMdncusIifYcrBfwrlJSY=
+go.etcd.io/etcd/api/v3 v3.5.7/go.mod h1:9qew1gCdDDLu+VwmeG+iFpL+QlpHTo7iubavdVDgCAA=
+go.etcd.io/etcd/client/pkg/v3 v3.5.7 h1:y3kf5Gbp4e4q7egZdn5T7W9TSHUvkClN6u+Rq9mEOmg=
+go.etcd.io/etcd/client/pkg/v3 v3.5.7/go.mod h1:o0Abi1MK86iad3YrWhgUsbGx1pmTS+hrORWc2CamuhY=
+go.etcd.io/etcd/client/v2 v2.305.7 h1:AELPkjNR3/igjbO7CjyF1fPuVPjrblliiKj+Y6xSGOU=
+go.etcd.io/etcd/client/v3 v3.5.7 h1:u/OhpiuCgYY8awOHlhIhmGIGpxfBU/GZBUP3m/3/Iz4=
+go.etcd.io/etcd/client/v3 v3.5.7/go.mod h1:sOWmj9DZUMyAngS7QQwCyAXXAL6WhgTOPLNS/NabQgw=
+go.etcd.io/etcd/pkg/v3 v3.5.7 h1:obOzeVwerFwZ9trMWapU/VjDcYUJb5OfgC1zqEGWO/0=
+go.etcd.io/etcd/raft/v3 v3.5.7 h1:aN79qxLmV3SvIq84aNTliYGmjwsW6NqJSnqmI1HLJKc=
+go.etcd.io/etcd/server/v3 v3.5.7 h1:BTBD8IJUV7YFgsczZMHhMTS67XuA4KpRquL0MFOJGRk=
 go.opencensus.io v0.21.0/go.mod h1:mSImk1erAIZhrmZN+AvHh14ztQfjbGwt4TtuofqLduU=
 go.opencensus.io v0.22.0/go.mod h1:+kGneAE2xo2IficOXnaByMWTGM9T73dGwxeWcUqIpI8=
 go.opencensus.io v0.22.2/go.mod h1:yxeiOL68Rb0Xd1ddK5vPZ/oVn4vY4Ynel7k9FzqtOIw=
@@ -330,8 +357,8 @@ go.opencensus.io v0.22.3/go.mod h1:yxeiOL68Rb0Xd1ddK5vPZ/oVn4vY4Ynel7k9FzqtOIw=
 go.opencensus.io v0.22.4/go.mod h1:yxeiOL68Rb0Xd1ddK5vPZ/oVn4vY4Ynel7k9FzqtOIw=
 go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.35.0 h1:xFSRQBbXF6VvYRf2lqMJXxoB72XI1K/azav8TekHHSw=
 go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.35.0/go.mod h1:h8TWwRAhQpOd0aM5nYsRD8+flnkj+526GEIVlarH7eY=
-go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.35.0 h1:Ajldaqhxqw/gNzQA45IKFWLdG7jZuXX/wBW1d5qvbUI=
-go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.35.0/go.mod h1:9NiG9I2aHTKkcxqCILhjtyNA1QEiCjdBACv4IvrFQ+c=
+go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.35.1 h1:sxoY9kG1s1WpSYNyzm24rlwH4lnRYFXUVVBmKMBfRgw=
+go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.35.1/go.mod h1:9NiG9I2aHTKkcxqCILhjtyNA1QEiCjdBACv4IvrFQ+c=
 go.opentelemetry.io/otel v1.10.0 h1:Y7DTJMR6zs1xkS/upamJYk0SxxN4C9AqRd77jmZnyY4=
 go.opentelemetry.io/otel v1.10.0/go.mod h1:NbvWjCthWHKBEUMpf0/v8ZRZlni86PpGFEMA9pnQSnQ=
 go.opentelemetry.io/otel/exporters/otlp/internal/retry v1.10.0 h1:TaB+1rQhddO1sF71MpZOZAuSPW1klK2M8XxfrBMfK7Y=
@@ -352,10 +379,9 @@ go.opentelemetry.io/proto/otlp v0.19.0/go.mod h1:H7XAot3MsfNsj7EXtrA2q5xSNQ10UqI
 go.uber.org/atomic v1.7.0 h1:ADUqmZGgLDDfbSL9ZmPxKTybcoEYHgpYfELNoN+7hsw=
 go.uber.org/atomic v1.7.0/go.mod h1:fEN4uk6kAWBTFdckzkM89CLk9XfWZrxpCo0nPH17wJc=
 go.uber.org/goleak v1.1.10/go.mod h1:8a7PlsEVH3e/a/GLqe5IIrQx6GzcnRmZEufDUTk4A7A=
-go.uber.org/goleak v1.2.0 h1:xqgm/S+aQvhWFTtR0XK3Jvg7z8kGV8P4X14IzwN3Eqk=
+go.uber.org/goleak v1.2.1 h1:NBol2c7O1ZokfZ0LEU9K6Whx/KnwvepVetCUhtKja4A=
 go.uber.org/multierr v1.6.0 h1:y6IPFStTAIT5Ytl7/XYmHvzXQ7S3g/IeZW9hyZ5thw4=
 go.uber.org/multierr v1.6.0/go.mod h1:cdWPpRnG4AhwMwsgIHip0KRBQjJy5kYEpYjJxpXp9iU=
-go.uber.org/zap v1.17.0/go.mod h1:MXVU+bhUf/A7Xi2HNOnopQOrmycQ5Ih87HtOu4q5SSo=
 go.uber.org/zap v1.19.0 h1:mZQZefskPPCMIBCSEH0v2/iUqqLrYtaeqwD6FUGUnFE=
 go.uber.org/zap v1.19.0/go.mod h1:xg/QME4nWcxGxrpdeYfq7UvYrLh66cuVKdrbD1XF/NI=
 golang.org/x/crypto v0.0.0-20180904163835-0709b304e793/go.mod h1:6SG95UA2DQfeDnfUPMdvaQW0Q7yPrPDi9nlGo2tz2b4=
@@ -365,6 +391,7 @@ golang.org/x/crypto v0.0.0-20190605123033-f99c8df09eb5/go.mod h1:yigFU9vqHzYiE8U
 golang.org/x/crypto v0.0.0-20191011191535-87dc89f01550/go.mod h1:yigFU9vqHzYiE8UmvKecakEJjdnWj3jj499lnFckfCI=
 golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9/go.mod h1:LzIPMQfyMNhhGPhUkYOs5KpL4U8rLKemX1yGLhDgUto=
 golang.org/x/crypto v0.1.0 h1:MDRAIl0xIo9Io2xV565hzXHw3zVseKrJKodhohM5CjU=
+golang.org/x/crypto v0.1.0/go.mod h1:RecgLatLF4+eUMCP1PoPZQb+cVrJcOPbHkTkbkB9sbw=
 golang.org/x/exp v0.0.0-20190121172915-509febef88a4/go.mod h1:CJ0aWSM057203Lf6IL+f9T1iT9GByDxfZKAQTCR3kQA=
 golang.org/x/exp v0.0.0-20190306152737-a1d7652674e8/go.mod h1:CJ0aWSM057203Lf6IL+f9T1iT9GByDxfZKAQTCR3kQA=
 golang.org/x/exp v0.0.0-20190510132918-efd6b22b2522/go.mod h1:ZjyILWgesfNpC6sMxTJOJm9Kp84zZh5NQWvqDGG3Qr8=
@@ -387,7 +414,6 @@ golang.org/x/lint v0.0.0-20190930215403-16217165b5de/go.mod h1:6SW0HCj/g11FgYtHl
 golang.org/x/lint v0.0.0-20191125180803-fdd1cda4f05f/go.mod h1:5qLYkcX4OjUUV8bRuDixDT3tpyyb+LUpUlRWLxfhWrs=
 golang.org/x/lint v0.0.0-20200130185559-910be7a94367/go.mod h1:3xt1FjdF8hUf6vQPIChWIBhFzV8gjjsPE/fR3IyQdNY=
 golang.org/x/lint v0.0.0-20200302205851-738671d3881b/go.mod h1:3xt1FjdF8hUf6vQPIChWIBhFzV8gjjsPE/fR3IyQdNY=
-golang.org/x/lint v0.0.0-20210508222113-6edffad5e616/go.mod h1:3xt1FjdF8hUf6vQPIChWIBhFzV8gjjsPE/fR3IyQdNY=
 golang.org/x/mobile v0.0.0-20190312151609-d3739f865fa6/go.mod h1:z+o9i4GpDbdi3rU15maQ/Ox0txvL9dWGYEHz965HBQE=
 golang.org/x/mobile v0.0.0-20190719004257-d2bd2a29d028/go.mod h1:E/iHnbuqvinMTCcRqshq8CkpyQDoeVncDDYHnLhea+o=
 golang.org/x/mod v0.0.0-20190513183733-4bf6d317e70e/go.mod h1:mXi4GBBbnImb6dmsKGUJ2LatrhH/nqhxcFungHvyanc=
@@ -396,7 +422,6 @@ golang.org/x/mod v0.1.1-0.20191105210325-c90efee705ee/go.mod h1:QqPTAvyqsEbceGzB
 golang.org/x/mod v0.1.1-0.20191107180719-034126e5016b/go.mod h1:QqPTAvyqsEbceGzBzNggFXnrqF1CaUcvgkdR5Ot7KZg=
 golang.org/x/mod v0.2.0/go.mod h1:s0Qsj1ACt9ePp/hMypM3fl4fZqREWJwdYDEqhRiZZUA=
 golang.org/x/mod v0.3.0/go.mod h1:s0Qsj1ACt9ePp/hMypM3fl4fZqREWJwdYDEqhRiZZUA=
-golang.org/x/mod v0.4.2/go.mod h1:s0Qsj1ACt9ePp/hMypM3fl4fZqREWJwdYDEqhRiZZUA=
 golang.org/x/net v0.0.0-20180724234803-3673e40ba225/go.mod h1:mL1N/T3taQHkDXs73rZJwtUhF3w3ftmwwsq0BUmARs4=
 golang.org/x/net v0.0.0-20180826012351-8a410e7b638d/go.mod h1:mL1N/T3taQHkDXs73rZJwtUhF3w3ftmwwsq0BUmARs4=
 golang.org/x/net v0.0.0-20181114220301-adae6a3d119a/go.mod h1:mL1N/T3taQHkDXs73rZJwtUhF3w3ftmwwsq0BUmARs4=
@@ -430,8 +455,8 @@ golang.org/x/net v0.0.0-20210405180319-a5a99cb37ef4/go.mod h1:p54w0d4576C0XHj96b
 golang.org/x/net v0.0.0-20210525063256-abc453219eb5/go.mod h1:9nx3DQGgdP8bBQD5qxJ1jj9UTztislL4KSBs9R2vV5Y=
 golang.org/x/net v0.0.0-20220127200216-cd36cc0744dd/go.mod h1:CfG3xpIq0wQ8r1q4Su4UZFWDARRcnwPjda9FqA0JpMk=
 golang.org/x/net v0.0.0-20220225172249-27dd8689420f/go.mod h1:CfG3xpIq0wQ8r1q4Su4UZFWDARRcnwPjda9FqA0JpMk=
-golang.org/x/net v0.3.1-0.20221206200815-1e63c2f08a10 h1:Frnccbp+ok2GkUS2tC84yAq/U9Vg+0sIO7aRL3T4Xnc=
-golang.org/x/net v0.3.1-0.20221206200815-1e63c2f08a10/go.mod h1:MBQ8lrhLObU/6UmLb4fmbmk5OcyYmqtbGd/9yIeKjEE=
+golang.org/x/net v0.8.0 h1:Zrh2ngAOFYneWTAIAPethzeaQLuHwhuBkuV6ZiRnUaQ=
+golang.org/x/net v0.8.0/go.mod h1:QVkue5JL9kW//ek3r6jTKnTFis1tRmNAW2P1shuFdJc=
 golang.org/x/oauth2 v0.0.0-20180821212333-d2e6202438be/go.mod h1:N/0e6XlmueqKjAGxoOufVs8QHGRruUQn6yWY3a++T0U=
 golang.org/x/oauth2 v0.0.0-20190226205417-e64efc72b421/go.mod h1:gOpvHmFTYa4IltrdGE7lF6nIHvwfUNPOp7c8zoXwtLw=
 golang.org/x/oauth2 v0.0.0-20190604053449-0f29369cfe45/go.mod h1:gOpvHmFTYa4IltrdGE7lF6nIHvwfUNPOp7c8zoXwtLw=
@@ -451,7 +476,8 @@ golang.org/x/sync v0.0.0-20200317015054-43a5402ce75a/go.mod h1:RxMgew5VJxzue5/jJ
 golang.org/x/sync v0.0.0-20200625203802-6e8e738ad208/go.mod h1:RxMgew5VJxzue5/jJTE5uejpjVlOe/izrB70Jof72aM=
 golang.org/x/sync v0.0.0-20201020160332-67f06af15bc9/go.mod h1:RxMgew5VJxzue5/jJTE5uejpjVlOe/izrB70Jof72aM=
 golang.org/x/sync v0.0.0-20201207232520-09787c993a3a/go.mod h1:RxMgew5VJxzue5/jJTE5uejpjVlOe/izrB70Jof72aM=
-golang.org/x/sync v0.0.0-20210220032951-036812b2e83c/go.mod h1:RxMgew5VJxzue5/jJTE5uejpjVlOe/izrB70Jof72aM=
+golang.org/x/sync v0.1.0 h1:wsuoTGHzEhffawBOhz5CYhcrV4IdKZbEyZjBMuTp12o=
+golang.org/x/sync v0.1.0/go.mod h1:RxMgew5VJxzue5/jJTE5uejpjVlOe/izrB70Jof72aM=
 golang.org/x/sys v0.0.0-20180830151530-49385e6e1522/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
 golang.org/x/sys v0.0.0-20180905080454-ebe1bf3edb33/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
 golang.org/x/sys v0.0.0-20181116152217-5ac8a444bdc5/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
@@ -488,19 +514,19 @@ golang.org/x/sys v0.0.0-20201119102817-f84b799fce68/go.mod h1:h1NjWce9XRLGQEsW7w
 golang.org/x/sys v0.0.0-20210119212857-b64e53b001e4/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
 golang.org/x/sys v0.0.0-20210124154548-22da62e12c0c/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
 golang.org/x/sys v0.0.0-20210330210617-4fbd30eecc44/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
-golang.org/x/sys v0.0.0-20210403161142-5e06dd20ab57/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
 golang.org/x/sys v0.0.0-20210423082822-04245dca01da/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=
 golang.org/x/sys v0.0.0-20210510120138-977fb7262007/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
 golang.org/x/sys v0.0.0-20210603081109-ebe580a85c40/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
 golang.org/x/sys v0.0.0-20210615035016-665e8c7367d1/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
 golang.org/x/sys v0.0.0-20211216021012-1d35b9e2eb4e/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
 golang.org/x/sys v0.0.0-20220114195835-da31bd327af9/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
-golang.org/x/sys v0.3.0 h1:w8ZOecv6NaNa/zC8944JTU3vz4u6Lagfk4RPQxv92NQ=
-golang.org/x/sys v0.3.0/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
+golang.org/x/sys v0.0.0-20220908164124-27713097b956/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
+golang.org/x/sys v0.6.0 h1:MVltZSvRTcU2ljQOhs94SXPftV6DCNnZViHeQps87pQ=
+golang.org/x/sys v0.6.0/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
 golang.org/x/term v0.0.0-20201126162022-7de9c90e9dd1/go.mod h1:bj7SfCRtBDWHUb9snDiAeCFNEtKQo2Wmx5Cou7ajbmo=
 golang.org/x/term v0.0.0-20210927222741-03fcf44c2211/go.mod h1:jbD1KX2456YbFQfuXm/mYQcufACuNUgVhRMnK/tPxf8=
-golang.org/x/term v0.3.0 h1:qoo4akIqOcDME5bhc/NgxUdovd6BSS2uMsVjB56q1xI=
-golang.org/x/term v0.3.0/go.mod h1:q750SLmJuPmVoN1blW3UFBPREJfb1KmY3vwxfr+nFDA=
+golang.org/x/term v0.6.0 h1:clScbb1cHjoCkyRbWwBEUZ5H/tIFu5TAXIqaZD0Gcjw=
+golang.org/x/term v0.6.0/go.mod h1:m6U89DPEgQRMq3DNkDClhWw02AUbt2daBVO4cn4Hv9U=
 golang.org/x/text v0.0.0-20170915032832-14c0d48ead0c/go.mod h1:NqM8EUOU14njkJ3fqMW+pc6Ldnwhi/IjpwHt7yyuwOQ=
 golang.org/x/text v0.3.0/go.mod h1:NqM8EUOU14njkJ3fqMW+pc6Ldnwhi/IjpwHt7yyuwOQ=
 golang.org/x/text v0.3.1-0.20180807135948-17ff2d5776d2/go.mod h1:NqM8EUOU14njkJ3fqMW+pc6Ldnwhi/IjpwHt7yyuwOQ=
@@ -509,8 +535,8 @@ golang.org/x/text v0.3.3/go.mod h1:5Zoc/QRtKVWzQhOtBMvqHzDpF6irO9z98xDceosuGiQ=
 golang.org/x/text v0.3.5/go.mod h1:5Zoc/QRtKVWzQhOtBMvqHzDpF6irO9z98xDceosuGiQ=
 golang.org/x/text v0.3.6/go.mod h1:5Zoc/QRtKVWzQhOtBMvqHzDpF6irO9z98xDceosuGiQ=
 golang.org/x/text v0.3.7/go.mod h1:u+2+/6zg+i71rQMx5EYifcz6MCKuco9NR6JIITiCfzQ=
-golang.org/x/text v0.5.0 h1:OLmvp0KP+FVG99Ct/qFiL/Fhk4zp4QQnZ7b2U+5piUM=
-golang.org/x/text v0.5.0/go.mod h1:mrYo+phRRbMaCq/xk9113O4dZlRixOauAjOtrjsXDZ8=
+golang.org/x/text v0.8.0 h1:57P1ETyNKtuIjB4SRd15iJxuhj8Gc416Y78H3qgMh68=
+golang.org/x/text v0.8.0/go.mod h1:e1OnstbJyHTd6l/uOt8jFFHp6TRDWZR/bV3emEE/zU8=
 golang.org/x/time v0.0.0-20181108054448-85acf8d2951c/go.mod h1:tRJNPiyCQ0inRvYxbN9jk5I+vvW/OXSQhTDSoE431IQ=
 golang.org/x/time v0.0.0-20190308202827-9d24e82272b4/go.mod h1:tRJNPiyCQ0inRvYxbN9jk5I+vvW/OXSQhTDSoE431IQ=
 golang.org/x/time v0.0.0-20191024005414-555d28b269f0/go.mod h1:tRJNPiyCQ0inRvYxbN9jk5I+vvW/OXSQhTDSoE431IQ=
@@ -559,7 +585,7 @@ golang.org/x/tools v0.0.0-20200729194436-6467de6f59a7/go.mod h1:njjCfa9FT2d7l9Bc
 golang.org/x/tools v0.0.0-20200804011535-6c149bb5ef0d/go.mod h1:njjCfa9FT2d7l9Bc6FUM5FLjQPp3cFF28FI3qnDFljA=
 golang.org/x/tools v0.0.0-20200825202427-b303f430e36d/go.mod h1:njjCfa9FT2d7l9Bc6FUM5FLjQPp3cFF28FI3qnDFljA=
 golang.org/x/tools v0.0.0-20210106214847-113979e3529a/go.mod h1:emZCQorbCU4vsT4fOWvOPXz4eW1wZW4PmDk9uLelYpA=
-golang.org/x/tools v0.1.2/go.mod h1:o0xws9oXOQQZyjljx8fwUC0k7L1pTE6eaCbjGeHmOkk=
+golang.org/x/tools v0.7.0 h1:W4OVu8VVOaIO0yzWMNdepAulS7YfoS3Zabrm8DOXXU4=
 golang.org/x/xerrors v0.0.0-20190717185122-a985d3407aa7/go.mod h1:I/5z698sn9Ka8TeJc9MKroUUfqBBauWjQqLJ2OPfmY0=
 golang.org/x/xerrors v0.0.0-20191011141410-1b5146add898/go.mod h1:I/5z698sn9Ka8TeJc9MKroUUfqBBauWjQqLJ2OPfmY0=
 golang.org/x/xerrors v0.0.0-20191204190536-9bdfabe68543/go.mod h1:I/5z698sn9Ka8TeJc9MKroUUfqBBauWjQqLJ2OPfmY0=
@@ -619,7 +645,6 @@ google.golang.org/genproto v0.0.0-20200729003335-053ba62fc06f/go.mod h1:FWY/as6D
 google.golang.org/genproto v0.0.0-20200804131852-c06518451d9c/go.mod h1:FWY/as6DDZQgahTzZj3fqbO1CbirC29ZNUFHwi0/+no=
 google.golang.org/genproto v0.0.0-20200825200019-8632dd797987/go.mod h1:FWY/as6DDZQgahTzZj3fqbO1CbirC29ZNUFHwi0/+no=
 google.golang.org/genproto v0.0.0-20201019141844-1ed22bb0c154/go.mod h1:FWY/as6DDZQgahTzZj3fqbO1CbirC29ZNUFHwi0/+no=
-google.golang.org/genproto v0.0.0-20210602131652-f16073e35f0c/go.mod h1:UODoCrxHCcBojKKwX1terBiRUaqAsFqJiF615XL43r0=
 google.golang.org/genproto v0.0.0-20211118181313-81c1377c94b1/go.mod h1:5CzLGKJ67TSI2B9POpiiyGha0AjJvZIUgRMt1dSmuhc=
 google.golang.org/genproto v0.0.0-20220502173005-c8bf987b8c21 h1:hrbNEivu7Zn1pxvHk6MBrq9iE22woVILTHqexqBxe6I=
 google.golang.org/genproto v0.0.0-20220502173005-c8bf987b8c21/go.mod h1:RAyBrSAP7Fh3Nc84ghnVLDPuV51xc9agzmm4Ph6i0Q4=
@@ -637,13 +662,11 @@ google.golang.org/grpc v1.30.0/go.mod h1:N36X2cJ7JwdamYAgDz+s+rVMFjt3numwzf/HckM
 google.golang.org/grpc v1.31.0/go.mod h1:N36X2cJ7JwdamYAgDz+s+rVMFjt3numwzf/HckM8pak=
 google.golang.org/grpc v1.33.1/go.mod h1:fr5YgcSWrqhRRxogOsw7RzIpsmvOZ6IcH4kBYTpR3n0=
 google.golang.org/grpc v1.36.0/go.mod h1:qjiiYl8FncCW8feJPdyg3v6XW24KsRHe+dy9BAGRRjU=
-google.golang.org/grpc v1.38.0/go.mod h1:NREThFqKR1f3iQ6oBuvc5LadQuXVGo9rkm5ZGrQdJfM=
 google.golang.org/grpc v1.40.0/go.mod h1:ogyxbiOoUXAkP+4+xa6PZSE9DZgIHtSpzjDTB9KAK34=
-google.golang.org/grpc v1.41.0/go.mod h1:U3l9uK9J0sini8mHphKoXyaqDA/8VyGnDee1zzIUK6k=
 google.golang.org/grpc v1.42.0/go.mod h1:k+4IHHFw41K8+bbowsex27ge2rCb65oeWqe4jJ590SU=
 google.golang.org/grpc v1.46.0/go.mod h1:vN9eftEi1UMyUsIF80+uQXhHjbXYbm0uXoFCACuMGWk=
-google.golang.org/grpc v1.49.0 h1:WTLtQzmQori5FUH25Pq4WT22oCsv8USpQ+F6rqtsmxw=
-google.golang.org/grpc v1.49.0/go.mod h1:ZgQEeidpAuNRZ8iRrlBKXZQP1ghovWIVhdJRyCDK+GI=
+google.golang.org/grpc v1.51.0 h1:E1eGv1FTqoLIdnBCZufiSHgKjlqG6fKFf6pPWtMTh8U=
+google.golang.org/grpc v1.51.0/go.mod h1:wgNDFcnuBGmxLKI/qn4T+m5BtEBYXJPvibbUPsAIPww=
 google.golang.org/protobuf v0.0.0-20200109180630-ec00e32a8dfd/go.mod h1:DFci5gLYBciE7Vtevhsrf46CRTquxDuWsQurQQe4oz8=
 google.golang.org/protobuf v0.0.0-20200221191635-4d8936d0db64/go.mod h1:kwYJMbMJ01Woi6D6+Kah6886xMZcty6N08ah7+eCXa0=
 google.golang.org/protobuf v0.0.0-20200228230310-ab0ca4ff8a60/go.mod h1:cfTl7dwQJ+fmap5saPgwCLgHXTUD7jkjRqWcaiX5VyM=
@@ -664,12 +687,13 @@ gopkg.in/alecthomas/kingpin.v2 v2.2.6/go.mod h1:FMv+mEhP44yOT+4EoQTLFTRgOQ1FBLks
 gopkg.in/check.v1 v0.0.0-20161208181325-20d25e280405/go.mod h1:Co6ibVJAznAaIkqp8huTwlJQCZ016jof/cbN4VW5Yz0=
 gopkg.in/check.v1 v1.0.0-20180628173108-788fd7840127/go.mod h1:Co6ibVJAznAaIkqp8huTwlJQCZ016jof/cbN4VW5Yz0=
 gopkg.in/check.v1 v1.0.0-20190902080502-41f04d3bba15/go.mod h1:Co6ibVJAznAaIkqp8huTwlJQCZ016jof/cbN4VW5Yz0=
-gopkg.in/check.v1 v1.0.0-20200227125254-8fa46927fb4f h1:BLraFXnmrev5lT+xlilqcH8XK9/i0At2xKjWk4p6zsU=
-gopkg.in/check.v1 v1.0.0-20200227125254-8fa46927fb4f/go.mod h1:Co6ibVJAznAaIkqp8huTwlJQCZ016jof/cbN4VW5Yz0=
+gopkg.in/check.v1 v1.0.0-20201130134442-10cb98267c6c h1:Hei/4ADfdWqJk1ZMxUNpqntNwaWcugrBjAiHlqqRiVk=
+gopkg.in/check.v1 v1.0.0-20201130134442-10cb98267c6c/go.mod h1:JHkPIbrfpd72SG/EVd6muEfDQjcINNoR0C8j2r3qZ4Q=
 gopkg.in/errgo.v2 v2.1.0/go.mod h1:hNsd1EY+bozCKY1Ytp96fpM3vjJbqLJn88ws8XvfDNI=
 gopkg.in/inf.v0 v0.9.1 h1:73M5CoZyi3ZLMOyDlQh031Cx6N9NDJ2Vvfl76EDAgDc=
 gopkg.in/inf.v0 v0.9.1/go.mod h1:cWUDdTG/fYaXco+Dcufb5Vnc6Gp2YChqWtbxRZE0mXw=
 gopkg.in/natefinch/lumberjack.v2 v2.0.0 h1:1Lc07Kr7qY4U2YPouBjpCLxpiyxIVoxqXgkXLknAOE8=
+gopkg.in/natefinch/lumberjack.v2 v2.0.0/go.mod h1:l0ndWWf7gzL7RNwBG7wST/UCcT4T24xpD6X8LsfU/+k=
 gopkg.in/yaml.v2 v2.2.1/go.mod h1:hI93XBmqTisBFMUTm0b8Fm+jr3Dg1NNxqwp+5A1VGuI=
 gopkg.in/yaml.v2 v2.2.2/go.mod h1:hI93XBmqTisBFMUTm0b8Fm+jr3Dg1NNxqwp+5A1VGuI=
 gopkg.in/yaml.v2 v2.2.3/go.mod h1:hI93XBmqTisBFMUTm0b8Fm+jr3Dg1NNxqwp+5A1VGuI=
@@ -691,33 +715,40 @@ honnef.co/go/tools v0.0.0-20190523083050-ea95bdfd59fc/go.mod h1:rf3lG4BRIbNafJWh
 honnef.co/go/tools v0.0.1-2019.2.3/go.mod h1:a3bituU0lyd329TUQxRnasdCoJDkEUEAqEt0JzvZhAg=
 honnef.co/go/tools v0.0.1-2020.1.3/go.mod h1:X/FiERA/W4tHapMX5mGpAtMSVEeEUOyHaw9vFzvIQ3k=
 honnef.co/go/tools v0.0.1-2020.1.4/go.mod h1:X/FiERA/W4tHapMX5mGpAtMSVEeEUOyHaw9vFzvIQ3k=
-k8s.io/api v0.26.0 h1:IpPlZnxBpV1xl7TGk/X6lFtpgjgntCg8PJ+qrPHAC7I=
-k8s.io/api v0.26.0/go.mod h1:k6HDTaIFC8yn1i6pSClSqIwLABIcLV9l5Q4EcngKnQg=
-k8s.io/apimachinery v0.26.0 h1:1feANjElT7MvPqp0JT6F3Ss6TWDwmcjLypwoPpEf7zg=
-k8s.io/apimachinery v0.26.0/go.mod h1:tnPmbONNJ7ByJNz9+n9kMjNP8ON+1qoAIIC70lztu74=
-k8s.io/apiserver v0.26.0 h1:q+LqIK5EZwdznGZb8bq0+a+vCqdeEEe4Ux3zsOjbc4o=
-k8s.io/apiserver v0.26.0/go.mod h1:aWhlLD+mU+xRo+zhkvP/gFNbShI4wBDHS33o0+JGI84=
-k8s.io/client-go v0.26.0 h1:lT1D3OfO+wIi9UFolCrifbjUUgu7CpLca0AD8ghRLI8=
-k8s.io/client-go v0.26.0/go.mod h1:I2Sh57A79EQsDmn7F7ASpmru1cceh3ocVT9KlX2jEZg=
-k8s.io/component-base v0.26.0 h1:0IkChOCohtDHttmKuz+EP3j3+qKmV55rM9gIFTXA7Vs=
-k8s.io/component-base v0.26.0/go.mod h1:lqHwlfV1/haa14F/Z5Zizk5QmzaVf23nQzCwVOQpfC8=
-k8s.io/component-helpers v0.26.0 h1:KNgwqs3EUdK0HLfW4GhnbD+q/Zl9U021VfIU7qoVYFk=
-k8s.io/component-helpers v0.26.0/go.mod h1:jHN01qS/Jdj95WCbTe9S2VZ9yxpxXNY488WjF+yW4fo=
-k8s.io/klog/v2 v2.80.1 h1:atnLQ121W371wYYFawwYx1aEY2eUfs4l3J72wtgAwV4=
-k8s.io/klog/v2 v2.80.1/go.mod h1:y1WjHnz7Dj687irZUWR/WLkLc5N1YHtjLdmgWjndZn0=
-k8s.io/kube-openapi v0.0.0-20221012153701-172d655c2280 h1:+70TFaan3hfJzs+7VK2o+OGxg8HsuBr/5f6tVAjDu6E=
-k8s.io/kube-openapi v0.0.0-20221012153701-172d655c2280/go.mod h1:+Axhij7bCpeqhklhUTe3xmOn6bWxolyZEeyaFpjGtl4=
-k8s.io/utils v0.0.0-20221107191617-1a15be271d1d h1:0Smp/HP1OH4Rvhe+4B8nWGERtlqAGSftbSbbmm45oFs=
-k8s.io/utils v0.0.0-20221107191617-1a15be271d1d/go.mod h1:OLgZIPagt7ERELqWJFomSt595RzquPNLL48iOWgYOg0=
+k8s.io/api v0.27.0 h1:2owttiA8Oa+J3idFeq8TSnNpm4y6AOGPI3PDbIpp2cE=
+k8s.io/api v0.27.0/go.mod h1:Wl+QRvQlh+T8SK5f4F6YBhhyH6hrFO08nl74xZb1MUE=
+k8s.io/apimachinery v0.27.0 h1:vEyy/PVMbPMCPutrssCVHCf0JNZ0Px+YqPi82K2ALlk=
+k8s.io/apimachinery v0.27.0/go.mod h1:5ikh59fK3AJ287GUvpUsryoMFtH9zj/ARfWCo3AyXTM=
+k8s.io/apiserver v0.27.0 h1:sXt/2yVMebZef6GqJHs4IYHSdSYwwrJCafBV/KSCwDw=
+k8s.io/apiserver v0.27.0/go.mod h1:8heEJ5f6EqiKwXC3Ez3ikgOvGtRSEQG/SQZkhO9UzIg=
+k8s.io/client-go v0.27.0 h1:DyZS1fJkv73tEy7rWv4VF6NwGeJ7SKvNaLRXZBYLA+4=
+k8s.io/client-go v0.27.0/go.mod h1:XVEmpNnM+4JYO3EENoFV/ZDv3KxKVJUnzGo70avk+C4=
+k8s.io/cloud-provider v0.27.0 h1:UWEvGvfd9VDRSrtmek7dDeHfUUtycHyvIO6TGI9bFJE=
+k8s.io/cloud-provider v0.27.0/go.mod h1:hUbqXpAWGaOTUhwL5k2QO9i2l9mEMhdMV9ChbvB3Gmw=
+k8s.io/component-base v0.27.0 h1:g3/FkscH8Uqg9SiDCEfhfhTVwKiVo4T2+iBwUqiFkMg=
+k8s.io/component-base v0.27.0/go.mod h1:PXyBQd/vYYjqqGB83rnsHffTTG6zlmxZAd0ZSOu6evk=
+k8s.io/component-helpers v0.27.0 h1:rymQGJc4s30hHeb5VGuPdht8gKIPecj+Bw2FOJSavE4=
+k8s.io/component-helpers v0.27.0/go.mod h1:vMjVwym/Y0BVyNvg8a4Et2vyPJAh/JhBM0OTRAt0Ceg=
+k8s.io/controller-manager v0.27.0 h1:xW0V4tXJfxRmc5OEwZn0GHU0auKySRJmlVMS/tqrWPw=
+k8s.io/controller-manager v0.27.0/go.mod h1:E9SEe60LMWkBTe7IUm1pVTrikc5tjzEl6RUNbBUdm3c=
+k8s.io/klog/v2 v2.90.1 h1:m4bYOKall2MmOiRaR1J+We67Do7vm9KiQVlT96lnHUw=
+k8s.io/klog/v2 v2.90.1/go.mod h1:y1WjHnz7Dj687irZUWR/WLkLc5N1YHtjLdmgWjndZn0=
+k8s.io/kms v0.27.0 h1:adCotKQybOjxwbxW7ogXyv8uQGan/3Y126S2aNW4YFY=
+k8s.io/kms v0.27.0/go.mod h1:vI2R4Nhw+PZ+DYtVPVYKsIqip2IYjZWK9bESR64WdIw=
+k8s.io/kube-openapi v0.0.0-20230308215209-15aac26d736a h1:gmovKNur38vgoWfGtP5QOGNOA7ki4n6qNYoFAgMlNvg=
+k8s.io/kube-openapi v0.0.0-20230308215209-15aac26d736a/go.mod h1:y5VtZWM9sHHc2ZodIH/6SHzXj+TPU5USoA8lcIeKEKY=
+k8s.io/kubelet v0.27.0 h1:zn70SDJKNmRSFG2qeU2UITzZWdEbLVWIf/u1kd1raUQ=
+k8s.io/kubelet v0.27.0/go.mod h1:Z6ipUvM0AFzUWxvSmot8OodwcMN15lgkFM3bcBexBsI=
+k8s.io/utils v0.0.0-20230209194617-a36077c30491 h1:r0BAOLElQnnFhE/ApUsg3iHdVYYPBjNSSOMowRZxxsY=
+k8s.io/utils v0.0.0-20230209194617-a36077c30491/go.mod h1:OLgZIPagt7ERELqWJFomSt595RzquPNLL48iOWgYOg0=
 rsc.io/binaryregexp v0.2.0/go.mod h1:qTv7/COck+e2FymRvadv62gMdZztPaShugOCi3I+8D8=
 rsc.io/quote/v3 v3.1.0/go.mod h1:yEA65RcK8LyAZtP9Kv3t0HmxON59tX3rD+tICJqUlj0=
 rsc.io/sampler v1.3.0/go.mod h1:T1hPZKmBbMNahiBKFy5HrXp6adAjACjK9JXDnKaTXpA=
-sigs.k8s.io/apiserver-network-proxy/konnectivity-client v0.0.33 h1:LYqFq+6Cj2D0gFfrJvL7iElD4ET6ir3VDdhDdTK7rgc=
-sigs.k8s.io/apiserver-network-proxy/konnectivity-client v0.0.33/go.mod h1:soWkSNf2tZC7aMibXEqVhCd73GOY5fJikn8qbdzemB0=
-sigs.k8s.io/json v0.0.0-20220713155537-f223a00ba0e2 h1:iXTIw73aPyC+oRdyqqvVJuloN1p0AC/kzH07hu3NE+k=
-sigs.k8s.io/json v0.0.0-20220713155537-f223a00ba0e2/go.mod h1:B8JuhiUyNFVKdsE8h686QcCxMaH6HrOAZj4vswFpcB0=
+sigs.k8s.io/apiserver-network-proxy/konnectivity-client v0.1.1 h1:MB1zkK+WMOmfLxEpjr1wEmkpcIhZC7kfTkZ0stg5bog=
+sigs.k8s.io/apiserver-network-proxy/konnectivity-client v0.1.1/go.mod h1:/4NLd21PQY0B+H+X0aDZdwUiVXYJQl/2NXA5KVtDiP4=
+sigs.k8s.io/json v0.0.0-20221116044647-bc3834ca7abd h1:EDPBXCAspyGV4jQlpZSudPeMmr1bNJefnuqLsRAsHZo=
+sigs.k8s.io/json v0.0.0-20221116044647-bc3834ca7abd/go.mod h1:B8JuhiUyNFVKdsE8h686QcCxMaH6HrOAZj4vswFpcB0=
 sigs.k8s.io/structured-merge-diff/v4 v4.2.3 h1:PRbqxJClWWYMNV1dhaG4NsibJbArud9kFxnAMREiWFE=
 sigs.k8s.io/structured-merge-diff/v4 v4.2.3/go.mod h1:qjx8mGObPmV2aSZepjQjbmb2ihdVs8cGKBraizNC69E=
-sigs.k8s.io/yaml v1.2.0/go.mod h1:yfXDCHCao9+ENCvLSE62v9VSji2MKu5jeNfTrofGhJc=
 sigs.k8s.io/yaml v1.3.0 h1:a2VclLzOGrwOHDiV8EfBGhvjHvP46CtW5j6POvhYGGo=
 sigs.k8s.io/yaml v1.3.0/go.mod h1:GeOyir5tyXNByN85N/dRIT9es5UQNerPYEKK56eTBm8=

From 1cec38acc0c65f1bf2c5b0e3fadd8ff176deb4d3 Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Sun, 16 Apr 2023 11:16:24 +0800
Subject: [PATCH 227/272] sync blog
 2023-04-20-read-write-once-pod-access-mode-beta.md

sync blog 2023-04-20-read-write-once-pod-access-mode-beta.md
---
 ...20-read-write-once-pod-access-mode-beta.md | 205 ++++++++++++++++++
 1 file changed, 205 insertions(+)
 create mode 100644 content/zh-cn/blog/_posts/2023-04-20-read-write-once-pod-access-mode-beta.md

diff --git a/content/zh-cn/blog/_posts/2023-04-20-read-write-once-pod-access-mode-beta.md b/content/zh-cn/blog/_posts/2023-04-20-read-write-once-pod-access-mode-beta.md
new file mode 100644
index 00000000000..acb6db74c19
--- /dev/null
+++ b/content/zh-cn/blog/_posts/2023-04-20-read-write-once-pod-access-mode-beta.md
@@ -0,0 +1,205 @@
+---
+layout: blog
+title: "Kubernetes 1.27: Single Pod Access Mode for PersistentVolumes Graduates to Beta"
+date: 2023-04-20
+slug: read-write-once-pod-access-mode-beta
+---
+<!--
+layout: blog
+title: "Kubernetes 1.27：持久卷的单个Pod访问模式升级为Beta版"
+date: 2023-04-20
+slug: read-write-once-pod-access-mode-beta
+-->
+
+<!--
+**Author:** Chris Henzie (Google)
+-->
+**作者**：Chris Henzie (Google)
+
+**译者**：顾欣 (ICBC)
+
+<!--
+With the release of Kubernetes v1.27 the ReadWriteOncePod feature has graduated
+to beta. In this blog post, we'll take a closer look at this feature, what it
+does, and how it has evolved in the beta release.
+-->
+随着 Kubernetes v1.27 的发布，ReadWriteOncePod 功能已经升级为 Beta 版。
+在这篇博客文章中，我们将更详细地介绍这个功能，作用以及在 Beta 版本中的发展。
+
+<!--
+## What is ReadWriteOncePod?
+-->
+## 什么是 ReadWriteOncePod  {#what-is-readwriteoncepod}
+
+<!--
+ReadWriteOncePod is a new access mode for
+[PersistentVolumes](/docs/concepts/storage/persistent-volumes/#persistent-volumes) (PVs)
+and [PersistentVolumeClaims](/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims) (PVCs)
+introduced in Kubernetes v1.22. This access mode enables you to restrict volume
+access to a single pod in the cluster, ensuring that only one pod can write to
+the volume at a time. This can be particularly useful for stateful workloads
+that require single-writer access to storage.
+-->
+ReadWriteOncePod 是 Kubernetes 在 v1.22 中引入的一种新的访问模式，
+适用于 [PersistentVolume](/zh-cn/docs/concepts/storage/persistent-volumes/#persistent-volumes)(PVs)
+和 [PersistentVolumeClaim](/zh-cn/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims)(PVCs)。
+此访问模式使你能够将存储卷访问限制在集群中的单个 Pod 上，确保一次只有一个 Pod 可以写入存储卷。
+这可能对需要单一写入者访问存储的有状态工作负载特别有用。
+
+<!--
+For more context on access modes and how ReadWriteOncePod works read
+[What are access modes and why are they important?](/blog/2021/09/13/read-write-once-pod-access-mode-alpha/#what-are-access-modes-and-why-are-they-important)
+in the _Introducing Single Pod Access Mode for PersistentVolumes_ article from 2021.
+-->
+要了解有关访问模式和 ReadWriteOncePod 如何工作的更多背景信息，
+请阅读 2021 年介绍 PersistentVolume 的单个 Pod 访问模式的文章中的[什么是访问模式和为什么它们如此重要？](/blog/2021/09/13/read-write-once-pod-access-mode-alpha/#what-are-access-modes-and-why-are-they-important)。
+
+<!--
+## Changes in the ReadWriteOncePod beta
+-->
+## ReadWriteOncePod 的 Beta 版中变化  {#changes-in-the-readwriteoncepod-beta}
+
+<!--
+The ReadWriteOncePod beta adds support for
+[scheduler preemption](/docs/concepts/scheduling-eviction/pod-priority-preemption/)
+of pods using ReadWriteOncePod PVCs.
+-->
+ReadWriteOncePod Beta 版为使用 ReadWriteOncePod PVC 的 Pod 添加[调度器抢占](/zh-cn/docs/concepts/scheduling-eviction/pod-priority-preemption/)。
+
+<!--
+Scheduler preemption allows higher-priority pods to preempt lower-priority pods,
+so that they can start running on the same node. With this release, pods using
+ReadWriteOncePod PVCs can also be preempted if a higher-priority pod requires
+the same PVC.
+-->
+调度器抢占允许更高优先级的 Pod 抢占较低优先级的 Pod，以便它们可以在同一节点上运行。
+在此版本中，如果更高优先级的 Pod 需要相同的 PVC，使用 ReadWriteOncePod PVCs 的 Pod 也可以被抢占。
+
+<!--
+## How can I start using ReadWriteOncePod?
+-->
+## 如何开始使用 ReadWriteOncePod？  {#how-can-i-start-using-readwriteoncepod}
+
+<!--
+With ReadWriteOncePod now in beta, it will be enabled by default in cluster
+versions v1.27 and beyond.
+-->
+随着 ReadWriteOncePod 现已升级为 Beta 版，在 v1.27 及更高版本的集群中将默认启用该功能。
+
+<!--
+Note that ReadWriteOncePod is
+[only supported for CSI volumes](/docs/concepts/storage/persistent-volumes/#access-modes).
+Before using this feature you will need to update the following
+[CSI sidecars](https://kubernetes-csi.github.io/docs/sidecar-containers.html)
+to these versions or greater:
+-->
+请注意，ReadWriteOncePod [仅支持 CSI 卷](/zh-cn/docs/concepts/storage/persistent-volumes/#access-modes)。
+在使用此功能之前，你需要将以下 [CSI Sidecars](https://kubernetes-csi.github.io/docs/sidecar-containers.html)更新至以下版本或更高版本：
+
+<!--
+- [csi-provisioner:v3.0.0+](https://github.com/kubernetes-csi/external-provisioner/releases/tag/v3.0.0)
+- [csi-attacher:v3.3.0+](https://github.com/kubernetes-csi/external-attacher/releases/tag/v3.3.0)
+- [csi-resizer:v1.3.0+](https://github.com/kubernetes-csi/external-resizer/releases/tag/v1.3.0)
+-->
+- [csi-provisioner:v3.0.0+](https://github.com/kubernetes-csi/external-provisioner/releases/tag/v3.0.0)
+- [csi-attacher:v3.3.0+](https://github.com/kubernetes-csi/external-attacher/releases/tag/v3.3.0)
+- [csi-resizer:v1.3.0+](https://github.com/kubernetes-csi/external-resizer/releases/tag/v1.3.0)
+
+<!--
+To start using ReadWriteOncePod, create a PVC with the ReadWriteOncePod access mode:
+-->
+要开始使用 ReadWriteOncePod，请创建具有 ReadWriteOncePod 访问模式的 PVC：
+
+```yaml
+kind: PersistentVolumeClaim
+apiVersion: v1
+metadata:
+  name: single-writer-only
+spec:
+  accessModes:
+  - ReadWriteOncePod #仅允许一个容器访问且独占写入权限。
+  resources:
+    requests:
+      storage: 1Gi
+```
+
+<!--
+If your storage plugin supports
+[dynamic provisioning](/docs/concepts/storage/dynamic-provisioning/),
+new PersistentVolumes will be created with the ReadWriteOncePod access mode applied.
+
+Read [Migrating existing PersistentVolumes](/blog/2021/09/13/read-write-once-pod-access-mode-alpha/#migrating-existing-persistentvolumes)
+for details on migrating existing volumes to use ReadWriteOncePod.
+-->
+如果你的存储插件支持[动态制备](/zh-cn/docs/concepts/storage/dynamic-provisioning/)，
+新创建的持久卷将应用 ReadWriteOncePod 访问模式。
+
+阅读[迁移现有持久卷](/blog/2021/09/13/read-write-once-pod-access-mode-alpha/#migrating-existing-persistentvolumes)
+以了解如何迁移现有卷以使用 ReadWriteOncePod。
+
+<!--
+## How can I learn more?
+-->
+## 如何了解更多信息？ {#how-can-i-learn-more}
+
+<!--
+Please see the [alpha blog post](/blog/2021/09/13/read-write-once-pod-access-mode-alpha)
+and [KEP-2485](https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/2485-read-write-once-pod-pv-access-mode/README.md)
+for more details on the ReadWriteOncePod access mode and motivations for CSI spec changes.
+-->
+请查看 [Alpha 版博客](/blog/2021/09/13/read-write-once-pod-access-mode-alpha)和
+[KEP-2485](https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/2485-read-write-once-pod-pv-access-mode/README.md)
+以了解关于 ReadWriteOncePod 访问模式的更多详细信息以及对 CSI 规约作更改的动机。
+
+<!--
+## How do I get involved?
+-->
+## 如何参与？ {#how-do-i-get-involved}
+
+<!--
+The [Kubernetes #csi Slack channel](https://kubernetes.slack.com/messages/csi)
+and any of the standard
+[SIG Storage communication channels](https://github.com/kubernetes/community/blob/master/sig-storage/README.md#contact)
+are great mediums to reach out to the SIG Storage and the CSI teams.
+-->
+[Kubernetes #csi Slack](https://kubernetes.slack.com/messages/csi)频道以及任何常规的
+[SIG 存储沟通渠道](https://github.com/kubernetes/community/blob/master/sig-storage/README.md#contact)
+都是联系 SIG 存储和 CSI 团队的最佳途径。
+
+<!--
+Special thanks to the following people whose thoughtful reviews and feedback helped shape this feature:
+-->
+特别感谢以下人士的仔细的审查和反馈，帮助完成了这个功能：
+
+<!--
+* Abdullah Gharaibeh (ahg-g)
+* Aldo Culquicondor (alculquicondor)
+* Antonio Ojea (aojea)
+* David Eads (deads2k)
+* Jan Šafránek (jsafrane)
+* Joe Betz (jpbetz)
+* Kante Yin (kerthcet)
+* Michelle Au (msau42)
+* Tim Bannister (sftim)
+* Xing Yang (xing-yang)
+-->
+* Abdullah Gharaibeh (ahg-g)
+* Aldo Culquicondor (alculquicondor)
+* Antonio Ojea (aojea)
+* David Eads (deads2k)
+* Jan Šafránek (jsafrane)
+* Joe Betz (jpbetz)
+* Kante Yin (kerthcet)
+* Michelle Au (msau42)
+* Tim Bannister (sftim)
+* Xing Yang (xing-yang)
+
+<!--
+If you’re interested in getting involved with the design and development of CSI
+or any part of the Kubernetes storage system, join the
+[Kubernetes Storage Special Interest Group](https://github.com/kubernetes/community/tree/master/sig-storage) (SIG).
+We’re rapidly growing and always welcome new contributors.
+-->
+如果您有兴趣参与 CSI 或 Kubernetes 存储系统的任何部分的设计和开发，
+请加入 [Kubernetes 存储特别兴趣小组](https://github.com/kubernetes/community/tree/master/sig-storage)(SIG)。
+我们正在迅速发展，始终欢迎新的贡献者。
\ No newline at end of file

From f368fe085ce603de5dadf3ca68dd31a27bc8af80 Mon Sep 17 00:00:00 2001
From: Ricardo Katz <rkatz@vmware.com>
Date: Sun, 16 Apr 2023 17:32:25 -0300
Subject: [PATCH 228/272] Add missing index on pt-br tasks

---
 content/pt-br/docs/tasks/configure-pod-container/_index.md | 5 +++++
 1 file changed, 5 insertions(+)
 create mode 100644 content/pt-br/docs/tasks/configure-pod-container/_index.md

diff --git a/content/pt-br/docs/tasks/configure-pod-container/_index.md b/content/pt-br/docs/tasks/configure-pod-container/_index.md
new file mode 100644
index 00000000000..9fa656fb20a
--- /dev/null
+++ b/content/pt-br/docs/tasks/configure-pod-container/_index.md
@@ -0,0 +1,5 @@
+---
+title: "Configurar Pods e Contêineres"
+description: Realizar tarefas comuns de configuração de Pods e contêineres 
+weight: 30
+---
\ No newline at end of file

From b5130362639674da47351a0c155f6ebb3449918e Mon Sep 17 00:00:00 2001
From: Guangwen Feng <fenggw-fnst@fujitsu.com>
Date: Fri, 14 Apr 2023 17:25:39 +0800
Subject: [PATCH 229/272] [zh-cn] Sync pod-lifecycle.md

Signed-off-by: Guangwen Feng <fenggw-fnst@fujitsu.com>
---
 .../concepts/workloads/pods/pod-lifecycle.md  | 71 ++++++++++++++-----
 1 file changed, 52 insertions(+), 19 deletions(-)

diff --git a/content/zh-cn/docs/concepts/workloads/pods/pod-lifecycle.md b/content/zh-cn/docs/concepts/workloads/pods/pod-lifecycle.md
index b944e99b709..1af273c7a47 100644
--- a/content/zh-cn/docs/concepts/workloads/pods/pod-lifecycle.md
+++ b/content/zh-cn/docs/concepts/workloads/pods/pod-lifecycle.md
@@ -148,12 +148,13 @@ Pod 阶段的数量和含义是严格定义的。
 下面是 `phase` 可能的值：
 
 <!--
-Value | Description
-`Pending` | The Pod has been accepted by the Kubernetes cluster, but one or more of the containers has not been set up and made ready to run. This includes time a Pod spends waiting to bescheduled as well as the time spent downloading container images over the network.
-`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.
+Value       | Description
+:-----------|:-----------
+`Pending`   | The Pod has been accepted by the Kubernetes cluster, but one or more of the containers has not been set up and made ready to run. This includes time a Pod spends waiting to be scheduled as well as the time spent downloading container images over the network.
+`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. That is, 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. This phase typically occurs due to an error in communicating with the node where the Pod should be running.
+`Failed`    | All containers in the Pod have terminated, and at least one container has terminated in failure. That is, 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. This phase typically occurs due to an error in communicating with the node where the Pod should be running.
 -->
 取值 | 描述
 :-----|:-----------
@@ -176,6 +177,18 @@ Pod 被赋予一个可以体面终止的期限，默认为 30 秒。
 你可以使用 `--force` 参数来[强制终止 Pod](/zh-cn/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination-forced)。
 {{< /note >}}
 
+<!--
+Since Kubernetes 1.27, the kubelet transitions deleted pods, except for
+[static pods](/docs/tasks/configure-pod-container/static-pod/) and
+[force-deleted pods](/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination-forced)
+without a finalizer, to a terminal phase (`Failed` or `Succeeded` depending on
+the exit statuses of the pod containers) before their deletion from the API server.
+-->
+从 Kubernetes 1.27 开始，除了[静态 Pod](/zh-cn/docs/tasks/configure-pod-container/static-pod/)
+和没有 Finalizer 的[强制终止 Pod](/zh-cn/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination-forced)
+之外，`kubelet` 会将已删除的 Pod 转换到终止阶段
+（`Failed` 或 `Succeeded` 具体取决于 Pod 容器的退出状态），然后再从 API 服务器中删除。
+
 <!--
 If a node dies or is disconnected from the rest of the cluster, Kubernetes
 applies a policy for setting the `phase` of all Pods on the lost node to Failed.
@@ -551,9 +564,6 @@ Each probe must define exactly one of these four mechanisms:
   [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
@@ -581,8 +591,6 @@ Each probe must define exactly one of these four mechanisms:
   目标应该实现
   [gRPC 健康检查](https://grpc.io/grpc/core/md_doc_health-checking.html)。
   如果响应的状态是 "SERVING"，则认为诊断成功。
-  gRPC 探针是一个 Alpha 特性，只有在你启用了
-  "GRPCContainerProbe" [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)时才能使用。
 
 `httpGet`
 : 对容器的 IP 地址上指定端口和路径执行 HTTP `GET` 请求。如果响应的状态码大于等于 200
@@ -895,27 +903,47 @@ An example flow:
       {{< /note >}}
 
 <!--
-1. At the same time as the kubelet is starting graceful shutdown, the control plane removes that
-   shutting-down Pod from EndpointSlice (and Endpoints) objects where these represent
+1. At the same time as the kubelet is starting graceful shutdown of the Pod, the control plane evaluates whether
+   to remove that shutting-down Pod from EndpointSlice (and Endpoints) objects, where those objects represent
    a {{< glossary_tooltip term_id="service" text="Service" >}} with a configured
    {{< glossary_tooltip text="selector" term_id="selector" >}}.
    {{< glossary_tooltip text="ReplicaSets" term_id="replica-set" >}} and other workload resources
    no longer treat the shutting-down Pod as a valid, in-service replica. Pods that shut down slowly
-   cannot continue to serve traffic as load balancers (like the service proxy) remove the Pod from
-   the list of endpoints as soon as the termination grace period _begins_.
+   should not continue to serve regular traffic and should start terminating and finish processing open connections.
+   Some applications need to go beyond finishing open connections and need more graceful termination -
+   for example: session draining and completion. Any endpoints that represent the terminating pods
+   are not immediately removed from EndpointSlices,
+   and a status indicating [terminating state](/docs/concepts/services-networking/endpoint-slices/#conditions)
+   is exposed from the EndpointSlice API (and the legacy Endpoints API). Terminating
+   endpoints always have their `ready` status
+   as `false` (for backward compatibility with versions before 1.26),
+   so load balancers will not use it for regular traffic.
+   If traffic draining on terminating pod is needed, the actual readiness can be checked as a condition `serving`.
+   You can find more details on how to implement connections draining
+   in the tutorial [Pods And Endpoints Termination Flow](/docs/tutorials/services/pods-and-endpoint-termination-flow/)
 -->
-3. 在 `kubelet` 启动体面关闭逻辑的同时，控制面会将关闭的 Pod 从对应的
-   EndpointSlice（和 Endpoints）对象中移除，过滤条件是 Pod
+3. 在 `kubelet` 启动 Pod 的体面关闭逻辑的同时，控制平面会评估是否将关闭的
+   Pod 从对应的 EndpointSlice（和端点）对象中移除，过滤条件是 Pod
    被对应的{{< glossary_tooltip term_id="service" text="服务" >}}以某
    {{< glossary_tooltip text="选择算符" term_id="selector" >}}选定。
    {{< glossary_tooltip text="ReplicaSet" term_id="replica-set" >}}
    和其他工作负载资源不再将关闭进程中的 Pod 视为合法的、能够提供服务的副本。
-   关闭动作很慢的 Pod 也无法继续处理请求数据，
-   因为负载均衡器（例如服务代理）已经在终止宽限期开始的时候将其从端点列表中移除。
+   关闭动作很慢的 Pod 不应继续处理常规服务请求，而应开始终止并完成对打开的连接的处理。
+   一些应用程序不仅需要完成对打开的连接的处理，还需要更进一步的体面终止逻辑 -
+   比如：排空和完成会话。任何正在终止的 Pod 所对应的端点都不会立即从 EndpointSlice
+   中被删除，EndpointSlice API（以及传统的 Endpoints API）会公开一个状态来指示其处于
+   [终止状态](/zh-cn/docs/concepts/services-networking/endpoint-slices/#conditions)。
+   正在终止的端点始终将其 `ready` 状态设置为 `false`（为了向后兼容 1.26 之前的版本），
+   因此负载均衡器不会将其用于常规流量。
+   如果需要排空正被终止的 Pod 上的流量，可以将 `serving` 状况作为实际的就绪状态。
+   你可以在教程
+   [探索 Pod 及其端点的终止行为](/zh-cn/docs/tutorials/services/pods-and-endpoint-termination-flow/)
+   中找到有关如何实现连接排空的更多详细信息。
+
    {{<note>}}
    <!--
    If you don't have the `EndpointSliceTerminatingCondition` feature gate enabled
-   in your cluster (the gate is on by default from Kubernetes 1.22, and locked to default in 1.26), then the    Kubernetes control
+   in your cluster (the gate is on by default from Kubernetes 1.22, and locked to default in 1.26), then the Kubernetes control
    plane removes a Pod from any relevant EndpointSlices as soon as the Pod's
    termination grace period _begins_. The behavior above is described when the
    feature gate `EndpointSliceTerminatingCondition` is enabled.
@@ -931,6 +959,8 @@ An example flow:
 1. When the grace period expires, the kubelet triggers forcible shutdown. The container runtime sends
    `SIGKILL` to any processes still running in any container in the Pod.
    The kubelet also cleans up a hidden `pause` container if that container runtime uses one.
+1. The kubelet transitions the pod into a terminal phase (`Failed` or `Succeeded` depending on
+   the end state of its containers). This step is guaranteed since version 1.27.
 1. The kubelet triggers forcible removal of Pod object from the API server, by setting grace period
    to 0 (immediate deletion).
 1. The API server deletes the Pod's API object, which is then no longer visible from any client.
@@ -939,6 +969,9 @@ An example flow:
    中所有容器内仍在运行的进程发送 `SIGKILL` 信号。
    `kubelet` 也会清理隐藏的 `pause` 容器，如果容器运行时使用了这种容器的话。
 
+1. `kubelet` 将 Pod 转换到终止阶段（`Failed` 或 `Succeeded` 具体取决于其容器的结束状态）。
+    这一步从 1.27 版本开始得到保证。
+
 1. `kubelet` 触发强制从 API 服务器上删除 Pod 对象的逻辑，并将体面终止限期设置为 0
    （这意味着马上删除）。
 

From 8dd85a67bd68e93790d94fce84fb790b8480f558 Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Mon, 17 Apr 2023 22:02:36 +0800
Subject: [PATCH 230/272] sync release-managers.md

sync release-managers.md
---
 content/zh-cn/releases/release-managers.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/zh-cn/releases/release-managers.md b/content/zh-cn/releases/release-managers.md
index 395f38cad90..5b17238c418 100644
--- a/content/zh-cn/releases/release-managers.md
+++ b/content/zh-cn/releases/release-managers.md
@@ -172,6 +172,7 @@ GitHub 访问控制：[@kubernetes/release-managers](https://github.com/orgs/kub
 GitHub 提及：[@kubernetes/release-engineering](https://github.com/orgs/kubernetes/teams/release-engineering)
 
 - Adolfo García Veytia ([@puerco](https://github.com/puerco))
+- Cici Huang ([@cici37](https://github.com/cici37))
 - Carlos Panato ([@cpanato](https://github.com/cpanato))
 - Jeremy Rickard ([@jeremyrickard](https://github.com/jeremyrickard))
 - Marko Mudrinić ([@xmudrii](https://github.com/xmudrii))
@@ -247,7 +248,6 @@ GitHub Mentions: @kubernetes/release-engineering
 GitHub 提及：@kubernetes/release-engineering
 
 - Arnaud Meukam ([@ameukam](https://github.com/ameukam))
-- Cici Huang ([@cici37](https://github.com/cici37))
 - Jim Angel ([@jimangel](https://github.com/jimangel))
 - Joseph Sandoval ([@jrsapi](https://github.com/jrsapi))
 - Xander Grzywinski([@salaxander](https://github.com/salaxander))

From 1bfe310520181ed2f1cca5a44ecbd440e5718af8 Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Mon, 17 Apr 2023 22:07:19 +0800
Subject: [PATCH 231/272] sync horizontal-pod-autoscale.md

sync horizontal-pod-autoscale.md
---
 .../docs/tasks/run-application/horizontal-pod-autoscale.md      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/zh-cn/docs/tasks/run-application/horizontal-pod-autoscale.md b/content/zh-cn/docs/tasks/run-application/horizontal-pod-autoscale.md
index 2ef34b6544c..f4340a313db 100644
--- a/content/zh-cn/docs/tasks/run-application/horizontal-pod-autoscale.md
+++ b/content/zh-cn/docs/tasks/run-application/horizontal-pod-autoscale.md
@@ -493,7 +493,7 @@ pod usage is still within acceptable limits.
 -->
 ### 容器资源指标   {#container-resource-metrics}
 
-{{< feature-state for_k8s_version="v1.20" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
 
 <!--
 The HorizontalPodAutoscaler API also supports a container metric source where the HPA can track the

From d6ba23f7a87d7c6edb004797b04a213209e635a7 Mon Sep 17 00:00:00 2001
From: Lichao <106173220+lichao127@users.noreply.github.com>
Date: Wed, 12 Apr 2023 22:17:26 -0700
Subject: [PATCH 232/272] add instructions to disable swap

---
 .../production-environment/tools/kubeadm/install-kubeadm.md      | 1 +
 1 file changed, 1 insertion(+)

diff --git a/content/en/docs/setup/production-environment/tools/kubeadm/install-kubeadm.md b/content/en/docs/setup/production-environment/tools/kubeadm/install-kubeadm.md
index 01f0d75f7d8..eae4cb3a7dd 100644
--- a/content/en/docs/setup/production-environment/tools/kubeadm/install-kubeadm.md
+++ b/content/en/docs/setup/production-environment/tools/kubeadm/install-kubeadm.md
@@ -27,6 +27,7 @@ see the [Creating a cluster with kubeadm](/docs/setup/production-environment/too
 * Unique hostname, MAC address, and product_uuid for every node. See [here](#verify-mac-address) for more details.
 * Certain ports are open on your machines. See [here](#check-required-ports) for more details.
 * Swap disabled. You **MUST** disable swap in order for the kubelet to work properly.
+    * For example, `sudo swapoff -a` will disable swapping temporarily. To make this change persistent across reboots, make sure swap is disabled in config files like `/etc/fstab`, `systemd.swap`, depending how it was configured on your system.
 
 <!-- steps -->
 

From 6e985800b286f216ada24e7c2e8209e47014ace8 Mon Sep 17 00:00:00 2001
From: Arhell <arhell333@gmail.com>
Date: Tue, 18 Apr 2023 00:28:03 +0300
Subject: [PATCH 233/272] [id] Fix mismatch in Labels and Selectors concept
 page

---
 .../id/docs/concepts/overview/working-with-objects/labels.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/id/docs/concepts/overview/working-with-objects/labels.md b/content/id/docs/concepts/overview/working-with-objects/labels.md
index 90f58d5a5a5..dc4c16da733 100644
--- a/content/id/docs/concepts/overview/working-with-objects/labels.md
+++ b/content/id/docs/concepts/overview/working-with-objects/labels.md
@@ -172,7 +172,7 @@ Seperti yang telah disebutkan sebelumnya, kondisi _set-based_ lebih ekspresif.
 kubectl get pods -l 'environment in (production, qa)'
 ```
 
-atau membatasi pencocokan negatif dengan operator _exists_:
+atau membatasi pencocokan negatif dengan operator _notin_:
 
 ```shell
 kubectl get pods -l 'environment,environment notin (frontend)'

From 53ca344721be1df7db20ae5fcf129bd250b4e53d Mon Sep 17 00:00:00 2001
From: Paul Sanford <me@paulsanford.net>
Date: Mon, 17 Apr 2023 16:52:42 -0600
Subject: [PATCH 234/272] Fix references to exclude-from-external-load-balancer
 (add s)

The annotation is "node.kubernetes.io/exclude-from-external-load-balancers," but the docs refer to it twice as "node.kubernetes.io/exclude-from-external-load-balancer" (without the s at the end). This change fixes those references.
---
 content/en/docs/reference/labels-annotations-taints/_index.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/en/docs/reference/labels-annotations-taints/_index.md b/content/en/docs/reference/labels-annotations-taints/_index.md
index 5ede3e30731..0ef92685794 100644
--- a/content/en/docs/reference/labels-annotations-taints/_index.md
+++ b/content/en/docs/reference/labels-annotations-taints/_index.md
@@ -339,9 +339,9 @@ Used on: ServiceAccount
 
 The value for this annotation must be **true** to take effect. This annotation indicates that pods running as this service account may only reference Secret API objects specified in the service account's `secrets` field.
 
-### node.kubernetes.io/exclude-from-external-load-balancer
+### node.kubernetes.io/exclude-from-external-load-balancers
 
-Example: `node.kubernetes.io/exclude-from-external-load-balancer`
+Example: `node.kubernetes.io/exclude-from-external-load-balancers`
 
 Used on: Node
 

From 38c756b3b261f7637a647a0904d72ea9b39acf0d Mon Sep 17 00:00:00 2001
From: ydFu <ader.ydfu@gmail.com>
Date: Tue, 18 Apr 2023 14:56:38 +0800
Subject: [PATCH 235/272] [zh] sync
 tasks/configure-pod-container/migrate-from-psp.md

Signed-off-by: ydFu <ader.ydfu@gmail.com>
---
 .../docs/tasks/configure-pod-container/migrate-from-psp.md     | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/content/zh-cn/docs/tasks/configure-pod-container/migrate-from-psp.md b/content/zh-cn/docs/tasks/configure-pod-container/migrate-from-psp.md
index e99a2c04b1b..d5da098123c 100644
--- a/content/zh-cn/docs/tasks/configure-pod-container/migrate-from-psp.md
+++ b/content/zh-cn/docs/tasks/configure-pod-container/migrate-from-psp.md
@@ -12,6 +12,7 @@ reviewers:
 - liggitt
 content_type: task
 min-kubernetes-server-version: v1.22
+weight: 260
 -->
 
 <!-- overview -->
@@ -388,7 +389,7 @@ For each updated PodSecurityPolicy:
 3. Create the new PodSecurityPolicies. If any Roles or ClusterRoles are granting `use` on all PSPs
    this could cause the new PSPs to be used instead of their mutating counter-parts.
 4. Update your authorization to grant access to the new PSPs. In RBAC this means updating any Roles
-   or ClusterRoles that grant the `use` permision on the original PSP to also grant it to the
+   or ClusterRoles that grant the `use` permission on the original PSP to also grant it to the
    updated PSP.
 -->
 3. 创建新的 PodSecurityPolicy。如果存在 Role 或 ClusterRole 对象为用户授权了在所有 PSP

From 4e239493a2d02f9de663d13b9170bcd3ecbf7135 Mon Sep 17 00:00:00 2001
From: nishipy <goodisonev4@gmail.com>
Date: Tue, 18 Apr 2023 07:56:09 -0400
Subject: [PATCH 236/272] Update design doc reference link of PLEG

Signed-off-by: nishipy <goodisonev4@gmail.com>
---
 content/ru/docs/concepts/_index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/ru/docs/concepts/_index.md b/content/ru/docs/concepts/_index.md
index 93fbc731a10..19e42ed49e9 100644
--- a/content/ru/docs/concepts/_index.md
+++ b/content/ru/docs/concepts/_index.md
@@ -17,7 +17,7 @@ weight: 40
 
 Чтобы работать с Kubernetes, вы используете *объекты API Kubernetes* для описания *желаемого состояния вашего кластера*: какие приложения или другие рабочие нагрузки вы хотите запустить, какие образы контейнеров они используют, количество реплик, какие сетевые и дисковые ресурсы вы хотите использовать и сделать доступными и многое другое. Вы устанавливаете желаемое состояние, создавая объекты с помощью API Kubernetes, обычно через интерфейс командной строки `kubectl`. Вы также можете напрямую использовать API Kubernetes для взаимодействия с кластером и установки или изменения желаемого состояния.
 
-После того, как вы установили желаемое состояние, *Плоскость управления Kubernetes* заставляет текущее состояние кластера соответствовать желаемому состоянию с помощью генератора событий жизненного цикла подов ([Pod Lifecycle Event Generator, PLEG](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/node/pod-lifecycle-event-generator.md)). Для этого Kubernetes автоматически выполняет множество задач, таких как запуск или перезапуск контейнеров, масштабирование количества реплик данного приложения и многое другое. Плоскость управления Kubernetes состоит из набора процессов, запущенных в вашем кластере:
+После того, как вы установили желаемое состояние, *Плоскость управления Kubernetes* заставляет текущее состояние кластера соответствовать желаемому состоянию с помощью генератора событий жизненного цикла подов ([Pod Lifecycle Event Generator, PLEG](https://github.com/kubernetes/design-proposals-archive/blob/main/node/pod-lifecycle-event-generator.md)). Для этого Kubernetes автоматически выполняет множество задач, таких как запуск или перезапуск контейнеров, масштабирование количества реплик данного приложения и многое другое. Плоскость управления Kubernetes состоит из набора процессов, запущенных в вашем кластере:
 
 * **Мастер Kubernetes** — это коллекция из трех процессов, которые выполняются на одном узле в вашем кластере, который обозначен как главный узел. Это процессы: [kube-apiserver](/docs/admin/kube-apiserver/), [kube-controller-manager](/docs/admin/kube-controller-manager/) и [kube-scheduler](/docs/admin/kube-scheduler/).
 * Каждый отдельный неосновной узел в вашем кластере выполняет два процесса:

From b2a9c3cd75b1f3ae30c18b39f606d4a5c52f3a3b Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Tue, 18 Apr 2023 19:28:45 +0800
Subject: [PATCH 237/272] sync configure-pdb.md

sync configure-pdb.md
---
 .../zh-cn/docs/tasks/run-application/configure-pdb.md  | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/content/zh-cn/docs/tasks/run-application/configure-pdb.md b/content/zh-cn/docs/tasks/run-application/configure-pdb.md
index 6b2da2697c2..0fb6a139a23 100644
--- a/content/zh-cn/docs/tasks/run-application/configure-pdb.md
+++ b/content/zh-cn/docs/tasks/run-application/configure-pdb.md
@@ -429,18 +429,18 @@ These pods are tracked via `.status.currentHealthy` field in the PDB status.
 -->
 ## 不健康的 Pod 驱逐策略   {#unhealthy-pod-eviction-policy}
 
-{{< feature-state for_k8s_version="v1.26" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.26" state="beta" >}}
 
 {{< note >}}
 <!--
-In order to use this behavior, you must enable the `PDBUnhealthyPodEvictionPolicy`
+This feature is enabled by default. You can disable it by disabling the `PDBUnhealthyPodEvictionPolicy`
 [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
 on the [API server](/docs/reference/command-line-tools-reference/kube-apiserver/).
 -->
-为了使用此行为，你必须在
-[API 服务器](/zh-cn/docs/reference/command-line-tools-reference/kube-apiserver/)上启用
+此特性默认启用，你可以通过在
+[API 服务器](/zh-cn/docs/reference/command-line-tools-reference/kube-apiserver/)上禁用
 `PDBUnhealthyPodEvictionPolicy`
-[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)。
+[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)来禁用它。
 {{< /note >}}
 
 <!--

From 282a690377c0ea2b926d259aa9cbfd3d1ce4e3db Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Tue, 18 Apr 2023 19:35:55 +0800
Subject: [PATCH 238/272] sync user-namespaces.md

sync user-namespaces.md
---
 .../docs/tasks/configure-pod-container/user-namespaces.md   | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/content/zh-cn/docs/tasks/configure-pod-container/user-namespaces.md b/content/zh-cn/docs/tasks/configure-pod-container/user-namespaces.md
index 8b225ef8618..185003caec4 100644
--- a/content/zh-cn/docs/tasks/configure-pod-container/user-namespaces.md
+++ b/content/zh-cn/docs/tasks/configure-pod-container/user-namespaces.md
@@ -96,10 +96,10 @@ Pods, you also need to ensure that the user namespace Pods are
 
 <!--
 Please note that **if your container runtime doesn't support user namespaces, the
-new `pod.spec` field will be silently ignored and the pod will be created without
-user namespaces.**
+`hostUsers` field in the pod spec will be silently ignored and the pod will be
+created without user namespaces.**
 -->
-请注意 **如果你的容器运行时环境不支持用户名字空间，字段 `pod.spec` 将被忽略，
+请注意 **如果你的容器运行时环境不支持用户名字空间，那么 Pod 规约中的 `hostUsers` 字段将被静默忽略，
 并且系统会在没有用户名字空间的环境中创建 Pod。**
 
 <!-- steps -->

From 729689eeb5cc3d138539dd2d34a63f1333cb1ec0 Mon Sep 17 00:00:00 2001
From: Arhell <arhell333@gmail.com>
Date: Wed, 19 Apr 2023 00:20:15 +0300
Subject: [PATCH 239/272] [id] Fixed Calico Quickstart link

---
 .../network-policy-provider/calico-network-policy.md            | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/id/docs/tasks/administer-cluster/network-policy-provider/calico-network-policy.md b/content/id/docs/tasks/administer-cluster/network-policy-provider/calico-network-policy.md
index 9eb79e76769..a7a7bb457da 100644
--- a/content/id/docs/tasks/administer-cluster/network-policy-provider/calico-network-policy.md
+++ b/content/id/docs/tasks/administer-cluster/network-policy-provider/calico-network-policy.md
@@ -42,7 +42,7 @@ Putuskan apakah kamu ingin menggelar (_deploy_) sebuah klaster di [_cloud_](#mem
 
 Untuk membuat satu klaster Calico dengan hos tunggal dalam waktu lima belas menit dengan menggunakan kubeadm, silakan merujuk pada
 
-[Memulai cepat Calico](https://docs.projectcalico.org/latest/getting-started/kubernetes/).
+[Memulai cepat Calico](https://projectcalico.docs.tigera.io/getting-started/kubernetes/).
 
 
 ## {{% heading "whatsnext" %}}

From 06ac68baf6b1baaa1be0b7e6ed6c561b24810f6b Mon Sep 17 00:00:00 2001
From: windsonsea <haifeng.yao@daocloud.io>
Date: Tue, 18 Apr 2023 16:21:09 +0800
Subject: [PATCH 240/272] [zh] sync /tutorials/security/seccomp.md

---
 .../zh-cn/docs/tutorials/security/seccomp.md  | 98 ++++++++++---------
 1 file changed, 52 insertions(+), 46 deletions(-)

diff --git a/content/zh-cn/docs/tutorials/security/seccomp.md b/content/zh-cn/docs/tutorials/security/seccomp.md
index 6d469437853..08e8c28408b 100644
--- a/content/zh-cn/docs/tutorials/security/seccomp.md
+++ b/content/zh-cn/docs/tutorials/security/seccomp.md
@@ -33,7 +33,7 @@ profiles that give only the necessary privileges to your container processes.
 -->
 Seccomp 代表安全计算（Secure Computing）模式，自 2.6.12 版本以来，一直是 Linux 内核的一个特性。
 它可以用来沙箱化进程的权限，限制进程从用户态到内核态的调用。
-Kubernetes 能使你自动将加载到 {{< glossary_tooltip text="节点" term_id="node" >}}上的
+Kubernetes 能使你自动将加载到{{< glossary_tooltip text="节点" term_id="node" >}}上的
 seccomp 配置文件应用到你的 Pod 和容器。
 
 识别你的工作负载所需要的权限是很困难的。在本篇教程中，
@@ -137,6 +137,7 @@ ls profiles
 You should see three profiles listed at the end of the final step:
 -->
 你应该看到在最后一步的末尾列出有三个配置文件：
+
 ```
 audit.json  fine-grained.json  violation.json
 ```
@@ -150,7 +151,6 @@ so each node of the cluster is a container. This allows for files
 to be mounted in the filesystem of each container similar to loading files
 onto a node.
 -->
-
 ## 使用 kind 创建本地 Kubernetes 集群 {#create-a-local-kubernetes-cluster-with-kind}
 
 为简单起见，[kind](https://kind.sigs.k8s.io/) 可用来创建加载了 seccomp 配置文件的单节点集群。
@@ -163,6 +163,7 @@ Kind 在 Docker 中运行 Kubernetes，因此集群的每个节点都是一个
 Download that example kind configuration, and save it to a file named `kind.yaml`:
 -->
 下载该示例 kind 配置，并将其保存到名为 `kind.yaml` 的文件中：
+
 ```shell
 curl -L -O https://k8s.io/examples/pods/security/seccomp/kind.yaml
 ```
@@ -233,6 +234,12 @@ of the kubelet. Use `docker exec` to run a command in the Pod:
 你应该会看到 `profiles/` 目录已成功加载到 kubelet 的默认 seccomp 路径中。
 使用 `docker exec` 在 Pod 中运行命令：
 
+<!--
+```shell
+# Change 6a96207fed4b to the container ID you saw from "docker ps"
+docker exec -it 6a96207fed4b ls /var/lib/kubelet/seccomp/profiles
+```
+-->
 ```shell
 # 将 6a96207fed4b 更改为你从 “docker ps” 看到的容器 ID
 docker exec -it 6a96207fed4b ls /var/lib/kubelet/seccomp/profiles
@@ -253,21 +260,17 @@ running within kind.
 -->
 ## 启用使用 `RuntimeDefault` 作为所有工作负载的默认 seccomp 配置文件 {#enable-runtimedefault-as-default}
 
-{{< feature-state state="beta" for_k8s_version="v1.25" >}}
+{{< feature-state state="stable" for_k8s_version="v1.27" >}}
 
 <!-- 
-To use seccomp profile defaulting, you must run the kubelet with the `SeccompDefault`
-[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) enabled
-(this is the default). You must also explicitly enable the defaulting behavior for each
-node where you want to use this with the corresponding `--seccomp-default`
-[command line flag](/docs/reference/command-line-tools-reference/kubelet).
-Both have to be enabled simultaneously to use the feature.
+To use seccomp profile defaulting, you must run the kubelet with the
+`--seccomp-default`
+[command line flag](/docs/reference/command-line-tools-reference/kubelet)
+enabled for each node where you want to use it. 
 -->
-要使用 Seccomp（安全计算模式）配置文件来设定默认值，你必须要在启用 `SeccompDefault`
-[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)的情况下运行 kubelet
-（这是默认值）。
-你还必须显式地启用每个节点的默认行为，以及相应的
-`--seccomp-default` [命令行标志](/zh-cn/docs/reference/command-line-tools-reference/kubelet)。两者必须同时启用才能使用该特性。
+要使用 Seccomp（安全计算模式）配置文件采用默认设置这一行为，你必须使用在想要启用此行为的每个节点上启用
+`--seccomp-default`
+[命令行标志](/zh-cn/docs/reference/command-line-tools-reference/kubelet)来运行 kubelet。
 
 <!-- 
 If enabled, the kubelet will use the `RuntimeDefault` seccomp profile by default, which is
@@ -337,14 +340,11 @@ Kubernetes 项目建议你在部分节点上启用此特性门控，
 <!--
 Kubernetes {{< skew currentVersion >}} lets you configure the seccomp profile
 that applies when the spec for a Pod doesn't define a specific seccomp profile.
-This is a beta feature and the corresponding `SeccompDefault` [feature
-gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled by
-default. However, you still need to enable this defaulting for each node where
-you would like to use it.
+However, you still need to enable this defaulting for each node where you would
+like to use it.
 -->
 Kubernetes {{< skew currentVersion >}} 允许你配置 Seccomp 配置文件，
 当 Pod 的规约未定义特定的 Seccomp 配置文件时应用该配置文件。
-这是一个 Beta 特性，默认启用相应的 `SeccompDefault` [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)。
 但是，你仍然需要为要使用它的每个节点启用此默认设置。
 
 <!--
@@ -368,8 +368,6 @@ the minimum required Kubernetes version and enables the `SeccompDefault` feature
 ```yaml
 kind: Cluster
 apiVersion: kind.x-k8s.io/v1alpha4
-featureGates:
-  SeccompDefault: true
 nodes:
   - role: control-plane
     image: kindest/node:v1.23.0@sha256:49824ab1727c04e56a21a5d8372a402fcd32ea51ac96a2706a12af38934f81ac
@@ -386,7 +384,6 @@ nodes:
         kind: JoinConfiguration
         nodeRegistration:
           kubeletExtraArgs:
-            feature-gates: SeccompDefault=true
             seccomp-default: "true"
 ```
 
@@ -439,11 +436,11 @@ 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/)
+If you have the `seccompDefault` [configuration](/docs/reference/config-api/kubelet-config.v1beta1/)
 enabled, then Pods use the `RuntimeDefault` seccomp profile whenever
 no other seccomp profile is specified. Otherwise, the default is `Unconfined`.
 -->
-如果你已经启用了 `SeccompDefault` [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)，
+如果你已经启用了 `seccompDefault` [配置](/zh-cn/docs/reference/config-api/kubelet-config.v1beta1/)，
 只要没有指定其他 seccomp 配置文件，那么 Pod 就会使用 `RuntimeDefault` seccomp 配置文件。
 否则，默认值为 `Unconfined`。
 {{< /note >}}
@@ -506,26 +503,15 @@ Here's a manifest for that Pod:
 
 {{< 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 a future release of Kubernetes. Please always use
-the native API fields in favor of the annotations.
-
-Since Kubernetes v1.25, kubelets no longer support the annotations, use of the
-annotations in static pods is no longer supported, and the seccomp annotations
-are no longer auto-populated when pods with seccomp fields are created.
-Auto-population of the seccomp fields from the annotations is planned to be
-removed in a future release.
+Older versions of Kubernetes allowed you to configure seccomp
+behavior using {{< glossary_tooltip text="annotations" term_id="annotation" >}}.
+Kubernetes {{< skew currentVersion >}} only supports using fields within
+`.spec.securityContext` to configure seccomp, and this tutorial explains that
+approach.
 -->
-已弃用的 seccomp 注解 `seccomp.security.alpha.kubernetes.io/pod`（针对整个 Pod）和
-`container.seccomp.security.alpha.kubernetes.io/[name]`（针对单个容器）
-将随着未来 Kubernetes 的发布而被删除。
-请在可能的情况下使用原生 API 字段而不是注解。
-
-从 Kubernetes v1.25 开始，kubelet 不再支持这些注解，
-也不再支持在静态 Pod 中使用注解，并且当创建带有 seccomp 字段的 Pod 时不再自动填充 seccomp 注解。
-从注释中自动填充 seccomp 字段的特性，将计划在未来的版本中删除。
+旧版本的 Kubernetes 允许你使用{{< glossary_tooltip text="注解" term_id="annotation" >}}配置
+seccomp 行为。Kubernetes {{< skew currentVersion >}} 仅支持使用位于 `.spec.securityContext`
+内的字段来配置 seccomp。本教程将阐述这个方法。
 {{< /note >}}
 
 <!--
@@ -592,6 +578,12 @@ container belonging to that control plane container:
 现在，你可以使用 `curl` 从 kind 控制平面容器内部访问该端点，位于该服务所公开的端口上。
 使用 `docker exec` 在属于该控制平面容器的容器中运行 `curl` 命令：
 
+<!--
+```shell
+# Change 6a96207fed4b to the control plane container ID you saw from "docker ps"
+docker exec -it 6a96207fed4b curl localhost:32373
+```
+-->
 ```shell
 # 将 6a96207fed4b 更改为你从 “docker ps” 看到的控制平面容器 ID
 docker exec -it 6a96207fed4b curl localhost:32373
@@ -625,6 +617,7 @@ For example:
 如果你在控制平面容器中 `curl` 端点，你会看到更多的写入。
 
 例如：
+
 ```
 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
@@ -683,7 +676,7 @@ kubectl apply -f https://k8s.io/examples/pods/security/seccomp/ga/violation-pod.
 The Pod creates, but there is an issue.
 If you check the status of the Pod, you should see that it failed to start.
 -->
-Pod 创建，但存在问题。
+Pod 已创建，但存在问题。
 如果你检查 Pod 状态，你应该看到它没有启动。
 
 ```shell
@@ -732,7 +725,7 @@ The manifest for this example is:
 如果你看一看 `fine-grained.json` 配置文件，
 你会注意到第一个示例的 syslog 中看到的一些系统调用，
 其中配置文件设置为 `"defaultAction": "SCMP_ACT_LOG"`。
-现在的配置文件设置 `"defaultAction": "SCMP_ACT_ERRNO"`,
+现在的配置文件设置 `"defaultAction": "SCMP_ACT_ERRNO"`，
 但在 `"action": "SCMP_ACT_ALLOW"` 块中明确允许一组系统调用。
 理想情况下，容器将成功运行，并且你看到没有消息发送到 `syslog`。
 
@@ -769,6 +762,12 @@ mention calls from `http-echo`:
 -->
 打开一个新的终端窗口并使用 `tail` 来监视提到来自 `http-echo` 的调用的日志条目：
 
+<!--
+```shell
+# The log path on your computer might be different from "/var/log/syslog"
+tail -f /var/log/syslog | grep 'http-echo'
+```
+-->
 ```shell
 # 你计算机上的日志路径可能与 “/var/log/syslog” 不同
 tail -f /var/log/syslog | grep 'http-echo'
@@ -796,6 +795,7 @@ 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
@@ -806,6 +806,12 @@ Use `curl` to access that endpoint from inside the kind control plane container:
 -->
 使用 `curl` 从 kind 控制平面容器内部访问端点：
 
+<!--
+```shell
+# Change 6a96207fed4b to the control plane container ID you saw from "docker ps"
+docker exec -it 6a96207fed4b curl localhost:32373
+```
+-->
 ```shell
 # 将 6a96207fed4b 更改为你从 “docker ps” 看到的控制平面容器 ID
 docker exec -it 6a96207fed4b curl localhost:32373
@@ -847,4 +853,4 @@ You can learn more about Linux seccomp:
 你可以了解有关 Linux seccomp 的更多信息：
 
 * [seccomp 概述](https://lwn.net/Articles/656307/)
-* [Docker 的 Seccomp 安全配置文件](https://docs.docker.com/engine/security/seccomp/)
\ No newline at end of file
+* [Docker 的 Seccomp 安全配置文件](https://docs.docker.com/engine/security/seccomp/)

From ea3440dca92862c823f1cba17f13df7282625640 Mon Sep 17 00:00:00 2001
From: windsonsea <haifeng.yao@daocloud.io>
Date: Tue, 18 Apr 2023 13:51:15 +0800
Subject: [PATCH 241/272] [zh] sync
 /kubernetes-api/cluster-resources/lease-v1.md

---
 .../cluster-resources/lease-v1.md             | 329 ++++--------------
 1 file changed, 73 insertions(+), 256 deletions(-)

diff --git a/content/zh-cn/docs/reference/kubernetes-api/cluster-resources/lease-v1.md b/content/zh-cn/docs/reference/kubernetes-api/cluster-resources/lease-v1.md
index 03c44053d26..2ca911ff9b1 100644
--- a/content/zh-cn/docs/reference/kubernetes-api/cluster-resources/lease-v1.md
+++ b/content/zh-cn/docs/reference/kubernetes-api/cluster-resources/lease-v1.md
@@ -8,59 +8,56 @@ description: "Lease 定义了租约的概念。"
 title: "Lease"
 weight: 5
 ---
-
 <!--
-The file is auto-generated from the Go source code of the component using a generic
-[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
-to generate the reference documentation, please read
-[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
-To update the reference content, please follow the 
-[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
-guide. You can file document formatting bugs against the
-[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
+api_metadata:
+  apiVersion: "coordination.k8s.io/v1"
+  import: "k8s.io/api/coordination/v1"
+  kind: "Lease"
+content_type: "api_reference"
+description: "Lease defines a lease concept."
+title: "Lease"
+weight: 5
+auto_generated: true
 -->
 
 `apiVersion: coordination.k8s.io/v1`
 
 `import "k8s.io/api/coordination/v1"`
 
-
 ## Lease {#Lease}
+
 <!--
 Lease defines a lease concept.
 -->
 Lease 定义了租约的概念。
+
 <hr>
 
 - **apiVersion**: coordination.k8s.io/v1
 
-
 - **kind**: Lease
 
-
 - **metadata** (<a href="{{< ref "../common-definitions/object-meta#ObjectMeta" >}}">ObjectMeta</a>)
 
-<!--
+  <!--
   More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
--->
+  -->
   更多信息： https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
 
 - **spec** (<a href="{{< ref "../cluster-resources/lease-v1#LeaseSpec" >}}">LeaseSpec</a>)
 
-<!--
-  Specification of the Lease. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
--->
-  Lease 规范。更多信息： https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
-
-
-
+  <!--
+  spec contains the specification of the Lease. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
+  -->
+  spec 包含 Lease 的规约。更多信息：
+  https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
 
 ## LeaseSpec {#LeaseSpec}
 
 <!--
 LeaseSpec is a specification of a Lease.
 -->
-LeaseSpec 是一个 Lease 的规范。
+LeaseSpec 是一个 Lease 的规约。
 
 <hr>
 
@@ -75,21 +72,6 @@ LeaseSpec 是一个 Lease 的规范。
 - **holderIdentity** (string)
 
   holderIdentity contains the identity of the holder of a current lease.
-
-- **leaseDurationSeconds** (int32)
-
-  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.
-
-- **leaseTransitions** (int32)
-
-  leaseTransitions is the number of transitions of a lease between holders.
-
-- **renewTime** (MicroTime)
-
-  renewTime is a time when the current holder of a lease has last updated the lease.
-
-  <a name="MicroTime"></a>
-  *MicroTime is version of Time with microsecond level precision.*
 -->
 - **acquireTime** (MicroTime)
 
@@ -102,13 +84,29 @@ LeaseSpec 是一个 Lease 的规范。
 
   holderIdentity 包含当前租约持有人的身份。
 
+<!--
 - **leaseDurationSeconds** (int32)
 
-  leaseDurationSeconds 是租约候选人需要等待强制获取租约的持续时间。这是相对于上次观察到的更新时间的度量。
+  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.
 
 - **leaseTransitions** (int32)
 
-  LeasetTransitions 是租约持有人之间的转换次数。
+  leaseTransitions is the number of transitions of a lease between holders.
+
+- **renewTime** (MicroTime)
+
+  renewTime is a time when the current holder of a lease has last updated the lease.
+
+  <a name="MicroTime"></a>
+  *MicroTime is version of Time with microsecond level precision.*
+-->
+- **leaseDurationSeconds** (int32)
+
+  leaseDurationSeconds 是租约候选人需要等待强制获取租约的持续时间。这是相对于上次观察到的 renewTime 的度量。
+
+- **leaseTransitions** (int32)
+
+  leaseTransitions 是租约持有人之间的转换次数。
 
 - **renewTime** (MicroTime)
 
@@ -117,9 +115,6 @@ LeaseSpec 是一个 Lease 的规范。
   <a name="MicroTime"></a>
   **MicroTime 是具有微秒级精度的时间版本。**
 
-
-
-
 ## LeaseList {#LeaseList}
 
 <!--
@@ -131,38 +126,30 @@ LeaseList 是 Lease 对象的列表。
 
 - **apiVersion**: coordination.k8s.io/v1
 
-
 - **kind**: LeaseList
 
-
 - **metadata** (<a href="{{< ref "../common-definitions/list-meta#ListMeta" >}}">ListMeta</a>)
 
-<!--
+  <!--
   Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
--->
-   标准列表元数据。更多信息： https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
+  -->
+  标准的列表元数据。更多信息：
+  https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
 
 - **items** ([]<a href="{{< ref "../cluster-resources/lease-v1#Lease" >}}">Lease</a>), required
 
-<!--
-  Items is a list of schema objects.
--->
-  Items 是架构对象的列表。
-
-
+  <!--
+  items is a list of schema objects.
+  -->
+  items 是架构对象的列表。
 
 <!--
 ## Operations {#Operations}
 -->
 ## 操作   {#operations}
 
-
 <hr>
 
-
-
-
-
 <!--
 ### `get` read the specified Lease
 
@@ -172,7 +159,7 @@ GET /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases/{name}
 
 #### Parameters
 -->
-### `get` 读取指定的租赁
+### `get` 读取指定的 Lease
 
 #### HTTP 请求
 
@@ -185,19 +172,17 @@ GET /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases/{name}
 
   name of the Lease
 
-
 - **namespace** (*in path*): string, required
 
   <a href="{{< ref "../common-parameters/common-parameters#namespace" >}}">namespace</a>
 
-
 - **pretty** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
 -->
 - **name** (**路径参数**): string, 必需
 
-  Lease 名称
+  Lease 名称。
 
 - **namespace** (**路径参数**): string, 必需
 
@@ -232,99 +217,84 @@ GET /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases
 <!--
 #### Parameters
 
-
 - **namespace** (*in path*): string, required
 
   <a href="{{< ref "../common-parameters/common-parameters#namespace" >}}">namespace</a>
 
-
 - **allowWatchBookmarks** (*in query*): boolean
 
   <a href="{{< ref "../common-parameters/common-parameters#allowWatchBookmarks" >}}">allowWatchBookmarks</a>
 
-
 - **continue** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#continue" >}}">continue</a>
 
-
 - **fieldSelector** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldSelector" >}}">fieldSelector</a>
 
-
 - **labelSelector** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#labelSelector" >}}">labelSelector</a>
 
-
 - **limit** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#limit" >}}">limit</a>
 
-
 - **pretty** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
 
-
 - **resourceVersion** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersion" >}}">resourceVersion</a>
 
-
 - **resourceVersionMatch** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
 
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
 
-
 - **watch** (*in query*): boolean
 
   <a href="{{< ref "../common-parameters/common-parameters#watch" >}}">watch</a>
 -->
 #### 参数
 
-
 - **namespace** (**路径参数**): string, 必需
 
   <a href="{{< ref "../common-parameters/common-parameters#namespace" >}}">namespace</a>
 
-
 - **allowWatchBookmarks** (**查询参数**): boolean
 
   <a href="{{< ref "../common-parameters/common-parameters#allowWatchBookmarks" >}}">allowWatchBookmarks</a>
 
-
 - **continue** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#continue" >}}">continue</a>
 
-
 - **fieldSelector** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldSelector" >}}">fieldSelector</a>
 
-
 - **labelSelector** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#labelSelector" >}}">labelSelector</a>
 
-
 - **limit** (**查询参数**): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#limit" >}}">limit</a>
 
-
 - **pretty** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
 
-
 - **resourceVersion** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersion" >}}">resourceVersion</a>
@@ -333,12 +303,14 @@ GET /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases
 
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
+- **sendInitialEvents** (**查询参数**): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
 
 - **timeoutSeconds** (**查询参数**): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
 
-
 - **watch** (**查询参数**): boolean
 
   <a href="{{< ref "../common-parameters/common-parameters#watch" >}}">watch</a>
@@ -366,84 +338,73 @@ GET /apis/coordination.k8s.io/v1/leases
 <!--
 #### Parameters
 
-
 - **allowWatchBookmarks** (*in query*): boolean
 
   <a href="{{< ref "../common-parameters/common-parameters#allowWatchBookmarks" >}}">allowWatchBookmarks</a>
 
-
 - **continue** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#continue" >}}">continue</a>
 
-
 - **fieldSelector** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldSelector" >}}">fieldSelector</a>
 
-
 - **labelSelector** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#labelSelector" >}}">labelSelector</a>
 
-
 - **limit** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#limit" >}}">limit</a>
 
-
 - **pretty** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
 
-
 - **resourceVersion** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersion" >}}">resourceVersion</a>
 
-
 - **resourceVersionMatch** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
 
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
 
-
 - **watch** (*in query*): boolean
 
   <a href="{{< ref "../common-parameters/common-parameters#watch" >}}">watch</a>
+
 -->
 #### 参数
 
-
 - **allowWatchBookmarks** (**查询参数**): boolean
 
   <a href="{{< ref "../common-parameters/common-parameters#allowWatchBookmarks" >}}">allowWatchBookmarks</a>
 
-
 - **continue** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#continue" >}}">continue</a>
 
-
 - **fieldSelector** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldSelector" >}}">fieldSelector</a>
 
-
 - **labelSelector** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#labelSelector" >}}">labelSelector</a>
 
-
 - **limit** (**查询参数**): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#limit" >}}">limit</a>
 
-
 - **pretty** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
@@ -456,27 +417,23 @@ GET /apis/coordination.k8s.io/v1/leases
 
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
+- **sendInitialEvents** (**查询参数**): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
 
 - **timeoutSeconds** (**查询参数**): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
 
-
 - **watch** (**查询参数**): boolean
 
   <a href="{{< ref "../common-parameters/common-parameters#watch" >}}">watch</a>
 
 <!--
 #### Response
-
-
-200 (<a href="{{< ref "../cluster-resources/lease-v1#LeaseList" >}}">LeaseList</a>): OK
-
-401: Unauthorized
 -->
 #### 响应
 
-
 200 (<a href="{{< ref "../cluster-resources/lease-v1#LeaseList" >}}">LeaseList</a>): OK
 
 401: Unauthorized
@@ -485,8 +442,6 @@ GET /apis/coordination.k8s.io/v1/leases
 ### `create` create a Lease
 
 #### HTTP Request
-
-POST /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases
 -->
 ### `create` 创建 Lease
 
@@ -497,83 +452,57 @@ POST /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases
 <!--
 #### Parameters
 
-
 - **namespace** (*in path*): string, required
 
   <a href="{{< ref "../common-parameters/common-parameters#namespace" >}}">namespace</a>
 
-
 - **body**: <a href="{{< ref "../cluster-resources/lease-v1#Lease" >}}">Lease</a>, required
 
-  
-
-
 - **dryRun** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
 
-
 - **fieldManager** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
 
-
 - **fieldValidation** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
 
-
 - **pretty** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
 -->
 #### 参数
 
-
 - **namespace** (**路径参数**): string, 必需
 
   <a href="{{< ref "../common-parameters/common-parameters#namespace" >}}">namespace</a>
 
-
 - **body**: <a href="{{< ref "../cluster-resources/lease-v1#Lease" >}}">Lease</a>, 必需
 
-  
-
-
 - **dryRun** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
 
-
 - **fieldManager** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
 
-
 - **fieldValidation** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
 
-
 - **pretty** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
 
 <!--
 #### Response
-
-
-200 (<a href="{{< ref "../cluster-resources/lease-v1#Lease" >}}">Lease</a>): OK
-
-201 (<a href="{{< ref "../cluster-resources/lease-v1#Lease" >}}">Lease</a>): Created
-
-202 (<a href="{{< ref "../cluster-resources/lease-v1#Lease" >}}">Lease</a>): Accepted
-
-401: Unauthorized
 -->
 #### 响应
 
-
 200 (<a href="{{< ref "../cluster-resources/lease-v1#Lease" >}}">Lease</a>): OK
 
 201 (<a href="{{< ref "../cluster-resources/lease-v1#Lease" >}}">Lease</a>): Created
@@ -586,80 +515,62 @@ POST /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases
 ### `update` replace the specified Lease
 
 #### HTTP Request
-
-PUT /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases/{name}
 -->
 ### `update` 替换指定的 Lease
 
 #### HTTP 请求
 
 PUT /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases/{name}
+
 <!--
 #### Parameters
 
-
 - **name** (*in path*): string, required
 
   name of the Lease
 
-
 - **namespace** (*in path*): string, required
 
   <a href="{{< ref "../common-parameters/common-parameters#namespace" >}}">namespace</a>
 
-
 - **body**: <a href="{{< ref "../cluster-resources/lease-v1#Lease" >}}">Lease</a>, required
 
-  
-
-
 - **dryRun** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
 
-
 - **fieldManager** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
 
-
 - **fieldValidation** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
 
-
 - **pretty** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
 -->
 #### 参数
 
-
 - **name** (**路径参数**): string, 必需
 
-  租贷名称
-
+  Lease 的名称。
 
 - **namespace** (**路径参数**): string, 必需
 
   <a href="{{< ref "../common-parameters/common-parameters#namespace" >}}">namespace</a>
 
-
 - **body**: <a href="{{< ref "../cluster-resources/lease-v1#Lease" >}}">Lease</a>, 必需
 
-  
-
-
 - **dryRun** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
 
-
 - **fieldManager** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
 
-
 - **fieldValidation** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
@@ -670,17 +581,9 @@ PUT /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases/{name}
 
 <!--
 #### Response
-
-
-200 (<a href="{{< ref "../cluster-resources/lease-v1#Lease" >}}">Lease</a>): OK
-
-201 (<a href="{{< ref "../cluster-resources/lease-v1#Lease" >}}">Lease</a>): Created
-
-401: Unauthorized
 -->
 #### 响应
 
-
 200 (<a href="{{< ref "../cluster-resources/lease-v1#Lease" >}}">Lease</a>): OK
 
 201 (<a href="{{< ref "../cluster-resources/lease-v1#Lease" >}}">Lease</a>): Created
@@ -691,112 +594,83 @@ PUT /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases/{name}
 ### `patch` partially update the specified Lease
 
 #### HTTP Request
-
-PATCH /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases/{name}
 -->
 ### `patch` 部分更新指定的 Lease
 
 #### HTTP 请求
 
 PATCH /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases/{name}
+
 <!--
 #### Parameters
 
-
 - **name** (*in path*): string, required
 
   name of the Lease
 
-
 - **namespace** (*in path*): string, required
 
   <a href="{{< ref "../common-parameters/common-parameters#namespace" >}}">namespace</a>
 
-
 - **body**: <a href="{{< ref "../common-definitions/patch#Patch" >}}">Patch</a>, required
 
-  
-
-
 - **dryRun** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
 
-
 - **fieldManager** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
 
-
 - **fieldValidation** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
 
-
 - **force** (*in query*): boolean
 
   <a href="{{< ref "../common-parameters/common-parameters#force" >}}">force</a>
 
-
 - **pretty** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
 -->
 #### 参数
 
-
 - **name** (**路径参数**): string, 必需
 
-  租贷名称
-
+  Lease 的名称。
 
 - **namespace** (**路径参数**): string, 必需
 
   <a href="{{< ref "../common-parameters/common-parameters#namespace" >}}">namespace</a>
 
-
 - **body**: <a href="{{< ref "../common-definitions/patch#Patch" >}}">Patch</a>, 必需
 
-  
-
-
 - **dryRun** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
 
-
 - **fieldManager** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
 
-
 - **fieldValidation** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
 
-
 - **force** (**查询参数**): boolean
 
   <a href="{{< ref "../common-parameters/common-parameters#force" >}}">force</a>
 
-
 - **pretty** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
 
 <!--
 #### Response
-
-
-200 (<a href="{{< ref "../cluster-resources/lease-v1#Lease" >}}">Lease</a>): OK
-
-201 (<a href="{{< ref "../cluster-resources/lease-v1#Lease" >}}">Lease</a>): Created
-
-401: Unauthorized
 -->
 #### 响应
 
-
 200 (<a href="{{< ref "../cluster-resources/lease-v1#Lease" >}}">Lease</a>): OK
 
 201 (<a href="{{< ref "../cluster-resources/lease-v1#Lease" >}}">Lease</a>): Created
@@ -807,102 +681,75 @@ PATCH /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases/{name}
 ### `delete` delete a Lease
 
 #### HTTP Request
-
-DELETE /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases/{name}
 -->
 ### `delete` 删除一个 Lease
 
 #### HTTP 请求
 
 DELETE /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases/{name}
+
 <!--
 #### Parameters
 
-
 - **name** (*in path*): string, required
 
   name of the Lease
 
-
 - **namespace** (*in path*): string, required
 
   <a href="{{< ref "../common-parameters/common-parameters#namespace" >}}">namespace</a>
 
-
 - **body**: <a href="{{< ref "../common-definitions/delete-options#DeleteOptions" >}}">DeleteOptions</a>
 
-  
-
-
 - **dryRun** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
 
-
 - **gracePeriodSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#gracePeriodSeconds" >}}">gracePeriodSeconds</a>
 
-
 - **pretty** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
 
-
 - **propagationPolicy** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#propagationPolicy" >}}">propagationPolicy</a>
 -->
 #### 参数
 
-
 - **name** (**路径参数**): string, 必需
 
-  租贷的名称
-
+  Lease 的名称。
 
 - **namespace** (**路径参数**): string, 必需
 
   <a href="{{< ref "../common-parameters/common-parameters#namespace" >}}">namespace</a>
 
-
 - **body**: <a href="{{< ref "../common-definitions/delete-options#DeleteOptions" >}}">DeleteOptions</a>
 
-  
-
-
 - **dryRun** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
 
-
 - **gracePeriodSeconds** (**查询参数**): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#gracePeriodSeconds" >}}">gracePeriodSeconds</a>
 
-
 - **pretty** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
 
-
 - **propagationPolicy** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#propagationPolicy" >}}">propagationPolicy</a>
 
 <!--
 #### Response
-
-
-200 (<a href="{{< ref "../common-definitions/status#Status" >}}">Status</a>): OK
-
-202 (<a href="{{< ref "../common-definitions/status#Status" >}}">Status</a>): Accepted
-
-401: Unauthorized
 -->
 #### 响应
 
-
 200 (<a href="{{< ref "../common-definitions/status#Status" >}}">Status</a>): OK
 
 202 (<a href="{{< ref "../common-definitions/status#Status" >}}">Status</a>): Accepted
@@ -913,77 +760,65 @@ DELETE /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases/{name}
 ### `deletecollection` delete collection of Lease
 
 #### HTTP Request
-
-DELETE /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases
 -->
 ### `deletecollection` 删除 Lease 收款
 
 #### HTTP 请求
 
 DELETE /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases
+
 <!--
 #### Parameters
 
-
 - **namespace** (*in path*): string, required
 
   <a href="{{< ref "../common-parameters/common-parameters#namespace" >}}">namespace</a>
 
-
 - **body**: <a href="{{< ref "../common-definitions/delete-options#DeleteOptions" >}}">DeleteOptions</a>
 
-  
-
-
 - **continue** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#continue" >}}">continue</a>
 
-
 - **dryRun** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
 
-
 - **fieldSelector** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldSelector" >}}">fieldSelector</a>
 
-
 - **gracePeriodSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#gracePeriodSeconds" >}}">gracePeriodSeconds</a>
 
-
 - **labelSelector** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#labelSelector" >}}">labelSelector</a>
 
-
 - **limit** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#limit" >}}">limit</a>
 
-
 - **pretty** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
 
-
 - **propagationPolicy** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#propagationPolicy" >}}">propagationPolicy</a>
 
-
 - **resourceVersion** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersion" >}}">resourceVersion</a>
 
-
 - **resourceVersionMatch** (*in query*): string
 
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
 
 - **timeoutSeconds** (*in query*): integer
 
@@ -991,66 +826,55 @@ DELETE /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases
 -->
 #### 参数
 
-
 - **namespace** (**路径参数**): string, 必需
 
   <a href="{{< ref "../common-parameters/common-parameters#namespace" >}}">namespace</a>
 
-
 - **body**: <a href="{{< ref "../common-definitions/delete-options#DeleteOptions" >}}">DeleteOptions</a>
 
-  
-
-
 - **continue** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#continue" >}}">continue</a>
 
-
 - **dryRun** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
 
-
 - **fieldSelector** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldSelector" >}}">fieldSelector</a>
 
-
 - **gracePeriodSeconds** (**查询参数**): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#gracePeriodSeconds" >}}">gracePeriodSeconds</a>
 
-
 - **labelSelector** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#labelSelector" >}}">labelSelector</a>
 
-
 - **limit** (**查询参数**): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#limit" >}}">limit</a>
 
-
 - **pretty** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
 
-
 - **propagationPolicy** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#propagationPolicy" >}}">propagationPolicy</a>
 
-
 - **resourceVersion** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersion" >}}">resourceVersion</a>
 
-
 - **resourceVersionMatch** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
+- **sendInitialEvents** (**查询参数**): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
 
 - **timeoutSeconds** (**查询参数**): integer
 
@@ -1058,16 +882,9 @@ DELETE /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases
 
 <!--
 #### Response
-
-
-200 (<a href="{{< ref "../common-definitions/status#Status" >}}">Status</a>): OK
-
-401: Unauthorized
 -->
 #### 响应
 
-
 200 (<a href="{{< ref "../common-definitions/status#Status" >}}">Status</a>): OK
 
 401: Unauthorized
-

From 51462146f35dee41a6446a9f01db6f70cf1284de Mon Sep 17 00:00:00 2001
From: windsonsea <haifeng.yao@daocloud.io>
Date: Tue, 18 Apr 2023 14:17:08 +0800
Subject: [PATCH 242/272] [zh] sync
 /kubernetes-api/cluster-resources/node-v1.md

---
 .../cluster-resources/node-v1.md              | 201 ++++++++++--------
 1 file changed, 116 insertions(+), 85 deletions(-)

diff --git a/content/zh-cn/docs/reference/kubernetes-api/cluster-resources/node-v1.md b/content/zh-cn/docs/reference/kubernetes-api/cluster-resources/node-v1.md
index 21b7a6c99bc..db12827b3e1 100644
--- a/content/zh-cn/docs/reference/kubernetes-api/cluster-resources/node-v1.md
+++ b/content/zh-cn/docs/reference/kubernetes-api/cluster-resources/node-v1.md
@@ -8,7 +8,6 @@ description: "Node 是 Kubernetes 中的工作节点。"
 title: "Node"
 weight: 1
 ---
-
 <!-- 
 api_metadata:
   apiVersion: "v1"
@@ -29,7 +28,6 @@ weight: 1
 <!-- 
 Node is a worker node in Kubernetes. Each node will have a unique identifier in the cache (i.e. in etcd). 
 -->
-
 Node 是 Kubernetes 中的工作节点。
 每个节点在缓存中（即在 etcd 中）都有一个唯一的标识符。
 
@@ -44,7 +42,6 @@ Node 是 Kubernetes 中的工作节点。
 
   Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata 
 -->
-
 - **metadata** (<a href="{{< ref "../common-definitions/object-meta#ObjectMeta" >}}">ObjectMeta</a>)
 
   标准的对象元数据。
@@ -55,7 +52,6 @@ Node 是 Kubernetes 中的工作节点。
 
   Spec defines the behavior of a node. https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status 
 -->
-
 - **spec** (<a href="{{< ref "../cluster-resources/node-v1#NodeSpec" >}}">NodeSpec</a>)
 
   spec 定义节点的行为。
@@ -66,7 +62,6 @@ Node 是 Kubernetes 中的工作节点。
 
   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 
 -->
-
 - **status** (<a href="{{< ref "../cluster-resources/node-v1#NodeStatus" >}}">NodeStatus</a>)
 
   此节点的最近观测状态。由系统填充。只读。
@@ -77,7 +72,6 @@ Node 是 Kubernetes 中的工作节点。
 <!-- 
 NodeSpec describes the attributes that a node is created with. 
 -->
-
 NodeSpec 描述了创建节点时使用的属性。
 
 <hr>
@@ -87,14 +81,12 @@ NodeSpec 描述了创建节点时使用的属性。
   <!-- 
   Deprecated: Previously used to specify the source of the node's configuration for the DynamicKubeletConfig feature. This feature is removed.
   -->
-
   已弃用：以前用于为 DynamicKubeletConfig 功能指定节点配置的来源。此功能已删除。
 
   <a name="NodeConfigSource"></a>
   <!-- 
   *NodeConfigSource specifies a source of node configuration. Exactly one subfield (excluding metadata) must be non-nil. This API is deprecated since 1.22* 
   -->
-
   **NodeConfigSource 指定节点配置的来源。指定一个子字段（不包括元数据）必须为非空。此 API 自 1.22的版本起已被弃用**
 
   - **configSource.configMap** (ConfigMapNodeConfigSource)
@@ -158,7 +150,8 @@ NodeSpec 描述了创建节点时使用的属性。
     - **configSource.configMap.uid** (string)
 
       <!--
-      UID is the metadata.UID of the referenced ConfigMap. This field is forbidden in Node.Spec, and required in Node.Status. -->
+      UID is the metadata.UID of the referenced ConfigMap. This field is forbidden in Node.Spec, and required in Node.Status.
+      -->
 
       uid 是所引用的 ConfigMap 的 metadata.uid。
       该字段在 Node.spec 中是禁止的，在 Node.status 中是必需的。
@@ -168,7 +161,6 @@ NodeSpec 描述了创建节点时使用的属性。
   <!--
   Deprecated. Not all kubelets will set this field. Remove field after 1.13. see: https://issues.k8s.io/61966 
   -->
-
   已弃用。并非所有 kubelet 都会设置此字段。
   1.13 的版本之后会删除该字段。参见： https://issues.k8s.io/61966
 
@@ -177,7 +169,6 @@ NodeSpec 描述了创建节点时使用的属性。
   <!-- 
   PodCIDR represents the pod IP range assigned to the node. 
   -->
-
   podCIDR 表示分配给节点的 Pod IP 范围。
 
 - **podCIDRs** ([]string)
@@ -185,7 +176,6 @@ NodeSpec 描述了创建节点时使用的属性。
   <!-- 
   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. 
   -->
-
   podCIDRs 表示分配给节点以供该节点上的 Pod 使用的 IP 范围。
   如果指定了该字段，则第 0 个条目必须与 podCIDR 字段匹配。
   对于 IPv4 和 IPv6，它最多可以包含 1 个值。
@@ -195,7 +185,6 @@ NodeSpec 描述了创建节点时使用的属性。
   <!-- 
   ID of the node assigned by the cloud provider in the format: \<ProviderName>://\<ProviderSpecificNodeID> 
   -->
-
   云提供商分配的节点ID，格式为：\<ProviderName>://\<ProviderSpecificNodeID>
 
 - **taints** ([]Taint)
@@ -203,14 +192,12 @@ NodeSpec 描述了创建节点时使用的属性。
   <!-- 
   If specified, the node's taints. 
   -->
-
   如果设置了，则为节点的污点。
 
   <a name="Taint"></a>
   <!-- 
   *The node this Taint is attached to has the "effect" on any pod that does not tolerate the Taint.* 
   -->
-
   **此污点附加到的节点对任何不容忍污点的 Pod 都有 “影响”。**
 
   <!-- 
@@ -221,7 +208,7 @@ NodeSpec 描述了创建节点时使用的属性。
 
   - **taints.effect** (string), 必需
 
-   必需的。污点对不容忍污点的 Pod 的影响。合法的 effect 值有 NoSchedule、PreferNoSchedule 和 NoExecute。
+    必需的。污点对不容忍污点的 Pod 的影响。合法的 effect 值有 NoSchedule、PreferNoSchedule 和 NoExecute。
 
   <!-- 
   - **taints.key** (string), required
@@ -246,8 +233,8 @@ NodeSpec 描述了创建节点时使用的属性。
     *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.*
     -->
 
-    Time 是 time.Time 的包装器，它支持对 YAML 和 JSON 的正确编组。
-    time 包的许多工厂方法提供了包装器。
+    **Time 是 time.Time 的包装器，它支持对 YAML 和 JSON 的正确编组。
+    time 包的许多工厂方法提供了包装器。**
 
   - **taints.value** (string)
 
@@ -272,7 +259,6 @@ NodeSpec 描述了创建节点时使用的属性。
 <!-- 
 NodeStatus is information about the current status of a node. 
 -->
-
 NodeStatus 是有关节点当前状态的信息。
 
 <hr>
@@ -282,9 +268,8 @@ NodeStatus 是有关节点当前状态的信息。
   <!--
   *Patch strategy: merge on key `type`*
   
-  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 https://pr.k8s.io/79391 for an example.
+  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 https://pr.k8s.io/79391 for an example. Consumers should assume that addresses can change during the lifetime of a Node. However, there are some exceptions where this may not be possible, such as Pods that inherit a Node's address in its own status or consumers of the downward API (status.hostIP).
   -->
-
   **补丁策略：根据 `type` 键执行合并操作**
 
   节点可到达的地址列表。从云提供商处查询（如果有）。
@@ -294,11 +279,14 @@ NodeStatus 是有关节点当前状态的信息。
   调用者应改为使用完全替换性质的补丁操作。
   有关示例，请参见 https://pr.k8s.io/79391。
 
+  消费者应假设地址可以在节点的生命期内发生变化。
+  然而在一些例外情况下这是不可能的，例如在自身状态中继承 Node 地址的 Pod
+  或 downward API (status.hostIP) 的消费者。
+
   <a name="NodeAddress"></a>
   <!--
   *NodeAddress contains information for the node's address.* 
   -->
-
   **NodeAddress 包含节点地址的信息。**
 
   <!--
@@ -326,7 +314,6 @@ NodeStatus 是有关节点当前状态的信息。
   <!--
   Allocatable represents the resources of a node that are available for scheduling. Defaults to Capacity. 
   -->
-
   allocatable 表示节点的可用于调度的资源。默认为容量。
 
 - **capacity** (map[string]<a href="{{< ref "../common-definitions/quantity#Quantity" >}}">Quantity</a>)
@@ -334,7 +321,6 @@ NodeStatus 是有关节点当前状态的信息。
   <!--
   Capacity represents the total resources of a node. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#capacity 
   -->
-
   capacity 代表一个节点的总资源。
   更多信息： https://kubernetes.io/zh-cn/docs/concepts/storage/persistent-volumes/#capacity
 
@@ -345,7 +331,6 @@ NodeStatus 是有关节点当前状态的信息。
   
   Conditions is an array of current observed node conditions. More info: https://kubernetes.io/docs/concepts/nodes/node/#condition 
   -->
-
   **补丁策略：根据 `type` 键执行合并操作**
 
   conditions 是当前观测到的节点状况的数组。
@@ -355,7 +340,6 @@ NodeStatus 是有关节点当前状态的信息。
   <!--
   *NodeCondition contains condition information for a node.* 
   -->
-
   **NodeCondition 包含节点状况的信息。**
 
   <!--
@@ -431,14 +415,12 @@ NodeStatus 是有关节点当前状态的信息。
   <!--
   Status of the config assigned to the node via the dynamic Kubelet config feature. 
   -->
-
   通过动态 Kubelet 配置功能分配给节点的配置状态。
 
   <a name="NodeConfigStatus"></a>
   <!-- 
   *NodeConfigStatus describes the status of the config assigned by Node.Spec.ConfigSource.* 
   -->
-
   **NodeConfigStatus 描述了由 Node.spec.configSource 分配的配置的状态。**
 
   - **config.active** (NodeConfigSource)
@@ -690,8 +672,8 @@ NodeStatus 是有关节点当前状态的信息。
 
       - **config.lastKnownGood.configMap.namespace** (string), 必需
 
-       namespace 是所引用的 ConfigMap 的 metadata.namespace。
-       此字段在所有情况下都是必需的。
+        namespace 是所引用的 ConfigMap 的 metadata.namespace。
+        此字段在所有情况下都是必需的。
 
       - **config.lastKnownGood.configMap.resourceVersion** (string)
 
@@ -716,14 +698,12 @@ NodeStatus 是有关节点当前状态的信息。
   <!--
   Endpoints of daemons running on the Node. 
   -->
-
   在节点上运行的守护进程的端点。
 
   <a name="NodeDaemonEndpoints"></a>
   <!--
   *NodeDaemonEndpoints lists ports opened by daemons running on the Node.* 
   -->
-
   **NodeDaemonEndpoints 列出了节点上运行的守护进程打开的端口。**
 
   - **daemonEndpoints.kubeletEndpoint** (DaemonEndpoint)
@@ -756,14 +736,12 @@ NodeStatus 是有关节点当前状态的信息。
   <!--
   List of container images on this node 
   -->
-
   该节点上的容器镜像列表。
 
   <a name="ContainerImage"></a>
   <!--
   *Describe a container image* 
   -->
-
   **描述一个容器镜像**
 
   - **images.names** ([]string)
@@ -788,7 +766,6 @@ NodeStatus 是有关节点当前状态的信息。
   <!--
   Set of ids/uuids to uniquely identify the node. More info: https://kubernetes.io/docs/concepts/nodes/node/#info 
   -->
-
   用于唯一标识节点的 ids/uuids 集。
   更多信息： https://kubernetes.io/zh-cn/docs/concepts/architecture/nodes/#info
 
@@ -796,7 +773,6 @@ NodeStatus 是有关节点当前状态的信息。
   <!--
   *NodeSystemInfo is a set of ids/uuids to uniquely identify the node.* 
   -->
-
   **NodeSystemInfo 是一组用于唯一标识节点的 ids/uuids。**
 
   <!--
@@ -817,7 +793,7 @@ NodeStatus 是有关节点当前状态的信息。
 
   - **nodeInfo.bootID** (string), 必需
 
-   节点报告的 bootID。
+    节点报告的 bootID。
 
   <!--
   - **nodeInfo.containerRuntimeVersion** (string), required
@@ -879,7 +855,7 @@ NodeStatus 是有关节点当前状态的信息。
 
   - **nodeInfo.operatingSystem** (string), 必需
 
-   节点上报的操作系统。
+    节点上报的操作系统。
 
   <!--
   - **nodeInfo.osImage** (string), required
@@ -908,7 +884,6 @@ NodeStatus 是有关节点当前状态的信息。
   <!--
   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. 
   -->
-
   NodePhase 是最近观测到的节点的生命周期阶段。
   更多信息： https://kubernetes.io/zh-cn/docs/concepts/architecture/nodes/#phase
   
@@ -919,14 +894,12 @@ NodeStatus 是有关节点当前状态的信息。
   <!--
   List of volumes that are attached to the node. 
   -->
-
   附加到节点的卷的列表。
 
   <a name="AttachedVolume"></a>
   <!--
   *AttachedVolume describes a volume attached to a node* 
   -->
-
   **AttachedVolume 描述附加到节点的卷**
 
   <!--
@@ -937,7 +910,7 @@ NodeStatus 是有关节点当前状态的信息。
 
    - **volumesAttached.devicePath** (string), 必需
 
-    devicePath 表示卷应该可用的设备路径。
+     devicePath 表示卷应该可用的设备路径。
 
   <!--
   - **volumesAttached.name** (string), required
@@ -954,7 +927,6 @@ NodeStatus 是有关节点当前状态的信息。
   <!--
   List of attachable volumes in use (mounted) by the node. 
   -->
-
   节点正在使用（安装）的可附加卷的列表。
 
 ## NodeList {#NodeList}
@@ -962,7 +934,6 @@ NodeStatus 是有关节点当前状态的信息。
 <!--
 NodeList is the whole list of all Nodes which have been registered with master. 
 -->
-
 NodeList 是已注册到 master 的所有节点的完整列表。
 
 <hr>
@@ -976,7 +947,6 @@ NodeList 是已注册到 master 的所有节点的完整列表。
   <!--
   Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds 
   -->
-
   标准的列表元数据。
   更多信息： https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
 
@@ -985,7 +955,6 @@ NodeList 是已注册到 master 的所有节点的完整列表。
 
   List of nodes
 -->
-
 - **items** ([]<a href="{{< ref "../cluster-resources/node-v1#Node" >}}">Node</a>), 必需
 
   节点的列表。
@@ -998,7 +967,6 @@ NodeList 是已注册到 master 的所有节点的完整列表。
 GET /api/v1/nodes/{name}
 #### Parameters 
 -->
-
 ## 操作 {#Operations}
 
 <hr>
@@ -1017,7 +985,6 @@ GET /api/v1/nodes/{name}
 - **pretty** (*in query*): string
 #### Response 
 -->
-
 - **name** (**路径参数**): string, 必需
 
   节点的名称。
@@ -1038,7 +1005,6 @@ GET /api/v1/nodes/{name}
 GET /api/v1/nodes/{name}/status
 #### Parameters 
 -->
-
 ### `get` 读取指定节点的状态
 
 #### HTTP 请求
@@ -1053,7 +1019,6 @@ GET /api/v1/nodes/{name}/status
 - **pretty** (*in query*): string
 #### Response 
 -->
-
 - **name** (**路径参数**): string, 必需
 
   节点的名称。
@@ -1074,28 +1039,60 @@ GET /api/v1/nodes/{name}/status
 GET /api/v1/nodes
 #### Parameters
 -->
-
 ### `list` 列出或监视节点类型的对象
 
 #### HTTP 请求
 
 GET /api/v1/nodes
 
-#### 参数
-
 <!--
+#### Parameters
+
 - **allowWatchBookmarks** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#allowWatchBookmarks" >}}">allowWatchBookmarks</a>
+
 - **continue** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#continue" >}}">continue</a>
+
 - **fieldSelector** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldSelector" >}}">fieldSelector</a>
+
 - **labelSelector** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#labelSelector" >}}">labelSelector</a>
+
 - **limit** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#limit" >}}">limit</a>
+
 - **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
 - **resourceVersion** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#resourceVersion" >}}">resourceVersion</a>
+
 - **resourceVersionMatch** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
+
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
 - **timeoutSeconds** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
+
 - **watch** (*in query*): boolean
-#### Response
+
+  <a href="{{< ref "../common-parameters/common-parameters#watch" >}}">watch</a>
 -->
+#### 参数
 
 - **allowWatchBookmarks** (**查询参数**): boolean
 
@@ -1129,6 +1126,10 @@ GET /api/v1/nodes
 
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
+- **sendInitialEvents** (**查询参数**): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
 - **timeoutSeconds** (**查询参数**): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -1137,6 +1138,9 @@ GET /api/v1/nodes
 
   <a href="{{< ref "../common-parameters/common-parameters#watch" >}}">watch</a>
 
+<!--
+#### Response
+-->
 #### 响应
 
 200 (<a href="{{< ref "../cluster-resources/node-v1#NodeList" >}}">NodeList</a>): OK
@@ -1149,7 +1153,6 @@ GET /api/v1/nodes
 POST /api/v1/nodes
 #### Parameters 
 -->
-
 ### `create` 创建一个节点
 
 #### HTTP 请求
@@ -1166,7 +1169,6 @@ POST /api/v1/nodes
 - **pretty** (*in query*): string
 #### Response 
 -->
-
 - **body**: <a href="{{< ref "../cluster-resources/node-v1#Node" >}}">Node</a>, 必需
 
 - **dryRun** (**查询参数**): string
@@ -1201,7 +1203,6 @@ POST /api/v1/nodes
 PUT /api/v1/nodes/{name}
 #### Parameters 
 -->
-
 ### `update` 替换指定节点
 
 #### HTTP 请求
@@ -1220,7 +1221,6 @@ PUT /api/v1/nodes/{name}
 - **pretty** (*in query*): string
 #### Response 
 -->
-
 - **name** (**路径参数**): string, 必需
 
   节点的名称。
@@ -1260,7 +1260,6 @@ PUT /api/v1/nodes/{name}/status
 
 #### Parameters 
 -->
-
 ### `update` 替换指定节点的状态
 
 #### HTTP 请求
@@ -1279,7 +1278,6 @@ PUT /api/v1/nodes/{name}/status
 - **pretty** (*in query*): string
 #### Response 
 -->
-
 - **name** (**路径参数**): string, 必需
 
   节点的名称。
@@ -1316,7 +1314,6 @@ PUT /api/v1/nodes/{name}/status
 PATCH /api/v1/nodes/{name}
 #### Parameters 
 -->
-
 ### `patch` 部分更新指定节点
 
 #### HTTP 请求
@@ -1336,7 +1333,6 @@ PATCH /api/v1/nodes/{name}
 - **pretty** (*in query*): string
 #### Response 
 -->
-
 - **name** (**路径参数**): string, 必需
 
   节点的名称。
@@ -1377,7 +1373,6 @@ PATCH /api/v1/nodes/{name}
 PATCH /api/v1/nodes/{name}/status
 #### Parameters 
 -->
-
 ### `patch` 部分更新指定节点的状态
 
 #### HTTP 请求
@@ -1397,7 +1392,6 @@ PATCH /api/v1/nodes/{name}/status
 - **pretty** (*in query*): string
 #### Response 
 -->
-
 - **name** (**路径参数**): string, 必需
 
   节点的名称。
@@ -1438,7 +1432,6 @@ PATCH /api/v1/nodes/{name}/status
 DELETE /api/v1/nodes/{name}
 #### Parameters 
 -->
-
 ### `delete` 删除一个节点
 
 #### HTTP 请求
@@ -1457,7 +1450,6 @@ DELETE /api/v1/nodes/{name}
 - **propagationPolicy** (*in query*): string
 #### Response
 -->
-
 - **name** (**路径参数**): string, 必需
 
   节点的名称。
@@ -1490,36 +1482,68 @@ DELETE /api/v1/nodes/{name}
 
 <!--
 ### `deletecollection` delete collection of Node
-#### HTTP Request
-DELETE /api/v1/nodes
-#### Parameters 
--->
 
+#### HTTP Request
+-->
 ### `deletecollection` 删除节点的集合
 
 #### HTTP 请求
 
 DELETE /api/v1/nodes
 
-#### 参数
+<!--
+#### Parameters
 
 - **body**: <a href="{{< ref "../common-definitions/delete-options#DeleteOptions" >}}">DeleteOptions</a>
 
-<!--
 - **continue** (*in query*): string
-- **dryRun** (*in query*): string
-- **fieldSelector** (*in query*): string
-- **gracePeriodSeconds** (*in query*): integer
-- **labelSelector** (*in query*): string
-- **limit** (*in query*): integer
-- **pretty** (*in query*): string
-- **propagationPolicy** (*in query*): string
-- **resourceVersion** (*in query*): string
-- **resourceVersionMatch** (*in query*): string
-- **timeoutSeconds** (*in query*): integer
-#### Response
--->
 
+  <a href="{{< ref "../common-parameters/common-parameters#continue" >}}">continue</a>
+
+- **dryRun** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
+
+- **fieldSelector** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#fieldSelector" >}}">fieldSelector</a>
+
+- **gracePeriodSeconds** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#gracePeriodSeconds" >}}">gracePeriodSeconds</a>
+
+- **labelSelector** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#labelSelector" >}}">labelSelector</a>
+
+- **limit** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#limit" >}}">limit</a>
+
+- **pretty** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
+
+- **propagationPolicy** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#propagationPolicy" >}}">propagationPolicy</a>
+
+- **resourceVersion** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#resourceVersion" >}}">resourceVersion</a>
+
+- **resourceVersionMatch** (*in query*): string
+
+  <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
+
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
+- **timeoutSeconds** (*in query*): integer
+
+  <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
+-->
 - **continue** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#continue" >}}">continue</a>
@@ -1560,12 +1584,19 @@ DELETE /api/v1/nodes
 
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
+- **sendInitialEvents** (**查询参数**): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
 - **timeoutSeconds** (**查询参数**): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
 
+<!--
+#### Response
+-->
 #### 响应
 
 200 (<a href="{{< ref "../common-definitions/status#Status" >}}">Status</a>): OK
 
-401: Unauthorized
\ No newline at end of file
+401: Unauthorized

From 8ea2718e0841481e29a328f88a34a2c6a3f43342 Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Wed, 19 Apr 2023 15:42:51 +0800
Subject: [PATCH 243/272] sync controller-manager-leader-migration.md

sync controller-manager-leader-migration.md
---
 .../administer-cluster/controller-manager-leader-migration.md   | 2 --
 1 file changed, 2 deletions(-)

diff --git a/content/zh-cn/docs/tasks/administer-cluster/controller-manager-leader-migration.md b/content/zh-cn/docs/tasks/administer-cluster/controller-manager-leader-migration.md
index 0c548ab635c..785635a560d 100644
--- a/content/zh-cn/docs/tasks/administer-cluster/controller-manager-leader-migration.md
+++ b/content/zh-cn/docs/tasks/administer-cluster/controller-manager-leader-migration.md
@@ -17,8 +17,6 @@ weight: 250
 
 <!-- overview -->
 
-{{< feature-state for_k8s_version="v1.24" state="stable"  >}}
-
 {{< glossary_definition term_id="cloud-controller-manager" length="all">}}
 
 <!--

From cd282d486719050cb8ebc650095ee2063ce482d8 Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Wed, 19 Apr 2023 15:48:54 +0800
Subject: [PATCH 244/272] sync persistent-volumes.md

sync persistent-volumes.md
---
 content/zh-cn/docs/concepts/storage/persistent-volumes.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/content/zh-cn/docs/concepts/storage/persistent-volumes.md b/content/zh-cn/docs/concepts/storage/persistent-volumes.md
index c5ad768185e..07f3a4bb775 100644
--- a/content/zh-cn/docs/concepts/storage/persistent-volumes.md
+++ b/content/zh-cn/docs/concepts/storage/persistent-volumes.md
@@ -1084,7 +1084,8 @@ The access modes are:
 : the volume can be mounted as read-write by many nodes.
 
  `ReadWriteOncePod`
-: the volume can be mounted as read-write by a single Pod. Use ReadWriteOncePod
+: {{< feature-state for_k8s_version="v1.27" state="beta" >}}
+  the volume can be mounted as read-write by a single Pod. Use ReadWriteOncePod
   access mode if you want to ensure that only one pod across whole cluster can
   read that PVC or write to it. This is only supported for CSI volumes and
   Kubernetes version 1.22+.
@@ -1106,7 +1107,8 @@ covers this in more detail.
 : 卷可以被多个节点以读写方式挂载。
 
 `ReadWriteOncePod`
-: 卷可以被单个 Pod 以读写方式挂载。
+: {{< feature-state for_k8s_version="v1.27" state="beta" >}}
+  卷可以被单个 Pod 以读写方式挂载。
   如果你想确保整个集群中只有一个 Pod 可以读取或写入该 PVC，
   请使用 ReadWriteOncePod 访问模式。这只支持 CSI 卷以及需要 Kubernetes 1.22 以上版本。
 

From 93c076114a1e474bc8fc8ae09f141f45c04c98b8 Mon Sep 17 00:00:00 2001
From: windsonsea <haifeng.yao@daocloud.io>
Date: Wed, 19 Apr 2023 14:19:16 +0800
Subject: [PATCH 245/272] [zh] sync /administer-cluster/encrypt-data.md

---
 .../tasks/administer-cluster/encrypt-data.md  | 101 +++++++++++++++---
 1 file changed, 89 insertions(+), 12 deletions(-)

diff --git a/content/zh-cn/docs/tasks/administer-cluster/encrypt-data.md b/content/zh-cn/docs/tasks/administer-cluster/encrypt-data.md
index 6da9caa86d2..b21dd4ed179 100644
--- a/content/zh-cn/docs/tasks/administer-cluster/encrypt-data.md
+++ b/content/zh-cn/docs/tasks/administer-cluster/encrypt-data.md
@@ -28,11 +28,15 @@ This page shows how to enable and configure encryption of secret data at rest.
 * etcd v3.0 or later is required
 
 * To encrypt a custom resource, your cluster must be running Kubernetes v1.26 or newer.
+
+* Use of wildcard for resource encryption is available from Kubernetes v1.27 or newer.
 -->
 * 需要 etcd v3.0 或者更高版本
 
 * 要加密自定义资源，你的集群必须运行 Kubernetes v1.26 或更高版本。
 
+* 在 Kubernetes v1.27 或更高版本中可以使用通配符配置资源加密。
+
 <!-- steps -->
 
 <!--
@@ -67,6 +71,9 @@ decrypt data stored in the etcd.
 -->
 ## 理解静态数据加密    {#understanding-the-encryption-at-rest-configuration}
 
+<!--
+do not encrypt events even though  *.* is specified below
+-->
 ```yaml
 apiVersion: apiserver.config.k8s.io/v1
 kind: EncryptionConfiguration
@@ -93,6 +100,24 @@ resources:
           keys:
             - name: key1
               secret: YWJjZGVmZ2hpamtsbW5vcHFyc3R1dnd4eXoxMjM0NTY=
+  - resources:
+      - events
+    providers:
+      - identity: {} # 即使如下指定 *.* 也不会加密 events
+  - resources:
+      - '*.apps'
+    providers:
+      - aescbc:
+          keys:
+          - name: key2
+            secret: c2VjcmV0IGlzIHNlY3VyZSwgb3IgaXMgaXQ/Cg==
+  - resources:
+      - '*.*'
+    providers:
+      - aescbc:
+          keys:
+          - name: key3
+            secret: c2VjcmV0IGlzIHNlY3VyZSwgSSB0aGluaw==
 ```
 
 <!--
@@ -126,16 +151,63 @@ The first provider in the list is used to encrypt resources written into the sto
 resources from storage, each provider that matches the stored data attempts in order to decrypt the
 data. If no provider can read the stored data due to a mismatch in format or secret key, an error
 is returned which prevents clients from accessing that resource.
-
-For more detailed information about the `EncryptionConfiguration` struct, please refer to the
-[encryption configuration API](/docs/reference/config-api/apiserver-encryption.v1/).
 -->
 每个条目只能指定一个 provider 类型（可以是 `identity` 或 `aescbc`，但不能在同一个项目中同时指定二者）。
 列表中的第一个 provider 用于加密写入存储的资源。
 当从存储器读取资源时，与存储的数据匹配的所有 provider 将按顺序尝试解密数据。
 如果由于格式或密钥不匹配而导致没有 provider 能够读取存储的数据，则会返回一个错误，以防止客户端访问该资源。
 
-有关 `EncryptionConfiguration` 结构体的更多详细信息，请参阅[加密配置 API](/zh-cn/docs/reference/config-api/apiserver-encryption.v1/)。
+<!--
+`EncryptionConfiguration` supports the use of wildcards to specify the resources that should be encrypted.
+Use '`*.<group>`' to encrypt all resources within a group (for eg '`*.apps`' in above example) or '`*.*`'
+to encrypt all resources. '`*.`' can be used to encrypt all resource in the core group. '`*.*`' will
+encrypt all resources, even custom resources that are added after API server start.
+-->
+`EncryptionConfiguration` 支持使用通配符指定应加密的资源。
+使用 “`*.<group>`” 加密 group 内的所有资源（例如以上例子中的 “`*.apps`”）或使用
+“`*.*`” 加密所有资源。“`*.`” 可用于加密核心组中的所有资源。“`*.*`”
+将加密所有资源，甚至包括 API 服务器启动之后添加的自定义资源。
+
+{{< note >}}
+<!--
+Use of wildcards that overlap within the same resource list or across multiple entries are not allowed
+since part of the configuration would be ineffective. The `resources` list's processing order and precedence
+are determined by the order it's listed in the configuration.
+-->
+不允许在同一资源列表或跨多个条目中使用相互重疊的通配符，因为这样一来配置的一部分将无法生效。
+`resources` 列表的处理顺序和优先级由配置中列出的顺序决定。
+{{< /note >}}
+
+<!--
+Opting out of encryption for specific resources while wildcard is enabled can be achieved by adding a new
+`resources` array item with the resource name, followed by the `providers` array item with the `identity` provider.
+For example, if '`*.*`' is enabled and you want to opt-out encryption for the `events` resource, add a new item
+to the `resources` array with `events` as the resource name, followed by the providers array item with `identity`.
+The new item should look like this:
+-->
+如果启用了通配符，但想要针对特定资源退出加密，则可以通过添加带有资源名称的新 `resources` 数组项，
+后跟附带 `identity` 提供商的 `providers` 数组项。例如，如果启用了 “`*.*`”，
+但想要排除对 `events` 资源的加密，则应向 `resources` 数组添加一个新项（以 `events` 为资源名称），
+后跟包含 `identity` 的 providers 数组。新项应如下所示：
+
+```yaml
+- resources:
+    - events
+  providers:
+    - identity: {}
+```
+
+<!--
+Ensure that the new item is listed before the wildcard '`*.*`' item in the resources array to give it precedence.
+-->
+确保新项列在资源数组中的通配符 “`*.*`” 项之前，使新项优先。
+
+<!--
+For more detailed information about the `EncryptionConfiguration` struct, please refer to the
+[encryption configuration API](/docs/reference/config-api/apiserver-encryption.v1/).
+-->
+有关 `EncryptionConfiguration` 结构体的更多详细信息，
+请参阅[加密配置 API](/zh-cn/docs/reference/config-api/apiserver-encryption.v1/)。
 
 {{< caution >}}
 <!--
@@ -157,11 +229,9 @@ Name | Encryption | Strength | Speed | Key Length | Other Considerations
 `secretbox` | XSalsa20 and Poly1305 | Strong | Faster | 32-byte | A newer standard and may not be considered acceptable in environments that require high levels of review.
 `aesgcm` | AES-GCM with random nonce | Must be rotated every 200k writes | Fastest | 16, 24, or 32-byte | Is not recommended for use except when an automated key rotation scheme is implemented.
 `aescbc` | AES-CBC with [PKCS#7](https://datatracker.ietf.org/doc/html/rfc2315) padding | Weak | Fast | 32-byte | Not recommended due to CBC's vulnerability to padding oracle attacks.
-`kms` | Uses envelope encryption scheme: Data is encrypted by data encryption keys (DEKs) using AES-CBC with [PKCS#7](https://datatracker.ietf.org/doc/html/rfc2315) padding (prior to v1.25), using AES-GCM starting from v1.25, DEKs are encrypted by key encryption keys (KEKs) according to configuration in Key Management Service (KMS) | Strongest | Fast | 32-bytes |  The recommended choice for using a third party tool for key management. Simplifies key rotation, with a new DEK generated for each encryption, and KEK rotation controlled by the user. [Configure the KMS provider](/docs/tasks/administer-cluster/kms-provider/)
-+{{< /table >}}
-
-Each provider supports multiple keys - the keys are tried in order for decryption, and if the provider
-is the first provider, the first key is used for encryption.
+`kms v1` | Uses envelope encryption scheme: Data is encrypted by data encryption keys (DEKs) using AES-CBC with [PKCS#7](https://datatracker.ietf.org/doc/html/rfc2315) padding (prior to v1.25), using AES-GCM starting from v1.25, DEKs are encrypted by key encryption keys (KEKs) according to configuration in Key Management Service (KMS) | Strongest | Slow (_compared to `kms v2`_) | 32-bytes |  Simplifies key rotation, with a new DEK generated for each encryption, and KEK rotation controlled by the user. [Configure the KMS V1 provider](/docs/tasks/administer-cluster/kms-provider#configuring-the-kms-provider-kms-v1).
+`kms v2` | Uses envelope encryption scheme: Data is encrypted by data encryption keys (DEKs) using AES-GCM, DEKs are encrypted by key encryption keys (KEKs) according to configuration in Key Management Service (KMS) | Strongest | Fast | 32-bytes |  The recommended choice for using a third party tool for key management. Available in beta from `v1.27`. A new DEK is generated at startup and reused for encryption. The DEK is rotated when the KEK is rotated. [Configure the KMS V2 provider](/docs/tasks/administer-cluster/kms-provider#configuring-the-kms-provider-kms-v2).
+{{< /table >}}
 -->
 {{< table caption="Kubernetes 静态数据加密的 Provider" >}}
 名称 | 加密类型   | 强度     | 速度  | 密钥长度   | 其它事项
@@ -170,9 +240,13 @@ is the first provider, the first key is used for encryption.
 `secretbox` | XSalsa20 和 Poly1305 | 强 | 更快 | 32 字节 | 较新的标准，在需要高度评审的环境中可能不被接受。
 `aesgcm` | 带有随机数的 AES-GCM | 必须每 200k 写入一次 | 最快 | 16、24 或者 32字节 | 建议不要使用，除非实施了自动密钥循环方案。
 `aescbc` | 填充 [PKCS#7](https://datatracker.ietf.org/doc/html/rfc2315) 的 AES-CBC | 弱 | 快 | 32 字节 | 由于 CBC 容易受到密文填塞攻击（Padding Oracle Attack），不推荐使用。
-`kms` | 使用信封加密方案：数据使用带有 [PKCS#7](https://datatracker.ietf.org/doc/html/rfc2315) 填充的 AES-CBC（v1.25 之前），从 v1.25 开始使用 AES-GCM 通过数据加密密钥（DEK）加密，DEK 根据 Key Management Service（KMS）中的配置通过密钥加密密钥（Key Encryption Keys，KEK）加密 | 最强 | 快 | 32 字节 | 建议使用第三方工具进行密钥管理。为每个加密生成新的 DEK，并由用户控制 KEK 轮换来简化密钥轮换。[配置 KMS 提供程序](/zh-cn/docs/tasks/administer-cluster/kms-provider/)
+`kms v1` | 使用信封加密方案：数据使用带有 [PKCS#7](https://datatracker.ietf.org/doc/html/rfc2315) 填充的 AES-CBC（v1.25 之前），从 v1.25 开始使用 AES-GCM 通过数据加密密钥（DEK）加密，DEK 根据 Key Management Service（KMS）中的配置通过密钥加密密钥（Key Encryption Keys，KEK）加密 | 最强 | 快 | 32 字节 | 建议使用第三方工具进行密钥管理。为每个加密生成新的 DEK，并由用户控制 KEK 轮换来简化密钥轮换。从 `v1.27` 开始，该功能处于 Beta 阶段。系统在启动时生成一个新的 DEK 并重复使用它进行加密。当 KEK 被轮转时，DEK 也会被轮转。[配置 KMS V2 provider](/zh-cn/docs/tasks/administer-cluster/kms-provider#configuring-the-kms-provider-kms-v2)。
 {{< /table >}}
 
+<!--
+Each provider supports multiple keys - the keys are tried in order for decryption, and if the provider
+is the first provider, the first key is used for encryption.
+-->
 每个 provider 都支持多个密钥 - 在解密时会按顺序使用密钥，如果是第一个 provider，则第一个密钥用于加密。
 
 {{< caution >}}
@@ -267,6 +341,9 @@ To create a new Secret, perform the following steps:
    2. 编辑 `kube-apiserver` 静态 Pod 的清单：`/etc/kubernetes/manifests/kube-apiserver.yaml`，
       代码范例如下：
 
+   <!--
+   add this line
+   -->
    ```yaml
    apiVersion: v1
    kind: Pod
@@ -339,7 +416,7 @@ program to retrieve the contents of your secret data.
 <!--
 1. Using the `etcdctl` command line, read that Secret out of etcd:
 -->
-2. 使用 etcdctl 命令行，从 etcd 中读取 Secret：
+2. 使用 `etcdctl` 命令行，从 etcd 中读取 Secret：
 
    ```
    ETCDCTL_API=3 etcdctl get /registry/secrets/default/secret1 [...] | hexdump -C
@@ -458,7 +535,7 @@ When running a single `kube-apiserver` instance, step 2 may be skipped.
 在不发生停机的情况下更改 Secret 需要多步操作，特别是在有多个 `kube-apiserver`
 进程正在运行的高可用环境中。
 
-1. 生成一个新密钥并将其添加为所有服务器上当前提供程序的第二个密钥条目
+1. 生成一个新密钥并将其添加为所有服务器上当前 provider 的第二个密钥条目
 1. 重新启动所有 `kube-apiserver` 进程以确保每台服务器都可以使用新密钥进行解密
 1. 将新密钥设置为 `keys` 数组中的第一个条目，以便在配置中使用其进行加密
 1. 重新启动所有 `kube-apiserver` 进程以确保每个服务器现在都使用新密钥进行加密

From 3dd4b95a606da721771188741e8aada64176137f Mon Sep 17 00:00:00 2001
From: Sergey Shevchenko <sergeyshevchdevelop@gmail.com>
Date: Wed, 19 Apr 2023 13:18:20 +0300
Subject: [PATCH 246/272] fix: Fix column order for feature-gates table

---
 .../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 56fb28b56b0..7e157bd00f3 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
@@ -56,7 +56,7 @@ For a reference to old feature gates that are removed, please refer to
 
 | Feature | Default | Stage | Since | Until |
 |---------|---------|-------|-------|-------|
-| `AdmissionWebhookMatchConditions` | Alpha | `false` | 1.27 | |
+| `AdmissionWebhookMatchConditions` | `false` | Alpha | 1.27 | |
 | `APIListChunking` | `false` | Alpha | 1.8 | 1.8 |
 | `APIListChunking` | `true` | Beta | 1.9 | |
 | `APIPriorityAndFairness` | `false` | Alpha | 1.18 | 1.19 |

From 10fe5e561377d03a716c07fa113497db8ea56ff9 Mon Sep 17 00:00:00 2001
From: Arhell <arhell333@gmail.com>
Date: Thu, 20 Apr 2023 00:26:45 +0300
Subject: [PATCH 247/272] [fr] update curl command

---
 content/fr/docs/concepts/cluster-administration/certificates.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/fr/docs/concepts/cluster-administration/certificates.md b/content/fr/docs/concepts/cluster-administration/certificates.md
index 46637f2fda5..8e82e075bb5 100644
--- a/content/fr/docs/concepts/cluster-administration/certificates.md
+++ b/content/fr/docs/concepts/cluster-administration/certificates.md
@@ -21,7 +21,7 @@ manuellement grâce à `easyrsa`, `openssl` ou `cfssl`.
 
 1.  Téléchargez, décompressez et initialisez la version corrigée de easyrsa3.
 
-        curl -LO https://storage.googleapis.com/kubernetes-release/easy-rsa/easy-rsa.tar.gz
+        curl -LO https://dl.k8s.io/easy-rsa/easy-rsa.tar.gz
         tar xzf easy-rsa.tar.gz
         cd easy-rsa-master/easyrsa3
         ./easyrsa init-pki

From e4360124e4a1aadc8cc45b5c281f572253591771 Mon Sep 17 00:00:00 2001
From: Fabian B <fabian.baumanis@mailbox.org>
Date: Thu, 20 Apr 2023 11:23:13 +0200
Subject: [PATCH 248/272] Add translation for "Install tools"

---
 content/de/docs/tasks/tools/_index.md | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/content/de/docs/tasks/tools/_index.md b/content/de/docs/tasks/tools/_index.md
index 1de111c0ce8..cb0a825dc58 100644
--- a/content/de/docs/tasks/tools/_index.md
+++ b/content/de/docs/tasks/tools/_index.md
@@ -3,3 +3,25 @@ title: "Werkzeuge installieren"
 weight: 10
 ---
 
+## kubectl
+
+Das Kubernetes Befehlszeilenprogramm [kubectl](/docs/user-guide/kubectl/) ermöglicht es Ihnen, Befehle auf einem Kubernetes-Cluster auszuführen. Sie können mit kubectl Anwendungen bereitstellen, Cluster-Ressourcen überwachen und verwalten sowie Logs einsehen.
+Weitere Informationen über alle verfügbaren `kubectl`-Befehle finden Sie in der [Kommandoreferenz von kubectl](/docs/reference/kubectl/).
+
+`kubectl` kann unter Linux, macOS und Windows installiert werden. [Hier](install-kubectl) finden Sie Anleitungen zur Installation von `kubectl`.
+
+## kind
+Mit [`kind`](https://kind.sigs.k8s.io/) können Sie Kubernetes lokal auf Ihrem Computer ausführen. Voraussetzung hierfür ist eine konfigurierte und funktionierende [Docker](https://docs.docker.com/get-docker/)-Installation.
+
+Die `kind` [Schnellstart](https://kind.sigs.k8s.io/docs/user/quick-start/)-Seite gibt Informationen darüber, was für den schnellen Einstieg mit `kind` benötigt wird.
+
+## minikube
+Ähnlich wie `kind` ist [`minikube`](https://minikube.sigs.k8s.io/) ein Tool, mit dem man Kubernetes lokal auf dem Computer ausführen kann. Minikube erstellt Cluster mit einer Node oder mehreren Nodes. Somit ist es ein praktisches Tool für tägliche Entwicklungsaktivitäten mit Kubernetes, oder um Kubernetes einfach einmal lokal auszuprobieren. 
+
+[Hier](/install-minikube) erfahren Sie, wie Sie `minikube` auf Ihrem Computer installieren können.
+Falls Sie `minikube` bereits installiert haben, können Sie es verwenden, um eine [Beispiel-Anwendung zu bereitzustellen.](/docs/tutorials/hello-minikube/).
+
+## kubeadm
+Mit `kubeadm` können Sie Kubernetes-Cluster erstellen und verwalten. `kubeadm` führt alle notwendigen Schritte aus, um ein minimales aber sicheres Cluster in einer benutzerfreundlichen Art und Weise aufzusetzen.
+[Auf dieser Seite](/docs/setup/production-environment/tools/kubeadm/install-kubeadm/) finden Sie Anleitungen zur Installation von `kubeadm`.
+Sobald Sie `kubeadm` installiert haben, erfahren Sie [hier](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/) wie man ein Cluster mit `kubeadm` erstellt.
\ No newline at end of file

From 25e2d857cf602a65ebe57dbb276fb432a2e739d5 Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Thu, 20 Apr 2023 19:50:19 +0800
Subject: [PATCH 249/272] sync assign-cpu-resource.md

sync assign-cpu-resource.md
---
 .../docs/tasks/configure-pod-container/assign-cpu-resource.md  | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/content/zh-cn/docs/tasks/configure-pod-container/assign-cpu-resource.md b/content/zh-cn/docs/tasks/configure-pod-container/assign-cpu-resource.md
index 20c151905f6..fc966259669 100644
--- a/content/zh-cn/docs/tasks/configure-pod-container/assign-cpu-resource.md
+++ b/content/zh-cn/docs/tasks/configure-pod-container/assign-cpu-resource.md
@@ -425,6 +425,7 @@ kubectl delete namespace cpu-example
 * [Configure Memory and CPU Quotas for a Namespace](/docs/tasks/administer-cluster/manage-resources/quota-memory-cpu-namespace/)
 * [Configure a Pod Quota for a Namespace](/docs/tasks/administer-cluster/manage-resources/quota-pod-namespace/)
 * [Configure Quotas for API Objects](/docs/tasks/administer-cluster/quota-api-object/)
+* [Resize CPU and Memory Resources assigned to Containers](/docs/tasks/configure-pod-container/resize-container-resources/)
 -->
 ### 针对集群管理员 {for-cluster-administrators}
 
@@ -435,3 +436,5 @@ kubectl delete namespace cpu-example
 * [为名字空间配置内存和 CPU 配额](/zh-cn/docs/tasks/administer-cluster/manage-resources/quota-memory-cpu-namespace/)
 * [为名字空间配置 Pod 配额](/zh-cn/docs/tasks/administer-cluster/manage-resources/quota-pod-namespace/)
 * [配置 API 对象的配额](/zh-cn/docs/tasks/administer-cluster/quota-api-object/)
+* [调整分配给容器的 CPU 和内存资源](/zh-cn/docs/tasks/configure-pod-container/resize-container-resources/)
+ 
\ No newline at end of file

From 80ce7b0f5734fa7dddea1af712723c350e0427d6 Mon Sep 17 00:00:00 2001
From: Qiming Teng <tengqm@outlook.com>
Date: Wed, 12 Apr 2023 12:15:15 +0800
Subject: [PATCH 250/272] Update feature gates for v1.27

---
 .../feature-gates-removed.md                  |  83 +++++++++++--
 .../feature-gates.md                          | 113 +++++-------------
 2 files changed, 106 insertions(+), 90 deletions(-)

diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates-removed.md b/content/en/docs/reference/command-line-tools-reference/feature-gates-removed.md
index 50d1dd29bfc..eebb0137e38 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates-removed.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates-removed.md
@@ -58,8 +58,22 @@ In the following table:
 | `CSIDriverRegistry` | `false` | Alpha | 1.12 | 1.13 |
 | `CSIDriverRegistry` | `true` | Beta | 1.14 | 1.17 |
 | `CSIDriverRegistry` | `true` | GA | 1.18 | 1.21 |
+| `CSIInlineVolume` | `false` | Alpha | 1.15 | 1.15 |
+| `CSIInlineVolume` | `true` | Beta | 1.16 | 1.24 |
+| `CSIInlineVolume` | `true` | GA | 1.25 | 1.26 |
+| `CSIMigration` | `false` | Alpha | 1.14 | 1.16 |
+| `CSIMigration` | `true` | Beta | 1.17 | 1.24 |
+| `CSIMigration` | `true` | GA | 1.25 | 1.26 |
+| `CSIMigrationAWS` | `false` | Alpha | 1.14 | 1.16 |
+| `CSIMigrationAWS` | `false` | Beta | 1.17 | 1.22 |
+| `CSIMigrationAWS` | `true` | Beta | 1.23 | 1.24 |
+| `CSIMigrationAWS` | `true` | GA | 1.25 | 1.26 |
 | `CSIMigrationAWSComplete` | `false` | Alpha | 1.17 | 1.20 |
 | `CSIMigrationAWSComplete` | - | Deprecated | 1.21 | 1.21 |
+| `CSIMigrationAzureDisk` | `false` | Alpha | 1.15 | 1.18 |
+| `CSIMigrationAzureDisk` | `false` | Beta | 1.19 | 1.22 |
+| `CSIMigrationAzureDisk` | `true` | Beta | 1.23 | 1.23 |
+| `CSIMigrationAzureDisk` | `true` | GA | 1.24 | 1.26 |
 | `CSIMigrationAzureDiskComplete` | `false` | Alpha | 1.17 | 1.20 |
 | `CSIMigrationAzureDiskComplete` | - | Deprecated | 1.21 | 1.21 |
 | `CSIMigrationAzureFileComplete` | `false` | Alpha | 1.17 | 1.20 |
@@ -85,17 +99,17 @@ In the following table:
 | `CSIVolumeFSGroupPolicy` | `false` | Alpha | 1.19 | 1.19 |
 | `CSIVolumeFSGroupPolicy` | `true` | Beta | 1.20 | 1.22 |
 | `CSIVolumeFSGroupPolicy` | `true` | GA | 1.23 | 1.25 |
+| `CSRDuration` | `true` | Beta | 1.22 | 1.23 |
+| `CSRDuration` | `true` | GA | 1.24 | 1.25 |
 | `ConfigurableFSGroupPolicy` | `false` | Alpha | 1.18 | 1.19 |
 | `ConfigurableFSGroupPolicy` | `true` | Beta | 1.20 | 1.22 |
 | `ConfigurableFSGroupPolicy` | `true` | GA | 1.23 | 1.25 |
-| `CronJobControllerV2` | `false` | Alpha | 1.20 | 1.20 |
-| `CronJobControllerV2` | `true` | Beta | 1.21 | 1.21 |
-| `CronJobControllerV2` | `true` | GA | 1.22 | 1.23 |
-| `CSRDuration` | `true` | Beta | 1.22 | 1.23 |
-| `CSRDuration` | `true` | GA | 1.24 | 1.25 |
 | `ControllerManagerLeaderMigration` | `false` | Alpha | 1.21 | 1.21 |
 | `ControllerManagerLeaderMigration` | `true` | Beta | 1.22 | 1.23 |
 | `ControllerManagerLeaderMigration` | `true` | GA | 1.24 | 1.26 |
+| `CronJobControllerV2` | `false` | Alpha | 1.20 | 1.20 |
+| `CronJobControllerV2` | `true` | Beta | 1.21 | 1.21 |
+| `CronJobControllerV2` | `true` | GA | 1.22 | 1.23 |
 | `CustomPodDNS` | `false` | Alpha | 1.9 | 1.9 |
 | `CustomPodDNS` | `true` | Beta| 1.10 | 1.13 |
 | `CustomPodDNS` | `true` | GA | 1.14 | 1.16 |
@@ -114,6 +128,9 @@ In the following table:
 | `CustomResourceWebhookConversion` | `false` | Alpha | 1.13 | 1.14 |
 | `CustomResourceWebhookConversion` | `true` | Beta | 1.15 | 1.15 |
 | `CustomResourceWebhookConversion` | `true` | GA | 1.16 | 1.18 |
+| `DaemonSetUpdateSurge` | `false` | Alpha | 1.21 | 1.21 |
+| `DaemonSetUpdateSurge` | `true` | Beta | 1.22 | 1.24 |
+| `DaemonSetUpdateSurge` | `true` | GA | 1.25 | 1.26 |
 | `DefaultPodTopologySpread` | `false` | Alpha | 1.19 | 1.19 |
 | `DefaultPodTopologySpread` | `true` | Beta | 1.20 | 1.23 |
 | `DefaultPodTopologySpread` | `true` | GA | 1.24 | 1.25 |
@@ -138,18 +155,21 @@ In the following table:
 | `EndpointSliceProxying` | `false` | Alpha | 1.18 | 1.18 |
 | `EndpointSliceProxying` | `true` | Beta | 1.19 | 1.21 |
 | `EndpointSliceProxying` | `true` | GA | 1.22 | 1.24 |
+| `EphemeralContainers` | `false` | Alpha | 1.16 | 1.22 |
+| `EphemeralContainers` | `true` | Beta | 1.23 | 1.24 |
+| `EphemeralContainers` | `true` | GA | 1.25 | 1.26 |
 | `EvenPodsSpread` | `false` | Alpha | 1.16 | 1.17 |
 | `EvenPodsSpread` | `true` | Beta | 1.18 | 1.18 |
 | `EvenPodsSpread` | `true` | GA | 1.19 | 1.21 |
 | `ExpandCSIVolumes` | `false` | Alpha | 1.14 | 1.15 |
 | `ExpandCSIVolumes` | `true` | Beta | 1.16 | 1.23 |
-| `ExpandCSIVolumes` | `true` | GA | 1.24 | 1.27 |
+| `ExpandCSIVolumes` | `true` | GA | 1.24 | 1.26 |
 | `ExpandInUsePersistentVolumes` | `false` | Alpha | 1.11 | 1.14 |
 | `ExpandInUsePersistentVolumes` | `true` | Beta | 1.15 | 1.23 |
-| `ExpandInUsePersistentVolumes` | `true` | GA | 1.24 | 1.27 |
+| `ExpandInUsePersistentVolumes` | `true` | GA | 1.24 | 1.26 |
 | `ExpandPersistentVolumes` | `false` | Alpha | 1.8 | 1.10 |
 | `ExpandPersistentVolumes` | `true` | Beta | 1.11 | 1.23 |
-| `ExpandPersistentVolumes` | `true` | GA | 1.24 | 1.27 |
+| `ExpandPersistentVolumes` | `true` | GA | 1.24 | 1.26 |
 | `ExperimentalCriticalPodAnnotation` | `false` | Alpha | 1.5 | 1.12 |
 | `ExperimentalCriticalPodAnnotation` | `false` | Deprecated | 1.13 | 1.16 |
 | `ExternalPolicyForExternalIP` | `true` | GA | 1.18 | 1.22 |
@@ -171,7 +191,7 @@ In the following table:
 | `IPv6DualStack` | `true` | GA | 1.23 | 1.24 |
 | `IdentifyPodOS` | `false` | Alpha | 1.23 | 1.23 |
 | `IdentifyPodOS` | `true` | Beta | 1.24 | 1.24 |
-| `IdentifyPodOS` | `true` | GA | 1.25 | 1.27 |
+| `IdentifyPodOS` | `true` | GA | 1.25 | 1.26 |
 | `ImmutableEphemeralVolumes` | `false` | Alpha | 1.18 | 1.18 |
 | `ImmutableEphemeralVolumes` | `true` | Beta | 1.19 | 1.20 |
 | `ImmutableEphemeralVolumes` | `true` | GA | 1.21 | 1.24 |
@@ -191,6 +211,9 @@ In the following table:
 | `LegacyNodeRoleBehavior` | `false` | Alpha | 1.16 | 1.18 |
 | `LegacyNodeRoleBehavior` | `true` | Beta | 1.19 | 1.20 |
 | `LegacyNodeRoleBehavior` | `false` | GA | 1.21 | 1.22 |
+| `LocalStorageCapacityIsolation` | `false` | Alpha | 1.7 | 1.9 |
+| `LocalStorageCapacityIsolation` | `true` | Beta | 1.10 | 1.24 |
+| `LocalStorageCapacityIsolation` | `true` | GA | 1.25 | 1.26 |
 | `MountContainers` | `false` | Alpha | 1.9 | 1.16 |
 | `MountContainers` | `false` | Deprecated | 1.17 | 1.17 |
 | `MountPropagation` | `false` | Alpha | 1.8 | 1.9 |
@@ -198,6 +221,9 @@ In the following table:
 | `MountPropagation` | `true` | GA | 1.12 | 1.14 |
 | `NamespaceDefaultLabelName` | `true` | Beta | 1.21 | 1.21 |
 | `NamespaceDefaultLabelName` | `true` | GA | 1.22 | 1.23 |
+| `NetworkPolicyEndPort` | `false` | Alpha | 1.21 | 1.21 |
+| `NetworkPolicyEndPort` | `true` | Beta | 1.22 | 1.24 |
+| `NetworkPolicyEndPort` | `true` | GA | 1.25 | 1.26 |
 | `NodeDisruptionExclusion` | `false` | Alpha | 1.16 | 1.18 |
 | `NodeDisruptionExclusion` | `true` | Beta | 1.19 | 1.20 |
 | `NodeDisruptionExclusion` | `true` | GA | 1.21 | 1.22 |
@@ -285,6 +311,9 @@ In the following table:
 | `StartupProbe` | `false` | Alpha | 1.16 | 1.17 |
 | `StartupProbe` | `true` | Beta | 1.18 | 1.19 |
 | `StartupProbe` | `true` | GA | 1.20 | 1.23 |
+| `StatefulSetMinReadySeconds` | `false` | Alpha | 1.22 | 1.22 |
+| `StatefulSetMinReadySeconds` | `true` | Beta | 1.23 | 1.24 |
+| `StatefulSetMinReadySeconds` | `true` | GA | 1.25 | 1.26 |
 | `StorageObjectInUseProtection` | `true` | Beta | 1.10 | 1.10 |
 | `StorageObjectInUseProtection` | `true` | GA | 1.11 | 1.24 |
 | `StreamingProxyRedirects` | `false` | Beta | 1.5 | 1.5 |
@@ -400,6 +429,18 @@ In the following table:
 - `CSIDriverRegistry`: Enable all logic related to the CSIDriver API object in
   `csi.storage.k8s.io`.
 
+- `CSIInlineVolume`: Enable CSI Inline volumes support for pods.
+
+- `CSIMigration`: Enables shims and translation logic to route volume
+  operations from in-tree plugins to corresponding pre-installed CSI plugins
+
+- `CSIMigrationAWS`: Enables shims and translation logic to route volume
+  operations from the AWS-EBS in-tree plugin to EBS CSI plugin. Supports
+  falling back to in-tree EBS plugin for mount operations to nodes that have
+  the feature disabled or that do not have EBS CSI plugin installed and
+  configured. Does not support falling back for provision operations, for those
+  the CSI plugin must be installed and configured.
+
 - `CSIMigrationAWSComplete`: Stops registering the EBS in-tree plugin in
   kubelet and volume controllers and enables shims and translation logic to
   route volume operations from the AWS-EBS in-tree plugin to EBS CSI plugin.
@@ -408,6 +449,14 @@ In the following table:
   been deprecated in favor of the `InTreePluginAWSUnregister` feature flag
   which prevents the registration of in-tree EBS plugin.
 
+- `CSIMigrationAzureDisk`: Enables shims and translation logic to route volume
+  operations from the Azure-Disk in-tree plugin to AzureDisk CSI plugin.
+  Supports falling back to in-tree AzureDisk plugin for mount operations to
+  nodes that have the feature disabled or that do not have AzureDisk CSI plugin
+  installed and configured. Does not support falling back for provision
+  operations, for those the CSI plugin must be installed and configured.
+  Requires CSIMigration feature flag enabled.
+
 - `CSIMigrationAzureDiskComplete`: Stops registering the Azure-Disk in-tree
   plugin in kubelet and volume controllers and enables shims and translation
   logic to route volume operations from the Azure-Disk in-tree plugin to
@@ -508,6 +557,10 @@ In the following table:
 - `CustomResourceWebhookConversion`: Enable webhook-based conversion
   on resources created from [CustomResourceDefinition](/docs/concepts/extend-kubernetes/api-extension/custom-resources/).
 
+- `DaemonSetUpdateSurge`: Enables the DaemonSet workloads to maintain
+  availability during update per node.
+  See [Perform a Rolling Update on a DaemonSet](/docs/tasks/manage-daemon/update-daemon-set/).
+
 - `DefaultPodTopologySpread`: Enables the use of `PodTopologySpread` scheduling plugin to do
   [default spreading](/docs/concepts/scheduling-eviction/topology-spread-constraints/#internal-default-constraints).
 
@@ -540,6 +593,10 @@ In the following table:
    Endpoints, enabling scalability and performance improvements. See
    [Enabling Endpoint Slices](/docs/concepts/services-networking/endpoint-slices/).
 
+- `EphemeralContainers`: Enable the ability to add
+  {{< glossary_tooltip text="ephemeral containers" term_id="ephemeral-container" >}}
+  to running Pods.
+
 - `EvenPodsSpread`: Enable pods to be scheduled evenly across topology domains. See
   [Pod Topology Spread Constraints](/docs/concepts/scheduling-eviction/topology-spread-constraints/).
 
@@ -608,6 +665,11 @@ In the following table:
   node disruption will ignore the `node-role.kubernetes.io/master` label in favor of the
   feature-specific labels provided by `NodeDisruptionExclusion` and `ServiceNodeExclusion`.
 
+- `LocalStorageCapacityIsolation`: Enable the consumption of
+  [local ephemeral storage](/docs/concepts/configuration/manage-resources-containers/)
+  and also the `sizeLimit` property of an
+  [emptyDir volume](/docs/concepts/storage/volumes/#emptydir).
+
 - `MountContainers`: Enable using utility containers on host as the volume mounter.
 
 - `MountPropagation`: Enable sharing volume mounted by one container to other containers or pods.
@@ -718,6 +780,9 @@ In the following table:
 - `StartupProbe`: Enable the [startup](/docs/concepts/workloads/pods/pod-lifecycle/#when-should-you-use-a-startup-probe)
   probe in the kubelet.
 
+- `StatefulSetMinReadySeconds`: Allows `minReadySeconds` to be respected by
+  the StatefulSet controller.
+
 - `StorageObjectInUseProtection`: Postpone the deletion of PersistentVolume or
   PersistentVolumeClaim objects if they are still being used.
 
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 7e157bd00f3..a68aa6a9a19 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
@@ -56,7 +56,6 @@ For a reference to old feature gates that are removed, please refer to
 
 | Feature | Default | Stage | Since | Until |
 |---------|---------|-------|-------|-------|
-| `AdmissionWebhookMatchConditions` | `false` | Alpha | 1.27 | |
 | `APIListChunking` | `false` | Alpha | 1.8 | 1.8 |
 | `APIListChunking` | `true` | Beta | 1.9 | |
 | `APIPriorityAndFairness` | `false` | Alpha | 1.18 | 1.19 |
@@ -69,6 +68,7 @@ For a reference to old feature gates that are removed, please refer to
 | `APIServerIdentity` | `true` | Beta | 1.26 | |
 | `APIServerTracing` | `false` | Alpha | 1.22 | 1.26 |
 | `APIServerTracing` | `true` | Beta | 1.27 | |
+| `AdmissionWebhookMatchConditions` | `false` | Alpha | 1.27 | |
 | `AggregatedDiscoveryEndpoint` | `false` | Alpha | 1.26 | 1.26 |
 | `AggregatedDiscoveryEndpoint` | `true` | Beta | 1.27 | |
 | `AnyVolumeDataSource` | `false` | Alpha | 1.18 | 1.23 |
@@ -84,7 +84,9 @@ For a reference to old feature gates that are removed, please refer to
 | `CSINodeExpandSecret` | `false` | Alpha | 1.25 | 1.26 |
 | `CSINodeExpandSecret` | `true` | Beta | 1.27 | |
 | `CSIVolumeHealth` | `false` | Alpha | 1.21 | |
+| `CloudControllerManagerWebhook` | false | Alpha | 1.27 | |
 | `CloudDualStackNodeIPs` | false | Alpha | 1.27 | |
+| `ClusterTrustBundle` | false | Alpha | 1.27 | |
 | `ComponentSLIs` | `false` | Alpha | 1.26 | 1.26 |
 | `ComponentSLIs` | `true` | Beta | 1.27 | |
 | `ContainerCheckpoint` | `false` | Alpha | 1.25 | |
@@ -110,7 +112,9 @@ For a reference to old feature gates that are removed, please refer to
 | `HPAContainerMetrics` | `true` | Beta | 1.27 | |
 | `HPAScaleToZero` | `false` | Alpha | 1.16 | |
 | `HonorPVReclaimPolicy` | `false` | Alpha | 1.23 |  |
-| `IPTablesOwnershipCleanup` | `false` | Alpha | 1.25 | |
+| `IPTablesOwnershipCleanup` | `false` | Alpha | 1.25 | 1.26 |
+| `IPTablesOwnershipCleanup` | `true` | Beta | 1.27 | |
+| `InPlacePodVerticalScaling` | `false` | Alpha | 1.27 | |
 | `InTreePluginAWSUnregister` | `false` | Alpha | 1.21 | |
 | `InTreePluginAzureDiskUnregister` | `false` | Alpha | 1.21 | |
 | `InTreePluginAzureFileUnregister` | `false` | Alpha | 1.21 | |
@@ -123,14 +127,15 @@ For a reference to old feature gates that are removed, please refer to
 | `JobPodFailurePolicy` | `true` | Beta | 1.26 | |
 | `JobReadyPods` | `false` | Alpha | 1.23 | 1.23 |
 | `JobReadyPods` | `true` | Beta | 1.24 | |
-| `KMSv2` | `false` | Alpha | 1.25 | |
+| `KMSv2` | `false` | Alpha | 1.25 | 1.26 |
+| `KMSv2` | `true` | Beta | 1.27 | |
 | `KubeletInUserNamespace` | `false` | Alpha | 1.22 | |
 | `KubeletPodResources` | `false` | Alpha | 1.13 | 1.14 |
 | `KubeletPodResources` | `true` | Beta | 1.15 | |
+| `KubeletPodResourcesDynamicResources` | `false` | Alpha | 1.27 | |
 | `KubeletPodResourcesGet` | `false` | Alpha | 1.27 | |
 | `KubeletPodResourcesGetAllocatable` | `false` | Alpha | 1.21 | 1.22 |
 | `KubeletPodResourcesGetAllocatable` | `true` | Beta | 1.23 | |
-| `KubeletPodResourcesDynamicResources` | `false` | Alpha | 1.27 | |
 | `KubeletTracing` | `false` | Alpha | 1.25 | 1.26 |
 | `KubeletTracing` | `true` | Beta | 1.27 | |
 | `LegacyServiceAccountTokenTracking` | `false` | Alpha | 1.26 | 1.26 |
@@ -149,10 +154,8 @@ For a reference to old feature gates that are removed, please refer to
 | `MinDomainsInPodTopologySpread` | `false` | Alpha | 1.24 | 1.24 |
 | `MinDomainsInPodTopologySpread` | `false` | Beta | 1.25 | 1.26 |
 | `MinDomainsInPodTopologySpread` | `true` | Beta | 1.27 | |
-| `MixedProtocolLBService` | `false` | Alpha | 1.20 | 1.23 |
-| `MixedProtocolLBService` | `true` | Beta | 1.24 | |
-| `MinDomainsInPodTopologySpread` | `false` | Beta | 1.25 | |
-| `MinimizeIPTablesRestore` | `false` | Alpha | 1.26 | - |
+| `MinimizeIPTablesRestore` | `false` | Alpha | 1.26 | 1.26 |
+| `MinimizeIPTablesRestore` | `true` | Beta | 1.27 | |
 | `MultiCIDRRangeAllocator` | `false` | Alpha | 1.25 | |
 | `MultiCIDRServiceAllocator` | `false` | Alpha | 1.27 | |
 | `NetworkPolicyStatus` | `false` | Alpha | 1.24 |  |
@@ -193,9 +196,11 @@ For a reference to old feature gates that are removed, please refer to
 | `RotateKubeletServerCertificate` | `true` | Beta | 1.12 | |
 | `SELinuxMountReadWriteOncePod` | `false` | Alpha | 1.25 | 1.26 |
 | `SELinuxMountReadWriteOncePod` | `true` | Beta | 1.27 | |
+| `SecurityContextDeny` | `false` | Alpha | 1.27 | |
 | `ServiceNodePortStaticSubrange` | `false` | Alpha | 1.27 | |
 | `SizeMemoryBackedVolumes` | `false` | Alpha | 1.20 | 1.21 |
 | `SizeMemoryBackedVolumes` | `true` | Beta | 1.22 | |
+| `StableLoadBalancerNodeGet` | `true` | Beta | 1.27 | |
 | `StatefulSetAutoDeletePVC` | `false` | Alpha | 1.22 | 1.26 |
 | `StatefulSetAutoDeletePVC` | `false` | Beta | 1.27 | |
 | `StatefulSetStartOrdinal` | `false` | Alpha | 1.26 | 1.26 |
@@ -231,20 +236,6 @@ For a reference to old feature gates that are removed, please refer to
 | `CPUManager` | `false` | Alpha | 1.8 | 1.9 |
 | `CPUManager` | `true` | Beta | 1.10 | 1.25 |
 | `CPUManager` | `true` | GA | 1.26 | - |
-| `CSIInlineVolume` | `false` | Alpha | 1.15 | 1.15 |
-| `CSIInlineVolume` | `true` | Beta | 1.16 | 1.24 |
-| `CSIInlineVolume` | `true` | GA | 1.25 | - |
-| `CSIMigration` | `false` | Alpha | 1.14 | 1.16 |
-| `CSIMigration` | `true` | Beta | 1.17 | 1.24 |
-| `CSIMigration` | `true` | GA | 1.25 | - |
-| `CSIMigrationAWS` | `false` | Alpha | 1.14 | 1.16 |
-| `CSIMigrationAWS` | `false` | Beta | 1.17 | 1.22 |
-| `CSIMigrationAWS` | `true` | Beta | 1.23 | 1.24 |
-| `CSIMigrationAWS` | `true` | GA | 1.25 | - |
-| `CSIMigrationAzureDisk` | `false` | Alpha | 1.15 | 1.18 |
-| `CSIMigrationAzureDisk` | `false` | Beta | 1.19 | 1.22 |
-| `CSIMigrationAzureDisk` | `true` | Beta | 1.23 | 1.23 |
-| `CSIMigrationAzureDisk` | `true` | GA | 1.24 | |
 | `CSIMigrationAzureFile` | `false` | Alpha | 1.15 | 1.20 |
 | `CSIMigrationAzureFile` | `false` | Beta | 1.21 | 1.23 |
 | `CSIMigrationAzureFile` | `true` | Beta | 1.24 | 1.25 |
@@ -264,9 +255,6 @@ For a reference to old feature gates that are removed, please refer to
 | `CronJobTimeZone` | `false` | Alpha | 1.24 | 1.24 |
 | `CronJobTimeZone` | `true` | Beta | 1.25 | 1.26 |
 | `CronJobTimeZone` | `true` | GA | 1.27 | - |
-| `DaemonSetUpdateSurge` | `false` | Alpha | 1.21 | 1.21 |
-| `DaemonSetUpdateSurge` | `true` | Beta | 1.22 | 1.24 |
-| `DaemonSetUpdateSurge` | `true` | GA | 1.25 | - |
 | `DelegateFSGroupToCSIDriver` | `false` | Alpha | 1.22 | 1.22 |
 | `DelegateFSGroupToCSIDriver` | `true` | Beta | 1.23 | 1.25 |
 | `DelegateFSGroupToCSIDriver` | `true` | GA | 1.26 |-|
@@ -289,18 +277,12 @@ For a reference to old feature gates that are removed, please refer to
 | `EndpointSliceTerminatingCondition` | `false` | Alpha | 1.20 | 1.21 |
 | `EndpointSliceTerminatingCondition` | `true` | Beta | 1.22 | 1.25 |
 | `EndpointSliceTerminatingCondition` | `true` | GA | 1.26 | |
-| `EphemeralContainers` | `false` | Alpha | 1.16 | 1.22 |
-| `EphemeralContainers` | `true` | Beta | 1.23 | 1.24 |
-| `EphemeralContainers` | `true` | GA | 1.25 | - |
 | `ExecProbeTimeout` | `true` | GA | 1.20 | - |
-| `JobMutableNodeSchedulingDirectives` | `true` | Beta | 1.23 | 1.26 |
-| `JobMutableNodeSchedulingDirectives` | `true` | GA | 1.27 | |
 | `GRPCContainerProbe` | `false` | Alpha | 1.23 | 1.23 |
 | `GRPCContainerProbe` | `true` | Beta | 1.24 | 1.26 |
 | `GRPCContainerProbe` | `true` | GA | 1.27 | |
-| `IdentifyPodOS` | `false` | Alpha | 1.23 | 1.23 |
-| `IdentifyPodOS` | `true` | Beta | 1.24 | 1.24 |
-| `IdentifyPodOS` | `true` | GA | 1.25 | - |
+| `JobMutableNodeSchedulingDirectives` | `true` | Beta | 1.23 | 1.26 |
+| `JobMutableNodeSchedulingDirectives` | `true` | GA | 1.27 | |
 | `JobTrackingWithFinalizers` | `false` | Alpha | 1.22 | 1.22 |
 | `JobTrackingWithFinalizers` | `false` | Beta | 1.23 | 1.24 |
 | `JobTrackingWithFinalizers` | `true` | Beta | 1.25 | 1.25 |
@@ -310,15 +292,12 @@ For a reference to old feature gates that are removed, please refer to
 | `KubeletCredentialProviders` | `true` | GA | 1.26 | - |
 | `LegacyServiceAccountTokenNoAutoGeneration` | `true` | Beta | 1.24 | 1.25 |
 | `LegacyServiceAccountTokenNoAutoGeneration` | `true` | GA | 1.26 | - |
-| `LocalStorageCapacityIsolation` | `false` | Alpha | 1.7 | 1.9 |
-| `LocalStorageCapacityIsolation` | `true` | Beta | 1.10 | 1.24 |
-| `LocalStorageCapacityIsolation` | `true` | GA | 1.25 | - |
 | `MixedProtocolLBService` | `false` | Alpha | 1.20 | 1.23 |
 | `MixedProtocolLBService` | `true` | Beta | 1.24 | 1.25 |
 | `MixedProtocolLBService` | `true` | GA | 1.26 | - |
-| `NetworkPolicyEndPort` | `false` | Alpha | 1.21 | 1.21 |
-| `NetworkPolicyEndPort` | `true` | Beta | 1.22 | 1.24 |
-| `NetworkPolicyEndPort` | `true` | GA | 1.25 | - |
+| `OpenAPIV3` | `false` | Alpha | 1.23 | 1.23 |
+| `OpenAPIV3` | `true` | Beta | 1.24 | 1.26 |
+| `OpenAPIV3` | `true` | GA | 1.27 | - |
 | `PodSecurity` | `false` | Alpha | 1.22 | 1.22 |
 | `PodSecurity` | `true` | Beta | 1.23 | 1.24 |
 | `PodSecurity` | `true` | GA | 1.25 | |
@@ -334,18 +313,12 @@ For a reference to old feature gates that are removed, please refer to
 | `ServerSideFieldValidation` | `false` | Alpha | 1.23 | 1.24 |
 | `ServerSideFieldValidation` | `true` | Beta | 1.25 | 1.26 |
 | `ServerSideFieldValidation` | `true` | GA | 1.27 | - |
-| `OpenAPIV3` | `false` | Alpha | 1.23 | 1.23 |
-| `OpenAPIV3` | `true` | Beta | 1.24 | 1.26 |
-| `OpenAPIV3` | `true` | GA | 1.27 | - |
 | `ServiceIPStaticSubrange` | `false` | Alpha | 1.24 | 1.24 |
 | `ServiceIPStaticSubrange` | `true` | Beta | 1.25 | 1.25 |
 | `ServiceIPStaticSubrange` | `true` | GA | 1.26 | - |
 | `ServiceInternalTrafficPolicy` | `false` | Alpha | 1.21 | 1.21 |
 | `ServiceInternalTrafficPolicy` | `true` | Beta | 1.22 | 1.25 |
 | `ServiceInternalTrafficPolicy` | `true` | GA | 1.26 | - |
-| `StatefulSetMinReadySeconds` | `false` | Alpha | 1.22 | 1.22 |
-| `StatefulSetMinReadySeconds` | `true` | Beta | 1.23 | 1.24 |
-| `StatefulSetMinReadySeconds` | `true` | GA | 1.25 | - |
 | `TopologyManager` | `false` | Alpha | 1.16 | 1.17 |
 | `TopologyManager` | `true` | Beta | 1.18 | 1.26 |
 | `TopologyManager` | `true` | GA | 1.27 | - |
@@ -400,7 +373,8 @@ A *General Availability* (GA) feature is also referred to as a *stable* feature.
 
 Each feature gate is designed for enabling/disabling a specific feature:
 
-- `AdmissionWebhookMatchConditions`: Enable [match conditions](/docs/reference/access-authn-authz/extensible-admission-controllers/#matching-requests-matchconditions) on mutating & validating admission webhooks.
+- `AdmissionWebhookMatchConditions`: Enable [match conditions](/docs/reference/access-authn-authz/extensible-admission-controllers/#matching-requests-matchconditions)
+  on mutating & validating admission webhooks.
 - `APIListChunking`: Enable the API clients to retrieve (`LIST` or `GET`)
   resources from API server in chunks.
 - `APIPriorityAndFairness`: Enable managing request concurrency with
@@ -420,11 +394,6 @@ Each feature gate is designed for enabling/disabling a specific feature:
   {{< glossary_tooltip text="PVC" term_id="persistent-volume-claim" >}}.
 - `AppArmor`: Enable use of AppArmor mandatory access control for Pods running on Linux nodes.
   See [AppArmor Tutorial](/docs/tutorials/security/apparmor/) for more details.
-- `CloudDualStackNodeIPs`: Enables dual-stack `kubelet --node-ip` with external cloud providers.
-  See [Configure IPv4/IPv6 dual-stack](/docs/concepts/services-networking/dual-stack/#configure-ipv4-ipv6-dual-stack)
-  for more details.
-- `ContainerCheckpoint`: Enables the kubelet `checkpoint` API.
-  See [Kubelet Checkpoint API](/docs/reference/node/kubelet-checkpoint-api/) for more details.
 - `CPUManager`: Enable container level CPU affinity support, see
   [CPU Management Policies](/docs/tasks/administer-cluster/cpu-management-policies/).
 - `CPUManagerPolicyAlphaOptions`: This allows fine-tuning of CPUManager policies,
@@ -436,22 +405,6 @@ Each feature gate is designed for enabling/disabling a specific feature:
   This feature gate guards *a group* of CPUManager options whose quality level is beta.
   This feature gate will never graduate to stable.
 - `CPUManagerPolicyOptions`: Allow fine-tuning of CPUManager policies.
-- `CSIInlineVolume`: Enable CSI Inline volumes support for pods.
-- `CSIMigration`: Enables shims and translation logic to route volume
-  operations from in-tree plugins to corresponding pre-installed CSI plugins
-- `CSIMigrationAWS`: Enables shims and translation logic to route volume
-  operations from the AWS-EBS in-tree plugin to EBS CSI plugin. Supports
-  falling back to in-tree EBS plugin for mount operations to nodes that have
-  the feature disabled or that do not have EBS CSI plugin installed and
-  configured. Does not support falling back for provision operations, for those
-  the CSI plugin must be installed and configured.
-- `CSIMigrationAzureDisk`: Enables shims and translation logic to route volume
-  operations from the Azure-Disk in-tree plugin to AzureDisk CSI plugin.
-  Supports falling back to in-tree AzureDisk plugin for mount operations to
-  nodes that have the feature disabled or that do not have AzureDisk CSI plugin
-  installed and configured. Does not support falling back for provision
-  operations, for those the CSI plugin must be installed and configured.
-  Requires CSIMigration feature flag enabled.
 - `CSIMigrationAzureFile`: Enables shims and translation logic to route volume
   operations from the Azure-File in-tree plugin to AzureFile CSI plugin.
   Supports falling back to in-tree AzureFile plugin for mount operations to
@@ -489,11 +442,18 @@ Each feature gate is designed for enabling/disabling a specific feature:
   [Storage Capacity](/docs/concepts/storage/storage-capacity/).
   Check the [`csi` volume type](/docs/concepts/storage/volumes/#csi) documentation for more details.
 - `CSIVolumeHealth`: Enable support for CSI volume health monitoring on node.
+- `CloudControllerManagerWebhook`: Enable webhooks in cloud controller manager.
+- `CloudDualStackNodeIPs`: Enables dual-stack `kubelet --node-ip` with external cloud providers.
+  See [Configure IPv4/IPv6 dual-stack](/docs/concepts/services-networking/dual-stack/#configure-ipv4-ipv6-dual-stack)
+  for more details.
+- `ClusterTrustBundle`: Enable ClusterTrustBundle objects and kubelet integration.
 - `ComponentSLIs`: Enable the `/metrics/slis` endpoint on Kubernetes components like
   kubelet, kube-scheduler, kube-proxy, kube-controller-manager, cloud-controller-manager
   allowing you to scrape health check metrics.
 - `ConsistentHTTPGetHandlers`: Normalize HTTP get URL and Header passing for lifecycle
   handlers with probers.
+- `ContainerCheckpoint`: Enables the kubelet `checkpoint` API.
+  See [Kubelet Checkpoint API](/docs/reference/node/kubelet-checkpoint-api/) for more details.
 - `ContextualLogging`: When you enable this feature gate, Kubernetes components that support
    contextual logging add extra detail to log output.
 - `CronJobTimeZone`: Allow the use of the `timeZone` optional field in [CronJobs](/docs/concepts/workloads/controllers/cron-jobs/)
@@ -505,9 +465,6 @@ Each feature gate is designed for enabling/disabling a specific feature:
 - `CustomResourceValidationExpressions`: Enable expression language validation in CRD
   which will validate customer resource based on validation rules written in
   the `x-kubernetes-validations` extension.
-- `DaemonSetUpdateSurge`: Enables the DaemonSet workloads to maintain
-  availability during update per node.
-  See [Perform a Rolling Update on a DaemonSet](/docs/tasks/manage-daemon/update-daemon-set/).
 - `DelegateFSGroupToCSIDriver`: If supported by the CSI driver, delegates the
   role of applying `fsGroup` from a Pod's `securityContext` to the driver by
   passing `fsGroup` through the NodeStageVolume and NodePublishVolume CSI calls.
@@ -534,9 +491,6 @@ Each feature gate is designed for enabling/disabling a specific feature:
    condition fields.
 - `EfficientWatchResumption`: Allows for storage-originated bookmark (progress
   notify) events to be delivered to the users. This is only applied to watch operations.
-- `EphemeralContainers`: Enable the ability to add
-  {{< glossary_tooltip text="ephemeral containers" term_id="ephemeral-container" >}}
-  to running pods.
 - `EventedPLEG`: Enable support for the kubelet to receive container life cycle events from the
   {{< glossary_tooltip text="container runtime" term_id="container-runtime" >}} via
   an extension to {{<glossary_tooltip term_id="cri" text="CRI">}}.
@@ -576,6 +530,7 @@ Each feature gate is designed for enabling/disabling a specific feature:
 - `HPAScaleToZero`: Enables setting `minReplicas` to 0 for `HorizontalPodAutoscaler`
   resources when using custom or external metrics.
 - `IPTablesOwnershipCleanup`: This causes kubelet to no longer create legacy iptables rules.
+- `InPlacePodVerticalScaling`: Enables in-place Pod vertical scaling.
 - `InTreePluginAWSUnregister`: Stops registering the aws-ebs in-tree plugin in kubelet
   and volume controllers.
 - `InTreePluginAzureDiskUnregister`: Stops registering the azuredisk in-tree plugin in kubelet
@@ -632,10 +587,6 @@ Each feature gate is designed for enabling/disabling a specific feature:
   [service account tokens](/docs/reference/access-authn-authz/authentication/#service-account-tokens).
 - `LegacyServiceAccountTokenTracking`: Track usage of Secret-based
   [service account tokens](/docs/reference/access-authn-authz/authentication/#service-account-tokens).
-- `LocalStorageCapacityIsolation`: Enable the consumption of
-  [local ephemeral storage](/docs/concepts/configuration/manage-resources-containers/)
-  and also the `sizeLimit` property of an
-  [emptyDir volume](/docs/concepts/storage/volumes/#emptydir).
 - `LocalStorageCapacityIsolationFSQuotaMonitoring`: When `LocalStorageCapacityIsolation`
   is enabled for
   [local ephemeral storage](/docs/concepts/configuration/manage-resources-containers/)
@@ -665,8 +616,6 @@ Each feature gate is designed for enabling/disabling a specific feature:
   Service instance.
 - `MultiCIDRRangeAllocator`: Enables the MultiCIDR range allocator.
 - `MultiCIDRServiceAllocator`: Track IP address allocations for Service cluster IPs using IPAddress objects.
-- `NetworkPolicyEndPort`: Enable use of the field `endPort` in NetworkPolicy objects,
-  allowing the selection of a port range instead of a single port.
 - `NetworkPolicyStatus`: Enable the `status` subresource for NetworkPolicy objects.
 - `NewVolumeManagerReconstruction`: Enable improved discovery of mounted volumes during kubelet
   startup.
@@ -684,6 +633,7 @@ Each feature gate is designed for enabling/disabling a specific feature:
 - `NodeInclusionPolicyInPodTopologySpread`: Enable using `nodeAffinityPolicy` and `nodeTaintsPolicy` in
   [Pod topology spread constraints](/docs/concepts/scheduling-eviction/topology-spread-constraints/)
   when calculating pod topology spread skew.
+- `NodeLogQuery`: Enables querying logs of node services using the `/logs` endpoint.
 - `NodeOutOfServiceVolumeDetach`: When a Node is marked out-of-service using the
   `node.kubernetes.io/out-of-service` taint, Pods on the node will be forcefully deleted
    if they can not tolerate this taint, and the volume detach operations for Pods terminating
@@ -739,6 +689,7 @@ Each feature gate is designed for enabling/disabling a specific feature:
 - `SeccompDefault`: Enables the use of `RuntimeDefault` as the default seccomp profile
   for all workloads.
   The seccomp profile is specified in the `securityContext` of a Pod and/or a Container.
+- `SecurityContextDeny`: This gate signals that the `SecurityContextDeny` admission controller is deprecated.
 - `ServerSideApply`: Enables the [Sever Side Apply (SSA)](/docs/reference/using-api/server-side-apply/)
   feature on the API Server.
 - `ServerSideFieldValidation`: Enables server-side field validation. This means the validation
@@ -753,8 +704,8 @@ Each feature gate is designed for enabling/disabling a specific feature:
   for more details.
 - `SizeMemoryBackedVolumes`: Enable kubelets to determine the size limit for
   memory-backed volumes (mainly `emptyDir` volumes).
-- `StatefulSetMinReadySeconds`: Allows `minReadySeconds` to be respected by
-  the StatefulSet controller.
+- `StableLoadBalancerNodeGet`: Enables less load balancer re-configurations by 
+  the service controller (KCCM) as an effect of changing node state.
 - `StatefulSetStartOrdinal`: Allow configuration of the start ordinal in a
   StatefulSet. See
   [Start ordinal](/docs/concepts/workloads/controllers/statefulset/#start-ordinal)

From 8095fdb540aec1a0400fe95a0a6db11dbbe87ccf Mon Sep 17 00:00:00 2001
From: mostafahanafi <mostafahanafi2001@hotmail.com>
Date: Fri, 21 Apr 2023 05:46:57 +0100
Subject: [PATCH 251/272] changed selection color to kubernetes blue

---
 assets/scss/_base.scss | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/assets/scss/_base.scss b/assets/scss/_base.scss
index 8b2cc87b3ec..20025064d2b 100644
--- a/assets/scss/_base.scss
+++ b/assets/scss/_base.scss
@@ -102,6 +102,16 @@ main {
   }
 }
 
+::selection {
+  background: #326ce5;
+  color: white;
+}
+
+::-moz-selection {
+  background: #326ce5;
+  color: white;
+}
+
 // HEADER
 
 #hamburger {

From 8c9dab43d3e6c39f01fd533bf1631473c9eddb01 Mon Sep 17 00:00:00 2001
From: "xin.li" <xin.li@daocloud.io>
Date: Fri, 21 Apr 2023 23:20:48 +0800
Subject: [PATCH 252/272] [zh-cn] sync
 configure-liveness-readiness-startup-probes.md security-context.md and
 assign-memory-resource.md

Signed-off-by: xin.li <xin.li@daocloud.io>
---
 .../assign-memory-resource.md                 |  7 ++-
 ...igure-liveness-readiness-startup-probes.md | 57 ++++++++++++-------
 .../security-context.md                       | 45 ++++++++-------
 3 files changed, 67 insertions(+), 42 deletions(-)

diff --git a/content/zh-cn/docs/tasks/configure-pod-container/assign-memory-resource.md b/content/zh-cn/docs/tasks/configure-pod-container/assign-memory-resource.md
index 71ac184837d..15407495914 100644
--- a/content/zh-cn/docs/tasks/configure-pod-container/assign-memory-resource.md
+++ b/content/zh-cn/docs/tasks/configure-pod-container/assign-memory-resource.md
@@ -98,8 +98,8 @@ for the Pod:
 -->
 ## 指定内存请求和限制    {#specify-a-memory-request-and-a-memory-limit}
 
-要为容器指定内存请求，请在容器资源清单中包含 `resources：requests` 字段。
-同理，要指定内存限制，请包含 `resources：limits`。
+要为容器指定内存请求，请在容器资源清单中包含 `resources: requests` 字段。
+同理，要指定内存限制，请包含 `resources: limits`。
 
 在本练习中，你将创建一个拥有一个容器的 Pod。
 容器将会请求 100 MiB 内存，并且内存会被限制在 200 MiB 以内。
@@ -544,6 +544,8 @@ kubectl delete namespace mem-example
 * [Configure a Pod Quota for a Namespace](/docs/tasks/administer-cluster/manage-resources/quota-pod-namespace/)
 
 * [Configure Quotas for API Objects](/docs/tasks/administer-cluster/quota-api-object/)
+
+* [Resize CPU and Memory Resources assigned to Containers](/docs/tasks/configure-pod-container/resize-container-resources/)
 -->
 ### 集群管理员扩展阅读    {#for-cluster-administrators}
 
@@ -554,4 +556,5 @@ kubectl delete namespace mem-example
 * [为命名空间配置内存和 CPU 配额](/zh-cn/docs/tasks/administer-cluster/manage-resources/quota-memory-cpu-namespace/)
 * [配置命名空间下 Pod 总数](/zh-cn/docs/tasks/administer-cluster/manage-resources/quota-pod-namespace/)
 * [配置 API 对象配额](/zh-cn/docs/tasks/administer-cluster/quota-api-object/)
+* [调整分配给容器的 CPU 和内存资源的大小](/docs/tasks/configure-pod-container/resize-container-resources/)
 
diff --git a/content/zh-cn/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md b/content/zh-cn/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
index 6bb607d51a1..4ad57c2e29f 100644
--- a/content/zh-cn/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
+++ b/content/zh-cn/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
@@ -31,7 +31,6 @@ A common pattern for liveness probes is to use the same low-cost HTTP endpoint
 s for readiness probes, but with a higher failureThreshold. This ensures that the pod
 is observed as not-ready for some period of time before it is hard killed.
 -->
-
 存活探针的常见模式是为就绪探针使用相同的低成本 HTTP 端点，但具有更高的 failureThreshold。
 这样可以确保在硬性终止 Pod 之前，将观察到 Pod 在一段时间内处于非就绪状态。
 
@@ -75,8 +74,9 @@ scalable; and increased workload on remaining pods due to some failed pods.
 Understand the difference between readiness and liveness probes and when to apply them for your app.
 -->
 错误的存活探针可能会导致级联故障。
-这会导致在高负载下容器重启；例如由于应用程序无法扩展，导致客户端请求失败；以及由于某些 Pod 失败而导致剩余 Pod 的工作负载增加。
-了解就绪探针和存活探针之间的区别，以及何时为应用程序配置使用它们非常重要。
+这会导致在高负载下容器重启；例如由于应用程序无法扩展，导致客户端请求失败；以及由于某些
+Pod 失败而导致剩余 Pod 的工作负载增加。了解就绪探针和存活探针之间的区别，
+以及何时为应用程序配置使用它们非常重要。
 {{< /note >}}
 
 ## {{% heading "prerequisites" %}}
@@ -247,7 +247,7 @@ and restarts it.
 `periodSeconds` 字段指定了 kubelet 每隔 3 秒执行一次存活探测。
 `initialDelaySeconds` 字段告诉 kubelet 在执行第一次探测前应该等待 3 秒。
 kubelet 会向容器内运行的服务（服务在监听 8080 端口）发送一个 HTTP GET 请求来执行探测。
-如果服务器上 `/healthz`  路径下的处理程序返回成功代码，则 kubelet 认为容器是健康存活的。
+如果服务器上 `/healthz` 路径下的处理程序返回成功代码，则 kubelet 认为容器是健康存活的。
 如果处理程序返回失败代码，则 kubelet 会杀死这个容器并将其重启。
 
 <!--
@@ -262,7 +262,7 @@ returns a status of 200. After that, the handler returns a status of 500.
 -->
 返回大于或等于 200 并且小于 400 的任何代码都标示成功，其它返回代码都标示失败。
 
-你可以访问 [server.go](https://github.com/kubernetes/kubernetes/blob/master/test/images/agnhost/liveness/server.go)。
+你可以访问 [server.go](https://github.com/kubernetes/kubernetes/blob/master/test/images/agnhost/liveness/server.go)
 阅读服务的源码。
 容器存活期间的最开始 10 秒中，`/healthz` 处理程序返回 200 的状态码。
 之后处理程序返回 500 的状态码。
@@ -380,11 +380,9 @@ kubectl describe pod goproxy
 {{< feature-state for_k8s_version="v1.24" state="beta" >}}
 
 <!--
-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.
+If your application implements the [gRPC Health Checking Protocol](https://github.com/grpc/grpc/blob/master/doc/health-checking.md),
+this example shows how to configure Kubernetes to use it for application liveness checks.
+Similarly you can configure readiness and startup probes.
 
 Here is an example manifest:
 -->
@@ -395,22 +393,40 @@ kubelet 可以配置为使用该协议来执行应用存活性检查。
 [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)
 才能配置依赖于 gRPC 的检查机制。
 
+这个例子展示了如何配置 Kubernetes 以将其用于应用程序的存活性检查。
+类似地，你可以配置就绪探针和启动探针。
+
 下面是一个示例清单：
 
 {{< 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, you must also specify the `service`.
+To use a gRPC probe, `port` must be configured. If you want to distinguish probes of different types
+and probes for different features you can use the `service` field.
+You can set `service` to the value `liveness` and make your gRPC Health Checking endpoint
+respond to this request differently then when you set `service` set to `readiness`.
+This lets you use the same endpoint for different kinds of container health check
+(rather than needing to listen on two different ports).
+If you want to specify your own custom service name and also specify a probe type,
+the Kubernetes project recommends that you use a name that concatenates
+those. For example: `myservice-liveness` (using `-` as a separator).
 -->
-要使用 gRPC 探针，必须配置 `port` 属性。如果健康状态端点配置在非默认服务之上，
-你还必须设置 `service` 属性。
+要使用 gRPC 探针，必须配置 `port` 属性。
+如果要区分不同类型的探针和不同功能的探针，可以使用 `service` 字段。
+你可以将 `service` 设置为 `liveness`，并使你的 gRPC
+健康检查端点对该请求的响应与将 `service` 设置为 `readiness` 时不同。
+这使你可以使用相同的端点进行不同类型的容器健康检查（而不需要在两个不同的端口上侦听）。
+如果你想指定自己的自定义服务名称并指定探测类型，Kubernetes
+项目建议你使用使用一个可以关联服务和探测类型的名称来命名。
+例如：`myservice-liveness`（使用 `-` 作为分隔符）。
 
 {{< note >}}
 <!--
-Unlike HTTP and TCP probes, named ports cannot be used and custom host cannot be configured.
+Unlike HTTP and TCP probes, you cannot specify the healthcheck port by name, and you
+cannot configure a custom hostname.
 -->
-与 HTTP 和 TCP 探针不同，gRPC 探测不能使用命名端口或定制主机。
+与 HTTP 和 TCP 探针不同，gRPC 探测不能使用按名称指定端口，
+也不能自定义主机名。
 {{< /note >}}
 
 <!--
@@ -580,7 +596,7 @@ Readiness probes runs on the container during its whole lifecycle.
 <!--
 Liveness probes *do not* wait for readiness probes to succeed. If you want to wait before executing a liveness probe you should use initialDelaySeconds or a startupProbe.
 -->
-存活探针 **不等待** 就绪性探针成功。
+存活探针**不等待**就绪性探针成功。
 如果要在执行存活探针之前等待，应该使用 `initialDelaySeconds` 或 `startupProbe`。
 {{< /caution >}}
 
@@ -751,8 +767,8 @@ in the range 1 to 65535.
 [HTTP Probes](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#httpgetaction-v1-core)
 允许针对 `httpGet` 配置额外的字段：
 
-* `host`：连接使用的主机名，默认是 Pod 的 IP。也可以在 HTTP 头中设置 “Host” 来代替。
-* `scheme` ：用于设置连接主机的方式（HTTP 还是 HTTPS）。默认是 "HTTP"。
+* `host`：连接使用的主机名，默认是 Pod 的 IP。也可以在 HTTP 头中设置 "Host" 来代替。
+* `scheme`：用于设置连接主机的方式（HTTP 还是 HTTPS）。默认是 "HTTP"。
 * `path`：访问 HTTP 服务的路径。默认值为 "/"。
 * `httpHeaders`：请求中自定义的 HTTP 头。HTTP 头字段允许重复。
 * `port`：访问容器的端口号或者端口名。如果数字必须在 1～65535 之间。
@@ -840,7 +856,7 @@ to resolve it.
 -->
 ### 探针层面的 `terminationGracePeriodSeconds`
 
-{{< feature-state for_k8s_version="v1.25" state="beta" >}}
+{{< feature-state for_k8s_version="v1.27" state="stable" >}}
 
 <!--
 Prior to release 1.21, the pod-level `terminationGracePeriodSeconds` was used
@@ -871,7 +887,6 @@ by default. For users choosing to disable this feature, please note the followin
 * The `ProbeTerminationGracePeriod` feature gate is only available on the API Server. 
 The kubelet always honors the probe-level `terminationGracePeriodSeconds` field if 
 it is present on a Pod.
-
 -->
 {{< note >}}
 从 Kubernetes 1.25 开始，默认启用 `ProbeTerminationGracePeriod` 特性。
diff --git a/content/zh-cn/docs/tasks/configure-pod-container/security-context.md b/content/zh-cn/docs/tasks/configure-pod-container/security-context.md
index fdd0c680447..3e2c7ca1172 100644
--- a/content/zh-cn/docs/tasks/configure-pod-container/security-context.md
+++ b/content/zh-cn/docs/tasks/configure-pod-container/security-context.md
@@ -710,7 +710,7 @@ To assign SELinux labels, the SELinux security module must be loaded on the host
 -->
 ### 高效重打 SELinux 卷标签
 
-{{< feature-state for_k8s_version="v1.25" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.27" state="beta" >}}
 
 <!--
 By default, the container runtime recursively assigns SELinux label to all
@@ -727,10 +727,11 @@ To benefit from this speedup, all these conditions must be met:
 要使用这项加速功能，必须满足下列条件：
 
 <!--
-* Alpha feature gates `ReadWriteOncePod` and `SELinuxMountReadWriteOncePod` must
-  be enabled.
+* The [feature gates](/docs/reference/command-line-tools-reference/feature-gates/) `ReadWriteOncePod`
+  and `SELinuxMountReadWriteOncePod` must be enabled.
 -->
-* 必须启用 Alpha 特性门控 `ReadWriteOncePod` 和 `SELinuxMountReadWriteOncePod`。
+* 必须启用 `ReadWriteOncePod` 和 `SELinuxMountReadWriteOncePod`
+  [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)。
 
 <!--
 * Pod must use PersistentVolumeClaim with `accessModes: ["ReadWriteOncePod"]`.
@@ -750,11 +751,18 @@ To benefit from this speedup, all these conditions must be met:
   * If you use a volume backed by a CSI driver, that CSI driver must announce that it
     supports mounting with `-o context` by setting `spec.seLinuxMount: true` in
     its CSIDriver instance.
+
+* The corresponding PersistentVolume must be either:
+  * A volume that uses the legacy in-tree `iscsi`, `rbd` or `fc` volume type.
+  * Or a volume that uses a {{< glossary_tooltip text="CSI" term_id="csi" >}} driver.
+    The CSI driver must announce that it supports mounting with `-o context` by setting
+    `spec.seLinuxMount: true` in its CSIDriver instance.
 -->
-* 对应的 PersistentVolume 必须是使用 {< glossary_tooltip text="CSI" term_id="csi" >}}
-  驱动程序的卷，或者是传统的 `iscsi` 卷类型的卷。
-  * 如果使用基于 CSI 驱动程序的卷，CSI 驱动程序必须能够通过在 CSIDriver
-    实例中设置 `spec.seLinuxMount: true` 以支持 `-o context` 挂载。
+* 对应的 PersistentVolume 必须是：
+  * 使用传统树内（In-Tree） `iscsi`、`rbd` 或 `fs` 卷类型的卷。
+  * 或者是使用 {< glossary_tooltip text="CSI" term_id="csi" >}} 驱动程序的卷
+    CSI 驱动程序必须能够通过在 CSIDriver 实例中设置 `spec.seLinuxMount: true`
+    以支持 `-o context` 挂载。
 
 <!--
 For any other volume types, SELinux relabelling happens another way: the container
@@ -767,19 +775,18 @@ The more files and directories in the volume, the longer that relabelling takes.
 卷中的文件和目录越多，重打标签需要耗费的时间就越长。
 
 {{< note >}}
+<!-- remove after Kubernetes v1.30 is released -->
 <!--
-In Kubernetes 1.25, the kubelet loses track of volume labels after restart. In
-other words, then kubelet may refuse to start Pods with errors similar to  "conflicting
-SELinux labels of volume", while there are no conflicting labels in Pods. Make sure
-nodes are
-[fully drained](https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/)
-before restarting kubelet.
+If you are running Kubernetes v1.25, refer to the v1.25 version of this task page:
+[Configure a Security Context for a Pod or Container](https://v1-25.docs.kubernetes.io/docs/tasks/configure-pod-container/security-context/) (v1.25).  
+There is an important note in that documentation about a situation where the kubelet
+can lose track of volume labels after restart. This deficiency has been fixed
+in Kubernetes 1.26.
 -->
-在 Kubernetes 1.25 中，kubelet 在重启后会丢失对卷标签的追踪记录。
-换言之，kubelet 可能会拒绝启动 Pod，原因类似于 “conflicting
-SELinux labels of volume”，
-但实际上 Pod 中并没有冲突的标签。在重启 kubelet
-之前确保节点已被[完全腾空](/zh-cn/docs/tasks/administer-cluster/safely-drain-node/)。
+如果你的 Kubernetes 版本是 v1.25，请参阅此任务页面的 v1.25 版本：
+[为 Pod 或 Container 配置安全上下文](https://v1-25.docs.kubernetes.io/docs/tasks/configure-pod-container/security-context/)（v1.25）。
+该文档中有一个重要的说明：kubelet 在重启后会丢失对卷标签的追踪记录。
+这个缺陷已经在 Kubernetes 1.26 中修复。
 {{< /note >}}
 
 <!--

From 8ffca5bf24f765d6995497442bfad2b9d62b69d6 Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Thu, 20 Apr 2023 19:59:32 +0800
Subject: [PATCH 253/272] sync install-kubeadm.md

sync install-kubeadm.md
---
 .../production-environment/tools/kubeadm/install-kubeadm.md    | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/content/zh-cn/docs/setup/production-environment/tools/kubeadm/install-kubeadm.md b/content/zh-cn/docs/setup/production-environment/tools/kubeadm/install-kubeadm.md
index a2ffb2e18d2..dae206a0f04 100644
--- a/content/zh-cn/docs/setup/production-environment/tools/kubeadm/install-kubeadm.md
+++ b/content/zh-cn/docs/setup/production-environment/tools/kubeadm/install-kubeadm.md
@@ -41,6 +41,7 @@ see the [Creating a cluster with kubeadm](/docs/setup/production-environment/too
 * Unique hostname, MAC address, and product_uuid for every node. See [here](#verify-mac-address) for more details.
 * Certain ports are open on your machines. See [here](#check-required-ports) for more details.
 * Swap disabled. You **MUST** disable swap in order for the kubelet to work properly.
+    * For example, `sudo swapoff -a` will disable swapping temporarily. To make this change persistent across reboots, make sure swap is disabled in config files like `/etc/fstab`, `systemd.swap`, depending how it was configured on your system.
 -->
 * 一台兼容的 Linux 主机。Kubernetes 项目为基于 Debian 和 Red Hat 的 Linux
   发行版以及一些不提供包管理器的发行版提供通用的指令。
@@ -50,6 +51,8 @@ see the [Creating a cluster with kubeadm](/docs/setup/production-environment/too
 * 节点之中不可以有重复的主机名、MAC 地址或 product_uuid。请参见[这里](#verify-mac-address)了解更多详细信息。
 * 开启机器上的某些端口。请参见[这里](#check-required-ports)了解更多详细信息。
 * 禁用交换分区。为了保证 kubelet 正常工作，你**必须**禁用交换分区。
+  * 例如，`sudo swapoff -a` 将暂时禁用交换分区。要使此更改在重启后保持不变，请确保在如
+    `/etc/fstab`、`systemd.swap` 等配置文件中禁用交换分区，具体取决于你的系统如何配置。
 
 <!-- steps -->
 

From 6579d24eb1b38bc656ca69bc9dc9f7c4ba701dda Mon Sep 17 00:00:00 2001
From: windsonsea <haifeng.yao@daocloud.io>
Date: Fri, 21 Apr 2023 17:16:59 +0800
Subject: [PATCH 254/272] [zh] sync /workload-resources/job-v1.md

---
 .../workload-resources/job-v1.md              | 135 +++++++++---------
 1 file changed, 68 insertions(+), 67 deletions(-)

diff --git a/content/zh-cn/docs/reference/kubernetes-api/workload-resources/job-v1.md b/content/zh-cn/docs/reference/kubernetes-api/workload-resources/job-v1.md
index 03ba7fc8292..c847b050409 100644
--- a/content/zh-cn/docs/reference/kubernetes-api/workload-resources/job-v1.md
+++ b/content/zh-cn/docs/reference/kubernetes-api/workload-resources/job-v1.md
@@ -8,7 +8,6 @@ description: "Job 表示单个任务的配置。"
 title: "Job"
 weight: 9
 ---
-
 <!--
 api_metadata:
 apiVersion: "batch/v1"
@@ -45,7 +44,8 @@ Job 表示单个任务的配置。
 -->
 - **metadata** (<a href="{{< ref "../common-definitions/object-meta#ObjectMeta" >}}">ObjectMeta</a>)
 
-  标准的对象元数据。更多信息： https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
+  标准的对象元数据。更多信息：
+  https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
 
 <!--
 - **spec** (<a href="{{< ref "../workload-resources/job-v1#JobSpec" >}}">JobSpec</a>)
@@ -54,7 +54,8 @@ Job 表示单个任务的配置。
 -->
 - **spec** (<a href="{{< ref "../workload-resources/job-v1#JobSpec" >}}">JobSpec</a>)
 
-  任务的预期行为的规约。更多信息： https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
+  任务的预期行为的规约。更多信息：
+  https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
 
 <!--
 - **status** (<a href="{{< ref "../workload-resources/job-v1#JobStatus" >}}">JobStatus</a>)
@@ -63,8 +64,8 @@ Job 表示单个任务的配置。
 -->
 - **status** (<a href="{{< ref "../workload-resources/job-v1#JobStatus" >}}">JobStatus</a>)
 
-  任务的当前状态。更多信息： https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
-
+  任务的当前状态。更多信息：
+  https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
 
 ## JobSpec {#JobSpec}
 
@@ -80,7 +81,7 @@ JobSpec 描述了任务执行的情况。
 <!--
 - **template** (<a href="{{< ref "../workload-resources/pod-template-v1#PodTemplateSpec" >}}">PodTemplateSpec</a>), required
 
-  Describes the pod that will be created when executing a job. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
+  Describes the pod that will be created when executing a job. The only allowed template.spec.restartPolicy values are "Never" or "OnFailure". More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
 
 - **parallelism** (int32)
 
@@ -88,38 +89,41 @@ JobSpec 描述了任务执行的情况。
 -->
 - **template** (<a href="{{< ref "../workload-resources/pod-template-v1#PodTemplateSpec" >}}">PodTemplateSpec</a>), 必需
 
-  描述执行任务时将创建的 Pod。更多信息： https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
+  描述执行任务时将创建的 Pod。template.spec.restartPolicy 可以取的值只能是
+  "Never" 或 "OnFailure"。更多信息：
+  https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
 
 - **parallelism** (int32)
 
   指定任务应在任何给定时刻预期运行的 Pod 个数上限。
   当(.spec.completions - .status.successful) \< .spec.parallelism 时，
   即当剩余的工作小于最大并行度时，在稳定状态下运行的 Pod 的实际数量将小于此数量。
-  更多信息： https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
+  更多信息：
+  https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
 
 ### Lifecycle
 
 <!--
 - **completions** (int32)
 
-  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/
+  Specifies the desired number of successfully finished pods the job should be run with.  Setting to null 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/
 -->
 - **completions** (int32)
 
-  指定任务应该运行并预期成功完成的 Pod 个数。设置为 nil 意味着任何 Pod 的成功都标识着所有 Pod 的成功，
+  指定任务应该运行并预期成功完成的 Pod 个数。设置为空意味着任何 Pod 的成功都标识着所有 Pod 的成功，
   并允许 parallelism 设置为任何正值。设置为 1 意味着并行性被限制为 1，并且该 Pod 的成功标志着任务的成功。更多信息：
   https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
 
 <!--
 - **completionMode** (string)
 
-  CompletionMode specifies how Pod completions are tracked. It can be `NonIndexed` (default) or `Indexed`.
-
+  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.
 -->
 - **completionMode** (string)
 
-  completionMode 指定如何跟踪 Pod 完成情况。它可以是 `NonIndexed` （默认） 或者 `Indexed`。
+  completionMode 指定如何跟踪 Pod 完成情况。它可以是 `NonIndexed`（默认）或者 `Indexed`。
 
   `NonIndexed` 表示当有 `.spec.completions` 个成功完成的 Pod 时，认为 Job 完成。每个 Pod 完成都是彼此同源的。
 
@@ -175,7 +179,7 @@ JobSpec 描述了任务执行的情况。
 <!--
 - **suspend** (boolean)
 
-  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.
+  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.
 -->
 - **suspend** (boolean)
 
@@ -205,9 +209,9 @@ JobSpec 描述了任务执行的情况。
   manualSelector 控制 Pod 标签和 Pod 选择器的生成。除非你确定你在做什么，否则不要设置 `manualSelector`。
   当此字段为 false 或未设置时，系统会选择此 Pod 唯一的标签并将这些标签附加到 Pod 模板。
   当此字段为 true 时，用户负责选择唯一标签并指定选择器。
-  未能选择唯一标签可能会导致此任务和其他任务无法正常运行。
-  但是，你可能会在使用旧的 `extensions/v1beta1` API 创建的任务中看到 `manualSelector=true`。
-  更多信息： https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/#specifying-your-own-pod-selector
+  未能选择唯一标签可能会导致此任务和其他任务无法正常运行。但是，你可能会在使用旧的 `extensions/v1beta1` API
+  创建的任务中看到 `manualSelector=true`。更多信息：
+  https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/#specifying-your-own-pod-selector
 
 <!--
 ### Alpha level
@@ -216,7 +220,7 @@ JobSpec 描述了任务执行的情况。
 
   Specifies the policy of handling failed pods. In particular, it allows to specify the set of actions and conditions which need to be satisfied to take the associated action. If empty, the default behaviour applies - the counter of failed pods, represented by the jobs's .status.failed field, is incremented and it is checked against the backoffLimit. This field cannot be used in combination with restartPolicy=OnFailure.
 -->
-### Alpha 级别
+### Alpha 级别   {#alpha-level}
 
 - **podFailurePolicy** (PodFailurePolicy)
 
@@ -254,12 +258,12 @@ JobSpec 描述了任务执行的情况。
 
     <!--
     <a name="PodFailurePolicyRule"></a>
-    *PodFailurePolicyRule describes how a pod failure is handled when the requirements are met. One of OnExitCodes and onPodConditions, but not both, can be used in each rule.*
+    *PodFailurePolicyRule describes how a pod failure is handled when the requirements are met. One of onExitCodes and onPodConditions, but not both, can be used in each rule.*
     -->
 
     <a name="PodFailurePolicyRule"></a>
     **PodFailurePolicyRule 描述当满足要求时如何处理一个 Pod 失效。
-    在每个规则中可以使用 OnExitCodes 和 onPodConditions 之一，但不能同时使用二者。**
+    在每个规则中可以使用 onExitCodes 和 onPodConditions 之一，但不能同时使用二者。**
 
     <!--
     - **podFailurePolicy.rules.action** (string), required
@@ -422,6 +426,7 @@ JobStatus 表示 Job 的当前状态。
   表示任务控制器开始处理任务的时间。在挂起状态下创建 Job 时，直到第一次恢复时才会设置此字段。
   每次从暂停中恢复任务时都会重置此字段。它表示为 RFC3339 格式的 UTC 时间。
 
+  <a name="Time"></a>
   **Time 是 time.Time 的包装器，支持正确编码为 YAML 和 JSON。time 包提供的许多工厂方法都提供了包装器。**
 
 <!--
@@ -437,6 +442,7 @@ JobStatus 表示 Job 的当前状态。
   表示任务完成的时间。不能保证对多个独立操作按发生的先后顺序设置。此字段表示为 RFC3339 格式的 UTC 时间。
   仅当任务成功完成时才设置完成时间。
 
+  <a name="Time"></a>
   **Time 是 time.Time 的包装器，支持正确编码为 YAML 和 JSON。time 包提供的许多工厂方法都提供了包装器。**
 
 <!--
@@ -466,7 +472,7 @@ JobStatus 表示 Job 的当前状态。
 <!--
 - **completedIndexes** (string)
 
-  CompletedIndexes holds the completed indexes when .spec.completionMode = "Indexed" 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 "1,3-5,7".
+  completedIndexes holds the completed indexes when .spec.completionMode = "Indexed" 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 "1,3-5,7".
 -->
 - **completedIndexes** (string)
 
@@ -516,11 +522,11 @@ JobStatus 表示 Job 的当前状态。
 
   - **conditions.status** (string), 必需
 
-    状况的状态，True、False、Unknown 之一。
+    状况的状态：True、False、Unknown 之一。
 
   - **conditions.type** (string), 必需
 
-    任务状况的类型，Completed 或 Failed。
+    任务状况的类型：Completed 或 Failed。
 
   - **conditions.lastProbeTime** (Time)
 
@@ -531,6 +537,7 @@ JobStatus 表示 Job 的当前状态。
     *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.*
     -->
     
+    <a name="Time"></a>
     **Time 是对 time.Time 的封装，支持正确编码为 YAML 和 JSON。我们为 time 包提供的许多工厂方法提供了封装器。**
 
   <!--
@@ -548,6 +555,7 @@ JobStatus 表示 Job 的当前状态。
     *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.*
     -->
 
+    <a name="Time"></a>
     **Time 是 time.Time 的包装器，支持正确编码为 YAML 和 JSON。time 包提供的许多工厂方法都提供了包装器。**
 
   <!--
@@ -571,18 +579,22 @@ JobStatus 表示 Job 的当前状态。
 <!--
 - **uncountedTerminatedPods** (UncountedTerminatedPods)
 
-  UncountedTerminatedPods holds the UIDs of Pods that have terminated but the job controller hasn't yet accounted for in the status counters.
+  uncountedTerminatedPods holds the UIDs of Pods that have terminated but the job controller hasn'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.
+  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.
 -->
-
 - **uncountedTerminatedPods** (UncountedTerminatedPods)
 
   UncountedTerminatedPods 保存已终止但尚未被任务控制器纳入状态计数器中的 Pod 的 UID 的集合。
 
   任务控制器所创建 Pod 带有终结器。当 Pod 终止（成功或失败）时，控制器将执行三个步骤以在任务状态中对其进行说明：
-  （1）将 Pod UID 添加到此字段的列表中。（2）去掉 Pod 中的终结器。（3）从数组中删除 Pod UID，同时为相应的计数器加一。
+
+  1. 将 Pod UID 添加到此字段的列表中。
+  2. 去掉 Pod 中的终结器。
+  3. 从数组中删除 Pod UID，同时为相应的计数器加一。
 
   <!--
   Old jobs might not be tracked using this field, in which case the field remains null.
@@ -599,8 +611,8 @@ JobStatus 表示 Job 的当前状态。
   - **uncountedTerminatedPods.failed** ([]string)
 
     *Set: unique values will be kept during a merge*
-
-    Failed holds UIDs of failed Pods.
+    
+    failed holds UIDs of failed Pods.
   -->
 
   - **uncountedTerminatedPods.failed** ([]string)
@@ -613,8 +625,8 @@ JobStatus 表示 Job 的当前状态。
   - **uncountedTerminatedPods.succeeded** ([]string)
 
     *Set: unique values will be kept during a merge*
-
-    Succeeded holds UIDs of succeeded Pods.
+    
+    succeeded holds UIDs of succeeded Pods.
   -->
 
   - **uncountedTerminatedPods.succeeded** ([]string)
@@ -626,7 +638,7 @@ JobStatus 表示 Job 的当前状态。
 <!--
 ### Beta level
 -->
-### Beta 级别
+### Beta 级别   {#beta-level}
 
 <!--
 - **ready** (int32)
@@ -635,7 +647,6 @@ JobStatus 表示 Job 的当前状态。
 
   This field is beta-level. The job controller populates the field when the feature gate JobReadyPods is enabled (enabled by default).
 -->
-
 - **ready** (int32)
 
   状况为 Ready 的 Pod 数量。
@@ -667,7 +678,8 @@ JobList 是 Job 的集合。
 
 - **metadata** (<a href="{{< ref "../common-definitions/list-meta#ListMeta" >}}">ListMeta</a>)
 
-  标准列表元数据。更多信息： https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
+  标准列表元数据。更多信息：
+  https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
 
 - **items** ([]<a href="{{< ref "../workload-resources/job-v1#Job" >}}">Job</a>), required
 
@@ -676,7 +688,6 @@ JobList 是 Job 的集合。
 <!--
 ## Operations {#Operations}
 -->
-
 ## 操作 {#Operations}
 
 <hr>
@@ -824,7 +835,6 @@ GET /apis/batch/v1/namespaces/{namespace}/jobs
 
   <a href="{{< ref "../common-parameters/common-parameters#continue" >}}">continue</a>
 -->
-
 - **allowWatchBookmarks** (**查询参数**): boolean
 
   <a href="{{< ref "../common-parameters/common-parameters#allowWatchBookmarks" >}}">allowWatchBookmarks</a>
@@ -842,7 +852,6 @@ GET /apis/batch/v1/namespaces/{namespace}/jobs
 
   <a href="{{< ref "../common-parameters/common-parameters#labelSelector" >}}">labelSelector</a>
 -->
-
 - **fieldSelector** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldSelector" >}}">fieldSelector</a>
@@ -860,7 +869,6 @@ GET /apis/batch/v1/namespaces/{namespace}/jobs
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
 -->
-
 - **limit** (**查询参数**): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#limit" >}}">limit</a>
@@ -878,7 +886,6 @@ GET /apis/batch/v1/namespaces/{namespace}/jobs
 
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 -->
-
 - **resourceVersion** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersion" >}}">resourceVersion</a>
@@ -888,6 +895,10 @@ GET /apis/batch/v1/namespaces/{namespace}/jobs
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 <!--
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -896,6 +907,9 @@ GET /apis/batch/v1/namespaces/{namespace}/jobs
 
   <a href="{{< ref "../common-parameters/common-parameters#watch" >}}">watch</a>
 -->
+- **sendInitialEvents** (**查询参数**): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
 
 - **timeoutSeconds** (**查询参数**): integer
 
@@ -943,7 +957,6 @@ GET /apis/batch/v1/jobs
 
   <a href="{{< ref "../common-parameters/common-parameters#continue" >}}">continue</a>
 -->
-
 - **allowWatchBookmarks** (**查询参数**): boolean
 
   <a href="{{< ref "../common-parameters/common-parameters#allowWatchBookmarks" >}}">allowWatchBookmarks</a>
@@ -961,7 +974,6 @@ GET /apis/batch/v1/jobs
 
   <a href="{{< ref "../common-parameters/common-parameters#labelSelector" >}}">labelSelector</a>
 -->
-
 - **fieldSelector** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldSelector" >}}">fieldSelector</a>
@@ -979,7 +991,6 @@ GET /apis/batch/v1/jobs
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
 -->
-
 - **limit** (**查询参数**): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#limit" >}}">limit</a>
@@ -997,7 +1008,6 @@ GET /apis/batch/v1/jobs
 
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 -->
-
 - **resourceVersion** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersion" >}}">resourceVersion</a>
@@ -1007,6 +1017,10 @@ GET /apis/batch/v1/jobs
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 <!--
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
@@ -1015,6 +1029,9 @@ GET /apis/batch/v1/jobs
 
   <a href="{{< ref "../common-parameters/common-parameters#watch" >}}">watch</a>
 -->
+- **sendInitialEvents** (**查询参数**): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
 
 - **timeoutSeconds** (**查询参数**): integer
 
@@ -1074,7 +1091,6 @@ POST /apis/batch/v1/namespaces/{namespace}/jobs
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
 -->
-
 - **dryRun** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
@@ -1092,7 +1108,6 @@ POST /apis/batch/v1/namespaces/{namespace}/jobs
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
 -->
-
 - **fieldValidation** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
@@ -1149,7 +1164,6 @@ PUT /apis/batch/v1/namespaces/{namespace}/jobs/{name}
 
 - **body**: <a href="{{< ref "../workload-resources/job-v1#Job" >}}">Job</a>, required
 -->
-
 - **name** (**路径参数**): string, 必需
 
   Job 的名称。
@@ -1169,7 +1183,6 @@ PUT /apis/batch/v1/namespaces/{namespace}/jobs/{name}
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
 -->
-
 - **dryRun** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
@@ -1187,7 +1200,6 @@ PUT /apis/batch/v1/namespaces/{namespace}/jobs/{name}
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
 -->
-
 - **fieldValidation** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
@@ -1240,7 +1252,6 @@ PUT /apis/batch/v1/namespaces/{namespace}/jobs/{name}/status
 
 - **body**: <a href="{{< ref "../workload-resources/job-v1#Job" >}}">Job</a>, required
 -->
-
 - **name** (**路径参数**): string, 必需
 
   Job 的名称。
@@ -1260,7 +1271,6 @@ PUT /apis/batch/v1/namespaces/{namespace}/jobs/{name}/status
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
 -->
-
 - **dryRun** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
@@ -1278,7 +1288,6 @@ PUT /apis/batch/v1/namespaces/{namespace}/jobs/{name}/status
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
 -->
-
 - **fieldValidation** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
@@ -1350,7 +1359,6 @@ PATCH /apis/batch/v1/namespaces/{namespace}/jobs/{name}
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
 -->
-
 - **dryRun** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
@@ -1368,7 +1376,6 @@ PATCH /apis/batch/v1/namespaces/{namespace}/jobs/{name}
 
   <a href="{{< ref "../common-parameters/common-parameters#force" >}}">force</a>
 -->
-
 - **fieldValidation** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
@@ -1382,7 +1389,6 @@ PATCH /apis/batch/v1/namespaces/{namespace}/jobs/{name}
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
 -->
-
 - **pretty** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
@@ -1431,7 +1437,6 @@ PATCH /apis/batch/v1/namespaces/{namespace}/jobs/{name}/status
 
 - **body**: <a href="{{< ref "../common-definitions/patch#Patch" >}}">Patch</a>, required
 -->
-
 - **name** (**路径参数**): string, 必需
 
   Job 的名称。
@@ -1451,7 +1456,6 @@ PATCH /apis/batch/v1/namespaces/{namespace}/jobs/{name}/status
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldManager" >}}">fieldManager</a>
 -->
-
 - **dryRun** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
@@ -1469,7 +1473,6 @@ PATCH /apis/batch/v1/namespaces/{namespace}/jobs/{name}/status
 
   <a href="{{< ref "../common-parameters/common-parameters#force" >}}">force</a>
 -->
-
 - **fieldValidation** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldValidation" >}}">fieldValidation</a>
@@ -1483,7 +1486,6 @@ PATCH /apis/batch/v1/namespaces/{namespace}/jobs/{name}/status
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
 -->
-
 - **pretty** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
@@ -1546,7 +1548,6 @@ DELETE /apis/batch/v1/namespaces/{namespace}/jobs/{name}
 
   <a href="{{< ref "../common-parameters/common-parameters#gracePeriodSeconds" >}}">gracePeriodSeconds</a>
 -->
-
 - **dryRun** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
@@ -1564,7 +1565,6 @@ DELETE /apis/batch/v1/namespaces/{namespace}/jobs/{name}
 
   <a href="{{< ref "../common-parameters/common-parameters#propagationPolicy" >}}">propagationPolicy</a>
 -->
-
 - **pretty** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
@@ -1623,7 +1623,6 @@ DELETE /apis/batch/v1/namespaces/{namespace}/jobs
 
   <a href="{{< ref "../common-parameters/common-parameters#dryRun" >}}">dryRun</a>
 -->
-
 - **continue** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#continue" >}}">continue</a>
@@ -1641,7 +1640,6 @@ DELETE /apis/batch/v1/namespaces/{namespace}/jobs
 
   <a href="{{< ref "../common-parameters/common-parameters#gracePeriodSeconds" >}}">gracePeriodSeconds</a>
 -->
-
 - **fieldSelector** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#fieldSelector" >}}">fieldSelector</a>
@@ -1659,7 +1657,6 @@ DELETE /apis/batch/v1/namespaces/{namespace}/jobs
 
   <a href="{{< ref "../common-parameters/common-parameters#limit" >}}">limit</a>
 -->
-
 - **labelSelector** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#labelSelector" >}}">labelSelector</a>
@@ -1677,7 +1674,6 @@ DELETE /apis/batch/v1/namespaces/{namespace}/jobs
 
   <a href="{{< ref "../common-parameters/common-parameters#propagationPolicy" >}}">propagationPolicy</a>
 -->
-
 - **pretty** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#pretty" >}}">pretty</a>
@@ -1695,7 +1691,6 @@ DELETE /apis/batch/v1/namespaces/{namespace}/jobs
 
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 -->
-
 - **resourceVersion** (**查询参数**): string
 
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersion" >}}">resourceVersion</a>
@@ -1705,10 +1700,17 @@ DELETE /apis/batch/v1/namespaces/{namespace}/jobs
   <a href="{{< ref "../common-parameters/common-parameters#resourceVersionMatch" >}}">resourceVersionMatch</a>
 
 <!--
+- **sendInitialEvents** (*in query*): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
+
 - **timeoutSeconds** (*in query*): integer
 
   <a href="{{< ref "../common-parameters/common-parameters#timeoutSeconds" >}}">timeoutSeconds</a>
 -->
+- **sendInitialEvents** (**查询参数**): boolean
+
+  <a href="{{< ref "../common-parameters/common-parameters#sendInitialEvents" >}}">sendInitialEvents</a>
 
 - **timeoutSeconds** (**查询参数**): integer
 
@@ -1726,4 +1728,3 @@ DELETE /apis/batch/v1/namespaces/{namespace}/jobs
 200 (<a href="{{< ref "../common-definitions/status#Status" >}}">Status</a>): OK
 
 401: Unauthorized
-

From 64a06fd595f33442cab9969e1fcb191369812358 Mon Sep 17 00:00:00 2001
From: windsonsea <haifeng.yao@daocloud.io>
Date: Sun, 23 Apr 2023 11:01:45 +0800
Subject: [PATCH 255/272] tweak line wrappings in declarative-config.md

---
 .../declarative-config.md                     | 119 +++++++++++-------
 1 file changed, 74 insertions(+), 45 deletions(-)

diff --git a/content/en/docs/tasks/manage-kubernetes-objects/declarative-config.md b/content/en/docs/tasks/manage-kubernetes-objects/declarative-config.md
index ef51d18fc6d..cc06edbede9 100644
--- a/content/en/docs/tasks/manage-kubernetes-objects/declarative-config.md
+++ b/content/en/docs/tasks/manage-kubernetes-objects/declarative-config.md
@@ -12,16 +12,12 @@ retains writes made to live objects without merging the changes
 back into the object configuration files. `kubectl diff` also gives you a
 preview of what changes `apply` will make.
 
-
 ## {{% heading "prerequisites" %}}
 
-
 Install [`kubectl`](/docs/tasks/tools/).
 
 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
 
-
-
 <!-- steps -->
 
 ## Trade-offs
@@ -52,7 +48,7 @@ Following are definitions for terms used in this document:
 - *live object configuration / live configuration*: The live configuration
   values of an object, as observed by the Kubernetes cluster. These are kept in the Kubernetes
   cluster storage, typically etcd.
-- *declarative configuration writer /  declarative writer*: A person or software component
+- *declarative configuration writer / declarative writer*: A person or software component
   that makes updates to a live object. The live writers referred to in this topic make changes
   to object configuration files and run `kubectl apply` to write the changes.
 
@@ -62,7 +58,7 @@ Use `kubectl apply` to create all objects, except those that already exist,
 defined by configuration files in a specified directory:
 
 ```shell
-kubectl apply -f <directory>/
+kubectl apply -f <directory>
 ```
 
 This sets the `kubectl.kubernetes.io/last-applied-configuration: '{...}'`
@@ -157,8 +153,8 @@ if those objects already exist. This approach accomplishes the following:
 2. Clears fields removed from the configuration file in the live configuration.
 
 ```shell
-kubectl diff -f <directory>/
-kubectl apply -f <directory>/
+kubectl diff -f <directory>
+kubectl apply -f <directory>
 ```
 
 {{< note >}}
@@ -371,14 +367,19 @@ to result in the user deleting something unintentionally:
 kubectl delete -f <filename>
 ```
 
-### Alternative: `kubectl apply -f <directory/> --prune`
+### Alternative: `kubectl apply -f <directory> --prune`
 
 As an alternative to `kubectl delete`, you can use `kubectl apply` to identify objects to be deleted after
 their manifests have been removed from a directory in the local filesystem.
 
 In Kubernetes {{< skew currentVersion >}}, there are two pruning modes available in kubectl apply:
-- Allowlist-based pruning: This mode has existed since kubectl v1.5 but is still in alpha due to usability, correctness and performance issues with its design. The ApplySet-based mode is designed to replace it.
-- ApplySet-based pruning: An _apply set_ is a server-side object (by default, a Secret) that kubectl can use to accurately and efficiently track set membership across **apply** operations. This mode was introduced in alpha in kubectl v1.27 as a replacement for allowlist-based pruning.
+
+- Allowlist-based pruning: This mode has existed since kubectl v1.5 but is still
+  in alpha due to usability, correctness and performance issues with its design.
+  The ApplySet-based mode is designed to replace it.
+- ApplySet-based pruning: An _apply set_ is a server-side object (by default, a Secret)
+  that kubectl can use to accurately and efficiently track set membership across **apply**
+  operations. This mode was introduced in alpha in kubectl v1.27 as a replacement for allowlist-based pruning.
 
 {{< tabs name="kubectl_apply_prune" >}}
 {{% tab name="Allow list" %}}
@@ -386,23 +387,31 @@ In Kubernetes {{< skew currentVersion >}}, there are two pruning modes available
 {{< feature-state for_k8s_version="v1.5" state="alpha" >}}
 
 {{< warning >}}
-Take care when using `--prune` with `kubectl apply` in allow list mode. Which objects are pruned depends on the values of the `--prune-allowlist`, `--selector` and `--namespace` flags, and relies on dynamic discovery of the objects in scope. Especially if flag values are changed between invocations, this can lead to objects being unexpectedly deleted or retained.
+Take care when using `--prune` with `kubectl apply` in allow list mode. Which
+objects are pruned depends on the values of the `--prune-allowlist`, `--selector`
+and `--namespace` flags, and relies on dynamic discovery of the objects in scope.
+Especially if flag values are changed between invocations, this can lead to objects
+being unexpectedly deleted or retained.
 {{< /warning >}}
 
 To use allowlist-based pruning, add the following flags to your `kubectl apply` invocation:
+
 - `--prune`: Delete previously applied objects that are not in the set passed to the current invocation.
-- `--prune-allowlist`: A list of group-version-kinds (GVKs) to consider for pruning. This flag is optional but strongly encouraged, as its default value is a partial list of both namespaced and cluster-scoped types, which can lead to surprising results.
-- `--selector/-l`: Use a label selector to constrain the set of objects selected for pruning. This flag is optional but strongly encouraged.
-- `--all`: use instead of `--selector/-l` to explicitly select all previously applied objects of the allowlisted types.
+- `--prune-allowlist`: A list of group-version-kinds (GVKs) to consider for pruning.
+  This flag is optional but strongly encouraged, as its default value is a partial
+  list of both namespaced and cluster-scoped types, which can lead to surprising results.
+- `--selector/-l`: Use a label selector to constrain the set of objects selected
+  for pruning. This flag is optional but strongly encouraged.
+- `--all`: use instead of `--selector/-l` to explicitly select all previously
+  applied objects of the allowlisted types.
 
 Allowlist-based pruning queries the API server for all objects of the allowlisted GVKs that match the given labels (if any), and attempts to match the returned live object configurations against the object
 manifest files. If an object matches the query, and it does not have a
 manifest in the directory, and it has a `kubectl.kubernetes.io/last-applied-configuration` annotation,
 it is deleted.
 
-
 ```shell
-kubectl apply -f <directory/> --prune -l <labels> --prune-allowlist=<gvk-list>
+kubectl apply -f <directory> --prune -l <labels> --prune-allowlist=<gvk-list>
 ```
 
 {{< warning >}}
@@ -423,30 +432,49 @@ have the labels given (if any), and do not appear in the subdirectory.
 changes might be introduced in subsequent releases.
 {{< /caution >}}
 
-To use ApplySet-based pruning, set the `KUBECTL_APPLYSET=true` environment variable, and add the following flags to your `kubectl apply` invocation:
-- `--prune`: Delete previously applied objects that are not in the set passed to the current invocation.
-- `--applyset`: The name of an object that kubectl can use to accurately and efficiently track set membership across `apply` operations.
+To use ApplySet-based pruning, set the `KUBECTL_APPLYSET=true` environment variable,
+and add the following flags to your `kubectl apply` invocation:
+- `--prune`: Delete previously applied objects that are not in the set passed
+  to the current invocation.
+- `--applyset`: The name of an object that kubectl can use to accurately and
+  efficiently track set membership across `apply` operations.
 
 ```shell
-KUBECTL_APPLYSET=true kubectl apply -f <directory/> --prune --applyset=<name>
+KUBECTL_APPLYSET=true kubectl apply -f <directory> --prune --applyset=<name>
 ```
 
-By default, the type of the ApplySet parent object used is a Secret. However, ConfigMaps can also be used in the format: `--applyset=configmaps/<name>`. When using a Secret or ConfigMap, kubectl will create the object if it does not already exist.
+By default, the type of the ApplySet parent object used is a Secret. However,
+ConfigMaps can also be used in the format: `--applyset=configmaps/<name>`.
+When using a Secret or ConfigMap, kubectl will create the object if it does not already exist.
 
-It is also possible to use custom resources as ApplySet parent objects. To enable this, label the Custom Resource Definition (CRD) that defines the resource you want to use with the following: `applyset.kubernetes.io/is-parent-type: true`. Then, create the object you want to use as an ApplySet parent (kubectl does not do this automatically for custom resources). Finally, refer to that object in the applyset flag as follows: `--applyset=<resource>.<group>/<name>` (for example, `widgets.custom.example.com/widget-name`).
+It is also possible to use custom resources as ApplySet parent objects. To enable
+this, label the Custom Resource Definition (CRD) that defines the resource you want
+to use with the following: `applyset.kubernetes.io/is-parent-type: true`. Then, create
+the object you want to use as an ApplySet parent (kubectl does not do this automatically
+for custom resources). Finally, refer to that object in the applyset flag as follows:
+`--applyset=<resource>.<group>/<name>` (for example, `widgets.custom.example.com/widget-name`).
 
-With ApplySet-based pruning, kubectl adds the `applyset.kubernetes.io/part-of=<parentID>` label to each object in the set before they are sent to the server. For performance reasons, it also collects the list of resource types and namespaces that the set contains and adds these in annotations on the live parent object. Finally, at the end of the apply operation, it queries the API server for objects of those types in those namespaces (or in the cluster scope, as applicable) that belong to the set, as defined by the `applyset.kubernetes.io/part-of=<parentID>` label.
+With ApplySet-based pruning, kubectl adds the `applyset.kubernetes.io/part-of=<parentID>`
+label to each object in the set before they are sent to the server. For performance reasons,
+it also collects the list of resource types and namespaces that the set contains and adds
+these in annotations on the live parent object. Finally, at the end of the apply operation,
+it queries the API server for objects of those types in those namespaces
+(or in the cluster scope, as applicable) that belong to the set, as defined by the
+`applyset.kubernetes.io/part-of=<parentID>` label.
 
 Caveats and restrictions:
+
 - Each object may be a member of at most one set.
-- The `--namespace` flag is required when using any namespaced parent, including the default Secret.  This means that ApplySets spanning multiple namespaces must use a cluster-scoped custom resource as the parent object.
-- To safely use ApplySet-based pruning with multiple directories, use a unique ApplySet name for each.
+- The `--namespace` flag is required when using any namespaced parent, including
+  the default Secret.  This means that ApplySets spanning multiple namespaces must
+  use a cluster-scoped custom resource as the parent object.
+- To safely use ApplySet-based pruning with multiple directories,
+  use a unique ApplySet name for each.
 
 {{% /tab %}}
 
 {{< /tabs >}}
 
-
 ## How to view an object
 
 You can use `kubectl get` with `-o yaml` to view the configuration of a live object:
@@ -478,8 +506,10 @@ is used to identify fields that have been removed from the configuration
 file and need to be cleared from the live configuration. Here are the steps used
 to calculate which fields should be deleted or set:
 
-1. Calculate the fields to delete. These are the fields present in `last-applied-configuration` and missing from the configuration file.
-2. Calculate the fields to add or set. These are the fields present in the configuration file whose values don't match the live configuration.
+1. Calculate the fields to delete. These are the fields present in
+   `last-applied-configuration` and missing from the configuration file.
+2. Calculate the fields to add or set. These are the fields present in
+   the configuration file whose values don't match the live configuration.
 
 Here's an example. Suppose this is the configuration file for a Deployment object:
 
@@ -534,11 +564,11 @@ Here are the merge calculations that would be performed by `kubectl apply`:
    regardless of whether they appear in the `last-applied-configuration`.
    In this example, `minReadySeconds` appears in the
    `last-applied-configuration` annotation, but does not appear in the configuration file.
-    **Action:** Clear `minReadySeconds` from the live configuration.
+   **Action:** Clear `minReadySeconds` from the live configuration.
 2. Calculate the fields to set by reading values from the configuration
    file and comparing them to values in the live configuration. In this example,
    the value of `image` in the configuration file does not match
-    the value in the live configuration. **Action:** Set the value of `image` in the live configuration.
+   the value in the live configuration. **Action:** Set the value of `image` in the live configuration.
 3. Set the `last-applied-configuration` annotation to match the value
    of the configuration file.
 4. Merge the results from 1, 2, 3 into a single patch request to the API server.
@@ -984,22 +1014,22 @@ configuration involves several manual steps:
 
 1. Export the live object to a local configuration file:
 
-     ```shell
-     kubectl get <kind>/<name> -o yaml > <kind>_<name>.yaml
-     ```
+   ```shell
+   kubectl get <kind>/<name> -o yaml > <kind>_<name>.yaml
+   ```
 
 1. Manually remove the `status` field from the configuration file.
 
-    {{< note >}}
-    This step is optional, as `kubectl apply` does not update the status field
-    even if it is present in the configuration file.
-    {{< /note >}}
+   {{< note >}}
+   This step is optional, as `kubectl apply` does not update the status field
+   even if it is present in the configuration file.
+   {{< /note >}}
 
 1. Set the `kubectl.kubernetes.io/last-applied-configuration` annotation on the object:
 
-    ```shell
-    kubectl replace --save-config -f <kind>_<name>.yaml
-    ```
+   ```shell
+   kubectl replace --save-config -f <kind>_<name>.yaml
+   ```
 
 1. Change processes to use `kubectl apply` for managing the object exclusively.
 
@@ -1011,9 +1041,9 @@ TODO(pwittrock): Why doesn't export remove the status field?  Seems like it shou
 
 1. Set the `kubectl.kubernetes.io/last-applied-configuration` annotation on the object:
 
-    ```shell
-    kubectl replace --save-config -f <kind>_<name>.yaml
-    ```
+   ```shell
+   kubectl replace --save-config -f <kind>_<name>.yaml
+   ```
 
 1. Change processes to use `kubectl apply` for managing the object exclusively.
 
@@ -1040,7 +1070,6 @@ template:
 
 ## {{% heading "whatsnext" %}}
 
-
 * [Managing Kubernetes Objects Using Imperative Commands](/docs/tasks/manage-kubernetes-objects/imperative-command/)
 * [Imperative Management of Kubernetes Objects Using Configuration Files](/docs/tasks/manage-kubernetes-objects/imperative-config/)
 * [Kubectl Command Reference](/docs/reference/generated/kubectl/kubectl-commands/)

From 2259666d4848a5dfd10c9d985c77588fc472a8e3 Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Sun, 23 Apr 2023 11:16:05 +0800
Subject: [PATCH 256/272] sync etcd.md

sync etcd.md
---
 content/zh-cn/docs/reference/glossary/etcd.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/zh-cn/docs/reference/glossary/etcd.md b/content/zh-cn/docs/reference/glossary/etcd.md
index 24498005e8a..34e410bfebd 100644
--- a/content/zh-cn/docs/reference/glossary/etcd.md
+++ b/content/zh-cn/docs/reference/glossary/etcd.md
@@ -35,7 +35,7 @@ tags:
 <!--
 If your Kubernetes cluster uses etcd as its backing store, make sure you have a
 [back up](/docs/tasks/administer-cluster/configure-upgrade-etcd/#backing-up-an-etcd-cluster) plan
-for those data.
+for the data.
 -->	
 如果你的 Kubernetes 集群使用 etcd 作为其后台数据库，
 请确保你针对这些数据有一份

From ffc1c917a9dfcc00ef292edc95213b52fe69c2f8 Mon Sep 17 00:00:00 2001
From: Zhuzhenghao <zhenghao.zhu@daocloud.io>
Date: Thu, 13 Apr 2023 17:39:14 +0800
Subject: [PATCH 257/272] [zh] sync 1.27 custom-resource-definitions

---
 .../custom-resource-definitions.md            | 123 ++++++++++++++----
 1 file changed, 96 insertions(+), 27 deletions(-)

diff --git a/content/zh-cn/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md b/content/zh-cn/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md
index 3418cde1cf4..62041dac59a 100644
--- a/content/zh-cn/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md
+++ b/content/zh-cn/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md
@@ -505,7 +505,8 @@ anyOf:
 ```
 
 <!--
-Violations of the structural schema rules are reported in the `NonStructural` condition in the CustomResourceDefinition.
+Violations of the structural schema rules are reported in the `NonStructural` condition in the
+CustomResourceDefinition.
 -->
 如果违反了结构化模式规则，CustomResourceDefinition 的 `NonStructural`
 状况中会包含报告信息。
@@ -1195,7 +1196,7 @@ For example:
         required:
           - minReplicas
           - replicas
-          - maxReplicas 
+          - maxReplicas
 ```
 
 <!--
@@ -1225,7 +1226,7 @@ The CronTab "my-new-cron-object" is invalid:
 ```
 
 <!--
-`x-kubernetes-validations` could have multiple rules. 
+`x-kubernetes-validations` could have multiple rules.
 
 The `rule` under `x-kubernetes-validations` represents the expression which will be evaluated by CEL.
 
@@ -1244,8 +1245,8 @@ The CronTab "my-new-cron-object" is invalid:
 ```
 
 <!--
-Validation rules are compiled when CRDs are created/updated. 
-The request of CRDs create/update will fail if compilation of validation rules fail. 
+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.
 -->
 当 CRD 被创建/更新时，验证规则被编译。
@@ -1256,7 +1257,7 @@ Compilation process includes type checking as well.
 The compilation failure:
 
 - `no_matching_overload`: this function has no overload for the types of the arguments.
- 
+
   For example, a rule like `self == true` against a field of integer type will get error:
 -->
 编译失败：
@@ -1269,9 +1270,9 @@ The compilation failure:
   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.
-  
+
   For example, a rule like `self.nonExistingField > 0` against a non-existing field will return
   the following error:
 -->
@@ -1285,7 +1286,7 @@ The compilation failure:
 
 <!--
 - `invalid argument`: invalid argument to macros.
- 
+
   For example, a rule like `has(self)` will return error:
 -->
 - `invalid argument`：对宏的无效参数。
@@ -1633,6 +1634,64 @@ xref: [CEL types](https://github.com/google/cel-spec/blob/v0.6.0/doc/langdef.md#
 [OpenAPI 类型](https://swagger.io/specification/#data-types)、
 [Kubernetes 结构化模式](/zh-cn/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#specifying-a-structural-schema)。
 
+<!--
+#### The messageExpression field
+-->
+#### `messageExpression` 字段  {#the-messageExpression-field}
+
+<!--
+Similar to the `message` field, which defines the string reported for a validation rule failure,
+`messageExpression` allows you to use a CEL expression to construct the message string.
+This allows you to insert more descriptive information into the validation failure message.
+`messageExpression` must evaluate a string and may use the same variables that are available to the `rule`
+field. For example:
+-->
+`message` 字段定义因验证规则失败时提示的字符串，与它类似，
+`messageExpression` 允许你使用 CEL 表达式构造消息字符串。
+这使你可以在验证失败消息中插入更详细的信息。`messageExpression`
+必须计算为字符串，并且可以使用在 `rule` 字段中可用的变量。
+例如：
+
+```yaml
+x-kubernetes-validations:
+- rule: "self.x <= self.maxLimit"
+  messageExpression: '"x exceeded max limit of " + string(self.maxLimit)'
+```
+
+<!--
+Keep in mind that CEL string concatenation (`+` operator) does not auto-cast to string. If
+you have a non-string scalar, use the `string(<value>)` function to cast the scalar to a string
+like shown in the above example.
+-->
+请记住，CEL 字符串连接（`+` 运算符）不会自动转换为字符串。
+如果你有一个非字符串标量，请使用 `string(<value>)` 函数将标量转换为字符串，如上例所示。
+
+<!--
+`messageExpression` must evaluate to a string, and this is checked while the CRD is being written. Note that it is possible
+to set `message` and `messageExpression` on the same rule, and if both are present, `messageExpression`
+will be used. However, if `messageExpression` evaluates to an error, the string defined in `message`
+will be used instead, and the `messageExpression` error will be logged. This fallback will also occur if
+the CEL expression defined in `messageExpression` generates an empty string, or a string containing line
+breaks.
+-->
+`messageExpression` 必须计算为一个字符串，并且在编写 CRD 时进行检查。
+请注意，可以在同一个规则上设置 `message` 和 `messageExpression`，如果两者都存在，则将使用 `messageExpression`。
+但是，如果 `messageExpression` 计算出错，则将使用 `message` 中定义的字符串，而 `messageExpression` 的错误将被打印到日志。
+如果在 `messageExpression` 中定义的 CEL 表达式产生一个空字符串或包含换行符的字符串，也会发生这种回退。
+
+<!--
+If one of the above conditions are met and no `message` has been set, then the default validation failure
+message will be used instead.
+-->
+如果满足上述条件之一且未设置 `message` 字段，则将使用默认的检查失败消息。
+
+<!--
+`messageExpression` is a CEL expression, so the restrictions listed in [Resource use by validation functions](#resource-use-by-validation-functions) apply. If evaluation halts due to resource constraints
+during `messageExpression` execution, then no further validation rules will be executed.
+-->
+`messageExpression` 是一个 CEL 表达式，因此[验证函数的资源使用](#resource-use-by-validation-functions)中列出的限制也适用于它。
+如果在 `messageExpression` 执行期间由于资源限制而导致计算停止，则不会执行进一步的检查规则。
+
 <!--
 #### Validation functions {#available-validation-functions}
 -->
@@ -1749,7 +1808,7 @@ Here are some examples for transition rules:
 <!--
 #### Resource use by validation functions
 -->
-#### 验证函数的资源使用
+#### 验证函数的资源使用  {#resource-use-by-validation-functions}
 
 <!--
 When you create or update a CustomResourceDefinition that uses validation rules,
@@ -1766,8 +1825,8 @@ too many instructions, execution of the rule will be halted, and an error will r
 -->
 运行时也使用类似的系统来观察解释器的行动。如果解释器执行了太多的指令，规则的执行将被停止，并且会产生一个错误。
 <!--
-Each CustomResourceDefinition is also allowed a certain amount of resources to finish executing all of 
-its validation rules. If the sum total of its rules are estimated at creation time to go over that limit, 
+Each CustomResourceDefinition is also allowed a certain amount of resources to finish executing all of
+its validation rules. If the sum total of its rules are estimated at creation time to go over that limit,
 then a validation error will also occur.
 -->
 每个 CustomResourceDefinition 也被允许有一定数量的资源来完成其所有验证规则的执行。
@@ -1798,7 +1857,7 @@ given, and this will happen for anything that can be iterated over (lists, maps,
 如果没有给出 `foo` 的长度限制，成本系统总是假设最坏的情况，这将发生在任何可以被迭代的事物上（list、map 等）。
 
 <!--
-Because of this, it is considered best practice to put a limit via `maxItems`, `maxProperties`, and 
+Because of this, it is considered best practice to put a limit via `maxItems`, `maxProperties`, and
 `maxLength` for anything that will be processed in a validation rule in order to prevent validation
 errors during cost estimation. For example, given this schema with one rule:
 -->
@@ -1823,8 +1882,8 @@ then the API server rejects this rule on validation budget grounds with error:
 API 服务器以验证预算为由拒绝该规则，并显示错误：
 
 ```
-spec.validation.openAPIV3Schema.properties[spec].properties[foo].x-kubernetes-validations[0].rule: Forbidden: 
-CEL rule exceeded budget by more than 100x (try simplifying the rule, or adding maxItems, maxProperties, and 
+spec.validation.openAPIV3Schema.properties[spec].properties[foo].x-kubernetes-validations[0].rule: Forbidden:
+CEL rule exceeded budget by more than 100x (try simplifying the rule, or adding maxItems, maxProperties, and
 maxLength where arrays, maps, and strings are used)
 ```
 
@@ -1880,7 +1939,7 @@ openAPIV3Schema:
 ```
 
 <!--
-If a list inside of a list has a validation rule that uses `self.all`, that is significantly more expensive 
+If a list inside of a list has a validation rule that uses `self.all`, that is significantly more expensive
 than a non-nested list with the same rule. A rule that would have been allowed on a non-nested list might need
 lower limits set on both nested lists in order to be allowed. For example, even without having limits set,
 the following rule is allowed:
@@ -2114,31 +2173,38 @@ default.
 `baz` 字段则被完全剪裁掉，因为该字段是不可为空的，并且没有默认值设置。
 
 <!--
-### Publish Validation Schema in OpenAPI v2
+### Publish Validation Schema in OpenAPI
 
 CustomResourceDefinition [OpenAPI v3 validation schemas](#validation) which are
 [structural](#specifying-a-structural-schema) and [enable pruning](#field-pruning) are published
-as part of the [OpenAPI v2 spec](/docs/concepts/overview/kubernetes-api/#openapi-and-swagger-definitions)
-from Kubernetes API server.
+as [OpenAPI v3](/docs/concepts/overview/kubernetes-api/#openapi-and-swagger-definitions) and
+OpenAPI v2 from Kubernetes API server. It is recommended to use the OpenAPI v3 document
+as it is a lossless representation of the CustomResourceDefinition OpenAPI v3 validation schema
+while OpenAPI v2 represents a lossy conversion.
 
 The [kubectl](/docs/reference/kubectl/) command-line tool consumes the published schema to perform
 client-side validation (`kubectl create` and `kubectl apply`), schema explanation (`kubectl explain`)
 on custom resources. The published schema can be consumed for other purposes as well, like client generation or documentation.
 -->
-### 以 OpenAPI v2 形式发布合法性检查模式      {#publish-validation-schema-in-openapi-v2}
+### 以 OpenAPI 形式发布合法性检查模式  {#publish-validation-schema-in-openapi}
 
 CustomResourceDefinition 的[结构化的](#specifying-a-structural-schema)、
 [启用了剪裁的](#field-pruning) [OpenAPI v3 合法性检查模式](#validation)会在
 Kubernetes API 服务器上作为
-[OpenAPI v2 规约](/zh-cn/docs/concepts/overview/kubernetes-api/#openapi-and-swagger-definitions)的一部分发布出来。
+[OpenAPI 3](/zh-cn/docs/concepts/overview/kubernetes-api/#openapi-and-swagger-definitions)
+和 OpenAPI v2 发布出来。建议使用 OpenAPI v3 文档，因为它是 CustomResourceDefinition OpenAPI v3
+验证模式的无损表示，而 OpenAPI v2 表示有损转换。
 
 [kubectl](/zh-cn/docs/reference/kubectl/) 命令行工具会基于所发布的模式定义来执行客户端的合法性检查
 （`kubectl create` 和 `kubectl apply`），为定制资源的模式定义提供解释（`kubectl explain`）。
 所发布的模式还可被用于其他目的，例如生成客户端或者生成文档。
 
 <!--
-The OpenAPI v3 validation schema is converted to OpenAPI v2 schema, and
-show up in `definitions` and `paths` fields in the
+
+#### Compatibility with OpenAPI V2
+
+For compatibility with OpenAPI V2, the OpenAPI v3 validation schema performs a lossy conversion
+to the OpenAPI v2 schema. The schema show up in `definitions` and `paths` fields in the
 [OpenAPI v2 spec](/docs/concepts/overview/kubernetes-api/#openapi-and-swagger-definitions).
 
 The following modifications are applied during the conversion to keep backwards compatibility with
@@ -2146,6 +2212,11 @@ kubectl in previous 1.13 version. These modifications prevent kubectl from being
 valid OpenAPI schemas that it doesn't understand. The conversion won't modify the validation schema defined in CRD,
 and therefore won't affect [validation](#validation) in the API server.
 -->
+#### Compatibility with OpenAPI V2
+
+为了与 OpenAPI V2 兼容，OpenAPI v3 验证模式会对 OpenAPI v2 模式进行有损转换。
+该模式显示在 [OpenAPI v2 规范](/zh-cn/docs/concepts/overview/kubernetes-api/#openapi-and-swagger-definitions)中的
+`definitions` 和` paths` 字段中。
 OpenAPI v3 合法性检查模式定义会被转换为 OpenAPI v2 模式定义，并出现在
 [OpenAPI v2 规范](/zh-cn/docs/concepts/overview/kubernetes-api/#openapi-and-swagger-definitions)的
 `definitions` 和 `paths` 字段中。
@@ -2156,16 +2227,14 @@ OpenAPI v3 合法性检查模式定义会被转换为 OpenAPI v2 模式定义，
 API 服务器中的[合法性检查](#validation)。
 
 <!--
-1. The following fields are removed as they aren't supported by OpenAPI v2
-   (in future versions OpenAPI v3 will be used without these restrictions)
+1. The following fields are removed as they aren't supported by OpenAPI v2.
 
    - The fields `allOf`, `anyOf`, `oneOf` and `not` are removed
 
 2. If `nullable: true` is set, we drop `type`, `nullable`, `items` and `properties` because OpenAPI v2 is
    not able to express nullable. To avoid kubectl to reject good objects, this is necessary.
 -->
-1. 以下字段会被移除，因为它们在 OpenAPI v2 中不支持（在将来版本中将使用 OpenAPI v3，
-   因而不会有这些限制）
+1. 以下字段会被移除，因为它们在 OpenAPI v2 中不支持。
 
    - 字段 `allOf`、`anyOf`、`oneOf` 和 `not` 会被删除
 

From 3ba3ac3927729560bb80043d66bb825c1fec4fe4 Mon Sep 17 00:00:00 2001
From: Zhuzhenghao <zhenghao.zhu@daocloud.io>
Date: Thu, 13 Apr 2023 16:36:43 +0800
Subject: [PATCH 258/272] [zh] sync 1.27 extensible-admission-controllers

---
 .../extensible-admission-controllers.md       | 145 ++++++++++++++++++
 1 file changed, 145 insertions(+)

diff --git a/content/zh-cn/docs/reference/access-authn-authz/extensible-admission-controllers.md b/content/zh-cn/docs/reference/access-authn-authz/extensible-admission-controllers.md
index af84e467523..7b29c76a347 100644
--- a/content/zh-cn/docs/reference/access-authn-authz/extensible-admission-controllers.md
+++ b/content/zh-cn/docs/reference/access-authn-authz/extensible-admission-controllers.md
@@ -1059,6 +1059,151 @@ The `matchPolicy` for an admission webhooks defaults to `Equivalent`.
 -->
 准入 Webhook 所用的 `matchPolicy` 默认为 `Equivalent`。
 
+<!--
+### Matching requests: `matchConditions`
+-->
+### 匹配请求：`matchConditions`  {#matching-requests-matchConditions}
+
+{{< feature-state state="alpha" for_k8s_version="v1.27" >}}
+
+{{< note >}}
+<!--
+Use of `matchConditions` requires the [featuregate](/docs/reference/command-line-tools-reference/feature-gates/)
+`AdmissionWebhookMatchConditions` to be explicitly enabled on the kube-apiserver before this feature can be used.
+-->
+使用 `matchConditions` 需要先在 kube-apiserver
+上明确启用[功能门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)
+`AdmissionWebhookMatchConditions`，然后才能使用此功能。
+{{< /note >}}
+
+<!--
+You can define _match conditions_for webhooks if you need fine-grained request filtering. These
+conditions are useful if you find that match rules, `objectSelectors` and `namespaceSelectors` still
+doesn't provide the filtering you want over when to call out over HTTP. Match conditions are
+[CEL expressions](/docs/reference/using-api/cel/). All match conditions must evaluate to true for the
+webhook to be called.
+-->
+如果你需要细粒度地过滤请求，你可以为 Webhook 定义**匹配条件**。
+如果你发现匹配规则、`objectSelectors` 和 `namespaceSelectors` 仍然不能提供你想要的何时进行 HTTP
+调用的过滤条件，那么添加这些条件会很有用。
+匹配条件是 [CEL 表达式](/docs/reference/using-api/cel/)。
+所有匹配条件都必须为 true 才能调用 Webhook。
+
+<!--
+Here is an example illustrating a few different uses for match conditions:
+-->
+以下是一个例子，说明了匹配条件的几种不同用法：
+
+```yaml
+apiVersion: admissionregistration.k8s.io/v1
+kind: ValidatingWebhookConfiguration
+webhooks:
+  - name: my-webhook.example.com
+    matchPolicy: Equivalent
+    rules:
+      - operations: ['CREATE','UPDATE']
+        apiGroups: ['*']
+        apiVersions: ['*']
+        resources: ['*']
+    failurePolicy: 'Ignore' # 失败时继续处理请求但跳过 Webhook (可选值)
+    sideEffects: None
+    clientConfig:
+      service:
+        namespace: my-namespace
+        name: my-webhook
+      caBundle: '<omitted>'
+    matchConditions:
+      - name: 'exclude-leases' # 每个匹配条件必须有唯一的名称
+        expression: '!(request.resource.group == "coordination.k8s.io" && request.resource.resource == "leases")' # 匹配非租约资源
+      - name: 'exclude-kubelet-requests'
+        expression: '!("system:nodes" in request.userInfo.groups)' # 匹配非节点用户发出的请求
+      - name: 'rbac' # 跳过 RBAC 请求，该请求将由第二个 Webhook 处理
+        expression: 'request.resource.group != "rbac.authorization.k8s.io"'
+
+  # 这个示例演示了如何使用 “authorizer”。
+  # 授权检查比简单的表达式更复杂，因此在这个示例中，使用第二个 Webhook 来针对 RBAC 请求进行处理。
+  # 两个 Webhook 都可以由同一个端点提供服务。
+  - name: rbac.my-webhook.example.com
+    matchPolicy: Equivalent
+    rules:
+      - operations: ['CREATE','UPDATE']
+        apiGroups: ['rbac.authorization.k8s.io']
+        apiVersions: ['*']
+        resources: ['*']
+    failurePolicy: 'Fail' # 失败时拒绝请求 (默认值)
+    sideEffects: None
+    clientConfig:
+      service:
+        namespace: my-namespace
+        name: my-webhook
+      caBundle: '<omitted>'
+    matchConditions:
+      - name: 'breakglass'
+        # 跳过由授权给 “breakglass” 的用户在这个 Webhook 上发起的请求。
+        # “breakglass” API 不需要在这个检查之外存在。
+        expression: '!authorizer.group("admissionregistration.k8s.io").resource("validatingwebhookconfigurations").name("my-webhook.example.com").check("breakglass").allowed()'
+```
+
+<!-- 
+Match conditions have access to the following CEL variables:
+-->
+匹配条件可以访问以下 CEL 变量：
+
+<!--
+- `object` - The object from the incoming request. The value is null for DELETE requests. The object
+  version may be converted based on the [matchPolicy](#matching-requests-matchpolicy).
+-->
+- `object` - 来自传入请求的对象。对于 DELETE 请求，该值为 null。
+  该对象版本可能根据 [matchPolicy](#matching-requests-matchpolicy) 进行转换。
+<!--
+- `oldObject` - The existing object. The value is null for CREATE requests.
+-->
+- `oldObject` - 现有对象。对于 CREATE 请求，该值为 null。
+<!--
+- `request` - The request portion of the [AdmissionReview](#request), excluding `object` and `oldObject`.
+-->
+- `request` - [AdmissionReview](#request) 的请求部分，不包括 object 和 oldObject。
+<!--
+- `authorizer` - A CEL Authorizer. May be used to perform authorization checks for the principal
+  (authenticated user) of the request. See
+  [Authz](https://pkg.go.dev/k8s.io/apiserver/pkg/cel/library#Authz) in the Kubernetes CEL library
+  documentation for more details.
+-->
+- `authorizer` - 一个 CEL 鉴权组件。可用于对请求的主体（经过身份认证的用户）执行鉴权检查。
+  更多详细信息，请参阅 Kubernetes CEL 库文档中的
+  [Authz](https://pkg.go.dev/k8s.io/apiserver/pkg/cel/library#Authz)。
+<!--
+- `authorizer.requestResource` - A shortcut for an authorization check configured with the request
+  resource (group, resource, (subresource), namespace, name).
+-->
+- `authorizer.requestResource` - 对配置的请求资源（组、资源、（子资源）、名字空间、名称）进行授权检查的快捷方式。
+
+<!--
+For more information on CEL expressions, refer to the
+[Common Expression Language in Kubernetes reference](/docs/reference/using-api/cel/).
+-->
+了解有关 CEL 表达式的更多信息，请参阅
+[Kubernetes 参考文档中的通用表达式语言](/zh-cn/docs/reference/using-api/cel/)。
+
+<!--
+In the event of an error evaluating a match condition the webhook is never called. Whether to reject
+the request is determined as follows:
+-->
+如果在对匹配条件求值时出现错误，则不会调用 Webhook。根据以下方式确定是否拒绝请求：
+
+<!--
+1. If **any** match condition evaluated to `false` (regardless of other errors), the API server skips the webhook.
+-->
+1. 如果**任何一个**匹配条件求值结果为 `false`（不管其他错误），API 服务器将跳过 Webhook。
+<!--
+1. Otherwise:
+    - for [`failurePolicy: Fail`](#failure-policy), reject the request (without calling the webhook).
+    - for [`failurePolicy: Ignore`](#failure-policy), proceed with the request but skip the webhook.
+-->
+1. 否则：
+   - 对于 [`failurePolicy: Fail`](#failure-policy)，拒绝请求（不调用 Webhook）。
+   - 对于 [`failurePolicy: Ignore`](#failure-policy)，继续处理请求但跳过 Webhook。
+
 <!--
 ### Contacting the webhook
 -->

From 4787efefeecb9de2610b3dbcf7439e126ef9b980 Mon Sep 17 00:00:00 2001
From: Ricardo Katz <rkatz@vmware.com>
Date: Sun, 23 Apr 2023 17:16:32 -0300
Subject: [PATCH 259/272] rkatz stepping down from pt approvers

---
 OWNERS_ALIASES | 2 --
 1 file changed, 2 deletions(-)

diff --git a/OWNERS_ALIASES b/OWNERS_ALIASES
index 05fe413e085..64d68b7737c 100644
--- a/OWNERS_ALIASES
+++ b/OWNERS_ALIASES
@@ -167,7 +167,6 @@ aliases:
     - edsoncelio
     - femrtnz
     - jcjesus
-    - rikatz
     - stormqueen1990
     - yagonobre
   sig-docs-pt-reviews: # PR reviews for Portugese content
@@ -176,7 +175,6 @@ aliases:
     - femrtnz
     - jcjesus
     - mrerlison
-    - rikatz
     - stormqueen1990
     - yagonobre
   sig-docs-vi-owners: # Admins for Vietnamese content

From 6b54e95127f9e5472fff86f3b944fff64713693a Mon Sep 17 00:00:00 2001
From: Arhell <arhell333@gmail.com>
Date: Mon, 24 Apr 2023 00:23:26 +0300
Subject: [PATCH 260/272] [ru] update curl command

---
 content/ru/docs/tasks/administer-cluster/certificates.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/ru/docs/tasks/administer-cluster/certificates.md b/content/ru/docs/tasks/administer-cluster/certificates.md
index dfb94c44c8e..3170f5b4120 100644
--- a/content/ru/docs/tasks/administer-cluster/certificates.md
+++ b/content/ru/docs/tasks/administer-cluster/certificates.md
@@ -17,7 +17,7 @@ weight: 20
 1. Скачайте, распакуйте и инициализируйте пропатченную версию `easyrsa3`.
 
    ```shell
-   curl -LO https://storage.googleapis.com/kubernetes-release/easy-rsa/easy-rsa.tar.gz
+   curl -LO curl -LO https://dl.k8s.io/easy-rsa/easy-rsa.tar.gz
    tar xzf easy-rsa.tar.gz
    cd easy-rsa-master/easyrsa3
    ./easyrsa init-pki

From c7f1fdf50c85197a997e99421b40ffbff26baece Mon Sep 17 00:00:00 2001
From: Benjamin Wang <wachao@vmware.com>
Date: Mon, 24 Apr 2023 07:00:50 +0800
Subject: [PATCH 261/272] update the minimum recommended etcd versions to
 3.4.22+ and 3.5.6+

3.3 is end of life.

There is also a data inconsistency issue in 3.4.21 and 3.5.5,
so 3.4.22+ and 3.5.6+ are the minimum recommended versions.
Please read https://groups.google.com/g/etcd-dev/c/8S7u6NqW6C4.

Signed-off-by: Benjamin Wang <wachao@vmware.com>
---
 .../en/docs/tasks/administer-cluster/configure-upgrade-etcd.md  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/tasks/administer-cluster/configure-upgrade-etcd.md b/content/en/docs/tasks/administer-cluster/configure-upgrade-etcd.md
index 542a3a57c29..6df175e93c1 100644
--- a/content/en/docs/tasks/administer-cluster/configure-upgrade-etcd.md
+++ b/content/en/docs/tasks/administer-cluster/configure-upgrade-etcd.md
@@ -38,7 +38,7 @@ weight: 270
   clusters. Therefore, run etcd clusters on dedicated machines or isolated
   environments for [guaranteed resource requirements](https://etcd.io/docs/current/op-guide/hardware/).
 
-* The minimum recommended version of etcd to run in production is `3.2.10+`.
+* The minimum recommended etcd versions to run in production are `3.4.22+` and `3.5.6+`.
 
 ## Resource requirements
 

From 428cd59d66f9522324c16d04ef59956877af6e5c Mon Sep 17 00:00:00 2001
From: Tim Bannister <tim@scalefactory.com>
Date: Mon, 24 Apr 2023 03:03:06 +0100
Subject: [PATCH 262/272] Fix article title

---
 .../en/blog/_posts/2023-04-24-openapi-v3-field-validation-ga.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/blog/_posts/2023-04-24-openapi-v3-field-validation-ga.md b/content/en/blog/_posts/2023-04-24-openapi-v3-field-validation-ga.md
index 1bd1295f975..79546bec2ce 100644
--- a/content/en/blog/_posts/2023-04-24-openapi-v3-field-validation-ga.md
+++ b/content/en/blog/_posts/2023-04-24-openapi-v3-field-validation-ga.md
@@ -1,6 +1,6 @@
 ---
 layout: blog
-title: "Server Side Field Validation and OpenAPI V3 move to GA"
+title: "Kubernetes 1.27: Server Side Field Validation and OpenAPI V3 move to GA"
 date: 2023-04-24
 slug: openapi-v3-field-validation-ga
 ---

From 6cf09b449d2cbceca986f56667f4b08117ed826a Mon Sep 17 00:00:00 2001
From: Kirill Kononovich <41591254+kirkonru@users.noreply.github.com>
Date: Wed, 31 Aug 2022 15:37:55 +0300
Subject: [PATCH 263/272] Add a RU localization for the networking.md file

Apply suggestions from code review

Co-authored-by: Dmitry Shurupov <dmitry.shurupov@palark.com>

Removed the plugins section in line with EN page
---
 .../cluster-administration/networking.md      | 32 +++++++++++++++++++
 1 file changed, 32 insertions(+)
 create mode 100644 content/ru/docs/concepts/cluster-administration/networking.md

diff --git a/content/ru/docs/concepts/cluster-administration/networking.md b/content/ru/docs/concepts/cluster-administration/networking.md
new file mode 100644
index 00000000000..3fc6964aac0
--- /dev/null
+++ b/content/ru/docs/concepts/cluster-administration/networking.md
@@ -0,0 +1,32 @@
+---
+reviewers:
+title: Сеть в кластере
+content_type: concept
+weight: 50
+---
+
+<!-- overview -->
+Сеть — важная часть Kubernetes, но понять, как именно она работает, бывает непросто. Существует 4 уникальных сетевых проблемы, которые требуют внимнаия:
+
+1. Высокосвязанные коммуникации между контейнерами: решается организацией коммуникации между {{< glossary_tooltip text="Pod'ами" term_id="pod" >}} и `localhost`.
+2. Связь Pod'ов друг с другом (Pod-to-Pod): именно ей уделяется основное внимание в этом документе.
+3. Связь Pod'ов с сервисами (Pod-to-Service): подробнее об этом можно почитать в разделе [Сервисы](/docs/concepts/services-networking/service/).
+4. Связь внешних систем с сервисами (External-to-Service): информация о данных коммуникациях также приведена в разделе [Сервисы](/docs/concepts/services-networking/service/).
+
+<!-- body -->
+
+Суть Kubernetes — в организации совместного использования хостов приложениями. Обычно совместное использование подразумевает, что два приложения не могут задействовать одни и те же порты. Создать единую глобальную схему использования портов очень сложно. В результате пользователи рискуют получить сложноустранимые проблемы на уровне кластера.
+
+Динамическое распределение портов значительно усложняет систему: каждое приложение должно уметь принимать порты в виде флагов-параметров, серверы API должны уметь вставлять динамические номера портов в конфигурационные блоки, сервисы должны знать, как найти друг друга и т.п. Вместо того чтобы пытаться разобраться со всем этим, Kubernetes использует иной подход.
+
+Больше узнать о сетевой модели Kubernetes можно в [соответствующем разделе](/docs/concepts/services-networking/).
+
+## Реализация сетевой модели Kubernetes
+
+Сетевая модель реализуется средой исполнения для контейнеров на узлах. Наиболее распространенные среды исполнения используют плагины [Container Network Interface](https://github.com/containernetworking/cni) (CNI) для управления сетью и обеспечения безопаснояти коммуникаций. Существует множество различных плагинов CNI от разных разработчиков. Некоторые из них предлагают только базовые функции, такие как добавление и удаление сетевых интерфейсов. Другие позволяют проводить интеграцию с различныеми системами оркестрации контейнеров, поддерживают запуск нескольких CNI-плагинов/расширенные функции IPAM и т.д.
+
+Неполный список сетевых аддонов, поддерживаемых Kubernetes, приведен [на соответствующей странице в разделе "Сеть и сетевая политика"](/docs/concepts/cluster-administration/addons/#networking-and-network-policy).
+
+## {{% heading "whatsnext" %}}
+
+Подробнее о разработке сетевой модели, принципах, лежащих в ее основе, и некоторых планах на будущее можно узнать из соответствующего [документа](https://git.k8s.io/design-proposals-archive/network/networking.md).

From eda71187b0971e6e0ea4a583a8f3cbbdd1ee343d Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Mon, 24 Apr 2023 19:45:10 +0800
Subject: [PATCH 264/272] sync client-authentication.v1beta1.md

sync client-authentication.v1beta1.md
---
 .../docs/reference/config-api/client-authentication.v1beta1.md  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/zh-cn/docs/reference/config-api/client-authentication.v1beta1.md b/content/zh-cn/docs/reference/config-api/client-authentication.v1beta1.md
index 6c005e2c2b2..b3524fc2b3b 100644
--- a/content/zh-cn/docs/reference/config-api/client-authentication.v1beta1.md
+++ b/content/zh-cn/docs/reference/config-api/client-authentication.v1beta1.md
@@ -290,7 +290,7 @@ exec 插件本身至少应通过文件访问许可来实施保护。</p>
 
   
 <tr><td><code>expirationTimestamp</code><br/>
-<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#time-v1-meta"><code>meta/v1.Time</code></a>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#time-v1-meta"><code>meta/v1.Time</code></a>
 </td>
 <td>
    <!-- ExpirationTimestamp indicates a time when the provided credentials expire. -->

From b00b0af5cadb0954b36da64f404886619e4c8425 Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Mon, 24 Apr 2023 19:58:45 +0800
Subject: [PATCH 265/272] sync self-subject-review-v1alpha1.md

sync self-subject-review-v1alpha1.md
---
 .../authorization-resources/self-subject-review-v1alpha1.md    | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/content/zh-cn/docs/reference/kubernetes-api/authorization-resources/self-subject-review-v1alpha1.md b/content/zh-cn/docs/reference/kubernetes-api/authorization-resources/self-subject-review-v1alpha1.md
index ecf6c758650..b98fc96aa56 100644
--- a/content/zh-cn/docs/reference/kubernetes-api/authorization-resources/self-subject-review-v1alpha1.md
+++ b/content/zh-cn/docs/reference/kubernetes-api/authorization-resources/self-subject-review-v1alpha1.md
@@ -27,10 +27,11 @@ auto_generated: true
 ## SelfSubjectReview {#SelfSubjectReview}
 
 <!--
-SelfSubjectReview contains the user information that the kube-apiserver has about the user making this request. When using impersonation, users will receive the user info of the user being impersonated.
+SelfSubjectReview contains the user information that the kube-apiserver has about the user making this request. When using impersonation, users will receive the user info of the user being impersonated. If impersonation or request header authentication is used, any extra keys will have their case ignored and returned as lowercase.
 -->
 SelfSubjectReview 包含 kube-apiserver 所拥有的与发出此请求的用户有关的用户信息。
 使用伪装时，用户将收到被伪装用户的用户信息。
+如果使用了伪装或请求头认证，任何额外的键将忽略其大小写并以小写形式返回。
 
 <hr>
 

From c76cbc8ffeba31673a454e1c229df161bd76e6fe Mon Sep 17 00:00:00 2001
From: Zhuzhenghao <zhenghao.zhu@daocloud.io>
Date: Sun, 23 Apr 2023 17:44:59 +0800
Subject: [PATCH 266/272] [zh] sync 1.2 kube-apiserver

---
 .../kube-apiserver.md                         | 184 +++++++++++-------
 1 file changed, 111 insertions(+), 73 deletions(-)

diff --git a/content/zh-cn/docs/reference/command-line-tools-reference/kube-apiserver.md b/content/zh-cn/docs/reference/command-line-tools-reference/kube-apiserver.md
index e3ac50b7ccf..355c93ce8a7 100644
--- a/content/zh-cn/docs/reference/command-line-tools-reference/kube-apiserver.md
+++ b/content/zh-cn/docs/reference/command-line-tools-reference/kube-apiserver.md
@@ -782,9 +782,9 @@ CIDRs opened in GCE firewall for L7 LB traffic proxy & health checks
 <tr>
 <td></td><td style="line-height: 130%; word-wrap: break-word;">
 <!--
-Enable lock contention profiling, if profiling is enabled
+Enable block profiling, if profiling is enabled
 -->
-如果启用了性能分析，则启用锁争用性能分析。
+如果启用了性能分析，则启用阻塞分析。
 </td>
 </tr>
 
@@ -793,17 +793,33 @@ Enable lock contention profiling, if profiling is enabled
 </tr>
 <tr>
 <td></td><td style="line-height: 130%; word-wrap: break-word;">
+<p>
 <!--
 List of allowed origins for CORS, comma separated.  
 An allowed origin can be a regular expression to support subdomain matching. 
-If this list is empty CORS will not be enabled.
+If this list is empty CORS will not be enabled. Please ensure each expression matches the entire hostname by anchoring to the start with '^' or including the '//' prefix, and by anchoring to the end with '$' or including the ':' port separator suffix. Examples of valid expressions are '//example.com(:|$)' and '^https://example.com(:|$)'
 -->
 CORS 允许的来源清单，以逗号分隔。
 允许的来源可以是支持子域匹配的正则表达式。
 如果此列表为空，则不会启用 CORS。
+请确保每个表达式与整个主机名相匹配，方法是用'^'锚定开始或包括'//'前缀，同时用'$'锚定结束或包括':'端口分隔符后缀。
+有效表达式的例子是'//example.com(:|$)'和'^https://example.com(:|$)'。
+</p>
 </td>
 </tr>
 
+<tr>
+<td colspan="2">--debug-socket-path string</td>
+</tr>
+<tr>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>
+<!--
+Use an unprotected (no authn/authz) unix-domain socket for profiling with the given path
+-->
+使用位于给定路径的、未受保护的（无身份认证或鉴权的）UNIX 域套接字执行性能分析。
+</p></td>
+</tr>
+
 <tr>
 <td colspan="2">--default-not-ready-toleration-seconds int&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<!--Default: -->默认值：300</td>
 </tr>
@@ -853,13 +869,11 @@ Number of workers spawned for DeleteCollection call. These are used to speed up
 </td>
 <td style="line-height: 130%; word-wrap: break-word;">
 <!--
-admission plugins that should be disabled although they are in the default enabled plugins list (NamespaceLifecycle, LimitRanger, ServiceAccount, TaintNodesByCondition, PodSecurity, Priority, DefaultTolerationSeconds, DefaultStorageClass, StorageObjectInUseProtection, PersistentVolumeClaimResize, RuntimeClass, CertificateApproval, CertificateSigning, CertificateSubjectRestriction, DefaultIngressClass, MutatingAdmissionWebhook, ValidatingAdmissionPolicy, ValidatingAdmissionWebhook, ResourceQuota).
-Comma-delimited list of admission plugins: AlwaysAdmit, AlwaysDeny, AlwaysPullImages, CertificateApproval, CertificateSigning, CertificateSubjectRestriction, DefaultIngressClass, DefaultStorageClass, DefaultTolerationSeconds, DenyServiceExternalIPs, EventRateLimit, ExtendedResourceToleration, ImagePolicyWebhook, LimitPodHardAntiAffinityTopology, LimitRanger, MutatingAdmissionWebhook, NamespaceAutoProvision, NamespaceExists, NamespaceLifecycle, NodeRestriction, OwnerReferencesPermissionEnforcement, PersistentVolumeClaimResize, PersistentVolumeLabel, PodNodeSelector, PodSecurity, PodTolerationRestriction, Priority, ResourceQuota, RuntimeClass, SecurityContextDeny, ServiceAccount, StorageObjectInUseProtection, TaintNodesByCondition, ValidatingAdmissionPolicy, ValidatingAdmissionWebhook.
-The order of plugins in this flag does not matter.
+admission plugins that should be disabled although they are in the default enabled plugins list (NamespaceLifecycle, LimitRanger, ServiceAccount, TaintNodesByCondition, PodSecurity, Priority, DefaultTolerationSeconds, DefaultStorageClass, StorageObjectInUseProtection, PersistentVolumeClaimResize, RuntimeClass, CertificateApproval, CertificateSigning, ClusterTrustBundleAttest, CertificateSubjectRestriction, DefaultIngressClass, MutatingAdmissionWebhook, ValidatingAdmissionPolicy, ValidatingAdmissionWebhook, ResourceQuota). Comma-delimited list of admission plugins: AlwaysAdmit, AlwaysDeny, AlwaysPullImages, CertificateApproval, CertificateSigning, CertificateSubjectRestriction, ClusterTrustBundleAttest, DefaultIngressClass, DefaultStorageClass, DefaultTolerationSeconds, DenyServiceExternalIPs, EventRateLimit, ExtendedResourceToleration, ImagePolicyWebhook, LimitPodHardAntiAffinityTopology, LimitRanger, MutatingAdmissionWebhook, NamespaceAutoProvision, NamespaceExists, NamespaceLifecycle, NodeRestriction, OwnerReferencesPermissionEnforcement, PersistentVolumeClaimResize, PersistentVolumeLabel, PodNodeSelector, PodSecurity, PodTolerationRestriction, Priority, ResourceQuota, RuntimeClass, SecurityContextDeny, ServiceAccount, StorageObjectInUseProtection, TaintNodesByCondition, ValidatingAdmissionPolicy, ValidatingAdmissionWebhook. The order of plugins in this flag does not matter.
 -->
 <p>
-尽管位于默认启用的插件列表中，仍须被禁用的准入插件（NamespaceLifecycle、LimitRanger、ServiceAccount、TaintNodesByCondition、PodSecurity、Priority、DefaultTolerationSeconds、DefaultStorageClass、StorageObjectInUseProtection、PersistentVolumeClaimResize、RuntimeClass、CertificateApproval、CertificateSigning、CertificateSubjectRestriction、DefaultIngressClass、MutatingAdmissionWebhook、ValidatingAdmissionPolicy、ValidatingAdmissionWebhook、ResourceQuota）。
-取值为逗号分隔的准入插件列表：AlwaysAdmit、AlwaysDeny、AlwaysPullImages、CertificateApproval、CertificateSigning、CertificateSubjectRestriction、DefaultIngressClass、DefaultStorageClass、DefaultTolerationSeconds、DenyServiceExternalIPs、EventRateLimit、ExtendedResourceToleration、ImagePolicyWebhook、LimitPodHardAntiAffinityTopology、LimitRanger、MutatingAdmissionWebhook、NamespaceAutoProvision、NamespaceExists、NamespaceLifecycle、NodeRestriction、OwnerReferencesPermissionEnforcement、PersistentVolumeClaimResize、PersistentVolumeLabel、PodNodeSelector、PodSecurity、PodTolerationRestriction、Priority、ResourceQuota、RuntimeClass、SecurityContextDeny、ServiceAccount、StorageObjectInUseProtection、TaintNodesByCondition、ValidatingAdmissionPolicy、ValidatingAdmissionWebhook。
+尽管位于默认启用的插件列表中，仍须被禁用的准入插件（NamespaceLifecycle、LimitRanger、ServiceAccount、TaintNodesByCondition、PodSecurity、Priority、DefaultTolerationSeconds、DefaultStorageClass、StorageObjectInUseProtection、PersistentVolumeClaimResize、RuntimeClass、CertificateApproval、CertificateSigning、ClusterTrustBundleAttest、CertificateSubjectRestriction、DefaultIngressClass、MutatingAdmissionWebhook、ValidatingAdmissionPolicy、ValidatingAdmissionWebhook、ResourceQuota）。
+取值为逗号分隔的准入插件列表：AlwaysAdmit、AlwaysDeny、AlwaysPullImages、CertificateApproval、CertificateSigning、CertificateSubjectRestriction、ClusterTrustBundleAttest、DefaultIngressClass、DefaultStorageClass、DefaultTolerationSeconds、DenyServiceExternalIPs、EventRateLimit、ExtendedResourceToleration、ImagePolicyWebhook、LimitPodHardAntiAffinityTopology、LimitRanger、MutatingAdmissionWebhook、NamespaceAutoProvision、NamespaceExists、NamespaceLifecycle、NodeRestriction、OwnerReferencesPermissionEnforcement、PersistentVolumeClaimResize、PersistentVolumeLabel、PodNodeSelector、PodSecurity、PodTolerationRestriction、Priority、ResourceQuota、RuntimeClass、SecurityContextDeny、ServiceAccount、StorageObjectInUseProtection、TaintNodesByCondition、ValidatingAdmissionPolicy、ValidatingAdmissionWebhook。
 该标志中插件的顺序无关紧要。
 </p>
 </td>
@@ -900,11 +914,11 @@ File with apiserver egress selector configuration.
 </td>
 <td style="line-height: 130%; word-wrap: break-word;">
 <!--
-admission plugins that should be enabled in addition to default enabled ones (NamespaceLifecycle, LimitRanger, ServiceAccount, TaintNodesByCondition, PodSecurity, Priority, DefaultTolerationSeconds, DefaultStorageClass, StorageObjectInUseProtection, PersistentVolumeClaimResize, RuntimeClass, CertificateApproval, CertificateSigning, CertificateSubjectRestriction, DefaultIngressClass, MutatingAdmissionWebhook, ValidatingAdmissionPolicy, ValidatingAdmissionWebhook, ResourceQuota). Comma-delimited list of admission plugins: AlwaysAdmit, AlwaysDeny, AlwaysPullImages, CertificateApproval, CertificateSigning, CertificateSubjectRestriction, DefaultIngressClass, DefaultStorageClass, DefaultTolerationSeconds, DenyServiceExternalIPs, EventRateLimit, ExtendedResourceToleration, ImagePolicyWebhook, LimitPodHardAntiAffinityTopology, LimitRanger, MutatingAdmissionWebhook, NamespaceAutoProvision, NamespaceExists, NamespaceLifecycle, NodeRestriction, OwnerReferencesPermissionEnforcement, PersistentVolumeClaimResize, PersistentVolumeLabel, PodNodeSelector, PodSecurity, PodTolerationRestriction, Priority, ResourceQuota, RuntimeClass, SecurityContextDeny, ServiceAccount, StorageObjectInUseProtection, TaintNodesByCondition, ValidatingAdmissionPolicy, ValidatingAdmissionWebhook. The order of plugins in this flag does not matter.
+admission plugins that should be enabled in addition to default enabled ones (NamespaceLifecycle, LimitRanger, ServiceAccount, TaintNodesByCondition, PodSecurity, Priority, DefaultTolerationSeconds, DefaultStorageClass, StorageObjectInUseProtection, PersistentVolumeClaimResize, RuntimeClass, CertificateApproval, CertificateSigning, ClusterTrustBundleAttest, CertificateSubjectRestriction, DefaultIngressClass, MutatingAdmissionWebhook, ValidatingAdmissionPolicy, ValidatingAdmissionWebhook, ResourceQuota). Comma-delimited list of admission plugins: AlwaysAdmit, AlwaysDeny, AlwaysPullImages, CertificateApproval, CertificateSigning, CertificateSubjectRestriction, ClusterTrustBundleAttest, DefaultIngressClass, DefaultStorageClass, DefaultTolerationSeconds, DenyServiceExternalIPs, EventRateLimit, ExtendedResourceToleration, ImagePolicyWebhook, LimitPodHardAntiAffinityTopology, LimitRanger, MutatingAdmissionWebhook, NamespaceAutoProvision, NamespaceExists, NamespaceLifecycle, NodeRestriction, OwnerReferencesPermissionEnforcement, PersistentVolumeClaimResize, PersistentVolumeLabel, PodNodeSelector, PodSecurity, PodTolerationRestriction, Priority, ResourceQuota, RuntimeClass, SecurityContextDeny, ServiceAccount, StorageObjectInUseProtection, TaintNodesByCondition, ValidatingAdmissionPolicy, ValidatingAdmissionWebhook. The order of plugins in this flag does not matter.
 -->
 <p>
-除了默认启用的插件（NamespaceLifecycle、LimitRanger、ServiceAccount、TaintNodesByCondition、PodSecurity、Priority、DefaultTolerationSeconds、DefaultStorageClass、StorageObjectInUseProtection、PersistentVolumeClaimResize、RuntimeClass、CertificateApproval、CertificateSigning、CertificateSubjectRestriction、DefaultIngressClass、MutatingAdmissionWebhook、ValidatingAdmissionPolicy、ValidatingAdmissionWebhook、ResourceQuota）之外要启用的准入插件。
-取值为逗号分隔的准入插件列表：AlwaysAdmit、AlwaysDeny、AlwaysPullImages、CertificateApproval、CertificateSigning、CertificateSubjectRestriction、DefaultIngressClass、DefaultStorageClass、DefaultTolerationSeconds、DenyServiceExternalIPs、EventRateLimit、ExtendedResourceToleration、ImagePolicyWebhook、LimitPodHardAntiAffinityTopology、LimitRanger、MutatingAdmissionWebhook、NamespaceAutoProvision、NamespaceExists、NamespaceLifecycle、NodeRestriction、OwnerReferencesPermissionEnforcement、PersistentVolumeClaimResize、PersistentVolumeLabel、PodNodeSelector、PodSecurity、PodTolerationRestriction、Priority、ResourceQuota、RuntimeClass、SecurityContextDeny、ServiceAccount、StorageObjectInUseProtection、TaintNodesByCondition、ValidatingAdmissionPolicy、ValidatingAdmissionWebhook。该标志中插件的顺序无关紧要。
+除了默认启用的插件（NamespaceLifecycle、LimitRanger、ServiceAccount、TaintNodesByCondition、PodSecurity、Priority、DefaultTolerationSeconds、DefaultStorageClass、StorageObjectInUseProtection、PersistentVolumeClaimResize、RuntimeClass、CertificateApproval、CertificateSigning、ClusterTrustBundleAttest、CertificateSubjectRestriction、DefaultIngressClass、MutatingAdmissionWebhook、ValidatingAdmissionPolicy、ValidatingAdmissionWebhook、ResourceQuota）之外要启用的准入插件。
+取值为逗号分隔的准入插件列表：AlwaysAdmit、AlwaysDeny、AlwaysPullImages、CertificateApproval、CertificateSigning、CertificateSubjectRestriction、ClusterTrustBundleAttest、DefaultIngressClass、DefaultStorageClass、DefaultTolerationSeconds、DenyServiceExternalIPs、EventRateLimit、ExtendedResourceToleration、ImagePolicyWebhook、LimitPodHardAntiAffinityTopology、LimitRanger、MutatingAdmissionWebhook、NamespaceAutoProvision、NamespaceExists、NamespaceLifecycle、NodeRestriction、OwnerReferencesPermissionEnforcement、PersistentVolumeClaimResize、PersistentVolumeLabel、PodNodeSelector、PodSecurity、PodTolerationRestriction、Priority、ResourceQuota、RuntimeClass、SecurityContextDeny、ServiceAccount、StorageObjectInUseProtection、TaintNodesByCondition、ValidatingAdmissionPolicy、ValidatingAdmissionWebhook。该标志中插件的顺序无关紧要。
 </p>
 </td>
 </tr>
@@ -1185,16 +1199,16 @@ comma-separated 'key=True|False' pairs
 <tr>
 <td>
 </td>
-<td style="line-height: 130%; word-wrap: break-word;">
+<td style="line-height: 130%; word-wrap: break-word;"><p>
 <!--
-A set of key=value pairs that describe feature gates for alpha/experimental features. Options are:<br/>
-APIListChunking=true|false (BETA - default=true)<br/>
+A set of key=value pairs that describe feature gates for alpha/experimental features. Options are:<br/>APIListChunking=true|false (BETA - default=true)<br/>
 APIPriorityAndFairness=true|false (BETA - default=true)<br/>
 APIResponseCompression=true|false (BETA - default=true)<br/>
-APISelfSubjectReview=true|false (ALPHA - default=false)<br/>
+APISelfSubjectReview=true|false (BETA - default=true)<br/>
 APIServerIdentity=true|false (BETA - default=true)<br/>
-APIServerTracing=true|false (ALPHA - default=false)<br/>
-AggregatedDiscoveryEndpoint=true|false (ALPHA - default=false)<br/>
+APIServerTracing=true|false (BETA - default=true)<br/>
+AdmissionWebhookMatchConditions=true|false (ALPHA - default=false)<br/>
+AggregatedDiscoveryEndpoint=true|false (BETA - default=true)<br/>
 AllAlpha=true|false (ALPHA - default=false)<br/>
 AllBeta=true|false (BETA - default=false)<br/>
 AnyVolumeDataSource=true|false (BETA - default=true)<br/>
@@ -1204,29 +1218,31 @@ CPUManagerPolicyBetaOptions=true|false (BETA - default=true)<br/>
 CPUManagerPolicyOptions=true|false (BETA - default=true)<br/>
 CSIMigrationPortworx=true|false (BETA - default=false)<br/>
 CSIMigrationRBD=true|false (ALPHA - default=false)<br/>
-CSINodeExpandSecret=true|false (ALPHA - default=false)<br/>
+CSINodeExpandSecret=true|false (BETA - default=true)<br/>
 CSIVolumeHealth=true|false (ALPHA - default=false)<br/>
-ComponentSLIs=true|false (ALPHA - default=false)<br/>
+CloudControllerManagerWebhook=true|false (ALPHA - default=false)<br/>
+CloudDualStackNodeIPs=true|false (ALPHA - default=false)<br/>
+ClusterTrustBundle=true|false (ALPHA - default=false)<br/>
+ComponentSLIs=true|false (BETA - default=true)<br/>
 ContainerCheckpoint=true|false (ALPHA - default=false)<br/>
 ContextualLogging=true|false (ALPHA - default=false)<br/>
-CronJobTimeZone=true|false (BETA - default=true)<br/>
 CrossNamespaceVolumeDataSource=true|false (ALPHA - default=false)<br/>
 CustomCPUCFSQuotaPeriod=true|false (ALPHA - default=false)<br/>
 CustomResourceValidationExpressions=true|false (BETA - default=true)<br/>
 DisableCloudProviders=true|false (ALPHA - default=false)<br/>
 DisableKubeletCloudCredentialProviders=true|false (ALPHA - default=false)<br/>
-DownwardAPIHugePages=true|false (BETA - default=true)<br/>
 DynamicResourceAllocation=true|false (ALPHA - default=false)<br/>
-EventedPLEG=true|false (ALPHA - default=false)<br/>
+ElasticIndexedJob=true|false (BETA - default=true)<br/>
+EventedPLEG=true|false (BETA - default=false)<br/>
 ExpandedDNSConfig=true|false (BETA - default=true)<br/>
 ExperimentalHostUserNamespaceDefaulting=true|false (BETA - default=false)<br/>
-GRPCContainerProbe=true|false (BETA - default=true)<br/>
-GracefulNodeShutdown=true|false (BETA - default=true)
+GracefulNodeShutdown=true|false (BETA - default=true)<br/>
 GracefulNodeShutdownBasedOnPodPriority=true|false (BETA - default=true)<br/>
-HPAContainerMetrics=true|false (ALPHA - default=false)<br/>
+HPAContainerMetrics=true|false (BETA - default=true)<br/>
 HPAScaleToZero=true|false (ALPHA - default=false)<br/>
 HonorPVReclaimPolicy=true|false (ALPHA - default=false)<br/>
-IPTablesOwnershipCleanup=true|false (ALPHA - default=false)<br/>
+IPTablesOwnershipCleanup=true|false (BETA - default=true)<br/>
+InPlacePodVerticalScaling=true|false (ALPHA - default=false)<br/>
 InTreePluginAWSUnregister=true|false (ALPHA - default=false)<br/>
 InTreePluginAzureDiskUnregister=true|false (ALPHA - default=false)<br/>
 InTreePluginAzureFileUnregister=true|false (ALPHA - default=false)<br/>
@@ -1235,76 +1251,80 @@ InTreePluginOpenStackUnregister=true|false (ALPHA - default=false)<br/>
 InTreePluginPortworxUnregister=true|false (ALPHA - default=false)<br/>
 InTreePluginRBDUnregister=true|false (ALPHA - default=false)<br/>
 InTreePluginvSphereUnregister=true|false (ALPHA - default=false)<br/>
-JobMutableNodeSchedulingDirectives=true|false (BETA - default=true)<br/>
 JobPodFailurePolicy=true|false (BETA - default=true)<br/>
 JobReadyPods=true|false (BETA - default=true)<br/>
-KMSv2=true|false (ALPHA - default=false)<br/>
+KMSv2=true|false (BETA - default=true)<br/>
 KubeletInUserNamespace=true|false (ALPHA - default=false)<br/>
 KubeletPodResources=true|false (BETA - default=true)<br/>
+KubeletPodResourcesDynamicResources=true|false (ALPHA - default=false)<br/>
+KubeletPodResourcesGet=true|false (ALPHA - default=false)<br/>
 KubeletPodResourcesGetAllocatable=true|false (BETA - default=true)<br/>
-KubeletTracing=true|false (ALPHA - default=false)<br/>
-LegacyServiceAccountTokenTracking=true|false (ALPHA - default=false)<br/>
+KubeletTracing=true|false (BETA - default=true)<br/>
+LegacyServiceAccountTokenTracking=true|false (BETA - default=true)<br/>
 LocalStorageCapacityIsolationFSQuotaMonitoring=true|false (ALPHA - default=false)<br/>
 LogarithmicScaleDown=true|false (BETA - default=true)<br/>
 LoggingAlphaOptions=true|false (ALPHA - default=false)<br/>
 LoggingBetaOptions=true|false (BETA - default=true)<br/>
-MatchLabelKeysInPodTopologySpread=true|false (ALPHA - default=false)<br/>
+MatchLabelKeysInPodTopologySpread=true|false (BETA - default=true)<br/>
 MaxUnavailableStatefulSet=true|false (ALPHA - default=false)<br/>
 MemoryManager=true|false (BETA - default=true)<br/>
 MemoryQoS=true|false (ALPHA - default=false)<br/>
-MinDomainsInPodTopologySpread=true|false (BETA - default=false)<br/>
-MinimizeIPTablesRestore=true|false (ALPHA - default=false)<br/>
+MinDomainsInPodTopologySpread=true|false (BETA - default=true)<br/>
+MinimizeIPTablesRestore=true|false (BETA - default=true)<br/>
 MultiCIDRRangeAllocator=true|false (ALPHA - default=false)<br/>
+MultiCIDRServiceAllocator=true|false (ALPHA - default=false)<br/>
 NetworkPolicyStatus=true|false (ALPHA - default=false)<br/>
+NewVolumeManagerReconstruction=true|false (BETA - default=true)<br/>
 NodeInclusionPolicyInPodTopologySpread=true|false (BETA - default=true)<br/>
+NodeLogQuery=true|false (ALPHA - default=false)<br/>
 NodeOutOfServiceVolumeDetach=true|false (BETA - default=true)<br/>
 NodeSwap=true|false (ALPHA - default=false)<br/>
 OpenAPIEnums=true|false (BETA - default=true)<br/>
-OpenAPIV3=true|false (BETA - default=true)<br/>
-PDBUnhealthyPodEvictionPolicy=true|false (ALPHA - default=false)<br/>
+PDBUnhealthyPodEvictionPolicy=true|false (BETA - default=true)<br/>
 PodAndContainerStatsFromCRI=true|false (ALPHA - default=false)<br/>
 PodDeletionCost=true|false (BETA - default=true)<br/>
 PodDisruptionConditions=true|false (BETA - default=true)<br/>
 PodHasNetworkCondition=true|false (ALPHA - default=false)<br/>
-PodSchedulingReadiness=true|false (ALPHA - default=false)<br/>
+PodSchedulingReadiness=true|false (BETA - default=true)<br/>
 ProbeTerminationGracePeriod=true|false (BETA - default=true)<br/>
 ProcMountType=true|false (ALPHA - default=false)<br/>
 ProxyTerminatingEndpoints=true|false (BETA - default=true)<br/>
 QOSReserved=true|false (ALPHA - default=false)<br/>
-ReadWriteOncePod=true|false (ALPHA - default=false)<br/>
+ReadWriteOncePod=true|false (BETA - default=true)<br/>
 RecoverVolumeExpansionFailure=true|false (ALPHA - default=false)<br/>
 RemainingItemCount=true|false (BETA - default=true)<br/>
 RetroactiveDefaultStorageClass=true|false (BETA - default=true)<br/>
 RotateKubeletServerCertificate=true|false (BETA - default=true)<br/>
-SELinuxMountReadWriteOncePod=true|false (ALPHA - default=false)<br/>
-SeccompDefault=true|false (BETA - default=true)<br/>
-ServerSideFieldValidation=true|false (BETA - default=true)<br/>
+SELinuxMountReadWriteOncePod=true|false (BETA - default=true)<br/>
+SecurityContextDeny=true|false (ALPHA - default=false)<br/>
+ServiceNodePortStaticSubrange=true|false (ALPHA - default=false)<br/>
 SizeMemoryBackedVolumes=true|false (BETA - default=true)<br/>
-StatefulSetAutoDeletePVC=true|false (ALPHA - default=false)<br/>
-StatefulSetStartOrdinal=true|false (ALPHA - default=false)<br/>
+StableLoadBalancerNodeSet=true|false (BETA - default=true)<br/>
+StatefulSetAutoDeletePVC=true|false (BETA - default=true)<br/>
+StatefulSetStartOrdinal=true|false (BETA - default=true)<br/>
 StorageVersionAPI=true|false (ALPHA - default=false)<br/>
 StorageVersionHash=true|false (BETA - default=true)<br/>
 TopologyAwareHints=true|false (BETA - default=true)<br/>
-TopologyManager=true|false (BETA - default=true)<br/>
 TopologyManagerPolicyAlphaOptions=true|false (ALPHA - default=false)<br/>
 TopologyManagerPolicyBetaOptions=true|false (BETA - default=false)<br/>
 TopologyManagerPolicyOptions=true|false (ALPHA - default=false)<br/>
 UserNamespacesStatelessPodsSupport=true|false (ALPHA - default=false)<br/>
 ValidatingAdmissionPolicy=true|false (ALPHA - default=false)<br/>
 VolumeCapacityPriority=true|false (ALPHA - default=false)<br/>
+WatchList=true|false (ALPHA - default=false)<br/>
 WinDSR=true|false (ALPHA - default=false)<br/>
 WinOverlay=true|false (BETA - default=true)<br/>
 WindowsHostNetwork=true|false (ALPHA - default=true)
 -->
-<p>
 一组 key=value 对，用来描述测试性/试验性功能的特性门控。可选项有：<br/>
 APIListChunking=true|false (BETA - 默认值=true)<br/>
 APIPriorityAndFairness=true|false (BETA - 默认值=true)<br/>
 APIResponseCompression=true|false (BETA - 默认值=true)<br/>
-APISelfSubjectReview=true|false (ALPHA - 默认值=false)<br/>
+APISelfSubjectReview=true|false (BETA - 默认值=true)<br/>
 APIServerIdentity=true|false (BETA - 默认值=true)<br/>
-APIServerTracing=true|false (ALPHA - 默认值=false)<br/>
-AggregatedDiscoveryEndpoint=true|false (ALPHA - 默认值=false)<br/>
+APIServerTracing=true|false (BETA - 默认值=true)<br/>
+AdmissionWebhookMatchConditions=true|false (ALPHA - 默认值=false)<br/>
+AggregatedDiscoveryEndpoint=true|false (BETA - 默认值=true)<br/>
 AllAlpha=true|false (ALPHA - 默认值=false)<br/>
 AllBeta=true|false (BETA - 默认值=false)<br/>
 AnyVolumeDataSource=true|false (BETA - 默认值=true)<br/>
@@ -1314,29 +1334,31 @@ CPUManagerPolicyBetaOptions=true|false (BETA - 默认值=true)<br/>
 CPUManagerPolicyOptions=true|false (BETA - 默认值=true)<br/>
 CSIMigrationPortworx=true|false (BETA - 默认值=false)<br/>
 CSIMigrationRBD=true|false (ALPHA - 默认值=false)<br/>
-CSINodeExpandSecret=true|false (ALPHA - 默认值=false)<br/>
+CSINodeExpandSecret=true|false (BETA - 默认值=true)<br/>
 CSIVolumeHealth=true|false (ALPHA - 默认值=false)<br/>
-ComponentSLIs=true|false (ALPHA - 默认值=false)<br/>
+CloudControllerManagerWebhook=true|false (ALPHA - 默认值=false)<br/>
+CloudDualStackNodeIPs=true|false (ALPHA - 默认值=false)<br/>
+ClusterTrustBundle=true|false (ALPHA - 默认值=false)<br/>
+ComponentSLIs=true|false (BETA - 默认值=true)<br/>
 ContainerCheckpoint=true|false (ALPHA - 默认值=false)<br/>
 ContextualLogging=true|false (ALPHA - 默认值=false)<br/>
-CronJobTimeZone=true|false (BETA - 默认值=true)<br/>
 CrossNamespaceVolumeDataSource=true|false (ALPHA - 默认值=false)<br/>
 CustomCPUCFSQuotaPeriod=true|false (ALPHA - 默认值=false)<br/>
 CustomResourceValidationExpressions=true|false (BETA - 默认值=true)<br/>
 DisableCloudProviders=true|false (ALPHA - 默认值=false)<br/>
 DisableKubeletCloudCredentialProviders=true|false (ALPHA - 默认值=false)<br/>
-DownwardAPIHugePages=true|false (BETA - 默认值=true)<br/>
 DynamicResourceAllocation=true|false (ALPHA - 默认值=false)<br/>
-EventedPLEG=true|false (ALPHA - 默认值=false)<br/>
+ElasticIndexedJob=true|false (BETA - 默认值=true)<br/>
+EventedPLEG=true|false (BETA - 默认值=false)<br/>
 ExpandedDNSConfig=true|false (BETA - 默认值=true)<br/>
 ExperimentalHostUserNamespaceDefaulting=true|false (BETA - 默认值=false)<br/>
-GRPCContainerProbe=true|false (BETA - 默认值=true)<br/>
-GracefulNodeShutdown=true|false (BETA - 默认值=true)
+GracefulNodeShutdown=true|false (BETA - 默认值=true)<br/>
 GracefulNodeShutdownBasedOnPodPriority=true|false (BETA - 默认值=true)<br/>
-HPAContainerMetrics=true|false (ALPHA - 默认值=false)<br/>
+HPAContainerMetrics=true|false (BETA - 默认值=true)<br/>
 HPAScaleToZero=true|false (ALPHA - 默认值=false)<br/>
 HonorPVReclaimPolicy=true|false (ALPHA - 默认值=false)<br/>
-IPTablesOwnershipCleanup=true|false (ALPHA - 默认值=false)<br/>
+IPTablesOwnershipCleanup=true|false (BETA - 默认值=true)<br/>
+InPlacePodVerticalScaling=true|false (ALPHA - 默认值=false)<br/>
 InTreePluginAWSUnregister=true|false (ALPHA - 默认值=false)<br/>
 InTreePluginAzureDiskUnregister=true|false (ALPHA - 默认值=false)<br/>
 InTreePluginAzureFileUnregister=true|false (ALPHA - 默认值=false)<br/>
@@ -1345,63 +1367,67 @@ InTreePluginOpenStackUnregister=true|false (ALPHA - 默认值=false)<br/>
 InTreePluginPortworxUnregister=true|false (ALPHA - 默认值=false)<br/>
 InTreePluginRBDUnregister=true|false (ALPHA - 默认值=false)<br/>
 InTreePluginvSphereUnregister=true|false (ALPHA - 默认值=false)<br/>
-JobMutableNodeSchedulingDirectives=true|false (BETA - 默认值=true)<br/>
 JobPodFailurePolicy=true|false (BETA - 默认值=true)<br/>
 JobReadyPods=true|false (BETA - 默认值=true)<br/>
-KMSv2=true|false (ALPHA - 默认值=false)<br/>
+KMSv2=true|false (BETA - 默认值=true)<br/>
 KubeletInUserNamespace=true|false (ALPHA - 默认值=false)<br/>
 KubeletPodResources=true|false (BETA - 默认值=true)<br/>
+KubeletPodResourcesDynamicResources=true|false (ALPHA - 默认值=false)<br/>
+KubeletPodResourcesGet=true|false (ALPHA - 默认值=false)<br/>
 KubeletPodResourcesGetAllocatable=true|false (BETA - 默认值=true)<br/>
-KubeletTracing=true|false (ALPHA - 默认值=false)<br/>
-LegacyServiceAccountTokenTracking=true|false (ALPHA - 默认值=false)<br/>
+KubeletTracing=true|false (BETA - 默认值=true)<br/>
+LegacyServiceAccountTokenTracking=true|false (BETA - 默认值=true)<br/>
 LocalStorageCapacityIsolationFSQuotaMonitoring=true|false (ALPHA - 默认值=false)<br/>
 LogarithmicScaleDown=true|false (BETA - 默认值=true)<br/>
 LoggingAlphaOptions=true|false (ALPHA - 默认值=false)<br/>
 LoggingBetaOptions=true|false (BETA - 默认值=true)<br/>
-MatchLabelKeysInPodTopologySpread=true|false (ALPHA - 默认值=false)<br/>
+MatchLabelKeysInPodTopologySpread=true|false (BETA - 默认值=true)<br/>
 MaxUnavailableStatefulSet=true|false (ALPHA - 默认值=false)<br/>
 MemoryManager=true|false (BETA - 默认值=true)<br/>
 MemoryQoS=true|false (ALPHA - 默认值=false)<br/>
-MinDomainsInPodTopologySpread=true|false (BETA - 默认值=false)<br/>
-MinimizeIPTablesRestore=true|false (ALPHA - 默认值=false)<br/>
+MinDomainsInPodTopologySpread=true|false (BETA - 默认值=true)<br/>
+MinimizeIPTablesRestore=true|false (BETA - 默认值=true)<br/>
 MultiCIDRRangeAllocator=true|false (ALPHA - 默认值=false)<br/>
+MultiCIDRServiceAllocator=true|false (ALPHA - 默认值=false)<br/>
 NetworkPolicyStatus=true|false (ALPHA - 默认值=false)<br/>
+NewVolumeManagerReconstruction=true|false (BETA - 默认值=true)<br/>
 NodeInclusionPolicyInPodTopologySpread=true|false (BETA - 默认值=true)<br/>
+NodeLogQuery=true|false (ALPHA - 默认值=false)<br/>
 NodeOutOfServiceVolumeDetach=true|false (BETA - 默认值=true)<br/>
 NodeSwap=true|false (ALPHA - 默认值=false)<br/>
 OpenAPIEnums=true|false (BETA - 默认值=true)<br/>
-OpenAPIV3=true|false (BETA - 默认值=true)<br/>
-PDBUnhealthyPodEvictionPolicy=true|false (ALPHA - 默认值=false)<br/>
+PDBUnhealthyPodEvictionPolicy=true|false (BETA - 默认值=true)<br/>
 PodAndContainerStatsFromCRI=true|false (ALPHA - 默认值=false)<br/>
 PodDeletionCost=true|false (BETA - 默认值=true)<br/>
 PodDisruptionConditions=true|false (BETA - 默认值=true)<br/>
 PodHasNetworkCondition=true|false (ALPHA - 默认值=false)<br/>
-PodSchedulingReadiness=true|false (ALPHA - 默认值=false)<br/>
+PodSchedulingReadiness=true|false (BETA - 默认值=true)<br/>
 ProbeTerminationGracePeriod=true|false (BETA - 默认值=true)<br/>
 ProcMountType=true|false (ALPHA - 默认值=false)<br/>
 ProxyTerminatingEndpoints=true|false (BETA - 默认值=true)<br/>
 QOSReserved=true|false (ALPHA - 默认值=false)<br/>
-ReadWriteOncePod=true|false (ALPHA - 默认值=false)<br/>
+ReadWriteOncePod=true|false (BETA - 默认值=true)<br/>
 RecoverVolumeExpansionFailure=true|false (ALPHA - 默认值=false)<br/>
 RemainingItemCount=true|false (BETA - 默认值=true)<br/>
 RetroactiveDefaultStorageClass=true|false (BETA - 默认值=true)<br/>
 RotateKubeletServerCertificate=true|false (BETA - 默认值=true)<br/>
-SELinuxMountReadWriteOncePod=true|false (ALPHA - 默认值=false)<br/>
-SeccompDefault=true|false (BETA - 默认值=true)<br/>
-ServerSideFieldValidation=true|false (BETA - 默认值=true)<br/>
+SELinuxMountReadWriteOncePod=true|false (BETA - 默认值=true)<br/>
+SecurityContextDeny=true|false (ALPHA - 默认值=false)<br/>
+ServiceNodePortStaticSubrange=true|false (ALPHA - 默认值=false)<br/>
 SizeMemoryBackedVolumes=true|false (BETA - 默认值=true)<br/>
-StatefulSetAutoDeletePVC=true|false (ALPHA - 默认值=false)<br/>
-StatefulSetStartOrdinal=true|false (ALPHA - 默认值=false)<br/>
+StableLoadBalancerNodeSet=true|false (BETA - 默认值=true)<br/>
+StatefulSetAutoDeletePVC=true|false (BETA - 默认值=true)<br/>
+StatefulSetStartOrdinal=true|false (BETA - 默认值=true)<br/>
 StorageVersionAPI=true|false (ALPHA - 默认值=false)<br/>
 StorageVersionHash=true|false (BETA - 默认值=true)<br/>
 TopologyAwareHints=true|false (BETA - 默认值=true)<br/>
-TopologyManager=true|false (BETA - 默认值=true)<br/>
 TopologyManagerPolicyAlphaOptions=true|false (ALPHA - 默认值=false)<br/>
 TopologyManagerPolicyBetaOptions=true|false (BETA - 默认值=false)<br/>
 TopologyManagerPolicyOptions=true|false (ALPHA - 默认值=false)<br/>
 UserNamespacesStatelessPodsSupport=true|false (ALPHA - 默认值=false)<br/>
 ValidatingAdmissionPolicy=true|false (ALPHA - 默认值=false)<br/>
 VolumeCapacityPriority=true|false (ALPHA - 默认值=false)<br/>
+WatchList=true|false (ALPHA - 默认值=false)<br/>
 WinDSR=true|false (ALPHA - 默认值=false)<br/>
 WinOverlay=true|false (BETA - 默认值=true)<br/>
 WindowsHostNetwork=true|false (ALPHA - 默认值=true)
@@ -2214,6 +2240,18 @@ in addition 'Connection: close' response header is set in order to tear down the
 </td>
 </tr>
 
+<tr>
+<td colspan="2">--shutdown-watch-termination-grace-period duration</td>
+</tr>
+<tr>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>
+<!--
+This option, if set, represents the maximum amount of grace period the apiserver will wait for active watch request(s) to drain during the graceful server shutdown window.
+-->
+此选项如果被设置了，则表示 API 服务器体面关闭服务器窗口内，等待活跃的监听请求耗尽的最长宽限期。
+</p></td>
+</tr>
+
 <tr>
 <td colspan="2">--storage-backend string</td>
 </tr>

From b672cea482f2546ccaadb13ab01ff4ae9eeeedd7 Mon Sep 17 00:00:00 2001
From: Zhuzhenghao <zhenghao.zhu@daocloud.io>
Date: Thu, 13 Apr 2023 15:27:13 +0800
Subject: [PATCH 267/272] [zh] resync page extensible-admission-controllers

---
 .../extensible-admission-controllers.md       | 424 ++++++++++--------
 1 file changed, 233 insertions(+), 191 deletions(-)

diff --git a/content/zh-cn/docs/reference/access-authn-authz/extensible-admission-controllers.md b/content/zh-cn/docs/reference/access-authn-authz/extensible-admission-controllers.md
index 7b29c76a347..7beaa90ee91 100644
--- a/content/zh-cn/docs/reference/access-authn-authz/extensible-admission-controllers.md
+++ b/content/zh-cn/docs/reference/access-authn-authz/extensible-admission-controllers.md
@@ -3,8 +3,14 @@ title: 动态准入控制
 content_type: concept
 weight: 40
 ---
-
 <!--
+reviewers:
+- smarterclayton
+- lavalamp
+- caesarxuchao
+- deads2k
+- liggitt
+- jpbetz
 title: Dynamic Admission Control
 content_type: concept
 weight: 40
@@ -21,6 +27,7 @@ This page describes how to build, configure, use, and monitor admission webhooks
 此页面描述了如何构建、配置、使用和监视准入 Webhook。
 
 <!-- body -->
+
 <!--
 ## What are admission webhooks?
 -->
@@ -29,16 +36,16 @@ This page describes how to build, configure, use, and monitor admission webhooks
 <!--
 Admission webhooks are HTTP callbacks that receive admission requests and do
 something with them. You can define two types of admission webhooks,
-[validating admission Webhook](/docs/reference/access-authn-authz/admission-controllers/#validatingadmissionwebhook)
+[validating admission webhook](/docs/reference/access-authn-authz/admission-controllers/#validatingadmissionwebhook)
 and
 [mutating admission webhook](/docs/reference/access-authn-authz/admission-controllers/#mutatingadmissionwebhook).
-Mutating admission Webhooks are invoked first, and can modify objects sent to the API server to enforce custom defaults.
+Mutating admission webhooks are invoked first, and can modify objects sent to the API server to enforce custom defaults.
 -->
 准入 Webhook 是一种用于接收准入请求并对其进行处理的 HTTP 回调机制。
 可以定义两种类型的准入 webhook，即
 [验证性质的准入 Webhook](/zh-cn/docs/reference/access-authn-authz/admission-controllers/#validatingadmissionwebhook) 和
 [修改性质的准入 Webhook](/zh-cn/docs/reference/access-authn-authz/admission-controllers/#mutatingadmissionwebhook)。
-修改性质的准入 Webhook 会先被调用。它们可以更改发送到 API 
+修改性质的准入 Webhook 会先被调用。它们可以更改发送到 API
 服务器的对象以执行自定义的设置默认值操作。
 
 <!--
@@ -48,24 +55,25 @@ validating admission webhooks are invoked and can reject requests to enforce cus
 在完成了所有对象修改并且 API 服务器也验证了所传入的对象之后，
 验证性质的 Webhook 会被调用，并通过拒绝请求的方式来强制实施自定义的策略。
 
+{{< note >}}
 <!--
 Admission webhooks that need to guarantee they see the final state of the object in order to enforce policy
 should use a validating admission webhook, since objects can be modified after being seen by mutating webhooks.
 -->
-{{< note >}}
 如果准入 Webhook 需要保证它们所看到的是对象的最终状态以实施某种策略。
 则应使用验证性质的准入 Webhook，因为对象被修改性质 Webhook 看到之后仍然可能被修改。
 {{< /note >}}
 
 <!--
-### Experimenting with admission webhooks
+## Experimenting with admission webhooks
 
-write and deploy them with great caution. Please read the [user
-guides](/docs/reference/access-authn-authz/extensible-admission-controllers/#write-an-admission-webhook-server) for
-instructions if you intend to write/deploy production-grade admission webhooks.
+Admission webhooks are essentially part of the cluster control-plane. You should
+write and deploy them with great caution. Please read the
+[user guides](/docs/reference/access-authn-authz/extensible-admission-controllers/#write-an-admission-webhook-server)
+for instructions if you intend to write/deploy production-grade admission webhooks.
 In the following, we describe how to quickly experiment with admission webhooks.
 -->
-### 尝试准入 Webhook {#experimenting-with-admission-webhooks}
+## 尝试准入 Webhook {#experimenting-with-admission-webhooks}
 
 准入 Webhook 本质上是集群控制平面的一部分。你应该非常谨慎地编写和部署它们。
 如果你打算编写或者部署生产级准入 webhook，请阅读[用户指南](/zh-cn/docs/reference/access-authn-authz/extensible-admission-controllers/#write-an-admission-webhook-server)以获取相关说明。
@@ -101,19 +109,19 @@ that is validated in a Kubernetes e2e test. The webhook handles the
 as an `AdmissionReview` object in the same version it received.
 -->
 请参阅 Kubernetes e2e 测试中的
-[admission webhook 服务器](https://github.com/kubernetes/kubernetes/blob/release-1.21/test/images/agnhost/webhook/main.go)
+[Admission Webhook 服务器](https://github.com/kubernetes/kubernetes/blob/release-1.21/test/images/agnhost/webhook/main.go)
 的实现。webhook 处理由 API 服务器发送的 `AdmissionReview` 请求，并且将其决定
 作为 `AdmissionReview` 对象以相同版本发送回去。
 
 <!--
 See the [webhook request](#request) section for details on the data sent to webhooks.
 -->
-有关发送到 webhook 的数据的详细信息，请参阅 [webhook 请求](#request)。
+有关发送到 Webhook 的数据的详细信息，请参阅 [Webhook 请求](#request)。
 
 <!--
 See the [webhook response](#response) section for the data expected from webhooks.
 -->
-要获取来自 webhook 的预期数据，请参阅 [webhook 响应](#response)。
+要获取来自 Webhook 的预期数据，请参阅 [Webhook 响应](#response)。
 
 <!--
 The example admission webhook server leaves the `ClientAuth` field
@@ -125,7 +133,7 @@ how to [authenticate API servers](#authenticate-apiservers).
 -->
 示例准入 Webhook 服务器置 `ClientAuth` 字段为
 [空](https://github.com/kubernetes/kubernetes/blob/v1.22.0/test/images/agnhost/webhook/config.go#L38-L39)，
-默认为 `NoClientCert` 。这意味着 webhook 服务器不会验证客户端的身份，认为其是 apiservers。
+默认为 `NoClientCert` 。这意味着 Webhook 服务器不会验证客户端的身份，认为其是 apiservers。
 如果你需要双向 TLS 或其他方式来验证客户端，请参阅
 如何[对 apiservers 进行身份认证](#authenticate-apiservers)。
 
@@ -141,18 +149,18 @@ The test also creates a [service](/docs/reference/generated/kubernetes-api/{{< p
 as the front-end of the webhook server. See
 [code](https://github.com/kubernetes/kubernetes/blob/v1.22.0/test/e2e/apimachinery/webhook.go#L748).
 -->
-e2e 测试中的 webhook 服务器通过
+e2e 测试中的 Webhook 服务器通过
 [deployment API](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#deployment-v1-apps)
 部署在 Kubernetes 集群中。该测试还将创建一个
 [service](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#service-v1-core)
-作为 webhook 服务器的前端。参见
+作为 Webhook 服务器的前端。参见
 [相关代码](https://github.com/kubernetes/kubernetes/blob/v1.22.0/test/e2e/apimachinery/webhook.go#L748)。
 
 <!--
 You may also deploy your webhooks outside of the cluster. You will need to update
 your webhook configurations accordingly.
 -->
-你也可以在集群外部署 webhook。这样做需要相应地更新你的 webhook 配置。
+你也可以在集群外部署 Webhook。这样做需要相应地更新你的 Webhook 配置。
 
 <!--
 ### Configure admission webhooks on the fly
@@ -166,15 +174,16 @@ webhooks via
 or
 [MutatingWebhookConfiguration](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io).
 -->
-你可以通过 
+你可以通过
 [ValidatingWebhookConfiguration](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#validatingwebhookconfiguration-v1-admissionregistration-k8s-io)
-或者 
+或者
 [MutatingWebhookConfiguration](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io) 动态配置哪些资源要被哪些准入 Webhook 处理。
+
 <!--
 The following is an example `ValidatingWebhookConfiguration`, a mutating webhook configuration is similar.
 See the [webhook configuration](#webhook-configuration) section for details about each config field.
 -->
-以下是一个 `ValidatingWebhookConfiguration` 示例，mutating webhook 配置与此类似。有关每个配置字段的详细信息，请参阅 [webhook 配置](#webhook-configuration) 部分。
+以下是一个 `ValidatingWebhookConfiguration` 示例，Mutating Webhook 配置与此类似。有关每个配置字段的详细信息，请参阅 [Webhook 配置](#webhook-configuration) 部分。
 
 ```yaml
 apiVersion: admissionregistration.k8s.io/v1
@@ -184,11 +193,11 @@ metadata:
 webhooks:
 - name: "pod-policy.example.com"
   rules:
-  - apiGroups:   [""]
+  - apiGroups: [""]
     apiVersions: ["v1"]
-    operations:  ["CREATE"]
-    resources:   ["pods"]
-    scope:       "Namespaced"
+    operations: ["CREATE"]
+    resources: ["pods"]
+    scope: "Namespaced"
   clientConfig:
     service:
       namespace: "example-namespace"
@@ -198,6 +207,7 @@ webhooks:
   sideEffects: None
   timeoutSeconds: 5
 ```
+
 {{< note >}}
 <!-- 
 You must replace the `<CA_BUNDLE>` in the above example by a valid CA bundle
@@ -207,30 +217,30 @@ which is a PEM-encoded CA bundle for validating the webhook's server certificate
 这是一个用 PEM 编码的 CA 证书包，用于校验 Webhook 的服务器证书。
 {{< /note >}}
 
-<!-- 
+<!--
 The `scope` field specifies if only cluster-scoped resources ("Cluster") or namespace-scoped
 resources ("Namespaced") will match this rule. "&lowast;" means that there are no scope restrictions.
 -->
 `scope` 字段指定是仅集群范围的资源（Cluster）还是名字空间范围的资源资源（Namespaced）将与此规则匹配。
 `*` 表示没有范围限制。
 
+{{< note >}}
 <!--
 When using `clientConfig.service`, the server cert must be valid for
 `<svc_name>.<svc_namespace>.svc`.
 -->
-{{< note >}}
 当使用 `clientConfig.service` 时，服务器证书必须对 `<svc_name>.<svc_namespace>.svc` 有效。
 {{< /note >}}
 
+{{< note >}}
 <!--
 Default timeout for a webhook call is 10 seconds,
 You can set the `timeout` and it is encouraged to use a short timeout for webhooks.
 If the webhook call times out, the request is handled according to the webhook's
 failure policy.
 -->
-{{< note >}}
-Webhook 调用的默认超时是 10 秒，你可以设置 `timeout` 并建议对 webhook 设置较短的超时时间。
-如果 webhook 调用超时，则根据 webhook 的失败策略处理请求。
+Webhook 调用的默认超时是 10 秒，你可以设置 `timeout` 并建议对 Webhook 设置较短的超时时间。
+如果 Webhook 调用超时，则根据 Webhook 的失败策略处理请求。
 {{< /note >}}
 
 <!--
@@ -242,12 +252,12 @@ After you create the webhook configuration, the system will take a few seconds
 to honor the new configuration.
 -->
 当一个 API 服务器收到与 `rules` 相匹配的请求时，
-该 API 服务器将按照 `clientConfig` 中指定的方式向 webhook 发送一个 `admissionReview` 请求。
+该 API 服务器将按照 `clientConfig` 中指定的方式向 Webhook 发送一个 `admissionReview` 请求。
 
 创建 Webhook 配置后，系统将花费几秒钟使新配置生效。
 
 <!--
-### Authenticate API servers
+### Authenticate API servers   {#authenticate-apiservers}
 -->
 ### 对 API 服务器进行身份认证 {#authenticate-apiservers}
 
@@ -322,71 +332,74 @@ For more information about `AdmissionConfiguration`, see the
 [AdmissionConfiguration (v1) reference](/docs/reference/config-api/apiserver-webhookadmission.v1/).
 See the [webhook configuration](#webhook-configuration) section for details about each config field.
 
-* In the kubeConfig file, provide the credentials:
+In the kubeConfig file, provide the credentials:
 -->
 有关 `AdmissionConfiguration` 的更多信息，请参见
 [AdmissionConfiguration (v1) reference](/docs/reference/config-api/apiserver-webhookadmission.v1/)。
-有关每个配置字段的详细信息，请参见 [webhook 配置](#webhook-配置)部分。
+有关每个配置字段的详细信息，请参见 [Webhook 配置](#webhook-配置)部分。
 
-* 在 kubeConfig 文件中，提供证书凭据：
+在 kubeConfig 文件中，提供证书凭据：
+
+```yaml
+apiVersion: v1
+kind: Config
+users:
+# 名称应设置为服务的 DNS 名称或配置了 Webhook 的 URL 的主机名（包括端口）。
+# 如果将非 443 端口用于服务，则在配置 1.16+ API 服务器时，该端口必须包含在名称中。
+#
+# 对于配置在默认端口（443）上与服务对话的 Webhook，请指定服务的 DNS 名称：
+# - name: webhook1.ns1.svc
+#   user: ...
+#
+# 对于配置在非默认端口（例如 8443）上与服务对话的 Webhook，请在 1.16+ 中指定服务的 DNS 名称和端口：
+# - name: webhook1.ns1.svc:8443
+#   user: ...
+# 并可以选择仅使用服务的 DNS 名称来创建第二节，以与 1.15 API 服务器版本兼容：
+# - name: webhook1.ns1.svc
+#   user: ...
+#
+# 对于配置为使用 URL 的 webhook，请匹配在 webhook 的 URL 中指定的主机（和端口）。
+# 带有 `url: https://www.example.com` 的 webhook：
+# - name: www.example.com
+#   user: ...
+#
+# 带有 `url: https://www.example.com:443` 的 webhook：
+# - name: www.example.com:443
+#   user: ...
+#
+# 带有 `url: https://www.example.com:8443` 的 webhook：
+# - name: www.example.com:8443
+#   user: ...
+#
+- name: 'webhook1.ns1.svc'
+  user:
+    client-certificate-data: "<pem encoded certificate>"
+    client-key-data: "<pem encoded key>"
+# `name` 支持使用 * 通配符匹配前缀段。
+- name: '*.webhook-company.org'
+  user:
+    password: "<password>"
+    username: "<name>"
+# '*' 是默认匹配项。
+- name: '*'
+  user:
+    token: "<token>"
+```
 
-    ```yaml
-    apiVersion: v1
-    kind: Config
-    users:
-    # 名称应设置为服务的 DNS 名称或配置了 Webhook 的 URL 的主机名（包括端口）。
-    # 如果将非 443 端口用于服务，则在配置 1.16+ API 服务器时，该端口必须包含在名称中。
-    #
-    # 对于配置在默认端口（443）上与服务对话的 Webhook，请指定服务的 DNS 名称：
-    # - name: webhook1.ns1.svc
-    #   user: ...
-    #
-    # 对于配置在非默认端口（例如 8443）上与服务对话的 Webhook，请在 1.16+ 中指定服务的 DNS 名称和端口：
-    # - name: webhook1.ns1.svc:8443
-    #   user: ...
-    # 并可以选择仅使用服务的 DNS 名称来创建第二节，以与 1.15 API 服务器版本兼容：
-    # - name: webhook1.ns1.svc
-    #   user: ...
-    #
-    # 对于配置为使用 URL 的 webhook，请匹配在 webhook 的 URL 中指定的主机（和端口）。
-    # 带有 `url: https://www.example.com` 的 webhook：
-    # - name: www.example.com
-    #   user: ...
-    #
-    # 带有 `url: https://www.example.com:443` 的 webhook：
-    # - name: www.example.com:443
-    #   user: ...
-    #
-    # 带有 `url: https://www.example.com:8443` 的 webhook：
-    # - name: www.example.com:8443
-    #   user: ...
-    #
-    - name: 'webhook1.ns1.svc'
-      user:
-        client-certificate-data: "<pem encoded certificate>"
-        client-key-data: "<pem encoded key>"
-    # `name` 支持使用 * 通配符匹配前缀段。
-    - name: '*.webhook-company.org'
-      user:
-        password: "<password>"
-        username: "<name>"
-    # '*' 是默认匹配项。
-    - name: '*'
-      user:
-        token: "<token>"
-    ```
 <!--
 Of course you need to set up the webhook server to handle these authentication requests.
 -->
 当然，你需要设置 Webhook 服务器来处理这些身份验证请求。
 
-<!-- ## Webhook request and response -->
+<!--
+## Webhook request and response
+-->
 ## Webhook 请求与响应 {#webhook-request-and-response}
 
 <!--
 ### Request
 
-Webhooks are sent as POST request, with `Content-Type: application/json`,
+Webhooks are sent as POST requests, with `Content-Type: application/json`,
 with an `AdmissionReview` API object in the `admission.k8s.io` API group
 serialized to JSON as the body.
 
@@ -396,7 +409,8 @@ with the `admissionReviewVersions` field in their configuration:
 
 ### 请求 {#request}
 
-Webhook 发送 POST 请求时，请设置 `Content-Type: application/json` 并对 `admission.k8s.io`  API 组中的 `AdmissionReview` 对象进行序列化，将所得到的 JSON 作为请求的主体。
+Webhook 发送 POST 请求时，请设置 `Content-Type: application/json` 并对 `admission.k8s.io` API
+组中的 `AdmissionReview` 对象进行序列化，将所得到的 JSON 作为请求的主体。
 
 Webhook 可以在配置中的 `admissionReviewVersions` 字段指定可接受的 `AdmissionReview` 对象版本：
 
@@ -414,7 +428,7 @@ webhooks:
 Webhooks are required to support at least one `AdmissionReview`
 version understood by the current and previous API server.
 -->
-创建 webhook 配置时，`admissionReviewVersions` 是必填字段。
+创建 Webhook 配置时，`admissionReviewVersions` 是必填字段。
 Webhook 必须支持至少一个当前和以前的 API 服务器都可以解析的 `AdmissionReview` 版本。
 
 <!--
@@ -455,24 +469,24 @@ request:
   subResource: scale
 
   # 在对 API 服务器的原始请求中，传入对象的标准 group/version/kind
-  # 仅当 webhook 指定 `matchPolicy: Equivalent` 且将对 API 服务器的原始请求
-  # 转换为 webhook 注册的版本时，这才与 `kind` 不同。
+  # 仅当 Webhook 指定 `matchPolicy: Equivalent` 且将对 API 服务器的原始请求
+  # 转换为 Webhook 注册的版本时，这才与 `kind` 不同。
   requestKind:
     group: autoscaling
     version: v1
     kind: Scale
 
   # 在对 API 服务器的原始请求中正在修改的资源的标准 group/version/kind
-  # 仅当 webhook 指定了 `matchPolicy：Equivalent` 并且将对 API 服务器的原始请求转换为
-  # webhook 注册的版本时，这才与 `resource` 不同。
+  # 仅当 Webhook 指定了 `matchPolicy：Equivalent` 并且将对 API 服务器的原始请求转换为
+  # Webhook 注册的版本时，这才与 `resource` 不同。
   requestResource:
     group: apps
     version: v1
     resource: deployments
 
   # subResource（如果请求是针对 subResource 的）
-  # 仅当 webhook 指定了 `matchPolicy：Equivalent` 并且将对
-  # API 服务器的原始请求转换为该 webhook 注册的版本时，这才与 `subResource` 不同。
+  # 仅当 Webhook 指定了 `matchPolicy：Equivalent` 并且将对
+  # API 服务器的原始请求转换为该 Webhook 注册的版本时，这才与 `subResource` 不同。
   requestSubResource: scale
 
   # 被修改资源的名称
@@ -585,9 +599,10 @@ Webhook 禁止请求的最简单响应示例：
 ```
 
 <!--
-When rejecting a request, the webhook can customize the http code and message returned to the user using the `status` field. 
-The specified status object is returned to the user.
-See the [API documentation](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#status-v1-meta) for details about the `status` type.
+When rejecting a request, the webhook can customize the http code and message returned to the user
+using the `status` field. The specified status object is returned to the user.
+See the [API documentation](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#status-v1-meta)
+for details about the `status` type.
 Example of a response to forbid a request, customizing the HTTP status code and message presented to the user:
 -->
 当拒绝请求时，Webhook 可以使用 `status` 字段自定义 http 响应码和返回给用户的消息。
@@ -624,7 +639,8 @@ For `patchType: JSONPatch`, the `patch` field contains a base64-encoded array of
 对于 `patchType: JSONPatch`，`patch` 字段包含一个以 base64 编码的 JSON patch 操作数组。
 
 <!--
-As an example, a single patch operation that would set `spec.replicas` would be `[{"op": "add", "path": "/spec/replicas", "value": 3}]`
+As an example, a single patch operation that would set `spec.replicas` would be
+`[{"op": "add", "path": "/spec/replicas", "value": 3}]`
 
 Base64-encoded, this would be `W3sib3AiOiAiYWRkIiwgInBhdGgiOiAiL3NwZWMvcmVwbGljYXMiLCAidmFsdWUiOiAzfV0=`
 -->
@@ -652,18 +668,19 @@ So a webhook response to add that label would be:
 }
 ```
 
-<!-- 
-Admission webhooks can optionally return warning messages that are returned to the requesting client in HTTP `Warning` headers with a warning code of 299. Warnings can be sent with allowed or rejected admission responses. 
+<!--
+Admission webhooks can optionally return warning messages that are returned to the requesting client
+in HTTP `Warning` headers with a warning code of 299. Warnings can be sent with allowed or rejected admission responses.
 -->
 准入 Webhook 可以选择性地返回在 HTTP `Warning` 头中返回给请求客户端的警告消息，警告代码为 299。
 警告可以与允许或拒绝的准入响应一起发送。
 
-<!-- 
+<!--
 If you're implementing a webhook that returns a warning:
 
 * Don't include a "Warning:" prefix in the message
 * Use warning messages to describe problems the client making the API request should correct or be aware of
-* Limit warnings to 120 characters if possible 
+* Limit warnings to 120 characters if possible
 -->
 如果你正在实现返回一条警告的 webhook，则：
 
@@ -674,7 +691,7 @@ If you're implementing a webhook that returns a warning:
 {{< caution >}}
 <!-- 
 Individual warning messages over 256 characters may be truncated by the API server before being returned to clients.
-If more than 4096 characters of warning messages are added (from all sources), additional warning messages are ignored. 
+If more than 4096 characters of warning messages are added (from all sources), additional warning messages are ignored.
 -->
 超过 256 个字符的单条警告消息在返回给客户之前可能会被 API 服务器截断。
 如果超过 4096 个字符的警告消息（来自所有来源），则额外的警告消息会被忽略。
@@ -731,37 +748,44 @@ Webhook，则应为每个 Webhook 赋予一个唯一的名称。
 Each webhook must specify a list of rules used to determine if a request to the API server should be sent to the webhook.
 Each rule specifies one or more operations, apiGroups, apiVersions, and resources, and a resource scope:
 -->
-每个 webhook 必须指定用于确定是否应将对 apiserver 的请求发送到 webhook 的规则列表。
+每个 Webhook 必须指定用于确定是否应将对 apiserver 的请求发送到 webhook 的规则列表。
 每个规则都指定一个或多个 operations、apiGroups、apiVersions 和 resources 以及资源的 scope：
 
 <!--
-* `operations` lists one or more operations to match. Can be `"CREATE"`, `"UPDATE"`, `"DELETE"`, `"CONNECT"`, or `"*"` to match all.
+* `operations` lists one or more operations to match. Can be `"CREATE"`, `"UPDATE"`, `"DELETE"`, `"CONNECT"`,
+  or `"*"` to match all.
 * `apiGroups` lists one or more API groups to match. `""` is the core API group. `"*"` matches all API groups.
 * `apiVersions` lists one or more API versions to match. `"*"` matches all API versions.
 * `resources` lists one or more resources to match.
-    * `"*"` matches all resources, but not subresources.
-    * `"*/*"` matches all resources and subresources.
-    * `"pods/*"` matches all subresources of pods.
-    * `"*/status"` matches all status subresources.
-* `scope` specifies a scope to match. Valid values are `"Cluster"`, `"Namespaced"`, and `"*"`. Subresources match the scope of their parent resource. Default is `"*"`.
-    * `"Cluster"` means that only cluster-scoped resources will match this rule (Namespace API objects are cluster-scoped).
-    * `"Namespaced"` means that only namespaced resources will match this rule.
-    * `"*"` means that there are no scope restrictions.
+
+  * `"*"` matches all resources, but not subresources.
+  * `"*/*"` matches all resources and subresources.
+  * `"pods/*"` matches all subresources of pods.
+  * `"*/status"` matches all status subresources.
+
+* `scope` specifies a scope to match. Valid values are `"Cluster"`, `"Namespaced"`, and `"*"`.
+  Subresources match the scope of their parent resource. Default is `"*"`.
+
+  * `"Cluster"` means that only cluster-scoped resources will match this rule (Namespace API objects are cluster-scoped).
+  * `"Namespaced"` means that only namespaced resources will match this rule.
+  * `"*"` means that there are no scope restrictions.
 -->
 * `operations` 列出一个或多个要匹配的操作。
   可以是 `CREATE`、`UPDATE`、`DELETE`、`CONNECT` 或 `*` 以匹配所有内容。
 * `apiGroups` 列出了一个或多个要匹配的 API 组。`""` 是核心 API 组。`"*"` 匹配所有 API 组。
 * `apiVersions` 列出了一个或多个要匹配的 API 版本。`"*"` 匹配所有 API 版本。
 * `resources` 列出了一个或多个要匹配的资源。
-    * `"*"` 匹配所有资源，但不包括子资源。
-    * `"*/*"` 匹配所有资源，包括子资源。
-    * `"pods/*"` 匹配 pod 的所有子资源。
-    * `"*/status"` 匹配所有 status 子资源。
+
+  * `"*"` 匹配所有资源，但不包括子资源。
+  * `"*/*"` 匹配所有资源，包括子资源。
+  * `"pods/*"` 匹配 pod 的所有子资源。
+  * `"*/status"` 匹配所有 status 子资源。
 * `scope` 指定要匹配的范围。有效值为 `"Cluster"`、`"Namespaced"` 和 `"*"`。
   子资源匹配其父资源的范围。默认值为 `"*"`。
-    * `"Cluster"` 表示只有集群作用域的资源才能匹配此规则（API 对象 Namespace 是集群作用域的）。
-    * `"Namespaced"` 意味着仅具有名字空间的资源才符合此规则。
-    * `"*"` 表示没有作用域限制。
+
+  * `"Cluster"` 表示只有集群作用域的资源才能匹配此规则（API 对象 Namespace 是集群作用域的）。
+  * `"Namespaced"` 意味着仅具有名字空间的资源才符合此规则。
+  * `"*"` 表示没有作用域限制。
 
 <!--
 If an incoming request matches one of the specified `operations`, `groups`, `versions`,
@@ -855,9 +879,10 @@ 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.
+Use the object selector only if the webhook is opt-in, because end users may skip
+the admission webhook by setting the labels.
 -->
-仅当选择使用 webhook 时才使用对象选择器，因为最终用户可以通过设置标签来
+仅当选择使用 Webhook 时才使用对象选择器，因为最终用户可以通过设置标签来
 跳过准入 Webhook。
 
 <!--
@@ -926,7 +951,7 @@ webhooks:
       matchExpressions:
         - key: runlevel
           operator: NotIn
-          values: ["0","1"]
+          values: ["0", "1"]
     rules:
       - operations: ["CREATE"]
         apiGroups: ["*"]
@@ -936,8 +961,8 @@ webhooks:
 ```
 
 <!--
-This example shows a validating webhook that matches a `CREATE` of any namespaced resource inside a namespace
-that is associated with the "environment" of "prod" or "staging":
+This example shows a validating webhook that matches a `CREATE` of any namespaced resource inside
+a namespace that is associated with the "environment" of "prod" or "staging":
 -->
 此示例显示了一个验证性质的 Webhook，它将匹配到对某名字空间中的任何具名字空间的资源的
 `CREATE` 请求，前提是该名字空间具有值为 "prod" 或 "staging" 的 "environment" 标签：
@@ -951,7 +976,7 @@ webhooks:
       matchExpressions:
         - key: environment
           operator: In
-          values: ["prod","staging"]
+          values: ["prod", "staging"]
     rules:
       - operations: ["CREATE"]
         apiGroups: ["*"]
@@ -983,7 +1008,7 @@ For example, if a webhook only specified a rule for some API groups/versions
 and a request was made to modify the resource via another API group/version (like `extensions/v1beta1`),
 the request would not be sent to the webhook.
 -->
-例如，如果一个 webhook 仅为某些 API 组/版本指定了规则（例如
+例如，如果一个 Webhook 仅为某些 API 组/版本指定了规则（例如
 `apiGroups:["apps"], apiVersions:["v1","v1beta1"]`），而修改资源的请求是通过另一个
 API 组/版本（例如 `extensions/v1beta1`）发出的，该请求将不会被发送到 Webhook。
 
@@ -991,25 +1016,28 @@ API 组/版本（例如 `extensions/v1beta1`）发出的，该请求将不会被
 The `matchPolicy` lets a webhook define how its `rules` are used to match incoming requests.
 Allowed values are `Exact` or `Equivalent`.
 -->
-`matchPolicy` 允许 webhook 定义如何使用其 `rules` 匹配传入的请求。
+`matchPolicy` 允许 Webhook 定义如何使用其 `rules` 匹配传入的请求。
 允许的值为 `Exact` 或 `Equivalent`。
 
 <!--
 * `Exact` means a request should be intercepted only if it exactly matches a specified rule.
-* `Equivalent` means a request should be intercepted if modifies a resource listed in `rules`, even via another API group or version.
+* `Equivalent` means a request should be intercepted if modifies a resource listed in `rules`,
+  even via another API group or version.
 
 In the example given above, the webhook that only registered for `apps/v1` could use `matchPolicy`:
+
 * `matchPolicy: Exact` would mean the `extensions/v1beta1` request would not be sent to the webhook
-* `matchPolicy: Equivalent` means the `extensions/v1beta1` request would be sent to the webhook (with the objects converted to a version the webhook had specified: `apps/v1`)
+* `matchPolicy: Equivalent` means the `extensions/v1beta1` request would be sent to the webhook
+  (with the objects converted to a version the webhook had specified: `apps/v1`)
 -->
 * `Exact` 表示仅当请求与指定规则完全匹配时才应拦截该请求。
 * `Equivalent` 表示如果某个请求意在修改 `rules` 中列出的资源，
   即使该请求是通过其他 API 组或版本发起，也应拦截该请求。
 
-在上面给出的示例中，仅为 `apps/v1` 注册的 webhook 可以使用 `matchPolicy`：
+在上面给出的示例中，仅为 `apps/v1` 注册的 Webhook 可以使用 `matchPolicy`：
 * `matchPolicy: Exact` 表示不会将 `extensions/v1beta1` 请求发送到 Webhook
-* `matchPolicy:Equivalent` 表示将 `extensions/v1beta1` 请求发送到 webhook
-  （将对象转换为 webhook 指定的版本：`apps/v1`）
+* `matchPolicy:Equivalent` 表示将 `extensions/v1beta1` 请求发送到 Webhook
+  （将对象转换为 Webhook 指定的版本：`apps/v1`）
 
 <!--
 Specifying `Equivalent` is recommended, and ensures that webhooks continue to intercept the
@@ -1019,7 +1047,8 @@ resources they expect when upgrades enable new versions of the resource in the A
 Webhook 继续拦截他们期望的资源。
 
 <!--
-When a resource stops being served by the API server, it is no longer considered equivalent to other versions of that resource that are still served.
+When a resource stops being served by the API server, it is no longer considered equivalent to
+other versions of that resource that are still served.
 For example, `extensions/v1beta1` deployments were first deprecated and then removed (in Kubernetes v1.16).
 
 Since that removal, a webhook with a `apiGroups:["extensions"], apiVersions:["v1beta1"], resources:["deployments"]` rule
@@ -1029,7 +1058,7 @@ for stable versions of resources.
 当 API 服务器停止提供某资源时，该资源不再被视为等同于该资源的其他仍在提供服务的版本。
 例如，`extensions/v1beta1` 中的 Deployment 已被废弃，计划在 v1.16 中移除。
 
-移除后，带有 `apiGroups:["extensions"], apiVersions:["v1beta1"], resources: ["deployments"]` 
+移除后，带有 `apiGroups:["extensions"], apiVersions:["v1beta1"], resources: ["deployments"]`
 规则的 Webhook 将不再拦截通过 `apps/v1` API 来创建的 Deployment。
 因此，Webhook 应该优先注册稳定版本的资源。
 
@@ -1054,8 +1083,8 @@ webhooks:
     scope: "Namespaced"
 ```
 
-<!-- 
-The `matchPolicy` for an admission webhooks defaults to `Equivalent`. 
+<!--
+The `matchPolicy` for an admission webhooks defaults to `Equivalent`.
 -->
 准入 Webhook 所用的 `matchPolicy` 默认为 `Equivalent`。
 
@@ -1144,7 +1173,7 @@ webhooks:
         expression: '!authorizer.group("admissionregistration.k8s.io").resource("validatingwebhookconfigurations").name("my-webhook.example.com").check("breakglass").allowed()'
 ```
 
-<!-- 
+<!--
 Match conditions have access to the following CEL variables:
 -->
 匹配条件可以访问以下 CEL 变量：
@@ -1217,8 +1246,8 @@ stanza of the webhook configuration.
 Webhooks can either be called via a URL or a service reference,
 and can optionally include a custom CA bundle to use to verify the TLS connection.
 -->
-API 服务器确定请求应发送到 webhook 后，它需要知道如何调用 webhook。
-此信息在 webhook 配置的 `clientConfig` 节中指定。
+API 服务器确定请求应发送到 Webhook 后，它需要知道如何调用 webhook。
+此信息在 Webhook 配置的 `clientConfig` 节中指定。
 
 Webhook 可以通过 URL 或服务引用来调用，并且可以选择包含自定义 CA 包，以用于验证 TLS 连接。
 
@@ -1231,7 +1260,7 @@ Webhook 可以通过 URL 或服务引用来调用，并且可以选择包含自
 `url` gives the location of the webhook, in standard URL form
 (`scheme://host:port/path`).
 -->
-`url` 以标准 URL 形式给出 webhook 的位置（`scheme://host:port/path`）。
+`url` 以标准 URL 形式给出 Webhook 的位置（`scheme://host:port/path`）。
 
 <!--
 The `host` should not refer to a service running in the cluster; use
@@ -1247,12 +1276,12 @@ 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 installations are likely to be non-portable, i.e., not easy
-to turn up in a new cluster.
+which run an API server which might need to make calls to this
+webhook. Such installations are likely to be non-portable or not readily
+run in a new cluster.
 -->
 请注意，将 `localhost` 或 `127.0.0.1` 用作 `host` 是有风险的，
-除非你非常小心地在所有运行 apiserver 的、可能需要对此 webhook 
+除非你非常小心地在所有运行 apiserver 的、可能需要对此 Webhook
 进行调用的主机上运行。这样的安装方式可能不具有可移植性，即很难在新集群中启用。
 
 <!--
@@ -1261,8 +1290,8 @@ The scheme must be "https"; the URL must begin with "https://".
 scheme 必须为 "https"；URL 必须以 "https://" 开头。
 
 <!--
-Attempting to use a user or basic auth e.g. "user:password@" is not allowed.
-Fragments ("#...") and query parameters ("?...") are also not allowed.
+Attempting to use a user or basic auth (for example `user:password@`) is not allowed.
+Fragments (`#...`) and query parameters (`?...`) are also not allowed.
 -->
 使用用户或基本身份验证（例如："user:password@"）是不允许的。
 使用片段（"#..."）和查询参数（"?..."）也是不允许的。
@@ -1321,14 +1350,16 @@ webhooks:
       path: /my-path
       port: 1234
 ```
+
 {{< note >}}
 <!-- 
 You must replace the `<CA_BUNDLE>` in the above example by a valid CA bundle
-which is a PEM-encoded CA bundle for validating the webhook's server certificate. 
+which is a PEM-encoded CA bundle for validating the webhook's server certificate.
 -->
 你必须在以上示例中将 `<CA_BUNDLE>` 替换为一个有效的 VA 证书包，
 这是一个用 PEM 编码的 CA 证书包，用于校验 Webhook 的服务器证书。
 {{< /note >}}
+
 <!--
 ### Side effects
 -->
@@ -1342,7 +1373,7 @@ Webhook 通常仅对发送给他们的 `AdmissionReview` 内容进行操作。
 但是，某些 Webhook 在处理 admission 请求时会进行带外更改。
 
 <!--
-Webhooks that make out-of-band changes ("side effects") must also have a reconcilation mechanism
+Webhooks that make out-of-band changes ("side effects") must also have a reconciliation mechanism
 (like a controller) that periodically determines the actual state of the world, and adjusts
 the out-of-band data modified by the admission webhook to reflect reality.
 This is because a call to an admission webhook does not guarantee the admitted object will be persisted as is, or at all.
@@ -1372,16 +1403,16 @@ Webhooks indicate whether they have side effects using the `sideEffects` field i
   `dryRun: true` is sent to the webhook, the webhook will suppress the side effects (the webhook
   is `dryRun`-aware).
 -->
-Webhook 使用 webhook 配置中的 `sideEffects` 字段显示它们是否有副作用：
+Webhook 使用 Webhook 配置中的 `sideEffects` 字段显示它们是否有副作用：
 
-* `None`：调用 webhook 没有副作用。
-* `NoneOnDryRun`：调用 webhook 可能会有副作用，但是如果将带有 `dryRun: true`
-  属性的请求发送到 webhook，则 webhook 将抑制副作用（该 webhook 可识别 `dryRun`）。
+* `None`：调用 Webhook 没有副作用。
+* `NoneOnDryRun`：调用 Webhook 可能会有副作用，但是如果将带有 `dryRun: true`
+  属性的请求发送到 webhook，则 Webhook 将抑制副作用（该 Webhook 可识别 `dryRun`）。
 
 <!--
 Here is an example of a validating webhook indicating it has no side effects on `dryRun: true` requests:
 -->
-这是一个 validating webhook 的示例，表明它对 `dryRun: true` 请求没有副作用：
+这是一个 validating Webhook 的示例，表明它对 `dryRun: true` 请求没有副作用：
 
 ```yaml
 apiVersion: admissionregistration.k8s.io/v1
@@ -1427,8 +1458,8 @@ webhooks:
     timeoutSeconds: 2
 ```
 
-<!-- 
-The timeout for an admission webhook defaults to 10 seconds. 
+<!--
+The timeout for an admission webhook defaults to 10 seconds.
 -->
 准入 Webhook 所用的超时时间默认为 10 秒。
 
@@ -1464,9 +1495,9 @@ and mutating webhooks can specify a `reinvocationPolicy` to control whether they
 可以将 `reinvocationPolicy` 设置为 `Never` 或 `IfNeeded`。 默认为 `Never`。
 
 <!--
-* `Never`: the webhook must not be called more than once in a single admission evaluation
+* `Never`: the webhook must not be called more than once in a single admission evaluation.
 * `IfNeeded`: the webhook may be called again as part of the admission evaluation if the object
-being admitted is modified by other admission plugins after the initial webhook call.
+  being admitted is modified by other admission plugins after the initial webhook call.
 -->
 * `Never`: 在一次准入测试中，不得多次调用 Webhook。
 * `IfNeeded`: 如果在最初的 Webhook 调用之后被其他对象的插件修改了被接纳的对象，
@@ -1479,9 +1510,11 @@ The important elements to note are:
 
 <!--
 * 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.
+* 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 (recommended for webhooks with side-effects).
+* To validate an object after all mutations are guaranteed complete, use a validating admission
+  webhook instead (recommended for webhooks with side-effects).
 -->
 * 不能保证附加调用的次数恰好是一。
 * 如果其他调用导致对该对象的进一步修改，则不能保证再次调用 Webhook。
@@ -1490,7 +1523,8 @@ The important elements to note are:
   （推荐用于有副作用的 Webhook）。
 
 <!--
-Here is an example of a mutating webhook opting into being re-invoked if later admission plugins modify the object:
+Here is an example of a mutating webhook opting into being re-invoked if later admission plugins
+modify the object:
 -->
 这是一个修改性质的 Webhook 的示例，该 Webhook 在以后的准入插件修改对象时被重新调用：
 
@@ -1510,7 +1544,7 @@ in an object could already exist in the user-provided object, but it is essentia
 修改性质的 Webhook 必须具有[幂等](#idempotence)性，并且能够成功处理
 已被接纳并可能被修改的对象的修改性质的 Webhook。
 对于所有修改性质的准入 Webhook 都是如此，因为它们可以在对象中进行的
-任何更改可能已经存在于用户提供的对象中，但是对于选择重新调用的 webhook
+任何更改可能已经存在于用户提供的对象中，但是对于选择重新调用的 Webhook
 来说是必不可少的。
 
 <!--
@@ -1527,10 +1561,10 @@ are handled. Allowed values are `Ignore` or `Fail`.
 
 Here is a mutating webhook configured to reject an API request if errors are encountered calling the admission webhook:
 -->
-`failurePolicy` 定义了如何处理准入 webhook 中无法识别的错误和超时错误。允许的值为 `Ignore` 或 `Fail`。
+`failurePolicy` 定义了如何处理准入 Webhook 中无法识别的错误和超时错误。允许的值为 `Ignore` 或 `Fail`。
 
-* `Ignore` 表示调用 webhook 的错误将被忽略并且允许 API 请求继续。
-* `Fail` 表示调用 webhook 的错误导致准入失败并且 API 请求被拒绝。
+* `Ignore` 表示调用 Webhook 的错误将被忽略并且允许 API 请求继续。
+* `Fail` 表示调用 Webhook 的错误导致准入失败并且 API 请求被拒绝。
 
 这是一个修改性质的 webhook，配置为在调用准入 Webhook 遇到错误时拒绝 API 请求：
 
@@ -1542,8 +1576,8 @@ webhooks:
   failurePolicy: Fail
 ```
 
-<!-- 
-The default `failurePolicy` for an admission webhooks is `Fail`. 
+<!--
+The default `failurePolicy` for an admission webhooks is `Fail`.
 -->
 准入 Webhook 所用的默认 `failurePolicy` 是 `Fail`。
 
@@ -1560,14 +1594,13 @@ monitoring mechanisms help cluster admins to answer questions like:
 
 2. What change did the mutating webhook applied to the object?
 
-3. Which webhooks are frequently rejecting API requests? What's the reason for a
-   rejection?
+3. Which webhooks are frequently rejecting API requests? What's the reason for a rejection?
 -->
 API 服务器提供了监视准入 Webhook 行为的方法。这些监视机制可帮助集群管理员回答以下问题：
 
-1. 哪个修改性质的 webhook 改变了 API 请求中的对象？
+1. 哪个修改性质的 Webhook 改变了 API 请求中的对象？
 2. 修改性质的 Webhook 对对象做了哪些更改？
-3. 哪些 webhook 经常拒绝 API 请求？是什么原因拒绝？
+3. 哪些 Webhook 经常拒绝 API 请求？是什么原因拒绝？
 
 <!--
 ### Mutating webhook auditing annotations
@@ -1601,12 +1634,13 @@ The audit level of a event determines which annotations get recorded:
 
 <!--
 - At `Metadata` audit level or higher, an annotation with key
-  `mutation.webhook.admission.k8s.io/round_{round idx}_index_{order idx}` gets logged with JSON payload indicating
-  a webhook gets invoked for given request and whether it mutated the object or not.
+- At `Metadata` audit level or higher, an annotation with key
+  `mutation.webhook.admission.k8s.io/round_{round idx}_index_{order idx}` gets logged with JSON
+  payload indicating a webhook gets invoked for given request and whether it mutated the object or not.
 -->
 - 在 `Metadata` 或更高审计级别上，将使用 JSON 负载记录带有键名
-`mutation.webhook.admission.k8s.io/round_{round idx}_index_{order idx}` 的注解，
-该注解表示针对给定请求调用了 Webhook，以及该 Webhook 是否更改了对象。
+  `mutation.webhook.admission.k8s.io/round_{round idx}_index_{order idx}` 的注解，
+  该注解表示针对给定请求调用了 Webhook，以及该 Webhook 是否更改了对象。
 
   <!--
   For example, the following annotation gets recorded for a webhook being reinvoked. The webhook is
@@ -1741,7 +1775,7 @@ API 服务器从 `/metrics` 端点公开 Prometheus 指标，这些指标可用
 Sometimes it's useful to know which admission webhooks are frequently rejecting API requests, and the
 reason for a rejection.
 
-In v1.16+, kube-apiserver exposes a Prometheus counter metric recording admission webhook rejections. The
+The API server exposes a Prometheus counter metric recording admission webhook rejections. The
 metrics are labelled to identify the causes of webhook rejection(s):
 -->
 有时，了解哪些准入 Webhook 经常拒绝 API 请求以及拒绝的原因是很有用的。
@@ -1757,20 +1791,22 @@ metrics are labelled to identify the causes of webhook rejection(s):
 - `type`: the admission webhook type, can be one of `admit` and `validating`.
 - `error_type`: identifies if an error occurred during the webhook invocation
   that caused the rejection. Its value can be one of:
-   - `calling_webhook_error`: unrecognized errors or timeout errors from the admission webhook happened and the
-   webhook's [Failure policy](#failure-policy) is set to `Fail`.
-   - `no_error`: no error occurred. The webhook rejected the request with `allowed: false` in the admission
-   response. The metrics label `rejection_code` records the `.status.code` set in the admission response.
-   - `apiserver_internal_error`: an API server internal error happened.
+
+  - `calling_webhook_error`: unrecognized errors or timeout errors from the admission webhook happened and the
+    webhook's [Failure policy](#failure-policy) is set to `Fail`.
+  - `no_error`: no error occurred. The webhook rejected the request with `allowed: false` in the admission
+    response. The metrics label `rejection_code` records the `.status.code` set in the admission response.
+  - `apiserver_internal_error`: an API server internal error happened.
+
 - `rejection_code`: the HTTP status code set in the admission response when a
   webhook rejected a request.
 -->
 - `name`：拒绝请求 Webhook 的名称。
 - `operation`：请求的操作类型可以是 `CREATE`、`UPDATE`、`DELETE` 和 `CONNECT` 其中之一。
-- `type`：Admission webhook 类型，可以是 `admit` 和 `validating` 其中之一。
-- `error_type`：标识在 webhook 调用期间是否发生了错误并且导致了拒绝。其值可以是以下之一：
+- `type`：Admission Webhook 类型，可以是 `admit` 和 `validating` 其中之一。
+- `error_type`：标识在 Webhook 调用期间是否发生了错误并且导致了拒绝。其值可以是以下之一：
   - `calling_webhook_error`：发生了来自准入 Webhook 的无法识别的错误或超时错误，
-    并且 webhook 的 [失败策略](#failure-policy) 设置为 `Fail`。
+    并且 Webhook 的 [失败策略](#failure-policy) 设置为 `Fail`。
   - `no_error`：未发生错误。Webhook 在准入响应中以 `allowed: false` 值拒绝了请求。
     度量标签 `rejection_code` 记录了在准入响应中设置的 `.status.code`。
   - `apiserver_internal_error`：apiserver 发生内部错误。
@@ -1815,7 +1851,8 @@ the initial application.
 2. For a `CREATE` pod request, if the field `.spec.containers[].resources.limits`
    of a container is not set, set default resource limits.
 
-3. For a `CREATE` pod request, inject a sidecar container with name `foo-sidecar` if no container with the name `foo-sidecar` already exists.
+3. For a `CREATE` pod request, inject a sidecar container with name `foo-sidecar` if no container
+   with the name `foo-sidecar` already exists.
 
 In the cases above, the webhook can be safely reinvoked, or admit an object that already has the fields set.
 -->
@@ -1891,16 +1928,18 @@ versions. See [Matching requests: matchPolicy](#matching-requests-matchpolicy) f
 <!--
 ### Availability
 
-It is recommended that admission Webhooks should evaluate as quickly as possible (typically in milliseconds), since they add to API request latency.
+It is recommended that admission webhooks should evaluate as quickly as possible (typically in
+milliseconds), since they add to API request latency.
 It is encouraged to use a small timeout for webhooks. See [Timeouts](#timeouts) for more detail.
 
-It is recommended that admission webhooks should leverage some format of load-balancing, to provide high availability and
-performance benefits. If a webhook is running within the cluster, you can run multiple webhook backends behind a service
-to leverage the load-balancing that service supports.
+It is recommended that admission webhooks should leverage some format of load-balancing, to
+provide high availability and performance benefits. If a webhook is running within the cluster,
+you can run multiple webhook backends behind a service to leverage the load-balancing that service
+supports.
 -->
 ### 可用性   {#availability}
 
-建议准入 webhook 尽快完成执行（时长通常是毫秒级），因为它们会增加 API 请求的延迟。
+建议准入 Webhook 尽快完成执行（时长通常是毫秒级），因为它们会增加 API 请求的延迟。
 建议对 Webhook 使用较小的超时值。有关更多详细信息，请参见[超时](#timeouts)。
 
 建议 Admission Webhook 应该采用某种形式的负载均衡机制，以提供高可用性和高性能。
@@ -1912,9 +1951,11 @@ to leverage the load-balancing that service supports.
 Admission webhooks that need to guarantee they see the final state of the object in order to enforce policy
 should use a validating admission webhook, since objects can be modified after being seen by mutating webhooks.
 
-For example, a mutating admission webhook is configured to inject a sidecar container with name "foo-sidecar" on every
-`CREATE` pod request. If the sidecar *must* be present, a validating admisson webhook should also be configured to intercept `CREATE` pod requests, and validate
-that a container with name "foo-sidecar" with the expected configuration exists in the to-be-created object.
+For example, a mutating admission webhook is configured to inject a sidecar container with name
+"foo-sidecar" on every `CREATE` pod request. If the sidecar *must* be present, a validating
+admisson webhook should also be configured to intercept `CREATE` pod requests, and validate that a
+container with name "foo-sidecar" with the expected configuration exists in the to-be-created
+object.
 -->
 
 ### 确保看到对象的最终状态 {#guaranteeing-the-final-state-of-the-object-is-seen}
@@ -1923,7 +1964,7 @@ that a container with name "foo-sidecar" with the expected configuration exists
 则应该使用一个验证性质的 webhook，
 因为可以通过 mutating Webhook 看到对象后对其进行修改。
 
-例如，一个修改性质的准入Webhook 被配置为在每个 `CREATE` Pod 请求中
+例如，一个修改性质的准入 Webhook 被配置为在每个 `CREATE` Pod 请求中
 注入一个名称为 "foo-sidecar" 的 sidecar 容器。
 
 如果*必须*存在边车容器，则还应配置一个验证性质的准入 Webhook 以拦截
@@ -1942,7 +1983,8 @@ When a node that runs the webhook server pods
 becomes unhealthy, the webhook deployment will try to reschedule the pods to another node. However the requests will
 get rejected by the existing webhook server since the `"env"` label is unset, and the migration cannot happen.
 
-It is recommended to exclude the namespace where your webhook is running with a [namespaceSelector](#matching-requests-namespaceselector).
+It is recommended to exclude the namespace where your webhook is running with a
+[namespaceSelector](#matching-requests-namespaceselector).
 -->
 ### 避免自托管的 Webhooks 中出现死锁 {#avoiding-deadlocks-in-self-hosted-webhooks}
 
@@ -1971,7 +2013,7 @@ set to `NoneOnDryRun`. See [Side effects](#side-effects) for more detail.
 -->
 ### 副作用  {#side-effects}
 
-建议准入 Webhook 应尽可能避免副作用，这意味着该准入 webhook 仅对发送给他们的
+建议准入 Webhook 应尽可能避免副作用，这意味着该准入 Webhook 仅对发送给他们的
 `AdmissionReview` 的内容起作用，并且不要进行额外更改。
 如果 Webhook 没有任何副作用，则 `.webhooks[].sideEffects` 字段应设置为
 `None`。

From 0111d739b6272e27c6289c768c0f11e0197a9a99 Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Tue, 25 Apr 2023 21:48:06 +0800
Subject: [PATCH 268/272] sync status.md

sync status.md
---
 .../reference/kubernetes-api/common-definitions/status.md     | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/zh-cn/docs/reference/kubernetes-api/common-definitions/status.md b/content/zh-cn/docs/reference/kubernetes-api/common-definitions/status.md
index 0d3a6de1b6f..3b1a2be574e 100644
--- a/content/zh-cn/docs/reference/kubernetes-api/common-definitions/status.md
+++ b/content/zh-cn/docs/reference/kubernetes-api/common-definitions/status.md
@@ -158,10 +158,10 @@ guide. You can file document formatting bugs against the
 
     <!--
     UID of the resource. (when there is a single resource which can be described). 
-    More info: http://kubernetes.io/docs/user-guide/identifiers#uids 
+    More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#uids
     -->
     资源的 UID（当有单个可以描述的资源时）。
-    更多信息： http://kubernetes.io/docs/user-guide/identifiers#uids
+    更多信息： https://kubernetes.io/zh-cn/docs/concepts/overview/working-with-objects/names#uids
 
 - **kind** (string)
 

From fe878980eb28071af2c20be75c165a4d1f475f19 Mon Sep 17 00:00:00 2001
From: Kensei Nakada <handbomusic@gmail.com>
Date: Wed, 26 Apr 2023 07:58:00 +0900
Subject: [PATCH 269/272] Add the deprecation notice of
 KubeSchedulerConfiguration v1beta3

---
 content/en/docs/reference/scheduling/config.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/content/en/docs/reference/scheduling/config.md b/content/en/docs/reference/scheduling/config.md
index 86391158266..d1ba65585a9 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 ([v1beta3](/docs/reference/config-api/kube-scheduler-config.v1beta3/)
-or [v1](/docs/reference/config-api/kube-scheduler-config.v1/))
+KubeSchedulerConfiguration [v1](/docs/reference/config-api/kube-scheduler-config.v1/)
 struct.
 
 A minimal configuration looks as follows:
@@ -35,9 +34,10 @@ clientConnection:
 
   {{< note >}}
   KubeSchedulerConfiguration [v1beta2](/docs/reference/config-api/kube-scheduler-config.v1beta2/)
-  is deprecated in v1.25 and will be removed in v1.26. Please migrate KubeSchedulerConfiguration to
-  [v1beta3](/docs/reference/config-api/kube-scheduler-config.v1beta3/) or [v1](/docs/reference/config-api/kube-scheduler-config.v1/)
-  before upgrading Kubernetes to v1.25.
+  is deprecated in v1.25 and will be removed in v1.28. 
+  KubeSchedulerConfiguration [v1beta3](/docs/reference/config-api/kube-scheduler-config.v1beta3/)
+  is deprecated in v1.26 and will be removed in v1.29.
+  Please migrate KubeSchedulerConfiguration to [v1](/docs/reference/config-api/kube-scheduler-config.v1/).
   {{< /note >}}
 ## Profiles
 

From 136bdad0d4a00c296da6ca72baa09731aba729c7 Mon Sep 17 00:00:00 2001
From: Niranjan Darshan <niranjan.darshan@india.nec.com>
Date: Wed, 26 Apr 2023 08:30:16 +0530
Subject: [PATCH 270/272] Fixed broken link blog 2022 (#40663)

* Fixed broken link blog 2022

* added correct link
---
 content/en/blog/_posts/2022-12-27-cpumanager-goes-GA.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/blog/_posts/2022-12-27-cpumanager-goes-GA.md b/content/en/blog/_posts/2022-12-27-cpumanager-goes-GA.md
index d1edc4575b0..d7ced81802d 100644
--- a/content/en/blog/_posts/2022-12-27-cpumanager-goes-GA.md
+++ b/content/en/blog/_posts/2022-12-27-cpumanager-goes-GA.md
@@ -40,7 +40,7 @@ compatible behavior when disabled, and to document how to interact with each oth
 
 This enabled the Kubernetes project to graduate to GA the CPU Manager core component and core CPU allocation algorithms to GA,
 while also enabling a new age of experimentation in this area.
-In Kubernetes v1.26, the CPU Manager supports [three different policy options](/docs/tasks/administer-cluster/cpu-management-policies.md#static-policy-options):
+In Kubernetes v1.26, the CPU Manager supports [three different policy options](/docs/tasks/administer-cluster/cpu-management-policies#static-policy-options):
 
 `full-pcpus-only`
 : restrict the CPU Manager core allocation algorithm to full physical cores only, reducing noisy neighbor issues from hardware technologies that allow sharing cores.

From 235c5be1b773135ebfc510ba966ad3751684aef2 Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Tue, 25 Apr 2023 21:54:13 +0800
Subject: [PATCH 271/272] sync service-topology.md

sync service-topology.md
---
 .../docs/concepts/services-networking/service-topology.md     | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/zh-cn/docs/concepts/services-networking/service-topology.md b/content/zh-cn/docs/concepts/services-networking/service-topology.md
index f605350272e..b9a3f188a05 100644
--- a/content/zh-cn/docs/concepts/services-networking/service-topology.md
+++ b/content/zh-cn/docs/concepts/services-networking/service-topology.md
@@ -20,12 +20,12 @@ weight: 150
 <!--
 This feature, specifically the alpha `topologyKeys` API, is deprecated since
 Kubernetes v1.21.
-[Topology Aware Hints](/docs/concepts/services-networking/topology-aware-hints/),
+[Topology Aware Routing](/docs/concepts/services-networking/topology-aware-routing/),
 introduced in Kubernetes v1.21, provide similar functionality.
 -->
 此功能特性，尤其是 Alpha 阶段的 `topologyKeys` API，在 Kubernetes v1.21
 版本中已被废弃。Kubernetes v1.21 版本中引入的
-[拓扑感知的提示](/zh-cn/docs/concepts/services-networking/topology-aware-hints/),
+[拓扑感知路由](/zh-cn/docs/concepts/services-networking/topology-aware-routing/),
 提供类似的功能。
 {{</ note >}}
 

From d5a5370ba2614f0fe38b2e1275b0be349898cc46 Mon Sep 17 00:00:00 2001
From: ydFu <ader.ydfu@gmail.com>
Date: Wed, 26 Apr 2023 16:25:41 +0800
Subject: [PATCH 272/272] [zh] sync
 blog\_posts\2022-12-27-cpumanager-goes-GA.md

Signed-off-by: ydFu <ader.ydfu@gmail.com>
---
 content/zh-cn/blog/_posts/2022-12-27-cpumanager-goes-GA.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/zh-cn/blog/_posts/2022-12-27-cpumanager-goes-GA.md b/content/zh-cn/blog/_posts/2022-12-27-cpumanager-goes-GA.md
index 9e7b876d103..48f66608bb9 100644
--- a/content/zh-cn/blog/_posts/2022-12-27-cpumanager-goes-GA.md
+++ b/content/zh-cn/blog/_posts/2022-12-27-cpumanager-goes-GA.md
@@ -88,11 +88,11 @@ compatible behavior when disabled, and to document how to interact with each oth
 <!--
 This enabled the Kubernetes project to graduate to GA the CPU Manager core component and core CPU allocation algorithms to GA,
 while also enabling a new age of experimentation in this area.
-In Kubernetes v1.26, the CPU Manager supports [three different policy options](/docs/tasks/administer-cluster/cpu-management-policies.md#static-policy-options):
+In Kubernetes v1.26, the CPU Manager supports [three different policy options](/docs/tasks/administer-cluster/cpu-management-policies#static-policy-options):
 -->
 这使得 Kubernetes 项目能够将 CPU 管理器核心组件和核心 CPU 分配算法进阶至 GA，同时也开启了该领域新的实验时代。
 在 Kubernetes v1.26 中，CPU
-管理器支持[三个不同的策略选项](/zh-cn/docs/tasks/administer-cluster/cpu-management-policies.md#static-policy-options)：
+管理器支持[三个不同的策略选项](/zh-cn/docs/tasks/administer-cluster/cpu-management-policies#static-policy-options)：
 
 <!--
 `full-pcpus-only`